[Adding CC to bug-hurd, _again_, don't remove it!]
22: 9186 IO-APIC-level libata, NVidia CK804
23: 13705 IO-APIC-level libata, eth0
These two could cause problems, I don't know what libata or nvidia is.
But if GNU Mach has support for your NIC and any of these two, it
might explain the sudden reboot. Have you tried compiling a really
bare kernel with only say an IDE driver?
>Could you check where that EIP is? gdb is your friend, issue the
>following in gdb: info line *EIP
I will try, but the most frequent result is still a reboot, so as a
consequence it might take some time before I can get into gdb
again. Good to know that it's gdb by the way, since I know gdb. I
was afraid that it might be something unique to mach.
To properly debug GNU Mach you will either have to use printf's in the
code, or hack it to support a serial debugger. Or use GNU Mach 2.x,
which doesn't even compile. For this you could have equally used nm
or somesuch instead of firing up gdb on the kernel image just to get
the function name where things died.
_______________________________________________
Bug-hurd mailing list
Bug-hurd@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-hurd
