[00:33] <infinity> bjf / herton: Who do I whine at about three kernels falling behind on the SRU cadence?
[00:34] <infinity> bjf / herton: bug #1068733, bug #1068572, and bug #1068229
[00:34] <ubot2> Launchpad bug 1068733 in linux-armadaxp (Ubuntu) "linux-armadaxp: 3.2.0-1610.15 -proposed tracker" [Medium,In progress] https://launchpad.net/bugs/1068733
[00:34] <ubot2> Launchpad bug 1068572 in Kernel SRU Workflow "linux-ti-omap4: 3.2.0-1421.28 -proposed tracker" [Undecided,In progress] https://launchpad.net/bugs/1068572
[00:34] <ubot2> Launchpad bug 1068229 in Kernel SRU Workflow "linux-ti-omap4: 3.0.0-1217.30 -proposed tracker" [Undecided,In progress] https://launchpad.net/bugs/1068229
[00:35] <infinity> bjf / herton: Oh, and bug #1068573
[00:35] <ubot2> Launchpad bug 1068573 in linux-armadaxp (Ubuntu) "linux-armadaxp: 3.5.0-1604.6 -proposed tracker" [Medium,In progress] https://launchpad.net/bugs/1068573
[00:35] <infinity> hggdh: ^-- You have any input on what's holding up the above?
[01:40] <herton> infinity, yes they wait QA, not sure what's holding it though
[09:01]  * apw yawns
[09:10]  * cking offers apw some coffee
[09:16]  * apw tiptoes round his machine after finding it with a read-only root this morning
[09:16] <smb> The coffee machine?
[09:16] <apw> i wish
[09:40] <ppisati> apw: quantal?
[09:40] <apw> quantal indeed
[09:41] <ppisati> apw: happened to me too with quantal on haswell
[09:41] <apw> not haswell, a very old dell ... hmmm
[10:15] <stefano_> hi
[10:16] <stefano_> I have a problem running latest ubuntu kernel version under xen
[10:17] <stefano_> basically there has been a patch cousing a problem with drivers/xen/platform_pci.c
[10:17] <stefano_> commit b9136d207f0c05c96c6b9c980fa7f7fd541a65a8 introduces a bug under xen
[10:18] <stefano_> commit 38ad4f4b6cc713b3c42cb4252688ef5c296d7455 fixes it
[10:19] <stefano_> the kernel 3.5.0-17-generic has b9136d207f0c05c96c6b9c980fa7f7fd541a65a8 but not 38ad4f4b6cc713b3c42cb4252688ef5c296d7455
[10:19] <stefano_> do you know if 38ad4f4b6cc713b3c42cb4252688ef5c296d7455 will be included at some point for 12.10?
[10:19] <smb> stefano_, Seems that other one was not tagged stable, so not automatically
[10:20] <smb> stefano_, Could you open a lp bug and add the info in there and then subscribe me?
[10:20] <stefano_> ok, I never used lp, do I need to register?
[10:22] <smb> stefano_, Yeah, I guess. But ok if you would have to just for that I try to get it done
[10:24] <stefano_> smb: I am on https://launchpad.net/~ubuntu-kernel-team
[10:25] <stefano_> smb: do you know what should I do from there? or should I use some different lonk?
[10:25] <stefano_> link?
[10:25] <smb> stefano_, Oh, so you have an account already
[10:25] <smb> https://bugs.launchpad.net/ubuntu/+filebug
[10:26] <smb> package would be "linux"
[10:28] <stefano_> smb: I am just registering...
[10:30] <smb> stefano_, So I was misunderstanding the "I am on ..."
[10:30] <stefano_> sorry, I confused you :)
[10:30] <stefano_> but now I am :)
[10:33] <smb> stefano_, Not bad to have. Then we also can make you aware of Xen bugs . :)
[10:35] <stefano_> ah, thanks :)
[10:36] <stefano_> how can I subscribe you for the bug?
[10:37] <stefano_> smb: sorry I always forget to put smb: in front of the line..
[10:38] <smb> stefano_, Heh, igf I would not be distracted by a second thread of conversation it would not matter
[10:39] <smb> There should be a subscribe someone else link at the right
[10:39] <smb> I am stefan-bader-canonical
[10:40] <stefano_> I just did :)
[10:40] <stefano_> do you think I should put more infos about the bug?
[10:41] <smb> bug 1081054
[10:41] <ubot2> Launchpad bug 1081054 in linux (Ubuntu) "Kernel panic running latest ubuntu 12.10 kernel version (3.5.0-17-generic) under xen." [Undecided,New] https://launchpad.net/bugs/1081054
[10:41] <stefano_> I did not because we know already the solution
[10:41] <smb> stefano_, I guess it should be ok... just need to 
[10:41] <smb> make sure the botstays happy
[10:42] <stefano_> smb: thanks for all your help :)
[10:42] <smb> stefano_, Oh, thanks for the info about the issue (plus the patch that fixes it)
[10:43] <smb> stefano_, If it would be always that simple... :)
[10:43] <stefano_> smb: do you have an idea of the timeframe when users will download a new ISO and kernel will include both patches?
[10:44] <stefano_> just so I can give a vague indication to our customers
[10:44] <smb> stefano_, I don't think we re-create any isos for non-lts releases. 
[10:44] <stefano_> ah...
[10:44] <smb> The cloudimgs are rebuild if they use them
[10:44] <smb> otherwise it is updates
[10:45] <stefano_> ok, any idea of kernel updates timeframe than ? :)
[10:45] <smb> but timeframe worst case 6 weeks if it misses a cycle completely
[10:45] <stefano_> ah, good than :)
[11:20] <caribou> I'm having a problem with the most recent mainline build. boots up to GUI but trying to login causes a stack trace in 'nouveau' and it flickers back to the login screen
[11:21] <caribou> any other kernel close to mainline that I should test ?
[11:22] <caribou> the mainline I used is 3.7.0-999.201211190405
[11:22] <caribou> (yesterday's build)
[11:27] <caribou> nm, looks like 3.7.0-999-generic #201211080405 does the trick
[11:32]  * ppisati -> out for lunch
[14:18] <smb> jsalisbury, herton, This morning a bug was reported for Quantal that provides the sha1 to the patches breaking and fixing some Xen regression. So it would only require some crank-turning. ;) -> bug 1081064
[14:19]  * smb expectantly looks at ubot2 
[14:19] <herton> smb, wrong bug num? it redirects me to a landscape bug
[14:19] <smb> meh fingers... https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1081054
[14:19] <ubot2> Launchpad bug 1081054 in linux (Ubuntu) "Kernel panic running latest ubuntu 12.10 kernel version (3.5.0-17-generic) under xen." [Medium,Triaged]
[14:21] <herton> smb, will take a look and queue on 3.5 stable. I was busy looking at the ceph updates for it, just going to finish a build test and queue the xen fix also
[14:23] <smb> herton, Sure, I'd leave it to you on how exactly this runs through... Actually now this is an interesting thought... does it need two acks because this could be and upstream stable update which we do take without asking but then we have not been responsible for that before...
[14:24] <herton> smb, yeah I don't know. If you want in parallel to send that as a SRU for two acks that's fine
[14:25] <smb> herton, Oh you know, I tried to avoid *that* decision by telling you ;)
[14:27] <smb> Actually I rather just thought of the strange implications that you running "stable" has.
[14:31] <herton> smb, is 3.5 the only version affected by the bug?
[14:31] <smb> herton, As far as we were told, but give me a sec
[14:34] <smb> herton, First patch came in 3.4 and the fix 3.6, so potentially 3.4 could be affected too... If that is supported by anyone
[14:34] <herton> smb, greg still supports it, so I think is worth sending to stable mailing list as well. 3.4 is one of the chosen longterm trees
[14:35] <smb> Hm, though probably only causes problems for PVonHVM guests as I cannot remember having problems with Quantal in HVM and PVM
[14:36] <jsalisbury> herton, smb, just let me know if you need help building test kernels, etc for that bug
[15:06] <zequence> What kind of problems could one expect to see in using an older kernel for any Ubuntu release (like a 2 year older kernel, compared to the release)
[15:13]  * herton -> lunch
[15:27] <jsalisbury> ##
[15:27] <jsalisbury> ## Kernel team meeting today @ 17:00 UTC
[15:27] <jsalisbury> ##
[15:48]  * ogasawara back in 20
[16:21] <ogasawara> rtg: I was gonna prep an upload before EOD day tomorrow to get -rc6 to the masses before most of us drop off for Thanksgiving/Black Friday.
[16:23] <rtg> ogasawara, I was thinking we should get that uploaded today so as to mitigate any carnage that we might cause. note that apw will be around (I think) for the 2 days we are out.
[16:23] <ogasawara> rtg: ack, I'll prep it for upload by EOD today then
[16:23] <apw> rtg should be around anyhow
[16:23] <apw> ogasawara, will get the union stuff tested shortly
[16:23] <rtg> ogasawara, works for me
[16:24] <ogasawara> apw: ack
[16:24] <rtg> I don't think there is anything else in the pipe. the userns stuff is still  a WIP
[16:24] <ogasawara> rtg: I shoved on patch to linux-meta already for the clean old kernels work, and I want to get one config tweak in too that jsalisbury just pinged me about.
[16:24] <rtg> ogasawara, -rc6 works on my laptop, so it _must_ be shippable
[16:25] <rtg> ogasawara, oh, I might have some firmware patches. guess I'd better wrap that up today as well.
[16:26] <rtg> I was working on that last friday and kinda forgot
[16:26] <rtg> I wrote yet another script to help sort out firmware duplicates and obsoleted files.
[16:27] <ogasawara> rtg: I'm also on the brink of getting this updated i915 driver carried for Haswell in our ubuntu/ dir.  I'm hoping to get that out for testing next week.
[16:27] <smb> ogasawara, Hm, maybe I would have some patch for xen. Though upstream discussion on it is not final but at least my own testing was good
[16:28]  * smb needs to propose the thing soonish
[16:28] <rtg>  ogasawara: but the haswell support is for Quantal, right ?
[16:28] <ogasawara> rtg: right, Quantal
[16:29] <rtg> you were just trying to distract me with you non-sequitur 
[16:29] <ogasawara> rtg: of course :)
[16:29] <apw> vile vile vile
[16:30]  * rtg forgot his headset, so no mumbling....
[16:31] <rtg> apw, I did, however, buy a stack of books about IPv6 at Powells. Did you know that the technical bookstore is now a pile of rubble? I found that a bit confusing the other morning.
[16:32] <apw> rtg, i did know they had moved it to over the road from the other one i think
[16:32] <rtg> apw, yep, right across the street from the main store
[17:00] <jsalisbury> ##
[17:00] <jsalisbury> ## Kernel Team Meeting starting now
[17:00] <jsalisbury> ##
[17:23] <ecanuto> hey all, we have this bug https://bugs.launchpad.net/bugs/1033233 and I would like to know who can help to have this kernel patch in ubuntu-updates (or proposed)
[17:23] <ubot2> Launchpad bug 1033233 in alsa-driver (Ubuntu) "[iMac9,1, Realtek ALC889A, Speaker, Internal] No sound at all with kernel 3.5.0" [Medium,Confirmed]
[17:23] <ecanuto> also, world like to know if the bug need to be tagged when we have a patch that fix issue
[17:26] <herton> ecanuto, I'll take a look at it. Since it's a stable patch I'll queue it on our 3.5 maintained tree, just have to catch up on grabbing stable patches...
[17:29] <herton> ecanuto, the procedure usually when you have the patch upstream, is just send it to kernel-team@lists.ubuntu.com for inclusion
[17:29] <ecanuto> herton, oh, did not know that
[17:30] <ecanuto> herton, next time I will send it to the list
[17:30] <herton> ecanuto, not required to send to the list, but it's faster to people notice it
[17:30] <ecanuto> btw, it is the only thing that I don't like in launchpad, fill a bug not necessary notify the package maintainers
[17:41] <ecanuto> herton, is it going to be available for raring too?
[17:42]  * ppisati -> EOD
[17:43] <herton> ecanuto, yes, I think it is already available on raring, since it went in 3.7
[17:44] <herton> (the patch)
[17:45] <ecanuto> herton, thank you
[18:36] <rtg> jjohansen, jsalisbury, AceLan: I need to bounce tangerine for kernel upgrade
[18:36] <jjohansen> rtg: give me 1 min to copy a file down
[18:37] <jjohansen> rtg: okay
[18:38] <ecanuto> herton, where I can found a tutorial about upload kernel to PPA
[18:38] <ecanuto> I just upload one but fail to build :(
[18:39] <ohsix> you use pbuilder or something to make sure it builds locally, i haven't done it in a long time; i've forgotten the details :o
[18:39] <ohsix> i _think_ you may need to ask for extra space in your PPA as well, kernels take a lot of it
[18:40] <ecanuto> humm
[18:40] <herton> also https://help.launchpad.net/Packaging/PPA/Uploading may be of help
[18:41] <ecanuto> just got this error:
[18:41] <ecanuto> http://paste.ubuntu.com/1373056/
[18:42] <ecanuto> herton, yes, I ready it, other packages works, only linux kernel fails
[18:45] <ecanuto> locally it builds
[18:57] <rtg> everaldo, looks like you've been messing with configs. 'echo 1 > debian.master/abi/3.5.0-18.30/amd64/ignore.modules', then rebuild
[18:58] <everaldo> rtg, humm, where I can put it on sources?
[18:59] <everaldo> I just get a clean kernel sources package and put it on my ppa changing version in changelog
[19:00] <rtg> everaldo, oh, you're changing version. hence "Checking modules for generic...previous or current modules file missing!". you definitely need to read the URL that herton referenced above.
[19:01] <everaldo> let me check
[19:01] <herton> everaldo, also take a look at https://wiki.ubuntu.com/KernelTeam/KernelMaintenance
[19:01]  * rtg reboots for kernel test
[19:02] <everaldo> the first link don't have anything new... let me see this one
[19:03] <everaldo> herton, thanks, this looks to have what I need :-)
[19:07] <rtg> ogasawara, just pushed a horde of firmware patches to raring master-next
[19:07] <ogasawara> ack, I'll pull em then kick off test builds
[19:09] <rtg> ogasawara, I'm still observing periodic random build failures on parallel builds. I've just gotta go find root cause because its starting to piss me off.
[19:09] <ogasawara> rtg: I haven't seen that issue in a while.  I'll let you know if I do.
[19:09] <rtg> ogasawara, its often during the headers packaging phase.
[19:34] <ogasawara> ogasawara@adamo:~/ubuntu-raring-signed$ ./update-version ../ubuntu-raring
[19:34] <ogasawara> dch warning: Recognised distributions are:
[19:34] <ogasawara> {hardy,lucid,maverick,natty,oneiric,precise,quantal}{,-updates,-security,-proposed,-backports} and UNRELEASED.
[19:34] <ogasawara> Using your request anyway.
[19:34] <ogasawara> dch warning: ignoring distribution passed to --release as changelog has already been released
[19:34] <ogasawara> dch: Did you see that warning?  Press RETURN to continue...
[19:34] <ogasawara> Updated to version: 3.7.0-3.9
[19:34] <ogasawara> git commit -s -m 'UBUNTU: Ubuntu-3.7.0-3.9' debian/changelog
[19:34] <ogasawara> git tag -s -m 'Ubuntu-3.7.0-3.9' 'Ubuntu-3.7.0-3.9'
[19:34] <ogasawara> ogasawara@adamo:~/ubuntu-raring-signed$ head -1 debian/changelog 
[19:34] <ogasawara> linux-signed (3.7.0-3.9) precise; urgency=low
[19:34] <ogasawara> rtg, apw: ^^ I assume I manually fix up that linux-signed changelog to s/precise/raring/
[19:36] <rtg> ogasawara, yeah, looks like raring isn't in the approved list yet
[19:38] <rtg> ogasawara, I just used 'dch -i' last time and fixed it up by hand
[20:05]  * rtg -> lunch
[20:08] <apw> ogasawara, cirtainly if it is not raring do fix, as to why ... hmmm
[20:08] <apw> it is meant to copy it up one
[20:09] <apw> ogasawara, and when i ./update-version it does indeed do so
[20:09] <apw> +linux-signed (3.7.0-3.9) raring; urgency=low
[20:10] <apw> ogasawara, so even more confused as to how yours does not
[20:10] <ogasawara> hrm
[20:12] <apw> so i just did ./update-version ../ubuntu-raring to get that
[20:12] <ogasawara> apw: do I need to be running raring?  
[20:12] <apw>       MISS: cpufreq-nforce2
[20:12] <ogasawara> apw: I'd note that the machine I ran my runes on is a precise box
[20:12] <apw> ogasawara, nope i am running quantal
[20:12] <ogasawara> apw: I've fixed that build failure up locally here
[20:12] <apw> so it might be a P/R ...
[20:13] <apw> ogasawara, let me knoe when its pushed so i can test this overlay stuff
[20:13] <apw> (build and test)
[20:13] <ogasawara> apw: ack, just waiting on my final test builds
[20:37] <ogasawara> apw: pushed to master-next what I anticipate to be the 3.7.0-3.9 upload
[20:39] <infinity> hggdh: Around?
[20:39] <hggdh> infinity: yes
[20:40] <infinity> hggdh: Any idea what (or who) the holdup is on the 4 ARM kernels from the last SRU cadence that are stuck in regression-testing?
[20:40] <hggdh> infinity: ugh
[20:40] <infinity> hggdh: That's armadaxp on quantal and precise, and ti-omap4 on precise and oneiric.
[20:40] <infinity> Unless I missed some, and there's more than those 4...
[20:40]  * infinity looks again.
[20:41] <hggdh> infinity: for the pandas, my fault, and will run them now. For the armada, I am finding out how to automate the install
[20:41] <infinity> Nope, just those 4.
[20:41] <infinity> hggdh: For automating armadaxp, I'd talk to rbasak, if I were you.
[20:42] <infinity> hggdh: But maybe today, you could manual 'em up (or get someone else to), so I can get the kernels out the door and move the show on?
[20:42] <hggdh> infinity: indeed, he is the one I am looking for (or mahmoh)
[20:43] <hggdh> infinity: I am on the pandas now; since rbasak is (most probably) out for the day, I am following up with mahmoh
[20:43] <infinity> Kay, cool.  Thanks.
[20:43] <infinity> (Aren't you glad we won't be supporting the nexus7 kernel?)
[20:44]  * infinity knocks on apw's head.
[20:52] <hggdh> infinity: absolutely extactic
[22:44] <ogasawara> BenC: would you like me to CC you on our standard kernel upload announcements so you have a heads up to rebase ppc?
[22:44] <BenC> ogasawara: yes, please
[22:45] <ogasawara> BenC: your @ubuntu.com email? or something else?
[22:45] <BenC> @ubuntu.com is fine
[23:23] <infinity> ogasawara: That whole CC for rebases thing would be wildly more useful if master didn't just FTBFS. ;)
[23:23] <infinity> apw: How does one get an FTBFS when building nothing?  I'm impressed.
[23:24] <apw> infinity, ?
[23:25] <infinity> apw: master FTBFS on PPC during headers install.
[23:25] <infinity> aufs-related.
[23:26] <apw> oh ppc ?
[23:26] <apw> how is ppc even differnt
[23:26] <infinity> Heck if I know.  Maybe aufs headers are being arch-limited or arch-mangled somehow?
[23:27] <apw> infinity, nope, thats a static file
[23:27] <apw> ogasawara, i'll have a look in the morning, there is something subtle going on
[23:28] <infinity> Well, the other possibility is that sulfur briefly lost its mind to cosmic rays.
[23:28] <infinity> But it ain't a Panda, so I doubt it.
[23:28] <apw> infinity, and odder that code has literally not changed since the previous upload
[23:28] <apw> very spooky
[23:28] <infinity> yeah, I'm looking through the diff right now.
[23:28] <infinity> I'll give it back too and see.
[23:28] <apw> thanks, and i'll look at it in the am i have an early start anyhow
[23:36] <apw> infinity, oh dear, it worked that time
[23:37] <apw> infinity, a parallel build failure
[23:38] <apw> perhaps
[23:38] <apw> will do some testing ...
[23:39] <infinity> apw: Oh, that could well be it.  4 cores in the failure, 2 in the success, it's probably highly reproducible if you throw it at -j20 and try a few times (if your guess is right).
[23:42] <apw> infinity, though in theory the headers build is -j1 for this reason ... as its building everywhere i'll poke it in the am
[23:44] <rtg> apw, I've seen this same failure on x86'en. its something to do with binary-arch-headers
[23:44] <apw> rtg, right, in the headers
[23:45] <rtg> apw, I'm beginning to think that '$(hmake) silentoldconfig' needs 'prepare' added as one of the targets. I'll dig into it in the AM if you haven't already solved it by then
[23:45] <apw> rtg, ack
[23:46]  * rtg -> EOD
[23:46] <rtg> apw, go to bed