[07:18] <smb> morning .+
[07:21]  * smb grumbles a bit about short lived hardware
[07:39] <cking> smb, what's broken?
[07:41] <smb> cking, Most likely the mainboard of my working desktop (cannot rule out cpu completely). Just refuses to stay powered now. You press the power switch and at least the cpu fan and the drive bays light up. You release it and all goes off. 
[07:41] <smb> s/working/work/ as it is not working right now... :-P
[07:42] <smb> At least I was able to transfer the important stuff over to the travel netbook by moving all hdds somewhere else.
[07:43] <smb> But that board was "just" 2yrs old... :-P
[07:44] <smb> cking, Btw, your oneiric system does not show upstart-udev-bridge daemon eating all your cpu time, does it?
[07:44] <cking> what was the make of the board?
[07:44] <smb> cking, asrock
[07:44] <cking> asrock does not rock then
[07:45] <cking> smb,  upstart-udev-bridge daemon is OK for me
[07:46] <smb> Unfortunately if I want to only replace the board I seem to be stuck with them. As am2+ is not really state of the art anymore. Hard to find just a replacement. But I'd hate to waste the ram (or cpu if its still working)
[07:46] <smb> cking, upstart seems to be in a monologue here:
[07:46] <smb> write(2, "arguments to dbus_message_iter_a"..., 232) = 232
[07:46] <smb> write(2, "process 380: ", 13)
[07:46] <smb> repeating over and over
[07:47] <smb> and upstart-udev-bridge being pid 380
[07:48] <cking> smb, what happens if you do sudo service udev stop (and then start again)?
[07:50] <smb> cking, The new process seems ok and stays in select...
[07:52] <smb> Seems to have cured it so far. Took a while between the stop until the bridge deamon really went away.
[07:52] <smb> System feels much smoother now. :-P
[08:03] <cking> smb, so do you think the motherboard has dry solder joints that fail due to thermal expansion/contraction?
[08:06] <smb> cking, No rather not, because it usually did stay on for the day without issues. It could be failed capacitors or something else with the on-board power routing. At least the problem remained the same after replacing power supply (which would also give some time to cool down)
[11:45] <Ceno3x> Hi guys. I need to build a source package for a kernel I'm working on so I can then upload it to launchpad. I'm already building the packages with make-kpkg so I shouldn't be too far off. Can anyone point me in the right direction?
[12:16] <TeTeT> Ceno3x: for building source packages I usually use debuild -S from the packages main directory
[14:16]  * ogasawara back in 20
[14:56] <ppisati_> apw: cve 1083 in the cve matrix is marked as "needed" for almost all releases
[14:56] <apw> yes we don't have an upstream fix for it yet
[14:57] <apw> i have passed that back to the security team for resolution
[14:57] <ppisati_> apw: but the corresponding lp bug says only hardy and linux-ec2 need it since all the others are marked as "fix released"
[14:57] <ppisati_> lp 813935
[14:57] <apw> bug is incorrect i beleieve
[14:57] <ubot2> Launchpad bug 813935 in linux-ti-omap4 "CVE-2011-1083" [Low,Fix released] https://launchpad.net/bugs/813935
[14:57] <ppisati_> ah ok
[14:57] <bjf> ppisati, bug #865171, please verify
[14:57] <ubot2> Launchpad bug 865171 in linux-ti-omap4 "enable ftrace for the 80211 layer" [Undecided,Fix committed] https://launchpad.net/bugs/865171
[14:59] <ppisati_> bjf: do i manually change the tag to "verification done" or is thjere any script that i should run?
[15:16] <apw> ppisati_, i believe it is manual, just put some comment on and change it
[15:24] <ppisati_> ok, done
[15:27] <bjf> ppisati_, i believe the tag is "verification-done-oneiric"
[15:27] <bjf> ppisati_, and you change it manually
[15:49] <bjf> herton, sconklin, bug #880476
[15:49] <ubot2> Launchpad bug 880476 in linux "after update to kernel 3.0.0-13 ubuntu 11.10 does not start" [High,Triaged] https://launchpad.net/bugs/880476
[15:49] <jpds> Is there any way I can install an oneiric kernel on a Lucid machine?
[15:49] <jpds> I have a USB adapter that works on oneiric, but doesn't on Lucid.
[15:50] <jpds> And the Natty backport kernel doesn't seem to do the trick.
[15:50] <bjf> jpds, you can install the lts-backport-oneiric package (currently in -proposed)
[15:50] <jpds> bjf: Oh, I didn't look in there - I'll try that; thanks.
[15:55] <jsalisbury> bjf, sconklin, herton, Possible oneiric-proposed kernel regression: bug 880476
[15:55] <ubot2> Launchpad bug 880476 in linux "after update to kernel 3.0.0-13 ubuntu 11.10 does not start" [High,Triaged] https://launchpad.net/bugs/880476
[15:59] <sconklin> jsalisbury: ack
[16:02] <jsalisbury> sconklin, I'm going to try 3.0.0-13 on my laptop now.
[16:03] <bjf> jsalisbury, you should have -proposed enabled :-)
[16:04] <jsalisbury> bjf, yes I do :)
[16:09] <ppisati_> apw: cve 1767/hardy - nitpick: +goto out;;
[16:09] <apw> yep thats a bit shit :)
[16:10] <apw> clearly writing too much shell right now
[16:10] <apw> ppisati_, do reply and point it out formally and i can get it fixed on application
[16:24] <focalt> hey guys
[16:25] <focalt> suddently after installing a rt-kernel
[16:25] <focalt> I loss admin rights
[16:25] <focalt> I dunno why...
[16:25] <focalt> I just cant install anything from synaptic
[16:25] <focalt> or by typing sudo...
[16:25] <apw> focalt, try rebooting into a different kernel
[16:25] <focalt> it's the same
[16:26] <focalt> apw, 
[16:26] <focalt> it's the second time this happens...
[16:26] <focalt> I'm tired of reinstalling system :
[16:26] <focalt> :\
[16:27] <jjohansen> focalt: boot into runlevel 1, and see what is going on
[16:28] <focalt> jjohansen, sorry you must be more specific than that... i'm kind of new to linux  
[16:29] <jsalisbury> bjf, sconklin, herton, re bug 880476 I was able to boot into 3.0.0-13 without and issue.
[16:29] <ubot2> Launchpad bug 880476 in linux "after update to kernel 3.0.0-13 ubuntu 11.10 does not start" [High,Triaged] https://launchpad.net/bugs/880476
[16:29] <tgardner> jsalisbury, its gotta be HW specific
[16:30] <jsalisbury> tgardner, I have a Lenovo x201
[16:30] <jjohansen> focalt: okay, when you boot you can specify the run level as part of the kernel command line for grub.  putting a 1 in there will result in the machine booting in single user mode, with no need to log in.  You are root and have full access
[16:31] <tgardner> jsalisbury, get him to re-install it by copying the deb from the archive, then 'sudo dpkg -i linux-image*'
[16:31] <tgardner> make sure he's got enough disk space
[16:31] <jsalisbury> tgardner, will do
[16:31] <focalt> jjohansen, and how do I do that. i mean where do I put that run level?
[16:31] <jjohansen> focalt: in grub when you go to select a kernel select edit
[16:32] <tgardner> jsalisbury, I think he's got initrd issues if it can't find the rootfs
[16:32] <jjohansen> on the line with the linux kernel and its options, splash, vt.handoff etc you just add a 1
[16:33] <jsalisbury> tgardner, there was one other person reporting this issue as well.  Comment #25
[16:33] <jjohansen> make sure it is separated by a space
[16:33] <herton> jsalisbury, tgardner: yeah, can some bug/issue with the disk controller module used or initramfs related problem
[16:33] <ppisati_> focalt: so you can login, right? and if yes, what's happend if you open a terminal and execute "sudo id"?
[16:33] <ppisati_> s/login/log in/
[16:34] <ppisati_> s/what's/what does it/
[16:34] <jjohansen> focalt: so eg.
[16:34] <jjohansen>   linux   /boot/vmlinuz-3.0.0-12-generic root=UUID=7df1f324-9c3e-4ec0-9eb5-1bc0e383ce64 ro   quiet splash nomodeset vt.handoff=7 1
[16:37] <focalt> jjohansen, ppisati_, I guess I found my problem 
[16:37] <focalt> I did sudo usermod -G audio focalt
[16:37] <focalt> in my /etc/group file
[16:38] <focalt> I have my username only in the audio group
[16:38] <tgardner> jsalisbury, how do you know you have the same platform ?
[16:38] <jsalisbury> tgardner, I don't have the same platform.  The bug reporter has an Acer and I have a Lenovo.
[16:39] <tgardner> jsalisbury, oh, I guess I was confused.
[16:39] <ppisati_> focalt: 
[16:39] <jsalisbury> tgardner, I wan't able to reproduce on my machine.  I asked the other person affected by this for their hardware details.
[16:39] <ppisati_> from the man page
[16:39] <ppisati_> "If the user is currently a member of a group which is not listed, the user will be removed from the group. This behaviour can be changed via the -a option, which appends the user to the current supplementary group list.
[16:39] <ppisati_> "
[16:39] <ppisati_> -G option
[16:40] <ppisati_> you missed the -a option
[16:40] <focalt> ppisati_, yep
[16:40] <focalt> I guess that's it 
[16:40] <focalt> so if I reboot in recovery mode
[16:41] <focalt> and change the group file?
[16:41] <focalt> will solve this shit?
[16:41] <ppisati_> focalt: yep
[16:42] <ppisati_> focalt: here is a list of groups my user is in http://paste.ubuntu.com/718970/
[16:42] <focalt> thanks man :)
[16:42] <focalt> ppisati_, your username is flag right?
[16:43] <tgardner> skaet, do you know if there is a bug filed to make sure the Natty and Oneiric LTS kernels get onto the next Lucid DVD point release ?
[16:43] <jsalisbury> tgardner, do you have a link to the kernel deb archive?  I thought it was off here: http://kernel.ubuntu.com/~kernel-ppa/  But I guess not.
[16:44] <tgardner> jsalisbury, http://archive.ubuntu.com/ubuntu/pool/main/l/linux/
[16:44] <skaet> tgardner, not aware of one,  but haven't hunted for it either.   Probably best to just submit and mark it for lucid-updates.
[16:44] <jsalisbury> tgardner, thanks
[16:44] <tgardner> skaet, will do
[16:44] <skaet> tgardner, thanks.
[16:48] <tgardner> skaet, bug #881529
[16:48] <ubot2> Launchpad bug 881529 in debian-installer "Natty and Oneiric LTS backport kernels need to get onto the Lucid 10.04.4 point release DVD." [High,In progress] https://launchpad.net/bugs/881529
[16:50] <skaet> tgardner, thanks.
[17:23] <smoser> smb, around ?
[17:24] <smb> In some way. Whats up?
[17:24] <smoser> if i tell you that i did not issue a reboot, how would you think that https://launchpadlibrarian.net/83606521/precise-daily-amd64-server-20111024-m1.large-ebs.log got rebooted?
[17:24] <smoser> is there some watch dog device now ?
[17:25] <smb> Not that one would come to my mind
[17:26] <smb> Could amazon have implemented something?
[17:26] <smoser> so what else would have done that ? can xen host somehow spy? 
[17:26] <smoser> yeah... i wouldnt hvae thought they'd implement something, and i would hope they wouldn't do something other than adding a watchdog device
[17:28] <smb> Well, if there is a device it would be something that comes with our kernel. 
[17:28] <smb> Though I have not looked there, yet for tsomething like that
[17:29] <smb> Hm, maybe one can detect when the cpus go into some sort of stop after the panic...
[17:30] <smb> It would be something to look when my next crash happens. Maybe even in xm list there would be a different state than "b"
[17:35] <smb> And in kernel 3.0 there is a xen watchdog timer, which we compile as module. But that requires a hypervisor of 4.0 or higher. And Amazon normally is back on 3.4
[17:48] <nigelb> manjo: ohai
[17:48] <nigelb> Is there a track named hwe?
[17:49] <manjo> nigelb, nope
[17:49] <nigelb> manjo: that's why your BP isn't scheeduled.
[17:50] <manjo> nigelb, so I will need to rename HWE to say kernel ? 
[17:50] <nigelb> Yeah.
[17:51] <manjo> nigelb, since there is no kernel track I am going to use hardware
[17:51] <nigelb> np!
[17:51] <manjo> pgraner, ^ I guess you are ok with that ? 
[17:51] <nigelb> Just make sure it exists
[17:52] <nigelb> There is a kernel...
[17:52] <nigelb> ah.. linaro.
[17:53] <manjo> nigelb, done thanks  a ton
[17:53] <nigelb> manjo: np!
[17:53] <manjo> wait for it to show up on the schedule I guess .. 
[17:53] <nigelb> Yeah, it runs on the hour I think.
[17:53] <nigelb> There's a cron
[17:57]  * tgardner -> lunch
[18:01] <cking> manjo, hwe is 2nd class citizen ;-)
[18:01] <manjo> cking, now I know the secret of you leaving :) 
[18:02] <cking> heh
[18:02] <manjo> :) 
[18:04] <manjo> nigelb, where are you located ?
[18:05] <mah> Need Help during kernel building : when booting it shows fuse: device not found
[18:05] <nigelb> manjo: Bangalore :)
[18:06] <nigelb> manjo: Oh, Happy Diwali. The crackers seem to have subsided for the night here finally ;)
[18:06] <manjo> nigelb, thanks :) 
[18:07] <mah> fuse: device not found  ????
[19:30] <wmp> hello
[19:31] <wmp> i have problem with wireless driver, from brcmacs i want to switch driver to broadcom-wl
[19:31] <wmp> how to do it?
[19:42] <lamont> [14606.979430] ieee80211 phy0: wl0: wlc_recv: dropping a frame with invalid src mac address, a2: 00:00:00:00:00:00
[19:42] <lamont> ^^ I hate that my logfile is full of these
[19:46] <tgardner> lamont, I hate that you have to use a broadcom staging driver. Oneiric ?
[19:47] <lamont> oneiric
[19:47] <lamont> 12:00.0 Network controller: Broadcom Corporation BCM4313 802.11b/g/n Wireless LAN Controller (rev 01)
[19:48] <tgardner> lamont, yeah, that error message seems entirely superfluous. I wonder if it exists in 3.1
[19:50] <wmp> lamont: i have this same wifi card
[19:50] <tgardner> lamont, try the precise kernel. Broadcom is mainline in that version. http://archive.ubuntu.com/ubuntu/pool/main/l/linux/linux-image-3.1.0-1-generic_3.1.0-1.1_amd64.deb
[19:50] <lamont> wmp: it's very, um, chatty
[19:51] <wmp> lamont: now i testing support on broadcom-wl
[19:53] <tgardner> lamont, uh, nevermind. its still staging in 3.1
[19:54] <tgardner> maybe I can dial down the chattiness by changing wiphy_err to wiphy_dbg
[19:54] <lamont> figures
[19:55] <lamont> I would support such a notion, even more so if it made it into oneiric-updates eventually
[19:55] <tgardner> lamont, yep, thats my plan
[19:55] <cking> tgardner, you going to UHS this year?
[19:56] <tgardner> cking, I think so. I'm working o a git foo presentation for it.
[19:56] <lamont> now I just need to understand why xfce and my laptop hate each other
[19:56]  * cking wonders if he should be attending...
[19:56] <tgardner> lamont, will start a bug and attach the relevant info including the log noise.
[19:56] <tgardner> will you*
[20:00] <lamont> tgardner: sure.  may be tomorrow when I finally get it filed
[20:00] <tgardner> lamont, ok, just lemme know.
[20:00] <lamont> will do
[20:04] <tgardner> lamont, it seems to be cleaned up in the 3.2 merge, and it has gone mainline (i.e., no longer staging)
[20:05] <hggdh> herton: ping
[20:05] <herton> hggdh: pong
[20:05] <hggdh> herton: are we going to respin 3.0.13? If so, I will refrain from testing it
[20:06] <herton> hggdh: yes, it'll be respinned, one bug failed verification
[20:06] <hggdh> herton: ack, thank you. I will wait for the respin, then. Same tracking bug?
[20:07] <herton> hggdh: nope, it'll be a new tracking bug I expect. sconklin or bjf will take care, I'm going to take 3 days off beginning tomorrow
[20:08] <hggdh> k, thank you
[20:13] <lamont> if I want to flush entries from /proc/net/ip_conntrack, can I do that easily>
[20:14] <tgardner> lamont, you didn't used to be able to, but I'm thinking you ought to be able to now, especially with the advent of network name spaces.
[20:15] <lamont> cool
[20:16] <tgardner> lamont, http://linux.die.net/man/8/conntrack