public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: Dave Airlie <airlied@linux.ie>
Cc: pbadari@us.ibm.com, linux-kernel@vger.kernel.org, hugh@veritas.com
Subject: Re: 2.6.14 X spinning in the kernel
Date: Mon, 14 Nov 2005 18:57:51 -0800	[thread overview]
Message-ID: <20051114185751.795b8a3d.akpm@osdl.org> (raw)
In-Reply-To: <Pine.LNX.4.58.0511150247160.24064@skynet>

Dave Airlie <airlied@linux.ie> wrote:
>
> 
> >
> > 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.
> 
> Yes invariably the GPU has crashed and isn't responding to anything.

But radeon_do_wait_for_idle() and radeon_do_wait_for_fifo() have timeouts. 
Should Badari have waited longer?

> 
> Also what X was doing etc at the time is invalulable info..
> 

And whether a particualr kernel version introduced this behaviour.

  reply	other threads:[~2005-11-15  2:58 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-14 23:51 2.6.14 X spinning in the kernel Badari Pulavarty
2005-11-15  0:17 ` Andrew Morton
2005-11-15  0:52   ` Badari Pulavarty
2005-11-15  1:30     ` Andrew Morton
2005-11-15  2:48       ` Dave Airlie
2005-11-15  2:57         ` Andrew Morton [this message]
2005-11-15  3:02           ` Dave Airlie
2005-11-15 22:50         ` Badari Pulavarty
2005-11-15  3:10       ` Dave Jones
2005-11-15 22:49       ` Badari Pulavarty
2005-11-16 21:07         ` Max Krasnyansky
2005-11-16 21:52           ` Badari Pulavarty
2005-11-16 22:11             ` Lee Revell
2005-11-16 22:37               ` Badari Pulavarty
2005-11-16 22:42             ` Dave Airlie
2005-11-16 23:27               ` Badari Pulavarty
2005-11-17  0:10               ` Badari Pulavarty
2005-11-16 15:24 ` Pasi Savolainen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20051114185751.795b8a3d.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=airlied@linux.ie \
    --cc=hugh@veritas.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pbadari@us.ibm.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox