From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from lists.xenproject.org (lists.xenproject.org [192.237.175.120]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 1C2D3C54E71 for ; Fri, 22 Mar 2024 19:22:47 +0000 (UTC) Received: from list by lists.xenproject.org with outflank-mailman.697087.1088330 (Exim 4.92) (envelope-from ) id 1rnkTA-0001sa-88; Fri, 22 Mar 2024 19:22:24 +0000 X-Outflank-Mailman: Message body and most headers restored to incoming version Received: by outflank-mailman (output) from mailman id 697087.1088330; Fri, 22 Mar 2024 19:22:24 +0000 Received: from localhost ([127.0.0.1] helo=lists.xenproject.org) by lists.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1rnkTA-0001sT-5b; Fri, 22 Mar 2024 19:22:24 +0000 Received: by outflank-mailman (input) for mailman id 697087; Fri, 22 Mar 2024 19:22:23 +0000 Received: from se1-gles-flk1-in.inumbo.com ([94.247.172.50] helo=se1-gles-flk1.inumbo.com) by lists.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1rnkT9-0001sN-Kr for xen-devel@lists.xenproject.org; Fri, 22 Mar 2024 19:22:23 +0000 Received: from mailhost.m5p.com (mailhost.m5p.com [74.104.188.4]) by se1-gles-flk1.inumbo.com (Halon) with ESMTPS id 80149ce1-e881-11ee-a1ee-f123f15fe8a2; Fri, 22 Mar 2024 20:22:20 +0100 (CET) Received: from m5p.com (mailhost.m5p.com [IPv6:2001:470:1f07:15ff:0:0:0:f7]) by mailhost.m5p.com (8.17.1/8.15.2) with ESMTPS id 42MJM42A055590 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Fri, 22 Mar 2024 15:22:10 -0400 (EDT) (envelope-from ehem@m5p.com) Received: (from ehem@localhost) by m5p.com (8.17.1/8.15.2/Submit) id 42MJM1fV055589; Fri, 22 Mar 2024 12:22:01 -0700 (PDT) (envelope-from ehem) X-BeenThere: xen-devel@lists.xenproject.org List-Id: Xen developer discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: xen-devel-bounces@lists.xenproject.org Precedence: list Sender: "Xen-devel" X-Inumbo-ID: 80149ce1-e881-11ee-a1ee-f123f15fe8a2 Date: Fri, 22 Mar 2024 12:22:01 -0700 From: Elliott Mitchell To: Kelly Choi Cc: xen-devel@lists.xenproject.org, Jan Beulich , Andrew Cooper , Roger Pau =?iso-8859-1?Q?Monn=E9?= , Wei Liu Subject: Re: Serious AMD-Vi(?) issue Message-ID: References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: On Fri, Mar 22, 2024 at 04:41:45PM +0000, Kelly Choi wrote: > > I can see you've recently engaged with our community with some issues you'd > like help with. > We love the fact you are participating in our project, however, our > developers aren't able to help if you do not provide the specific details. Please point to specific details which have been omitted. Fairly little data has been provided as fairly little data is available. The primary observation is large numbers of: (XEN) AMD-Vi: IO_PAGE_FAULT: DDDD:bb:dd.f d0 addr ffffff???????000 flags 0x8 I Lines in Xen's ring buffer. I recall spotting 3 messages from Linux's SATA driver (which weren't saved due to other causes being suspected), which would likely be associated with hundreds or thousands of the above log messages. I never observed any messages from the NVMe subsystem during that phase. The most overt sign was telling the Linux kernel to scan for inconsistencies and the kernel finding some. The domain didn't otherwise appear to notice trouble. This is from memory, it would take some time to discover whether any messages were missed. Present mitigation action is inhibiting the messages, but the trouble is certainly still lurking. -- (\___(\___(\______ --=> 8-) EHM <=-- ______/)___/)___/) \BS ( | ehem+sigmsg@m5p.com PGP 87145445 | ) / \_CS\ | _____ -O #include O- _____ | / _/ 8A19\___\_|_/58D2 7E3D DDF4 7BA6 <-PGP-> 41D1 B375 37D0 8714\_|_/___/5445