public inbox for linuxppc-dev@ozlabs.org 
 help / color / mirror / Atom feed
From: "Joseph P. Garcia" <jpgarcia@execpc•com>
To: linuxppc-dev@lists•linuxppc.org
Subject: PMU panic in 2.4bk
Date: Mon, 29 Jan 2001 16:55:20 -0600	[thread overview]
Message-ID: <01012916552001.05635@momiji> (raw)


I've been recently getting a PMU panic using an unmodified 2.4 kernel from
the bitkeeper rsync.  Looking in via-pmu.c, the issues appears to be known as
a potential problem, and I think I have found that it is.

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?

Thanks.

--
Joseph P. Garcia
http://www.execpc.com/~jpgarcia

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

             reply	other threads:[~2001-01-29 22:55 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-29 22:55 Joseph P. Garcia [this message]
2001-01-30  9:45 ` PMU panic in 2.4bk 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=01012916552001.05635@momiji \
    --to=jpgarcia@execpc$(echo .)com \
    --cc=linuxppc-dev@lists$(echo .)linuxppc.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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