Created attachment 709122 [details] Xorg log Description of problem: GPU lockup, no further working possible. Version-Release number of selected component (if applicable): Kernel: 3.8.1-201.fc18.x86_64 See attached Xorg.0.log How reproducible: Error occurs after some time machine is up and running. Steps to Reproduce: 1. Boot Fedora 18 2. wait some hours 3. error will occure Actual results: GPU / machine lockup Expected results: No lockup Additional info:
Created attachment 709123 [details] Output of dmesg
Created attachment 709124 [details] output of lspci
Created attachment 709125 [details] logfile messages
From /var/log/messages: Mar 12 16:56:39 robin kernel: [85627.117716] radeon 0000:01:00.0: GPU lockup CP stall for more than 10000msec Mar 12 16:56:39 robin kernel: [85627.117725] radeon 0000:01:00.0: GPU lockup (waiting for 0x0000000000066569) Mar 12 16:56:39 robin kernel: [85627.117731] radeon 0000:01:00.0: failed to get a new IB (-35) Mar 12 16:56:39 robin kernel: [85627.117736] [drm:radeon_cs_ib_chunk] *ERROR* Failed to get ib ! Mar 12 16:56:39 robin kernel: [85627.286488] radeon: wait for empty RBBM fifo failed ! Bad things might happen. Mar 12 16:56:39 robin kernel: [85627.462275] Failed to wait GUI idle while programming pipes. Bad things might happen. Mar 12 16:56:39 robin kernel: [85627.463375] radeon 0000:01:00.0: Saved 9467 dwords of commands on ring 0. Mar 12 16:56:39 robin kernel: [85627.464670] radeon 0000:01:00.0: (rs600_asic_reset:365) RBBM_STATUS=0x9401C100 Mar 12 16:56:40 robin kernel: [85627.965131] radeon 0000:01:00.0: (rs600_asic_reset:385) RBBM_STATUS=0x9401C100 Mar 12 16:56:40 robin kernel: [85628.464571] radeon 0000:01:00.0: (rs600_asic_reset:393) RBBM_STATUS=0x9400C100 Mar 12 16:56:41 robin kernel: [85628.964010] radeon 0000:01:00.0: (rs600_asic_reset:401) RBBM_STATUS=0x9400C100 Mar 12 16:56:41 robin kernel: [85628.964064] radeon 0000:01:00.0: failed to reset GPU Mar 12 16:56:41 robin kernel: [85628.992984] radeon 0000:01:00.0: GPU reset failed Mar 12 16:56:41 robin kernel: [85628.996717] radeon 0000:01:00.0: couldn't schedule ib Mar 12 16:56:41 robin kernel: [85628.996724] [drm:radeon_cs_ib_chunk] *ERROR* Failed to schedule IB ! Mar 12 16:56:41 robin kernel: [85628.998441] radeon 0000:01:00.0: couldn't schedule ib Mar 12 16:56:41 robin kernel: [85628.998443] [drm:radeon_cs_ib_chunk] *ERROR* Failed to schedule IB ! Mar 12 16:56:41 robin kernel: [85628.999049] radeon 0000:01:00.0: couldn't schedule ib Mar 12 16:56:41 robin kernel: [85628.999050] [drm:radeon_cs_ib_chunk] *ERROR* Failed to schedule IB ! Mar 12 16:56:41 robin kernel: [85629.000249] radeon 0000:01:00.0: couldn't schedule ib Mar 12 16:56:41 robin kernel: [85629.000251] [drm:radeon_cs_ib_chunk] *ERROR* Failed to schedule IB ! Mar 12 16:56:41 robin kernel: [85629.000831] radeon 0000:01:00.0: couldn't schedule ib Mar 12 16:56:41 robin kernel: [85629.000832] [drm:radeon_cs_ib_chunk] *ERROR* Failed to schedule IB ! Mar 12 16:56:41 robin kernel: [85629.001344] radeon 0000:01:00.0: couldn't schedule ib Mar 12 16:56:41 robin kernel: [85629.001345] [drm:radeon_cs_ib_chunk] *ERROR* Failed to schedule IB ! Mar 12 16:56:41 robin kernel: [85629.002689] radeon 0000:01:00.0: couldn't schedule ib Mar 12 16:56:41 robin kernel: [85629.002692] [drm:radeon_cs_ib_chunk] *ERROR* Failed to schedule IB ! Mar 12 16:56:41 robin kernel: [85629.003554] radeon 0000:01:00.0: couldn't schedule ib Mar 12 16:56:41 robin kernel: [85629.003555] [drm:radeon_cs_ib_chunk] *ERROR* Failed to schedule IB ! Mar 12 16:56:41 robin kernel: [85629.004105] radeon 0000:01:00.0: couldn't schedule ib Mar 12 16:56:41 robin kernel: [85629.004107] [drm:radeon_cs_ib_chunk] *ERROR* Failed to schedule IB ! Mar 12 16:56:41 robin kernel: [85629.004505] radeon 0000:01:00.0: couldn't schedule ib Mar 12 16:56:41 robin kernel: [85629.004507] [drm:radeon_cs_ib_chunk] *ERROR* Failed to schedule IB ! Mar 12 16:56:41 robin kernel: [85629.004602] radeon 0000:01:00.0: couldn't schedule ib Mar 12 16:56:41 robin kernel: [85629.004604] [drm:radeon_cs_ib_chunk] *ERROR* Failed to schedule IB ! Mar 12 16:56:41 robin kernel: [85629.005264] radeon 0000:01:00.0: couldn't schedule ib Mar 12 16:56:41 robin kernel: [85629.005271] [drm:radeon_cs_ib_chunk] *ERROR* Failed to schedule IB !
Hi everyone, i got the same error: dmesg: [ 2112.529246] radeon 0000:01:00.0: GPU lockup CP stall for more than 38888msec [ 2112.529253] radeon 0000:01:00.0: GPU lockup (waiting for 0x00000000000012de last fence id 0x00000000000012dd) [ 2161.094373] radeon 0000:01:00.0: couldn't schedule ib [ 2161.094377] [drm:radeon_cs_ib_chunk] *ERROR* Failed to schedule IB ! [ 2162.910958] radeon 0000:01:00.0: couldn't schedule ib [ 2162.910964] [drm:radeon_cs_ib_chunk] *ERROR* Failed to schedule IB ! [ 2351.975492] radeon 0000:01:00.0: couldn't schedule ib [ 2351.975499] [drm:radeon_cs_ib_chunk] *ERROR* Failed to schedule IB ! [ 2455.520769] radeon 0000:01:00.0: couldn't schedule ib [ 2455.520776] [drm:radeon_cs_ib_chunk] *ERROR* Failed to schedule IB ! [ 2819.559543] radeon 0000:01:00.0: couldn't schedule ib [ 2819.559549] [drm:radeon_cs_ib_chunk] *ERROR* Failed to schedule IB ! /var/log/messages: Apr 15 11:21:25 localhost abrt[11040]: Saved core dump of pid 9359 (/usr/bin/Xorg) to /var/tmp/abrt/ccpp-2013-04-15-11:21:22-9359 (184283136 bytes) Apr 15 11:21:25 localhost abrtd: Directory 'ccpp-2013-04-15-11:21:22-9359' creation detected Apr 15 11:21:25 localhost abrtd: Generación de seguimiento Apr 15 11:21:25 localhost abrtd: Backtrace is generated, 7710 bytes Apr 15 11:21:25 localhost abrtd: Cannot disassemble function at 0x0, not computing fingerprint Apr 15 11:21:25 localhost abrtd: Cannot disassemble function at 0x0, not computing fingerprint Apr 15 11:21:25 localhost abrtd: Cannot disassemble function at 0x0, not computing fingerprint Apr 15 11:21:25 localhost abrtd: Core backtrace is generated and saved, 1565 bytes Apr 15 11:21:25 localhost abrtd: Duplicate: core backtrace Apr 15 11:21:25 localhost abrtd: DUP_OF_DIR: /var/tmp/abrt/ccpp-2013-04-15-08:31:45-748 Apr 15 11:21:25 localhost abrtd: Deleting problem directory ccpp-2013-04-15-11:21:22-9359 (dup of ccpp-2013-04-15-08:31:45-748) Apr 15 11:21:25 localhost kdm[736]: X server for display :0 terminated unexpectedly Apr 15 11:21:25 localhost NetworkManager[711]: <warn> error requesting auth for org.freedesktop.NetworkManager.wifi.share.open: (3) GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Could not get UID of name ':1.224': no such name Apr 15 11:21:25 localhost NetworkManager[711]: <warn> error requesting auth for org.freedesktop.NetworkManager.wifi.share.protected: (3) GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Could not get UID of name ':1.224': no such name Apr 15 11:21:25 localhost NetworkManager[711]: <warn> error requesting auth for org.freedesktop.NetworkManager.wifi.share.open: (3) GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Could not get UID of name ':1.224': no such name Apr 15 11:21:29 localhost dbus-daemon[721]: dbus[721]: [system] Activating service name='net.reactivated.Fprint' (using servicehelper) And i have this directories: /var/tmp/abrt/ccpp-2013-04-15-08:31:45-748 /var/tmp/abrt/ccpp-2013-04-15-08:31:46-2814 Which information can i upload to get this bug fixed ? Cheers,
This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '18'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior to Fedora 18's end of life. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.