search for: nouveau_connector_hotplug_work

...ff88046d17ba00 req_cpu=0 cpu=0 kworker/0:3-1128 [000] d.h2 1973.704711: workqueue_queue_work: work struct=ffffffff819b85e0 function=push_to_pool workqueue=ffff88046d17ba00 req_cpu=32 cpu=0 kworker/0:3-1128 [000] d.h3 1973.757128: workqueue_queue_work: work struct=ffff88045db116e0 function=nouveau_connector_hotplug_work workqueue=ffff88046d17ba00 req_cpu=32 cpu=0 kworker/0:3-1128 [000] d.h3 1973.830281: workqueue_queue_work: work struct=ffff88045db116e0 function=nouveau_connector_hotplug_work workqueue=ffff88046d17ba00 req_cpu=32 cpu=0 kworker/0:3-1128 [000] d.s3 1973.838757: workqueue_queue_work: work s...

...Product: xorg Loading the nouveau driver leads to a kworker constantly using 100% of a CPU core. PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 211 root 20 0 0 0 0 R 100.0 0.0 2:51.00 kworker/1:1 Powertop suggests the problem comes from nouveau_connector_hotplug_work. I noticed this problem first occurred in kernel 3.9 and still persists in 3.14 rc8. In kernel 3.8 the problem did not occur. Some time ago, trying to figure out the cause, i also tried a kernel bisect. git bisect start # bad: [c1be5a5b1b355d40e6cf79cc979eb66dafa24ad1] Linux 3.9 git bisect bad c...

On Mon, Apr 20, 2015 at 11:03:43AM -0400, Martes wrote: > Tasks: 272 total, 2 running, 270 sleeping, 0 stopped, 0 zombie > %Cpu(s): 7.1 us, 18.3 sy, 0.0 ni, 73.8 id, 0.7 wa, 0.0 hi, 0.1 si, 0.0 st > KiB Mem : 32679644 total, 402520 free, 9889728 used, 22387396 buff/cache > KiB Swap: 0 total, 0 free, 0 used. 21951812 avail Mem > > PID USER

https://bugs.freedesktop.org/show_bug.cgi?id=76475 Priority: medium Bug ID: 76475 Assignee: nouveau at lists.freedesktop.org Summary: Nouveau fails to load due to unknown opcode 0x80 QA Contact: xorg-team at lists.x.org Severity: normal Classification: Unclassified OS: Linux (All) Reporter: patrick.clara at

This series was originally motivated by a deadlock, introduced in commit 1d7c71a3e2f77336df536855b0efd2dc5bdeb41b 'drm/nouveau/disp: port vblank handling to event interface', due to inverted lock order between nouveau_drm_vblank_enable() and nouveau_drm_vblank_handler() (the complete lockdep report is included in the patch 4/5 changelog). Because this series fixes the vblank event