|
[Date Prev] [Date Next] [Thread Prev] [Thread Next] [Date Index] [Thread Index]
|
RE: [PLUG] Kernel Troubles
|
ok, thanks. I don't know enough about the kernel to know all of the stuff
that happened.
I might try upgrading to 2.4.21 or 2.4.22. Right now it is running the
redhat kernel that comes with RH9. The main reason being that this machine
has an nVidia video card and I am lazy.
As for the message about getting the same brand over and over, I didn't buy
all of the drives, and up until now, I have never had any trouble with IBM
before. Luckily, I had a nearly full backup on the other drive (which was
done when the first one went and never deleted -- lazyness pays off, I
guess). I do not know if they are 75GX's (or whatever went bad). I know
that the 40GB's are not, but not sure about the 80GB.
So, thanks. I think I'll be playing with the kernel a bit this weekend.
-b
-----Original Message-----
From: plug-admin@lists.phillylinux.org
[mailto:plug-admin@lists.phillylinux.org]On Behalf Of Will Dyson
Sent: Wednesday, September 03, 2003 2:20 PM
To: plug@lists.phillylinux.org
Subject: Re: [PLUG] Kernel Troubles
On Tue, 2003-09-02 at 21:22, Bradley Molnar wrote:
> I'm not totally sure what the problem was, but, I did notice a couple of
> lines in /var/log/messages.*, namely,
>
> Aug 29 04:02:01 guardian kernel: EIP is at find_inode [kernel] 0x24
> (2.4.20-8)
> Aug 29 04:02:01 guardian kernel: [<f8822d5c>] ext3_lookup [ext3] 0x7c
> (0xc7fe1eb4))
That is an Oops report. The kernel dereferenced a null pointer or some
other Bad Thing. When this happens, the kernel's execption handler kills
the process that called into the kernel and prints a backtrace of the
kernel stack to the syslog.
So we can see that the kernel was executing the find_inode function
(which was called from ext3_lookup) when things went to hell.
In your case, it sounds like some vital kernel datastructure was
corrupted before the kernel noticed anything was wrong, causing the
machine to hang at some later time.
It could well be a bad disk that is the ultimate cause of the problem.
All filesystems that I know of basicaly trust their own on-disk
datastructures. If it read corrupted metadata, it would doubtless cause
a crash. Perhaps you should try fscking the filesystem on that disk.
But I also vaguely recall that 2.4.21 fixed a problem or two with ext3.
Since your uptime is shot anyway, you might consider upgrading.
--
Will Dyson
"Back off man, I'm a scientist!" -Dr. Peter Venkman
_________________________________________________________________________
Philadelphia Linux Users Group -- http://www.phillylinux.org
Announcements - http://lists.netisland.net/mailman/listinfo/plug-announce
General Discussion -- http://lists.netisland.net/mailman/listinfo/plug
_________________________________________________________________________
Philadelphia Linux Users Group -- http://www.phillylinux.org
Announcements - http://lists.netisland.net/mailman/listinfo/plug-announce
General Discussion -- http://lists.netisland.net/mailman/listinfo/plug
|
|