Date: Fri, 28 Jan 2011 11:26:46 +1100 From: Alex <joovke@joovke.com> To: freebsd-xen@freebsd.org Subject: Re: xenbusb_nop_confighook_cb timeout Message-ID: <4D420D46.2060600@joovke.com> In-Reply-To: <C7E74E12-B131-4926-AC98-FF19413E5CB5@kfu.com> References: <8ED72DD4-E865-4BF2-87C9-643B89D5E9AC@kfu.com> <alpine.BSF.2.00.1101260859380.20212@tiktik.epipe.com> <794BEEE2-A788-4939-BE23-E0E10DC51EC4@kfu.com> <4D413E35.9030107@joovke.com> <93D60E91-84E7-4372-AA57-29435917C574@kfu.com> <4D41E3D1.7040100@joovke.com> <C7E74E12-B131-4926-AC98-FF19413E5CB5@kfu.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi Nick, Would you mind showing me a copy of your dmesg for the XENHVM kernel? I just want to make a comparison with mine. Perhaps this subject may get someone else's attention, otherwise I'll file a PR. :) On 28/01/2011 9:40 AM, Nick Sayer wrote: > On Jan 27, 2011, at 1:29 PM, Alex wrote: > >> I've had that geom warning before on real hardware and it's never stopped it from working. > Ah, well, then never mind. I thought maybe it was germane to the hang. > > I don't know which differences we might have between us that would account for it working for me, but not for you. My machine is GPT+ZFS and it had no trouble transitioning to XENHVT once the "do something smart" panic went away. > > _______________________________________________ > freebsd-xen@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-xen > To unsubscribe, send any mail to "freebsd-xen-unsubscribe@freebsd.org" >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4D420D46.2060600>