Q: new kernel not booting (init segfaults) : how to debug ?

[Danny ter Haar <dth@dth.net>]

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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/