=== ikonia_ is now known as ikonia
[10:40] <binBASH> Hi all could anyone look into https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1318551 please? There seems to be an issue with CONFIG_SCHED_AUTOGROUP causing system bootup to fail mostly with kernel panic
[10:40] <ubot2`> Ubuntu bug 1318551 in linux "Kernel Panic - not syncing: An NMI occurred, please see the Integrated Management Log for details." [High,Confirmed]
[10:40] <ubot5> Ubuntu bug 1318551 in linux (Ubuntu) "Kernel Panic - not syncing: An NMI occurred, please see the Integrated Management Log for details." [High,Confirmed]
[10:49] <mnencia> binBASH: sometime with kernel panic, sometime not, but the system become so slow that it cannot even spawn a process
[10:49] <binBASH> mnencia: yup
[11:26] <apw> binBASH, this seems to be the -release pocket kerenl, ie not upgraded ?
[11:26] <apw>  [203930.174171] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 3.13.0-24-generic #46-Ubuntu
[11:27] <apw> does this occur with the latest kernel in -updates ?
[11:44] <binBASH> apw: tested it also with some of the nightly kernel builds from 3.15.x series, happens there also
[11:44] <apw> binBASH, is there an older kernle which did not show this issue?
[11:45] <apw> binBASH, did we try the latest 3.13 though?  that has a heap of stable updates on it
[11:46] <apw> from anywhere up to 3.17
=== yp is now known as ypwong
[11:51] <binBASH> apw: The only thing I got currently to answer this is kernel installation history => http://pastebin.com/raw.php?i=bxqAtDaN and yes I think it didn't appear on 3.11
=== tsimpson_ is now known as tsimpson
[11:54] <apw> binBASH, ok add that info to the bug, as it was introduced quite recent, a gross bisect would be the first step, to test with the mainline kernels between 3.11 and 3.13
[11:54] <apw> ie confirm it as in v3.13 and not in v3.11.<latest>
=== ubot5` is now known as ubot5
[11:54] <apw> and then test v3.12.<latest>
[11:59] <apw> get what you can test into the bug, and we can drive it from there
[14:05] <kirkland> hey team -- I'm having a bunch of problems with USB on an Intel NUC where I just installed Utopic
[14:05] <kirkland> actually, I've been working with jsalisbury on some regressions on the Trusty updates kernel, which seems to be going in the wrong direction, on the same hardware, with respect to USB
=== halfie_ is now known as halfie
=== halfie is now known as 1JTAABIAE
[14:58] <apw> kirkland, bug #?
[14:59] <kirkland> apw: I suspect it's part of or related to Bug #1350480
[14:59] <ubot2`> Launchpad bug 1350480 in linux "[REGRESSION] Kernel update renders Intel NUC (i5-3427) unbootable with USB devices plugged in" [High,In progress] https://launchpad.net/bugs/1350480
[14:59] <ubot5> bug 1350480 in linux (Ubuntu Utopic) "[REGRESSION] Kernel update renders Intel NUC (i5-3427) unbootable with USB devices plugged in" [High,In progress] https://launchpad.net/bugs/1350480
[15:01] <apw> kirkland, ok, the last thing in there was a test kernel with a proposed upstream fix applied, did that work ?
=== caribou_ is now known as caribou
=== FJKong_ is now known as FJKong_holiday
[16:51] <smoser> rtg, did i give information needed at https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1355196
[16:51] <ubot2`> Ubuntu bug 1355196 in linux "compiz fails with intel_do_flush_locked failed: Invalid argument" [High,Confirmed]
[16:51] <ubot5> Ubuntu bug 1355196 in linux (Ubuntu) "compiz fails with intel_do_flush_locked failed: Invalid argument" [High,Confirmed]
[17:30] <rtg> smoser, I've had some upgrade issues on a couple of laptops and found that a re-install worked just fine. how about booting a Live USB to see if that is your case ?
[17:30] <rtg> I had the same symptoms, e.g., blanks screen after lightdm login
[17:30] <smoser> that doesnt seem likely. i reprodue with the 'guest' user.
[17:30] <smoser> possibly it could be config in /etc/ somewhere i guess.
[17:32] <Sarvatt> i just updated the bug, seems like a problem on that whole generation of gpus on 3.16..
[17:32] <rtg> Sarvatt, is it a GM45 ?
[17:32] <Sarvatt> yup
[17:32] <rtg> ah, one of the old ones
[17:32] <Sarvatt> theres a fix in 3.17 thats cc:stable but its not in the queue yet
[17:33] <rtg> Sarvatt, I was googling this bug earlier today (got distracted), but noticed that patch.
[17:34] <rtg> Sarvatt, I think I saw it in the 3.16.x review pile, so it'll appear by about tomorrow in stable
[17:35] <Sarvatt> figured it woulda been in https://git.kernel.org/cgit/linux/kernel/git/stable/stable-queue.git/tree/queue-3.16
[17:36] <Sarvatt> yeah i dont see it in https://lkml.org/lkml/2014/9/3/918
[17:37] <Sarvatt> may want to manually pick it up, thats a pretty darn nasty bug
[17:37] <rtg> Sarvatt, already done
=== JanC_ is now known as JanC
[17:40] <rtg> smoser, I'm gonna upload today, so give 3.16.0-13.19 a try when it becomes available tomorrow.
[17:41] <Sarvatt> found a few dupes, its been busted since july, eww
[17:41] <rtg> Sarvatt, did you mark 'em as dupes against 1355196 ?
[17:42] <Sarvatt> yeah, figured you used that buglink
[17:42] <rtg> yup
[20:10] <BjoernC> ^^