>>>>> " " == Steffen Persvold <[EMAIL PROTECTED]> 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 ®s =
> 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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
