From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 200395] New: nv04_timer_read() hangs a CPU
Date: Tue, 03 Jul 2018 03:55:54 +0000 [thread overview]
Message-ID: <bug-200395-2300@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=200395
Bug ID: 200395
Summary: nv04_timer_read() hangs a CPU
Product: Drivers
Version: 2.5
Kernel Version: 4.17.3
Hardware: x86-64
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: Video(DRI - non Intel)
Assignee: drivers_video-dri@kernel-bugs.osdl.org
Reporter: be11f157cd19c4a2ba1e9c70a38b1a74@protonmail.com
Regression: No
Created attachment 277145
--> https://bugzilla.kernel.org/attachment.cgi?id=277145&action=edit
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.
--
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2018-07-03 3:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-03 3:55 bugzilla-daemon [this message]
2018-07-03 3:59 ` [Bug 200395] nv04_timer_read() hangs a CPU bugzilla-daemon
2018-07-03 4:04 ` bugzilla-daemon
2018-07-03 17:39 ` bugzilla-daemon
2018-07-03 17:40 ` bugzilla-daemon
2018-07-03 17:40 ` bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-200395-2300@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.