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>,
jeffrey.t.kirsher@intel.com, e1000-devel@lists.sourceforge.net
Subject: Re: Current Git: BUG: unable to handle kernel paging request at 0000000001a40ca0
Date: Wed, 23 Jul 2008 23:53:36 +0200 [thread overview]
Message-ID: <4887A860.6070607@gmx.de> (raw)
In-Reply-To: <48877200.9040608@gmx.de>
Dieter Ries schrieb:
> 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 tried to bisect the bug, which failed because there were too many
kernels not booting with other problems, I guess bisecting just fails in
the merge window.
With CONFIG_SLUB_DEBUG_ON the output looks different, unfortunately
netconsole stops before those are transmitted.
As there are always some lines about e1000 in the backtraces, I tried to
boot without LAN cable connected, and it worked, and crashed afterwards
when I plugged the cable in, with a bug in net/core/dev.c.
I will search on tomorrow, as it is getting quite late now.
Should I copy the messages with CONFIG_SLUB_DEBUG_ON by hand, or are
just some parts important?
cu
Dieter
next prev parent reply other threads:[~2008-07-23 21:53 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
2008-07-23 21:53 ` Dieter Ries [this message]
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=4887A860.6070607@gmx.de \
--to=clip3@gmx.de \
--cc=e1000-devel@lists.sourceforge.net \
--cc=jeffrey.t.kirsher@intel.com \
--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).