=== chiluk_away is now known as chiluk
=== doko_ is now known as doko
=== soren_ is now known as soren
=== chiluk is now known as chiluk_away
=== smb` is now known as smb
=== henrix_ is now known as henrix
[12:11]  * ppisati goes out for lunch
[12:39] <BenC> rtg: is 6.14 ready for me to rebase against?
[12:42] <rtg> BenC, still build testing. gimme an hour or so.
[12:42] <BenC> rtg: Ok, thanks
[12:42] <rtg> I've only pushed master-next so far
[12:43]  * BenC is glad he isn't the only one awake this early
[12:43] <BenC> Right, that's why I was asking, since I didn't see it in master
[12:43] <rtg> Its nice to get done by 1P so I can still get a bit of sunshine
[12:46] <BenC> rtg: How early does the sun set in your neck of the woods?
[12:47] <rtg> BenC, it was getting pretty dark by 5 when I got home last night. kinda depends on the cloud cover.
[12:51] <BenC> Get's dark 6 here. Honestly, the only reason I'm up this early is because my fiancé started work at 7am and I wake up with her.
[12:51] <BenC> Otherwise, you wouldn't see me till noonish
[12:54] <rtg> BenC, slacker :)
[12:55] <BenC> rtg: It's hard to live the stereotypical programmer life of late night sessions and still be a responsible adult and wake up early :)
[12:55] <rtg> indeed
[12:57]  * cking --> lunch
[12:59] <rtg> BenC, pushed raring master
[13:00] <rtg> haven't built armhf yet, but it ought to be OK
[13:02] <rtg> ogasawara, sforshee: need to reboot gomeisa when its quiet
[13:15] <sforshee> rtg, I'm done with gomeisa
[13:16] <rtg> sforshee, ogasawara has some stuff running so gotta wait for her
[13:22] <BenC> apw, rtg: If any of you guys need remote access to my ppc box, let me know and I'll add an account using your launchpad ssh key
[13:22] <apw> BenC, would love access indeed
=== chiluk_away is now known as chiluk
[13:49]  * henrix -> lunch
[13:59] <rtg> herton, is shank-bot gonna work on raring, i.e., will it emit the upload email or should I annoy ogasawara to send out her finely crafted missive ?
[14:00] <herton> rtg, yes, on my todo list
=== ogasawara_ is now known as ogasawara
[14:00] <herton> rtg, for now you should send manually
[14:00] <rtg> herton, hmm, well I've just upload raring, so I guess I'll have to annoy ogasawara once again. *sigh*
[14:01] <herton> (that is, annoy her :) )
[14:01] <ogasawara> rtg: ack, I'll send it out
[14:01] <rtg> ogasawara, oh, I didn't know you were listening :)
[14:03] <ogasawara> rtg: did you go ahead and bounce gomeisa?  I've not got anything important running so feel free if you haven't already.
[14:03] <rtg> ogasawara, I have not yet. you appeared to have some processes hung
=== Laney is now known as robert_ancell
=== robert_ancell is now known as Laney
[15:39]  * rtg -> vehicle maintenance. back in a bit.
=== henrix_ is now known as henrix
[15:45]  * ogasawara back in 20
[15:52] <jsalisbury> **
[15:52] <jsalisbury> ** Ubuntu Kernel Team Meeting - Today @ 17:00 UTC - #ubuntu-meeting
[15:52] <jsalisbury> **
[16:05] <bjf> brendand, thanks for the help yesterday. having access to that HW really helped.
[16:05] <brendand> bjf, any time
[16:37] <arges> rtg, hi
[16:37] <arges> rtg, fyi dave is in the same room as me, so I can hear you
[16:37] <arges> rtg, my pulse is screwed in raring
[16:37] <ogasawara> haha
[16:37] <rtg> arges, he hasn't said much. does he have a second instance ?
[16:37] <arges> rtg, his audio input doesn't work
[16:37] <arges> hear no evil so no evil
[16:37] <arges> see
[16:38] <rtg> arges, he's missing all of our good natured ribbing
[16:44] <apw> chiluk, welcome
[16:46] <chiluk> thanks guys.
[17:12] <arges> bjf, hey where is that nifty wiki page with the SRU schedules ... I seem to have misplaced that bookmark
[17:12] <bjf> arges, one sec
[17:12] <bjf> arges: https://wiki.ubuntu.com/RaringRingtail/ReleaseInterlock
[17:13] <arges> bjf, thanks
=== jsalisbury changed the topic of #ubuntu-kernel to: Home: https://wiki.ubuntu.com/Kernel/ || Ubuntu Kernel Team Meeting - Tues January 8th, 2013 - 17:00 UTC || If you have a question just ask, and do wait around for an answer!
[17:23] <hggdh> why isn't /var/log/syslog saved when we run 'ubuntu-bug linux'? I have noticed again and again that the oops/bug/error/warning is not always listed in dmesg
=== henrix is now known as henrix_
=== shadeslayer is now known as buildslayer
[17:57] <herton> hggdh, depending on the crash, syslog daemon may be unable to write/sync to the disk, eg. hard freeze etc., it depends
=== henrix_ is now known as henrix
[17:59] <hggdh> herton: in this specific case (bug 1089016) the system is still alive. I got the warning off the syslog; current dmesg is empty
[17:59] <ubot2`> Launchpad bug 1089016 in linux (Ubuntu) "WARNING: at /build/buildd/linux-3.5.0/fs/btrfs/super.c:221 __btrfs_abort_transaction+0x99/0xb0 [btrfs]()" [Undecided,Confirmed] https://launchpad.net/bugs/1089016
[18:02] <herton> hggdh, the system can still be alive yes, but if the file system module crashes, and /var/log/* is under that file system, it'll be unable to write. You can also have another types of crashes, like some deadlock in some write/sync operation, where the system will be alive but no data written because of the nature of the crash.
[18:07] <hggdh> herton: I understand all that. But the syslog was still written to in this case; running 'ubuntu-bug' succeeded, logging in succeeds, etc. But current dmesg is empty. The question still stands: why isnt syslog saved?
[18:07] <herton> hggdh, dmesg is cleared by autotest btw, I think that is what you experienced
[18:08] <hggdh> herton: which then causes a perfectly good bug not to have all necessary data -- in this case, the kernel error itself...
[18:10] <herton> hggdh, I think autotest does that so it can detect errors between tests, not sure since I didn't poked very much on its code. Anyway, if you can grab the crash from syslog or from autotest and post on the bug, I don't think it's a big issue.
[18:11]  * hggdh gives up
[18:29] <rtg> apw, what was that package you uploaded this morning where you had to futz with the symbols ?
[18:52]  * henrix -> EOD
[19:01]  * rtg -> lunch
=== henrix is now known as henrix_
[20:47] <apw> rtg, librostlab-blast
[20:47] <apw> rtg, i put together some dodgy scripting to do that one
[20:57] <jsalisbury> rtg, ogasawara should linux-tools be included for the backport kernel ?  bug 1088454
[20:57] <ubot2`> Launchpad bug 1088454 in linux (Ubuntu) "linux-generic-lts-quantal is missing linux-tools" [Medium,Confirmed] https://launchpad.net/bugs/1088454
=== panda is now known as Guest93521
[21:03] <rtg> apw, I eventually figured out that it was dpkg-gensymbols. the patch management for libpgf utterly defeated me, so I just hacked in the diff and uploaded it, then sent the patch to the maintainer.
[21:06] <rtg> jsalisbury, it likely should be, albeit under a different source package name.
[21:06] <rtg> jsalisbury, oh never mind, linux-tools is a binary generated from the kernel source package.
[21:07] <rtg> in short, yes, I think we can produce a linux-tools binary. I'll work on it friday.
[21:08] <jsalisbury> rtg, thanks!
[21:09]  * rtg -> EOD
[21:16] <hggdh> jsalisbury: just a heads up, bug 1089114
[21:16] <ubot2`> Launchpad bug 1089114 in linux (Ubuntu) " general protection fault: 0000 [#1] SMP on wl_cfg80211_scan+0x43/0x380 [wl] " [Undecided,New] https://launchpad.net/bugs/1089114
[21:18] <jsalisbury> hggdh, Do you have to blacklist those modules if you boot into the prior kernel?  It the prior kernel does'nt have this bug, we can perform a bisect to find the commit that introduced the regression.
[21:22] <hggdh> jsalisbury: I tried booting in the prior, and strangely got hit the same
[21:23] <hggdh> jsalisbury: mind you, I was running 3.7.0-5 until the update this morning
[21:23] <hggdh> with wireless...
[21:24] <jsalisbury> hggdh, hmm, that would make it a little difficult to bisect.  I can post some kernels to test in the bug.  We may need to test some of the 3.7 release candidates.  
[21:25] <jsalisbury> hggdh, there could also be something in userspace, but we can narrow that down by testing some of the earlier kernels.
[21:25] <hggdh> jsalisbury: no prob -- I will reboot on previous kernels, and try
[21:25] <jsalisbury> hggdh, thanks.  I'll post some links to the bug.
[21:26] <hggdh> jsalisbury: ack
[21:28] <hggdh> jsalisbury: the boot on 3.7.0-5 is also shown in the syslog I attached
[21:29] <jsalisbury> hggdh, ok, thanks
[21:58] <hggdh> jsalisbury: while installing the rc7 kernel, I got this: update-initramfs: Generating /boot/initrd.img-3.7.0-030700rc7-generic
[21:58] <hggdh> modprobe: ../tools/modprobe.c:550: print_action: Assertion `kmod_module_get_initstate(m) == KMOD_MODULE_BUILTIN' failed.
[21:58] <hggdh> Aborted (core dumped)
[21:58] <hggdh> samewise for rc6
[22:01] <hggdh> actually, it goes back sometime
[22:22] <jsalisbury> hggdh, hmm, interesting.  That machine may need something provided by an Ubuntu SAUCE patch
[22:37] <hggdh> jsalisbury: yeah. Another laptop does not show this core dumped error
[22:42] <jsalisbury> hggdh, Just as another data point, maybe test the latest Quantal kernel on the machine exhibiting this bug?
[22:43] <hggdh> jsalisbury: right now I am running an update-initramfs -u -k all -v to see where I get the core dumped message. I think it is on all installed kernels
[22:43] <jsalisbury> hggdh, ok
[22:46] <hggdh> jsalisbury: all kernels on this machine, going back to 3.4.19 show the 'core dumped' error
=== emma is now known as em
=== chiluk is now known as chiluk_away