Bug 200395 - nv04_timer_read() hangs a CPU
Summary: nv04_timer_read() hangs a CPU
Status: NEW
Alias: None
Product: Drivers
Classification: Unclassified
Component: Video(DRI - non Intel) (show other bugs)
Hardware: x86-64 Linux
: P1 normal
Assignee: drivers_video-dri
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-07-03 03:55 UTC by Thomas
Modified: 2018-07-03 17:40 UTC (History)
0 users

See Also:
Kernel Version: 4.17.4
Subsystem:
Regression: No
Bisected commit-id:


Attachments
dmesg output (74.21 KB, text/plain)
2018-07-03 03:55 UTC, Thomas
Details
4.17.4 dmesg output (70.84 KB, text/plain)
2018-07-03 17:40 UTC, Thomas
Details
Kernel .config (110.39 KB, text/x-mpsub)
2018-07-03 17:40 UTC, Thomas
Details

Description Thomas 2018-07-03 03:55:54 UTC
Created attachment 277145 [details]
dmesg output

Whenever I run "weston-launcher" from the Arch Linux repos the kernel hangs. As far as I can tell this is a nouveau issue. The official name of the offending GPU is "NVIDIA GeForce GTX 1060." Attached is the dmesg output right after I ran "weston-launcher"(getting it off that machine was not easy and involved a lot of rebooting). Unfortunately, the machine hangs when I do "lspci" or "lsusb". It seems to be an related if not the same issue. I do however have a working install of Microsoft Windows and can provide any hardware data collectible from Windows.
Comment 1 Thomas 2018-07-03 03:59:57 UTC
I forgot to add that there is also an integrated Intel GPU on the system.
Comment 2 Thomas 2018-07-03 04:04:38 UTC
It also hangs when I run X but interestingly not when I run swaywm.
Comment 3 Thomas 2018-07-03 17:39:30 UTC
I tested again with 4.17.4. Same behavior. I attached the new dmesg output and the kernel config.
Comment 4 Thomas 2018-07-03 17:40:21 UTC
Created attachment 277149 [details]
4.17.4 dmesg output
Comment 5 Thomas 2018-07-03 17:40:43 UTC
Created attachment 277151 [details]
Kernel .config

Note You need to log in before you can comment on or make changes to this bug.