/srv/irclogs.ubuntu.com/2015/05/20/#ubuntu-kernel.txt

=== gerald is now known as Guest78324
sbeattiebjf: Hi. I just looked at the apparmor failure log in http://kernel.ubuntu.com/testing/onibi__3.13.0-53.88__2015-05-18_17-33-00/console_output.txt.html ; it looks like it pulled in the apparmor packages in trusty-proposed, which means you shouldn't see the apparmor apport hook failure anymore (yay!), but it it looks like the trusty-proposed deb-src line wasn't enabled in apt's sources.list.06:07
sbeattiebjf: that may be the cause of the different failures seen this time, as part of the apparmor qrt test script downloads the source package and runs make check in it.06:09
bjfsbeattie, ack, i'll look at it tomorrow. thanks06:11
sbeattiebjf: no worries, thanks.06:14
sbeattieah, yep, I've reproduced the the failures with the sources from apparmor 2.8.95~2430-0ubuntu5.1 while binary packages from 2.8.95~2430-0ubuntu5.2 are installed.06:22
FourDollarssforshee: Hi, did you remember the patch you made for Dell New XPS 13? https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/hid/hid-multitouch.c?id=2c6e0277e1eab3df5db81c59e408b7b1c14b1b7206:41
FourDollarssforshee: Does it fix any problem?06:41
=== gerald is now known as Guest33142
pkernThe new 3.13 contains "tcp: make connect() mem charging friendly" but doesn't seem to contain "tcp: Fix crash in TCP Fast Open", is that intentional?09:16
pkernI didn't check if it crashes in the same way as 3.16 did, but it's somewhat concerning that the fixup wasn't picked up if it's needed. |:09:17
pkernYeah, it's dead on arrival for us.09:21
apwpkern, new 3.13 stable or new 3.13 in -updates in trusty ?09:22
pkern3.13 in -updates in trusty.09:22
apwhenrix, ^09:22
pkernOf course it relies on things to use fast open. Which probably just Google does? I don't know.09:22
apwyes, you are likely the only people in the world advertising that feature sadly09:23
pkernAnd using it in clients, I guess.09:23
* henrix goes have a look09:23
apwthat patch shows applied across the board (as it was a cve) but it was behind the other releases in trusty09:24
apwbut i had assumed that meant the introducing commit was also not released either ... hmmm09:24
henrixugh09:25
henrixyeah, that's correct09:25
henrixpkern: thanks for spotting that!  i'll go work on fixing that ;)09:28
infinityhenrix: Hrm.  Should we do a single-commit respin to pick that up?09:28
pkernhenrix: ta!09:28
infinityAccording to Ben's commit message, it should only affect 3.13 and 3.16.09:29
infinityAnd it was fixed in 3.16 already, so just 3.13.09:29
apwyeah somehow we paired it up in 3.16 and not in 3.1309:30
henrixinfinity: yeah, i believe a quick respin will be needed.  i go finish the V respin and start with fixing T09:30
infinityhenrix: +1 from me for a single-commit resping of T and lts-T.09:30
infinityrespin, too.09:30
infinityTyping hard.09:30
infinitypkern: Since you seem to be a pro at reproduction, can I get you to test henrix's kernel when he does the deed, so we can turn it around ASAP?09:31
pkerninfinity: Sure.09:32
genkgoinfinity: last week you helped me out with getting cloud tools for kernel 3.19. we switched to this kernel for our problems with creating vss snapshots on our hyperv machine.09:36
genkgoinfinity: unfortunately, it did not solve the issue. our vps goes read-only sometimes while creating these vss snapshots. now we have switched to a new kernel, the error is different than before.09:37
infinitygenkgo: You want apw, not me.09:37
genkgoblk_update_request i/o error, dev sa, sector xxx09:37
infinitygenkgo: I was just helping with the packaging mysteries, not the hyperv madness.09:37
genkgoinfinity: ok :)09:37
genkgoapw: i still have some hyperv madness :)09:38
apwgenkgo, ok add that info to the bug, and the new dmesg, and remind me of the bug number, and i'll see if we can get someone to reproduce it09:38
pkernhenrix: Just drop me a mail at $nick@google.com if you have something to test for me. I take it that a respin would likely be released earlier than next Sunday? :)09:39
henrixpkern: yeah, for sure before Sunday :)09:40
henrixpkern: i hope to have it uploaded and building later today, i'll email you once we have a test kernel09:40
pkernhenrix: Thank you :)09:41
genkgoapw: i did not report a bug before, because we thought it was related to the kernel version. if i run "ubuntu-bug linux" i get "This is not an official Ubuntu package. Please remove any third party package and try again." (*** Problem in linux-image-3.19.0-17-generic)09:41
infinitypkern: If all goes well, I'd expect to release it in < 24h.09:43
=== dupondje_ is now known as dupondje
genkgoapw: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/145698510:23
ubot5Launchpad bug 1456985 in linux (Ubuntu) "Filesystem goes read-only while creating VSS snapshot on HyperV" [Undecided,New]10:23
genkgoapw: While browsing through other bugs related to Hyper-V in the Ubuntu kernel, I found this one https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1445195. These patches will solve my problem. The reported problem here https://social.technet.microsoft.com/Forums/windowsserver/en-US/8807f61c-565e-45bc-abc4-af09abf59de2/ubuntu-14042-lts-generation-2-scsi-errors-on-vss-based-backups is an exact copy of the problem we are having.10:34
ubot5Launchpad bug 1445195 in linux (Ubuntu Wily) "[Hyper-V] Kernel patches for storvsc" [High,Triaged]10:34
infinitygenkgo: Ahh, lovely, thanks.10:52
infinityapw: Bonus points if you can get those on to all the master-nexts before the next SRU cycle happens. :)10:53
genkgoinfinity: for me this also great news. i had the feeling i was on my own with this problem. now fortunately i see there are many others that have the problem. and there is already a patch it.10:54
infinitygenkgo: Always nice to see that it's ultimately not our fault, too. :P10:54
genkgohehe, i totally understand that!10:55
apwsigh, i believe we are waiting on some testing for those from microsoft, will chace that up11:19
genkgoapw: if there is any testing we can do: please let me know. i'd love to help.11:30
apwgenkgo, yep, will make sure you get some test kerenls11:31
genkgoapw: wonderful, thanks for the good work11:31
jsalisburygenkgo, Should have test kernels for each release in about 15 to 20 minutes12:08
genkgojsalisbury: wonderful!12:08
genkgojsalisbury: should build a kernel myself then or is it apt-get install? i am not extremely familiar with building a kernel.. :)12:09
jsalisburygenkgo, I'll have the kernels as a .deb file, then you can dpkg -i them12:10
genkgojsalisbury: aight, that would be no problem :)12:10
jsalisburygenkgo, there is already a vivid kernel here: http://kernel.ubuntu.com/~jsalisbury/lp1445195/vivid/  Building the other releases now12:11
genkgojsalisbury: we are on trusty with vivid kernel, so i can use those already12:12
genkgojsalisbury: i am still working on something else now, but will make sure to install today. last time it took 36 hours before we had a machine crashed on backup, and then we were creating backups every hour.12:13
jsalisburygenkgo, great.  You just need to install the linux-image and linux-image-extra .deb packages.12:13
jsalisburygenkgo, ok, thanks12:14
genkgojsalisbury: great, thanks for the work12:14
jsalisburygenkgo, np12:14
jsalisburygenkgo, thanks for offering to test!12:15
genkgojsalisbury: sure, we would like to get rid of the problem asap. i am going to run the tests on a production machine. on machines with not enough activity (test machine) we were not able to reproduce the bug. or we did not wait long enough (4 days, backup every hour).12:18
sforsheeFourDollars: that patch gets INPUT_PROP_BUTTONPAD set for the xps 13 touchpad in i2c mode, though 015fdaa9f8edd89a456b3331088e1b77ebdad9d0 does as well12:36
genkgojsalisbury: could you say which patches are applied to that build?12:45
jsalisburygenkgo, yes, they are the following:12:47
jsalisburyscsi: storvsc: Increase the ring buffer size12:47
jsalisbury  scsi: storvsc: Size the queue depth based on the ringbuffer size12:47
jsalisbury  scsi: storvsc: Always send on the selected outgoing channel12:47
jsalisbury  scsi: storvsc: Retrieve information about the capability of the target12:47
jsalisbury  scsi: storvsc: Fix a bug in copy_from_bounce_buffer()12:47
jsalisbury  scsi: storvsc: Don't assume that the scatterlist is not chained12:47
jsalisbury  scsi: storvsc: Set the tablesize based on the information given by the 12:47
genkgojsalisbury: thanks, how about this one: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1454758?12:47
ubot5Launchpad bug 1454758 in linux (Ubuntu Wily) "[Hyper-V] storvsc: Set the SRB flags correctly when no data transfer is needed" [Critical,Triaged]12:47
jsalisburygenkgo, that particular commit is not in that test kernel.  It was cc'd to upstream stable and should come down through the normal stable process. 12:50
jsalisburygenkgo, I can build a test kernel the that commit and the previous 7 I posted12:51
genkgojsalisbury: i am not able to qualify whether the particular bug we are having (backups with hyperv) is related to that one, or to the storvsc onw. can you?12:52
jsalisburygenkgo, I don't believe it is related to eh backups bug, which is why it was requested in a seperate bug report12:53
genkgojsalisbury: just to be sure: the build you created fixes a.o. the backup bug, right?12:54
jsalisburygenkgo, correct12:54
genkgojsalisbury: lovely :)12:54
jsalisburygenkgo, I'll be building Utopic and Trusty test kernels as well, the commits are requiring a little backporting, so taking a little longer than expected.12:55
genkgojsalisbury: ok, but i need the one you already have builded, so that is no problem12:56
jsalisburygenkgo, cool12:56
genkgojsalisbury: at least, i do not see a reason why i should go back to 3.13 kernel12:56
FourDollarssforshee: So what's the difference between yours and the original one? I mean if there is no your commit, what's going to happen?13:08
sforsheeFourDollars: basically they arrived on the list at about the same time, and they went ahead and took both. For the xps 13 the results are identical; possibly for some other touchpads one or the other might not work.13:11
FourDollarssforshee: I see13:13
FourDollarssforshee: Thanks for your explanation.13:13
sforsheeFourDollars: obviously I like my approach better ;-)13:13
FourDollarssforshee: haha13:13
genkgojsalisbury: i am having dependency problems16:38
jsalisburygenkgo, I now have test kernels for Trusty and Utopic if your willing to test?  All the test kernels are available from: http://kernel.ubuntu.com/~jsalisbury/lp1445195/16:39
jsalisburygenkgo, Can you post any errors you are seeing16:39
genkgojsalisbury: http://paste.ubuntu.com/11247594/16:40
genkgojsalisbury: while runing sudo dpkg -i *.deb16:40
jsalisburygenkgo, try only installing one package at a time.  First the linux-image package then the linux-image-extra package16:41
genkgojsalisbury: no difference16:42
genkgojsalisbury: could it be the same dependency errors that i was having before?16:43
genkgoapw: could this be the same dependency problem?16:43
genkgojsalisbury: there is only a problem with tools and cloud tools16:44
genkgoimage headers and extra are doing fine16:44
jsalisburygenkgo, you won't need linux-tools or linux-cloud for this testing, only linux-image and linux-image-extra16:45
jsalisburygenkgo, So these two .debs:16:45
jsalisburylinux-image-3.19.0-17-generic_3.19.0-17.17~lp1445195_amd64.deb16:45
apwjsalisbury, yes if you are installing a "standard" kernel, not lts-foo, then you need to switch to the default linux-tools-common things16:46
jsalisburylinux-image-extra-3.19.0-17-generic_3.19.0-17.17~lp1445195_amd64.deb16:46
genkgojsalisbury: those are installed16:46
jsalisburyapw, is linux-tools needed for testing these hyper-v commits?  I didn't think so16:47
genkgojsalisbury: microsoft is saying they are required16:48
genkgojsalisbury: they are required, in which sense (backuping or otherwise) is unknown16:49
genkgojsalisbury: http://paste.ubuntu.com/11247689/16:51
genkgojsalisbury: so i still have the linux-lts-vivid-cloud-tools-common package16:52
jsalisburygenkgo, Hmm, I wonder if we need to remove that first.  Is this on a non-production system, so we can remove it first.  Then run:16:53
jsalisburysudo apt-get install -f16:53
jsalisburysudo apt-get clean16:53
jsalisburysudo dpkg -i linux-tools-3.19.0-17-generic_3.19.0-17.17~lp1445195_amd64.deb16:53
genkgojsalisbury: this is production :)16:55
genkgojsalisbury: not working, same error: linux-tools-3.19.0-17-generic depends on linux-tools-3.19.0-17; however: linux-tools-3.19.0-17-generic depends on linux-tools-3.19.0-17; however:16:56
jsalisburygenkgo, let me see if I can install it locally16:59
apwi think you need to remove the lts-foo versions of the common tools packages, which in fixed packages wont exist17:00
apwand then you ought to get the appropriate ones installed instead, the ones that got removed last time when installing lts-vivid17:00
jsalisburygenkgo, so remove this one:  linux-lts-vivid-cloud-tools-common 17:00
genkgojsalisbury: already did17:01
genkgono differece17:01
jsalisburygenkgo, can you run the dpkg -l command again, to see what else is there17:02
genkgojsalisbury: 17:04
genkgojsalisbury: http://paste.ubuntu.com/11247908/17:04
jsalisburygenkgo, can you purge all of the linux-tools pacakges then reinstall just linux-tools-3.19.0-17-generic_3.19.0-17.17~lp1445195_amd64.deb17:06
jsalisburysudo dpkg --purge PACKAGENAME17:06
genkgojsalisbury: sorry, but same issue17:07
genkgohttp://paste.ubuntu.com/11247941/17:08
genkgoyou can see, all purged, won't install17:08
genkgohmm17:08
jsalisburygenkgo, It looks like it did install, see line 58617:08
jsalisburyiU  linux-tools-3.19.0-17-generic       3.19.0-17.17~lp1445195              amd64        Linux kernel version specific tools for version 3.19.0-1717:08
genkgono, it got errors while installing17:09
jsalisburygenkgo, same dependency error:17:10
jsalisbury?17:10
jsalisburygenkgo, hmm, I wound if it's because I added ~lp1445195 onto the package name.  It doesn't cause issues with the kernel, but maybe the tools package doesn't like it17:11
jsalisburygenkgo, let me build one more kernel without that extra text17:11
genkgojsalisbury: ok, i will wait for that, my system is pretty clean now: http://paste.ubuntu.com/11248013/.17:15
jsalisburygenkgo, ok, building now, it should only take 15minutes or so17:16
genkgojsalisbury: i just got a reply from microsoft on my bug report17:36
genkgohttps://bugs.launchpad.net/ubuntu/+source/linux/+bug/145698517:36
ubot5Launchpad bug 1445195 in linux (Ubuntu Wily) "duplicate for #1456985 [Hyper-V] Kernel patches for storvsc" [High,Triaged]17:36
genkgohttps://bugs.launchpad.net/ubuntu/+source/linux/+bug/145698517:37
genkgojsalisbury: he is telling we also need https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1454758, which is not included in your build17:37
ubot5Launchpad bug 1454758 in linux (Ubuntu Wily) "[Hyper-V] storvsc: Set the SRB flags correctly when no data transfer is needed" [Critical,Triaged]17:37
jsalisburygenkgo, Ok, I'll add it to my next build.  17:38
genkgojsalisbury: ok, thanks a lot17:38
genkgoi will wait for that before testing, thanks for the stuff you have already done17:39
jsalisburygenkgo, np17:41
jsalisburygenkgo, I have an updated kernel available at: http://kernel.ubuntu.com/~jsalisbury/lp1445195/vivid/18:30
infinitypkern: The trusty kernel with that fix should be hitting -proposed on mirrors over the next 15-30 minutes (it just hit disk on ftpmaster).18:54
genkgo-jsalisbury: still have dependency problems: Package linux-cloud-tools-3.19.0-18 is not installed.20:14
genkgo-Same for the tools package20:15
jsalisburygenkgo, I'll have to investigate further.  We may be able to just use the --ignore-depends with dpkg since this is only a test kernel.20:18
genkgo-apw: can this be related to dependency problems we had before?20:18
infinityNo, it's not related to the previous issue, it's that jsalisbury builds his test kernels a bit differently from how they're built in the archive, I'd guess.20:19
infinityOh, and it's a vivid kernel, not an lts-vivid kernel, which changes things somewhat.20:19
infinityHrm.  That tools package is indeed useless. :P20:21
infinityJust a bunch of symlinks into the missing package that you don't have built.20:22
jsalisburygenkgo, we might get away without installing tools just to test this bug, but I'll test locally to see if I can get it to install.20:24
infinityjsalisbury: AFAIK, he needs the tools for the backup thingee to work.20:25
infinityjsalisbury: And your build didn't produce all the right packages.20:25
genkgo-infinity: that is what i believe too20:25
infinityjsalisbury: Did you just do a binary-generic build instead of a full build?20:25
genkgo-i dont know how ignore depends works20:26
infinitygenkgo-: Don't bother, ignoring deps will just leave you a bunch of dangling symlinks.20:26
jsalisburyinfinity, I used this:20:26
infinityNo actual binaries.20:26
jsalisburyfakeroot debian/rules clean && fakeroot debian/rules binary-headers && fakeroot debian/rules binary-generic20:26
jsalisburyso thats probably it20:26
infinityjsalisbury: Yeah.  Do a full build instead.20:26
infinityjsalisbury: THen you'll get the common packages, etc.20:26
jsalisburyinfinity, ack, thanks.  First time someone needed the tools package from me :-)20:27
jsalisburyinfinity, do you happen to know the option for a full build off hand?  If not, I'll dig it up20:29
apwjsalisbury, to make the tools you need binary-tools as well20:30
jsalisburyapw, got it, Thanks!20:31
jsalisburygenkgo, I should have an updated tools package for you shortly20:33
genkgo-jsalisbury: aight, i will make sure to go ahead with it right away, thanks again!20:35
jsalisburyapw, doing a 'fakeroot debian/rules binary-tools' produced an error:20:36
jsalisburydpkg-gencontrol: error: package linux-image-3.19.0-18-tools not in control info20:36
jsalisburydh_gencontrol: dpkg-gencontrol -plinux-image-3.19.0-18-tools -ldebian/changelog -Tdebian/linux-image-3.19.0-18-tools.substvars -Pdebian/linux-image-3.19.0-18-tools returned exit code 25520:36
jsalisburydebian/rules.d/2-binary-arch.mk:407: recipe for target 'binary-tools' failed20:36
jsalisburymake: *** [binary-tools] Error 220:36
flexiondotorginfinity, I've had a few sponsor requests turned down.20:40
flexiondotorginfinity, Please take a peek at this - https://bugs.launchpad.net/ubuntu-mate/+bug/145659120:40
ubot5Launchpad bug 1456591 in ubuntu-mate-artwork (Ubuntu) " ubuntu-mate-artwork 0.4.8 bug fix release [debdiff attached]" [Wishlist,Incomplete]20:40
flexiondotorginfinity, I'm just wanting to know if this is standard practice?20:41
flexiondotorginfinity, https://bugs.launchpad.net/ubuntu-mate/+bug/145659720:41
ubot5Launchpad bug 1456597 in ubuntu-mate-settings (Ubuntu) " ubuntu-mate-settings 0.4.5 release [debdiff attached]" [Wishlist,Incomplete]20:41
flexiondotorgsorry. Wrong channel.20:43
jsalisburyapw, ah ha.  This what is needed to build the tools: fakeroot debian/rules binary-perarch21:25
jsalisburygenkgo, There is a new tools package called linux-tools-3.19.0-18_3.19.0-18.18_amd64.deb at the URL: 21:32
jsalisburyhttp://kernel.ubuntu.com/~jsalisbury/lp1445195/vivid/21:32
garrettrI'm working on building Ubuntu kernels w/ grsecurity21:45
garrettrThe command I use to build the kernel is make-kpkg --initrd --overlay-dir=../ubuntu-package kernel_image kernel_headers21:46
garrettrWhere ubuntu-package is a copy of /usr/share/ubuntu-package from an up-to-date version of Ubuntu trusty (currently running 3.13.0-53)21:46
garrettrI have seen other guides recommend download the ubuntu-trusty git repo from kernel.ubuntu.com, and replace some of the Debian control scripts from /usr/share/kernel-package with the ones in the git repo21:48
garrettrMy questions are: 1. why do this? 2. why don't the control scripts in ubuntu-trusty/debian/control-scripts match those in /usr/share/kernel-package/{image,headers}?21:49
bjfsbeattie, i'm following up on the apparmor tests22:37
bjfsbeattie, i'm looking at: http://kernel.ubuntu.com/testing/dagmar__3.13.0-53.89__2015-05-20_21-43-00/ubuntu_qrt_apparmor/results/ubuntu_qrt_apparmor.test-apparmor.py/debug/ubuntu_qrt_apparmor.test-apparmor.py.DEBUG.html22:37
cykingjsalisbury, let me know when/if you have time to assist with that bug report. thanks :)23:23
jsalisburycyking, sorry, I got side tracked today, I'll have the next kernel built shortly.23:26
cykingjsalisbury, all good! thanks.23:27

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