All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Marco Berizzi <pupilla@hotmail.com>
Cc: Herbert Xu <herbert@gondor.apana.org.au>,
	linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: 2.6.25 crash: EIP: [<c02e2f14>] xfrm_output_resume+0x64/0x100 ss:esp 0068:c03a1e5c
Date: Fri, 9 May 2008 13:11:30 +0200	[thread overview]
Message-ID: <20080509111130.GA7968@elte.hu> (raw)
In-Reply-To: <BAY103-DAV9DAC70A1FBBEECCCC05E4B2D30@phx.gbl>


* Marco Berizzi <pupilla@hotmail.com> wrote:

> Herbert Xu wrote:
> 
> > On Fri, May 09, 2008 at 11:50:00AM +0200, Marco Berizzi wrote:
> > >
> > > I have rebooted the two boxes with slub_debug.
> > > This is the output taken with network console.
> > > Herbert does it help you?
> > >
> > > BUG: unable to handle kernel paging request at 6b6b6b9f
> >
> > Unfortunately this just confirms that your skb has been freed
> > prematurely because 6b is the poison value.
> >
> > However, it doesn't point us at the offender.
> 
> :-((

you could try x86.git and enable CONFIG_KMEMCHECK, which catches all 
sorts of memory corruption bugs at its root:

  http://people.redhat.com/mingo/x86.git/README

it's for 32-bit currently, and depends on the following CONFIG details 
in your .config:

        depends on X86_32
        depends on !X86_USE_3DNOW
        depends on !CC_OPTIMIZE_FOR_SIZE
        depends on !DEBUG_PAGEALLOC && SLUB

note that CONFIG_DEBUG_PAGEALLOC=y will catch a few types of corruption 
too. Note that KMEMCHECK and DEBUG_PAGEALLOC are exclusive.

	Ingo

  reply	other threads:[~2008-05-09 11:13 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-28  9:25 2.6.25 crash: EIP: [<c02e2f14>] xfrm_output_resume+0x64/0x100 ss:esp 0068:c03a1e5c Marco Berizzi
2008-04-28  9:42 ` David Miller
2008-04-28 10:18   ` Marco Berizzi
2008-04-29 14:37   ` Marco Berizzi
2008-05-02 12:02     ` Herbert Xu
2008-05-02 12:26       ` Marco Berizzi
2008-05-06 10:44         ` Marco Berizzi
2008-05-09  9:50           ` Marco Berizzi
2008-05-09 10:25             ` Herbert Xu
2008-05-09 10:28               ` Marco Berizzi
2008-05-09 11:11                 ` Ingo Molnar [this message]
2008-05-12  7:14               ` Marco Berizzi
2008-05-12  7:46                 ` Herbert Xu
2008-05-12  8:24                   ` Marco Berizzi
2008-05-12 15:06                     ` Marco Berizzi
2008-05-12 16:10                       ` Marco Berizzi
2008-05-14  8:19                         ` Marco Berizzi
2008-05-14 12:03                           ` Marco Berizzi
2008-05-14 12:21                             ` Herbert Xu
2008-05-14 12:32                               ` Marco Berizzi
2008-05-20  9:25                           ` [IPSEC]: Use the correct ip_local_out function Herbert Xu
2008-05-20 10:18                             ` Marco Berizzi
2008-05-20 21:32                             ` David Miller
2008-05-27  9:04                               ` Marco Berizzi
2008-06-07 20:27                               ` [patch 00/50] 2.6.25.6 -stable review Marco Berizzi
2008-06-07 20:43                                 ` Willy Tarreau
2008-06-08 11:56                                   ` Marco Berizzi
2008-06-08 12:36                                     ` Willy Tarreau
2008-06-08 14:10                                       ` David Miller
2008-06-08 14:19                                         ` Willy Tarreau
2008-06-08 15:38                                         ` Jay Cliburn
2008-06-08 16:06                                           ` Willy Tarreau
2008-06-08 20:07                                           ` Jeff Garzik
2008-06-09  2:26                                             ` David Miller
2008-05-05 14:01       ` 2.6.25 crash: EIP: [<c02e2f14>] xfrm_output_resume+0x64/0x100 ss:esp 0068:c03a1e5c Marco Berizzi
2008-04-30 15:15 ` Herbert Xu
2008-04-30 15:38   ` Marco Berizzi
2008-05-01 11:53     ` Herbert Xu
2008-05-01 12:59       ` Marco Berizzi
2008-05-01 14:09         ` Herbert Xu
2008-05-01 19:14           ` Marco Berizzi

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=20080509111130.GA7968@elte.hu \
    --to=mingo@elte.hu \
    --cc=herbert@gondor.apana.org.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pupilla@hotmail.com \
    /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.