radeon driver crash

[Laurent Bigonville]

Binary package hint: xserver-xorg-video-radeon

Hi,

From time to time my computer crash (screen into power safe mode) and then a hard reboot is needed

Hopefully, this time the logs have been saved.

I was looking at some high res photographs with firefox then the screen goes black a few seconds after the driver has recovered, scrolling into the photo makes it happening again (3 or 4 times) and then the computer completly crashed

02:00.0 VGA compatible controller: ATI Technologies Inc RV790 [Radeon HD 4800 Series]

The machine is running maverick
---
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: bigon 2256 F.... pulseaudio
 /dev/snd/controlC1: bigon 2256 F.... pulseaudio
CRDA: Error: [Errno 2] Aucun fichier ou dossier de ce type
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xfbaf8000 irq 76'
   Mixer name : 'Analog Devices AD1989B'
   Components : 'HDA:11d4989b,10438372,00100300'
   Controls : 48
   Simple ctrls : 27
Card1.Amixer.info:
 Card hw:1 'Q9000'/'Logitech, Inc. QuickCam Pro 9000 at usb-0000:00:1d.7-2, high speed'
   Mixer name : 'USB Mixer'
   Components : 'USB046d:0990'
   Controls : 2
   Simple ctrls : 1
Card1.Amixer.values:
 Simple mixer control 'Mic',0
   Capabilities: cvolume cvolume-joined cswitch cswitch-joined penum
   Capture channels: Mono
   Limits: Capture 0 - 3072
   Mono: Capture 0 [0%] [18.00dB] [on]
Card2.Amixer.info:
 Card hw:2 'HDMI'/'HDA ATI HDMI at 0xfbbfc000 irq 77'
   Mixer name : 'ATI R6xx HDMI'
   Components : 'HDA:1002aa01,00aa0100,00100100'
   Controls : 4
   Simple ctrls : 1
Card2.Amixer.values:
 Simple mixer control 'IEC958',0
   Capabilities: pswitch pswitch-joined penum
   Playback channels: Mono
   Mono: Playback [on]
DRM.card0.DisplayPort.1:
 status: disconnected
 enabled: disabled
 dpms: On
 modes:
 edid-base64:
DRM.card0.HDMI_Type_A.1:
 status: disconnected
 enabled: disabled
 dpms: On
 modes:
 edid-base64:
DRM.card0.VGA.1:
 status: disconnected
 enabled: disabled
 dpms: On
 modes:
 edid-base64:
DistroRelease: Ubuntu 10.10
Frequency: Once every few days.
HibernationDevice: RESUME=UUID=8dcaff54-5485-4db5-a620-c45d320b1984
MachineType: System manufacturer System Product Name
Package: xserver-xorg-video-ati 1:6.13.1-1ubuntu2
PackageArchitecture: amd64
ProcCmdLine: BOOT_IMAGE=/vmlinuz-2.6.35-15-generic root=/dev/mapper/hostname-root ro quiet splash
ProcEnviron:
 PATH=(custom, no user)
 LANG=fr_BE.utf8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.35-15.21-generic 2.6.35.1
Regression: Yes
Reproducible: No
RfKill:
 0: hci0: Bluetooth
  Soft blocked: no
  Hard blocked: no
Tags: maverick graphics regression-potential needs-upstream-testing maverick maverick
Uname: Linux 2.6.35-15-generic x86_64
UserGroups: pkcs11
dmi.bios.date: 04/24/2009
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0406
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: P6T DELUXE V2
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0406:bd04/24/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP6TDELUXEV2:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
system:
 distro: Ubuntu
 codename: maverick
 architecture: x86_64
 kernel: 2.6.35-15-generic

[Laurent Bigonville (bigon)]

More over errors like

Aug 18 21:07:14 fornost kernel: [ 5550.474043] [drm:radeon_ib_schedule] *ERROR* radeon: couldn't schedule IB(4).
Aug 18 21:07:14 fornost kernel: [ 5550.474045] [drm:radeon_cs_ioctl] *ERROR* Faild to schedule IB !

happends time to time during boot, and the screen gets completely scrambled when gdm is loaded

not sure if I should open a new bug for this

[Bryce Harrington (bryce)]

Hi Laurent,

        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.]

[Laurent Bigonville (bigon)]

apport information

[Laurent Bigonville (bigon)]

apport information

[Laurent Bigonville (bigon)]

apport information

[Laurent Bigonville (bigon)]

apport information

[Laurent Bigonville (bigon)]

apport information

[Laurent Bigonville (bigon)]

apport information

[Laurent Bigonville (bigon)]

apport information

[Laurent Bigonville (bigon)]

apport information

[Laurent Bigonville (bigon)]

apport information

[Laurent Bigonville (bigon)]

apport information

[Laurent Bigonville (bigon)]

apport information

[Laurent Bigonville (bigon)]

apport information

[Laurent Bigonville (bigon)]

apport information

[Laurent Bigonville (bigon)]

apport information

[Laurent Bigonville (bigon)]

apport information

[Laurent Bigonville (bigon)]

apport information

[Laurent Bigonville (bigon)]

apport information

[Laurent Bigonville (bigon)]

apport information

[Laurent Bigonville (bigon)]

apport information

[Laurent Bigonville (bigon)]

apport information

[Laurent Bigonville (bigon)]

apport information

[Laurent Bigonville (bigon)]

apport information

[Laurent Bigonville (bigon)]

apport information

[Laurent Bigonville (bigon)]

apport information

[Laurent Bigonville (bigon)]

apport information

[Laurent Bigonville (bigon)]

apport information

[Laurent Bigonville (bigon)]

apport information

[Laurent Bigonville (bigon)]

apport information

[Laurent Bigonville (bigon)]

apport information

[Laurent Bigonville (bigon)]

apport information

[Laurent Bigonville (bigon)]

apport information

[Laurent Bigonville (bigon)]

apport information

[Laurent Bigonville (bigon)]

apport information

[Laurent Bigonville (bigon)]

apport information

[Laurent Bigonville (bigon)]

apport information

[bugbot (bugbot)]

Hey Laurent,

Thanks for testing maverick during its development period. Unfortunately it looks like this bug report didn't get attention during the maverick development period. But I see there's not been more comments on the bug since the release, which makes me wonder if this is still an issue for you?

If you've not seen this issue since maverick's release yourself, it may have been solved by kernel or X or other updates that occurred late in the release; if so, would you mind please closing the bug for us? Go to the URL mentioned in this bug report, click the yellow icon(s) in the status column and set to 'Fix Released'.

If you no longer have the hardware needed to reproduce the problem, or otherwise feel the bug no longer needs tracked in Launchpad, you can set the status to 'Invalid'.

If you are the original reporter and still have this issue, just reply to this email saying so. (Or set the bug status to Confirmed.) If you are able to re-test this against 11.04 Natty Narwhal (our current development focus) and find the issue still affects Natty, please also run 'apport-collect <bug-number>' while running natty, which will add fresh logs and debug data, and flag it for the Ubuntu-X development team to look at.

[bugbot (bugbot)]

We're closing this bug since it is has been some time with no response from the original reporter. However, if the issue still exists please feel free to reopen with the requested information. Also, if you could, please test against the latest development version of Ubuntu, since this confirms the bug is one we may be able to pass upstream for help.

[penalvch (penalvch)]

Laurent Bigonville, this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? If so, could you please test for this with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ .

If it remains an issue, could you please run the following command in the development release from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report:

apport-collect -p linux <replace-with-bug-number>

Also, could you please test the latest upstream kernel available following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the daily kernel folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-fixed-upstream-v3.12-rc2

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding.