[02:44] <joewilliams> i am having pretty consistent kernel panics with 10.04, i installed linux-crashdump (per https://wiki.ubuntu.com/Kernel/CrashdumpRecipe) but it does not seem to collect the core and reboot automatically. any ideas?
=== ogasawara__ is now known as ogasawara
[04:20] <joewilliams> weird, wrt my earlier message, it works fine in my vmware image but not on my actual servers. any insight is appreciated
[04:21] <jk--> joewilliams: do you have the message from the kernel panic?
=== joewilliams is now known as joewilliams_away
[06:42] <El_Presidente> hi, i have to bisect the ubuntu kernel for a bug  how do i get this first test kernel elegantly installed?
[07:00] <RAOF> Running “fakeroot debian/rules binary-generic” is a good way to get .debs out of the kernel git tree.
[07:00] <RAOF> After the appropriate supplications to the machine god, obviously.
[07:04] <RAOF> El_Presidente: Some of the requisite supplications can be found https://wiki.ubuntu.com/KernelTeam/KernelForIdiots
[07:05] <El_Presidente> ty
=== yofel_ is now known as yofel
[11:35] <smoser> apw, jjohansen mentioned a "console/upstart" that you are working on. do you have that number ?
[11:37] <apw> smoser, yep .... am working on a bug where upstart jobs fail to open the console randomly
[11:37] <smoser> number ?
[11:37] <apw> bug #554172
[11:37] <ubot2> Launchpad bug 554172 in linux (Ubuntu Maverick) (and 2 other projects) "system services not starting at boot (affects: 187) (dups: 15) (heat: 826)" [High,Confirmed] https://launchpad.net/bugs/554172
[11:38] <smoser> on ec2, i dont see "randomly" for bug 606373
[11:38] <ubot2> Launchpad bug 606373 in linux-ec2 (Ubuntu) (and 1 other project) "cloud-init output does not get to console when booted with pv-grub and ramdisk (affects: 1) (heat: 144)" [Undecided,New] https://launchpad.net/bugs/606373
[11:38] <lag> apw: /dev/sdb1 on /home/lag type ext2 (rw,relatime)
[11:38] <smoser> but hears to hoping you fix it for me
[11:38] <apw> smoser, you do mention randomly for other services though
[11:38] <smoser> i do ?
[11:38] <apw> someone does
[11:39] <lag> apw: From fstab
[11:39] <lag> apw: UUID=1ac09563-457e-44d2-9058-fc77892447ae /home/lag       ext2 relatime                   0  0
[11:39] <apw> smoser, in comments 5 and 6
[11:40] <apw> you imply that actually other things don't get out sometimes too
[11:40] <smoser> oh. well, in my experience, the "random" that I see is based upon some event occuring that "fixes" it.  it seems to me that after some point in boot, it starts working again, but is broken in "early upstart". how many jobs run "early" is random. and the jobs do run, they just dont get data to the console.
[11:45] <apw> smoser, am working on getting a test version of upstart ... once thats working i'll ask you to try it, never know might work
[11:46] <smoser> apw, yeah, that'd be great.
[11:46] <apw> smoser, and if its the same problem that behaviour might be reasonable, as once something opens the console and uses it the issue goes away
[11:47] <smoser> thanks, apw 
[13:02] <apw> smoser, ok finally got the thing built: https://edge.launchpad.net/~apw/+archive/red/+packages
[13:02] <apw> smoser, are you able to test and see if that helps any
[13:03] <smoser> i'll give it a try. hmm.. that changelog entry doesn't seem like it will fix anything for me :)
[13:08] <apw> there were three uploads to get that far ... seems the package in the official packaging branch is missing a builddep, and i also cannot spell
[13:08]  * apw has boot tested it here, only on machines which don't see the issue commonly
[13:09] <apw> but it does at least boot :)
[13:27] <smoser> apw, it doesn't seem to fix it for me. 
[13:27] <apw> smoser, ok thats probabally confirmation its a different issue
[13:28] <smoser> i booted, saw the issue , installed your deb, and cleaned the instance so it thought it would be "first boot" again, rebooted, and still saw issue.
[13:28] <apw> smoser, still a useful indication .... though i have yet to prove it fixes the issue
[13:28] <smoser> there is one program that runs very early in boot (start on MOUNTED=/ and ifup eth0), that outputs a message that i dont see.
[13:29] <apw> smoser, and is that an upstart job (presuming so)
[13:29] <smoser> yes.
[13:30] <smoser> apw, were you suggesting somewhere else, that a open by non-upstart of /dev/console would fix something ?
[13:31] <apw> smoser, that would also fix the issue this upstart should fix ... as holding it open avoids the race which causes the issue for me
[13:31] <apw> it is suggesting its a different issue ... perhaps a console issue on xen
[13:32] <apw> though i need to 100% prove this does fix the issue, which is harder as i cannot reproduce it in upstart
[13:32] <smoser> right.
[13:32] <apw> still a boot test even is useful to me, as its pretty dangerous to upgrade upstart ... its not like we have an older one to boot into
[13:32] <smoser> so if i had an upstart job that did not do console output, that started on starting, opened /dev/console, and then daemonized , that basically would fix it ?
[13:33] <apw> it would be equivalent to the fix in upstart yes
[13:33] <apw> probabally an upstart job with console which did exec sleep 60 would probabally do it
[13:34] <apw> as a confirmation its not that problem
[13:40] <asal> hi all
[13:40] <asal> i have a problem with my usb flash mass storage as follows
[13:40] <asal> when i insert my flash in usb port it is detected by linux & kde but it is mounter only as read-only
[13:40] <asal> and when i use the command "dd of=/dev/sda count=1 bs=512"
[13:40] <asal> it reports me that the file-syste is read-only
[13:41] <asal> this matter is repeated by any linux that i htested including ubuntu-10.10 and knoppix 5.1 and 5.3
[13:41] <asal> is there anyone knowing my solution?
[13:42] <smb> Sure there does not happen to be a write-protect switch?
[13:43] <asal> smb: no 
[13:43] <asal> smb: it has no any key for write-protecting
[13:44] <asal> is was with no problem until is is inserted on a Windows-XP machin and a virus poluted it :-(
[13:45] <asal> and then it get this problem and it is write-protected with all kind of linuxes and also on Windows and DOS and any operating system :-(
[13:45] <asal> it was with no problem until it is inserted on a Windows-XP machin and a virus poluted it :-(
[13:45] <smb> Might be something that sw can change. In dmesg you should see messages from the block layer when the stick gets detected
[13:46] <asal> yes , I saw dmesg and there is a sentence such: "Write-protect is on" :-(
[14:03] <apw> asal what make of stick is it ?
[14:04] <smb> There seem to be rare cases when the write-protection has been activated. Though I only found references to windows programs to low-level format up to now
[14:10] <asal> it is only one filesystem on this memory and of type Fat32, but
[14:10] <asal> this problem is not related to its partitions and type of them, because
[14:10] <asal> after inserting this usb-memory the "dmesg" command reported about this device: "sd 3:0:0:0: [sdc] Write Protect is on"
[14:11] <asal> apw: its type is Kingston - silicon-power
[14:50] <diwic> bug #611810
[14:50] <ubot2> Launchpad bug 611810 in linux-backports-modules-2.6.32 (Ubuntu) (and 1 other project) "[PATCH] NVIDIA GPU audio-over-HDMI: Patch required to support recent GPUs (affects: 1) (heat: 12)" [Undecided,New] https://launchpad.net/bugs/611810
=== joewilliams_away is now known as joewilliams
[15:27] <joewilliams> jk-: yeah here's where i have been putting anything i can gather about it https://bugs.launchpad.net/bugs/614853
[15:27] <ubot2> Ubuntu bug 614853 in linux-ec2 (Ubuntu) "kernel panic divide error: 0000 [#1] SMP (affects: 1) (heat: 6)" [Undecided,New]
=== amitk is now known as amitk-afk
[16:44] <mpoirier> tgardner: is your mumble working properly ?
[16:45] <tgardner> mpoirier, yeah, is yours
[16:45] <mpoirier> tgardner: push-to-talk is acting up again...
[16:45] <mpoirier> sorry.
[16:46] <mpoirier> the problem is on my side. hold on,.
=== cnd is now known as cndougla
[17:54] <JFo> \m/ new laptop transition almost complete
[18:40] <lag> Does anyone know how to mount HDDs once in a schroot?
[18:42] <lag> I've tried:
[18:42] <lag> sudo mount --bind /home/lag /usr3/chroots/maverick-armel/mnt
[18:42] <lag> schroot -c maverick-armel
[18:42] <lag> ls /mnt
[18:42] <lag> <nada>
[18:42] <lag> :(
[18:43] <lag> Also there are no sdXX devnodes in /dev 
[18:43] <lag> :((
[18:43] <lag> blkid
[18:43] <lag> <nada>
[18:43] <lag> fdisk -l
[18:43] <lag> <nada>
[18:43] <lag> ls /dev/disk
[18:44] <lag> <nada>
[19:14] <lag> Sorted 
[19:14] <lag> The answer:
[19:14] <lag> In /etc/schroot/mount-defaults:
[19:14] <lag>  /dev            /dev             none   rw,bind     0       0
[19:14] <lag>  /home/lag   /home/lag  none rw,bind     0       0
[19:14] <lag> :D
[20:13] <apw> lag, nice
[20:13] <lag> It was a 'mare 
[20:48] <lag> Who's responsibility (within Canonical) is this? http://packages.ubuntu.com/maverick/main/newpkg
[20:49] <astinus> http://packages.ubuntu.com/about/
[20:50] <astinus> Or there should be a easy-ish way to file the bug in Launchpad
[20:50] <astinus> I've seen that a lot with Lucid (when in development) and now Maverick
[20:51] <lag> Launchpad - what's that?
[20:51] <lag> ;)
[20:52] <astinus> Something everyone should be forced to learn? ;)
[20:53] <astinus> I think the footer covers the problem adequately...
[20:53] <astinus> "To report a problem with the web site, e-mail frank@lichtenheld.de"
[20:53] <lag> astinus: I saw that, but he doesn't work for Ubuntu
[20:53] <lag> astinus: I'll email him anyway
[20:53] <astinus> lag: But is listed as the maintainer all the same?
[20:53] <astinus> lag: Lots of developers don't *work* for canonical :)
[20:54] <lag> astinus: This is true
[20:54] <lag> Emailing ...
[20:54] <astinus> They do a pretty good job of picking up talent in areas which are difficult or specialist :)
[20:54] <astinus> ie; Kernel development, UX/UI stuff to make things pretty
[20:59] <JFo> lag, will you be in taipei?
[20:59]  * JFo forgets
[21:00] <JFo> and what are you still doing online?
[21:00] <JFo> it must be dark there by now
[21:00] <lag> JFo: Yes, I'll be in Taipei (I'm the first speaker)
[21:00]  * lag quakes
[21:00] <lag> :)
[21:00] <JFo> heh
[21:00] <lag> It is dark
[21:01] <JFo> it is not work time for you anymore... workaholic
[21:02]  * lag has things to get nailed before sleep can commence 
[21:03] <lag> JFo: When are you going to arrive? 
[21:03] <JFo> dunno yet
[21:04] <lag> k
[21:04] <JFo> Pete is fighting with the travel agents
[21:04] <JFo> they are a real pain
[21:04] <lag> Ours are quality 
[21:04] <JFo> yeah, he's resorted to talking to the UK ones now
[21:06] <lag> UK are just better :)
[21:06] <lag> I want to do some herping while I'm in Taiwan :)
[21:07] <JFo> you want to play with snakes?
[21:07] <lag> Did you just look-up herping? :)
[21:07] <JFo> I did
[21:07] <astinus> travel agents in general suck ;)
[21:07] <JFo> Google is my friend :)
[21:08] <astinus> our ones in Spain are *useless* but the UK lot are adequate if you don't mind explaining things 10 times
[21:08] <JFo> <- had no clue what herping was
[21:08] <lag> JFo: Have you seen http://www.lmgtfy.com/
[21:08] <astinus> lol
[21:08] <lag> It's hilarious :)
[21:08] <lag> Type something in
[21:09] <lag> Then send someone the link
[21:09] <lag> Very (patronisingly) amusing 
[21:09] <lag> http://www.lmgtfy.com/?q=herping
[21:09] <JFo> nice
=== kamalmostafa is now known as kamal
[22:04] <lag> Right, that's it, my eyes are beginning to hurt
[22:04] <lag> JFo: Let me know when you'll be arriving in Taipai when you find out
[22:04] <JFo> will do
[22:32] <joewilliams> jk-: have a chance to checkout my bug?
=== sconklin is now known as sconklin-gone