Linux NFS development
 help / color / mirror / Atom feed
From: Roger Heflin <rheflin@atipa.com>
To: "J. Bruce Fields" <bfields@fieldses.org>
Cc: NFS <nfs@lists.sourceforge.net>,
	Linux-Kernel <linux-kernel@vger.kernel.org>
Subject: Re: Kernel BUG at mm/slab.c:2380 on NFS server in nfsd (2.6.21.1)
Date: Wed, 16 May 2007 11:35:38 -0500	[thread overview]
Message-ID: <464B32DA.5000506@atipa.com> (raw)
In-Reply-To: <20070516162937.GC9895@fieldses.org>

J. Bruce Fields wrote:
> 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?

I have not reproduced it yet, I will update if I do, I suspect
that I will be able to reproduce it, but it took several hours
of running.

> 
> Is it a new problem?  (And, if so, what changed?)

New different tests.

> 
>> 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.
> 

That was all I had before it took the machine out, it is on a serial
console at this time, so if it happens again I should get better data.

                              Roger

-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

      reply	other threads:[~2007-05-16 16:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-16 13:55 Kernel BUG at mm/slab.c:2380 on NFS server in nfsd (2.6.21.1) Roger Heflin
2007-05-16 16:29 ` J. Bruce Fields
2007-05-16 16:35   ` Roger Heflin [this message]

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=464B32DA.5000506@atipa.com \
    --to=rheflin@atipa.com \
    --cc=bfields@fieldses.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nfs@lists.sourceforge.net \
    /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