[tlinux-users:07703] Re: sudden power off on SUSE 10.0

I've had this happen a couple times in the past week with a Toshiba P15.  Identical symptoms ... no-notice shutdown.

My machine is running Fedora Core 4, so I'm suspecting that the OS doesn't make a difference.

I looked through /var/log/messages.n and I do see some overheat notifications -- ironically at times like 4AM when the system is idling except for the automatic update cron job.  Isaac, do your logs tell you anything?



On Sun, 26 Feb 2006 16:46:55 -0500
"Isaac Charles" <[email protected]> wrote:

> Greetings everyone.  I looked for a similar situation in the archives, but I
> couldn't find any.
> 
> I installed SUSE 10.0 a couple months ago and have been plagued with a weird
> sudden poweroff ever since.
> 
> First, the details:
> 
> I'm using a Toshiba Satellite 1135-S1554 (1130 series) with an Intel P4-M
> 2.2 GHz.  512 MB of ram.
> 
> I believe the linux kernel has been 2.6.13 from the start, but I could be
> wrong.  It's currently 2.6.13-15.8.  I allow SUSE to make whatever updates
> it wants, but this is not a problem that has suddenly appeared after some or
> other patch.
> 
> Everything else is whatever SUSE installed as part of a normal
> installation.  I use KDE, and the battery meter reads correctly at all
> times.  Even hibernate works fine!
> 
> SO!  Here's the problem.  While I'm working, the machine will, at an
> arbitrary time, suddenly poweroff.  No shutdown process.  No warnings.  One
> moment it's fine, the next it's turned off.  This is almost always when the
> machine is running on battery, although I've actually observed it ONCE while
> the machine was plugged in.
> 
> At first, of course, I thought the battery meter was showing the wrong
> information, but boots back and forth between linux and windows showed that
> the KDE battery meter is reading correctly and that there was no shortage of
> power.
> 
> My second theory was that the machine was overheating for some reason.  It
> didn't *feel* hot, but one never knows if the processor is overheating for
> lack of enough thermal compound or something.  The first couple times I saw
> the shutdown were under heavy load, so that seemed a reasonable theory.
> With further experience, though, heat does not seem to be an issue.
>