From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.sourceforge.net
Subject: [Bug 15779] New: [radeon X1300 KMS] infinite atombios loop on Xorg startup
Date: Tue, 13 Apr 2010 20:20:48 GMT [thread overview]
Message-ID: <bug-15779-2300@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=15779
Summary: [radeon X1300 KMS] infinite atombios loop on Xorg
startup
Product: Drivers
Version: 2.5
Kernel Version: 2.6.34-rc3-42171-g1f01696
Platform: All
OS/Version: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: Video(DRI - non Intel)
AssignedTo: drivers_video-dri@kernel-bugs.osdl.org
ReportedBy: tomastrnka@gmx.com
Regression: No
Created an attachment (id=25993)
--> (https://bugzilla.kernel.org/attachment.cgi?id=25993)
dmesg log of a KMS boot to runlevel 5
Booting current drm-radeon-testing (commit
3a44d81fb0e85b18484cae6a20f0661710b6c1db) on my AGP X1300 with KMS enabled
reliably leads to a blank screen (monitor goes to sleep) when Xorg fires up.
These two messages show up in dmesg:
[drm:atom_op_jump] *ERROR* atombios stuck in loop for more than 1sec aborting
[drm:atom_execute_table_locked] *ERROR* atombios stuck executing E1B9 (len 86,
WS 4, PS 0) @ 0xE1EC
This bug is here for a long long time but without the recent atombios loop
detection logic every Xorg startup using KMS ended with a blank screen and
locked up X (SSH working, X not responding to signals including SIGKILL,
machine unable to shutdown properly). With this checking in place, X
fortunately doesn't lock up and it's possible to kill it or switch VTs
normally.
KMS has never been working on this machine partly because of this issue and
also because of the race reported in bug 15078 (however, that one seems to have
vanished with recent kernels - without a relevant commit).
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
--
next reply other threads:[~2010-04-13 20:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-13 20:20 bugzilla-daemon [this message]
2010-04-13 20:21 ` [Bug 15779] [radeon X1300 KMS] infinite atombios loop on Xorg startup bugzilla-daemon
2010-04-13 20:23 ` bugzilla-daemon
2010-04-13 20:25 ` bugzilla-daemon
2013-11-20 13:29 ` 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-15779-2300@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=dri-devel@lists.sourceforge.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.