From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: Baolu Lu <baolu.lu@linux.intel.com>
Cc: George Hilliard <thirtythreeforty@gmail.com>,
Joerg Roedel <joro@8bytes.org>, Will Deacon <will@kernel.org>,
"iommu@lists.linux.dev" <iommu@lists.linux.dev>,
"linux1394-devel@lists.sourceforge.net"
<linux1394-devel@lists.sourceforge.net>,
Stefan Richter <stefanr@s5r6.in-berlin.de>
Subject: Re: 5.19.9 regression: DMAR error on i7-8650U
Date: Mon, 19 Sep 2022 08:27:20 +0300 [thread overview]
Message-ID: <Yyf9uIzwbb6O2E7o@black.fi.intel.com> (raw)
In-Reply-To: <4379585e-42e4-53d9-8ca4-bf5b8ff3c95d@linux.intel.com>
Hi George,
On Mon, Sep 19, 2022 at 08:53:48AM +0800, Baolu Lu wrote:
> On 9/18/22 8:00 AM, George Hilliard wrote:
> > I'm experiencing a regression on 5.19.9 from 5.19.8. Not sure if you are
> > already aware of this, apologies if it's noise. My hunch is that this
> > is an iommu problem since there were quite a few iommu changes in .9,
> > but I have also Cc'd Firewire maintainers on the chance that I'm wrong.
> >
> > My Apple Thunderbolt to Firewire adapter has quit working on 5.19.9 on
> > my Thinkpad T480s (i7-8650U), with the following log message while
> > enumerating the device (reformatted for email):
> >
> > [ 318.263546] thunderbolt 0-1: new device found, vendor=0x1 device=0x8004
> > [ 318.263559] thunderbolt 0-1: Apple, Inc. Thunderbolt to FireWire Adapter
> > [ 318.342416] pcieport 0000:05:01.0: pciehp: Slot(1): Card present
> > [ 318.342428] pcieport 0000:05:01.0: pciehp: Slot(1): Link Up
> > (snip)
> > [ 318.503177] pcieport 0000:08:00.0: enabling device (0000 -> 0003)
> > [ 318.504976] firewire_ohci 0000:09:00.0: enabling device (0000 -> 0002)
> > [ 318.562000] firewire_ohci 0000:09:00.0: added OHCI v1.10 device
> > as card 4, 8 IR + 8 IT contexts, quirks 0x0, physUB
> > [ 318.562109] DMAR: DRHD: handling fault status reg 2
> > [ 318.562114] DMAR: [INTR-REMAP] Request device [09:00.0] fault
> > index 0x8080 [fault reason 0x25] Blocked a
> > compatibility format interrupt request
> >
> > The last two lines are the new error.
> >
> > Happy to provide more details or experiment; this happens nearly every time.
> >
> > George
> >
>
> + Mika.
Since this is a regression, I wonder if you are able to bisect it to the
commit that caused the issue? As you say there are a couple of IOMMU
related changes between v5.19.8 and v5.19.9 so one option is to revert
them one by one and see if the problem goes away:
f7f13b8d49bf3eff2c98230532e0671195277216 swiotlb: avoid potential left shift overflow
9516acba29e322202674d18f4dc383879f7813a5 iommu/vt-d: Fix possible recursive locking in intel_iommu_init()
420d2045715588ad44cd7d806864a223b4fc05c9 iommu/vt-d: Correctly calculate sagaw value of IOMMU
77a2d61334f715293c20f4fa30df035fd870fba4 iommu/virtio: Fix interaction with VFIO
32e4b8dbc9119c07ea1888e72c8a5681b82e180c iommu: Fix false ownership failure on AMD systems with PASID activated
next prev parent reply other threads:[~2022-09-19 5:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-18 0:00 5.19.9 regression: DMAR error on i7-8650U George Hilliard
2022-09-19 0:53 ` Baolu Lu
2022-09-19 5:27 ` Mika Westerberg [this message]
2022-09-19 8:09 ` Mika Westerberg
2022-09-19 14:44 ` Mika Westerberg
2022-09-19 19:05 ` George Hilliard
2022-09-20 8:16 ` Baolu Lu
2022-09-19 8:31 ` 5.19.9 regression: DMAR error on i7-8650U #forregzbot Thorsten Leemhuis
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=Yyf9uIzwbb6O2E7o@black.fi.intel.com \
--to=mika.westerberg@linux.intel.com \
--cc=baolu.lu@linux.intel.com \
--cc=iommu@lists.linux.dev \
--cc=joro@8bytes.org \
--cc=linux1394-devel@lists.sourceforge.net \
--cc=stefanr@s5r6.in-berlin.de \
--cc=thirtythreeforty@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.