=== JanC_ is now known as JanC
[08:10] <ivan> hmm, shouldn't 4.4.0-53 be in linux-xenial/master?
[08:12] <ivan> and master-next is only up to -52
[08:14] <ivan> http://kernel.ubuntu.com/git/ubuntu/ubuntu-xenial.git I mean
[12:56] <ivan> OK -53 is in the repo now :-)
[16:03] <stoatwblr> I have a bug with mptsas - ata erase (and secure) erase are failing. (The running kernel lacks CONFIG_IDE_TASK_IOCTL support for this device.) - works fine if the disk is plugged into the server's onboard sata ports, but that means having to go onsite to do this stuff.
[16:06] <stoatwblr> mpt3sas actually... :)
[16:12] <stoatwblr> hmmm. already fixed upstream.
[16:28] <stoatwblr> has the mpt3sas "Fix secure erase premature termination" (Nov 30th) been rolled into ubuntu-kernel yet?
[16:28] <stoatwblr>  commit 18f6084a989ba1b38702f9af37a2e4049a924be6 and 7ff723ad0f87
=== PaulW2U_ is now known as PaulW2U
[16:43] <stoatwblr> it would appear not. How can I request it. Doesn't seem to be a way of filing a bug in launchpad.
[17:21] <rtg> stoatwblr, https://bugs.launchpad.net/ubuntu/+filebug
[17:26] <stoatwblr> thanks
[17:26] <stoatwblr> just checking whether 4.8.0-30-generic might have had it added (Don't think so but always worth looking)
[17:59] <rtg> BenC, I've been meaning to ask you about powerpc64-emb. I had to temporarily disable that flavor in Zesty (v.9) because arch/powerpc/kernel/head_64.S fails to assemble within the CONFIG_PPC_BOOK3E blocks.
[18:00] <BenC> rtg: What kernel version is zesty at?
[18:00] <rtg> BenC, 4.9-rc8
[18:00] <BenC> Are you still adding any patches from E500/BOOK3E?
[18:01] <BenC> All of the patches that I once had added are no longer needed, so if there are any remnants, you can remove them.
[18:01] <BenC> If something still isn’t compiling, I’ll take a look at it now.
[18:01] <rtg> BenC, looks like that file at least is vanilla
[18:42] <dmj_s76> sforshee: So I've identified another issue relating to linux-firmware and (this time) kernel 4.8.  Bug incoming.  
[18:43] <ogra_> bjf, hmm, i wonder if you cant copy to the PPA because it is owned by snappy-dev and you are not a member ... want me to try the command to verify ?
[18:43] <dmj_s76> sforshee: It seems iwlwifi on kernel 4.8 doesn't work with the latest microcode (/lib/firmware/iwlwifi-8000C-22.ucode) under some circumstances.
[18:43] <bjf> ogra_, yes, please try
[18:44] <bjf> ogra_, henrix just pointed out to me that that ppa is over 100% full
[18:44] <dmj_s76> Now my guess is that a) -22 microcode is buggy or b) 4.8 requires patches to work correctly with it.
[18:46] <ogra_> bjf, hmm, doesnt work for me either 
[18:46] <ogra_> oh
[18:46] <ogra_> then the error is weird though 
[18:46] <ogra_> it shoould still find it 
[18:46] <bjf> ogra_, indeed
[18:47] <dmj_s76> This has been reported online by users of many different distros.  In our case, the microcode causes kernel crashes when 64GB of RAM (4x16GB) is installed in a certain laptop model, but not 48GB (3x16GB) or other less populated configurations.
[18:48] <dmj_s76> renaming the -22 ucode so things fallback to the -21 fixes things.
[18:49] <ogra_> bjf, oh man ... 
[18:49] <ogra_> bjf, "--to=~snappy-dev/ubuntu/snappy-devices" ... works 
[18:49] <bjf> oh
[18:49] <ogra_> do you want to try yourself or should i just confirm (it is sitting at y/N )
[18:50] <bjf> ogra_, yes, let me try
[18:50] <henrix> ogra_: ah, i actually tried with "--to=~snappy-dev/snappy-devices" and it failed too... i guess i was close :)
[18:50] <ogra_> probably best if you try 
[18:50] <ogra_> henrix, yeah :)
[18:51] <bjf> ogra_, "./copy-package --from ubuntu --from-suite vivid-updates --to=~ppa:snappy-dev/ubuntu/snappy-devices --to-suite vivid -b linux linux-meta linux-signed" fails for me
[18:51] <ogra_> whats the error ? 
[18:52] <bjf> AssertionError: No such archive: ~ppa:snappy-dev/ubuntu/snappy-devices
[18:52] <ogra_> no
[18:52] <ogra_> no tilde in front of ppa 
[18:52] <bjf> oh! i see what i did
[18:52] <ogra_> its either tilde or ppa:
[18:52] <ogra_> iirc they are kind of equivalent 
[18:52] <bjf> ogra_, it's working
[18:52] <ogra_> \o/
[18:53] <bjf> ogra_, done! no errors
[18:53] <ogra_> yay
[18:55] <henrix> bjf: what? with a ppa at 100%?  that's odd
[18:55] <bjf> henrix, what can i say .. i think it worked
[18:57] <ogra_> i definitely see the packages 
[19:01] <sforshee> dmj_s76: that's nice. Please file a bug, we need one for any SRU.
[19:01] <sforshee> dmj_s76: once you've filed the bug I'll spin another linux-firmware with that reverted.
[19:32] <dmj_s76> sforshee: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1647826
[19:32] <ubot5> Ubuntu bug 1647826 in linux-firmware (Ubuntu) "intel 8260 doesn't work with linux kernel 4.8 when using ucode version 22" [Undecided,New]
[19:56] <sforshee> dmj_s76: sounds like we'll need this in yakkety and xenial, right? Do you know if the problems go away with a 4.9 kernel?
[19:57] <dmj_s76> sforshee: I haven't tested 4.9 yet
[19:57] <dmj_s76> Yakkety should be the priority for now, but xenial will need it by the next point release.
[20:01] <sforshee> dmj_s76: if you get a chance it would be nice to know about 4.9. We've got a 4.9 build in zesty-proposed.
[20:05] <sforshee> dmj_s76: do you have any idea whether or not there are similar issues with the other -22 firmwares?
[20:06] <dmj_s76> sforshee: I don't know how the other -22 firmwares behave.  We only ship a limited subset of wifi cards known to work well (except when bugs like this happen)
[20:20] <sforshee> dmj_s76: do you have links to the other reports of this problem? I'm trying to determine if we need to revert the -22 ucode completely or just the one
[20:24] <dmj_s76> sforshee: 
[20:24] <dmj_s76> https://bugs.launchpad.net/hplip/+bug/1635898
[20:24] <dmj_s76> https://bugs.archlinux.org/task/51271
[20:24] <dmj_s76> http://askubuntu.com/questions/856028/how-to-get-wifi-working-on-ubuntu-16-10
[20:24] <dmj_s76> https://www.danernielsen.com/getting-intel-wireless-8260-to-work-on-ubuntu-16-10/
[20:24] <ubot5> Ubuntu bug 1635898 in HPLIP "16.10 wireless off" [Undecided,Invalid]
[20:24] <dmj_s76> The reporter of that ubuntu bug is clearly hitting this same issue but doesn't know how to categorize it.
[20:33] <sforshee> dmj_s76: thanks. Between that and my own searching all the cases I see where the -22 ucode was clearly to blame were with 8260, so I guess I'll only remove that one.
[20:52] <dmj_s76> sforshee: still an issue on 4.9
[20:54] <sforshee> dmj_s76: thanks
[21:06] <sforshee> dmj_s76: posted a test build to the bug