From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 28876] New: [radeon HD4250] Frequent lockups while screen locked
Date: Thu, 1 Jul 2010 14:43:25 -0700 (PDT) [thread overview]
Message-ID: <bug-28876-502@http.bugs.freedesktop.org/> (raw)
https://bugs.freedesktop.org/show_bug.cgi?id=28876
Summary: [radeon HD4250] Frequent lockups while screen locked
Product: DRI
Version: unspecified
Platform: x86-64 (AMD64)
OS/Version: Linux (All)
Status: NEW
Severity: critical
Priority: medium
Component: DRM/Radeon
AssignedTo: dri-devel@lists.freedesktop.org
ReportedBy: ydirson@altern.org
Created an attachment (id=36664)
--> (https://bugs.freedesktop.org/attachment.cgi?id=36664)
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
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next reply other threads:[~2010-07-01 21:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-01 21:43 bugzilla-daemon [this message]
2010-07-01 21:46 ` [Bug 28876] [radeon HD4250] Frequent lockups while screen locked bugzilla-daemon
2010-07-01 23:33 ` bugzilla-daemon
2010-07-02 19:20 ` bugzilla-daemon
2011-05-20 20:09 ` bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-28876-502@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.org \
--cc=dri-devel@lists.freedesktop.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).