Re: Strange lockups on 2.4.2

[Steven Walter <srwalter@yahoo.com>]

On Tue, Mar 27, 2001 at 06:05:05PM +1000, Keith Owens wrote:
> On Mon, 26 Mar 2001 23:16:27 -0600, 
> Steven Walter <srwalter@yahoo.com> wrote:
> >This has happened twice, now, though I don't believe its completely
> >reproduceable.  What happens is an Oops, which drops me into kdb.  I've
> >been in X both times, however, which makes kdb rather useless.
> 
> Documentation/serial-console.txt
>

Unfortunately I don't have the money to go and buy a dumb-terminal, and
the nearest other computer is ~30 feet away.  I've actually looked into
writing code that allows to kernel to return to VGA-text mode for this
reason.

> >The thing I find most interesting about this is that only 4 lines of the
> >oops gets into the log.  4 lines, both times.  This time, those lines
> >were:
> >
> > printing eip:
> >c0112e1f
> >Oops: 0002
> >CPU:    0
> 
> That is a symptom of a broken klogd.  Always run klogd with the -x
> switch.  If that does not work, take a look at
> 
> ftp://ftp.<country>.kernel.org/pub/linux/utils/kernel/ksymoops/v2.4/patch-sysklogd-1-3-31-ksymoops-1.gz
> 
> One day the sysklogd maintainers might just fix this bug, that bug fix
> is almost 2 years old.

I actually already run klogd with -x due to earlier threads on lkml, so
it can't be that /particular/ problem, but klog/syslog may still be to
blame.  I'm usually lucky to get anything in my log between "--MARK--"
then "klogd restart" related to the crash.

-- 
-Steven
Freedom is the freedom to say that two plus two equals four.