public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Steffen Persvold <sp@scali.no>
Cc: lkml <linux-kernel@vger.kernel.org>,
	"nfs@lists.sourceforge.net" <nfs@lists.sourceforge.net>
Subject: Re: Kernel crash using NFSv3 on 2.4.4
Date: 30 Apr 2001 11:58:32 +0200	[thread overview]
Message-ID: <shsitjmd7zr.fsf@charged.uio.no> (raw)
In-Reply-To: <3AED12A4.FA869E84@scali.no>
In-Reply-To: Steffen Persvold's message of "Mon, 30 Apr 2001 02:22:12 -0500"

>>>>> " " == Steffen Persvold <sp@scali.no> writes:

     > Hi all, I have compiled a stock 2.4.4 kernel and applied SGI's
     > kdb patch v1.8. Most of the time this runs just fine, but one
     > time when I tried to copy a file from a NFS server I got a
     > kernel fault. Luckily it jumped right into the debugger and I
     > could to some batcktracing (quite useful!) :

     > Unable to handle kernel paging request at virtual address
     > 414478b1
     >  printing eip:
     > c012c826 *pde = 00000000

     > Entering kdb (current=0xca07a000, pid 971) on processor 0 Oops:
     > Oops due to oops @ 0xc012c826 eax = 0x20000000 ebx = 0xc15e4800
     > ecx = 0x00000000 edx = 0xc1447899 esi = 0x00000000 edi =
     > 0xc14477a0 esp = 0xca07ba98 eip = 0xc012c826 ebp = 0xca07baa4
     > xss = 0x00000018 xcs = 0x00000010 eflags = 0x00010046 xds =
     > 0xc1440018 xes = 0x00000018 origeax = 0xffffffff &regs =
     > 0xca07ba64 [0]kdb> bt
     >     EBP EIP Function(args)
     > 0xca07baa4 0xc012c826 kmem_cache_alloc_batch+0x46 (0xc14477a0,
     > 0x7, 0xcb965260)
     >                                kernel .text 0xc0100000
     >                                0xc012c7e0 0xc012c864
     > 0xca07bad0 0xc012ca8e kmalloc+0x82 (0x13c, 0x7, 0xca4ca040,
     > 0x0)

Looks like the IP layer is trying to allocate too much memory. You
wouldn't have set /proc/sys/net/core/{w,r}mem_{max,default} to some
value greater than 256k?

Cheers,
   Trond

      reply	other threads:[~2001-04-30  9:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-30  7:22 Kernel crash using NFSv3 on 2.4.4 Steffen Persvold
2001-04-30  9:58 ` Trond Myklebust [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=shsitjmd7zr.fsf@charged.uio.no \
    --to=trond.myklebust@fys.uio.no \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nfs@lists.sourceforge.net \
    --cc=sp@scali.no \
    /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