From: Dave Airlie <airlied@linux.ie>
To: Andrew Morton <akpm@osdl.org>
Cc: pbadari@us.ibm.com, linux-kernel@vger.kernel.org, hugh@veritas.com
Subject: Re: 2.6.14 X spinning in the kernel
Date: Tue, 15 Nov 2005 03:02:04 +0000 (GMT) [thread overview]
Message-ID: <Pine.LNX.4.58.0511150258420.24064@skynet> (raw)
In-Reply-To: <20051114185751.795b8a3d.akpm@osdl.org>
> > 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?
They timeout, and X usually goes straight back in there again, I can't
remember the codepath exactly at this stage but it just goes round and
round until you kick the machine..
in theory X should probably deal with the situation better... I think it
might be able to at least gracefully die or reset the chip...
> > Also what X was doing etc at the time is invalulable info..
> >
>
> And whether a particualr kernel version introduced this behaviour.
Yes, usually if a kernel introduced it it is because I've done something
really dumb (shouldn't happen too often and with radeons we usually catch
that before stable releases), or because the X server wasn't using DRI
before due to a too old DRM and suddenly the new DRM appears in the kernel
and it uses it ...
There is one known issue with some later version of X on radeons crashing
on PCI GART setups, benh was cooking a patch for X, it isn't something we
can fix in the kernel..
Dave.
--
David Airlie, Software Engineer
http://www.skynet.ie/~airlied / airlied at skynet.ie
Linux kernel - DRI, VAX / pam_smb / ILUG
next prev parent reply other threads:[~2005-11-15 3:02 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-14 23:51 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
2005-11-15 3:02 ` Dave Airlie [this message]
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=Pine.LNX.4.58.0511150258420.24064@skynet \
--to=airlied@linux.ie \
--cc=akpm@osdl.org \
--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
all inboxes | Powered by JetHome®