From: Danny ter Haar <dth@dth.net>
To: LKML <linux-kernel@vger.kernel.org>
Subject: Q: new kernel not booting (init segfaults) : how to debug ?
Date: Mon, 24 Sep 2007 21:24:10 +0200 [thread overview]
Message-ID: <20070924192410.GA8881@dth.net> (raw)
System: firewall
-Epia 5000 via c3 system
-bios 2.07 (latest available, upgraded from 1.09 with same behaviour)
-128Mb flash memory (ide emulation)
-256mb ram
-voyage linux (debian based)
Runs "standard" kernel just fine, 2.6.22.17 also compiles/runs
where as 2.6.23-rcX wont
Typed over from screenshot:
---------------------------------------
NET: Registered protocol family 1
NET: Registered protocol family 17
Using IPI Shortcut mode
Freeing unused kernel memory: 148k freed
init[1]: segfault at 85890000 eip 85890000 esp bfcfcb8c error 4
init[1]: segfault at 85890000 eip 85890000 esp bfcfcb8c error 4
init[1]: segfault at 85890000 eip 85890000 esp bfcfcb8c error 4
init[1]: segfault at 85890000 eip 85890000 esp bfcfcb8c error 4
init[1]: segfault at 85890000 eip 85890000 esp bfcfcb8c error 4
init[1]: segfault at 85890000 eip 85890000 esp bfcfcb8c error 4
init[1]: segfault at 85890000 eip 85890000 esp bfcfcb8c error 4
init[1]: segfault at 85890000 eip 85890000 esp bfcfcb8c error 4
init[1]: segfault at 85890000 eip 85890000 esp bfcfcb8c error 4
init[1]: segfault at 85890000 eip 85890000 esp bfcfcb8c error 4
printk: 788820 messages suppressed.
---------------------------------------
The only thing changed is the kernel.
I'm just plain flabbergasted about why this occurs and complete
lost how to debug/persue this any further.
Kernel config/systemmap etc at http://www.dth.net/kernel/c3/
Danny
next reply other threads:[~2007-09-24 19:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-24 19:24 Danny ter Haar [this message]
2007-09-24 20:15 ` Q: new kernel not booting (init segfaults) : how to debug ? Chuck Ebbert
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=20070924192410.GA8881@dth.net \
--to=dth@dth.net \
--cc=linux-kernel@vger.kernel.org \
/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