From: brian@worldcontrol.com
To: linux-kernel@vger.kernel.org
Subject: valen kernel: kmem_alloc: Bad slab magic (corrupt)
Date: Sun, 3 Feb 2002 20:05:34 -0800 [thread overview]
Message-ID: <20020204040534.GA2322@top.worldcontrol.com> (raw)
I have 14 machines all running Linux 2.2.19 with reiserfs. All
have been running for at least 4 months 24/7.
All are AMD Athlons or Durons, with 1.5GB memory, and are
interconnected by a 16 port 100mbit/s switch. All machines have
tons of cooling and are in a temperature, humidity and power
controlled environment. No overclocking.
The particular machine valen is a 1.333 GHz Athlon Thunderbird
Earlier today it started reporting:
Feb 3 08:24:57 valen kernel: kmem_alloc: Bad slab magic (corrupt) (name=size-4096)
Feb 3 08:25:17 valen last message repeated 7 times ...
Feb 3 08:27:46 valen kernel: kmem_alloc: Bad slab magic (corrupt) (name=size-4096)
Feb 3 08:27:47 valen kernel: nfs: task 2109 can't get a request slot
Feb 3 08:29:16 valen kernel: nfs: task 2111 can't get a request slot
Feb 3 08:29:24 valen kernel: nfs: task 2112 can't get a request slot
Feb 3 08:29:47 valen kernel: nfs: task 2109 can't get a request slot
...
rebooted machine, then later...
Feb 3 16:50:27 valen kernel: call_verify: server accept status: 2
Feb 3 16:50:27 valen kernel: RPC: garbage, retrying 0
Feb 3 16:50:27 valen kernel: call_verify: server accept status: 2
Feb 3 16:50:27 valen kernel: RPC: garbage, retrying 0
Feb 3 16:50:27 valen kernel: call_verify: server accept status: 2
Feb 3 16:50:27 valen kernel: RPC: garbage, exit EIO
Feb 3 16:50:27 valen kernel: nfs_get_root: getattr error = 5
Though I think most of the machines occasionally get these later
messages.
--
Brian Litzinger <brian@worldcontrol.com>
Copyright (c) 2002 By Brian Litzinger, All Rights Reserved
reply other threads:[~2002-02-04 4:07 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20020204040534.GA2322@top.worldcontrol.com \
--to=brian@worldcontrol.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.