r350 freeze starting X with radeon driver

Bug #328531 reported by mezclatebrother!
2
Affects Status Importance Assigned to Milestone
xserver-xorg-video-ati (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Well, i'm the #326867 bug reporter. With the last xorg and radeon driver update, now freezes in white when the gdm login appears. I have attached the Xorg log (there is a SIGSEGV).

Ubuntu 9.04

xorg:
  Instalados: 1:7.4~5ubuntu12
  Candidato: 1:7.4~5ubuntu12
  Tabla de versión:
 *** 1:7.4~5ubuntu12 0

xserver-xorg-video-radeon:
  Instalados: 1:6.10.99.0-1ubuntu1
  Candidato: 1:6.10.99.0-1ubuntu1
  Tabla de versión:
 *** 1:6.10.99.0-1ubuntu1 0

Backtrace:
0: /usr/X11R6/bin/X(xorg_backtrace+0x3b) [0x81340eb]
1: /usr/X11R6/bin/X(xf86SigHandler+0x55) [0x80c76f5]
2: [0xb7fa7400]
3: /usr/lib/xorg/modules//libshadow.so(shadowRemove+0x4e) [0xb78c9eee]
4: /usr/lib/xorg/modules//libshadow.so [0xb78ca3a4]
5: /usr/X11R6/bin/X [0x80c6517]
6: /usr/X11R6/bin/X [0x811190c]
7: /usr/X11R6/bin/X [0x811dbcc]
8: /usr/X11R6/bin/X [0x812442c]
9: /usr/X11R6/bin/X [0x80cef6e]
10: /usr/lib/xorg/modules/drivers//vesa_drv.so [0xb7a57bb2]
11: /usr/X11R6/bin/X [0x80c71eb]
12: /usr/X11R6/bin/X [0x816162b]
13: /usr/X11R6/bin/X [0x80e12c8]
14: /usr/X11R6/bin/X [0x80cbb83]
15: /usr/X11R6/bin/X [0x814aa85]
16: /usr/X11R6/bin/X [0x817b94c]
17: /usr/X11R6/bin/X [0x81447fb]
18: /usr/lib/xorg/modules/extensions//libglx.so [0xb7aa246a]
19: /usr/X11R6/bin/X(main+0x44c) [0x807224c]
20: /lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xe5) [0xb7b79775]
21: /usr/X11R6/bin/X [0x8071671]
Saw signal 11. Server aborting.
 ddxSigGiveUp: Closing log

Revision history for this message
mezclatebrother! (prueboblog) wrote :
Revision history for this message
Bryce Harrington (bryce) wrote :

Could you please also run `lspci -vvnn > lspci-vvnn.txt` and attach that file to this bug report? Thanks ahead of time.

Changed in xserver-xorg-video-ati:
status: New → Incomplete
Revision history for this message
mezclatebrother! (prueboblog) wrote : Re: [Bug 328531] Re: r350 freeze starting X with radeon driver

Ok.

2009/2/23 Bryce Harrington <email address hidden>

> Could you please also run `lspci -vvnn > lspci-vvnn.txt` and attach that
> file to this bug report? Thanks ahead of time.
>
> ** Changed in: xserver-xorg-video-ati (Ubuntu)
> Status: New => Incomplete
>
> --
> r350 freeze starting X with radeon driver
> https://bugs.launchpad.net/bugs/328531
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in "xserver-xorg-video-ati" source package in Ubuntu: Incomplete
>
> Bug description:
> Well, i'm the #326867 bug reporter. With the last xorg and radeon driver
> update, now freezes in white when the gdm login appears. I have attached the
> Xorg log (there is a SIGSEGV).
>
> Ubuntu 9.04
>
> xorg:
> Instalados: 1:7.4~5ubuntu12
> Candidato: 1:7.4~5ubuntu12
> Tabla de versión:
> *** 1:7.4~5ubuntu12 0
>
> xserver-xorg-video-radeon:
> Instalados: 1:6.10.99.0-1ubuntu1
> Candidato: 1:6.10.99.0-1ubuntu1
> Tabla de versión:
> *** 1:6.10.99.0-1ubuntu1 0
>

Bryce Harrington (bryce)
Changed in xserver-xorg-video-ati:
status: Incomplete → Confirmed
Bryce Harrington (bryce)
description: updated
Revision history for this message
Bryce Harrington (bryce) wrote :

Hmm, according to that log you're actually using the vesa driver, not radeon. So I guess you have two bugs - one that radeon is not running, and the other that vesa crashes. Which of the two would you like to focus on in this bug report? I'd encourage filing a second bug about the other issue.

For the vesa crash, please collect a full backtrace - see http://wiki.ubuntu.com/X/Backtracing for directions.

For the failure to boot radeon, we'll need an Xorg.0.log from an attempt at booting that. It should show "RADEON" in the log. Look in your Xorg.0.log.old. Also, check to see if any of your logs in /var/log/gdm/* have error messages.

Changed in xserver-xorg-video-ati:
status: Confirmed → Incomplete
Revision history for this message
mezclatebrother! (prueboblog) wrote :

I'm sorry. I really think that this crash was caused by radeon driver. I
swith between radeon and vesa to check the first one and to start normally
and send reports. In other hand, i am not working with that pc and
unfortunatly i can't make any probe.

2009/2/27 Bryce Harrington <email address hidden>

> Hmm, according to that log you're actually using the vesa driver, not
> radeon. So I guess you have two bugs - one that radeon is not running,
> and the other that vesa crashes. Which of the two would you like to
> focus on in this bug report? I'd encourage filing a second bug about
> the other issue.
>
> For the vesa crash, please collect a full backtrace - see
> http://wiki.ubuntu.com/X/Backtracing for directions.
>
> For the failure to boot radeon, we'll need an Xorg.0.log from an attempt
> at booting that. It should show "RADEON" in the log. Look in your
> Xorg.0.log.old. Also, check to see if any of your logs in
> /var/log/gdm/* have error messages.
>
> ** Changed in: xserver-xorg-video-ati (Ubuntu)
> Status: Confirmed => Incomplete
>
> --
> r350 freeze starting X with radeon driver
> https://bugs.launchpad.net/bugs/328531
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in “xserver-xorg-video-ati” source package in Ubuntu: Incomplete
>
> Bug description:
> Well, i'm the #326867 bug reporter. With the last xorg and radeon driver
> update, now freezes in white when the gdm login appears. I have attached the
> Xorg log (there is a SIGSEGV).
>
> Ubuntu 9.04
>
> xorg:
> Instalados: 1:7.4~5ubuntu12
> Candidato: 1:7.4~5ubuntu12
> Tabla de versión:
> *** 1:7.4~5ubuntu12 0
>
> xserver-xorg-video-radeon:
> Instalados: 1:6.10.99.0-1ubuntu1
> Candidato: 1:6.10.99.0-1ubuntu1
> Tabla de versión:
> *** 1:6.10.99.0-1ubuntu1 0
>
> Backtrace:
> 0: /usr/X11R6/bin/X(xorg_backtrace+0x3b) [0x81340eb]
> 1: /usr/X11R6/bin/X(xf86SigHandler+0x55) [0x80c76f5]
> 2: [0xb7fa7400]
> 3: /usr/lib/xorg/modules//libshadow.so(shadowRemove+0x4e) [0xb78c9eee]
> 4: /usr/lib/xorg/modules//libshadow.so [0xb78ca3a4]
> 5: /usr/X11R6/bin/X [0x80c6517]
> 6: /usr/X11R6/bin/X [0x811190c]
> 7: /usr/X11R6/bin/X [0x811dbcc]
> 8: /usr/X11R6/bin/X [0x812442c]
> 9: /usr/X11R6/bin/X [0x80cef6e]
> 10: /usr/lib/xorg/modules/drivers//vesa_drv.so [0xb7a57bb2]
> 11: /usr/X11R6/bin/X [0x80c71eb]
> 12: /usr/X11R6/bin/X [0x816162b]
> 13: /usr/X11R6/bin/X [0x80e12c8]
> 14: /usr/X11R6/bin/X [0x80cbb83]
> 15: /usr/X11R6/bin/X [0x814aa85]
> 16: /usr/X11R6/bin/X [0x817b94c]
> 17: /usr/X11R6/bin/X [0x81447fb]
> 18: /usr/lib/xorg/modules/extensions//libglx.so [0xb7aa246a]
> 19: /usr/X11R6/bin/X(main+0x44c) [0x807224c]
> 20: /lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xe5) [0xb7b79775]
> 21: /usr/X11R6/bin/X [0x8071671]
> Saw signal 11. Server aborting.
> ddxSigGiveUp: Closing log
>
>

Revision history for this message
Bryce Harrington (bryce) wrote :

Since the hardware is no longer available for doing troubleshooting with, we'll have to close the bug for now. However please feel free to reopen if you or anyone else has the same HW and can reproduce this issue using the latest development version of Ubuntu and is willing to do some troubleshooting with it.

Changed in xserver-xorg-video-ati:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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