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

[Manuel Bouyer <bouyer%antioche.eu.org@localhost>]

The following reply was made to PR port-xen/47057; it has been noted by GNATS.

From: Manuel Bouyer <bouyer%antioche.eu.org@localhost>
To: Roger Pau =?iso-8859-1?Q?Monn=E9?= <roger.pau%citrix.com@localhost>
Cc: "gnats-bugs%NetBSD.org@localhost" <gnats-bugs%NetBSD.org@localhost>,
        "port-xen-maintainer%netbsd.org@localhost" 
<port-xen-maintainer%NetBSD.org@localhost>,
        "gnats-admin%netbsd.org@localhost" <gnats-admin%NetBSD.org@localhost>,
        "netbsd-bugs%netbsd.org@localhost" <netbsd-bugs%NetBSD.org@localhost>,
        "royger%netbsd.org@localhost" <royger%NetBSD.org@localhost>
Subject: Re: port-xen/47057: Xen NetBSD DomU file system trash under Linux
 Dom0
Date: Sat, 20 Oct 2012 17:38:53 +0200

 On Sat, Oct 20, 2012 at 05:31:11PM +0200, Roger Pau Monné wrote:
 > > 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.
 
 You mean, it's always at xenbus_thread+0xf5 ? You never see other offsets ?
 
 > 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.
 
 Maybe just a printf instead of a printk at first.
 If the offset never changes, I wonder if it could be stuck in
        (void)HYPERVISOR_console_io(CONSOLEIO_write, ret, buf);
 
 -- 
 Manuel Bouyer <bouyer%antioche.eu.org@localhost>
      NetBSD: 26 ans d'experience feront toujours la difference
 --