linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: "Joseph P. Garcia" <jpgarcia@execpc.com>,
	<linuxppc-dev@lists.linuxppc.org>
Subject: Re: PMU panic in 2.4bk
Date: Tue, 30 Jan 2001 10:45:51 +0100	[thread overview]
Message-ID: <19341225031735.27091@mailhost.mipsys.com> (raw)
In-Reply-To: <01012916552001.05635@momiji>


>
>Symptoms:  upon heavy access to video (fb console or ati/XF4) like scrolling
>or netscape full screen, or heavy access to the hard drive (fsck or huge
>copy), I get 'LCD fire' (melting as some call it).  On once instance, the
>system just powered off after a brief burn/melt.   I know this is what
>happens when the PMU is ignored for too long.
>
>System: standard WallstreetII(PDQ) 300MHz, 384M RAM,  IBM 30G drive (4200rpm
>type)
>
>Anyone know more about this or how it might be fixed?

The PMU driver is interrupt driven. So the only thing supposed to be able
to cause this problem is if interrupts are turned off too long while the
PMU is in the middle of transmitting (or receiving) a message.

One this that may help is to turn ON the IDE "unmask" option with hdparm.
There's no reason to mask interrupts during transfers on recent
controllers (anything more recent than old buggy x86 stuffs), however
this option is OFF by default.

Another possible cause is a kernel crash or hang. If the PMU was
communicating at that time, then you are dead. If you can reproduce the
problem, try running without pmud (thus lowevering the frequency of PMU
requests).

I've seen this problem happening once or twice (with screen melt) on a
friend's machine, and the LCD "melting" is _not_ caused by the PMU
crashing. It's caused by the ATI chip crashing (FIFO issue in the driver
?). Now, it's possible that if xmon tries to display something in the
middle of an XFree accelerated operation, that would cause the ATI chip
to crash.

So my diagnositc is that something is crashing your box, possibly XF4 ATI
driver or atyfb, and this tend to happen while the PMU is talking or
beeing talked to.

If it was a PMU timeout, all you would get would be a brutal shutdown,
not a melting screen.

Ben.


** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

      reply	other threads:[~2001-01-30  9:45 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-29 22:55 PMU panic in 2.4bk Joseph P. Garcia
2001-01-30  9:45 ` 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=19341225031735.27091@mailhost.mipsys.com \
    --to=benh@kernel.crashing.org \
    --cc=jpgarcia@execpc.com \
    --cc=linuxppc-dev@lists.linuxppc.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).