From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 81391] nouveau E[ PFIFO][0000:01:00.0] read fault at 0x000020f000 [PTE] from BAR1/HOST_CPU on channel 0x00ffbdf000 [unknown]
Date: Wed, 30 Jul 2014 13:15:36 +0000 [thread overview]
Message-ID: <bug-81391-2300-mfVUCVfPtx@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-81391-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=81391
--- Comment #1 from Srihari Vijayaraghavan <linux.bug.reporting@gmail.com> ---
Created attachment 144741
--> https://bugzilla.kernel.org/attachment.cgi?id=144741&action=edit
lspci & .config
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2014-07-30 13:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-30 13:12 [Bug 81391] New: nouveau E[ PFIFO][0000:01:00.0] read fault at 0x000020f000 [PTE] from BAR1/HOST_CPU on channel 0x00ffbdf000 [unknown] bugzilla-daemon
2014-07-30 13:15 ` bugzilla-daemon [this message]
2014-07-30 13:21 ` [Bug 81391] " bugzilla-daemon
2014-10-12 1:15 ` 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-81391-2300-mfVUCVfPtx@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;
as well as URLs for NNTP newsgroup(s).