public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Corentin Labbe <clabbe.montjoie@gmail.com>
To: Vasant Hegde <vasant.hegde@amd.com>
Cc: joro@8bytes.org, suravee.suthikulpanit@amd.com, will@kernel.org,
	robin.murphy@arm.com, iommu@lists.linux.dev,
	linux-kernel@vger.kernel.org
Subject: Re: iommu: flood of ahci 0000:e6:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0055 address=0xa14a4000 flags=0x0070]
Date: Wed, 5 Feb 2025 14:41:40 +0100	[thread overview]
Message-ID: <Z6NqlD2Je5xVtFui@Red> (raw)
In-Reply-To: <0e4c38a8-3f7c-4cbe-9dd0-9e73d4d947e0@amd.com>

Le Wed, Feb 05, 2025 at 05:33:50PM +0530, Vasant Hegde a écrit :
> Hi,
> 
> On 2/3/2025 2:35 PM, Corentin Labbe wrote:
> > Hello
> > 
> > I have a supermicro server which is flooded of kernel message:
> > ahci 0000:e6:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0055 address=0xa14a4000 flags=0x0070]
> 
> 0x70 means, Page was present, its write request, but device doesn't have
> required permission.
> 
> As Robin mentioned, it could be FW region. Can you please double check?
> 
> Also what is the failure scenario? You see as soon as you boot or after running
> some tests? Can you provide dmesg?
> 
> -Vasant
> 

Hello

How to double check firmware region ?

For other questions, I just sent an email to Robin with all answers.

Thanks
Regards

      reply	other threads:[~2025-02-05 13:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-03  9:05 iommu: flood of ahci 0000:e6:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0055 address=0xa14a4000 flags=0x0070] Corentin Labbe
2025-02-03 13:01 ` Robin Murphy
2025-02-05 13:36   ` Corentin Labbe
2025-02-05 18:53     ` Robin Murphy
2025-02-05 12:03 ` Vasant Hegde
2025-02-05 13:41   ` Corentin Labbe [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Z6NqlD2Je5xVtFui@Red \
    --to=clabbe.montjoie@gmail.com \
    --cc=iommu@lists.linux.dev \
    --cc=joro@8bytes.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robin.murphy@arm.com \
    --cc=suravee.suthikulpanit@amd.com \
    --cc=vasant.hegde@amd.com \
    --cc=will@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox