=== k-s is now known as k-s[AWAY]
=== jcastro_ is now known as jcastro
=== __Purple__ is now known as _Purple_
[10:50]  * Kamping_Kaiser sticks his head in
=== You're now known as ubuntulog
=== k-s[AWAY] is now known as k-s
=== _Purple_ is now known as _Purple_away
[14:53] <genady12lap> hey I am having a problem with ubuntu 9.04 with freq scaling
[14:56] <genady12lap> can some one help me?
=== cooloney_ is now known as cooloney
[16:11] <randompie> Unable to boot kernel shipped with Jaunty Beta on an Nvidia RAID1 mirror. See: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/358255
[16:11] <ubot3> Malone bug 358255 in linux "[jaunty] Root on nvidia raid 1 mirror does not boot" [Undecided,New] 
[16:12] <wamty> anyone know what direction memcpy_tofs or memcpy_fromfs works ?
[16:20] <manjo> randompie, can you try with kernel option rootdelay=60 ? 
=== bdmurray_ is now known as bdmurray
[16:40] <randompie> manjo: what else to try and how to get more information to post here. Will need to reboot system
[16:41] <randompie> Also how to know what is the exact kernel package?
[16:41] <manjo> ?? uname -a should tell you what kernel you are currently running 
=== k-s is now known as k-s[AWAY]
[16:53] <randompie> uname -a only says 2.6.28-11. Current package is 2.6.28-11.38. How do I get those last 2 digits - the "-38" part.
[17:20] <manjo> randompie, for me uname -a 
[17:20] <manjo> Linux hungry 2.6.28-11-generic #41-Ubuntu SMP Wed Apr 8 04:39:23 UTC 2009 x86_64 GNU/Linux
[17:21] <manjo> randompie, also cat /proc/version
[17:21] <manjo> Linux version 2.6.28-11-generic (buildd@crested) (gcc version 4.3.3 (Ubuntu 4.3.3-5ubuntu4) ) #41-Ubuntu SMP Wed Apr 8 04:39:23 UTC 2009
[17:22] <rtg> manjo: 'cat /proc/version_signature'
[17:22] <manjo> proc/version
[17:23] <randompie> Thanks. It now says: cat /proc/version_signature 
[17:23] <randompie> Ubuntu 2.6.28-11.40-generic
[17:24] <randompie> manjo, rtg: so what is the latest? and how to install it?
[17:25] <manjo> randompie, for jaunty ? 
[17:26] <manjo> randompie, I updated on the 8th and its 41, I dont have any updates yet for amd64
[17:28] <manjo> randompie, were  you able to reboot with the kernel option I mentioned ? did the hdds come up ? 
[17:28] <SEJeff> I'm writing up a rough howto help you guys troubleshoot guide to a guy seeing deadlocks on an ubuntu nfs server (on the ubuntu-hardened ML)
[17:29] <randompie> so, I should file bug against #40 only. The wrong initrd drops me to a busybox sheel. How can I gather information from there to help people debug this. Also, has the ubuntu kernel made changes  as to what gets modularized and what not?
[17:29] <randompie> No, I haven't tried re-booting yet.
[17:29] <SEJeff> I'm going to suggest he go through the setups to setup crash like installing the crash package and add "crashkernel=128M@16M" to his kernel commandline
[17:29] <SEJeff> How do you install kernel debuginfo packages in ubuntu?
[17:30] <randompie> manjo: signing off to reboot.
[17:30] <manjo> k
=== manjo is now known as manjo_brb
[17:39] <rtg> SEJeff: I started a page at https://wiki.ubuntu.com/KernelTeam/CrashdumpRecipe. At last test, 32 bit still has some issues.
[17:41] <SEJeff> rtg, Oh wow I was basicly going to write up something very similar
[17:41] <SEJeff> Hopefully we can get this user to create a vmcore and attach it to a bug report. Thanks
[17:41] <rtg> SEJeff: feel free 'cause that page needs serious help.
[17:43] <SEJeff> rtg, I'm guessing linux-crashdump is intrepid+ ?
[17:44] <rtg> SEJeff: its a meta package taht also exists in Jaunty
[17:45] <SEJeff> Right but this is a "production" server in hardy
[17:45] <SEJeff> Too bad that packages isn't in hardy
[17:45] <SEJeff> The user sees the server panic/deadlock when an nfs client accesses it.
[17:45] <SEJeff> Kind of a big deal in an LTS release I'd think
[17:45] <rtg> SEJeff: yeah, it may not exist for Hardy
[17:45] <SEJeff> rtg so what needs to be installed other than crash?
[17:46] <rtg> SEJeff: kexec-tools
[17:48] <SEJeff> thanks. Most of my crash experience is on RHEL boxes. With crash and kexec-tools installed on a vanilla hardy install will it save the vmcore to somewhere like /var/crash?
[17:48] <SEJeff> Or will we need to fudge with the kernel.core_pattern sysctl
[17:48] <rtg> SEJeff: I'm not as familiar with Hardy, but that is the way Intrepid and Jaunty work.
[17:53] <SEJeff> Ok
[17:53] <SEJeff> thanks for the help tim
=== k-s[AWAY] is now known as k-s
[18:02] <randompie> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/358255 no chnage with rootdelay=60
[18:02] <ubot3> Malone bug 358255 in linux "[jaunty] Root on nvidia raid 1 mirror does not boot" [Undecided,New] 
[18:05] <deshantm_laptop> randompie: rootdelay=60 might not be long enough (for some things i have worked with it is not)
[18:05] <deshantm_laptop> not sure about the raid case
[18:06] <randompie> It works fine with a 2.6.27-13 initrd
[18:06] <deshantm_laptop> randompie: did you cat /proc/modules when you were dropped to the (initramfs) prompt?
[18:09] <randompie> yes. no mapper modules. incidentally, the mirror code is compiled into 2.6.28-11. These are modules in 2.6.27-13
[18:10] <deshantm_laptop> did the modules require any arguments? would the kernel command line need any arguments?
[18:12] <randompie> nope. no argument needed. the old initranfs boots out of the box. Actually, currently running a 2.6.28-11 kernel but with the old initramfs. The dm* modules are not loaded in this kernel.
[18:13] <deshantm_laptop> i am pretty sure that kernel version and modules version need to match for the initramfs to work
=== manjo_brb is now known as manjo
[18:20] <randompie> deshantm_laptop: then why does it work? What is the difference between the two scenarios? What I could dig out was that 2.6.28-11 compiles in a lot of stuff that 2.6.27-13 made modules - a simple comparison of the config shows that. The size of the initrd is also a pointer in this direction - there is a 1 MB size difference between the 2 initrds.
[18:21] <randompie> manjo: the rootdelay=60 did not work :(
[18:21] <manjo> randompie, did u try to upgrade to the latest kernel and make sure the initrd and kernel matches ? 
[18:23] <manjo> randompie, waht version are you running ? hardy/intrepid/jaunty ? 
[18:23] <randompie> I am running Ubuntu 2.6.28-11.40-generic. I did an update-initramfs multiple times to no avail. Jaunty-Beta
[18:24] <manjo> randompie, waht is your bug #  
[18:24] <randompie> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/358255
[18:24] <ubot3> Malone bug 358255 in linux "[jaunty] Root on nvidia raid 1 mirror does not boot" [Undecided,New] 
[18:28] <manjo> randompie, can you remove the quiet splash option from your boot command line and report what boot messages you see ? 
[18:29] <randompie> will do. If I gain get dropped to an initramfs, how can I copy the dmesg stuff out so as to look at it/post it here?
[18:29] <manjo> randompie, you can take a photo of the boot screen with your cell ? 
[18:29] <manjo> attach to the bug 
[18:31] <randompie> manjo: nothing more hi-tech than that?
[18:31] <manjo> heh that is acceptable hi tech debugging tool :)
[18:33] <manjo> randompie, and oh! reduce your screen font size
[18:33] <manjo> so that you get all the messages
[18:34] <manjo> randompie, setfont /usr/share/consolefonts/Uni1-VGA8.psf.gz
[18:34] <randompie> how do I reduce screen font size?
[18:34] <manjo> sorry
[18:34] <manjo> you may not be able to do that .. 
[18:34] <manjo> n
[18:34] <manjo> never mind
[18:35] <manjo> just remove quiet splash and reboot ... and see what messages you get 
[18:36] <randompie> so setfont is persistent across re-boots, right?
[18:37] <manjo> no
[18:37] <manjo> I was wrong 
[18:38] <randompie> Yes, I think the compiled in font takes precedence at boot time. Will get back to you. Just uploaded 1 photo taken earlier. Please check.
[18:38] <manjo> randompie, I think there is a vga=XX option for the kernel
[18:39] <SEJeff> manjo, randompie, yes it depends on the resolution you want the console fonts to be
[18:39] <manjo> SEJeff, I think he left 
[18:40] <SEJeff> manjo, Unless you know the resolution he should set it to you can tell him to put "vga=ask" for a mini-menu to select the resolution
[18:41] <manjo> SEJeff, k .. I think he is rebooting now will ask him when he returns
[18:41] <SEJeff> cool
[18:42] <SEJeff> manjo, http://www.linuxforums.org/forum/misc/2244-how-do-i-set-command-line-screen-resolution-rh9.html#post13498
[18:42] <SEJeff> There is a good start
[18:43] <manjo> so highest resolution -- smallest font ? 
[18:43] <manjo> or vice versa ? 
[18:43] <SEJeff> manjo, Correct
[18:44] <SEJeff> Depending on the display device he is using, if it is too high (for an lcd) it won't display. It will just say something like "resolution out of range"
[18:44] <SEJeff> And for a CRT it would just be unreadable
[18:44] <SEJeff> Generally just set it to the native resolution of the display and that should be good.
[18:44] <manjo> k thanks for the link 
[18:44] <SEJeff> np
[18:45] <SEJeff> vga=791 is generally a safe bet though
[18:45] <manjo> I suspect he might be hitting a casper bug
[18:46] <SEJeff> yuck
[18:46] <genady12lap> hey
=== fabbione-vac is now known as fabbione
[19:03] <genady12lap> heyhey I am having a problem with ubuntu 9.04 with freq scaling
[19:22] <randompie> manjo: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/358255 updated with photos
[19:22] <ubot3> Malone bug 358255 in linux "[jaunty] Root on nvidia raid 1 mirror does not boot" [High,Triaged] 
[19:31] <genady12lap> someone here?
[19:32] <genady12lap> why SpeedStep compiled into the kernel?
=== ivoks_ is now known as ivoks
=== k-s is now known as k-s[AWAY]
=== k-s[AWAY] is now known as k-s
=== k-s is now known as k-s[AWAY]
=== k-s[AWAY] is now known as k-s
=== zul_ is now known as uzl
=== uzl is now known as zul
[20:08] <t|tp> Is this the correct channel to ask questions about make-kpkg?
[20:43] <SEJeff> rtg, I'm not sure if the kdump stuff will work on hardy without some manual hackery. What do you think of adding an init script like on RHEL to save cores on boot to /var/crash/$DATEHASH?
[20:44] <SEJeff> And how does jaunty do it? I've not got a jaunty box here in the office to play with and the dsl at home is down
[20:44] <rtg> SEJeff: Jaunty just drops them in /var/crash, but won't over write an existing crash dump
[20:44] <SEJeff> rtg, Ok is there an init script somewhere on boot that does that?
[20:45] <SEJeff> Like there is in RHEL/centos?
[20:45] <rtg> SEJeff: for Jaunty its called 0_kdump and gets dropped into the /usr/share/initramfs somewhere
[20:45] <SEJeff> Ah ok
[20:46] <SEJeff> So none of that is done in hardy. The user will have to manually do it. Would it be difficult to backport the latest crash and linux-crashdump metapackage to hardy-backports?
[20:47] <rtg> SEJeff: it shouldn't be too hard. You'll probably want to run those patches through the k-t list, directed to Stefan Bader (smb)
[20:49] <SEJeff> Alright I'll try to setup a hardy vm and do it sometime this week. Thanks again
[20:49] <rtg> SEJeff: in the kexec-tools package, debian/rules installs debian/kdump.initramfs as /usr/share/initramfs-tools/scripts/init-bottom/0_kdump
[20:50] <SEJeff> ok
=== lamont` is now known as lamont
=== _Purple_away is now known as _Purple_
=== asac_ is now known as asac
=== SEJeff is now known as SEJeff_away
[23:44] <Nozelf> Hi, I'm trying to boot backtrack on my laptop from my flashdrive, but when I exec ./bootinst.sh i recieved Fatal: Cannot open /dev/loop: No such file or directory
[23:45] <Nozelf> Is a flashdrive problem?