From: Arjan van de Ven <arjanv@redhat.com>
To: Jim Gifford <maillist@jg555.com>
Cc: Kernel <linux-kernel@vger.kernel.org>
Subject: Re: Trouble with NFS with -mm3, -mm4, and -mm5
Date: Sat, 22 May 2004 20:38:01 +0200 [thread overview]
Message-ID: <1085251081.14486.9.camel@laptop.fenrus.com> (raw)
In-Reply-To: <01ef01c44027$7cb90920$d100a8c0@W2RZ8L4S02>
[-- Attachment #1: Type: text/plain, Size: 935 bytes --]
On Sat, 2004-05-22 at 20:06, Jim Gifford wrote:
> I keep getting the following oops using NFS with -mm3 thru -mm5.
>
> May 22 00:25:27 server ------------[ cut here ]------------
> May 22 00:25:27 server kernel BUG at include/linux/dcache.h:276!
> May 22 00:25:27 server invalid operand: 0000 [#1]
> May 22 00:25:27 server PREEMPT SMP
> May 22 00:25:27 server Modules linked in: vfat fat isofs zlib_inflate floppy
> ext2 videodev nfsd exportfs lockd sunrpc parport_pc lp parport ipt_TOS
> ipt_TCPMSS ipt_LOG ipt_limit iptable_mangle iptable_nat ip_conntrack_irc
> ip_conntrack_ftp ipt_REJECT ipt_state ip_conntrack af_packet bonding 8250
> serial_core ohci_hcd usbcore psmouse tulip crc32 iptable_filter ip_tables
> ovcamchip i2c_core rtc supermount unix aic7xxx megaraid sd_mod scsi_mod
does this happen without supermount too? It might just be that something
is confusing the VFS..... and thus the bug in dcache...
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-05-22 18:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-22 18:06 Jim Gifford
2004-05-22 18:38 ` Arjan van de Ven [this message]
2004-05-22 19:32 ` Jim Gifford
2004-05-22 21:42 ` Neil Brown
2004-05-23 4:08 ` Jim Gifford
2004-05-23 5:36 ` Neil Brown
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=1085251081.14486.9.camel@laptop.fenrus.com \
--to=arjanv@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maillist@jg555.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®