All of lore.kernel.org
 help / color / mirror / Atom feed
From: Le Rouzic <aime.le-rouzic@bull.net>
To: nfsv4 <nfsv4@linux-nfs.org>
Cc: linux-nfs@vger.kernel.org
Subject: Kernel Bug with 2.6.24-rc2-CITI_NFS4-ALL-1  in net/sunrpc/svc_xprt.c
Date: Wed, 12 Dec 2007 15:49:01 +0100	[thread overview]
Message-ID: <475FF4DD.6010700@bull.net> (raw)
In-Reply-To: <4757D2B5.4070800@bull.net>

hi,
Running as client RHEL5.1 Public Gold on a X86_64 bi-ways and
as server 2.6.24-rc2-CITI_NFS4_ALL-1 on a X86_64 bi-ways,
I get the following Oops on the server when on the client I run
in a infinite loop iozone with -U option:

while true
do
./iozone -+q 30 -ace -r 64 -i 0 -i 1 -i 2 -f /mnt/nosec/nfs4_gb -U 
/mnt/nosec
date
sleep 30
done

=============================================================================
Fedora Core release 6 (Zod)
Kernel 2.6.24-rc2-CITI_NFS4_ALL-1 on an x86_64

nfs4gb login: ------------[ cut here ]------------
kernel BUG at net/sunrpc/svc_xprt.c:323!
invalid opcode: 0000 [1] SMP
Entering kdb (current=0xffff8100031e6080, pid 3227) on processor 1 Oops: 
<NULL>
due to oops @ 0xffffffff805bfef1
     r15 = 0x0000000000001000      r14 = 0xffff810006cfc000
     r13 = 0xffff8100035363c0      r12 = 0xffff810004c30bc0
     rbp = 0xffff810007df4000      rbx = 0xffff810006994000
     r11 = 0xffff8100098c1d80      r10 = 0x0000000000007d2b
      r9 = 0x0000000000000004       r8 = 0xffff810004df9180
     rax = 0x0000000000041000      rcx = 0x0000000000000001
     rdx = 0x0000000000000000      rsi = 0x0000000000000001
     rdi = 0xffff810006994010 orig_rax = 0xffffffffffffffff
     rip = 0xffffffff805bfef1       cs = 0x0000000000000010
  eflags = 0x0000000000010203      rsp = 0xffff810007d73d90
      ss = 0x0000000000000018 &regs = 0xffff810007d73cf8
[1]kdb>
[1]kdb> bt
Stack traceback for pid 3227
0xffff8100031e6080     3227        2  1    1   R  0xffff8100031e63a0 *nfsd
rsp                rip                Function (args)
0xffff810007d73d78 0xffffffff805bfef1 svc_xprt_enqueue+0x19a 
(0xffff810006994000)
0xffff810007d73dc8 0xffffffff805b9198 svc_tcp_recvfrom+0x367 
(0xffff810006cfc000)
0xffff810007d73e48 0xffffffff805c0db8 svc_recv+0x62d 
(0xffff810006cfc000, 0xdbba0)
0xffff810007d73f08 0xffffffff803329db nfsd+0xdb (0xffff810006cfc000)
0xffff810007d73f48 0xffffffff8020cbf8 child_rip+0xa (invalid, invalid)
[1]kdb>

More at:
Bug:  http://bugzilla.linux-nfs.org/show_bug.cgi?id=155

Regards


-- 
-----------------------------------------------------------------
Company : Bull, Architect of an Open World TM (www.bull.com)
Name    : Aime Le Rouzic 
Mail    : Bull - BP 208 - 38432 Echirolles Cedex - France
E-Mail  : aime.le-rouzic@bull.net
Phone   : 33 (4) 76.29.75.51
Fax     : 33 (4) 76.29.75.18
----------------------------------------------------------------- 


  reply	other threads:[~2007-12-12 14:48 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-06 10:45 Results of a Robustness Regression tests campaign with RHEL5.1 Gold and linux-2.6.24-rc2-CITI_NFS4_ALL-1 Le Rouzic
2007-12-12 14:49 ` Le Rouzic [this message]
2007-12-15  0:12   ` Kernel Bug with 2.6.24-rc2-CITI_NFS4-ALL-1 in net/sunrpc/svc_xprt.c J. Bruce Fields
2007-12-15 16:45     ` Tom Tucker
2007-12-15 16:49       ` J. Bruce Fields
2007-12-15 16:52         ` J. Bruce Fields

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=475FF4DD.6010700@bull.net \
    --to=aime.le-rouzic@bull.net \
    --cc=linux-nfs@vger.kernel.org \
    --cc=nfsv4@linux-nfs.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.