dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 73420] [HAWAII] X.org fails to start due to atombios stucking (Sapphire r9 290x Tri-X)
Date: Sun, 26 Jan 2014 05:10:27 +0000	[thread overview]
Message-ID: <bug-73420-502-rc8j2QR7qS@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-73420-502@http.bugs.freedesktop.org/>


[-- Attachment #1.1: Type: text/plain, Size: 3245 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=73420

--- Comment #8 from Luzipher <luziphermcleod@yahoo.ie> ---
With newest stuff from git (xf86-video-ati, mesa, llvm, glamor) I now get X up
and running - in llvmpipe software mode. It still stalls the system for at
least one occurance of the 5s loop on X startup. dmesg shows 9 of the "atombios
stuck for more than 5s" messages currently.


Snippet from Xorg.0.log (startx)
[  7148.888] (==) RADEON(0): DPMS enabled
[  7148.888] (==) RADEON(0): Silken mouse enabled
[  7148.888] (II) RADEON(0): RandR 1.2 enabled, ignore the following RandR
disabled message.
[  7163.924] (--) RandR disabled
[  7163.928] (II) AIGLX: Screen 0 is not DRI2 capable
[  7163.928] (EE) AIGLX: reverting to software rendering
[  7163.995] (II) AIGLX: Loaded and initialized swrast
[  7163.995] (II) GLX: Initialized DRISWRAST GL provider for screen 0
[  7179.061] (II) RADEON(0): Setting screen physical size to 169 x 127
[  7179.096] (II) config/udev: Adding input device Power Button
(/dev/input/event1)
[  7179.096] (**) Power Button: Applying InputClass "evdev keyboard catchall"


Snippet from dmesg (same time):
[ 7140.354544] type=1006 audit(1390711184.643:8): pid=4169 uid=0 old
auid=4294967295 new auid=1000 old ses=4294967295 new ses=7 res=1
[ 7147.830641] [drm:atom_op_jump] *ERROR* atombios stuck in loop for more than
5secs aborting
[ 7147.830643] [drm:atom_execute_table_locked] *ERROR* atombios stuck executing
D368 (len 116, WS 0, PS 0) @ 0xD3D1
[ 7152.840265] [drm:atom_op_jump] *ERROR* atombios stuck in loop for more than
5secs aborting
[ 7152.840267] [drm:atom_execute_table_locked] *ERROR* atombios stuck executing
D368 (len 116, WS 0, PS 0) @ 0xD3D1
[ 7157.849874] [drm:atom_op_jump] *ERROR* atombios stuck in loop for more than
5secs aborting
[ 7157.849876] [drm:atom_execute_table_locked] *ERROR* atombios stuck executing
D368 (len 116, WS 0, PS 0) @ 0xD3D1
[ 7162.932450] [drm:atom_op_jump] *ERROR* atombios stuck in loop for more than
5secs aborting
[ 7162.932453] [drm:atom_execute_table_locked] *ERROR* atombios stuck executing
D368 (len 116, WS 0, PS 0) @ 0xD3D1
[ 7167.950130] [drm:atom_op_jump] *ERROR* atombios stuck in loop for more than
5secs aborting
[ 7167.950132] [drm:atom_execute_table_locked] *ERROR* atombios stuck executing
D368 (len 116, WS 0, PS 0) @ 0xD3D1
[ 7172.965693] [drm:atom_op_jump] *ERROR* atombios stuck in loop for more than
5secs aborting
[ 7172.965696] [drm:atom_execute_table_locked] *ERROR* atombios stuck executing
D368 (len 116, WS 0, PS 0) @ 0xD3D1
[ 7178.257075] [drm:atom_op_jump] *ERROR* atombios stuck in loop for more than
5secs aborting
[ 7178.257078] [drm:atom_execute_table_locked] *ERROR* atombios stuck executing
D368 (len 116, WS 0, PS 0) @ 0xD3D1
[ 7307.075602] [drm:atom_op_jump] *ERROR* atombios stuck in loop for more than
5secs aborting
[ 7307.075604] [drm:atom_execute_table_locked] *ERROR* atombios stuck executing
D368 (len 116, WS 0, PS 0) @ 0xD3D1
[ 7329.660921] [drm:atom_op_jump] *ERROR* atombios stuck in loop for more than
5secs aborting
[ 7329.660924] [drm:atom_execute_table_locked] *ERROR* atombios stuck executing
D368 (len 116, WS 0, PS 0) @ 0xD3D1

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 4134 bytes --]

[-- Attachment #2: Type: text/plain, Size: 159 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2014-01-26  5:10 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-09  1:46 [Bug 73420] New: [radeonsi] X.org fails to start due to atombios stucking on HAWAII (Sapphire r9 290x Tri-X) bugzilla-daemon
2014-01-09  1:47 ` [Bug 73420] " bugzilla-daemon
2014-01-09  1:58 ` [Bug 73420] [HAWAII] X.org fails to start due to atombios stucking " bugzilla-daemon
2014-01-09 14:22 ` bugzilla-daemon
2014-01-09 18:19 ` bugzilla-daemon
2014-01-10 21:33 ` bugzilla-daemon
2014-01-10 21:52 ` bugzilla-daemon
2014-01-10 21:57 ` bugzilla-daemon
2014-01-21 23:12 ` bugzilla-daemon
2014-01-26  5:10 ` bugzilla-daemon [this message]
2014-01-27 23:34 ` bugzilla-daemon
2014-01-27 23:37 ` bugzilla-daemon
2014-01-28 23:19 ` bugzilla-daemon
2014-01-29  5:20 ` [Bug 73420] [HAWAII] atombios stuck executing errors bugzilla-daemon
2014-01-29  5:21 ` bugzilla-daemon
2014-01-29 21:16 ` bugzilla-daemon
2014-01-29 21:19 ` bugzilla-daemon
2014-01-29 21:39 ` bugzilla-daemon
2014-01-30  0:19 ` bugzilla-daemon
2014-01-30 14:54 ` bugzilla-daemon
2014-01-30 15:57 ` bugzilla-daemon
2014-01-30 16:17 ` bugzilla-daemon
2014-01-30 23:21 ` 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-73420-502-rc8j2QR7qS@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