Intrepid: ATI driver crashes on Mobility Radeon 9600 (RV350)

Bug #294653 reported by Peter van der Spoel
18
Affects Status Importance Assigned to Milestone
xorg-server (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

After upgrading to Intrepid the ATI driver that comes with it fails to load. The xorg.log file even contains a stack trace (see attached files). Failsafe X is then started and after selecting 'Run Ubuntu in low-graphics mode' the xserver is coming up normally using the VESA driver.

Backtrace:
0: /usr/X11R6/bin/X(xf86SigHandler+0x79) [0x80c3009]
1: [0xb80a0400]
2: /usr/lib/xorg/modules/drivers//radeon_drv.so [0xb7b20b07]
3: /usr/lib/xorg/modules/drivers//radeon_drv.so [0xb7aee55a]
4: /usr/lib/xorg/modules/drivers//radeon_drv.so [0xb7af14fc]
5: /usr/X11R6/bin/X(InitOutput+0x96f) [0x80aac9f]
6: /usr/X11R6/bin/X(main+0x279) [0x8071b19]
7: /lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xe5) [0xb7ca7685]
8: /usr/X11R6/bin/X [0x8071101]
Saw signal 11. Server aborting.

[lspci]
00:00.0 Host bridge: Intel Corporation 82855PM Processor to I/O Controller (rev 03)
00:00.0 0600: 8086:3340 (rev 03)
    Subsystem: 103c:0890
    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
    Region 0: Memory at b0000000 (32-bit, prefetchable) [size=256M]
    Capabilities: <access denied>
    Kernel driver in use: agpgart-intel
    Kernel modules: intel-agp

01:00.0 VGA compatible controller: ATI Technologies Inc RV350 [Mobility Radeon 9600 M10]
01:00.0 0300: 1002:4e50
    Subsystem: 103c:0890
    Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
    Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
    Interrupt: pin A routed to IRQ 10
    Region 0: Memory at 98000000 (32-bit, prefetchable) [size=128M]
    Region 1: I/O ports at 2000 [size=256]
    Region 2: Memory at 90300000 (32-bit, non-prefetchable) [size=64K]
    [virtual] Expansion ROM at 90320000 [disabled] [size=128K]
    Capabilities: <access denied>
    Kernel modules: radeonfb

Revision history for this message
Peter van der Spoel (peter-vanderspoel-gmail) wrote :
Bryce Harrington (bryce)
description: updated
Revision history for this message
Bryce Harrington (bryce) wrote :

Please collect a full backtrace on this crash. See http://wiki.ubuntu.com/X/Backtracing for directions.

Changed in xorg:
status: New → Incomplete
Revision history for this message
exactt (giesbert) wrote :

same problem here. will attach gdb output.

Changed in xorg-server:
status: Incomplete → Confirmed
Revision history for this message
exactt (giesbert) wrote :

this is the first time doing this backtrace thingo. so forgive me if i did it the wrong way...

Revision history for this message
exactt (giesbert) wrote :
Revision history for this message
exactt (giesbert) wrote :
Revision history for this message
exactt (giesbert) wrote :
Revision history for this message
exactt (giesbert) wrote :
Revision history for this message
Tormod Volden (tormodvolden) wrote :

Peter, can you also install the debugging symbol packages and get a new backtrace please? That would confirm it really is the same issue. exactt, thanks for the gdb log.

Bryce Harrington (bryce)
Changed in xorg-server:
status: Confirmed → Incomplete
Revision history for this message
exactt (giesbert) wrote :

@Peter: Creating a debug log was really quite easy. It is straight forward following the wiki instructions. Please give it a try! Thx

@Tormod: Have you had a look at my debug logs? The problem exists and needs a fix be it the same problem as Peter's or not...

Revision history for this message
Tormod Volden (tormodvolden) wrote :

Can you please provide the output from:
 lsmod | grep radeon
and
 ls -l /dev/dri

Revision history for this message
exactt (giesbert) wrote :

after the x server crashed i switched to the console.

"lsmod | grep radeon" returned nothing
"ls -l /dev/dri" returned "insgesamt 0" (german for "overall 0" )

Revision history for this message
Tormod Volden (tormodvolden) wrote :

I checked your kern.log. You have fglrx modules installed... https://wiki.ubuntu.com/X/Troubleshooting/FglrxInteferesWithRadeonDriver

Revision history for this message
Eric Bauer (bauer-nricko) wrote :

Thank you for your help.
But, too long for me and my kinders. So I reinstall Ubuntu with the CD and the graphic card is OK. I just have problem with games on 3D accelerated config.

Revision history for this message
exactt (giesbert) wrote :

@Tormod: Thx a lot! Now it works. You just made somebody happy!

Revision history for this message
Tormod Volden (tormodvolden) wrote :

Great! I will close this bug, I suppose Peter had the same issue, otherwise he can reopen the bug.

Changed in xorg-server:
status: Incomplete → Invalid
Revision history for this message
Peter van der Spoel (peter-vanderspoel-gmail) wrote :

@Tormod: This was my problem as well it appears. After removing the fglrx modules I was able to startup correctly with the ati drivers.

Thanks a lot!!!

Changed in xorg-server:
status: Invalid → Confirmed
assignee: nobody → peter-vanderspoel-gmail
Changed in xorg-server:
assignee: peter-vanderspoel-gmail → nobody
status: Confirmed → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.