Messages in this thread | | | Date | Wed, 4 Aug 1999 00:36:35 +0200 | From | Peter Gervai <> | Subject | Re: kmem_alloc: Bad slab magic (corrupt) (name=size-128) |
| |
Hello,
On Tue, Aug 03, 1999 at 04:56:19PM -0400, Craig B Agricola wrote:
> This looks suspiciously like a problem that was plaguing the Token Ring > code around kernels 2.2.3-2.2.8 or so. How long does it take before you start > getting this message after you initialize your eth0 interface? In the Token > Ring case, the problem was traced down to lots of net packets that were lying > about thier length, so when they were being free'd, they were freeing up less > space than they were actually taking, so before long there was no more real > memory available to the kernel. You may want to take a look with a packet > sniffer to see if there are any bad packets flying around (maybe some bad > NetBUI junk or something...)
I am guilty of not providing enough information.
Kernel 2.2.10 (stock), K6-2/400, 256M,
eth0: 3c509 at 0x340 tag 1, 10baseT port, address 00 10 4b b9 c8 15, IRQ 5. 3c509.c:1.16 (2.2) 2/3/98 becker@cesdis.gsfc.nasa.gov.
The machine was loaded with close to 50% 10Mbps ethernet, mostly apache and ftp.
> On Tue, Aug 03, 1999 at 10:23:37PM +0200, Peter Gervai wrote: > > Hello, > > > > Aug 3 21:04:46 my kernel: kmem_alloc: Bad slab magic (corrupt) (name=size-128) > > Aug 3 21:04:46 my kernel: eth0: Couldn't allocate a sk_buff of size 60. > > Aug 3 21:04:47 my kernel: kmem_alloc: Bad slab magic (corrupt) (name=size-128) > > Aug 3 21:04:47 my kernel: eth0: Couldn't allocate a sk_buff of size 67. > > Aug 3 21:04:47 my kernel: kmem_alloc: Bad slab magic (corrupt) (name=size-128) > > (last messages repeated zillion times till reboot) [...]
regards, grin
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/
| |