From: Knut Petersen <Knut_Petersen@t-online.de>
To: linux-fbdev-devel@lists.sourceforge.net
Subject: Re: atyfb & lockups
Date: Wed, 30 Nov 2005 07:48:25 +0100 [thread overview]
Message-ID: <438D4B39.5090208@t-online.de> (raw)
In-Reply-To: <1133329905.16726.69.camel@gaston>
>I have an old PowerBook Wallstreet I here with a Rage LT-G. I've been
>booting it from Open Firmware instead of MacOS lately (thus didn't give
>a chance to the MacOS driver to do it's own tweaking of the chip) and
>the machine has been reliably locking up on me. Solid lockups. I finally
>figured out that the lockups appear to be atyfb related and that booting
>with video=atyfb:noaccel fixes it.
>It seems that when it's lockup, the whole machine is down, that is it
>won't take interrupts to get to the xmon low level debugger nor
>anything, thus I suspect the PCI is locked up.
>
>
Well, there are other possibilities.
When does the lockup occure? Immediately when booting? Later? During
start of
xdm/kdm? Random?
>Are there any ideas of where to look for the source of the problem ?
>
>
>
I would start to investigate the case by instrumenting and extending the
fb_sync code.
Try to include code there that resets the chip and switches to the
noaccel counterparts of the
accelerated functions when a timeout occures. That way you should have a
chance to resume.
Is the timeout counter ok? Maybe you should decrease/increase it. If
switching to
the noaccel function works, include a register dump before resetting the
chip, use show_trace()
etc for further debugging.
cu,
knut
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
next prev parent reply other threads:[~2005-11-30 6:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-30 5:51 atyfb & lockups Benjamin Herrenschmidt
2005-11-30 6:48 ` Knut Petersen [this message]
2005-12-02 2:14 ` Benjamin Herrenschmidt
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=438D4B39.5090208@t-online.de \
--to=knut_petersen@t-online.de \
--cc=linux-fbdev-devel@lists.sourceforge.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;
as well as URLs for NNTP newsgroup(s).