Date: Wed, 19 Oct 2022 21:49:35 +0100 From: Karl Pielorz <kpielorz_lst@tdx.co.uk> To: =?UTF-8?Q?Roger_Pau_Monn=C3=A9?= <roger.pau@citrix.com> Cc: freebsd-xen@freebsd.org Subject: Re: Recently moved to XS 8.2 on new hardware - seen a couple of FreeBSD DomU lock ups? Message-ID: <D7A2C118A79EECB1DD99A9AE@[10.12.30.106]> In-Reply-To: <Y06q3bx2/BbazkML@Air-de-Roger> References: <3C47F89ECDBA642ACCC7B932@[10.12.30.106]> <Y0l00fUaRtwIIjJS@Air-de-Roger> <91CF514F28FADFC45E157B96@[10.12.30.106]> <Y06q3bx2/BbazkML@Air-de-Roger>
next in thread | previous in thread | raw e-mail | index | archive | help
--On 18 October 2022 15:32 +0200 Roger Pau Monn=C3=A9 = <roger.pau@citrix.com>=20 wrote: > Since it might not be feasible to setup the watchdog on all VMs my > recommendation would be to try sending an NMI to the stuck processor, > and see if we can get a trace that way, see: > > https://lists.freebsd.org/archives/freebsd-xen/2022-October/000125.html > > That seems to get me a trace when used on a non-locked up VM, so it's > worth a try. Ok, I'll give that a go... No guarantee of when it'll happen next - but=20 thanks again, for at least giving me something to do / try :) -Karl
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?D7A2C118A79EECB1DD99A9AE>