[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20220118165325.GA3301052@dhcp-10-100-145-180.wdc.com>
Date: Tue, 18 Jan 2022 08:53:25 -0800
From: Keith Busch <kbusch@...nel.org>
To: Paul Menzel <pmenzel@...gen.mpg.de>
Cc: Jens Axboe <axboe@...nel.dk>,
Christoph Hellwig <hch@...radead.org>,
Sagi Grimberg <sagi@...mberg.me>,
linux-nvme@...ts.infradead.org, iommu@...ts.linux-foundation.org,
LKML <linux-kernel@...r.kernel.org>
Subject: Re: nvme: IO_PAGE_FAULT logged with Intel SSDPEKKF512G8
On Tue, Jan 18, 2022 at 03:32:45PM +0100, Paul Menzel wrote:
> On a Dell OptiPlex 5055 with an Intel SSDPEKKF512G8, Linux 5.10.82 reported
> an IO_PAGE_FAULT error. This is the first and only time this has happened.
>
> $ dmesg --level=err
> [ 4.194306] nvme 0000:01:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x000c address=0xffffc080 flags=0x0050]
> [ 4.206970] nvme 0000:01:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x000c address=0xffffc000 flags=0x0050]
> [ 7.327820] kfd kfd: VERDE not supported in kfd
> $ lspci -nn -s 01:00.0
> 01:00.0 Non-Volatile memory controller [0108]: Intel Corporation SSD Pro 7600p/760p/E 6100p Series [8086:f1a6] (rev 03)
I think it's a bug with the iommu implementation. If it causes problems,
you can typically work around it with kernel parameter "iommu=soft".
Powered by blists - more mailing lists