[BUG] 3.2-rcX radeon KMS system freeze

[BUG] 3.2-rcX radeon KMS system freeze

[Bob Tracy]

I've been trying to get KDE4 running on an Alpha, and I have things to
the point where FreeNX (non-KMS) KDE4 sessions work just fine.  When I
try a KDE4 session on the console with 3.2-rc[1-2] kernels and KMS
enabled, the KDE4 splash screen appears, and the expected left-to-right
fade-in of the five startup progress icons happens.  As soon as the
fifth icon (the big "K") is done appearing, I assume plasma-desktop
starts, and that's where the system locks-up solid.  Can't switch
virtual consoles, can't login remotely, etc.: system doesn't even
respond to pings.  Have to hit the reset switch to recover.

After rebooting, there's nothing to be found in any of the X11 and/or
syslog files as far as "Oops" messages or other errors.

Similar bad things happen when I try to test Gnome-3 sessions (KMS
required for non-fallback mode).  With FreeNX, the best I can do is test
Gnome-3 fallback mode (Gnome-2).

Apologies for the less-than-useful bug report.  If there's anything I
can do to generate/capture more diagnostic info, please don't hesitate
to let me know.  I'll be able to try a 3.2-rc3 kernel later today.

--Bob

Re: [BUG] 3.2-rcX radeon KMS system freeze

[Bob Tracy]

On Fri, Nov 25, 2011 at 02:33:51PM -0600, Bob Tracy wrote:
> Apologies for the less-than-useful bug report.  If there's anything I
> can do to generate/capture more diagnostic info, please don't hesitate
> to let me know.  I'll be able to try a 3.2-rc3 kernel later today.

Update for 3.2-rc3.  Logged-in via the kdm-greeter screen, and just as
soon as the kde session initialization started, I toggled back to a
virtual console to see if any error messages were being written there.
The only suspicious thing I saw was *many* messages in syslog of the
form:

<date> <hostname> kernel: do_entUnaUser: 836779 callbacks suppressed

as "virtuoso-t" started running.  I decided to chance switching to the
X11 session, and it ran for a little while before the system froze.  The
freeze "feels" like an out-of-memory condition, which could explain the
lack of error messages.  Things got really slow just before the system
became completely unresponsive.

--Bob