[Bug 73420] New: [radeonsi] X.org fails to start due to atombios stucking on HAWAII (Sapphire r9 290x Tri-X)

List overview All Threads
Download

newer

older

exynos_hdmi.c fails to build with...

[PATCH v2 0/5] add a TDA998x CODEC

bugzilla-daemon＠freedesktop.org

9 Jan 2014 9 Jan '14

1:46 a.m.

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

Priority: medium Bug ID: 73420 Assignee: dri-devel@lists.freedesktop.org Summary: [radeonsi] X.org fails to start due to atombios stucking on HAWAII (Sapphire r9 290x Tri-X) Severity: major Classification: Unclassified OS: Linux (All) Reporter: luziphermcleod@yahoo.ie Hardware: x86-64 (AMD64) Status: NEW Version: git Component: Drivers/Gallium/radeonsi Product: Mesa

Created attachment 91727 --> https://bugs.freedesktop.org/attachment.cgi?id=91727&action=edit dmesg

Observation: ============

System starts up fine (80x25 text mode), radeon module gets loaded and switches the console to high resolution. My system doesn't use a grahical splash screen or a graphical login manager and instead boots to a text-mode console. When I try to start X (startx), the screen blanks out (it stays active and there is a non-blinking cursor visible in the upper left corner) and pressing Num or CapsLock doesn't trigger the keyboard light for a few seconds. Then the cursor vanishes and Num/CapsLock work again. When pressing Ctrl-Alt-F2 it takes another few seconds before the switch to the text-mode console happens - there everything works normally again.

Dmesg shows a few of these in 5second intervals (see attachment): [ 635.088465] [drm:atom_op_jump] *ERROR* atombios stuck in loop for more than 5secs aborting [ 635.088467] [drm:atom_execute_table_locked] *ERROR* atombios stuck executing D368 (len 116, WS 0, PS 0) @ 0xD3D1

Driver Stack Details: =====================

1) Kernel: Vanilla 3.13.0-rc7 2) libdrm: git (commit e8cbc579651ef55274763c67acb366dd4155e0ce radeon: fix sumo2 pci id) 3) mesa: git (commit e8ff08edd823ddf6b0e07ef84d2ba8afc3abbc34 mesa: Namespace qualify fma to override ambiguity with fma from math.h) 4) Xorg-server: 1.15.0 5) xf86-video-ati: git (commit bcc454ea2fb239e13942270faec7801270615b9c radeon/exa: Always use a scratch surface for UTS to vram) 6) glamor: 0.5.1-r1 7) llvm: 3.5svn (updated on 09.01.2013)

Hardware Configuration: =====================

Graphics Card: Hawaii XT, Sapphire Radeon R9 290X Tri-X OC Battlefield 4 Edition, 4GB GDDR5, 2x DVI, HDMI, DisplayPort, full retail (11226-00-50G) Processor: Core i7-965 (LGA 1366) Mainboard: Asus P6T Deluxe RAM: 6GB

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

Attachments:

attachment.html (text/html — 3.9 KB)

Show replies by date

bugzilla-daemon＠freedesktop.org

9 Jan 9 Jan

1:47 a.m.

New subject: [Bug 73420] [radeonsi] X.org fails to start due to atombios stucking on HAWAII (Sapphire r9 290x Tri-X)

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

--- Comment #1 from Luzipher luziphermcleod@yahoo.ie --- Created attachment 91728 --> https://bugs.freedesktop.org/attachment.cgi?id=91728&action=edit Xorg.0.log

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

bugzilla-daemon＠freedesktop.org

1:58 a.m.

New subject: [Bug 73420] [HAWAII] X.org fails to start due to atombios stucking (Sapphire r9 290x Tri-X)

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

Michel Dänzer michel@daenzer.net changed:

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

bugzilla-daemon＠freedesktop.org

2:22 p.m.

New subject: [Bug 73420] [HAWAII] X.org fails to start due to atombios stucking (Sapphire r9 290x Tri-X)

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

--- Comment #2 from Alex Deucher agd5f@yahoo.com --- It looks like X is picking 640x480 since it's the only common mode across all the connected monitors. Does it work properly if you start X with 1 monitor and then attach the others after X has started?

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

bugzilla-daemon＠freedesktop.org

6:19 p.m.

New subject: [Bug 73420] [HAWAII] X.org fails to start due to atombios stucking (Sapphire r9 290x Tri-X)

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

--- Comment #3 from Luzipher luziphermcleod@yahoo.ie --- I disconnected all but one monitor from the card, but the issue is still there. Note that I don't even get a 640x480 screen, the screen is just black and for the first 5 seconds there is the non-blinking text-mode cursor in the upper left corner and the computer is not responding at all.

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

bugzilla-daemon＠freedesktop.org

10 Jan 10 Jan

9:33 p.m.

New subject: [Bug 73420] [HAWAII] X.org fails to start due to atombios stucking (Sapphire r9 290x Tri-X)

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

--- Comment #4 from Alex Deucher agd5f@yahoo.com --- Please attach a copy of your vbios. To get a copy of your vbios:

(as root) (use lspci to get the bus id) cd /sys/bus/pci/devices/<pci bus id> echo 1 > rom cat rom > /tmp/vbios.rom echo 0 > rom

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

bugzilla-daemon＠freedesktop.org

9:52 p.m.

New subject: [Bug 73420] [HAWAII] X.org fails to start due to atombios stucking (Sapphire r9 290x Tri-X)

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

--- Comment #5 from Luzipher luziphermcleod@yahoo.ie --- Created attachment 91844 --> https://bugs.freedesktop.org/attachment.cgi?id=91844&action=edit vbios.rom

The vbios.rom acquired as instructed via /sys

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

bugzilla-daemon＠freedesktop.org

9:57 p.m.

New subject: [Bug 73420] [HAWAII] X.org fails to start due to atombios stucking (Sapphire r9 290x Tri-X)

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

--- Comment #6 from Luzipher luziphermcleod@yahoo.ie --- Created attachment 91845 --> https://bugs.freedesktop.org/attachment.cgi?id=91845&action=edit rom acquired via GPU-Z

Note that the ROM-file acquired by GPU-Z is twice the size of the ROM acquired via /sys. GPU-Z also reports: Device ID: 1002 - 67B0 Subvendor: Sapphire/PCPartner (174B) BIOS Version: 015.042.000.000.000000 (113-C6710100-O05)

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

bugzilla-daemon＠freedesktop.org

21 Jan 21 Jan

11:12 p.m.

New subject: [Bug 73420] [HAWAII] X.org fails to start due to atombios stucking (Sapphire r9 290x Tri-X)

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

--- Comment #7 from Luzipher luziphermcleod@yahoo.ie --- I retestet this on current drm-next (commit 8c9b2e322d5c9b4e77fd308984ea303de4b63e1c ), which includes the drm-next-3.14 pull for radeon from agd5f. The problem persists.

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

bugzilla-daemon＠freedesktop.org

26 Jan 26 Jan

5:10 a.m.

New subject: [Bug 73420] [HAWAII] X.org fails to start due to atombios stucking (Sapphire r9 290x Tri-X)

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.

bugzilla-daemon＠freedesktop.org

27 Jan 27 Jan

11:34 p.m.

New subject: [Bug 73420] [HAWAII] X.org fails to start due to atombios stucking (Sapphire r9 290x Tri-X)

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

--- Comment #9 from Alex Deucher agd5f@yahoo.com --- Created attachment 92893 --> https://bugs.freedesktop.org/attachment.cgi?id=92893&action=edit possible fix

Does the attached patch help?

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

bugzilla-daemon＠freedesktop.org

11:37 p.m.

New subject: [Bug 73420] [HAWAII] X.org fails to start due to atombios stucking (Sapphire r9 290x Tri-X)

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

Alex Deucher agd5f@yahoo.com changed:

--- Comment #10 from Alex Deucher agd5f@yahoo.com --- Created attachment 92894 --> https://bugs.freedesktop.org/attachment.cgi?id=92894&action=edit possible fix

corrected patch.

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

bugzilla-daemon＠freedesktop.org

28 Jan 28 Jan

11:19 p.m.

New subject: [Bug 73420] [HAWAII] X.org fails to start due to atombios stucking (Sapphire r9 290x Tri-X)

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

--- Comment #11 from Luzipher luziphermcleod@yahoo.ie --- Unfortunately the patch (corrected version) doesn't help. I applied the patch to the drm-next kernel I cloned on 2014-01-21 (see comment above), resulting version was 3.13.0-rc8-15136-g8c9b2e3-dirty. The dmesg messages are still the same, so I won't repost them.

And thanks for taking a look, Alex ! :-)

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

bugzilla-daemon＠freedesktop.org

29 Jan 29 Jan

5:20 a.m.

New subject: [Bug 73420] [HAWAII] atombios stuck executing errors

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

Alex Deucher agd5f@yahoo.com changed:

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

bugzilla-daemon＠freedesktop.org

5:21 a.m.

New subject: [Bug 73420] [HAWAII] atombios stuck executing errors

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

--- Comment #12 from Alex Deucher agd5f@yahoo.com --- Created attachment 92966 --> https://bugs.freedesktop.org/attachment.cgi?id=92966&action=edit possible fix

The atombios errors are harmless, but the attached patch will prevent them from happening.

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

bugzilla-daemon＠freedesktop.org

9:16 p.m.

New subject: [Bug 73420] [HAWAII] atombios stuck executing errors

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

--- Comment #13 from Luzipher luziphermcleod@yahoo.ie --- The last patch helps, no more messages and the computer doesn't hang completely for several seconds (I wouldn't exactly say that's harmless ;-) ). Thanks for the fix !

I detected a few different error messages when checking dmesg: [drm:radeon_atom_get_leakage_vddc_based_on_leakage_params] *ERROR* Unknown table version 3, 1

Do those warrant a new bugreport ?

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

bugzilla-daemon＠freedesktop.org

9:19 p.m.

New subject: [Bug 73420] [HAWAII] atombios stuck executing errors

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

--- Comment #14 from Alex Deucher agd5f@yahoo.com --- (In reply to comment #13)

...

I detected a few different error messages when checking dmesg: [drm:radeon_atom_get_leakage_vddc_based_on_leakage_params] *ERROR* Unknown table version 3, 1

Do those warrant a new bugreport ?

Yes, please open a new bug report for those.

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

bugzilla-daemon＠freedesktop.org

9:39 p.m.

New subject: [Bug 73420] [HAWAII] atombios stuck executing errors

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

--- Comment #15 from Alex Deucher agd5f@yahoo.com --- Created attachment 93015 --> https://bugs.freedesktop.org/attachment.cgi?id=93015&action=edit possible fix

(In reply to comment #13)

...

I detected a few different error messages when checking dmesg: [drm:radeon_atom_get_leakage_vddc_based_on_leakage_params] *ERROR* Unknown table version 3, 1

This patch should fix this problem.

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

bugzilla-daemon＠freedesktop.org

30 Jan 30 Jan

12:19 a.m.

New subject: [Bug 73420] [HAWAII] atombios stuck executing errors

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

--- Comment #16 from Luzipher luziphermcleod@yahoo.ie --- Yes, that patch worked, no more messages. I still get no accel though ("RADEON(0): GPU accel disabled or not working, using shadowfb for KMS"), but I guess I need to investigate that further first - unless you have a quick idea ?

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

bugzilla-daemon＠freedesktop.org

2:54 p.m.

New subject: [Bug 73420] [HAWAII] atombios stuck executing errors

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

--- Comment #17 from Alex Deucher agd5f@yahoo.com --- (In reply to comment #16)

...

Yes, that patch worked, no more messages. I still get no accel though ("RADEON(0): GPU accel disabled or not working, using shadowfb for KMS"), but I guess I need to investigate that further first - unless you have a quick idea ?

Acceleration is currently disabled by default on hawaii as it's unstable for a lot of apps. You can force it on with Option "NoAccel" "false" in the device section of your xorg conf, but you'll see gpu hangs.

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

bugzilla-daemon＠freedesktop.org

3:57 p.m.

New subject: [Bug 73420] [HAWAII] atombios stuck executing errors

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

--- Comment #18 from Luzipher luziphermcleod@yahoo.ie --- Ah ok, I didn't know that. Thanks for the info - I'll try the option and see how it goes ;-)

Unrealted to the acceleration I discovered another error message in my dmesg: [drm:ci_dpm_set_power_state] *ERROR* ci_upload_dpm_level_enable_mask failed Should I report that in a new bug ? (I should really stop hijacking this bug, sorry)

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

bugzilla-daemon＠freedesktop.org

4:17 p.m.

New subject: [Bug 73420] [HAWAII] atombios stuck executing errors

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

--- Comment #19 from Alex Deucher agd5f@yahoo.com --- (In reply to comment #18)

...

Ah ok, I didn't know that. Thanks for the info - I'll try the option and see how it goes ;-)

Unrealted to the acceleration I discovered another error message in my dmesg: [drm:ci_dpm_set_power_state] *ERROR* ci_upload_dpm_level_enable_mask failed Should I report that in a new bug ? (I should really stop hijacking this bug, sorry)

Yes, open a new bug for the dpm stuff. In the new bug please note whether this is new after applying attachment 93015 or if this was always there.

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

bugzilla-daemon＠freedesktop.org

11:21 p.m.

New subject: [Bug 73420] [HAWAII] atombios stuck executing errors

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

Luzipher luziphermcleod@yahoo.ie changed:

--- Comment #20 from Luzipher luziphermcleod@yahoo.ie --- New bug for the dpm issues is: https://bugs.freedesktop.org/show_bug.cgi?id=74250

The patch from attachement 93015 causes the message about ci_upload_dpm_level_enable_mask failing (the message does not appear without the patch).

I'm changing status to resolved fixed, as the patch for the original issue is already committed and in drm-next.

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

4099

Age (days ago)

4120

Last active (days ago)

dri-devel@lists.freedesktop.org

22 comments

1 participants

tags (0)

participants (1)

bugzilla-daemon＠freedesktop.org