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

From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 73420] New: [radeonsi] X.org fails to start due to atombios stucking on HAWAII (Sapphire r9 290x Tri-X)
Date: Thu, 09 Jan 2014 01:46:43 +0000	[thread overview]
Message-ID: <bug-73420-502@http.bugs.freedesktop.org/> (raw)

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

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.

[-- Attachment #1.2: Type: text/html, Size: 3947 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