[10:16] <diwic> Hi, are there any 4.4 Ubuntu kernels for xenial somewhere for testing? I'm seeing a regression from ubuntu-xenial-4.3 and upstream-vanilla-4.4 and I'd like to see if the ubuntu-ified 4.4 is affected or not. 
[10:17] <diwic> (I e, our 4.3 works, upstream's 4.4 does not)
[10:17] <apw> diwic, yes in ppa:canonical-kernel-team/ubuntu/unstable ...
[10:18] <apw> though i think we know it has a number of issues still, cking was tracking at least two
[10:19] <diwic> issues such as "you're computer will catch fire" or such as "if you have ppc64el, once in a million, it will consume 2% more power" ?
[10:19] <diwic> s/you're/your
[10:19] <diwic> apw, i e, should I try it or not :-)
[10:19] <cking> apw, yep, there an issse introduced after 4.4-rc6 that causes grub-install to break, commit d3805611130af9b9 ("Split bios on chunk boundaries)
[10:19] <apw> "makes grub2 explode in your face sometimes" ...
[10:20] <diwic> that sounds bad enough, thanks
[10:20] <apw> diwic, but that is in mainline too
[10:20] <cking> apparent a fix for this is coming "real soon"
[10:20] <apw> cking, was there anohter one, or was that the intel idle performance stat thing ?
[10:20] <apw> (that isn
[10:20] <apw> (that isn't an issue at all in fact)
[10:21] <cking> apw, that was actually a fix to intel_pstate that actually is fine as it was shown to save ~1+ watts on a test scenario where it looked like the CPU was being exercised more because it was just in a lower p state
[10:21] <apw> ok so only one real issue remaining
[10:22] <cking> one real issue that we are aware of ;-)
[10:22] <diwic> fwiw, it's my touchpad that stopped working on 4.3 -> 4.4
[10:25] <caribou> apw: FYI, just found created LP: #1532146, I should have a fix handy soon
[10:25] <ubot5> Launchpad bug 1532146 in initramfs-tools (Ubuntu) "update-initramfs fails for MODULES=dep when root is on nvme device" [Medium,Confirmed] https://launchpad.net/bugs/1532146
[10:25] <caribou> apw: I'll also forward to debian which has the same issue
[10:32] <cking> diwic, i guess wait until the next release and if it still plays up, file a bug and get jsalisbury to help you bisect it
[10:32] <cking> s/next release/next kernel/
[10:33] <diwic> cking, you mean next kernel in the unstable ppa?
[10:34] <cking> diwic, well, the next one in the unstable ppa that fixes the grub-install bug :-/
[10:35]  * cking has no idea when that will be, sorry
[10:35] <apw> caribou, ok ta, i have another fix i need to get into initramfs-tools pretty soon too, so if you get me the fix i'll wrap those two up together
[10:36] <caribou> apw: sure, I should have the debdiff attached to the case in a few minutes
[10:36] <diwic> cking, ok :-) I suppose that we can't just revert the patch for the time being?
[10:36] <caribou> apw: I ran into this because yet another case of OOM panic during a kernel crash dump on trusty
[10:37] <caribou> apw: initramfs was again too big
[10:37] <caribou> apw: I'm soo happy I fixed this problem in Xenial
[10:37] <diwic> cking, well, if it doesn't ends up getting fixed soon anyhow
[10:38] <apw> caribou, yeah, that was a good bit of work to be proud of
=== ddstreet_away is now known as ddstreet
[13:26] <caribou> apw: debdiff for LP: #1532146 is in the bug
[13:26] <ubot5> Launchpad bug 1532146 in initramfs-tools (Ubuntu) "update-initramfs fails for MODULES=dep when root is on nvme device" [Medium,Confirmed] https://launchpad.net/bugs/1532146
[13:33] <caribou> apw: FYI, https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=785147 claims to fix this for Debian but it is in Experimental & not in Sid. 
[13:33] <ubot5> Debian bug 785147 in initramfs-tools "initramfs-tools: NVMe boot drives not supported" [Important,Fixed]
[13:36] <xnox> i can even test that...
[13:36] <xnox> cause i've been failing to install on to my nvme laptop for weeks now.
[13:37] <xnox> caribou, we will want it backported for trusty too... no?
[13:37] <xnox> cause cking and I worked on supporting nvme drives in trusty.....
[13:38] <caribou> xnox: that was my next step
[13:38] <caribou> xnox: I got the problem on Trusty & tested the fix there
[13:38] <xnox> ack ;)
[13:38] <caribou> xnox: so the SRU should be trivial
[13:39] <caribou> xnox: it is mostly important for Xenial, since I changed kdump-tools to produce specific initrd files using MODULES=dep
[13:39] <caribou> xnox: but it would be good for trusty too if someone decides to use MODULES=dep
[13:54] <apw> caribou, ack, prolly will be monday when i do the upload, i've got a lot on my "today" plate
=== LocutusOfBorg1 is now known as LocutusOfBorg
=== LocutusOfBorg is now known as LocutusOfBorg1
=== LocutusOfBorg1 is now known as LocutusOfBorg
[17:56] <killertofu> Wondering if I can get somebody to help with https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1310800
[17:56] <ubot5> Launchpad bug 1310800 in linux (Ubuntu) "056a:0302 Trusty Tahr, kernel 3.13: automatic load of wacom.ko driver cause a "hard" kernel panic" [High,Confirmed]
[17:57] <killertofu> I diagnosed the issue and provided a patch to fix it four months ago (comment #23), but nothing seems to have been done with it...
[18:04] <henrix> killertofu: ugg, that was a long time ago.  i'll have a look at that
[18:04] <kamal> killertofu, hi.  thanks for bringing it up here
[18:04] <kamal> henrix, :-)
[18:04] <henrix> kamal: heh, exactly at the same time :-)
[18:05] <kamal> killertofu, henrix and I are the maintainers for 3.13 and 1.16 ... we'll *both* take an immediate look at that!
[18:06] <killertofu> glad to have found you two then! :)
[18:13] <wxl> hey does anyone know if exfat support has reached the kernel yet?
[18:37] <kamal> killertofu, ok, we've got the wacom patch in the pipeline for the next cycles of trusty (3.13) and lts-backport-utopic (3.16) ...  i.e. it will likely appear in the kernels that will enter the -proposed channel early next week.
[18:39] <kamal> killertofu, a bot will post a message to bug 1310800 once that kernel is ready for verification testing.  thanks again for the heads-up on this.
[18:39] <ubot5> bug 1310800 in linux (Ubuntu) "056a:0302 Trusty Tahr, kernel 3.13: automatic load of wacom.ko driver cause a "hard" kernel panic" [High,Confirmed] https://launchpad.net/bugs/1310800
[18:41] <killertofu> kamal: awesome, thanks :)
[21:15] <hallyn> all right, lemme tkae a look at the src for bug 1531747
[21:15] <ubot5> bug 1531747 in linux (Ubuntu Xenial) "overlay: mkdir fails if directory exists in lowerdir in a user namespace" [High,Triaged] https://launchpad.net/bugs/1531747
[22:03] <skoe_> Hi, I want to debug an alsa issue (for the first time) on Xenial Xerus. https://wiki.ubuntu.com/Audio/UpgradingAlsa/DKMS seems to be the wrong way - at least I don't see a DKMS package there. Can somebody give me a pointer?
[22:11] <arges> skoe_: that wiki may be out of date. Have you filed a bug with your current issue? You can use 'ubuntu-bug linux' for example
[22:13] <skoe_> It's that one: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1525554
[22:13] <ubot5> Launchpad bug 1525554 in alsa-driver (Ubuntu) "[HP ProBook 470 G3, Intel Skylake HDMI, Digital Out, HDMI] No sound at all" [Undecided,Incomplete]
[22:14] <skoe_> But as I'm a software developer anyway I'm interested in looking into it nevertheless. Play a bit with printk and see what happens :)
[22:16] <arges> skoe_: Well first thing would be to see if this is a regression of sorts then if so, locating the commit(s) that are missing or break it
[22:16] <arges> skoe_: did this work in 14.04 ?
[22:17] <skoe_> The machine is new (xmas). It didn't work on 15.10 neither, but IIRC I didn't try 14.04.
[22:17] <arges> and can you play with alsamixer to get settings working? it could be bad defaults?
[22:17] <arges> my skylake machine uses analog out because I haven't 'upgraded' to hdmi yet : )
[22:18] <skoe_> It has no codec when the issue is there. The last it says is [ 145.033347] snd_hda_intel 0000:00:1f.3: no codecs initialized
[22:19] <skoe_> Look at https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1525554/comments/11
[22:19] <ubot5> Launchpad bug 1525554 in alsa-driver (Ubuntu) "[HP ProBook 470 G3, Intel Skylake HDMI, Digital Out, HDMI] No sound at all" [Undecided,Incomplete]
[22:19] <arges> skoe_: ok
[22:20] <arges> i'll point this at somebody who knows more about skylake patches
[22:21] <skoe_> Seems like it times out first (...probe error...) and gets a spurious response later (0x14f150f4).
[22:22] <skoe_> The same magic number is in the patch for this codec. Seems to be its ID. (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1454656)
[22:22] <ubot5> Launchpad bug 1454656 in HWE Next "Add support for Conexant codecs CX20721, CX20722, CX20723 and CX20724" [Undecided,Fix committed]
[22:22] <skoe_> Yeah, thanks. I'll stay here and see what happens :)
[22:24] <arges> skoe_: feel free to ping people here next week about it. good luck
[22:25] <skoe_> Thanks, I will