It locked up during memtest? Then you can rule out software. Were there any memory errors reported as it locked up? Did the screen stay up when it locked up? Can you make it through a memtest without it locking up or does it lock up about the same time each time? Processor temp is a good thing to check. As is, as Aaron mention, the caps on the board. If you have another power supply, I'd try that too. In fact, I've been dealing with a computer recently that locked up similarly due to bad, but generally sufficient, power.

Good luck,
Joel

Knowles, Christopher wrote:
It's tracking Testing. (remember, it's a demo/test/temptation box, not production)

Just ran memtest and durned if the thing didn't freak out again.

Thanks!

CJK

On Thursday 03 February 2005 07:34 am, Andrew Perrin wrote:

Hmmmm - well, memory is always a possible culprit, as is processor
temperature, but I don't remember if the k6/500 ones suffered much from
that.  Any cheapo SCSI stuff in there? I have some old SCSI CD-RW drives
and a SCSI tape drive that periodically make my debian system lock up for
reasons as yet undiagnosed.

What's the kernel version? What debian version are you tracking? How up to
date is the apt-get upgrade?

Oh, and just so you know: the probability of a work emergency approaches 1
as TSMW/N approaches her first hour of sleep, then decreases from there :)

ap

----------------------------------------------------------------------
Andrew J Perrin - http://www.unc.edu/~aperrin
Assistant Professor of Sociology, U of North Carolina, Chapel Hill
[EMAIL PROTECTED] * andrew_perrin (at) unc.edu

On Thu, 3 Feb 2005, Chris Knowles wrote:

I've got a Debian box I'm using to test/demo/tempt people at work with
some nifty features, and they're loving it.

Until this morning.

When, at 5 am, my pager goes off.  (And since I'd only just gotten "The
Screaming Maw of Want/Need" to get back to sleep, she woke up too.)

The box had gone down, and even though it's just a test, they want it
back up enough to pay me to come in early.

Came in, and no panic, no errors, no nothing, just a completely
non-responsive computer.  Rebooted and took a look around.  Logs are
ticking normally along one minute, then the next entry is from the
reboot.  After the reboot, all is ticking along famously again.

I'm not looking for a specific answer to what the problem is, what I
would like is where to look for any ideas of what went wrong.

(It's a box with Shorewall firewall, bind9, postfix, mailscanner, clamav,
spamassassin, webmin and a kitchen sink.  It's got ~400MB RAM, and 2 10GB
HD in a software raid config.  all with a AMDk6/500 processor.)

CJK

PS: TSMW/N is *not* a nickname for my wife. It's what we've taken to
calling the daughter after more than 1 hour of fussiness in the wee hours
of the morning.
--
TriLUG mailing list :
http://www.trilug.org/mailman/listinfo/trilug TriLUG Organizational FAQ : http://trilug.org/faq/
TriLUG Member Services FAQ : http://members.trilug.org/services_faq/
TriLUG PGP Keyring : http://trilug.org/~chrish/trilug.asc
--
TriLUG mailing list        : http://www.trilug.org/mailman/listinfo/trilug
TriLUG Organizational FAQ  : http://trilug.org/faq/
TriLUG Member Services FAQ : http://members.trilug.org/services_faq/
TriLUG PGP Keyring         : http://trilug.org/~chrish/trilug.asc

Reply via email to