[07:04] <ppisati> moin
[07:26] <smb> morning
[07:46]  * apw yawns ... come on engineer
[07:54] <smb> apw, what is the supposed time frame?
[07:58] <apw> smb, he has his head in the cabinet right now, he is supprised to find it already done, cause he hasn't read the damn history
[07:59] <smb> apw, At least him being present is already a surprise. Heck, who reads documentation these days...
[07:59] <apw> if i was going to an angry customer i would not want any supprises
[07:59] <smb> apw, He'd only know you are angry if he'd read the documentation
[08:00] <apw> this is a special install where he has been personally called by bt to tell him the issues, he should knwo
[08:01] <brendand> henrix, any info about the potential regression in the precise kernel? https://bugs.launchpad.net/kernel-sru-workflow/+bug/1167436
[08:01] <ubot2> Launchpad bug 1167436 in Kernel SRU Workflow certification-testing "linux: 3.2.0-41.65 -proposed tracker" [Medium,In progress]
[08:01] <brendand> henrix, anything we can do to help?
[08:08] <henrix> brendand: yesterday sconklin was bisecting the kernel to figure out about that regression
[08:08] <henrix> brendand: i'm not sure if he's done with that
[08:09] <brendand> henrix, but isn't there a bug number?
[08:09] <henrix> brendand: ah, yes sorry. give me 1 min...
[08:10] <henrix> brendand: so, there were a couple of bugs. bug #1167114, bug #1169380 and bug #1168961
[08:10] <ubot2> Launchpad bug 1167114 in linux (Ubuntu) "Ubuntu Kernel 3.5.0-27 does not boot" [High,Confirmed] https://launchpad.net/bugs/1167114
[08:10] <ubot2> Launchpad bug 1169380 in linux (Ubuntu) "Alienware M11x fails to boot with 3.2.40 upgrade" [High,Confirmed] https://launchpad.net/bugs/1169380
[08:10] <ubot2> Launchpad bug 1168961 in linux (Ubuntu) "Linux kernel 3.2.0-40-generic update causes regression, does not boot anymore" [High,Confirmed] https://launchpad.net/bugs/1168961
[08:11] <henrix> brendand: i'm pretty sure sconklin will be very happy if you have a system where you can easily reproduce the issue :)
[08:12] <brendand> henrix, we'll keep an eye out for it
[08:12] <henrix> brendand: great, thanks
[08:14] <brendand> henrix, by the way, i don't see any comment about a potential regression in https://bugs.launchpad.net/kernel-sru-workflow/+bug/1167157, but since the bugs are affecting the quantal kernel we can assume 12.04.2 is likely to be affected, right?
[08:14] <ubot2> Launchpad bug 1167157 in Kernel SRU Workflow certification-testing "linux-lts-quantal: 3.5.0-28.47~precise1 -proposed tracker" [Medium,In progress]
[08:16] <henrix> brendand: yes, i believe you can assume that although i haven't seen any bug report
[08:16] <brendand> henrix, hmm. all the bug reports mention the -updates kernel rather than -proposed
[08:17] <brendand> henrix, did you notice that?
[08:17] <henrix> brendand: yes, the regression has been introduced by a kernel that has been released already
[08:18] <brendand> henrix, that means though that there's no reason to hold this kernel for a bug that already has been released
[08:19] <brendand> henrix, also we did full testing for the last kernel and certainly didn't see any boot regressions so i'm not confident we'll be able to help, but we will try
[08:20] <henrix> brendand: i see what you mean, but since there are a *lot* of people hitting this bug, we would like to have it sorted out asap
[08:20] <brendand> henrix, of course
[08:20] <brendand> henrix, just keep us posted if you are going to respin
[08:21] <henrix> brendand: ok. today i havent check the progress yet, not sure if the root cause has been already identified. will go through those bugs later
[08:21] <henrix> thanks
[09:38] <Kalidarn> very rarely ive found im having a kernel panic
[09:39] <Kalidarn> i decided to take a photograph of it here
[09:39] <Kalidarn> http://imgur.com/a/FVFOv
[09:39] <Kalidarn> would i be right in saying this is before a network interface is brought up? meaning netconsole won't be possible
[09:39] <Kalidarn> yes i have a big monitor, that's everything that was on it
[09:40] <Kalidarn> ive had it panic twice since i installed raring ringtail, unfortunately the error spat out on the screen isn't all that meaningful
[09:40] <Kalidarn> all i can tell is that it failed on some GPL module
[09:41] <Kalidarn> by the way it says: Pid: 1250: Tainted GF
[09:41] <Kalidarn> the system doesn't have any serial ports unfortunately either
[09:41] <Kalidarn> never had a kernel panic in 12.10, but ive had two, when booting raring ringtail (been using it for 3 or so days)
[09:43] <Kalidarn> and yes i'm a kernel debug noob, i have looked at https://wiki.ubuntu.com/Kernel/KernelDebuggingTricks and https://wiki.ubuntu.com/Kernel/KernelDebuggingTricks#Network_Console however
[09:43] <Kalidarn> as someone in #kernelnewbies suggested i try netconsole
[10:04] <ppisati> brb
[10:37] <vstehle> Hi! While trying kernel from http://kernel.ubuntu.com/~kernel-ppa/mainline/daily/current/ I noticed DM_CACHE is not enabled in the config. Could some wizard here enable it for future builds, please?
[10:38] <vstehle> (This is a shiny, sexy, brand new feature of kernel 3.9, which allows to use your SSD as a HDD cache, btw.)
[10:40]  * ppisati -> out for lunch
[11:53] <infinity> psivaa: Is anyone doing regression testing on linux-ec2/lucid?
[11:55] <psivaa> infinity: plars said he will take it, he was busy trying to reproduce a bug yesterday for raring release 
[11:55] <infinity> psivaa: Check, raring release stuff is definitely higher priority, was just curious since the task has been idle for six days.
[11:56] <psivaa> infinity: ack, will ask him in any case. 
[12:20]  * henrix -> lunch
[12:51] <psino> which kernel version is in ubuntu raring? 3.8.0 or does it follow the 3.8.y git tree? more speficially, is it based on this release mentioned here: http://lwn.net/Articles/547533/? :)
[12:55] <smb> psino, type "head Makefile" in the top level directory :)
[12:59] <infinity> psino: Current raring kernel is 3.8.8-based, yes.
[13:01] <rtg> psino, bjf just hacked in some wiki info about how Ubuntu kernels are versioned.
[13:01] <bjf> rtg, link?
[13:02] <apw> rtg, isn't there a FAQ entry on that in the wiki already?
[13:02] <rtg> bjf, I was depending on you to remember the link :)
[13:03] <bjf> rtg, yes, but does psino know it?
[13:03] <psino> nope, psino doesn't know it, and doesn't seem to be able to find it
[13:03] <bjf> LOL
[13:03] <bjf> https://wiki.ubuntu.com/Kernel/FAQ#Kernel.2BAC8-FAQ.2BAC8-GeneralVersionMeaning.What_does_a_specific_Ubuntu_kernel_version_number_mean.3F
[13:03] <smb> rtg, bjf Maybe it would be worth to add the link to factoids
[13:04] <bjf> psino, ^
[13:04] <psino> hmm.
[13:04] <bjf> psino, also the FAQ right before that one on the same page
[13:05] <psino> I saw those entries, but I'm not sure how I can determine that http://packages.ubuntu.com/raring/kernel/linux-image-3.8.0-19-generic is actually 3.8.8
[13:06] <bjf> psino, it's not 3.8.8. we may have not applied all the patches. this can be the case is we've already picked up some patches earlier or if we found regressions and removed them
[13:06] <rtg> psino, thats 'cause its _not_ 3.8.8
[13:07] <smb> psino, Basically the Makefile contains that info in sublevel
[13:07] <bjf> psino, the only way to see what we've done is to look at the git repo
[13:07] <psino> I was really happy to see that the 3.8.8 announcement included patches for some issues I've been slightly bugging smb about
[13:07] <psino> smb: SUBLEVEL = 0 ?
[13:08] <bjf> psino, we _try_ to apply all the stable updates for any given upstream stable release but there is no guarantee
[13:09] <smb> psino, Not for me http://kernel.ubuntu.com/git?p=ubuntu/ubuntu-raring.git;a=blob;f=Makefile;h=290499c32aaa0d9b914ea0216df74ad82fcb9a83;hb=HEAD
[13:11] <psino> smb: I see, I'm probably looking at the wrong places as I don't have a checkout or anything on this machine
[13:12] <psino> bjf: ok, in this case, by looking at the ubuntu-raring.git repo, the patches I'm interested in have been applied
[13:12] <bjf> psino, cool, that really is the only way to kno for sure
[13:12] <smb> psino, Ah ok. Yes that link is into the current tree
[13:13] <psino> in any case, around a week ago I built my own kernel based on the ubuntu sources with the patches applied to see if it was stable / fixed the issue, which it did
[13:14] <psino> smb: looking at http://kernel.ubuntu.com/git?p=ubuntu/ubuntu-raring.git;a=summary, the indicates that the commits I needed are in 19.29
[13:14] <smb> So at least things should be fixed if you would base on 3.8.0-19.29. Indeed
[13:15] <psino> so now I'm just happy to wait for 13.04 to get a final release so I can move this out into production :)
[13:16] <smb> That kernel is available if you dist-upgrade even now (if you have a raring installation already)
[13:18] <plars> infinity, psivaa: yeah, it's going to happen today. ec2 is a bit of a pain right now, and I'm waiting on a few bits from IS, then I can hopefully streamline some of that
[13:19] <psivaa> plars: ack, thank you
[13:19] <smb> plars, How can EC2 *ever* be a pain? ;-P
[13:20] <plars> smb: well, in theory it *shouldn't* be
[13:20] <psino> smb, bjf, rtg: thanks for your help :)
[13:22] <smb> plars, I know, I know. In theory the world is round. :) Any special issues with the kernel or more "environmental"?
[13:22] <smb> psino, you are welcome
[13:23] <plars> smb: no, well, kinda
[13:23] <plars> smb: the kernel regression tests hardcode /dev/sdb2 to use for the scratch drive, I've talked to bjf about that already.  Unfortunately it looks like a lot of places it's hardcoded
[13:24] <plars> smb: on ec2, if you map ebs or ephemeral disk to sdb, parted errors out on it, apparently a known limitation in the kernel driver - not sure of the details off the top of my head
[13:24] <smb> plars, Ah yeah, that could be an issue for kvm too (if you use pv disks)
[13:25] <plars> smb: you can map it to /dev/xvda and it all works fine, but then the kernel regression tests don't work - workaround was to just use a stupid symlink for now
[13:25] <plars> smb: good to know
[13:26] <plars> smb: unfortunately, the version of ec2-api-tools I have doesn't seem to like mapping ephemeral disks to /dev/xvd*, I talked to utlemming about it and he said the new version of tools *should* fix that, but I don't see it in the ppa still
[13:26] <plars> smb: so it's a bunch of workarounds at the moment
[13:27] <smb> plars, Yeah it is all a bit messy. Maybe if xen never had called the paravirtualized disks sd*. Though it could have been that back then everything else would have failed
[13:29] <smb> Hm, could be the for Lucid ec2 there may or may not be that patch that names things to sd* still. I slowly loose a bit of track...
[13:46] <ppisati> uhm
[13:46] <ppisati> i just updated my laptop
[13:46] <ppisati> and now it keeps asking my ssh passphrase
[15:05] <jsalisbury> **
[15:05] <jsalisbury> ** Ubuntu Kernel Team Meeting - Today @ 17:00 UTC - #ubuntu-meeting
[15:05] <jsalisbury> **
[15:50] <apw> ppisati, sounds like a lovely new feature
[15:51] <ogra_> and safe !
[16:48] <apw> arges, http://s19n.net/articles/2011/kvm_clock.html
[16:49] <arges> apw: yup i've seen that one 
[16:49] <arges> : )
[16:53] <arges> apw: https://help.ubuntu.com/12.04/serverguide/
[16:59] <jsalisbury> ##
[16:59] <jsalisbury> ## Meeting starting in one minute
[16:59] <jsalisbury> ##
[17:14] <apw> shadeslayer, you don't need to wait for meetings to discuss things like patches, do come and bring them up here 
[17:15] <shadeslayer> well, that was kind of spur of the moment
[17:15] <shadeslayer> I merely intended to listen in today ;)
[17:25] <shadeslayer> apw: bug 1171940
[17:25] <ubot2> Launchpad bug 1171940 in linux (Ubuntu) "vgaswitcheroo on the Macbook Pro 8,2" [Undecided,New] https://launchpad.net/bugs/1171940
[18:00] <smb> arges, Maybe that reading helps as well Documentation/virtual/kvm/msr.txt
[18:00] <arges> smb: ok i'll read that too
[18:06]  * ppisati walks away
[19:40] <arges> smb: apw: not sure if you're both still around: https://lists.ubuntu.com/archives/kernel-team/2013-April/027875.html
[19:42] <arges> chiluk: actually got to do some kvm research! 
[19:42] <arges> was pretty fun
[19:43] <chiluk> yeah I was listening earlier.
[23:45] <bryce> sforshee, btw bug #1041790 has been hitting quite a few people, and now has a patch upstream which should ameliorate things and may be worth your consideration for sru's.  Jason Warner was hitting it (and now is disabling semaphores as a workaround).
[23:45] <ubot2> Launchpad bug 1041790 in xserver-xorg-video-intel (Ubuntu) "[snb] GPU lockup IPEHR: 0x0b160001 IPEHR: 0x0b140001, workaround i915.semaphores=0" [High,Triaged] https://launchpad.net/bugs/1041790
[23:52] <bjf> bryce, the patch we reverted, will it help with that?
[23:54] <bjf> bryce, we've been working on bug 1140716
[23:54] <ubot2> Launchpad bug 1140716 in linux-lts-quantal (Ubuntu Precise) "[regression] 3.5.0-26-generic and 3.2.0-39-generic GPU hangs on Sandybridge" [Critical,Confirmed] https://launchpad.net/bugs/1140716
[23:55] <bjf> bryce, we have a test kernel but jason said he was too busy to test
[23:57] <bryce> bjf, "maybe".  we never got to a verification that 1041790 and 1140716 are the same.  But didn't rule it out either.
[23:57] <bjf> bryce, testing a kernel could help :-)
[23:59] <bjf> bryce, but i can understand that preparing slide decks is more important than bugs affecting a number of users ;-)
[23:59] <bryce> bjf, Jason is waiting for the rest of his computer HW to arrive (by ship!) but said once he has more than one PC he can help with testing