All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 71659] New: [NVD9] Hangs under load with ![ PFIFO][0000:01:00.0] unhandled status 0x00800000
Date: Fri, 15 Nov 2013 20:14:42 +0000	[thread overview]
Message-ID: <bug-71659-8800@http.bugs.freedesktop.org/> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 2448 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=71659

          Priority: medium
            Bug ID: 71659
          Assignee: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
           Summary: [NVD9] Hangs under load with ![   PFIFO][0000:01:00.0]
                    unhandled status 0x00800000
        QA Contact: xorg-team-go0+a7rfsptAfugRpC6u6w@public.gmane.org
          Severity: normal
    Classification: Unclassified
                OS: Linux (All)
          Reporter: R.Palmer-mHdZ94l+r7K1Qrn1Bg8BZw@public.gmane.org
          Hardware: x86-64 (AMD64)
            Status: NEW
           Version: git
         Component: Driver/nouveau
           Product: xorg

With the Nouveau driver selected, my NVS 4200M/Ubuntu 13.10 system frequently
hangs when under heavy graphics load (flightgear usually triggers this within a
few minutes) and/or on battery power.  This does not happen with the nvidia-319
binary driver.

The mouse pointer continues to move at first, but often freezes later; the
keyboard LEDs do not react.  Sounds already playing continue until finished,
but no new ones start (i.e. applications are frozen).  Alt+SysRq works.

The kernel log always has the error
nouveau ![   PFIFO][0000:01:00.0] unhandled status 0x00800000
usually preceded by several instances of the warning
nouveau W[   PFIFO][0000:01:00.0] INTR 0x01000000: 0x00000005
and followed by a wide range of other errors.

This happens with both the default (3.11.0) kernel (Ubuntu bug
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1243557
) and the latest git kernel, with the default userspace (libdrm-nouveau
2.4.46/xserver-xorg-video-nouveau 1.0.9/mesa 9.2.1); the attached logs are with
the latter (crashes at Nov 15 18:05 and 18:42 in the kernel log, the Xorg log
is from the second of these).

With the latest git userspace (xorg/proto/dri3proto, mesa/drm, xcb/libxcb,
xorg/lib/libxshmfence, mesa/mesa, xorg/proto/presentproto, xcb/proto,
nouveau/xf86-video-nouveau), the system hangs on boot (at a correctly displayed
graphical splash screen), with Alt+SysRq not working and nothing recognisable
as an error in the logs.  I suspect this is due to an incompatible combination
of Ubuntu and latest-git (the recommended mesa/drm, nouveau/xf86-video-nouveau,
mesa/mesa wouldn't compile on its own, as it needs dri3 which isn't in Ubuntu
yet).

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

[-- Attachment #1.2: Type: text/html, Size: 3847 bytes --]

[-- Attachment #2: Type: text/plain, Size: 181 bytes --]

_______________________________________________
Nouveau mailing list
Nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
http://lists.freedesktop.org/mailman/listinfo/nouveau

             reply	other threads:[~2013-11-15 20:14 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-15 20:14 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
     [not found] ` <bug-71659-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2013-11-15 20:16   ` [Bug 71659] [NVD9] Hangs under load with ![ PFIFO][0000:01:00.0] unhandled status 0x00800000 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-11-15 20:16   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-11-15 20:19   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-11-15 20:20   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-11-15 20:29   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-11-18 18:54   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-11-18 18:54   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-11-18 18:59   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-11-18 23:46   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-11-27  5:06   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-01-09 21:25   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-01-09 21:34   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-01-10 20:39   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-01-10 20:49   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-01-13 23:08   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-01-15  3:40   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-01-15  9:28   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-01-15  9:34   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-01-15 19:20   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-01-15 19:25   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-03-30 11:45   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-03-30 11:46   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-03-30 11:53   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-06-29 21:58   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-07-22 20:28   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-07-22 20:29   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-07-22 23:12   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-11-20 22:47   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-11-20 22:52   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-11-22  4:27   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-11-23 10:46   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-12-02 22:18   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-01-12 21:27   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-01-22 14:18   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-02-01 23:37   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-02-11 11:41   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-12-04  8:40   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ

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-71659-8800@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon-cc+yj3umiyqdupfqwhejaq@public.gmane.org \
    --cc=nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.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.