Bug 716655

Summary: X no longer starts after kernel update: [drm] nouveau 0000:02:00.0: PFIFO_BAR_FAULT - VM: Trapped write at 00011b88b0 status 00001426 channel 0 (0x00000040)
Product: [Fedora] Fedora Reporter: Noel Duffy <noelduffy>
Component: xorg-x11-drv-nouveauAssignee: Ben Skeggs <bskeggs>
Status: CLOSED CANTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: unspecified    
Version: 14CC: airlied, ajax, bskeggs, elad
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-06-26 08:06:33 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Noel Duffy 2011-06-26 04:48:24 UTC 
Description of problem:

I updated Fedora 14 today to 2.6.35.13-92.fc14.x86_64. After rebooting, X would no longer start and I am instead presented with a blank black screen. Dozens of these messages are written to /var/log/messages every second:

Jun 26 16:22:25 pariah kernel: [ 1685.571017] [drm] nouveau 0000:02:00.0: PFIFO_BAR_FAULT - VM: Trapped write at 00011af8b0 status 00001426 channel 0 (0x00000040)

dmesg shows the same message. Nothing else is being logged.

Version-Release number of selected component (if applicable):

xorg-x11-drv-nouveau-0.0.16-11.20100826git065576d.fc14.x86_64

How reproducible:

X11 will not start at all. 

Additional info:

lspci -vvv shows this for the video card:

02:00.0 VGA compatible controller: nVidia Corporation C79 [GeForce G102M] (rev b1) (prog-if 00 [VGA controller])
	Subsystem: ASUSTeK Computer Inc. Device 19b4
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0, Cache Line Size: 64 bytes
	Interrupt: pin A routed to IRQ 23
	Region 0: Memory at fb000000 (32-bit, non-prefetchable) [size=16M]
	Region 1: Memory at e0000000 (64-bit, prefetchable) [size=256M]
	Region 3: Memory at f8000000 (64-bit, prefetchable) [size=32M]
	Region 5: I/O ports at dc00 [size=128]
	Expansion ROM at fafe0000 [disabled] [size=128K]
	Capabilities: [60] Power Management version 2
		Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
		Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
	Capabilities: [68] MSI: Enable- Count=1/1 Maskable- 64bit+
		Address: 0000000000000000  Data: 0000
	Kernel driver in use: nouveau
	Kernel modules: nouveau, nvidiafb

The laptop is an Asus K40IN.

Nothing obvious appears in /var/log/Xorg.0.log. Nothing is logged with either EE or WW, or indeed anything at all other than messages marked with ** or II.

This is what appears during boot for nouveau:

Jun 26 15:46:37 pariah kernel: [    1.577287] ACPI: Video Device [IGPU] (multi-head: yes  rom: no  post: no)
Jun 26 15:46:37 pariah kernel: [    1.595686] [drm] Initialized drm 1.1.0 20060810
Jun 26 15:46:37 pariah kernel: [    1.624767] ACPI: PCI Interrupt Link [SGRU] enabled at IRQ 23
Jun 26 15:46:37 pariah kernel: [    1.624775] nouveau 0000:02:00.0: PCI INT A -> Link[SGRU] -> GSI 23 (level, low) -> IRQ 23
Jun 26 15:46:37 pariah kernel: [    1.629295] [drm] nouveau 0000:02:00.0: Detected an NV50 generation card (0x0ac980b1)
Jun 26 15:46:37 pariah kernel: [    1.634312] [drm] nouveau 0000:02:00.0: Attempting to load BIOS image from PRAMIN
Jun 26 15:46:37 pariah kernel: [    1.696309] [drm] nouveau 0000:02:00.0: ... appears to be valid
Jun 26 15:46:37 pariah kernel: [    1.696313] [drm] nouveau 0000:02:00.0: BIT BIOS found
Jun 26 15:46:37 pariah kernel: [    1.696316] [drm] nouveau 0000:02:00.0: Bios version 62.79.71.00
Jun 26 15:46:37 pariah kernel: [    1.696319] [drm] nouveau 0000:02:00.0: TMDS table version 2.0
Jun 26 15:46:37 pariah kernel: [    1.696322] [drm] nouveau 0000:02:00.0: Found Display Configuration Block version 4.0
Jun 26 15:46:37 pariah kernel: [    1.696326] [drm] nouveau 0000:02:00.0: Raw DCB entry 0: 01000323 00010034
Jun 26 15:46:37 pariah kernel: [    1.696328] [drm] nouveau 0000:02:00.0: Raw DCB entry 1: 02011300 0000001e
Jun 26 15:46:37 pariah kernel: [    1.696331] [drm] nouveau 0000:02:00.0: Raw DCB entry 2: 0000000e 00000000
Jun 26 15:46:37 pariah kernel: [    1.696335] [drm] nouveau 0000:02:00.0: DCB connector table: VHER 0x40 5 16 4
Jun 26 15:46:37 pariah kernel: [    1.696338] [drm] nouveau 0000:02:00.0:   0: 0x00000040: type 0x40 idx 0 tag 0xff
Jun 26 15:46:37 pariah kernel: [    1.696341] [drm] nouveau 0000:02:00.0:   1: 0x00000100: type 0x00 idx 1 tag 0xff
Jun 26 15:46:37 pariah kernel: [    1.696345] [drm] nouveau 0000:02:00.0: Parsing VBIOS init table 0 at offset 0xDD76
Jun 26 15:46:37 pariah kernel: [    1.696685] elantech: assuming hardware version 2, firmware version 4.1.1
Jun 26 15:46:37 pariah kernel: [    1.732633] elantech: Synaptics capabilities query result 0x7e, 0x13, 0x0d.
Jun 26 15:46:37 pariah kernel: [    1.782321] [drm] nouveau 0000:02:00.0: Parsing VBIOS init table 1 at offset 0xE04E
Jun 26 15:46:37 pariah kernel: [    1.782324] [drm] nouveau 0000:02:00.0: Parsing VBIOS init table 2 at offset 0xE050
Jun 26 15:46:37 pariah kernel: [    1.782331] [drm] nouveau 0000:02:00.0: Parsing VBIOS init table 3 at offset 0xE111
Jun 26 15:46:37 pariah kernel: [    1.782339] [drm] nouveau 0000:02:00.0: Parsing VBIOS init table 4 at offset 0xE1D6
Jun 26 15:46:37 pariah kernel: [    1.782341] [drm] nouveau 0000:02:00.0: Parsing VBIOS init table at offset 0xE23B
Jun 26 15:46:37 pariah kernel: [    1.803283] [drm] nouveau 0000:02:00.0: 0xE23B: Condition still not met after 20ms, skipping following opcodes
Jun 26 15:46:37 pariah kernel: [    1.803295] [drm] nouveau 0000:02:00.0: Detected 512MiB VRAM
Jun 26 15:46:37 pariah kernel: [    1.803297] [drm] nouveau 0000:02:00.0: Stolen system memory at: 0x0120000000
Jun 26 15:46:37 pariah kernel: [    1.803384] [TTM] Zone  kernel: Available graphics memory: 2028464 kiB.
Jun 26 15:46:37 pariah kernel: [    1.803387] [TTM] Initializing pool allocator.
Jun 26 15:46:37 pariah kernel: [    1.803420] mtrr: type mismatch for e0000000,10000000 old: write-back new: write-combining
Jun 26 15:46:37 pariah kernel: [    1.824299] [drm] nouveau 0000:02:00.0: 512 MiB GART (aperture)
Jun 26 15:46:37 pariah kernel: [    1.828356] input: ETPS/2 Elantech Touchpad as /devices/platform/i8042/serio4/input/input7
Jun 26 15:46:37 pariah kernel: [    2.882697] [drm] nouveau 0000:02:00.0: Allocating FIFO number 1
Jun 26 15:46:37 pariah kernel: [    2.886077] [drm] nouveau 0000:02:00.0: nouveau_channel_alloc: initialised FIFO 1
Jun 26 15:46:37 pariah kernel: [    3.050959] [drm] nouveau 0000:02:00.0: allocated 1366x768 fb: 0x40250000, bo ffff880117dab400
Jun 26 15:46:37 pariah kernel: [    3.051016] fbcon: nouveaufb (fb0) is primary device
Jun 26 15:46:37 pariah kernel: [    3.056161] Console: switching to colour frame buffer device 170x48
Jun 26 15:46:37 pariah kernel: [    3.057621] fb0: nouveaufb frame buffer device
Jun 26 15:46:37 pariah kernel: [    3.057622] drm: registered panic notifier
Jun 26 15:46:37 pariah kernel: [    3.057626] Slow work thread pool: Starting up
Jun 26 15:46:37 pariah kernel: [    3.057705] Slow work thread pool: Ready
Jun 26 15:46:37 pariah kernel: [    3.057711] [drm] Initialized nouveau 0.0.16 20090420 for 0000:02:00.0 on minor 0
Jun 26 15:46:37 pariah kernel: [    3.080731] dracut: Starting plymouth daemon
Comment 1 Noel Duffy 2011-06-26 05:15:38 UTC 
I think that I have tracked down the cause of this problem. My laptop does not have an xorg.conf file in /etc/X11 normally. However, a few days ago I started livna-config-display to remind myself what it did. It reported an error about the proprietary nvidia driver being absent, so I clicked cancel and forgot about it. However, clicking cancel does not prevent it from writing an xorg.conf to /etc/X11 if one is not there. This xorg.conf lay quietly in /etc/X11 waiting for the next boot, at which time it caused havoc.

The xorg.conf it creates looks like this:


Section "Files"
        ModulePath   "/usr/lib64/xorg/modules"
EndSection

Section "ServerFlags"
        Option      "AIGLX" "on"
EndSection

Section "Device"
        Identifier  "Videocard0"
        Driver      "vesa"
EndSection

Section "Extensions"
        Option      "Composite" "Enable"
EndSection


When I removed this file and rebooted my laptop X11 started normally.

Arguably it is a bug in livna-config-display that it writes this xorg.conf when cancel is clicked. I have removed this program from my laptop.
Comment 2 Elad Alfassa 2011-06-26 08:06:33 UTC 
livna-config-display isn't in fedora, so please report a bug to livna-config-display upstream (rpmfusion I think).




-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers