/srv/irclogs.ubuntu.com/2012/10/04/#ubuntu-kernel.txt

infinityogasawara / apw: kernel iz broke on armhf.01:22
infinityhttps://launchpad.net/ubuntu/+source/linux/3.5.0-17.26/+build/387691601:22
=== henrix_ is now known as henrix
=== henrix is now known as henrix_
=== henrix_ is now known as henrix
* apw is looking into the -17 quantal armhf build failure11:18
* henrix -> lunch12:15
=== doko__ is now known as doko
jussiapw: ping? 12:31
apwoing12:32
ogasawaraapw: I seemed to have missed what our build failure was for armhf12:33
ogasawaraapw: looks like the build was restarted though12:34
apwogasawara, the error was essentiall the compiler trynig to read the file with the first 3 lines missing12:34
apwogasawara, it worked just fine on armel with the same config, so we put it back to see if it is transient12:35
apwogasawara, if it is we should cry12:35
ogasawaraapw: first 3 lines missing?!?!  that doesn't sound good.12:35
apwno, its first error was about the @ in the copyright messages12:36
ogasawaraapw: very odd12:36
apwogasawara, worrying is the word i am using12:37
ogasawaraapw: indeed, worrying is a better word12:38
smbogasawara, Just to get some feeling, when would you plan a next upload to the quantal kernel?12:45
ogasawarasmb: in a perfect world, not until after we release.  we obviously know that's never the case.12:45
ogasawarasmb: so I suspect upon the next critical bug fix, whenever that may be.12:46
smbThen I hope for the imperfect world and that I get more feedback on my latest test kernel for 102147112:46
smbbug 102147112:46
ubot2Launchpad bug 1021471 in linux "clone() hang when creating new network namespace (dmesg show unregister_netdevice: waiting for lo to become free. Usage count = 2)" [High,Triaged] https://launchpad.net/bugs/102147112:46
rtgthat one prolly counts as critical12:47
ogasawarasmb: I think that itself would be the critical bug we're looking for12:47
ogasawarasmb: and I suspect, the release team would allow an upload to fix that between now and next friday12:47
smb:) Ok, then I need to get feedback aspish. I think the last iteration step at least looks minimal invasive and works on the testcase12:48
ogasawaraapw: do you remember how far into the armhf build it failed?  just curious if we've made it past the trigger for the previous failure.12:49
ppisatiogasawara: smb: i think i've a commit for master too12:51
ogasawarappisati: ack12:51
ppisatiapw: last week we had a compiler failure on O armel, build was restarted and the failure disappeared12:52
ppisatiapw: you should prod infinity12:52
apwi am sure he will say buildds are like that12:56
apwogasawara, 41 minutes in12:57
ppisatiapw: do we have a dmesg of that builder?13:02
apwppisati, not that i know of13:03
bjfskaet: still looking for verification of bug 1033568. i'd hate to have to revert it.13:11
ubot2Launchpad bug 1033568 in linux "ACER aspire S3 track pad doesn't work with 12.04, backport needed from 12.10" [Medium,Fix committed] https://launchpad.net/bugs/103356813:11
xnoxbjf: well, the worst case? it didn't work before and still doesn't?13:21
rbasakrobher: where can I find the commit that you mention in https://bugs.launchpad.net/eilt/+bug/1061070/comments/11 please? I want to cherry-pick it for a test on 3.2.13:31
ubot2Launchpad bug 1061070 in linux "Reboot sometimes fails on highbank" [Medium,Confirmed]13:31
robherrbasak: ubuntu-quantal branch on our kernel tree or ikepanhc's kernel tree.13:33
ikepanhcrbasak: the patch in quantal-proposed (Ubuntu-3.5.0-17.26)13:35
ikepanhcrbasak: robher: http://kernel.ubuntu.com/git?p=ubuntu/ubuntu-quantal.git;a=commit;h=4743004fad90f0078073222342c62557bdd5d6b713:37
rbasakikepanhc: thank you! I was looking for it by commit hash thinking that it was the hash in that repo. I guess not :)13:38
ikepanhchash is not stable until it get into mainline... sometimes I need to grep the git log to find out, especially for CVE patches13:39
bjfxnox, that's not the worst case. if it's not verified it gets reverted.13:40
rbasakI understand. I just thought it was the hash of the entry in some repo I could get to13:40
robherrbasak: sorry, I should have been more specific.13:41
robherikepanhc: when will it land in quantal?13:42
ikepanhcapw: do we have plan to land quantal-17.26 before quantal release?13:43
apwikepanhc, i would expect it to be copied over once it has built yes13:43
xnoxbjf: ok. I thought if a revert happens -> new upload -> everything needs to be retested.13:43
xnoxbjf: but I am not familiar with kernel procedures to be honest.13:44
bjfxnox, nah, we're not that bad13:44
ikepanhcapw: thanks13:44
xnoxbjf: I had to retest everything after a revert in mdadm sru =(13:44
ikepanhcrobher: very soon I believe13:44
bjfxnox, and honestly, before it's reverted we will look at it again to see if it's so trivial that we'll let it pass13:44
bjfxnox, but if it is verifed, we don't have to do the review and it just sails through so that's what we prefer and why i nag (plus i like to nag)13:45
henrixbjf: for this specific bug, there are 3 (not so trivial) commits13:47
bjfhenrix, ouch13:47
rbasak474300413:48
rbasakoops13:48
=== yofel_ is now known as yofel
* ppisati goes out to buy some stuff16:03
rtgogasawara, looks like armhf is building correctly this time16:07
ogasawarartg: indeed, appears to have gotten much farther than the initial build16:07
ogasawarartg: which is good, but also concerning as to why the first build failed16:08
rtgogasawara, ghost in the machine16:08
ogasawarartg: I'm trying to wrap my brain around how the first build failure would even happen where the compiler just overlooks the initial lines in a file16:10
ogasawaraI'm guessing some level of corruption?16:10
rtgogasawara, its more likely that the source package wasn't delivered correctly.16:10
apwogasawara, i think we have had cases where throwing the builds back at the wall until the stick is a normal approach16:27
apwogasawara, it oculd be a compiler bug with something unitialised, or just bust h/w16:27
apwogasawara, not that we should not be crapping selves over it of course16:28
ogasawaraapw: indeed, it's definitely not the first time we're kicked a rebuild and "it worked".  But I would say I have never seen this type of failure before.16:29
apwogasawara, i was an oddy indeed16:41
Davieyapw: rebuild worked!17:04
apwDaviey, that a worry and no mistake17:05
DavieyI should have just given it back last night, in retrospect.17:05
apwmeh, it should be very rare that giving it back helps17:05
Davieyapw: clearly you don't have the racey unit tests we have to put up with in userspace.17:06
apwheh no, but this died compliling a simple file, in the first lines17:06
* rtg gets a whopping 50KiB/s from github17:11
rtgsconklin, are you working on bug #987566 ?17:34
ubot2Launchpad bug 987566 in linux-armadaxp "CVE-2012-2119" [Low,Fix released] https://launchpad.net/bugs/98756617:34
sconklinrtg: why yes I am, right now.17:35
rtgsconklin, ok, I'll leave you to it.17:35
sconklinI should have lied. It's not straightforward :-)17:35
rtgsconklin, this is the macvtap bug, right ?17:36
sconklinyes17:36
sconklinI'm just looking at Oneiric now17:36
rtgsconklin, it would be helpfull if you'd set those bugs to 'inprogress' and assign them so I don't replicate what you're doing.17:38
sconklinack17:38
* rtg -> lunch17:41
apwsconklin, CVE-2012-2390 on oneiric is actually fixed already, its an attibution error.  i have just shoved the annotation in and it is rebuilding17:43
ubot2apw: Memory leak in mm/hugetlb.c in the Linux kernel before 3.4.2 allows local users to cause a denial of service (memory consumption or system crash) via invalid MAP_HUGETLB mmap operations. (http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2012-2390)17:43
sconklinapw: ack17:45
=== henrix is now known as henrix_
=== henrix_ is now known as henrix
skaethenrix, bjf -  1033568,  has been validated to work fine.   Thanks henrix, bjf, jsalisbury :D18:30
bjfskaet, thanks18:31
henrixskaet: ack, thanks!18:31
* henrix -> EOD18:43
=== henrix is now known as henrix_
sconklinapw: you here?18:45
apwsconklin, yep18:49
sconklinwhen I set correct break-fix lines in a CVEs tracker file, do I also have to set not-affected for the appropriate releases, or will that happen automagically?18:50
apwif you add break-fix: and push them then the next run at :20 will update the tracker and you will get needes/pending etc18:51
sconklinremind me to buy you a beer at UDS18:51
sconklinthe CVE matrix is looking pretty good18:52
apwyeah we did pretty well zapping the ones which were old and actually closed19:07
apwthere are a few i think still which are closed and not right but jj is sorting those in theory when he gets time19:07
bjfapw, if we could get rid of those natty columns we'd look *really* good19:32
apwbjf, they will go away RSN when we go EOL, what 3 weeks?19:48
=== Nafallo is now known as ubot2
=== ubot2 is now known as Nafallo
bjfapw, yup20:02
* ogasawara lunch20:15
* rtg -> EOD20:36
cyphermoxfyi; https://bugs.launchpad.net/ubuntu/+source/linux/+bug/99263921:28
ubot2Launchpad bug 992639 in linux "Regression: 12.04 update breaks support for Internet Sticks (3G modems): Nokia CS-15, Nokia cs-17 and perhaps many others" [High,Confirmed]21:28
cyphermoxre: delay_use for usb_storage.21:29
jjohansenbjf: Was there a bug filed for the apparmor regression test failure I was looking at?22:03
bjfjjohansen: yes22:04
* jjohansen has been looking back through his logs and has only found Bug #105762322:04
ubot2Launchpad bug 1057623 in ubuntu-kernel-tests "test_apparmor failures on armhf-omap4" [Undecided,New] https://launchpad.net/bugs/105762322:04
bjfjjohansen: that looks like one, but i think i filed one as well22:04
bjflooking22:05
sbeattieyeah, but that's a different failure, due to PAGE_SIZE not being defined.22:05
* sbeattie is not sure what that's about.22:05
bjfjjohansen: bug 105043022:10
ubot2Launchpad bug 1050430 in apparmor "QRT regression test failure on quantal" [Undecided,New] https://launchpad.net/bugs/105043022:10
sbeattiebjf: thanks22:11
jjohansenbjf: thanks22:14

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!