netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dieter Ries <clip3@gmx.de>
To: Vegard Nossum <vegard.nossum@gmail.com>
Cc: linux-kernel@vger.kernel.org, jgarzik@pobox.com,
	netdev@vger.kernel.org, Pekka Enberg <penberg@cs.helsinki.fi>
Subject: Re: Current Git: BUG: unable to handle kernel paging request at 0000000001a40ca0
Date: Wed, 23 Jul 2008 20:01:36 +0200	[thread overview]
Message-ID: <48877200.9040608@gmx.de> (raw)
In-Reply-To: <19f34abd0807231046o4b194409w7d0e28a7cd745afa@mail.gmail.com>

Vegard Nossum schrieb:
> Hi,

Hi,

> 
> Dieter: If this is reproducible, it would probably help quite a bit to
> configure the kernel with CONFIG_SLUB_DEBUG and boot with
> slub_debug=FZPUT (unless you already have CONFIG_SLUB_DEBUG_ON set, in
> which case you are already running with the SLUB debugging at boot).
> It might catch the corruption before it becomes fatal, or give us some
> more clues anyway.
> 

I am bisecting the bug right now, as it is kind of reproducible. Its 
always network related, sometimes it happens when init brings up the 
nics, sometimes afterwards with ifconfig etc.

I will add CONFIG_SLUB_DEBUG_ON for the next runs, next time it happens 
I will post the output.

> 
> Vegard
> 
cu
Dieter

  reply	other threads:[~2008-07-23 18:16 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-23 15:39 Current Git: BUG: unable to handle kernel paging request at 0000000001a40ca0 Dieter Ries
2008-07-23 17:46 ` Vegard Nossum
2008-07-23 18:01   ` Dieter Ries [this message]
2008-07-23 21:53     ` Dieter Ries
2008-07-23 22:00       ` Vegard Nossum
2008-07-24  6:51         ` Dieter Ries
2008-07-24 13:49           ` Pekka Enberg
2008-07-24 13:51             ` Patrick McHardy
2008-07-24 17:53             ` Dieter Ries

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=48877200.9040608@gmx.de \
    --to=clip3@gmx.de \
    --cc=jgarzik@pobox.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=penberg@cs.helsinki.fi \
    --cc=vegard.nossum@gmail.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 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).