From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 84771] New: nouveau MMIO read write FAULT HUB_INIT timed out errors
Date: Thu, 18 Sep 2014 06:30:11 +0000 [thread overview]
Message-ID: <bug-84771-2300@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=84771
Bug ID: 84771
Summary: nouveau MMIO read write FAULT HUB_INIT timed out
errors
Product: Drivers
Version: 2.5
Kernel Version: 3.17-rc4
Hardware: x86-64
OS: Linux
Tree: Mainline
Status: NEW
Severity: high
Priority: P1
Component: Video(DRI - non Intel)
Assignee: drivers_video-dri@kernel-bugs.osdl.org
Reporter: christtchin@gmail.com
Regression: No
Created attachment 150771
--> https://bugzilla.kernel.org/attachment.cgi?id=150771&action=edit
dmesg of regular boot + startx
Trying to run Arch Linux on a Lenovo Y400 with an nvidia GT750M graphics card.
When trying to boot the nouveau drivers consistently spit out multiple errors.
Computer continues the boot process. Errors also occur whenever I try to run
anything with hardware acceleration, such as Xorg. It is a similar output to
the one that occurs during boot: PBUS, PIBUS, and PGRAPH errors. Attached is a
dmesg log of a regular boot and startx.
Also a log of opening up Xorg: http://pastebin.com/w48Dx4qq
And a log of opening up weston: http://pastebin.com/1VPFgapP
--
You are receiving this mail because:
You are watching the assignee of the bug.
next reply other threads:[~2014-09-18 6:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-18 6:30 bugzilla-daemon [this message]
2014-09-18 6:41 ` [Bug 84771] nouveau MMIO read write FAULT HUB_INIT timed out errors bugzilla-daemon
2014-09-18 6:52 ` bugzilla-daemon
2014-12-18 9:18 ` bugzilla-daemon
2016-10-22 16:26 ` bugzilla-daemon
2016-10-22 16:49 ` 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-84771-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox