All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Airlie <airlied@gmail.com>
To: ryantemporary@gmail.com
Cc: linux-kernel@vger.kernel.org, dri-devel@lists.sourceforge.net
Subject: Re: DRI lockup on R200, 2.6.11.7
Date: Thu, 28 Apr 2005 09:22:36 +0100	[thread overview]
Message-ID: <21d7e99705042801227ed5438e@mail.gmail.com> (raw)
In-Reply-To: <20050426202916.GA2635@xarello>

On 4/26/05, foo@porto.bmb.uga.edu <foo@porto.bmb.uga.edu> wrote:
> Using 2.6.11.7, I'm experiencing the same problem as reported here:
> http://lkml.org/lkml/2005/3/12/99
> 
> Except it happens for me after X is running.  X locks up, only the mouse
> pointer moves, X spins doing this:
> 
> --- SIGALRM (Alarm clock) @ 0 (0) ---
> rt_sigreturn(0xe)                       = -1 EBUSY (Device or resource busy)
> ioctl(5, 0x6444, 0)                     = -1 EBUSY (Device or resource busy)
> ioctl(5, 0x6444, 0)                     = -1 EBUSY (Device or resource busy)
> 
> Killing X causes the machine to reset shortly thereafter.  I've seen
> this on ATI Radeon 9200s and 9000 Pros.  X is version 4.3.0.dfsg.1-12.
> 

2.6.12 should fix this, there is patch at:
http://drm.bkbits.net:8080/drm-linus/gnupatch@424260f9PBUdlFvyiQw1maJBKvEtXA

Dave.

  reply	other threads:[~2005-04-28  8:40 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-26 20:29 DRI lockup on R200, 2.6.11.7 foo
2005-04-28  8:22 ` Dave Airlie [this message]
2005-04-28 16:34   ` foo
2005-05-05 18:41   ` Ryan Richter
2005-05-11 16:21   ` Ryan Richter
2005-05-14 10:50     ` Andreas Stenglein
2005-05-14 16:57       ` Ryan Richter
     [not found]         ` <20050514210047.2fff483f.khaqq@free.fr>
     [not found]           ` <20050514191707.GB20921@tau.solarneutrino.net>
     [not found]             ` <20050515115239.GA5773@buche.local>
     [not found]               ` <Pine.LNX.4.58.0505151136310.24826@skynet>
2005-05-17 16:45                 ` Ryan Richter

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=21d7e99705042801227ed5438e@mail.gmail.com \
    --to=airlied@gmail.com \
    --cc=dri-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ryantemporary@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.