Re: one remaining mystery about the FreeBSD domU failure on NetBSD XEN3_DOM0

[mlelstv%serpens.de@localhost (Michael van Elst)]

woods%planix.ca@localhost ("Greg A. Woods") writes:

>system was suffering the effects of accessing the corrupted filesystem I
>was experimenting with.  Note the SIGSEGV's from processes apparently
>after the kernel has gone into its halt-spin loop (this is the first
>time I've seen this particular misbehaviour):

>The operating system has halted.
>Please press any key to reboot.

>pid 412 (syslogd), jid 0, uid 0: exited on signal 11
>pid 343 (devd), jid 0, uid 0: exited on signal 11


This looks like some processes haven't been killed succesfully
(probably hanging in disk-wait) and when they fail to fault in pages,
the process gets a signal 11.