Bug 556538 - DMA protection error with libdrm_nouveau
Summary: DMA protection error with libdrm_nouveau
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 12
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-01-18 17:01 UTC by Jerry James
Modified: 2010-11-11 02:21 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-11-11 02:21:03 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Jerry James 2010-01-18 17:01:58 UTC
Description of problem:
I booted my computer this morning and got to the gdm screen.  I clicked on my username.  Normally, the user selector disappears and then the password entry box is drawn.  However, this time, the user selector disappeared and the password box did not appear.  I then discovered that, although the mouse pointer still moved, X was entirely unresponsive to both keypresses and mouse clicks.  I rebooted my machine, then found this in the tail of /var/log/messages from the failed boot:

Jan 18 09:13:13 153-10-10-10 kernel: [drm:drm_mode_rmfb] *ERROR* tried to remove a fb that we didn't own
Jan 18 09:13:13 153-10-10-10 kernel: [drm] nouveau 0000:04:00.0: Allocating FIFO number 2
Jan 18 09:13:13 153-10-10-10 kernel: [drm] nouveau 0000:04:00.0: nouveau_channel_alloc: initialised FIFO 2
Jan 18 09:13:13 153-10-10-10 kernel: [drm] TMDS-8: set mode 1920x1200 30
Jan 18 09:13:14 153-10-10-10 kernel: [drm] TMDS-10: set mode 1920x1200 31
Jan 18 09:13:23 153-10-10-10 kernel: [drm] nouveau 0000:04:00.0: PGRAPH_ERROR - nSource: PROTECTION_ERROR DMA_R_PROTECTION, nStatus:
Jan 18 09:13:23 153-10-10-10 kernel: [drm] nouveau 0000:04:00.0: PGRAPH_ERROR - Ch 2/4 Class 0x8297 Mthd 0x15e0 Data 0x00000000:0x00000000
Jan 18 09:13:23 153-10-10-10 kernel: [drm] nouveau 0000:04:00.0: magic set 1:
Jan 18 09:13:23 153-10-10-10 kernel: [drm] nouveau 0000:04:00.0:        0x00408900: 0x0000007e
Jan 18 09:13:23 153-10-10-10 kernel: [drm] nouveau 0000:04:00.0:        0x00408904: 0xf8725704
Jan 18 09:13:23 153-10-10-10 kernel: [drm] nouveau 0000:04:00.0:        0x00408908: 0xdad4a7bc
Jan 18 09:13:23 153-10-10-10 kernel: [drm] nouveau 0000:04:00.0:        0x0040890c: 0x8000d5f6
Jan 18 09:13:23 153-10-10-10 kernel: [drm] nouveau 0000:04:00.0:        0x00408910: 0x1fb8338c
Jan 18 09:13:23 153-10-10-10 kernel: [drm] nouveau 0000:04:00.0:        0x00408e08: 0x800a453e
Jan 18 09:13:23 153-10-10-10 kernel: [drm] nouveau 0000:04:00.0:        0x00408e0c: 0x00000000
Jan 18 09:13:23 153-10-10-10 kernel: [drm] nouveau 0000:04:00.0:        0x00408e10: 0xe419ffc0
Jan 18 09:13:23 153-10-10-10 kernel: [drm] nouveau 0000:04:00.0:        0x00408e14: 0x00000086
Jan 18 09:13:23 153-10-10-10 kernel: [drm] nouveau 0000:04:00.0:        0x00408e18: 0x02000410
Jan 18 09:13:23 153-10-10-10 kernel: [drm] nouveau 0000:04:00.0:        0x00408e1c: 0x9ae7dff0
Jan 18 09:13:23 153-10-10-10 kernel: [drm] nouveau 0000:04:00.0:        0x00408e20: 0x073d783f
Jan 18 09:13:23 153-10-10-10 kernel: [drm] nouveau 0000:04:00.0:        0x00408e24: 0x0e020206
Jan 18 09:13:23 153-10-10-10 kernel: [drm] nouveau 0000:04:00.0: magic set 2:
Jan 18 09:13:23 153-10-10-10 kernel: [drm] nouveau 0000:04:00.0:        0x00409900: 0x80000000
Jan 18 09:13:23 153-10-10-10 kernel: [drm] nouveau 0000:04:00.0:        0x00409904: 0x12f3373b
Jan 18 09:13:23 153-10-10-10 kernel: [drm] nouveau 0000:04:00.0:        0x00409908: 0xacc7fde7
Jan 18 09:13:23 153-10-10-10 kernel: [drm] nouveau 0000:04:00.0:        0x0040990c: 0x0000ff9f
Jan 18 09:13:23 153-10-10-10 kernel: [drm] nouveau 0000:04:00.0:        0x00409910: 0x6fff29a7
Jan 18 09:13:23 153-10-10-10 kernel: [drm] nouveau 0000:04:00.0:        0x00409e08: 0x800af420
Jan 18 09:13:23 153-10-10-10 kernel: [drm] nouveau 0000:04:00.0:        0x00409e0c: 0x00000000
Jan 18 09:13:23 153-10-10-10 kernel: [drm] nouveau 0000:04:00.0:        0x00409e10: 0x4eaf7f80
Jan 18 09:13:23 153-10-10-10 kernel: [drm] nouveau 0000:04:00.0:        0x00409e14: 0x000000be
Jan 18 09:13:23 153-10-10-10 kernel: [drm] nouveau 0000:04:00.0:        0x00409e18: 0x902400c8
Jan 18 09:13:23 153-10-10-10 kernel: [drm] nouveau 0000:04:00.0:        0x00409e1c: 0xbc44f082
Jan 18 09:13:23 153-10-10-10 kernel: [drm] nouveau 0000:04:00.0:        0x00409e20: 0x303c0d3f
Jan 18 09:13:23 153-10-10-10 kernel: [drm] nouveau 0000:04:00.0:        0x00409e24: 0x0b000208

The /var/log/Xorg.log from the failed boot is normal until after the modelines are printed, at which point it says:

[mi] EQ overflowing. The server is probably stuck in an infinite loop.

Backtrace:
0: /usr/bin/Xorg (xorg_backtrace+0x28) [0x49ea48]
1: /usr/bin/Xorg (mieqEnqueue+0x1f4) [0x49e414]
2: /usr/bin/Xorg (xf86PostMotionEventP+0xce) [0x478fae]
3: /usr/lib64/xorg/modules/input/evdev_drv.so (0x7fee72ef8000+0x516f) [0x7fee72efd16f]
4: /usr/bin/Xorg (0x400000+0x6bea7) [0x46bea7]
5: /usr/bin/Xorg (0x400000+0x116d53) [0x516d53]
6: /lib64/libpthread.so.0 (0x3e86a00000+0xf0f0) [0x3e86a0f0f0]
7: /lib64/libc.so.6 (ioctl+0x7) [0x3e85ed6937]
8: /usr/lib64/libdrm.so.2 (drmIoctl+0x23) [0x3ea20033b3]
9: /usr/lib64/libdrm.so.2 (drmCommandWrite+0x1b) [0x3ea200363b]
10: /usr/lib64/libdrm_nouveau.so.1 (0x7fee75553000+0x2e8d) [0x7fee75555e8d]
11: /usr/lib64/libdrm_nouveau.so.1 (nouveau_bo_map_range+0xfc) [0x7fee7555608c]
12: /usr/lib64/libdrm_nouveau.so.1 (0x7fee75553000+0x1e66) [0x7fee75554e66]
13: /usr/lib64/libdrm_nouveau.so.1 (nouveau_pushbuf_flush+0x29c) [0x7fee755551fc]
14: /usr/lib64/xorg/modules/drivers/nouveau_drv.so (0x7fee7577d000+0x3c0a9) [0x7fee757b90a9]
15: /usr/lib64/xorg/modules/drivers/nouveau_drv.so (0x7fee7577d000+0xd875) [0x7fee7578a875]
16: /usr/lib64/xorg/modules/libexa.so (0x7fee73339000+0x7d28) [0x7fee73340d28]
17: /usr/bin/Xorg (0x400000+0xd436c) [0x4d436c]
18: /usr/bin/Xorg (0x400000+0x2a3a9) [0x42a3a9]
19: /usr/bin/Xorg (0x400000+0x2c71c) [0x42c71c]
20: /usr/bin/Xorg (0x400000+0x21d5a) [0x421d5a]
21: /lib64/libc.so.6 (__libc_start_main+0xfd) [0x3e85e1eb1d]
22: /usr/bin/Xorg (0x400000+0x21909) [0x421909]

Version-Release number of selected component (if applicable):
libdrm-2.4.15-8.fc12.x86_64
xorg-x11-server-Xorg-1.7.4-1.fc12.x86_64
xorg-x11-drv-nouveau-0.0.15-18.20091105gite1c2efd.fc12.x86_64

How reproducible:
Not reproducible.  This is the first time this has happened.

Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:
Now that I am logged in successfully, I see that there is an xorg-x11-drv-nouveau update available.  I don't know if that can have anything to do with this crash, but I'll install it just in case.

Comment 1 Bug Zapper 2010-11-04 00:37:03 UTC
This message is a reminder that Fedora 12 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 12.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '12'.

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 prior to Fedora 12's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 12 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 please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

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.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 2 Jerry James 2010-11-11 02:21:03 UTC
I never saw this again.  With all the work on nouveau since then, let's assume this bug is gone.  I'll close it.


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