=== AceLan_ is now known as AceLan [12:50] apw, I assume this is a duplicate: https://bugs.launchpad.net/bugs/1494562 [12:50] Ubuntu bug 1494562 in linux (Ubuntu) "[4.2.0.10] kernel: Request for unknown module key 'Build time autogenerated kernel key: .....' err -11" [Undecided,Confirmed] [12:54] rtg, yes, will dup [12:56] rtg, and done [12:56] apw, ack [12:57] rtg, i have sent a proposed fix upstream, and having confirmed it is a 1/256 chance of recurring i have just done a no-change rebuild [12:57] until we get confirmation of the approach in my fix [12:57] apw, yup, I kind of figured that out, though I have not seen the patch. Perhaps you could attach it to the bug ? [13:00] rtg, attached [13:00] rtg, introduced in 3.19 i think so we may see this issue back there also [13:03] apw, gawd, how did you figure this patch out ? it makes my head hurt. [13:11] rtg, reading a lot of the history for that file change [13:12] no dobt [13:12] doubt* [13:13] rtg, one reason i have not yet applied it, as they may have reasons for that strip and then the fix is to strip it in the signer [13:13] not that i can imagine why one would do that, but hey [13:13] hence the no change rebuild [13:13] exactly, as there is only a very low change of it recurring on such a build [13:15] apw, do you suppose we can get -10.11 promoted this morning ? [13:16] -7.7 has a weird crash that I'd like to see if it just goes away [13:17] rtg, the testig i looked at looked good, bjf do you concur [13:17] rtg, and we were waiting on a last few tests to finish [13:17] which have been delayed because lcy01 got eaten by juju over night [13:17] again ? [13:18] lcy01 is normally broken, but today it is _gone_ same issue as ps4 [13:19] I noticed a bunch of test failures on an i386 box, but haven't drilled in to figure it out. everything else looked pretty good. [13:19] we have a couple of failures on xfs which seem to be output format changes, which cking is looking at [13:20] there are also a bunch of skylake changes I'd like to get into the wild [13:20] otherwise it looked generally sany [13:20] yeah i agree we want it out [13:20] i think the testing on the previous version was ok, so its not clear it could be any worse [13:20] so as soon as the adt tests finish i think it will be migratable [13:21] the problematic ones have made happily green [13:21] apw, guess I'll go work un unstable for a bit. 4.3-rc1 is out [13:21] ok [14:01] rtg, apw, testing for 4.2.0-10.11 looks good to me [14:02] bjf, ack. do I just remove the tag for auto-promotion ? [14:02] apw, ^ ? [14:02] bjf, if we set the test to good will shanky do that for us now ? [14:03] apw, lets try ... [14:03] when it sees all the ADT tests done, which they are not all yet [14:03] * apw whips the camels [14:04] poor camelids [14:05] bjf, ok i am wacking some failed dkms tests [14:05] but i think it would be good to see this do the right thing itself [14:06] apw, what exactly did you do? "automated-testing" is already "Fix Released" on the tracking bug [14:06] i exactly did nothing, i cirtainly did not move that task [14:06] oh are you looking at 10.10 or 10.11 [14:07] apw, 10.11 [14:07] oh and ... of course it would have gotten confused in the old stuff because we only have the [14:07] abi number, so this test of the shanky changes is a bust [14:07] :-) [14:07] that is all fixed with the new adt based regression bits [14:07] so ... rip the tag and we'll see it migrate when adt passes [14:08] apw: note that shank looks for the test results here: https://people.canonical.com/~kernel/status/dashboard-helper/proposed-migration/regressions.txt [14:10] henrix, no you shouldn't be using the adt-matrix that is a human jobbie, proposed-migration is good [14:10] now ... why on earth do i not have all the matching results ... in adt-matrix ... grr [14:10] henrix, what y9ou have done is right [14:11] apw: right, but i still see regressions in that regressions.txt for which i don't know what to do :) [14:11] apw: there are 3 tracking bugs halted because of these regressions [14:11] henrix, give me a minute [14:12] apw: ack, thanks [14:12] and i'll have a look and hsow you how i have a look [14:15] cking: further to my moan that 4.2 causes slowdown during IO, I'm also finding my laptop is painful when running any kind of hangout / webrtc chat thing - even with nobody else joined, and my webcam off! Very odd. [14:16] (may not be a 4.2 thing, but it certainly got very worse recently) (load avg 13 during a hangout, and completely unresponsive desktop) [14:16] does it grow spikes on the keyboard and stuff ? [14:16] or what do you mean by painful ? :) [14:16] back under your bridge! [14:17] popey, well, I've got 2+ more days of intensive fs testing to complete then I can do a full apples vs pears comparison [14:17] heh [14:17] bjf, ok leave that tag on there a sec, there is some issue with britney i'd like to get debugged [14:17] meanwhile, I'll send you an email with some things to try to get some more hard facts so I can ponder on what's going on === manjo` is now known as manjo [15:05] cking: thanks [16:44] Using 'ecryptfs-recover-private' with 4.2.0-10-lowlatency, getting "Could not find valid key in user session keyring ...", but 'keyctl list @u' shows the keys are present. I've been using this daily for weeks to mount external disk file-systems but today it fails, mount reporting "mount: mount(2) failed: No such file or directory" but both source and mountpoint exist. Any ideas? [16:45] tyhicks, ^^ [16:45] TJ-, cking: I can help in ~15 min [16:46] tyhicks: no rush... I'm digging into it but drawing blanks so far [17:01] Hi! it seems kernel 4.3 rc1 build failed or something, is that a known issue? if so how long is the build fix expected ? [17:01] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.3-rc1-unstable/ [17:05] TJ-: are you logged into the machine over ssh? [17:06] tyhicks: No, regular boot session with KDE. The problem FS is an external drive [17:06] tyhicks: Can I private you a link URL to a log of the attempt? [17:08] TJ-: Sure === slangase` is now known as slangasek [19:13] hey [19:13] what is the right way to do what i would have thought this would do: [19:13] git://kernel.ubuntu.com/ubuntu/ubuntu-wily [19:13] my expectation based on https://wiki.ubuntu.com/KernelTeam/GitKernelBuild [19:13] showing git clone git://kernel.ubuntu.com/ubuntu/ubuntu-lucid.git [19:16] i'm guessing its 'unstable' [19:16] based on http://kernel.ubuntu.com/git/ubuntu/unstable.git/ [19:16] is that right ? [19:19] smwe've moved wily and unstable to LP, so they've got new paths. [19:19] smoser, ^ [19:19] git://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/wily [19:19] thanks [19:19] git://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/unstable [19:20] seems someone is maintaining the unstable though at the old location still [19:20] smoser, both should be mirrored to kernel.ubuntu.com in the usual places [19:21] i dont see a wily at kernel.ubuntu.com [19:21] and get: [19:21] ⟫ git clone git://kernel.ubuntu.com/ubuntu/ubuntu-wily.git [19:21] Cloning into 'ubuntu-wily'... [19:21] fatal: remote error: access denied or repository not exported: /ubuntu/ubuntu-wily.git [19:23] smoser, apw did it. looks like he put wily in kernel-ppa/mirror [19:23] rtg, are you able to easily confirm or deny a suspicion i have that COMMAND_LINE_SIZE changed in the generic arm64 kernel between vivid and wily ? [19:23] smoser, that sounds familiar [19:24] smoser, its master in LP [19:24] well, it seems to have shortened. [19:25] smoser, '#define COMMAND_LINE_SIZE 1024' in both kernels [19:25] rtg, we can symlink that kernel-ppa/mirror/ubuntu-wily.git over to ubuntu, i have tested it, you wen't keen [19:26] apw, I'm fine the way it is. [19:26] ok [19:28] apw, at some point we should host all of our git repo on LP and just mirror them to wani [19:28] rtg, right that is the plan ... [19:28] apw, perhaps when we are all in the same room ? [19:28] well, whatever is correct, please update doc ? [19:29] smoser, URL ? (I can't remember it) [19:30] you can't remember from above, where i typed it :) [19:30] https://wiki.ubuntu.com/KernelTeam/GitKernelBuild [19:30] thats where i saw it [19:30] ah, smart alek. [19:30] you just think I read for content [19:30] also mentioned here https://wiki.ubuntu.com/Kernel/Dev/KernelGitGuide [19:31] apw, so maybe we _should_ just link wily. that way I don't have to edit wiki pages. [19:31] rtg, ok ... i'll sort it [19:33] rtg, and done [19:33] smoser, does it work for you now ? [19:34] does what work ? [19:37] the old name [19:38] smoser, git clone git://kernel.ubuntu.com/ubuntu/ubuntu-wily.git [19:43] ah.it does