[Ubuntu-x-swat] [Bug 1248256] Re: [MacBookPro10, 1] Plugging in displayport monitor causes kworker to take 100% CPU

2014-04-05 Thread Dale Hamel
@page p make sure that you're modules match your kernel version. Don't mean to be condescending, but that's a common error. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-nouveau in Ubuntu.

[Ubuntu-x-swat] [Bug 1248256] Re: [MacBookPro10, 1] Plugging in displayport monitor causes kworker to take 100% CPU

2014-04-04 Thread Dale Hamel
This does not appear to be exclusive to the nouveau or xorg. I've been able to reproduce it at the console by plugging in display port without X11 running. I open htop, everything looks fine. Then I plug in the display port cable and the CPU immediately shoots up to 100%. I've also loaded the

[Ubuntu-x-swat] [Bug 1020221] Re: [Lenovo ThinkPad T510] Connecting an external Monitor over DisplayPort freezes the screen

2014-04-04 Thread Dale Hamel
This does not appear to be exclusive to the nouveau or xorg. I've been able to reproduce it at the console by plugging in display port without X11 running. I open htop, everything looks fine. Then I plug in the display port cable and the CPU immediately shoots up to 100%. I've also loaded the

[Ubuntu-x-swat] [Bug 1248256] Re: [MacBookPro10, 1] Plugging in displayport monitor causes kworker to take 100% CPU

2014-04-04 Thread Dale Hamel
Well I'd much prefer to use just a normal HDMI monitor, but i work at a Mac shop and i'm stuck with a cinema display... I guess the price of the cinema display might be inhibitive? How many people really buy macs to run linux on them? My guess is that this is why this bug is rated so low

[Ubuntu-x-swat] [Bug 1248256] Re: [MacBookPro10, 1] Plugging in displayport monitor causes kworker to take 100% CPU

2014-04-04 Thread Dale Hamel
Note: kworker/0:1 was found to have extremely CPU usage through ps -auxf: root 15854 50.0 0.0 0 0 ?R17:35 2:09 \_ [kworker/0:1] There are a number of other threads with similar output: kworker/0:3-1128 [000] d.s2 1973.688813: workqueue_queue_work: work

[Ubuntu-x-swat] [Bug 1248256] Re: [MacBookPro10, 1] Plugging in displayport monitor causes kworker to take 100% CPU

2014-04-04 Thread Dale Hamel
Progress: kworker/0:1-15854 [000] d.h4 1821.296727: workqueue_queue_work: work struct=819b1920 function=console_callback workqueue=88046d17ba00 req_cpu=32 cpu=0 kworker/0:1-15854 [000] d.h2 1821.302144: workqueue_queue_work: work struct=819b85e0

[Ubuntu-x-swat] [Bug 1248256] Re: [MacBookPro10, 1] Plugging in displayport monitor causes kworker to take 100% CPU

2014-04-04 Thread Dale Hamel
The code in question appears to be: http://lxr.free- electrons.com/source/drivers/gpu/drm/nouveau/nouveau_connector.c#L915 -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-nouveau in Ubuntu.

[Ubuntu-x-swat] [Bug 1248256] Re: [MacBookPro10, 1] Plugging in displayport monitor causes kworker to take 100% CPU

2014-04-04 Thread Dale Hamel
Though it's just a wrapper for: http://lxr.free- electrons.com/source/drivers/gpu/drm/drm_crtc_helper.c#L884 Theory: For some reason, it is constantly toggling between DRM_MODE_DPMS_ON for some reason. Maybe we should report this bug against nouveau and probably the intel drivers as they will

[Ubuntu-x-swat] [Bug 1248256] Re: [MacBookPro10, 1] Plugging in displayport monitor causes kworker to take 100% CPU

2014-04-04 Thread Dale Hamel
My (assumed) kernel trace: http://lxr.free- electrons.com/source/drivers/gpu/drm/nouveau/nv50_display.c#L2201 - attempts to create the display here: http://lxr.free-electrons.com/ident?i=nouveau_connector_create Later on in the function there is some display port related code... wonder if it

[Ubuntu-x-swat] [Bug 1248256] Re: [MacBookPro10, 1] Plugging in displayport monitor causes kworker to take 100% CPU

2014-04-04 Thread Dale Hamel
I've created this issue against nouveau kernel driver: https://bugs.freedesktop.org/show_bug.cgi?id=77073 ** Bug watch added: freedesktop.org Bugzilla #77073 https://bugs.freedesktop.org/show_bug.cgi?id=77073 -- You received this bug notification because you are a member of Ubuntu-X, which

[Ubuntu-x-swat] [Bug 1248256] Re: [MacBookPro10, 1] Plugging in displayport monitor causes kworker to take 100% CPU

2014-04-04 Thread Dale Hamel
Oohh!! Found something very interesting in this log: https://bugs.freedesktop.org/attachment.cgi?id=96925 drm:drm_helper_hpd_irq_event is being fired a lot, which is likely the cause of the kernel workers? -- You received this bug notification because you are a member of Ubuntu-X, which is

[Ubuntu-x-swat] [Bug 1248256] Re: [MacBookPro10, 1] Plugging in displayport monitor causes kworker to take 100% CPU

2014-04-04 Thread Dale Hamel
They pointed to this bug: https://bugs.freedesktop.org/show_bug.cgi?id=76732 ** Bug watch added: freedesktop.org Bugzilla #76732 https://bugs.freedesktop.org/show_bug.cgi?id=76732 -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to

[Ubuntu-x-swat] [Bug 1248256] Re: [MacBookPro10, 1] Plugging in displayport monitor causes kworker to take 100% CPU

2014-04-04 Thread Dale Hamel
The main thing I've been able to gleam is that the bug first appeared in 3.9, so I'm going to try rolling back to 3.8.13 (and earlier) to see if that resolves the issue. It would be awesome to be able to bisect the exact point when this issue was introduced. -- You received this bug notification

[Ubuntu-x-swat] [Bug 1020221] Re: [Lenovo ThinkPad T510] Connecting an external Monitor over DisplayPort freezes the screen

2014-04-04 Thread Dale Hamel
This should be closed as a duplicate of https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video- nouveau/+bug/1248256 -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-nouveau in Ubuntu.

[Ubuntu-x-swat] [Bug 1248256] Re: [MacBookPro10, 1] Plugging in displayport monitor causes kworker to take 100% CPU

2014-04-04 Thread Dale Hamel
Another possible (but hilarious fix) is to comment out a line as suggested here: https://bugs.freedesktop.org/show_bug.cgi?id=76732#c22 Haven't tried that one yet, but 3.8-rc6 should be clean as it is before 0a0afd282fd715dd63d64b243299a64da14f8e8d, which is the first bad commit. -- You

[Ubuntu-x-swat] [Bug 1248256] Re: [MacBookPro10, 1] Plugging in displayport monitor causes kworker to take 100% CPU

2014-04-04 Thread Dale Hamel
I can confirm 3.8-rc6 resolves this problem. So, if rolling back your kernel is an option I would suggest trying that. Otherwise, keep an eye on the upstream ticket. Hope all this helps guys! -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to

[Ubuntu-x-swat] [Bug 1248256] Re: [MacBookPro10, 1] Plugging in displayport monitor causes kworker to take 100% CPU

2014-04-04 Thread Dale Hamel
I should probably mention I'm not using ubuntu at all, I'm using gentoo, so it's a lot easier for me to switch around my kernel... -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-nouveau in Ubuntu.