mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Dave Airlie <airlied@linux.ie>
To: Matti Aarnio <matti.aarnio@zmailer.org>
Cc: Andrew Morton <akpm@osdl.org>, linux-kernel@vger.kernel.org
Subject: Re: [bk tree] DRM add a version check.. for 2.6.12 (distro kernel maintainers + drm users plz read also...)
Date: Thu, 7 Apr 2005 14:00:07 +0100 (IST)	[thread overview]
Message-ID: <Pine.LNX.4.58.0504071357020.25035@skynet> (raw)
In-Reply-To: <20050407125345.GI3858@mea-ext.zmailer.org>

>
> My lattest runs were with 2 days old FC development (a.k.a. "bleeding edge")
> environment with  xorg-11-** of same age.  Then I noticed that these DRM
> patches didn't make it into  kernel-smp-2.6.11-1.1226_FC4.i686.rpm,
> and I made 2.6.12-rc2 -- just in case it had fixed the problem...
>

well these patches shouldn't really affect it..

> Could the card-lockups be recovered in a bit nicer way ?
> (And detected, too!)

In theory yes, but there isn't really anything you can do except reboot,
as usually the CP (command processor) is hung, and you have to do a full
GPU reset, I can't imagine X or Linux consoles surviving it too well...
ATI have a VPU Recover in their windows driver which does it.. but they
know their cards a bit better than we do..

it might be worth turning Render acceleration off Option "RenderAccel"
"No" in xorg.conf and see if it gets any stabler...

Dave.

-- 
David Airlie, Software Engineer
http://www.skynet.ie/~airlied / airlied at skynet.ie
Linux kernel - DRI, VAX / pam_smb / ILUG


  reply	other threads:[~2005-04-07 13:00 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-28 11:40 Dave Airlie
2005-04-07 11:49 ` Matti Aarnio
2005-04-07 12:38   ` Dave Airlie
2005-04-07 12:53     ` Matti Aarnio
2005-04-07 13:00       ` Dave Airlie [this message]
2005-04-09  8:50         ` Matti Aarnio

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.0504071357020.25035@skynet \
    --to=airlied@linux.ie \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matti.aarnio@zmailer.org \
    /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®