[00:42] <bananapie> If I install an upstream kernel provided by Ubuntu, is that the same thing as a mainline kernel?
[00:47] <TJ-> From the kernel team mainline PPA? Yes
[00:48] <TJ-> The prebuilt mainline kernels use the Ubuntu config though, to be as compatible as possible without adding any SAUC patches
[07:31] <smb> henrix, Ah thanks. Somehow I'd be interested to hear more details on how (and maybe on what hw) you succeeded. Cause I could not reproduce it with the steps I did before on less critical to me machines
[07:49] <henrix> smb: sure, i'm not in the office yet so i can give you only what i remember.  i do remember the eth card is a realtek using the r8169 driver
[07:53] <smb> henrix, Meh, I could wait for you to be in the office. :) I am not sure the card itself matters as my NAS which showed the bug and my other testbox have exactly the same model. But maybe its something with cpu to network speed (the NAS box is based on Atom, so not very powerful on the cpu side)
[07:56] <henrix> smb: ok, so that was on a lenovo laptop (ideapad something...) with 4 i7 cores, with threads enabled.  so, a bit more powerfull than an atom :)
[07:58] <smb> Hm, ok. So then rather not that. :) Did you need to write stuff for longer or do the crashes happen rather quick?
[07:59] <henrix> smb: no, that was quick.  i just started copying a few M
[08:01] <smb> henrix, Weird. So quite like on my NAS and no clue why the other cases just worked fine without any problem. o.O
[08:02] <henrix> smb: probably not relevant, but the client was running vivid
[08:03] <smb> henrix, No, unlikely since for anything I did (successful or not) I was using the same Trusty client 
[08:05] <henrix> smb: i'm still not convinced about the lts-u, though.  i've asked the guy on the bug to post the kernel log, but that didn't happen yet
[08:05] <smb> henrix, yep, saw the bug email
[08:05] <smb> or did not see it (any reply)
[08:06] <henrix> smb: i'll try to reproduce it in lts-u, but it will take me a bit
[08:06] <smb> henrix, ack
[08:46] <jjohansen> AceLan: see your mail, if you run into problems ping me
[08:47] <AceLan> jjohansen: got it, thank you very much
[08:47] <smb> henrix, @linux-stable -> [PATCH stable<3.19] net: handle null iovec pointer in skb_copy_and_csum_datagram_iovec()
[08:49] <henrix> smb: looking
[08:50] <apw> bananapie, TJ- is on the money if you mean the ones from ~kernel-ppa
[08:51] <henrix> smb: aaahhh!
[08:51] <smb> henrix, we are not alone... :-P
[08:51] <apw> henrix, let me guess, a regression in -proposed ?
[08:52] <henrix> apw: of course :)
[08:52] <apw> henrix, oh how we love those
[08:52] <apw> henrix, oh and please don't look at the adt-matrix for the moment, you will have a heart attack and its mostly lying
[08:53] <apw> henrix, an erroneous trigger with junk in a version (caused by another bug) has causes chaos
[08:53] <henrix> apw: yeah, i've been busy with other things so adt-matrix is very low in my priorities at the moment :)
[08:54] <apw> henrix, good, pretend is said nothing :) 
[08:55] <jjohansen> AceLan: one more thing, we just use the default config values
[08:56] <AceLan> jjohansen: that means we should align with ubuntu-vivid's apparmor releated options?
[08:57] <jjohansen> AceLan: yes, but you can get that by choosing the default config options when doing updateconfigs
[08:58] <AceLan> jjohansen: ../../../../../../kernel/security/apparmor/domain.c:610:2: error: implicit declaration of function 'task_no_new_privs' [-Werror=implicit-function-declaration]
[08:58] <jjohansen> AceLan: okay give me a few minutes to look at it
[08:58] <AceLan> jjohansen: thanks
[08:59] <AceLan> jjohansen: btw, I didn't change kernel options yet
[08:59] <jjohansen> AceLan: thats fine
[08:59] <smb> apw, henrix is busy trying to handle all the "good news" I seem to provide most of recently
[09:00] <apw> smb, how many is that in this set ?
[09:01] <smb> apw, not sure how much it may fall into one thing, but Trusty seemed to potentially have up to 3 regressions... though by the nature it might be one with random things happening to people
[09:02] <apw> smb, oh googy
[09:14] <AceLan> jjohansen: I don't want to occupy you too much time, no worries, I think I can fix this issue by myself. And I have to leave now, I'll contact you if I need your help next week, thanks a lot :)
[09:22] <jjohansen> ok, bye AceLan
[09:30] <who_me> hi, guys, why isn't the latest mainline building properly on x64? I see something about ZFS in the logs
[09:31] <who_me> actually both 4.2.4 and 4.1.11 are affected
[09:31] <smb> henrix, Yay! So this other system I just set up is usable to be unusable after writing doing the test. So that can be used for reproduction
[09:32] <henrix> smb: cool!
[09:32] <henrix> smb: so.... have you seen the reply to that patch in stable mailing-list?
[09:32] <smb> henrix, not yet
[09:33] <smb> now I did
[09:33] <henrix> smb: looks like a different solution had been posted already a few days ago :-/ i had that patch tagged as 'TODO', but havent actually checked it
[09:36] <smb> henrix, I see... So we could move that or that way or wait a little longer for maybe authoritative feedback...
[09:38] <henrix> smb: or just revert it for now, applying it again once we have a final version
[09:38] <smb> henrix, or that. 
[09:39] <smb> henrix, Since that gets is into a place at least no worse than before... maybe the best path
[09:41] <henrix> smb: gahhh! precise also has this commit.  bjf just uploaded it yesterday :)
[09:42] <henrix> at least it hasn't hit -proposed yet
[09:42] <smb> henrix, why stay only half broken of we can be completely broken...
[09:43] <smb> ;-P
[09:43] <henrix> heh, true
[09:43] <apw> henrix, yeah if it is only in CKT then its just buildd time wasted
[09:43] <apw> and maybe an upload number or two
[09:44] <smb> henrix, Just to be careful, I just installed your kernel version of T with the one patch reverted and now might have dhcp issues...
[09:58] <henrix> smb: any idea about what's wrong?  it shouldn't be kernel-related, i guess...
[10:00] <smb> henrix, well dhcp is something multicast so maybe changes that come together but then rely on the one we want to revert... or just coincidentally hw explosion
[10:03] <henrix> smb: yeah, odd
[10:05] <quadrispro> hi all
[10:05] <quadrispro> could anybody have a look at lp#1439111 please?
[10:05] <quadrispro> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1439111
[10:05] <quadrispro> it'd be 2-lines patch
[10:07]  * apw looks
[10:07] <apw> ok that made it into v4.3-rc1, dispite what the conmmentary says in the bug
[10:07] <apw> jsalisbury, ^ one for your list perhaps ...
[10:08] <apw> quadrispro, we'll try and get you a test kernel and so on soon ...
[10:08] <quadrispro> apw, true, I believed that was to be included in 4.2
[10:08] <quadrispro> apw, yeah thanks, do you think then we have chances to see that in wily at some point?
[10:08] <apw> quadrispro, yeah must have missed it, it was in the merge window instread
[10:09] <apw> quadrispro, the patch is pretty simple, and if the thing just does not work without it, it is hard to see how it would regress anything, so the chances are above average i'd say
[10:09] <apw> quadrispro, but we need to go through the motions, get a patch tested by you, reviewed etc
[10:10] <quadrispro> apw, I got my better half's Lenovo Yoga 3 11 ready to test it already :)
[10:12] <apw> heh, i know how that works oh so well
[10:13] <quadrispro> not too bad to be honest but yeah, it definitely lacks features
[10:18] <quadrispro> apw, thanks for helping out! i'll sit and wait until something happens on lp #1439111
[10:18] <apw> quadrispro, the guy i asked to have a look is east coast so don't expect it toooo sooon
[10:19] <apw> quadrispro, we are a bit frantic here, its "new release opening" time of the cycle
[10:22] <quadrispro> apw not a problem, my custom kernel has worked good so far. Therefore I can wait, thanks!
[10:40] <smb> henrix, OK... not sure what that was. I went back and forth with the kernels. That box has two NICs one Nvidia nforce and one Marvell. The Nvidia one appeared to get no incoming packets with the test kernel with the revert while the Marvel NIC did work ok. Though maybe the NVidia one which I used for the nfs test first still got spammed by the sender...? 
[10:40] <smb> Had to forcefully reboot my desktop. And now I have the other box up with the test kernel with the revert and the Nvidia NIC works still....
[10:41] <smb> henrix, So bottom line... I guess we could proceed with pushing the revert while waiting for the real fix
[10:43] <henrix> smb: cool, thanks!
[10:44] <apw> ogasawara, rtg, i am proceeding with opening repositories for xenial ... i am writing new opening instructions as i go as we've not updated for repos on LP
[12:37] <smb> henrix, Maybe (as soon as the re-spin is out) we should also write a note to the other two bug reports (the mumble and the other NULL pointer deref) we noticed for Trusty to ask them whether maybe that fixes those, too
[12:41] <henrix> smb: ah, good idea
[12:47] <apw> or make one test kernel on any one of them and just ask them to test that
[12:48] <smb> or that, which could be the one henrix already did for the nfs one
[12:49] <henrix> apw: ok, i've already a test kernel so i'll ask that
[17:22] <jsalisbury> quadrispro, apw, I posted a link to a test kernel in bug 1439111
[17:30] <apw> jsalisbury, hey thanks
[17:59] <TJ-> Is the amd64 build failure for mainline v4.2.4-unstable temporary? "rsync: change_dir "/home/kernel/COD/linux//spl" failed: No such file or directory "
[18:09] <rtg> apw, ^ that looks suspicious
[18:09] <TJ-> build log: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.2.4-unstable/BUILD.LOG.amd64
[18:31] <lownin> I'm running ubuntu server 15.04 on my home server.  After doing apt-get dist-upgrade, this happens when I try to boot - http://imgur.com/a/20zFG
[18:31] <lownin> It seems to be failing to boot with Ubuntu Kernel 3.19.0-31 and if I interupt grub during boot and select 3.19.0.15, my system boots just fine without the above errors.  Anyone have any ideas where I should even start with this?  Thanks!
[18:55] <dudebro> I have a strange problem. Running Ubuntu 14.04 3.13.0-66-generic. My laptop failed to resume from suspend, so I hard reset. Now, USB is broken, the window ("decorator") looks different, and when I try to reboot the computer just remains at the purple ubuntu screen with the multi-dot progress indicator scrolling away. This happens even when I try to boot into older kernels (e.g. 3.13.0-65-generic)
[18:58] <apw> lownin, if you are saying -15 woks and -31 does not, then finding the first one which fails would be good
[18:59] <lownin> apw: Forgive me, but I am not familiar with how I would select specific kernels and install them so they list in grub. Do you have instructions for that?
[19:39] <apw> lownin, you can find all the kernels for a series on the publishing page:
[19:39] <apw> https://launchpad.net/ubuntu/+source/linux/+publishinghistory
[19:40] <apw> and look for the ones in your release