From: "J. Bruce Fields" <bfields@fieldses.org>
To: Roger Heflin <rheflin@atipa.com>
Cc: NFS <nfs@lists.sourceforge.net>,
Linux-Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [NFS] Kernel BUG at mm/slab.c:2380 on NFS server in nfsd (2.6.21.1)
Date: Wed, 16 May 2007 12:29:37 -0400 [thread overview]
Message-ID: <20070516162937.GC9895@fieldses.org> (raw)
In-Reply-To: <464B0D47.6070509@atipa.com>
On Wed, May 16, 2007 at 08:55:19AM -0500, Roger Heflin wrote:
> Running bonnie over nfs on a RHEL4.4 client against a 2.6.21.1 server
> got me this crash after about 4 hours of running on the server:
>
> This was running lvm -> ext3 -> nfs ---- nfsclient (RHEL4.4).
Yipes. Has this happened only once, or do you have a way to reliably
reproduce it?
Is it a new problem? (And, if so, what changed?)
> May 15 21:10:31 vault1 kernel: ------------[ cut here ]------------
> May 15 21:10:31 vault1 kernel: kernel BUG at mm/slab.c:2380!
That's the check_spinlock_acquired() in cache_alloc_refill(). What
causes that to fail?
> May 15 21:10:31 vault1 kernel: invalid opcode: 0000 [1] SMP
> May 15 21:10:31 vault1 kernel: CPU 0
> May 15 21:10:31 vault1 kernel: Modules linked in: qla2xxx nfsd exportfs
> lockd nfs_acl sunrpc hidp l2cap bluetooth ipv6 cpufreq_ondemand jfs
> dm_mirror dm_multipath dm_mod video sbs i2c_ec dock button battery
> asus_acpi ac lp snd_intel8x0 snd_ac97_codec ac97_bus snd_seq_dummy
> snd_seq_oss snd_seq_midi_event snd_seq snd_seq_device sg snd_pcm_oss
> floppy snd_mixer_oss snd_pcm cfi_cmdset_0002 cfi_util mtdpart snd_timer
> jedec_probe cfi_probe gen_probe snd ck804xrom sata_nv mtdcore chipreg
> i2c_nforce2 soundcore map_funcs libata snd_page_alloc pcspkr i2c_core
> k8temp hwmon forcedeth ohci1394 ieee1394 parport_pc ide_cd parport cdrom
> serio_raw scsi_transport_fc shpchp megaraid_mbox sd_mod scsi_mod
> megaraid_mm ext3 jbd ehci_hcd ohci_hcd uhci_hcd
> May 15 21:10:31 vault1 kernel: Pid: 4256, comm: nfsd Not tainted 2.6.21.1 #1
> May 15 21:10:31 vault1 kernel: RIP: 0010:[<ffffffff8025a710>]
> [<ffffffff8025a710>] cache_alloc_refill+0xe6/0x1f3
> May 15 21:10:31 vault1 kernel: RSP: 0018:ffff81021dead6d0 EFLAGS: 00010002
> May 15 21:10:31 vault1 kernel: RAX: 0000000000000001 RBX:
> ffff81012211d960 RCX: ffff810120013040
> May 15 21:10:31 vault1 kernel: RDX: 000000000000000e RSI:
> ffff810139020000 RDI: ffff810120013040
There wasn't a backtrace?
--b.
next prev parent reply other threads:[~2007-05-16 16:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-16 13:55 Roger Heflin
2007-05-16 16:29 ` J. Bruce Fields [this message]
2007-05-16 16:35 ` [NFS] " Roger Heflin
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=20070516162937.GC9895@fieldses.org \
--to=bfields@fieldses.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nfs@lists.sourceforge.net \
--cc=rheflin@atipa.com \
/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
all inboxes | Powered by JetHome®