Re: port-xen/47057: Xen NetBSD DomU file system trash under Linux Dom0

[Roger Pau Monné <roger.pau%citrix.com@localhost>]

On 20/10/12 13:47, Manuel Bouyer wrote:
> What would be interesting here is a
> tr/a ffffa0000236e940

db{0}> tr/a ffffa0000236e940
trace: pid 0 lid 26 at 0xffffa0002e4848a8
breakpoint() at netbsd:breakpoint+0x5
xencons_tty_input() at netbsd:xencons_tty_input+0xc9
xencons_handler() at netbsd:xencons_handler+0x79
intr_biglock_wrapper() at netbsd:intr_biglock_wrapper+0x1d
evtchn_do_event() at netbsd:evtchn_do_event+0x15a
call_evtchn_do_event() at netbsd:call_evtchn_do_event+0xd
hypervisor_callback() at netbsd:hypervisor_callback+0x9e
xenbus_thread() at netbsd:xenbus_thread+0xf5

> (the lwp pointer of the xenbus thread). And alst what xenbus_thread+0xf5
> points to in sources.

Since the kernel was compiled without -g I guess there's no way to get
that now.

> You can also try to type 'continue' and enter ddb again to see
> if things changes (especially where in xenbus_thread it is
> interrupted).

Nope, the system is completely frozen, tried several times and the trace
is exactly the same. Will compile a new kernel with -g and let's see
what I can get, but I bet xenbus_thread is blocked at:

831: printk("XENBUS error %d while reading message\n", err);

In fact I'm going to replace that with a panic.