[02:42] <dannf> are autopkgtest failures for linux on xenial/armhf expected? https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/armhf/l/linux/20170928_172433_e133f@/log.gz
[06:32] <alkisg> I'm trying to do a small bisection on some kernel-side nbd bug, using the mainline PPA. And I got down to: 4.9=OK, 4.10=OK, 4.11=OK, 4.12=BAD.
[06:33] <alkisg> My problem is that without the mainline ppa, I have: 4.10.0-35-generic=BAD
[06:33] <alkisg> So I'm not sure how backporting of fixes go... should I now continue the bisection within the 4.11 series, even though the latest 4.10 from ubuntu is broken?
[07:16] <alkisg> I got it to: mainline: problem after last 4.11 and before 4.12.
[07:16]  * alkisg tries to bisect using this now: http://security.ubuntu.com/ubuntu/pool/main/l/linux-hwe/
[07:24] <alkisg> Nah, that just got me down to "between 4.8 and 4.11", trying http://gr.archive.ubuntu.com/ubuntu/pool/main/l/linux-hwe-edge/ now...
[07:28] <alkisg> The best I got is that this issue [https://github.com/NetworkBlockDevice/nbd/issues/57] happens between:
[07:28] <alkisg> Ubuntu's kernels: after 4.8.0-58 and before 4.10.0-14
[07:28] <alkisg> Mainline kernels: after 4.11.12 and before 4.12.0
[07:28] <alkisg> If someone can give me a hint on how to bisect it more without compiling kernels, please ping me :)
[10:27] <cascardo> alkisg: please, report a bug in launchpad
[14:46] <alkisg> cascardo: wouldn't it better to solve it upstream first, where I already filed the bug report, and then SRU it to Ubuntu?
[14:46] <alkisg> The last 10 kernel bug reports I filed in Ubuntu weren't really processed in launchpad...
[14:46] <alkisg> While SRUs generally were...
=== JanC_ is now known as JanC
[20:13] <alkisg> I also just tested on Debian Stretch with backports, it has the issue on 4.11 but not on 4.12, same as the mainline kernels; so Ubuntu having the issue in 4.10 is just a matter of some bad backport
[20:14] <alkisg> So I think the NBD kernel module bug report should be enough to get it solved
[21:29] <cascardo> alkisg: it's just that if there is a bug in zesty and if you want us to keep track of it and do the backport once it's fixed, we will need the bug. it's just process, and it would be helpful, actually
[21:30] <cascardo> otherwise, it might be fixed upstream, but the fix won't make it to zesty