public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andreas Stenglein <a.stenglein@gmx.net>
To: Ryan Richter <ryan@solarneutrino.net>
Cc: Dave Airlie <airlied@gmail.com>,
	linux-kernel@vger.kernel.org, dri-devel@lists.sourceforge.net
Subject: Re: DRI lockup on R200, 2.6.11.7
Date: Sat, 14 May 2005 12:50:51 +0200	[thread overview]
Message-ID: <20050514105051.GC8956@buche.local> (raw)
In-Reply-To: <20050511162159.GA19046@tau.solarneutrino.net> (from ryan@solarneutrino.net on Mi, Mai 11, 2005 at 18:21:59 +0200)

Am 11.05.2005 18:21:59 schrieb(en) Ryan Richter:

> Another one today, but it's a little different now.  I got to see this
> happen from the beginning today.  A few minutes before the crash, 3D
> operations become very slow.  When X hangs, it's now doing this:
> 

when comparing radeon_tcl.c with r200_tcl.c I noticed:

in radeon_tcl.c:
#define CLOSE_ELTS()  RADEON_NEWPRIM( rmesa )


in r200_tcl.c:
#define CLOSE_ELTS()                            \
do {                                            \
   if (0) R200_NEWPRIM( rmesa );                \
}                                               \
while (0)


Does the lockup occur when disabling hw-tcl?

best regards,
Andreas

  reply	other threads:[~2005-05-14  9:39 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
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 [this message]
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=20050514105051.GC8956@buche.local \
    --to=a.stenglein@gmx.net \
    --cc=airlied@gmail.com \
    --cc=dri-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ryan@solarneutrino.net \
    /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