[07:53] <smb> lamont, "ubuntu-bug linux" or you mean a full system dump? Btw, if your schedule allows maybe you could verify bug 1336253 against some real hw.
[07:53] <ubot5`> bug 1336253 in dahdi-linux (Ubuntu Utopic) "dahdi-dkms 1:2.5.0.1+dfsg-1ubuntu3: dahdi kernel module failed to build [xbus-sysfs.c:460:2: error: unknown field ‘drv_attrs’ specified in initializer]" [Medium,Fix committed] https://launchpad.net/bugs/1336253
[09:05] <apw> lamont, or are you saying it pops those stacks and stops dead so its not in syslog
=== tsimpson_ is now known as tsimpson
=== ubot5` is now known as ubot5
=== henrix_ is now known as henrix
[13:55] <lamont> apw: it was most likely temperature related - I have a photo of the stacktrace showing it in sym54c8xx_int calling credit_entropy_bits calling sym_interrupt and so on
[13:56] <lamont> smb: that box is running trusty :(
[13:56] <smb> lamont, there are new versions for P, T, and U. No excuse for being lazy :)
[13:57] <lamont> smb: cool.  it'll be tomorrow though.  pester me ?
[13:57] <smb> lamont, I love to pester people :)
[13:58]  * lamont needs to find an lm-sensors config for his lp1000r over lunch todya
[14:16] <lamont> smb: ii  dahdi-dkms                           1:2.5.0.1+dfsg-1ubuntu2             DAHDI telephony interface (dkms kernel driver)
[14:16] <lamont> that one? or a different one?
[14:16] <lamont> and how did I fix it to be happy, I wonder... nothing held on the box, and I have dahdi kernel drivers
[14:19] <smb> lamont, Yeah that one. Hm, not sure. I thought T did not work before... thoughcurrent in T would be ubuntu3 and pending ubuntu4
[14:20] <smb> But could be that T on T did work and the new version was for handling U on T
[14:20] <smb> But it has been more than two days since I messed around with those... I would need to refresh my memory
[14:21] <smb> Hm, now... not supposed to work in T... 
[14:21] <lamont> lsb_release -sc
[14:21] <lamont> precise
[14:21] <lamont> doh
[14:21] <smb> Ahhh
[14:21] <lamont> that's right - I reverted
[14:22] <smb> Yeah, that did work, but not the T HWE kernel which the proposed package should fix
[14:22] <lamont> oh. right.
[14:22] <lamont> I reinstalled precise because of other issues, and picked up the T HWE kernel, and reverted that kernel to the precise kernel
[14:22] <lamont> now I remember
[14:22] <smb> Unfortunately I uncovered later that we have another issue which I have to fix after this one. And that is that you need to do the dkms install while the right kernel runs
[14:23] <lamont> sounds like I just need to install the HWE kernel and see what breaks?  and I'll hope you fix that bug before tomorrow, then.
[14:24] <smb> lamont, I know how to fix it but was not sure it is allowed to upload another version while this one is still in proposed but I guess it would be ok as long as the changes has both updates
=== jpds is now known as Guest86457
[16:14] <jsalisbury> **
[16:14] <jsalisbury> ** Ubuntu Kernel Team Meeting - Today @ 17:00 UTC - #ubuntu-meeting
[16:14] <jsalisbury> **
[16:48] <henrix> AceLan: is it possible to have bug #838543 verified in Trusty ASAP?
[16:48] <ubot5> bug 838543 in gnome-settings-daemon (Ubuntu) "False battery warning +suspend" [Low,Confirmed] https://launchpad.net/bugs/838543
[16:54] <jsalisbury> ##
[16:54] <jsalisbury> ## Kernel team meeting in 5 minutes
[16:54] <jsalisbury> ##
=== jsalisbury changed the topic of #ubuntu-kernel to: Home: https://wiki.ubuntu.com/Kernel/ || Ubuntu Kernel Team Meeting - Tues December 16th, 2014 - 17:00 UTC || If you have a question just ask, and do wait around for an answer!  If the question is should I file a bug for something, likely you can assume yes.
[19:28] <lfrlucas> Hi. I installed kubuntu recently in a new desktop. When I logout from KDE, lightdm does not work anymore, and dmesg reports:
[19:28] <lfrlucas> INFO: task Xorg:1460 blocked for more than 120 seconds.
[19:28] <lfrlucas> [289202.586372]       Not tainted 3.13.0-40-generic #69-Ubuntu
[19:29] <lfrlucas> Could anyone help me?
[19:30] <lfrlucas> A call trace is also shown in dmesg
[19:30] <lfrlucas> Why is this happening
[19:32] <apw> lfrlucas, do file a bug, with the trace in it.  "ubuntu-bug linux" and let us know the bug number, then someone might have a better answer
[19:36] <lfrlucas> apw: Do know how can I kill the block xorg process? Try kill -9 but nothing happens.  Reboot is  the only solution?
[19:36] <apw> lfrlucas, yep, i would think if it has locked that hard, that is beyond saving
[19:38] <lfrlucas> ok