Kernel with rt-preempt patch 2.6.17-rt8 not booting

From: Raphael Hertzog
Date: Wed Aug 16 2006 - 05:57:21 EST


(Please CC me when responding)

Hello,

I was trying the latest rt-preempt patch (2.6.17-rt8) with linux 2.6.17.7 on a
little 386-based ISA CPU card (40Mhz, 8Mb RAM):
http://www.icop.com.tw/products_detail.asp?ProductID=205
More detailed spec of the CPU are here:
http://www.dmp.com.tw/tech/m6117d/

With all options activated (default config), the kernel wouldn't boot with
the following error displayed in loop:
Unknown interrupt or fault at EIP 00010086 c0120060 c01218b9

It happens very early in the boot and I don't see any other kernel message
before (or if there are any, they are very quickly moved out of the
display by the error message).

I tried to "isolate" the error by trying various combinations of options.
Deactivating CONFIG_PREEMPT_RT and CONFIG_PREEMPT_RCU and (and using
PREEMPT_DESKTOP and CLASSIC_RCU) let the kernel boot (I'm not sure which
of the two options solved the boot problem, I didn't try them individually)
but the "performance" was very bad compared to a stock kernel. I
guessed this was due to the "threaded soft/hard IRQ" and I tried to disable
those, and then the machine became very unresponsive... like it would
answer ping of the last 20 seconds all in once (it looks like the kernel
didn't receive any interrupt when the network trafic came in and did
everything in a batch later).

What more can I do to help fix this bug ? I'm happy to try out patches and
do whatever further research may be needed. The initial .config (which
didn't boot) is here:
http://ouaza.com/~rhertzog/config-2.6-rt

(this output below is generated with a stock 2.6.17.7 kernel)
# cat /proc/interrupts
CPU0
0: 88503366 XT-PIC timer
2: 0 XT-PIC cascade
3: 11 XT-PIC serial
4: 12 XT-PIC serial
5: 4958 XT-PIC NE2000
14: 10771 XT-PIC ide0
NMI: 0
ERR: 0

Cheers,
--
Raphaël Hertzog

Premier livre français sur Debian GNU/Linux :
http://www.ouaza.com/livre/admin-debian/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/