From nobody Wed Oct 19 20:49:35 2022 X-Original-To: freebsd-xen@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4Mt2tp0b7Tz4fQnl for ; Wed, 19 Oct 2022 20:50:42 +0000 (UTC) (envelope-from kpielorz_lst@tdx.co.uk) Received: from smtp.krpservers.com (smtp.krpservers.com [62.13.128.145]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.krpservers.com", Issuer "RapidSSL TLS DV RSA Mixed SHA256 2020 CA-1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Mt2tn0Z75z3G56 for ; Wed, 19 Oct 2022 20:50:40 +0000 (UTC) (envelope-from kpielorz_lst@tdx.co.uk) Received: from [10.12.30.106] by smtp.krpservers.com (8.16.1/8.15.2) with ESMTPSA id 29JKo251049877 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 19 Oct 2022 21:50:05 +0100 (BST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tdx.co.uk; s=krpdkim; t=1666212605; bh=NE8KL9e/CUgnm2Lccwr0WRlvHHe2cG5am3OSLQWjrbw=; h=Date:From:To:Subject; b=jzOa54rjLFpcqJm3yLr+uVRv0+pAncZdPGFFNJ/dS8HMDJGFyDe/u4adbaWRy6kY2 Low+ZdBaVdyxCy7lADVMC8OGExZDqNwxbNOFfU6jZpsmrd6W4OK3pidzqxol/LrZ8G hlAM7bU1J8PwqJf8E3KOteRR3slX7h1gkVkVjyjVMGhSkBHQmYPsAGsk3Bu5h0C734 LkEQt8D+5lqCYxfRVr44yViq5JIADy9oZj2BpyDdHnkv38K4iyc9no6rxM8z/pdb1h Qnpml13KBUVos+Umf/K5mSGKwZPLQJqeqUj97KFsy1aKs/UNdGP36ab78UVwS24JIN 07yagibfkItGg== Date: Wed, 19 Oct 2022 21:49:35 +0100 From: Karl Pielorz To: =?UTF-8?Q?Roger_Pau_Monn=C3=A9?= 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: In-Reply-To: References: <3C47F89ECDBA642ACCC7B932@[10.12.30.106]> <91CF514F28FADFC45E157B96@[10.12.30.106]> X-Mailer: Mulberry/4.0.8 (Win32) List-Id: Discussion List-Archive: https://lists.freebsd.org/archives/freebsd-xen List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-xen@freebsd.org X-BeenThere: freebsd-xen@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-Rspamd-Queue-Id: 4Mt2tn0Z75z3G56 X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=tdx.co.uk header.s=krpdkim header.b=jzOa54rj; dmarc=pass (policy=none) header.from=tdx.co.uk; spf=pass (mx1.freebsd.org: domain of kpielorz_lst@tdx.co.uk designates 62.13.128.145 as permitted sender) smtp.mailfrom=kpielorz_lst@tdx.co.uk X-Spamd-Result: default: False [-2.43 / 15.00]; SUBJECT_ENDS_QUESTION(1.00)[]; NEURAL_HAM_SHORT(-1.00)[-0.999]; NEURAL_HAM_MEDIUM(-1.00)[-0.998]; NEURAL_HAM_LONG(-0.93)[-0.928]; MID_RHS_IP_LITERAL(0.50)[]; DMARC_POLICY_ALLOW(-0.50)[tdx.co.uk,none]; R_DKIM_ALLOW(-0.20)[tdx.co.uk:s=krpdkim]; R_SPF_ALLOW(-0.20)[+a:smtp.krpservers.com]; MIME_GOOD(-0.10)[text/plain]; ASN(0.00)[asn:60969, ipnet:62.13.128.0/24, country:GB]; MLMMJ_DEST(0.00)[freebsd-xen@freebsd.org]; MIME_TRACE(0.00)[0:+]; FROM_EQ_ENVFROM(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; DKIM_TRACE(0.00)[tdx.co.uk:+]; FROM_HAS_DN(0.00)[]; ARC_NA(0.00)[]; RCPT_COUNT_TWO(0.00)[2]; TO_DN_SOME(0.00)[]; RCVD_COUNT_TWO(0.00)[2]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_TLS_ALL(0.00)[] X-ThisMailContainsUnwantedMimeParts: N --On 18 October 2022 15:32 +0200 Roger Pau Monn=C3=A9 = =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