[00:00] Oh. Or maybe the current trunk depends on something from a newer ubuntu-dev-tools. [00:00] Developers running precise. Crazy talk. [00:00] stable kernel folks are allowed [00:00] we actually support lts [00:01] I run both, to be fair. [00:01] Just that my laptop is raring. [00:01] i can try raring if that makes a diff (i also run multiple) [00:01] And all my other machines are precise. [00:01] same here [00:01] Well, it works here on raring. [00:01] YMMV. [00:01] can't hurt to try ... [00:01] Anyhow, if it doesn't work for some reason, I'll just copy it to a security PPA and be done with it. [00:02] Since I do have access to those. [00:03] nope, same error [00:03] It could just be that you don't have ubuntu-dev-tools installed...? [00:03] At least, I assume that's where that import is from. [00:03] trying [00:04] infinity, that seems to have made a diff [00:05] infinity, it thinks it did it [00:05] Well, we'll know in a minute or two. [00:05] copies are async. [00:05] Yeahp, looks good. [00:05] i see a second one in the ppa [00:06] * infinity scores those up. [00:06] You should be able to delete the oopsed quantal one. [00:06] infinity, the signed one is probably in the same situation [00:06] The signed one was uploaded to the archive, not the PPA. [00:06] so we just leave it [00:06] ? [00:06] I've got that covered, yeah. [00:07] ok, i'm backing away, let me know if i need to do anything else [00:07] ;) [00:07] Other than prodding people for rebases, I think we're good now. [00:08] Is this already fixed in raring? [00:10] it had not hit linus' tree the last i looked [00:10] i mentioned it to rtg, i'm not sure what his plan is/was [00:11] let me look at our tree [00:12] infinity, it's on our master-next [00:56] bjf: Say, not to nitpick, since this has been wrong for a few releases now, but why do the linux-signed changelogs say "precise"? :) [00:56] bjf: No point fixing it for this upload, but someone might want to get it right on the next. [00:57] https://launchpad.net/ubuntu/+source/linux-signed/3.5.0-24.37 [00:57] https://launchpad.net/ubuntu/+source/linux-signed/3.5.0-25.38 [00:57] Etc. [00:57] Oops. :) [00:57] infinity, looking [00:57] bjf: I assume someone just made it precise somewhere in the distant past, and automated tooling has kept it broken. :) [00:58] bjf: And since you upload to the PPA in a targetted fashion, and I copy to the archive in a similarly targetted way, it's never actually mattered. [00:59] bjf: Anyhow. No big deal for this round, just entertaining. [00:59] infinity, yup, looks like i may have been the one to "break" it in jan. [00:59] Heh. [00:59] Then you can fix it in a week or two. :) [00:59] infinity, tomorrow most likely since this is the start of a cycle [01:01] bjf: Also curious that linux-signed-image doesn't depend on sbsigntool in quantal, but it does in precise and raring... [01:02] infinity, your just all kinds of fun today [01:03] Yeah, I'm great at parties. [01:09] bjf: Again, not world-ending, since that was already wrong in the previous uploads, but if you could fit it in git so it matches precise/raring on the next round, that'd be cool. [01:09] infinity, i've noted it and will correct tomorrow [01:09] bjf: (Not sure how else the packaging differs between linux-signed/quantal and linux-signed-lts-quantal/precise, but it seems on that they should differ at all, except for the linux-extra dep. [01:09] ) [01:09] s/on/odd/ [01:09] Typing hard. [01:10] bjf: Anyhow, this all looks like it's going to build and be happy, so feel free to run away, I'll sort the promotions myself in a bit when it's all done and do bot/bug faffing. === BruceMa is now known as BruceMa_afk === BruceMa_afk is now known as BruceMa === amitk is now known as amitk-afk [08:09] moin [08:18] henrix_, can you help re-orient me in the kernel cadence? [08:18] henrix_, i'm starting to get lost === smb` is now known as smb [08:39] morning [08:54] brendand: The current cadence is a bit out of whack due to emergency security releases. We should be back in the normal flow of things in a day or three. [08:55] ppisati: https://bugs.launchpad.net/ubuntu/+source/linux-ti-omap4/+bug/1132939 could use some urgent attention while I sleep, so I can deal with it in the morning. :) [08:55] Launchpad bug 1132939 in kernel-sru-workflow "linux-ti-omap4: -proposed tracker" [Medium,In progress] [08:55] infinity, an estimated date for the next kernels to finish verification? [08:56] brendand: Well, the current set are skipping the whole process, due to the aforementioned security urgency. [08:56] infinity: saw it, doing the rebase right now [08:56] brendand: So, after that, you'd have to ask bjf about the next cycle. [08:59] bjf, linux-signed in Q differs from P or R in that it contains the full binaries, and so doesn't need those other deps as it works different. we may want to change that, but it is "right" at least [09:02] bjf: Translation, I'll probably work with Andy to make sure it gets changed to match P and R, for sanity and consistency but, yes, it's "correct" right now, as explained. False alarm earlier. === henrix_ is now known as henrix === amitk-afk is now known as amitk [09:27] apw: i understood that linux-3.5.y.z-queue was being built automatically from git but the latest build seems to be from Feb 16 [09:28] apw: do i need to kick it off? [09:28] henrix, they are automatic, but i thought there was two parts, the parts i was doing which are based on tags appearing [09:28] henrix, and another part which herton did which was maybe a daily [09:29] apw: hmm... ok. so i pushed some commits to -queue yesterday. do you have any idea how do i start a build in there? [09:31] apw: anyway, i'll ping herton later about this. i have .debs i've created manually yesterday so i'll just use those for now [09:40] henrix, ack === amitk_ is now known as amitk [10:53] henrix, erm, there are builds in the mainline builds since the 16th ? [10:53] henrix, in the -review ? [10:54] apw: oh, i checked the -queue branch only [10:54] * henrix goes look [10:54] it is optimising only one build i think [10:54] if they are the same [10:55] ah, ok. makes sense [10:55] * apw needs to check it is doing it a sane way round [10:58] henrix, yeah so if -review has built and matches -queue then we don't bother building that one too [10:58] as they would be identicle [10:58] apw: yep, got it. thanks [10:59] i wonder if we should be linking it into there ... maybe we should [10:59] you mean the 'current', right? it could make sense, yeah [11:00] but since very few people will actually look at those, not sure if its worth the trouble [11:00] i was more thinking the dates actually [11:40] * apw watches raring crater ... great [12:49] * rtg_ fixes quantal master-next build [13:02] * henrix -> lunch [13:22] * rtg_ preps raring kernel for upload, includes CVE-2013-1763 [13:26] uploaded... [14:45] Hi my friend has fujitsu siemens amilo laptop and this is graphical card detail: http://paste.ubuntu.com/5567659/ . The issue is resume back from suspend. It goes to suspend, but when wake up it goes black screen. He really likes 12.04.2. [14:52] I think it is kernel related because there was no fglrx driver in jockey-gtk [14:56] * cafetiere whines about i915 page flip hangs in v38 final [14:57] * cafetiere also wonders how he is the first to hit them [14:57] cafetiere, was your message to me? desperate to help my friend I made him switch from windows.. I do not want to look bad [14:57] cafetiere, isn't there a SAUCE patch just forthat ? [14:57] I think that was p [14:58] cafetiere, UBUNTU: SAUCE: drm/i915: Wait for pending flips to complete before tearing down the encoders [14:58] https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1082314 <<<-- I found this but I do not understand anything about it :(. [14:58] Launchpad bug 1082314 in mesa "Raring wake up from S3 broken" [Medium,Fix released] [14:58] Kurdistan: nope whining about my own woes [14:59] cafetiere, oki sorry... :( [14:59] rtg_: that is the one but this is during normal boot running === kentb-out is now known as kentb [15:01] I have Somme pointer from the x people to try, but not being able to use ones own devel box is a pain [15:11] Kurdistan, The best way to help your friend is to open a seperate bug report. Just run "ubuntu-bug" on the affected machine. That runs you through some questions and opens a launchpad bug. [15:22] brb [15:44] * ogasawara back in 20 [15:47] smb, he do not have launchpad account. [15:47] but I will ask him if I do not find out ha way and his laptop have really high temp. I am afriad of overheating. [15:51] ** [15:51] ** Ubuntu Kernel Team Meeting - Today @ 17:00 UTC - #ubuntu-meeting [15:51] ** [16:27] brendand, all you all sorted on what's happening wrt kernel SRU cadence now? [16:30] ppisati: What's happening with ti-omap4/quantal? Just waiting on one of your coworkers to upload to the PPA? [16:31] bjf: henrix: herton ^^^ [16:31] bug 1132939 [16:31] Launchpad bug 1132939 in Kernel SRU Workflow "linux-ti-omap4: 3.5.0-220.29 -proposed tracker" [Medium,In progress] https://launchpad.net/bugs/1132939 [16:33] infinity: ppisati: ok, i guess we forgot about those branches. thanks [16:34] bjf, a clear idea of when the next testing week will be would be handy right now [16:36] brendand: I'm not entirely clear on when your testing week is, but the next uploads should start today/tomorrow. [16:36] brendand: So, testing is the week or two following, I assume. [16:37] infinity, right === mdeslaur is now known as random_nickname === random_nickname is now known as mdeslaur [16:38] bjf: So... Setting verification testing to invalid REALLY pissed off the bot. Let's not do that again. :P [16:38] infinity, lol [16:39] infinity: last week i just set those to 'fix released'. and then, manually, set the 'promote-to-*' to 'confirmed' [16:41] henrix: Yeah, I opted to set verification to fix released after I promoted, so everything stayed automated. [16:41] henrix: But we'd earlier set verification to invalid and the bot commented on the bug every few hours, saying "SOMETHING'S WRONG, AND I REFUSE TO DO ANYTHING ABOUT THIS BUG, BUT I'LL STILL ADD COMMENTS, NYAH NYAH". [16:42] I think it's just being a brat for attention. [16:42] infinity: heh, probably :) [16:49] brendand, this is a prep week, next week is verification, the following week is regression testing [16:50] bjf, ok thanks [16:53] brendand, there was a small error on the interlock schedule which i've just corrected: https://wiki.ubuntu.com/RaringRingtail/ReleaseInterlock [17:00] ## [17:00] ## Meeting starting now [17:00] ## === jsalisbury changed the topic of #ubuntu-kernel to: Home: https://wiki.ubuntu.com/Kernel/ || Ubuntu Kernel Team Meeting - Tues March 5th, 2013 - 17:00 UTC || If you have a question just ask, and do wait around for an answer! === henrix is now known as henrix_ === henrix_ is now known as henrix === henrix is now known as henrix_ === henrix_ is now known as henrix [17:38] * ppisati -> EOD === timblechmann is now known as tim [18:40] * rtg_ -> lunch [20:18] Woa, another Quantal -lowlatency update. What's going on? [20:18] zequence, yesterday was for a high priority CVE [20:18] zequence, today, it's the start of the regular 3 week cycle [20:19] bjf: Ok [20:19] zequence, c'mon, you didn't have anything else to do did you? :-) [20:20] bjf: Actually, I'm taking the chance while I'm being sick to get some mixing done :) [20:21] ..not that updating the kernel takes me a long time [20:21] I just run a script pretty much [20:21] And try not mess up the changelog :P === henrix is now known as henrix_ [20:28] bjf: Not to harp, but should I be concerned that you're starting the new Q SRU cycle and no one's uploaded the ti-omap4/Q rebase for yesterday's CVE fiasco? :P [20:29] * rtg_ -> EOD [20:29] infinity, i guess i'll have to deal with that myself [20:31] bjf: I think that was the implication made earlier, yeah. [21:19] apw: I've had to revert a few of your config changes on ppc [21:19] apw: namely, all of the built-in self tests for FMAN/BMAN/QMAN were enabled, and really shouldn't be on unless doing extensive (performance hindering) debugging [21:21] Also, had to disable CRASH_DUMP because it really mucks up ppc in general (especially kexec kernel loading) [21:21] CRASH_DUMP makes it so it will be only relocatable to page aligned memory, where as normally we can relocate to arbitrary memory [21:22] And kexec doesn't have a way to detect that and mask/offset the memory when loading the kernel [21:36] BenC: Those are probably valid points for kexec in general which, while we don't officially support on other arches, we probably don't want to hinder. [21:36] apw: ^ [21:56] infinity: I'm all for re-enabling it on non-freescale kernels, but as I can't test them with it enabled (and it appears it never was before), I'm hesitant of doing so [22:10] BenC: I was sort of arguing that your reverts might be valid across the board, not that you should revert the reverts anywhere. :) [22:10] infinity: right, I was just saying that I know it keeps our equipment from even booting the kernels, just noting I don't mind if it's enabled in places where that isn't an issue :) [22:11] BenC: Booting is overrated. What you have there is the fix for every CVE, past, present, and future. [22:12] Optimism runs strong in you [22:12] Yeah, I get accused of that a lot. Must be my sunny disposition and friendly personality. [22:25] BenC: Does this mean there's a linux-ppc upload coming soon? [22:25] infinity: Yeah, recompiling now to make sure this all works [22:25] BenC: If so, give me a bit of warning, and I can make sure it lands on sagari. [22:26] Ok, thanks [22:27] * infinity should probably test your kernels on his PPC750 occasionally to make sure you haven't broken powerpc32. [22:27] I run raring's powerpc64 kernels on another machine, and they're not obviously broken, but my PPC750 is precise. I suppose installing and boot-testing the odd kernel wouldn't hurt. [22:28] people still use powerpc32? :) [22:28] we were discussing this at scale recently ;p [22:28] antarus: A fair few people do, AFAIK, though I'm just an "old hardware" case. [22:29] antarus: It's an ultra-low-power IBM PPC750 core, so despite being ancient, I don't really feel bad about running it, like I do with, say, old Pentiums. [22:56] infinity, i've uploaded a ti-omap4. i'm prepared for you to tell me all the ways i've screwed it up. === kentb is now known as kentb-out [23:08] bjf: Looks fine to me. [23:08] bjf: Sorry to disappoint. [23:09] bjf: I'll get it copied and released as soon as it's built tonight to clear the way for the normal SRU that should follow. [23:10] infinity, still plenty of time to find fault, don't rush. [23:10] bjf: Well, the one thing you did wrong was to mangle the bug so the bot started lying about builds being completed. :P [23:10] bjf: But the source itself looks fine.