archive mirror
 help / color / mirror / Atom feed
From: Kronos <>
Subject: [2.5.75] Slab corruption
Date: Mon, 14 Jul 2003 20:03:37 +0200	[thread overview]
Message-ID: <20030714180337.GA918@dreamland.darkstar.lan> (raw)

I got  a slab corruption under  2.5.75. I was browsing with  mozilla 1.4
and this  was the only  network load. Kernel is UP  with CONFIG_PREEMPT.
Full .config is here:

This is the first error:

Slab corruption: start=ef1962f4, expend=ef196af3, problemat=ef196503
Last user: [kfree_skbmem+20/48](kfree_skbmem+0x14/0x30)
Data: ***********************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************FF *******01 *******04 *******07 *******04 *******FE *******FA *******F9 *******************************************************************************************************************************************************************************************************08 *******06 *******04 *******04 *******03 *******01 *******00 *******01 *********************************************************************************************************************
Next: 71 F0 2C .44 23 2F C0 A5 C2 0F 17 ..................20 A0 
slab error in check_poison_obj(): cache `size-2048': object was modified after freeing
Call Trace:
 [check_poison_obj+363/432] check_poison_obj+0x16b/0x1b0
 [__kmalloc+361/464] __kmalloc+0x169/0x1d0
 [alloc_skb+72/240] alloc_skb+0x48/0xf0
 [alloc_skb+72/240] alloc_skb+0x48/0xf0
 [_end+945553231/1068985560] e100_rx_srv+0x197/0x530 [e100]
 [_end+945552455/1068985560] e100intr+0x1bf/0x200 [e100]
 [handle_IRQ_event+59/112] handle_IRQ_event+0x3b/0x70
 [do_IRQ+321/928] do_IRQ+0x141/0x3a0
 [common_interrupt+24/32] common_interrupt+0x18/0x20
 [acpi_processor_idle+346/495] acpi_processor_idle+0x15a/0x1ef
 [default_idle+0/48] default_idle+0x0/0x30
 [acpi_processor_idle+0/495] acpi_processor_idle+0x0/0x1ef
 [default_idle+0/48] default_idle+0x0/0x30
 [cpu_idle+49/64] cpu_idle+0x31/0x40
 [rest_init+0/240] _stext+0x0/0xf0
 [start_kernel+432/528] start_kernel+0x1b0/0x210
 [unknown_bootoption+0/256] unknown_bootoption+0x0/0x100

It  seems e100  fault... after  that I  saw other  (maybe related)  slab
corruptions. Full log is here:

The CPU is quite cool and the system survived memtest some time ago.

"It is more complicated than you think"
                -- The Eighth Networking Truth from RFC 1925

                 reply	other threads:[~2003-07-14 17:53 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20030714180337.GA918@dreamland.darkstar.lan \ \ \ \

* 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;
as well as URLs for NNTP newsgroup(s).