[Ubuntu-x-swat] [Bug 1248256] Re: [MacBookPro10, 1] Plugging in displayport monitor causes kworker to take 100% CPU
@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. https://bugs.launchpad.net/bugs/1248256 Title: [MacBookPro10,1] Plugging in displayport monitor causes kworker to take 100% CPU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1248256/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1248256] Re: [MacBookPro10, 1] Plugging in displayport monitor causes kworker to take 100% CPU
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 intel driver (rebooting into macOS, selecting integrated driver and confirming it is running with vga_switcheroo once i reboot back into linux), and i get the exact same behavior. Note, booting with the displayport cable attached will cause the system to hang during initialization, I guess because the kworker takes 100% of the CPU. I've also had this happen with the proprietary nvidia driver loaded. This doesn't seem to have anything to do with the graphics driver, but rather the kernel itself is having a hard time with the thunderbolt port managing the display port connection. Oddly enough, this issue doesn't happen 100% of the time for me. I've had days where it didn't happen at all, and days where it is non stop. I'm running out of ideas on debugging this one, other than that the problem is almost certainly in the kernel itself, and is probably related to sketchy thunderbolt support since this never happens with just normal HDMI output. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/1248256 Title: [MacBookPro10,1] Plugging in displayport monitor causes kworker to take 100% CPU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1248256/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1020221] Re: [Lenovo ThinkPad T510] Connecting an external Monitor over DisplayPort freezes the screen
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 intel driver (rebooting into macOS, selecting integrated driver and confirming it is running with vga_switcheroo once i reboot back into linux), and i get the exact same behavior. Note, booting with the displayport cable attached will cause the system to hang during initialization, I guess because the kworker takes 100% of the CPU. I've also had this happen with the proprietary nvidia driver loaded. This doesn't seem to have anything to do with the graphics driver, but rather the kernel itself is having a hard time with the thunderbolt port managing the display port connection. Oddly enough, this issue doesn't happen 100% of the time for me. I've had days where it didn't happen at all, and days where it is non stop. I'm running out of ideas on debugging this one, other than that the problem is almost certainly in the kernel itself, and is probably related to sketchy thunderbolt support since this never happens with just normal HDMI output. Hide comment -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/1020221 Title: [Lenovo ThinkPad T510] Connecting an external Monitor over DisplayPort freezes the screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1020221/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1248256] Re: [MacBookPro10, 1] Plugging in displayport monitor causes kworker to take 100% CPU
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 here. I'm setting up a debug kernel to take a look at what is spawning the kworkers later tonight based on http://engineernabendu.blogspot.ca/2013/10/tracking-linux-kworker- threads.html but I'm getting close to tossing my hands up and buying an HDMI monitor myself... -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/1248256 Title: [MacBookPro10,1] Plugging in displayport monitor causes kworker to take 100% CPU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1248256/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1248256] Re: [MacBookPro10, 1] Plugging in displayport monitor causes kworker to take 100% CPU
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 struct=88046f2135d8 function=od_dbs_timer [cpufreq_ondemand] workqueue=88046d17ba00 req_cpu=0 cpu=0 kworker/0:3-1128 [000] d.h2 1973.704711: workqueue_queue_work: work struct=819b85e0 function=push_to_pool workqueue=88046d17ba00 req_cpu=32 cpu=0 kworker/0:3-1128 [000] d.h3 1973.757128: workqueue_queue_work: work struct=88045db116e0 function=nouveau_connector_hotplug_work workqueue=88046d17ba00 req_cpu=32 cpu=0 kworker/0:3-1128 [000] d.h3 1973.830281: workqueue_queue_work: work struct=88045db116e0 function=nouveau_connector_hotplug_work workqueue=88046d17ba00 req_cpu=32 cpu=0 kworker/0:3-1128 [000] d.s3 1973.838757: workqueue_queue_work: work struct=88046f2135d8 function=od_dbs_timer [cpufreq_ondemand] workqueue=88046d17ba00 req_cpu=0 cpu=0 kworker/0:3-1128 [000] d.h2 1973.859889: workqueue_queue_work: work struct=819b85e0 function=push_to_pool workqueue=88046d17ba00 req_cpu=32 cpu=0 kworker/0:3-1128 [000] d.h3 1973.903514: workqueue_queue_work: work struct=88045db116e0 function=nouveau_connector_hotplug_work workqueue=88046d17ba00 req_cpu=32 cpu=0 ^C The output is from: /sys/kernel/debug/tracing/trace_pipe It appears that the hotplug function is failing and being readded to the queue over and over again. Note that this output was obtained while the nouveau GPU was active via vga_switcheroo. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/1248256 Title: [MacBookPro10,1] Plugging in displayport monitor causes kworker to take 100% CPU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1248256/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1248256] Re: [MacBookPro10, 1] Plugging in displayport monitor causes kworker to take 100% CPU
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 function=push_to_pool workqueue=88046d17ba00 req_cpu=32 cpu=0 kworker/0:1-15854 [000] d.h3 1821.326482: workqueue_queue_work: work struct=88045db116e0 function=nouveau_connector_hotplug_work workqueue=88046d17ba00 req_cpu=32 cpu=0 kworker/0:1-15854 [000] d.s2 1821.326908: workqueue_queue_work: work struct=88046f2135d8 function=od_dbs_timer [cpufreq_ondemand] workqueue=88046d17ba00 req_cpu=0 cpu=0 kworker/0:1-15854 [000] d.h3 1821.399680: workqueue_queue_work: work struct=88045db116e0 function=nouveau_connector_hotplug_work workqueue=88046d17ba00 req_cpu=32 cpu=0 kworker/0:1-15854 [000] d.h3 1821.408694: workqueue_queue_work: work struct=819b1920 function=console_callback workqueue=88046d17ba00 req_cpu=32 cpu=0 kworker/0:1-15854 [000] d.h2 1821.451348: workqueue_queue_work: work struct=819b85e0 function=push_to_pool workqueue=88046d17ba00 req_cpu=32 cpu=0 kworker/0:1-15854 [000] d.s2 1821.466868: workqueue_queue_work: work struct=88046f20f010 function=vmstat_update workqueue=88046d17ba00 req_cpu=32 cpu=0 kworker/0:1-15854 [000] d.h3 1821.472866: workqueue_queue_work: work struct=88045db116e0 function=nouveau_connector_hotplug_work workqueue=88046d17ba00 req_cpu=32 cpu=0 kworker/0:1-15854 [000] d.s2 1821.476856: workqueue_queue_work: work struct=88046f2135d8 function=od_dbs_timer [cpufreq_ondemand] workqueue=88046d17ba00 req_cpu=0 cpu=0 kworker/0:1-15854 [000] d.h3 1821.545851: workqueue_queue_work: work struct=88045db116e0 function=nouveau_connector_hotplug_work workqueue=88046d17ba00 req_cpu=32 cpu=0 kworker/0:1-15854 [000] d.h3 1821.604354: workqueue_queue_work: work struct=819b85e0 function=push_to_pool workqueue=88046d17ba00 req_cpu=32 cpu=0 kworker/0:1-15854 [000] d.h3 1821.618864: workqueue_queue_work: work struct=88045db116e0 function=nouveau_connector_hotplug_work workqueue=88046d17ba00 req_cpu=32 cpu=0 kworker/0:1-15854 [000] d.s2 1821.626806: workqueue_queue_work: work struct=88046f2135d8 function=od_dbs_timer [cpufreq_ondemand] workqueue=88046d17ba00 req_cpu=0 cpu=0 kworker/0:1-15854 [000] d.h3 1821.691890: workqueue_queue_work: work struct=88045db116e0 function=nouveau_connector_hotplug_work workqueue=88046d17ba00 req_cpu=32 cpu=0 kworker/0:1-15854 [000] d.h2 1821.757689: workqueue_queue_work: work struct=819b85e0 function=push_to_pool workqueue=88046d17ba00 req_cpu=32 cpu=0 kworker/0:1-15854 [000] d.h3 1821.765032: workqueue_queue_work: work struct=88045db116e0 function=nouveau_connector_hotplug_work workqueue=88046d17ba00 req_cpu=32 cpu=0 kworker/0:1-15854 [000] d.s2 1821.766767: workqueue_queue_work: work struct=88046f2135d8 function=od_dbs_timer [cpufreq_ondemand] workqueue=88046d17ba00 req_cpu=0 cpu=0 kworker/0:1-15854 [000] d.h3 1821.838323: workqueue_queue_work: work struct=88045db116e0 function=nouveau_connector_hotplug_work workqueue=88046d17ba00 req_cpu=32 cpu=0 kworker/0:1-15854 [000] d.s2 1821.906723: workqueue_queue_work: work struct=81a1c5c0 function=neigh_periodic_work workqueue=88046d17b000 req_cpu=32 cpu=0 kworker/0:1-15854 [000] d.h2 1821.910760: workqueue_queue_work: work struct=819b85e0 function=push_to_pool workqueue=88046d17ba00 req_cpu=32 cpu=0 kworker/0:1-15854 [000] d.h3 1821.911437: workqueue_queue_work: work struct=88045db116e0 function=nouveau_connector_hotplug_work workqueue=88046d17ba00 req_cpu=32 cpu=0 kworker/0:1-15854 [000] d.s2 1821.916720: workqueue_queue_work: work struct=88046f2135d8 function=od_dbs_timer [cpufreq_ondemand] workqueue=88046d17ba00 req_cpu=0 cpu=0 kworker/0:1-15854 [000] d.h3 1821.984590: workqueue_queue_work: work struct=88045db116e0 function=nouveau_connector_hotplug_work workqueue=88046d17ba00 req_cpu=32 cpu=0 kworker/0:1-15854 [000] d.h3 1822.057517: workqueue_queue_work: work struct=88045db116e0 function=nouveau_connector_hotplug_work workqueue=88046d17ba00 req_cpu=32 cpu=0 kworker/0:1-15854 [000] d.h2 1822.064569: workqueue_queue_work: work struct=819b85e0 function=push_to_pool workqueue=88046d17ba00 req_cpu=32 cpu=0 kworker/0:1-15854 [000] d.s2 1822.066675: workqueue_queue_work: work struct=88046f2135d8 function=od_dbs_timer [cpufreq_ondemand] workqueue=88046d17ba00 req_cpu=0 cpu=0 kworker/0:1-15854 [000] d.h3 1822.130584: workqueue_queue_work: work struct=88045db116e0 function=nouveau_connector_hotplug_work
[Ubuntu-x-swat] [Bug 1248256] Re: [MacBookPro10, 1] Plugging in displayport monitor causes kworker to take 100% CPU
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. https://bugs.launchpad.net/bugs/1248256 Title: [MacBookPro10,1] Plugging in displayport monitor causes kworker to take 100% CPU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1248256/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1248256] Re: [MacBookPro10, 1] Plugging in displayport monitor causes kworker to take 100% CPU
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 likely have better connections to kernel developers. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/1248256 Title: [MacBookPro10,1] Plugging in displayport monitor causes kworker to take 100% CPU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1248256/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1248256] Re: [MacBookPro10, 1] Plugging in displayport monitor causes kworker to take 100% CPU
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 has anything to do with this. http://lxr.free- electrons.com/source/drivers/gpu/drm/nouveau/nv50_display.c#L1944 anyways, nouveau_connector_create is what is scheduling the job that keeps looping. I bet we could at least come up with a junk fix that will stop the loop (probably with hilarious unintentional consequences) -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/1248256 Title: [MacBookPro10,1] Plugging in displayport monitor causes kworker to take 100% CPU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1248256/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1248256] Re: [MacBookPro10, 1] Plugging in displayport monitor causes kworker to take 100% CPU
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 is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/1248256 Title: [MacBookPro10,1] Plugging in displayport monitor causes kworker to take 100% CPU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1248256/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1248256] Re: [MacBookPro10, 1] Plugging in displayport monitor causes kworker to take 100% CPU
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 subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/1248256 Title: [MacBookPro10,1] Plugging in displayport monitor causes kworker to take 100% CPU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1248256/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1248256] Re: [MacBookPro10, 1] Plugging in displayport monitor causes kworker to take 100% CPU
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 xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/1248256 Title: [MacBookPro10,1] Plugging in displayport monitor causes kworker to take 100% CPU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1248256/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1248256] Re: [MacBookPro10, 1] Plugging in displayport monitor causes kworker to take 100% CPU
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 because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/1248256 Title: [MacBookPro10,1] Plugging in displayport monitor causes kworker to take 100% CPU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1248256/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1020221] Re: [Lenovo ThinkPad T510] Connecting an external Monitor over DisplayPort freezes the screen
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. https://bugs.launchpad.net/bugs/1020221 Title: [Lenovo ThinkPad T510] Connecting an external Monitor over DisplayPort freezes the screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1020221/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1248256] Re: [MacBookPro10, 1] Plugging in displayport monitor causes kworker to take 100% CPU
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 received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/1248256 Title: [MacBookPro10,1] Plugging in displayport monitor causes kworker to take 100% CPU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1248256/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1248256] Re: [MacBookPro10, 1] Plugging in displayport monitor causes kworker to take 100% CPU
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 xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/1248256 Title: [MacBookPro10,1] Plugging in displayport monitor causes kworker to take 100% CPU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1248256/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1248256] Re: [MacBookPro10, 1] Plugging in displayport monitor causes kworker to take 100% CPU
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. https://bugs.launchpad.net/bugs/1248256 Title: [MacBookPro10,1] Plugging in displayport monitor causes kworker to take 100% CPU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1248256/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
