[05:20] <ppisati> moin
[05:34] <bjf> night :-)
[06:00] <ppisati> bjf: sleep well :)
[06:32] <ppisati> robher: just for ECX1000? is it ok on ECX2000? i mean cpuidle
[06:33] <ppisati> robher: that's what the patch says, but i wanted to check
[07:01] <smb> morning
[07:41] <ppisati> smb: moin moin :)
[07:48]  * apw yawns ... moin ppisati
[07:48] <apw> smb, morning
[07:49] <smb> apw, ppisati, morning
[08:09] <smb> apw, I hope that is just fluke and coincidence but after dist-upgrading my haswell on saucy this morning it locks up somewhere on boot...
[08:09] <smb> not really locked up but not completing it
[11:17] <apw> ppisati, this IDLE config change, am i expecting that to only apply to generic and not generic-lpae
[11:18] <apw> ppisati, /me replies in email
[11:22] <apw> henrix, are we good matrix wise, found anything else dodgy ??
[11:22] <henrix> apw: nop, i believe we're good
[11:23] <henrix> apw: i reviewed the matrix yesterday and found nothing 
[11:23] <apw> henrix, sweet, happy again
[11:23] <henrix> :)
[11:24] <apw> henrix, have we missed CVE-2013-2237
[11:25] <apw> in 3.8 stable or something?  it seems 3.5 got the fix
[11:25] <apw> (we do both 3.5 and 3.8 stable right ?
[11:25] <apw> )
[11:25] <henrix> apw: i believe the fix is in 3.8 queue, but let me check...
[11:26] <apw> ahh we don't release them on the same schedule then ?
[11:26] <henrix> apw: yeah, 3.8 is currently under review and it contains the fix
[11:27] <henrix> apw: no, we actually have different schedules. this is mainly due to the fact that 3.5 is much older so it gets fewer patches
[11:28] <henrix> apw: so, they end up being released with a different cadence
[11:37] <apw> henrix, heh, i think i am supprised it is ahead :)
[11:38] <henrix> apw: :) just coincidence, i believe. i don't think that's always the case
[11:39] <henrix> anyway, i don't have strong arguments about having different cadences for different stable kernels. i just think its natural, but happy to do otherwise
[11:56] <apw> henrix, oh no it is your baby as it is ... how you think it should work is how ...
[11:57] <apw> henrix, i noticed it only as it seemed inconsistant in the matrix, and you have assured me it is covered, so i am good
[11:57] <henrix> apw: ack :)
[13:08] <robher> ppisati: yes, the cpuidle fix is only needed for highbank. The driver will not initialize on midway.
[13:12] <rtg> ppisati, kamal, sconklin, jjohansen, bjf: rebooting tangerine for kernel update
[13:13] <ppisati> rtg: ack
[13:13] <jjohansen> rtg: can you give me 2 mins
[13:13] <rtg> jjohansen, shit, already pulled the trigger
[13:13] <rtg> sorry, I didn't think anything was going on
[13:14] <jjohansen> heh its okay, I was just in the middle of a kernel copy, I can start it over when it comes back up
[13:14] <rtg> jjohansen, besides, what are you doing up so early anyways ?
[13:14] <jjohansen> rtg: oh, its more like up late debugging
[13:15]  * henrix -> late lunch
[13:36] <rtg> apw, whats up with the tools naming scheme changes ? I need to update the goldfish meta package.
[13:38] <apw> rtg, bah got distracted ... will sort them right now, so you can see what the pattern is
[13:47] <rtg> grumble, server issues. back in a few....
[13:47] <rtg> ppisati, kamal, sconklin, jjohansen, bjf: P.S. - tangerine is back if you hadn't already noticed
[13:48] <sconklin> ack
[13:50] <ppisati> rtg: cool
[14:07] <rtg> jsalisbury, cking, henrix: rebooting gomeisa for kernel update
[14:07] <jsalisbury> rtg, ack
[14:07] <henrix> rtg: ack
[14:08] <cking> rtg: ack
[14:13] <apw> bjf, i think we decided that shanky will be happy with random packages in the ckt ppa as long as there are not release-tracking-bugs for them
[14:29] <infinity> apw: We've had random packages in the PPA before (and there's at least one in there now), so I'd hope so.
[15:27] <bjf> apw, shanky only cares about bugs and doesn't care about the ppa (mostly) just to match packages with versions in bugs
[15:41] <apw> bjf, perfect as i have dumped some ~preN packages in there :)
[15:41] <bjf> apw, should be all good
[15:50] <apw> rtg, are all your changes for goldfish in the archive, i want to spin these changes against a clean tip
[15:50] <rtg> apw, the meta, or the kernel ?
[15:51] <rtg> apw, I'm working on i386 for goldfish, but I'll just merge after you push your tools package renaming
[15:52] <apw> ok ack
[16:12] <u-k-i-t> jsalisbury: bug 1212977. Tested today's ISO images and no change. The error remains even with the fix for bug 1223195.
[16:12] <ubot2`> Launchpad bug 1212977 in linux (Ubuntu Saucy) "saucy daily-live images are unbootable on Dell Optiplex 990; stuck in BusyBox shell" [High,Confirmed] https://launchpad.net/bugs/1212977
[16:12] <ubot2`> Launchpad bug 1223195 in linux (Ubuntu Saucy) "efivarfs built as a module in saucy, so not mounted at boot" [High,Fix released] https://launchpad.net/bugs/1223195
[16:14] <jsalisbury> u-k-i-t, can you run uname -a and confirm you are running the 3.11.0-7.13 kernel
[16:15] <u-k-i-t> jsalisbury: Will do. The kernel on the iso manifest says it is that version, but will double check.
[16:20] <u-k-i-t> jsalisbury: Yes a uname -a at the initramfs prompt failure point. Shows it running 3.11.0-7 #13.
[16:21] <jsalisbury> u-k-i-t, thanks for checking.  We'll have to investigate further.
[16:21] <u-k-i-t> jsalisbury: Ok
[16:29] <LinuxGol_>  /me is running HP Pavilion Slimline 3100n desktop PC running Ubuntu 13.04 server and kernel 3.8.0-30-generic.  seeing i2c i2c-3 sendbytes NAK bailout error every few seconds
[16:53] <apw> LinuxGold, siy
[16:53] <apw> LinuxGold, sounds like you should file a bug, and (if you know) add what kernel did not do this
[16:53] <LinuxGold> siiy?
[16:53] <apw> .
[16:54] <apw> LinuxGold, keyboard/finger failure
[16:54] <LinuxGold> looked in google, seems to be a bug reported on nouveau -- not sure if that was the specific bug?
[16:54] <apw> so you use nouveau, do you have an nvidia card
[16:54] <LinuxGold> sent email to kernel-team email
[16:54] <LinuxGold> yes
[16:55] <apw> i think as we said in response to that, file a bug and let us know the number
[16:55] <LinuxGold> shamm@minecraftsrv:~$ lsmod | grep i2c
[16:55] <LinuxGold> i2c_algo_bit           13413  1 nouveau
[16:55] <LinuxGold> i2c_nforce2            13020  0 
[16:55] <apw> that will get us all sorts of h/w info
[16:56] <apw> and let us track it
[16:56] <LinuxGold> k
[16:56] <LinuxGold> looking for url to report bug to
[16:56] <apw> 'ubuntu-bug linux' would be the command
[16:56] <LinuxGold> aha
[16:56] <LinuxGold> executing
[17:04] <LinuxGold> #1015165 -- incomplete
[17:04] <LinuxGold> ah
[17:04] <LinuxGold> i2c-4 not i2c-2
[17:05] <LinuxGold> having problem with bug website
[17:05] <LinuxGold> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1224004
[17:05] <ubot2`> Launchpad bug 1224004 in linux (Ubuntu) "i2c i2c-3: sendbytes: NAK bailout." [Undecided,New]
[17:06] <LinuxGold> thanks apw
[17:18] <rtg> apw, I'm ready to wrap goldfish and upload
[17:18] <apw> rtg, go ahead without me, i need to do more testing
[17:18] <apw> i'll rebase on you
[17:18] <rtg> apw, will do
[17:20] <LinuxGold> is there any way to disable the annoying NAK messages?
[17:52]  * rtg messed up the goldfish upload. doh!
[17:56] <ogra_> rtg, not that anyone makes use of it yet 
[17:56] <rtg> ogra_, well, it would be easier for someone to use if I actually got the build working.
[17:56] <ogra_> heh
[18:16]  * rtg -> lunch
[19:38] <TsarObomba> im connected to a buildbox that also acts as a desktop on the remote end
[19:39] <TsarObomba> im wondering if its possible to rebuild the nvidia mpodule for the box before I reboot
[19:39] <TsarObomba> (using a non-stock kernel here)