From: Manfred Spraul <manfred@colorfullife.com>
To: Jaco Kroon <jkroon@cs.up.ac.za>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Kernel BUG at slab.c:1930
Date: Wed, 19 May 2004 22:57:20 +0200 [thread overview]
Message-ID: <40ABCA30.8010806@colorfullife.com> (raw)
Hi,
>The following OOPS occured this morning. This is on a dual CPU machine,
>there were two oopses, unfortunately the other scrolled off the screen
>but the process was lockd (nfs related afaik).
>
>
Unfortunately the first one is the important one :-(
>Here is the oops (written off and typed up), unfortunately I don't know
>how to convert this to nicely readable symbols ...
>
>Kernel BUG at slab.c:1930
>
That's an oops caused by a consistency check while printing
/proc/slabinfo. Probably a side effect of the first oops.
--
Manfred
next reply other threads:[~2004-05-19 20:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-19 20:57 Manfred Spraul [this message]
2004-05-20 7:58 ` Kernel BUG at slab.c:1930 Jaco Kroon
-- strict thread matches above, loose matches on Subject: below --
2004-05-19 10:26 Jaco Kroon
2004-05-19 20:04 ` Michael Buesch
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=40ABCA30.8010806@colorfullife.com \
--to=manfred@colorfullife.com \
--cc=jkroon@cs.up.ac.za \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox