dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 81391] New: 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:12:17 +0000	[thread overview]
Message-ID: <bug-81391-2300@https.bugzilla.kernel.org/> (raw)

https://bugzilla.kernel.org/show_bug.cgi?id=81391

            Bug ID: 81391
           Summary: nouveau E[   PFIFO][0000:01:00.0] read fault at
                    0x000020f000 [PTE] from BAR1/HOST_CPU on channel
                    0x00ffbdf000 [unknown]
           Product: Drivers
           Version: 2.5
    Kernel Version: 3.16.0-rc7
          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: linux.bug.reporting@gmail.com
        Regression: No

Created attachment 144731
  --> https://bugzilla.kernel.org/attachment.cgi?id=144731&action=edit
kernel boot up messages extracted from syslog (/var/log/messages)

The error message displayed on the subject line floods the kernel log buffer:
nouveau E[   PFIFO][0000:01:00.0] read fault at 0x000020f000 [PTE] from
BAR1/HOST_CPU on channel 0x00ffbdf000 [unknown]
...
[   33.807019] systemd-journald[550]: /dev/kmsg buffer overrun, some messages
lost.

All of the useful messages I could extract out of syslog (/var/log/messages)
based on the kernel boot up time stamp is attached to this report.

I've also provided lspci -vvv & my .config as well.

I was however pleasantly surprised that the X.org & KDE did come up & appear to
be functioning fine, even including glxgears running smoothly as well.

Thank you for progressing Nouveau so far, so quickly & so nicely. And am happy
to test any patch you may want me to.

-- 
You are receiving this mail because:
You are watching the assignee of the bug.

             reply	other threads:[~2014-07-30 13:12 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-30 13:12 bugzilla-daemon [this message]
2014-07-30 13:15 ` [Bug 81391] 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:21 ` 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@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