Bug 1027429 - GNOME Shell hangs with PFIFO DMA_PUSHER INVALID_CMD
Summary: GNOME Shell hangs with PFIFO DMA_PUSHER INVALID_CMD
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-drv-nouveau
Version: 19
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Ben Skeggs
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-11-06 19:45 UTC by Robert Hancock
Modified: 2015-02-17 19:06 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-02-17 19:06:19 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
FreeDesktop.org 70390 0 None None None Never

Description Robert Hancock 2013-11-06 19:45:07 UTC
Description of problem:
GNOME Shell sometimes hangs up and the error below is output in dmesg. I need to switch to another virtual terminal, log in and kill -9 the gnome-shell process.

Version-Release number of selected component (if applicable):
xorg-x11-drv-nouveau-1.0.9-1.fc19.x86_64

How reproducible:
At random

Steps to Reproduce:
1. Unsure
2.
3.

Actual results:
Display appears to hang and in dmesg:

nouveau E[   PFIFO][0000:01:00.0] DMA_PUSHER - ch 4 [gnome-shell[2148]] get 0x00201c923c put 0x00201cbb18 ib_get 0x000003c0 ib_put 0x000003c1 state 0x80000024 (err: INVALID_CMD) push 0x00406040

Expected results:
GNOME Shell doesn't hang

Additional info:

lspci for device:
01:00.0 VGA compatible controller: NVIDIA Corporation G98 [Quadro NVS 295] (rev a1)

bootup nouveau messages:
[    1.241060] nouveau  [  DEVICE][0000:01:00.0] BOOT0  : 0x298e80a2
[    1.241062] nouveau  [  DEVICE][0000:01:00.0] Chipset: G98 (NV98)
[    1.241063] nouveau  [  DEVICE][0000:01:00.0] Family : NV50
[    1.242933] nouveau  [   VBIOS][0000:01:00.0] checking PRAMIN for image...
[    1.298258] nouveau  [   VBIOS][0000:01:00.0] ... appears to be valid
[    1.298260] nouveau  [   VBIOS][0000:01:00.0] using image from PRAMIN
[    1.298330] nouveau  [   VBIOS][0000:01:00.0] BIT signature found
[    1.298332] nouveau  [   VBIOS][0000:01:00.0] version 62.98.75.00.08
[    1.318557] nouveau  [     PFB][0000:01:00.0] RAM type: GDDR3
[    1.318559] nouveau  [     PFB][0000:01:00.0] RAM size: 256 MiB
[    1.318560] nouveau  [     PFB][0000:01:00.0]    ZCOMP: 960 tags
[    1.343334] nouveau  [  PTHERM][0000:01:00.0] FAN control: none / external
[    1.343339] nouveau  [  PTHERM][0000:01:00.0] fan management: disabled
[    1.343341] nouveau  [  PTHERM][0000:01:00.0] internal sensor: yes
[    1.343500] [TTM] Zone  kernel: Available graphics memory: 8196256 kiB
[    1.343502] [TTM] Zone   dma32: Available graphics memory: 2097152 kiB
[    1.343502] [TTM] Initializing pool allocator
[    1.343505] [TTM] Initializing DMA pool allocator
[    1.343523] nouveau  [     DRM] VRAM: 256 MiB
[    1.343524] nouveau  [     DRM] GART: 1048576 MiB
[    1.343527] nouveau  [     DRM] TMDS table version 2.0
[    1.343528] nouveau  [     DRM] DCB version 4.0
[    1.343529] nouveau  [     DRM] DCB outp 00: 02000386 0f200010
[    1.343530] nouveau  [     DRM] DCB outp 01: 02000332 00020010
[    1.343531] nouveau  [     DRM] DCB outp 02: 040113a6 0f200010
[    1.343532] nouveau  [     DRM] DCB outp 03: 04011342 00020010
[    1.343533] nouveau  [     DRM] DCB conn 00: 00005046
[    1.343535] nouveau  [     DRM] DCB conn 01: 0000a146
[    1.354098] [drm] Supports vblank timestamp caching Rev 1 (10.10.2010).
[    1.354099] [drm] No driver support for vblank timestamp query.
[    1.354224] nouveau  [     DRM] 4 available performance level(s)
[    1.354226] nouveau  [     DRM] 0: core 275MHz shader 550MHz memory 100MHz voltage 900mV fanspeed 100%
[    1.354228] nouveau  [     DRM] 1: core 460MHz shader 920MHz memory 695MHz voltage 900mV fanspeed 100%
[    1.354229] nouveau  [     DRM] 2: core 460MHz shader 920MHz memory 695MHz voltage 900mV fanspeed 100%
[    1.354231] nouveau  [     DRM] 3: core 540MHz shader 1300MHz memory 695MHz voltage 1100mV fanspeed 100%
[    1.354232] nouveau  [     DRM] c: core 540MHz shader 1300MHz memory 702MHz
[    1.369040] nouveau  [     DRM] MM: using M2MF for buffer copies

Comment 1 Michal Schmidt 2014-03-05 14:17:57 UTC
(In reply to Robert Hancock from comment #0)
> nouveau E[   PFIFO][0000:01:00.0] DMA_PUSHER - ch 4 [gnome-shell[2148]] get
> 0x00201c923c put 0x00201cbb18 ib_get 0x000003c0 ib_put 0x000003c1 state
> 0x80000024 (err: INVALID_CMD) push 0x00406040

This looks like this upstream bugreport:
https://bugs.freedesktop.org/show_bug.cgi?id=70390

Comment 2 Fedora End Of Life 2015-01-09 20:29:53 UTC
This message is a notice that Fedora 19 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 19. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 19 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 3 Fedora End Of Life 2015-02-17 19:06:19 UTC
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.