From: Matti Aarnio <matti.aarnio@zmailer.org>
To: Dave Airlie <airlied@linux.ie>
Cc: Matti Aarnio <matti.aarnio@zmailer.org>,
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 15:53:45 +0300 [thread overview]
Message-ID: <20050407125345.GI3858@mea-ext.zmailer.org> (raw)
In-Reply-To: <Pine.LNX.4.58.0504071334560.25035@skynet>
On Thu, Apr 07, 2005 at 01:38:52PM +0100, Dave Airlie wrote:
> > I tried 2.6.12-rc2 which includes this patch, and I get DRM failures
> > here, which causes application and X to hang. (I got failures with 2.6.11
> > also.)
>
> Does the FC-4 test kernel work? There was a bug in X6.8.2 but I think it
> would be fixed in FC-4 test.. I run Xorg CVS on a 9200 with the latest
> kernel and it seems fine... granted I've been able to crash it with
> running a few wierd apps.. I've just had no chance to debug it yet but it
> isn't the common case... maybe I should play tuxracer for a while..
>
> the symptoms are typical of a card lockup, spinning in ioctl forever...
>
> Dave.
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...
Could the card-lockups be recovered in a bit nicer way ?
(And detected, too!)
/Matti Aarnio
next prev parent reply other threads:[~2005-04-07 12:53 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 [this message]
2005-04-07 13:00 ` Dave Airlie
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=20050407125345.GI3858@mea-ext.zmailer.org \
--to=matti.aarnio@zmailer.org \
--cc=airlied@linux.ie \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.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®