Re: Hard Lockups can't happen (can they?)
On Sunday 27 March 2005 19:20, Doug wrote:
> First, if this happened when you added the hard drive, I would look at
> removing the hard drive and then seeing if the problem recurs. (if
> removing the hard drive does solve it, read more below to see why removing
> the hard drive might have fixed it)
I took the hard drive back out by disconnecting power and the ide cable from
it. No joy, I still locked up.
...
>
> Next, (another long shot) make sure the ram isn't corrupting data. Given
> the lockups occur with a specific program, this is highly unlikely, but in
> the end, it never hurts to check your ram. download memtest86
> (www.memtest86.org) or memtest86+ (www.memtest.org). To run this program,
Ran perfectly, no errors
...
>
> next, try testing your cpu. get a program called mprime.
> (www.mersenne.org - mersenne prime search, more commonly known as prime95
> to those windoze people) let that program run in stress test mode for a
> while and see if it gets any errors. This will do a few things for you.
> Check ram, check cpu & bus, check power draw...
Ran perfectly no errors
>
> if nothing shows up from the hardware at that point, I'd maybe move over to
> software. try: $dpkg-reconfigure konqueror
> or remove konqueror entirely and reinstall
I did this - actually removed it and re-installed. In fact I did it twice
Both times, the first time I ran konqueror, instead of locking the machine it
rebooted it immediately (and I don't mean a controlled shutdown either, it
just immediately started the reboot sequence). The second time I ran
konqueror it did the same as before - locked the machine up solid.
I suspect it is not actually konqueror, but one of the kio-slaves.
...
> moving along with software, it's possible that the upgrade affected
> xfree86. you might want to venture into fixing that. Although just a
> warning, I don't want to see you try fixing it and causing any further
> damage. xfree86 can be finicky at times...
I didn't want to get into that - besides, all the other applications are
working perfectly with X.
>
> well, that's all I can think of off the top of my head. Hopefully one of
> these things will help fix it. To do everything I've mentioned here will
> take a while...
Still have to ask the question. How can a user programme bring down linux?
And just to make sure, I was running htop whilst doing this to see if all the
memory got used up or something like that. Unless it was very fast, between
an htop refresh, memory remained about constant.
> -doug
>
> ----- Original Message -----
> From: "Ron Johnson" <ron.l.johnson@cox.net>
> To: "Debian-User" <debian-user@lists.debian.org>
> Sent: Sunday, March 27, 2005 9:09 AM
> Subject: Re: Hard Lockups can't happen (can they?)
--
Alan Chandler
alan@chandlerfamily.org.uk
First they ignore you, then they laugh at you,
then they fight you, then you win. --Gandhi
Reply to: