Date: Thu, 27 Jan 2011 14:40:58 -0800 From: Nick Sayer <nsayer@kfu.com> To: freebsd-xen@freebsd.org Subject: Re: xenbusb_nop_confighook_cb timeout Message-ID: <C7E74E12-B131-4926-AC98-FF19413E5CB5@kfu.com> In-Reply-To: <4D41E3D1.7040100@joovke.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>
next in thread | previous in thread | raw e-mail | index | archive | help
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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?C7E74E12-B131-4926-AC98-FF19413E5CB5>