From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@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 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============2017984300==" Return-path: Received: from culpepper.freedesktop.org (unknown [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id EC547FA80F for ; Sat, 25 Jan 2014 21:10:26 -0800 (PST) In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: dri-devel-bounces@lists.freedesktop.org Errors-To: dri-devel-bounces@lists.freedesktop.org To: dri-devel@lists.freedesktop.org List-Id: dri-devel@lists.freedesktop.org --===============2017984300== Content-Type: multipart/alternative; boundary="1390713026.FfBe478d0.23858"; charset="us-ascii" --1390713026.FfBe478d0.23858 Date: Sun, 26 Jan 2014 05:10:26 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" https://bugs.freedesktop.org/show_bug.cgi?id=73420 --- Comment #8 from Luzipher --- 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. --1390713026.FfBe478d0.23858 Date: Sun, 26 Jan 2014 05:10:26 +0000 MIME-Version: 1.0 Content-Type: text/html; charset="UTF-8"

Comment # 8 on bug 73420 from 
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.
--1390713026.FfBe478d0.23858-- --===============2017984300== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel --===============2017984300==--