/srv/irclogs.ubuntu.com/2016/01/15/#ubuntu-kernel.txt

xnox4.4 looks very juicy =001:30
tsimonq2phillw: well since i is usually every 3 point releases for Ubuntu, it's probably 4.502:43
phillwtsimonq2: I doubt 4.5 for an LTS... but, I'm happy to be proven wrong. 4.3 was the vote, as to if they sway to 4.4... I'm not too sure.02:46
tsimonq2phillw: where was this voted>02:50
phillwtsimonq2: read the mailing list. the kernel team do not 'vote', it is a technocracy just as the tech board are.02:52
mamarleyI asked in here just the other day and was told that 4.4 would be uploaded to Xenial "soon".03:00
phillwmamarley: I've no idea who told you that :)03:02
mamarleyLet me check...03:02
mamarley[11.01.16 13:14:44]  <apw> mamarley, yep, "soon" waiting on some dkms fallout to be resolved as much as anything03:03
mamarleyAfter I asked: "[11.01.16 13:13:55]  <mamarley> Xenial will eventually be getting 4.4, won't it?"03:03
phillwmamarley: The Ubuntu Linux kernel team has announced that the Linux kernel in Ubuntu 16.04 LTS has been upgraded to version 4.4, the latest stable release made available.03:04
phillwyou mean that annoucement :)03:04
phillwmamarley: this is pretty breaking news... http://news.softpedia.com/news/ubuntu-16-04-lts-now-based-on-linux-kernel-4-4-lts-498901.shtml03:05
mamarleyAccording to Launchpad, 4.4 hasn't been uploaded yet.  Softpedia isn't the most reliable news source...03:06
phillwmamarley: for the admins, this is a major head ache... Trust me. But, in the cycle we are just past alpha 1 testing and alpha 2 is not due until near end of month. It will be interesting to see if ubuntu actually take part in the alpha2 to test the kernel out.03:09
pkernHi. Did you hear anything about Haswell Intel machines being slow with current 3.19/4.2 kernels (on trusty, but that might not matter)? The problem is cores stuck to 450 MHz.10:14
apwpkern, don't think i have seen a specific result10:19
apws/result/report/g10:20
ckingpkern, not heard of any direct reports on this for Haswell10:23
ckingalthough I am aware of a few users seeing cpus getting stuck at a low freq allegedly because of a microcode update, but we've not figured out if this is a false report as yet10:24
g0g0boyhey all, I have a problem with an update scenario10:32
g0g0boyneed assistance10:32
g0g0boywas doing an apt-get update/upgrade and got an error: the following packages have unmet dependencies:10:33
apwg0g0boy, which packages10:34
g0g0boyrecomended I run apt-get -f install10:34
apwwhat series are you running ? do you have -proposed enabled ?10:34
g0g0boyone line is: linux-image-extra-4.2.0-23-generic : Depends: linux-image-4.2.0-23-generic but it is not installed10:35
g0g0boysecond line is: linux-image-generic : Depends: linux-image-4.2.0-23-generic but it is not installed10:35
TJ-g0g0boy: did you do "sudo apt-get dist-upgrade" ?10:35
g0g0boyI didn the apt-get -f install which tells me that I have no space in /boot :( forget to clean out my old kernels.10:35
TJ-g0g0boy: ahhh, first try "sudo apt-get autoremove". If that doesn't free up space then do "dpkg -l 'linux-image*' " and identify older kernel versions you no longer need10:36
g0g0boyTJ- same error10:36
g0g0boyTJ- same error again regarding depenacies10:37
apwyep you are in a hole an no mistake, you need to finish the install before it will do anything else10:37
g0g0boyI tried checking and deleting the old kernels to clear sapce but then get the depenacie error error  :(10:37
g0g0boygoing around in circles it seems10:37
apwyou might (as TJ- suggests) be able to request removal of an older kernel by hand10:37
apwg0g0boy, is /boot separate partition ?10:38
TJ-g0g0boy: once you've identified older versions you can remove them with "dpkg --remove linux-{image,headers}-<VERSION>" for each identified version10:38
apwg0g0boy, if so you could simply move the old kernel/initrds out of the way on to /, finish the install and then move htem back10:38
TJ-g0g0boy: once you've removed at least 1 older version there'll be space to fix with "apt-get -f install"10:38
g0g0boywill try usually use command: sudo apt-get purge -y linux-headers-xxxxxxx10:38
apwg0g0boy, likely you need to go under its view and use dpkg like TJ- suggests10:39
apwas apt knows things are going on10:39
apwand wnats to finish them first10:39
g0g0boyokay will try dpkg10:40
g0g0boywill let you know what happens, thanks for the suggestions10:40
g0g0boyso far looks like it is working  :)10:42
apwgood stuff, TJ- ^10:42
TJ-apw: we see that all the time - the default installer-created /boot/ is too small these days10:43
TJ-the pain-point is added to because there is no kernel image autoremove function, so GUI users esspecially don't know about autoremove10:44
apwTJ-, is there a bug filed to make that bigger, as it sounds like there should be10:46
apwTJ-, does it not also run autoremove the gui "install updates" i thought it did, which is why the kernles are now marked to keep just the last 310:47
TJ-hmm, well, unless something has changed very recently. We see this issue very frequently10:47
TJ-especially with broken boots after upgrades, due to an incomplete initrd.img10:48
g0g0boyTJ-, apw: no luck  :(10:48
TJ-g0g0boy: where are you at? have you removed some older kernel images?10:48
g0g0boyI was able to remove some items with dpkg --remove which I thought did something cleard out most of the linux-headers 10:48
apwheadres are not in /boot10:48
g0g0boyI stil lhave the following left10:48
TJ-g0g0boy: what does "df | grep boot" report?10:48
apwyou need to remove linux-image-* for older versions10:49
g0g0boy::::::/dev/sda1                     240972     240619         0 100% /boot10:49
g0g0boybrb10:49
g0g0boytry removing those also10:50
TJ-apw: this is the most relevant I can recall right now: bug 135709310:51
ubot5bug 1357093 in unattended-upgrades (Ubuntu) "Kernels not autoremoving, causing out of space error on LVM or Encrypted installation or on any installation, when /boot partition gets full" [Undecided,In progress] https://launchpad.net/bugs/135709310:51
g0g0boyconfirmed everything was removed now but still getting errors, come back to you shorlty, Im just reading through some of the output10:58
g0g0boyso I removed all linux-headers and linux-image-xxx so when I check for any kernels nothing appears11:02
g0g0boystill get error when doing apt-get upgrade or dist-upgrade11:02
g0g0boytry doing apt-get -f install and throws out a lot off output11:02
g0g0boyit appears to complain that it cannot find the old linux kernels11:03
TJ-g0g0boy: I'd recommend you /join #ubuntu since that is the correct support channel for these kind of issues11:03
g0g0boyI have the output just dunno where to post it for review11:03
g0g0boyLOL :( ok  :)11:04
g0g0boythanks anyways TJ-, apw11:04
TJ-g0g0boy: waiting for you there :)11:04
pkerncking: Urgh, that's a very good point.12:34
pkerncking: We did indeed push new microcode.12:34
ckingpkern, it would be useful to double check that. if you do find an issue with the microcode we can ping intel about it12:35
pkernBut we already did confirm that it doesn't happen with 3.13, fwiw. We found it with 3.19 and 4.2.12:36
apwpkern, presumably with the same firmware in place12:40
apw(and cpu firmware if loaded very early in initramfs)12:41
pkernYeah, we package it up and it's the same.12:41
apwi mean it was the same in each of the tests, 3.13 ok others not12:41
pkernIt was pretty clear that >3.13 used a different scaling method.12:44
ckingpkern, intel_pstate is now being used, is this specific to just one set of haswells?12:45
apwcking, that feels really familiar, some patch to make one specific model use something differnt in intel_pstate12:46
apw(perhaps it is tooo specific)12:46
ckingapw, b27580b05e6f5253228debc60b8ff4a786ff573a ("intel_pstate: Fix BYT frequency reporting") perhaps12:48
pkernSo I rebooted into 3.19 with the same firmware package installed and it's broken again. Now I can try to rollback the firmware.12:50
pkernThis is a Xeon E5-1650 v3.12:51
ckingpkern, sounds like https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/148034912:51
ubot5Launchpad bug 1480349 in intel-microcode (Ubuntu) "Intel Microcode Breaks frequency scaling in Xeon® E5-2687W v3 & E5-1650 v3" [High,Incomplete]12:51
pkernArgh. :) Thank you. I'll try rolling back the microcode update.12:52
ckingpkern, if it is, please add your findings to the bug and I will prod Intel again on this one12:53
pkernI'll try reverting to the trusty version.12:57
pkernYup, microcode.13:20
pkerncking: Ok, updated the bug. I theory I could try to bisect which microcode causes it, but still one'd need to raise it with Intel. \:13:29
ckingpkern, a bisect on the microcode would be useful if you can affort the time to do that13:30
ckingI'm contacting intel right now about it13:31
pkernI guess I could just try 0x2d on this processor and see what happens. Would fit date-wise.13:31
pkern(I have access to the errata but not when stuff got publically released, so I'd need to cross-ref multiple places.)13:32
ckingyep, 0x2d is a good start I think13:32
pkernOk, so 0x2b was actually even what the CPU was shipped with because there's no update in the package with that sig.13:38
ckingok, that's a good starting point13:40
dsmythiescking, pkern: Often CPU frequencies stuck low with the intel_pstate driver is due to somehow Clock Modulation being involved. You can test, by: 1 - disable the intel_pstate driver, as the acpi-cpufreq driver works fine with clock modulation; 2 - examine the Clock modulation MSR (0x19A) during the issue.14:51
dsmythiesapw,rtg: Re: A couple of days ago. Should I enter a bug report about the collateral damage due to the "depends on ZONE_DMA" issue? 11 devices are effected, all are sound cards. (reference: linux/sound/pci/Kconfig).14:56
apwdsmythies, yes please and paste the number here so we can find it in the deluge15:04
TJ-is there any guidance on when 4.4 will land for xenial? Been getting a few questions about testing it recently (I know it's only 5 days since release!) and I see the 4.4 tags in the repo15:09
manjortg, can you install gcc 4.9 in tangerine amd64 chroot ? 15:12
manjortg, the latest xenial gcc has bugs due to linaro merge 15:12
rtgmanjo, USE THE WILY CHROOT15:12
rtgoops15:13
manjortg, arm64 kernels don't boot .. yeah that is a good idea.. I will use wily 15:13
apwrtg, :)15:13
apwTJ-, we are in the last throws of getting the worst bits sorted, we are hoping "soon" like next week ish depending15:13
rtgTJ-, I've got a 4.4 kernel staged in unstable15:14
manjoapw, you like the yellin ?15:14
apw(ppa not debian unstable)15:14
apwmanjo, heh he only has one hand15:14
TJ-apw: thanks. that's 'sooner' than I expected. I'm running my own builds of v4.4 here, but had a few of the QA testers asking15:14
manjoapw, oops tmi ... 15:15
apwthey can get a preview in the ppa:canonical-kernel-team/ubuntu/unstable but its not supported15:15
apwas yet obviously15:15
apwmanjo, heh no not like that15:15
manjolol 15:15
pkernAfter having added the 0x2d microcode update my machine didn't even boot. Oh well.15:22
apwman15:27
dsmythiesapw, rtg: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/153464716:03
ubot5Launchpad bug 1534647 in linux (Ubuntu) "Collateral damage due to kernel configuration change enabling CONFIG_ZONE_DEVICE (Kernel 4.4 amd64)" [Undecided,New]16:03
apwrtg, ^16:03
apwoh you did that already16:03
apwrtg, i might look at that on monday if you haven't already16:03
rtgapw, I have not researched it yet, so feel free.16:04
rtgapw, I'm going through the bug list to see if there are some that apply to unstable, then I'll upload in a bit.16:05
apwsounds good16:05
rtggotta keep xnox happy16:05
apwhe does get antsy :)16:08
xnoxrtg, hm?! =)17:13
xnoxrtg, did you see my comment about CONFIG_KVM btw?17:13
* xnox checks bug mail and pulls latest kernel git changes17:14
rtgxnox, yes17:14
rtgonly applied to unstable though17:14
xnoxrtg, that's ok. no rush at the moment =)17:15
xnoxrtg, thanks.17:15
rtgapw, nm, update script is running amok17:16
rtgkamal, sforshee: I need to bounce tangerine and reinstall the xenial chroots17:17
sforsheertg: ack17:19
kamalrtg, ack17:19
rtgrebuilding xenial chroot on tangerine17:30
sil2100Hello! I recently merged a new ppp version from Debian and noticed that ppp is blocked in -proposed due to ppp-modules not being built for s390x17:58
sil2100Is there a reason for ppp-modules not being available for s390x ?17:58
rtgsil2100, checking...18:24
rtgsil2100, started bug #1534780 if you'd like to subscribe.18:47
ubot5bug 1534780 in linux (Ubuntu Xenial) "Xenial: review s390x module exclusions" [Undecided,In progress] https://launchpad.net/bugs/153478018:47
TJ-rtg: apw had a user testing 4.4.0-0.11 from unstable; getting PCI "unable to assign BAR" errors and resulting inoperable device. (4.3.0-5.16 was fine). Testing with "pci=realloc"18:51
sil2100rtg: thanks! :)18:58
rtgTJ- have them test vanilla mainline in order to make sure its not an Ubuntu patch causing the problem. http://kernel.ubuntu.com/~kernel-ppa/mainline/19:30
TJ-rtg: will do; there's been a long-standing (17 month) regression in the PCI bridge allocation code19:30
rtgTJ- have you narrowed it down to a committ ?19:31
TJ-I've been having to use mainline kernels with patches and I'm still waiting for YingHai Lu to get them into mainline. there's a mainline bug covering part of it at https://bugzilla.kernel.org/show_bug.cgi?id=8143119:31
ubot5bugzilla.kernel.org bug 81431 in PCI "pci=realloc fails to modify bridge windows, causing devices to fail BAR allocation" [High,New]19:31
TJ-rtg: right now the trouble is YingHai has a stack of patches because the rework is so invasive, and I don't think is focused on this stuff.19:32
rtggreat :(19:32
TJ-For v4.1 my issue only needed 2 patches from the stack, but now I need the entire stack19:32
apwbarf19:33
TJ-I'm currently pulling in git://git.kernel.org/pub/scm/linux/kernel/git/yinghai/linux-yinghai.git and the pci-for-v4.5-next19:33
TJ-I have to rework those patches to apply on 4.4 right now, though19:34
TJ-The user is 'phillw' and he's just posted the most recent kern.log (includes 4.4 and 4.3.x boots) here: http://phillw.net/kern.log19:36
phillwo/19:36
TJ-The line is "Jan 15 19:27:47 piglet kernel: [    0.687558] pci 0000:03:00.0: can't claim BAR 6 [mem 0xffff0000-0xffffffff pref]: no compatible bridge window"19:36
TJ-this is with "pci=realloc" too19:37
TJ-phillw: rtg suggests you test the upstream, mainline v4.4.0 build from http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.4-wily/19:38
TJ-phillw: did you notice, that last 4.4 boot doesn't have "assign-busses" ? I think you forgot to do "sudo update-grub" after changing /etc/default/grub 19:39
TJ-I need to head off to dinner now19:39
phillwTJ-: I'll do that now and reboot... I also want some food... it is 19:40 here and food time is about 17:00 :D19:40
phillwAs asked, I have issued sudo update-grub and WiFi still fails, logs are at http://phillw.net/kern.log20:01
TJ-phillw: one last config option to try adding, "nocrs"... as in "pci=realloc,assign-busses,nocrs" then "update-grub" then reboot test20:07
phillwTJ-: okies, can you hang on for a while, it is past 8pm here and I'm now cooking my meal I should have had at 6pm :)20:10
TJ-same here, and yes20:15
* tsimonq2 runs a generic kernel fresh out of Linus' git repo20:20
* phillw runs what ubuntu will be using... TJ- food cooked, rebooting with your extra command.20:34
phillwTJ-: file modified, still no WiFi, logs at http://phillw.net/kern.log20:47
TJ-phillw: that last 4.4 boot configured the wifi device correctly!20:49
TJ-as in, the 1 before this20:49
TJ-phillw: can you show me "dpkg -l 'linux-image*' | pastebinit"20:50
phillwTJ-: no, it did not. I have to reboot to 4.3 to have wifi20:52
TJ-Yes, it did. But, no driver module claimed it20:53
phillwokies.. just installing pastebinit20:53
phillwTJ-: http://paste.ubuntu.com/14510427/20:54
TJ-phillw: As I thought; your install didn't include "linux-image-extra-4.4.0-0-generic" which contains the ath9k and other drivers20:57
phillwTJ-: so an apt get should resolve it?20:58
phillwTJ-: we are about to find out :)21:00
phillwTJ-: Linux piglet 4.4.0-0-generic #11-Ubuntu SMP Mon Jan 11 16:58:35 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux21:04
TJ-phillw: so, that was why the wifi never came up even after the BAR assignment was fixed21:04
phillwso, it is add the ppa and then apt-get linux-image-extra-4.4.0-0-generic, which I assume will let apt know to grab the actual kernel as well :)21:05
TJ-phillw: if you check the dependency "apt-cache depends linux-image-extra-4.4.0-0-generic" that should pull in the -image- and the -headers-21:05
phillwphillw@piglet:~$ apt-cache depends linux-image-extra-4.4.0-0-generic21:06
phillwlinux-image-extra-4.4.0-0-generic21:06
phillw  Depends: linux-image-4.4.0-0-generic21:06
phillw |Depends: crda21:06
phillw    crda:i38621:06
phillw  Depends: wireless-crda21:06
phillwphillw@piglet:~$ 21:06
phillwyup :)21:06
phillwSo, add the ppa and then issue the image-extra apt to get the system?21:07
TJ-so asking for -extra- does the job. Usually, we have the meta-packages to pull in these dependencies21:08
phillwearly days, but the announcement is out and we do get asked!21:09
phillwTJ-:  Thanks ever so much for your patience on this. Bits I do recall from cycles ago, others are new to me. I'm happy to answer questions from any of our testers now.21:10
TJ-it would be a good test to remove (but save where you can reuse it) the pci=... additions, update-grub, and see if it works without those. I think you may need the pci=realloc but not the others, but you may get away without it, if the missing module was the core problem21:10
phillwTJ-: back to "" and it has booted fine :)21:18
phillwthese kernel modules wil be the death of us all :)21:19
TJ-LOL what a fuss!21:20
TJ-well, at least *you* aren't affected by the PCI bridge window issues then21:20
phillwindeed, just needed to ask for 'extra' and apt would have sorted it all out :D21:21
TJ-I must have missed in the logs where the initial BAR assignment failure was solved later on21:22
phillwI'll have a minion... oops, I mean volunteer, verify that adding the ppa and then the extra system results in a bootable system. tsimonq2 most likely has got 4.4 already, so I will need a volunteer without it installed on bare metal.21:24
phillwand you, as with all on here, are welcome to pop onto #phillw. We are an affable bunch and have testers willing to help out across various areas.21:25
tsimonq2phillw: no I compile directly from Linus' git repo21:39

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