All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Jones <davej@redhat.com>
To: chucklever@gmail.com
Cc: Chuck Lever <chuck.lever@oracle.com>,
	Linux Kernel <linux-kernel@vger.kernel.org>,
	Trond Myklebust <Trond.Myklebust@netapp.com>
Subject: Re: NFS oops in 2.6.26rc4
Date: Fri, 30 May 2008 14:21:26 -0400	[thread overview]
Message-ID: <20080530182126.GB32480@redhat.com> (raw)
In-Reply-To: <76bd70e30805301059v461e8f0eocc38b6fe36dd3b21@mail.gmail.com>

On Fri, May 30, 2008 at 01:59:12PM -0400, Chuck Lever wrote:

 > > When trying to mount an nfs export, I got this oops..
 > >
 > > BUG: unable to handle kernel paging request at f4569000
 > > IP: [<f8daac01>] :sunrpc:xdr_encode_opaque_fixed+0x2d/0x69
 > > *pde = 34c23163 *pte = 34569160
 > > Oops: 0000 [#1] SMP DEBUG_PAGEALLOC
 > > Modules linked in: nfs nfsd lockd nfs_acl auth_rpcgss exportfs sunrpc ext2 sg button via_rhine via_ircc pcspkr r8169 mii pata_sil680 irda crc_ccitt i2c_viapro i2c_core dm_snapshot dm_zero dm_mirror dm_log dm_mod pata_via ata_generic pata_acpi libata sd_mod scsi_mod ext3 jbd mbcache uhci_hcd ohci_hcd ehci_hcd [last unloaded: scsi_wait_scan]
 > > ...
 > > Code: e5 57 56 89 d6 53 83 ec 04 85 c9 89 45 f0 89 c8 74 4c 8d 59 03 c1 eb 02 8d 14 9d 00 00 00 00 29 ca 85 f6 74 11 c1 e9 02 8b 7d f0 <f3> a5 89 c1 83 e1 03 74 02 f3 a4 85 d2 74 1b 8b 7d f0 89 d1 c1
 > > EIP: [<f8daac01>] xdr_encode_opaque_fixed+0x2d/0x69 [sunrpc] SS:ESP 0068:f4566a68
 > > ---[ end trace a8a691a45122c25a ]---
 > > mount.nfs used greatest stack depth: 812 bytes left
 > 
 > The last line suggests you are trying this with 4KB kernel stacks.  I
 > have patches queued for .27 that provide some stack relief in this
 > code path.  If you hit this often, you might want to try with 8KB
 > stacks to see if that helps.

Yes, Fedora kernels have been using 4K stacks for some time.
>From the trace though, it doesn't look like we actually ran out of
stack space ? 

 > In the meantime, the traceback is a little funky, so I can't see
 > directly what the root cause is.  Can you provide the full command
 > line of the mount command that caused this?

mount point in the fstab is ..

gelk:/mnt/data      /mnt/nfs/gelk       nfs     nfsvers=3,tcp        0 0

 >  What "brand" of server were you trying to mount?

It's just another linux box. A no-name core2 duo, running 2.6.25.

 > How often can you reproduce this?

Seems to do it every time I ask it to.

	Dave

-- 
http://www.codemonkey.org.uk

  reply	other threads:[~2008-05-30 18:29 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-27 19:04 NFS oops in 2.6.26rc4 Dave Jones
2008-05-29 11:48 ` Jeff Layton
2008-05-30 17:59 ` Chuck Lever
2008-05-30 18:21   ` Dave Jones [this message]
2008-05-30 18:31     ` Trond Myklebust
2008-05-30 19:03       ` Dave Jones
2008-05-30 19:37         ` Chuck Lever
2008-06-04 14:19           ` Dave Jones
2008-06-04 18:13             ` Chuck Lever
2008-06-04 18:20               ` Dave Jones
2008-06-04 19:13                 ` Chuck Lever
2008-06-23 15:40                 ` Trond Myklebust
2008-06-23 15:55                   ` Dave Jones
2008-06-23 16:04                     ` Trond Myklebust
2008-06-23 23:11                   ` Dave Jones
2008-06-23 23:19                     ` Trond Myklebust

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=20080530182126.GB32480@redhat.com \
    --to=davej@redhat.com \
    --cc=Trond.Myklebust@netapp.com \
    --cc=chuck.lever@oracle.com \
    --cc=chucklever@gmail.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.