=== smb` is now known as smb [06:55] * smb yawns [07:36] kees, that is something your scripting is doing. your team does something which changes it to released over and over [07:37] smb, moin [07:37] apw, moin moin [07:39] kees, then generally i change it back on th next autotriage run === jibel__ is now known as jibel === Quintasan_ is now known as Quintasan [09:05] apw: What is the current status with the lucid kernel? [09:06] lucid kernel is built in the PPA [09:07] * smb wonders whether Daviey is personally affected [09:08] Daviey, https://launchpad.net/~canonical-kernel-team/+archive/ppa/+sourcepub/1825665/+listing-archive-extra [09:08] if you fancy doing a last test with the final binaries before they are copied out, it might make skeat happy [09:11] apw: That is all i hope to achieve in life. [09:12] apw: thanks [12:01] hi, I see odd upgrade issues in my kvm based automatic upgrade testing. after the upgrade to 3.0.0-5-generic in oneirc it won't find its root fs anymore. http://people.canonical.com/~mvo/tmp/Screenshot%20at%202011-07-21%2013:58:22.png <- screenshot of the kvm instance. the uuid displayed looks odd, all 00000 for the available paritions. with 2.6.28-8-generic (same image) it books just fine. any ideas where I should dig further? [12:02] blkid /dev/sda1 on the system gives me the right uuid [12:11] mvo, but normally UUID mappings are done in initramfs so we'd not expect the kernel to be doing anything with them would we ? [12:12] mvo, and that error looks like the kernel erroring the mount ... not initramfs dropping to busybox [12:12] have you lost your initramfs for the new kerenl [12:14] apw: thanks! I should have thought about this, let me investigate whats up with the initramfs [12:15] apw: ha! here we go, grub is missing the initrd line, now I just need to figure out why. thanks for your help [12:24] mvo, heh good === kentb-out is now known as kentb [14:01] apw, how is the lucid kernel with patch to fix bug 588861 coming along? [14:01] Launchpad bug 588861 in linux ""pad block corrupted" error when trying to register an image with 2.6.34 kernel" [High,In progress] https://launchpad.net/bugs/588861 [14:05] skaet, its all built, i 'handed' it to cjwatson and you in #ubuntu-release [14:06] * apw wanders out for some air [14:09] apw, coolio. Many thanks. :) [14:17] * smb suggests non-air tight windows to apw [14:24] * ogasawara back in 20 [14:33] brendand_, if you have issues with stable kernels or any kinds of questions about them, it's best to ask them in this public channel === brendand_ is now known as brendand [14:34] we've got a system being tested with the proposed maverick kernel which blanks the display after about 2-3 minutes from booting [14:34] we're sure it's not the screensaver [14:34] but this is after doing a full dist-upgrade [14:34] if we just update to the proposed kernel then it seems to work okay [14:35] would it be worth updating both the kernel and xserver-xorg (and perhaps the graphics drivers where applicable) [14:35] ? [14:36] brendand, yes, i think that makes sense, to get to the interaction that is causing the problem [14:40] apw, have gone ahead and updated kernel tracking bug to indicate it was ready to be published, and have now moved the kernel to -proposed. [14:41] great [14:44] so with dkms packages, should dkms be doing anything to check whether the linux-headers package installed matches the kernel, at least, or, preferably whether both are the defaults? [14:44] ogasawara, anytime your ready, ping me [14:44] bjf: cool, gimme about 10 more min [14:45] ogasawara, no rush, got plenty to do :-) [14:45] hallyn, DKMS typically _requiers_ the headers packages to match the kernel ABI [14:45] requires* [14:45] tgardner: hm, bc every lucid or maverick 'high' or 'critical' open-vm-dkms bug i just saw has them not matching [14:46] hallyn, well, we don't maintain DKMS, so I'm not all that familiar with it anymore [14:46] tgardner: ok, thanks. [14:46] hallyn, alberto milone has a lot of experience with it [14:46] if enough of these keep coming, i guess i'll look into it more [14:51] I've seen several people, mostly with MacBook Airs in Millbank that cannot reboot. I've just come across a MacBook Pro that cannot either: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/814118 [14:51] Ubuntu bug 814118 in linux "MacBookPro7,1 fails to reboot" [Undecided,Confirmed] [14:51] this is all in Natty [14:51] if you guys need any more information on those, do let me know. I sit right by these. [14:58] bjf: k, I'm ready whenever [14:58] bjf, your bot message has a mis-spelling: dianosing. bug #814118 [14:58] Launchpad bug 814118 in linux "MacBookPro7,1 fails to reboot" [Undecided,Confirmed] https://launchpad.net/bugs/814118 [14:58] tgardner, will fix [15:00] ogasawara, will be on my way soon [15:00] bjf: ack [15:00] ev, I maybe missed it but has that ever worked in 10.04 or not? Anyway, you may try to put reboot=? (with ? alternatively being b, t, k, a, e or p) to the kernel cmndline and try rebooting then. [15:01] ev, and of course add any outcome to the bug report [15:01] smb: I don't know about 10.04 - I could add a 10.04 kernel to the system and try rebooting from that, if you think it would prove valuable [15:01] and I'll give the reboot= ones a go in a bit [15:01] just about to jump on a call [15:02] ev, Sorry my fault of not reading 11 [15:02] ev, Whatever I said replace 10.04 with 11.04... [15:03] ah, so give old 11.04 kernels a go? [15:03] any one in particular? [15:03] ev, No I meant debug 11.04 [15:03] ev, Or tell us whether 11.04 used to work [15:03] okay, will do [15:22] cking, I was not really sure we had that covered anywhere else, so I added reboot= to https://wiki.ubuntu.com/BIOSandUbuntu#Reboot_Methods (which I think you started) [15:51] sconklin1, can you check that shank-bot has done the right thing with the lucid update, its in -proposed [15:52] shankbot is broken, I'm investigating [15:52] sconklin1, ooops :) [15:52] I can manually push it, though [16:31] sconklin, bjf, apw - can you join on a call in 10 minutes (info sent by google calendar) to discuss testing appropriate for the lucid kernel in -proposed? [16:39] ogasawara, we just uploaded yes? will you be uploading when 3.0 drops as well ? [16:39] apw: yes and yes [16:39] trying to schedue adding overlayfs [16:39] so i guess it makes most sense to shove it in with 3.0 [16:39] i'll get it applied shortly [16:39] apw: ack [16:40] apw: assuming 3.0 lands before end of next week, I'll likely just do one more upload next fri before Alpha3 [16:41] apw: we can squeeze one more in though if you wanted to get overlayfs in and tested [16:41] apw: the builds go quicker now since we dropped versatile [16:46] ogasawara, i think we are expecting it 'today' as he was g+ing that it would have been out yesterday other than this error [16:46] apw: yep, was just reading the LKML post [16:51] sconklin, apw, my input: yes it should be tested, it should be a full testing pass === sconklin1 is now known as sconklin === _LibertyZero is now known as LibertyZero [17:01] https://wiki.ubuntu.com/LucidLynx/ReleaseNotes/ChangeSummary/10.04.3 [17:04] reassigned bug 801610 to the kernel and marked it Confirmed, but then I remembered in the past that marking kernel bugs Confirmed without doing something else to them caused the kernel team to miss them; is that still true? [17:04] Launchpad bug 801610 in linux "Include enic & fnic drivers in ubuntu-installer" [High,Confirmed] https://launchpad.net/bugs/801610 [17:05] cjwatson, I'll take care of it [17:05] apw - what's this lucid bug the proposed kernel is meant to fix? [17:06] tgardner: thanks [17:52] * ppisati -> gym [17:57] heh, I like proxying through bjf's mumble [17:58] * smb bets that this has a nasty meaning in the uk... :-P [18:00] ogasawara, heh thats soundinf pretty dodgy [18:00] heh, for once I'm speechless [18:10] sconklin, Ok, lbm for lucid got uploaded to the ppa (and I pushed the tree) [18:11] smb: ack [18:13] brendand, the fix in that kernel is for eucalyptus [18:13] brendand, something to do with java not starting [18:16] apw - don't have a # by any chance? [18:16] bug #588861 [18:17] Launchpad bug 588861 in linux ""pad block corrupted" error when trying to register an image with 2.6.34 kernel" [High,In progress] https://launchpad.net/bugs/588861 [18:17] brendand, ^^ [18:47] tgardner, i see 2011-1020 applied to everything but natty/* is that intentional [19:41] * jjohansen lunch [19:54] apw, just took a lunch break. I'll get natty applied shortly [20:25] tgardner, ahh thanks === Quintasan_ is now known as Quintasan === kentb is now known as kentb-out === yofel_ is now known as yofel