| mequarks_ | anyone: does freenode host a proper channel for ubuntu core ("snappy")? | 04:09 |
|---|---|---|
| === _ruben_ is now known as _ruben | ||
| greg_ | Howdy | 09:18 |
| greg_ | I see a lot of oopses when disconnecting my webcam with 16.04. Where can i report this and how ? | 09:20 |
| apw | greg_, as that is likely kernel related i would start by reporting a bug against the ubuntu kernel after the oopses have occured (run ubuntu-bug linux) | 09:42 |
| horms | I'm wondering if this is an appropriate place to ask about linux-stable patches being included in Ubuntu Kernels. In particular the 3.13.0 kernel for Trusty | 15:03 |
| apw | horms, ask away | 15:04 |
| horms | I have some PCI quirks and IDs added by patches which are in mainline since v4.5. I recently asked for them to be backported to linux-stable as far back as v3.10. Most of the relveant linux-stable maintainers have done so. I am now wondering if/how they might migrate into 3.13.0 for Trusty as this turns out to be a particuarly important kernel for the hardware in question. | 15:06 |
| rtg | horms, send a request for inclusion to kernel-team@lists.ubuntu.com | 15:07 |
| horms | ok, can do. thanks | 15:07 |
| apw | though i assume as we still seem to be pulling in stables for trusty that it would end up there at some point | 15:07 |
| horms | right, that was my assumption. sooner would certainly be better than later for us. | 15:08 |
| rtg | I can never remember what are the actively maintained stable kernel versions | 15:08 |
| apw | if we are going to expedite them before a stable is pulled we will need a bug against the kernel anyhow | 15:08 |
| apw | with the details in | 15:09 |
| horms | ok, i can file a bug if that is needed | 15:09 |
| horms | 3.13 is not maintained by mainline. 3.14 is eol. 3.12 and 3.16 are the closest releases to 3.13 that are maintained by mainline | 15:10 |
| rtg | horms, if the patch is already staged for stable, then directly requesting it likely won't get it published any sooner. | 15:10 |
| horms | ok | 15:11 |
| horms | that is fine | 15:11 |
| horms | i'm wondering if there is some way to predict when it might be pulled in from stable | 15:11 |
| rtg | horms, however, if 3.13 isn't maintained, then direct requests are the only way to get a patch included | 15:11 |
| horms | oh, ok | 15:11 |
| horms | that is clear enough | 15:11 |
| apw | isn't that the one debian is now maintaining ? | 15:11 |
| horms | I'm not clear on who is maintaining which mainline kernels | 15:12 |
| horms | (though i should probably make a list :) | 15:12 |
| rtg | horms, kernel.org has a list of stable and longterm kernel versions | 15:15 |
| horms | Yes, I am looking at it now. I just meant I wasn't sure who was maintaining each item on that list. | 15:15 |
| rtg | horms, all stable releases come through git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git | 15:16 |
| horms | Right. What I meant was that I believe different individuals are responsible for different branches of that tree. Greg KH does some. Jiri Slaby does or at one stage did another. I guess its not particularly important to this discussion. | 15:17 |
| horms | Thanks for answering my questions. I'll go ahead and arange a bug report and email request. | 15:22 |
| bdmurray | rtg: bug 1620525 seems to be about yakkety but you mentioned a xenial kernel version? | 18:38 |
| ubot5 | bug 1620525 in linux (Ubuntu Yakkety) "sbuild with overlayfs fails in yakkety" [Critical,Triaged] https://launchpad.net/bugs/1620525 | 18:38 |
| rtg | bdmurray, they are the same kernel, to date Xenial kernels are simply pocket copied to Yakkety. We have not migrated to 4.8 just yet. | 18:41 |
| bdmurray | rtg: okay, got it | 18:47 |
| === marga_ is now known as marga | ||
| elmo | hey - on a brand new laptop I'm getting MCE events due to the CPU getting too hot - this may be a dumb question - but is that in any way expected? | 20:19 |
| elmo | (it's a lenovo T460s, if it matters - running Ununtu 16.04) | 20:19 |
| elmo | Ununtu? Also, Ubuntu | 20:20 |
| stgraber | elmo: I'd very strongly recommend you run a kernel that's a bit more recent than 4.4 on a Skylake system | 20:21 |
| stgraber | elmo: I'm on the 4.6 kernel that briefly went into yakkety-proposed on mine and it's allowing the package to go into much deeper sleep states than the 4.4 kernel did | 20:22 |
| elmo | uh | 20:22 |
| elmo | OK | 20:22 |
| elmo | is there a 4.6 I can install on 16.04 easily? | 20:23 |
| elmo | also, not being funny, but if it's that bad, shouldn't we be fixing it for everyone? (I appreciate that may not easy) | 20:23 |
| stgraber | elmo: you may also want to update your firmware as they fixed a bunch of power management issues in there recently-ish | 20:23 |
| elmo | stgraber: does that require Windows? | 20:23 |
| stgraber | elmo: nope | 20:23 |
| elmo | OK - I'll look into that, thanks | 20:24 |
| rtg | elmo, you could also try lts-yakkety 4.8.0-8.9 in ppa:canonical-kernel-team/unstable | 20:24 |
| stgraber | elmo: grab the .iso from lenovo, run geteltorito against it, run losetup -a on the output, mount /dev/mapper/looopXYZ somewhere, and copy the content to a USB stick, then reboot and boot frrom it | 20:24 |
| stgraber | in my case I don't even bother with the USB stick and just copy the FLASH directory and the .EFI to /boot/efi and add a temporary boot entry with (efibootmgr), but that's because messing with EFI is easier for me than finding a usb stick :) | 20:25 |
| elmo | stgraber: thanks, that's super helpful and will avoid a lot of flailing | 20:25 |
| elmo | rtg: will do | 20:26 |
| stgraber | elmo: what MCE message do you see in dmesg? just going to grep on mine to see if I'm seeing anything like it | 20:26 |
| stgraber | rtg: I actually just grabbed that one and was going to give it a try, see what powertop thinks of it :) | 20:26 |
| elmo | stgraber: https://pastebin.canonical.com/165584/ | 20:27 |
| elmo | err, right, sorry this is a public channel | 20:27 |
| rtg | stgraber, its getting close to what we're gonna release. I'm just awaiting some apparmor bits from jjohansen | 20:27 |
| elmo | http://paste.ubuntu.com/23179449/ | 20:27 |
| rtg | we're still a couple of weeks from getting it into proposed | 20:27 |
| stgraber | elmo: hmm, so I'm still seeing this on the 4.6 kernel, though I've got events = 1 instead of events = 210, not sure that qualifies as much better though :) | 20:29 |
| stgraber | elmo: would also be interesting to know what's actually happening to the CPU, whether it was in non-turbo and got slammed or whether it was actually running at turbo speed and was just forced out of it because of heat | 20:31 |
| elmo | stgraber: hmm, I'd have to be watching htop/powertop at the time it fires to tell right? | 20:33 |
| stgraber | elmo: yeah, cking may have some magic script to log frequency changes in his crazy testsuites though. Otherwise, you'd need to watch cpuinfo or something to see what frequency it's running at... | 20:36 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!