Bug 28876 - [radeon HD4250] Frequent lockups while screen locked
Summary: [radeon HD4250] Frequent lockups while screen locked
Status: RESOLVED FIXED
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Radeon (show other bugs)
Version: unspecified
Hardware: x86-64 (AMD64) Linux (All)
: medium critical
Assignee: Default DRI bug account
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-07-01 14:43 UTC by Yann Dirson
Modified: 2011-05-20 13:09 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
Xorg log file, with nearly 30k lines of repeated messages stripped (9.21 KB, application/x-gzip)
2010-07-01 14:43 UTC, Yann Dirson
no flags Details
Xorg log file for 2nd X server (the one that triggers the lockup) (28.77 KB, text/x-log)
2010-07-01 16:33 UTC, Yann Dirson
no flags Details

Description Yann Dirson 2010-07-01 14:43:25 UTC
Created attachment 36664 [details]
Xorg log file, with nearly 30k lines of repeated messages stripped

Direct symptoms:
- display left unattended with xscreensaver in simple blank mode
- DPMS disabled (checked both with xset and xscreensaver-demo)
- when coming back to my keyboard the monitor does not get a video signal
- I can still login remotely through ssh and reboot the machine properly

Hardware is an Asus "M4A88TD-V EVO/USB3" motherboard, featuring radeon HD4250 (RS780).  OS is uptodate Debian/testing.

syslog contains lines like the following.  In this case, although I was not here, it may be that someone tried to use the box.  In the 2 other occurences I have traces for, it I may even have been myself, but I did not dig at that time.

However, although the Xorg.0.log error lines are not timestamped, the file timestamp itself matches the box' reboot.  Since there are ~15000 occurences of the error, X may have been experiencing them since the error reported by the drm module.  I can try to get more detailed facts next time (unless unnecessary, just tell).

Jun 30 10:17:01 home /USR/SBIN/CRON[27295]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
Jun 30 10:18:10 home kernel: [130052.418150] executing set pll
Jun 30 10:18:10 home kernel: [130052.424023] executing set crtc timing
Jun 30 10:18:10 home kernel: [130052.424072] [drm] TMDS-11: set mode 1920x1200 1b
Jun 30 10:18:10 home acpid: client 2095[0:0] has disconnected
Jun 30 10:18:10 home acpid: client connected from 27304[0:0]
Jun 30 10:18:10 home acpid: 1 client rule loaded
Jun 30 10:18:13 home kernel: [130055.829085] [drm:radeon_ib_get] *ERROR* radeon: IB(0:0x0000000010101000:668)
Jun 30 10:18:13 home kernel: [130055.829088] [drm:radeon_ib_get] *ERROR* radeon: GPU lockup detected, fail to get a IB
Jun 30 10:18:13 home kernel: [130055.829090] [drm:radeon_cs_ioctl] *ERROR* Failed to get ib !
[...]
Jun 30 10:18:42 home kernel: [130084.275900] [drm:radeon_ib_get] *ERROR* radeon: IB(0:0x0000000010101000:668)
Jun 30 10:18:42 home kernel: [130084.275906] [drm:radeon_ib_get] *ERROR* radeon: GPU lockup detected, fail to get a IB
Jun 30 10:18:42 home kernel: [130084.275912] [drm:radeon_cs_ioctl] *ERROR* Failed to get ib !
Jun 30 11:17:01 home /USR/SBIN/CRON[27329]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)

In older occurences (do not recall the precise set of events, although the "wishing to unlock screen" event has always been the only way to see the problem), the 3 error lines occur on a longer timespan, some in sync with the clock (??):

Jun 27 19:17:01 home /USR/SBIN/CRON[26082]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
Jun 27 19:18:09 home kernel: [21853.241075] executing set pll
Jun 27 19:18:09 home kernel: [21853.248025] executing set crtc timing
Jun 27 19:18:09 home kernel: [21853.248076] [drm] TMDS-11: set mode 1920x1200 1b
Jun 27 19:18:12 home kernel: [21856.334252] [drm:radeon_ib_get] *ERROR* radeon: IB(0:0x0000000010101000:668)
Jun 27 19:18:12 home kernel: [21856.334261] [drm:radeon_ib_get] *ERROR* radeon: GPU lockup detected, fail to get a IB
Jun 27 19:18:12 home kernel: [21856.334269] [drm:radeon_cs_ioctl] *ERROR* Failed to get ib !
[...]
Jun 27 19:18:32 home kernel: [21876.279726] [drm:radeon_ib_get] *ERROR* radeon: IB(0:0x0000000010101000:668)
Jun 27 19:18:32 home kernel: [21876.279733] [drm:radeon_ib_get] *ERROR* radeon: GPU lockup detected, fail to get a IB
Jun 27 19:18:32 home kernel: [21876.279739] [drm:radeon_cs_ioctl] *ERROR* Failed to get ib !
Jun 27 19:19:00 home kernel: [21904.282670] [drm:radeon_ib_get] *ERROR* radeon: IB(0:0x0000000010101000:668)
Jun 27 19:19:00 home kernel: [21904.282678] [drm:radeon_ib_get] *ERROR* radeon: GPU lockup detected, fail to get a IB
Jun 27 19:19:00 home kernel: [21904.282685] [drm:radeon_cs_ioctl] *ERROR* Failed to get ib !
Jun 27 19:20:00 home kernel: [21964.322037] [drm:radeon_ib_get] *ERROR* radeon: IB(0:0x0000000010101000:668)
Jun 27 19:20:00 home kernel: [21964.322045] [drm:radeon_ib_get] *ERROR* radeon: GPU lockup detected, fail to get a IB
Jun 27 19:20:00 home kernel: [21964.322052] [drm:radeon_cs_ioctl] *ERROR* Failed to get ib !
Jun 27 19:21:00 home kernel: [22024.321528] [drm:radeon_ib_get] *ERROR* radeon: IB(0:0x0000000010101000:668)
Jun 27 19:21:00 home kernel: [22024.321537] [drm:radeon_ib_get] *ERROR* radeon: GPU lockup detected, fail to get a IB
Jun 27 19:21:00 home kernel: [22024.321544] [drm:radeon_cs_ioctl] *ERROR* Failed to get ib !
Jun 27 19:22:00 home kernel: [22084.321217] [drm:radeon_ib_get] *ERROR* radeon: IB(0:0x0000000010101000:668)
Jun 27 19:22:00 home kernel: [22084.321225] [drm:radeon_ib_get] *ERROR* radeon: GPU lockup detected, fail to get a IB
Jun 27 19:22:00 home kernel: [22084.321232] [drm:radeon_cs_ioctl] *ERROR* Failed to get ib !
Jun 27 19:23:00 home kernel: [22144.367818] [drm:radeon_ib_get] *ERROR* radeon: IB(0:0x0000000010101000:668)
Jun 27 19:23:00 home kernel: [22144.367827] [drm:radeon_ib_get] *ERROR* radeon: GPU lockup detected, fail to get a IB
Jun 27 19:23:00 home kernel: [22144.367833] [drm:radeon_cs_ioctl] *ERROR* Failed to get ib !
Jun 27 19:24:00 home kernel: [22204.414007] [drm:radeon_ib_get] *ERROR* radeon: IB(0:0x0000000010101000:668)
Jun 27 19:24:00 home kernel: [22204.414015] [drm:radeon_ib_get] *ERROR* radeon: GPU lockup detected, fail to get a IB
Jun 27 19:24:00 home kernel: [22204.414022] [drm:radeon_cs_ioctl] *ERROR* Failed to get ib !
Jun 27 19:24:12 home kernel: [22216.304962] [drm:radeon_ib_get] *ERROR* radeon: IB(0:0x0000000010101000:668)
Jun 27 19:24:12 home kernel: [22216.304970] [drm:radeon_ib_get] *ERROR* radeon: GPU lockup detected, fail to get a IB
Jun 27 19:24:12 home kernel: [22216.304977] [drm:radeon_cs_ioctl] *ERROR* Failed to get ib !

Xorg.0.log repeated messages are:

(EE) RADEON(0): Timeout trying to update memory controller settings !
(EE) RADEON(0): You will probably crash now ... 

Package versions are as follows (dpkg -l|grep xserver):

x11-xserver-utils                                    7.5+1                  
xserver-common                                       2:1.7.7-2              
xserver-xephyr                                       2:1.7.7-2              
xserver-xorg                                         1:7.5+6                
xserver-xorg-core                                    2:1.7.7-2              
xserver-xorg-core-dbg                                2:1.7.7-2              
xserver-xorg-input-all                               1:7.5+6                
xserver-xorg-input-evdev                             1:2.3.2-6              
xserver-xorg-input-synaptics                         1.2.2-2                
xserver-xorg-input-wacom                             0.10.5+20100416-1      
xserver-xorg-video-ati                               1:6.13.0-2             
xserver-xorg-video-fbdev                             1:0.4.2-2              
xserver-xorg-video-mach64                            6.8.2-3                
xserver-xorg-video-mga                               1:1.4.11.dfsg-4        
xserver-xorg-video-r128                              6.8.1-3                
xserver-xorg-video-radeon                            1:6.13.0-2             
xserver-xorg-video-radeon-dbg                        1:6.13.0-2             
xserver-xorg-video-vesa                              1:2.3.0-3
Comment 1 Yann Dirson 2010-07-01 14:46:07 UTC
And the relevant boot-time kernel logs are as follows (eg. shows KMS initialized):

Jun 30 18:35:40 home kernel: [   15.720780] pci 0000:01:05.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18
Jun 30 18:35:40 home kernel: [   15.821648] [drm] Initialized drm 1.1.0 20060810
Jun 30 18:35:40 home kernel: [   15.908369] [drm] radeon kernel modesetting enabled.
Jun 30 18:35:40 home kernel: [   15.908539] radeon 0000:01:05.0: setting latency timer to 64
Jun 30 18:35:40 home kernel: [   15.912423] [drm] radeon: Initializing kernel modesetting.
Jun 30 18:35:40 home kernel: [   15.912499] [drm] register mmio base: 0xFE8F0000
Jun 30 18:35:40 home kernel: [   15.912504] [drm] register mmio size: 65536
Jun 30 18:35:40 home kernel: [   15.918319] ATOM BIOS: 113
Jun 30 18:35:40 home kernel: [   15.918327] [drm] Clocks initialized !
Jun 30 18:35:40 home kernel: [   15.922848] [drm] Detected VRAM RAM=256M, BAR=256M
Jun 30 18:35:40 home kernel: [   15.922856] [drm] RAM width 32bits DDR
Jun 30 18:35:40 home kernel: [   15.922968] [TTM] Zone  kernel: Available graphics memory: 1901154 kiB.
Jun 30 18:35:40 home kernel: [   15.923002] [drm] radeon: 256M of VRAM memory ready
Jun 30 18:35:40 home kernel: [   15.923007] [drm] radeon: 512M of GTT memory ready.
Jun 30 18:35:40 home kernel: [   15.923094] [drm] Loading RS780 CP Microcode
Jun 30 18:35:40 home kernel: [   15.923102] platform radeon_cp.0: firmware: requesting radeon/RS780_pfp.bin
Jun 30 18:35:40 home kernel: [   15.953147] platform radeon_cp.0: firmware: requesting radeon/RS780_me.bin
Jun 30 18:35:40 home kernel: [   15.959784] [drm] GART: num cpu pages 131072, num gpu pages 131072
Jun 30 18:35:40 home kernel: [   15.993764] [drm] ring test succeeded in 0 usecs
Jun 30 18:35:40 home kernel: [   15.993987] [drm] radeon: ib pool ready.
Jun 30 18:35:40 home kernel: [   15.994036] [drm] ib test succeeded in 0 usecs
Jun 30 18:35:40 home kernel: [   15.994115] [drm] Radeon Display Connectors
Jun 30 18:35:40 home kernel: [   15.994116] [drm] Connector 0:
Jun 30 18:35:40 home kernel: [   15.994117] [drm]   VGA
Jun 30 18:35:40 home kernel: [   15.994119] [drm]   DDC: 0x7e40 0x7e40 0x7e44 0x7e44 0x7e48 0x7e48 0x7e4c 0x7e4c
Jun 30 18:35:40 home kernel: [   15.994120] [drm]   Encoders:
Jun 30 18:35:40 home kernel: [   15.994121] [drm]     CRT1: INTERNAL_KLDSCP_DAC1
Jun 30 18:35:40 home kernel: [   15.994122] [drm] Connector 1:
Jun 30 18:35:40 home kernel: [   15.994123] [drm]   DVI-D
Jun 30 18:35:40 home kernel: [   15.994124] [drm]   DDC: 0x7e50 0x7e50 0x7e54 0x7e54 0x7e58 0x7e58 0x7e5c 0x7e5c
Jun 30 18:35:40 home kernel: [   15.994125] [drm]   Encoders:
Jun 30 18:35:40 home kernel: [   15.994126] [drm]     DFP3: INTERNAL_KLDSCP_LVTMA
Jun 30 18:35:41 home kernel: [   16.135841] [drm] fb mappable at 0xD0141000
Jun 30 18:35:41 home kernel: [   16.135842] [drm] vram apper at 0xD0000000
Jun 30 18:35:41 home kernel: [   16.135844] [drm] size 9216000
Jun 30 18:35:41 home kernel: [   16.135844] [drm] fb depth is 24
Jun 30 18:35:41 home kernel: [   16.135845] [drm]    pitch is 7680
Jun 30 18:35:41 home kernel: [   16.136089] Console: switching to colour frame buffer device 240x75
Jun 30 18:35:41 home kernel: [   16.136093] fb0: radeondrmfb frame buffer device
Jun 30 18:35:41 home kernel: [   16.136094] registered panic notifier
Jun 30 18:35:41 home kernel: [   16.136097] [drm] Initialized radeon 2.0.0 20080528 for 0000:01:05.0 on minor 0
Comment 2 Yann Dirson 2010-07-01 16:33:46 UTC
Created attachment 36668 [details]
Xorg log file for 2nd X server (the one that triggers the lockup)

I can now reproduce the bug at will: it occurs when a second X server is launched (though xscreensaver and gdm).  The new server has a non-fonctionnal display (long sequences of white and black pixel resulting in irregular large but horizontal "stripes"), and it is when I switch to the original one that the monitor stops getting a video signal.

I attach the Xorg.log for that 2nd server.  Looks like it froze before completely initializing ?
Comment 3 Yann Dirson 2010-07-02 12:20:13 UTC
Forgot to note the kernel version, vanilla 2.6.32.13 (with evms-bd-claim patch, but that should not matter).
Comment 4 Yann Dirson 2011-05-20 13:09:04 UTC
This has not occured since quite some time now, fixed.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.