On Tue, 2003-06-10 at 02:59, Jesse Kline wrote:
> That really sucks dude. I'm no kernel guru, and your logs look like
> greek to me, however I would try plugging some of those lines into
> google to see if you can get any clues as to what might be the problem.
> I would also try booting with the stock redhat kernel to see if it still
> has problems, if not you may want to compile another kernel with
> different options, maybe try the redhat config script. When I was
> getting kernel oopses it turned out to be a faulty memory slot, I would
> try replacing the network card and maybe removing some of the hardware
> to try and narrow down the problem.
>
Yeah it looks pretty nasty. I tried plugging in the error message into
google, and came up with a huge variety of issues. Most were minor non
fatal errors, but this one seems fatal. After questioning the guy who
monitors all the mail meaages I found this as well:
/etc/cron.weekly/makewhatis.cron:
/usr/sbin/makewhatis: line 352: 24727 Broken pipe find .
-name
'*' $findarg -print
24728 Segmentation fault | $AWK '
That message coincidently was sent shortly before the kernel errors
started appearing. Might have to join the kernel mailing list...
Thanks,
--
Neil Jolly
(with Yoda-like voice)
"Confrontation leads to anger... Anger leads to fear... Fear leads
to using Windows NT in mission-critical combat systems... And this is
how the ancients fell...
