From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: James Cloos <cloos@jhcloos.com>
Cc: linux-fbdev-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
"David S. Miller" <davem@davemloft.net>,
Krzysztof Halasa <khc@pm.waw.pl>
Subject: Re: [Linux-fbdev-devel] radeonfb lockup in .28-rc (bisected)
Date: Tue, 04 Nov 2008 07:22:34 +1100 [thread overview]
Message-ID: <1225743754.8004.260.camel@pasglop> (raw)
In-Reply-To: <m33ai8akoo.fsf@lugabout.jhcloos.org>
On Mon, 2008-11-03 at 10:33 -0500, James Cloos wrote:
> >>>>> "Benjamin" == Benjamin Herrenschmidt <benh@kernel.crashing.org> writes:
>
> >> is in play. It is probably spinning through all of the 2000000 possible
> >> udelay(10) calls. I don't think I ever gave it twenty seconds before
> >> giving up. And certainly not forty seconds, if the freeze happens after
> >> setting the DST_Y_X register.
>
> Benjamin> Well, setting DST_Y_X is what triggers the transfer. The above
> Benjamin> means that the FIFO isn't emptying (ie, the engine is locked up).
>
> I gave it another try over the weekend and let it sit for five minutes.
> The reset message never appeared.
Because it's probably going to lockup trying to display it :-) I need to
make that stuff a bit more robust, by disabling acceleration if the
engine locks up for example.
> Again, that is fine by me. Otherwise I'll just leave the #if0 commit
> in my compile clone.
Allright, we'll see what I come up with, and at worst, I'll just revert
the whole thing.
Ben.
prev parent reply other threads:[~2008-11-03 20:22 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-27 23:45 radeonfb lockup in .28-rc (bisected) James Cloos
2008-10-28 0:00 ` David Miller
2008-10-28 1:46 ` James Cloos
2008-10-28 0:05 ` Benjamin Herrenschmidt
2008-10-28 1:50 ` James Cloos
2008-10-28 9:24 ` James Cloos
2008-11-02 21:48 ` [Linux-fbdev-devel] " Benjamin Herrenschmidt
2008-11-03 7:01 ` Paul Collins
2008-11-03 7:34 ` Benjamin Herrenschmidt
2008-11-04 6:49 ` Paul Collins
2008-11-04 21:33 ` Benjamin Herrenschmidt
2008-11-06 6:00 ` Paul Collins
2008-11-06 7:52 ` Benjamin Herrenschmidt
2008-11-04 21:36 ` Benjamin Herrenschmidt
2008-11-05 8:39 ` Benjamin Herrenschmidt
2008-11-05 10:28 ` Paul Collins
2008-11-05 20:31 ` Benjamin Herrenschmidt
2008-11-06 3:49 ` Benjamin Herrenschmidt
2008-11-06 4:49 ` Paul Collins
2008-11-03 15:33 ` James Cloos
2008-11-03 20:22 ` Benjamin Herrenschmidt [this message]
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=1225743754.8004.260.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=akpm@linux-foundation.org \
--cc=cloos@jhcloos.com \
--cc=davem@davemloft.net \
--cc=khc@pm.waw.pl \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).