[Bug 28671] Seg. fault and Oops with Radeon KMS (v2.6.34) on PPC ATI Radeon AGP r420 JH.

Tue Jun 22 12:32:13 PDT 2010

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

--- Comment #3 from Brett Witherspoon <brett.witherspoon at comcast.net> 2010-06-22 12:32:13 PDT ---
Yes, this does avoids the oops. Thank you. The fb console works just it should.
As you expected there are still some issues with X. The issue is very much like
what I experienced without KMS and X when I was testing. I am not sure if this
is separate issue and another bug report should be filed or not. If so let me
know, but I will report what I have so far here.

Using:
libdrm-2.4.21
mesa-7.8.2
xorg-1.8.1.901
ati-drivers-6.13.0

After starting X I get a cursor and multi-color lines in the background. The
window manager and other apps are started, but are not visible. Attempting to
switch VT will cause the machine to lockup. It also seems that it will also
lockup after a few min even if nothing is done. Xorg.log doesn't have any
errors i can see but dmesg after X is started does have some *ERROR*. I have
attached both. The *ERROR*'s in dmesg are repeated until the machine eventually
locks. I was in a bit of a hurry to get the messages before it locked, so it
only occurs once or twice here. Without KMS the issue is almost the same, but I
get a nasty race condition prior to the lockup.

I will also attempt to get some sort of backtrace if it is helpful. I will need
to re-compile with debuging symbols. libdrm, mesa, xorg, ati-drivers should be
enough? I am not sure if gdb is going to be useful in this case but I am happy
to give it a run tonight.

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.