Re: 2.6.14 X spinning in the kernel

[Dave Jones <davej@redhat.com>]

On Mon, Nov 14, 2005 at 05:30:37PM -0800, Andrew Morton wrote:

 > > CPU0:
 > > ffffffff8053c750 0000000000000000 00000000000018ff ffff81011c9a4230
 > >        ffff81011c9a4000 ffffffff8053c788 ffffffff8026de8f
 > > ffffffff8053c7a8
 > >        ffffffff80119591 ffffffff8053c7a8
 > > Call Trace: <IRQ> <ffffffff8026de8f>{showacpu+47}
 > > <ffffffff80119591>{smp_call_function_interrupt+81}
 > >        <ffffffff8010e968>{call_function_interrupt+132}  <EOI>
 > > <ffffffff880fa225>{:radeon:radeon_do_wait_for_idle+117}
 > >        <ffffffff880fa236>{:radeon:radeon_do_wait_for_idle+134}
 > >        <ffffffff880fa590>{:radeon:radeon_do_cp_idle+336}
 > > <ffffffff880fc215>{:radeon:radeon_do_release+85}
 > >        <ffffffff88104369>{:radeon:radeon_driver_pretakedown+9}
 > >        <ffffffff802783aa>{drm_takedown+74}
 > 
 > ah-hah.  We've had machines stuck in radeon_do_wait_for_idle() before.  In
 > fact, my workstation was doing it a year or two back.
 > 
 > Are you able to identify the most recent kernel which didn't do this?
 > 
 > David, is there a common cause for this?  ISTR that it's a semi-FAQ.

We've seen a few reports of this in the Fedora bugzilla over the
last year or so too. It seems to come and go.  The best explanation
I've heard so far is "The GPU got really confused".

		Dave