[X1400] random crash when loading the X server

Bug #584525 reported by Pablo Rodríguez
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
xserver-xorg-video-ati (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: xserver-xorg-video-ati

I used other distributions (Mandriva and openSUSE) with the radeonhd driver, but after I switched to Ubuntu 10.04, I experience random X crashes when the video driver is loaded. All I get is a black screen with some random red points at the first lines. I have to restart by turning off the computer and turning on again.

I guess that this is caused by the radeon video driver. Since I had to restart the computer, I have no /var/log/Xorg.0.log to append, since the new one doesn't reflect the crash. I'm not able to provide a full backtrace, because "ulimit -c" was set to 0 (and I wonder whether this setting will support a system restart).

Driver version is:

  xserver-xorg-video-ati:
    Installed: 1:6.13.0-1ubuntu5
    Candidate: 1:6.13.0-1ubuntu5

And Ubuntu version is:

  Description: Ubuntu 10.04 LTS
  Release: 10.04

Is there anything else I need to report the crash? (I don't mind reporting the bug myself upstream.)

Thanks for your help,

Pablo

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

Hi Pablo,

Please run the command 'apport-collect BUGNUMBER', which will attach several files we need for debugging.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

tags: added: crash
tags: added: needs-xorglog
tags: added: needs-lspci-vvnn
Changed in xserver-xorg-video-ati (Ubuntu):
status: New → Incomplete
Revision history for this message
Pablo Rodríguez (ousia) wrote :

Hi Bruce,

thanks for your fast reply.

Sorry, but I'm afraid I haven't expressed myself accurately.

The issue doesn't appear every time I boot the system (it seems totally random, at least to me) and the computer is totally unresponsive, so I cannot run any command then.

And I guess that if I run when I restart the computer, the files collected by apport-collect might be the wrong ones, since the reboot is fine.

Could you confirm this?

Thanks,

Pablo

Revision history for this message
Pablo Rodríguez (ousia) wrote :

Hi Bruce,

I have experienced another crash. I'm attaching the Xorg.0.log file, but I'm afraid it might be the previous one, since the crash happened less than 20 minutes ago and last modification from this file was almost 8 hours ago.

Sorry, I have realized that I don't know how I copied the Xorg.0.log file to the USB memory with Slax, but I'm afraid it is not there. Just in case it might help, I attach Xorg.0.log.old.

I have tried to get a «post mortem» (or «post crashem» ;-)) backtrace, but I'm afraid I cannot get rid of ulimit -c 0.

I have added the following uncommented line to /etc/security/limits.conf:

    root hard core unlimited

But ulimit -c in root is set to 0. This is why I cannot provide a retrospective backtrace.

How can I get core files for the root?

Thanks for your help,

Pablo

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

Thanks for the Xorg log. We also need the lspci -vnvn output attached to this bug as a file

tags: removed: needs-xorglog
Changed in xserver-xorg-video-ati (Ubuntu):
status: Incomplete → New
status: New → Incomplete
Revision history for this message
Pablo Rodríguez (ousia) wrote :

I guess this is what you want:

01:00.0 VGA compatible controller [0300]: ATI Technologies Inc Radeon Mobility X1400 [1002:7145]
 Subsystem: Dell Device [1028:2003]
 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 27
 Region 0: Memory at d0000000 (32-bit, prefetchable) [size=256M]
 Region 1: I/O ports at ee00 [size=256]
 Region 2: Memory at efdf0000 (32-bit, non-prefetchable) [size=64K]
 [virtual] Expansion ROM at efd00000 [disabled] [size=128K]
 Capabilities: [50] Power Management version 2
  Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
  Status: D0 PME-Enable- DSel=0 DScale=0 PME-
 Capabilities: [58] Express (v1) Legacy Endpoint, MSI 00
  DevCap: MaxPayload 128 bytes, PhantFunc 0, Latency L0s <4us, L1 unlimited
   ExtTag+ AttnBtn- AttnInd- PwrInd- RBE- FLReset-
  DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported-
   RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop+
   MaxPayload 128 bytes, MaxReadReq 128 bytes
  DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- TransPend-
  LnkCap: Port #0, Speed 2.5GT/s, Width x16, ASPM L0s L1, Latency L0 <64ns, L1 <1us
   ClockPM- Suprise- LLActRep- BwNot-
  LnkCtl: ASPM L1 Enabled; RCB 64 bytes Disabled- Retrain- CommClk+
   ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
  LnkSta: Speed 2.5GT/s, Width x16, TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt-
 Capabilities: [80] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 Enable+
  Address: 00000000fee0200c Data: 4199
 Kernel driver in use: radeon
 Kernel modules: radeon

Bryce Harrington (bryce)
tags: added: hardy lucid
Revision history for this message
Bryce Harrington (bryce) wrote :

You've not provided enough information to troubleshoot this bug. The X log you attached does not indicate an X crash. "randomly crashes" does not adequately explain the defect you're experiencing.

Changed in xserver-xorg-video-ati (Ubuntu):
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.