From: Baolu Lu <baolu.lu@linux.intel.com>
To: George Hilliard <thirtythreeforty@gmail.com>,
Joerg Roedel <joro@8bytes.org>, Will Deacon <will@kernel.org>,
Mika Westerberg <mika.westerberg@linux.intel.com>
Cc: baolu.lu@linux.intel.com,
"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:53:48 +0800 [thread overview]
Message-ID: <4379585e-42e4-53d9-8ca4-bf5b8ff3c95d@linux.intel.com> (raw)
In-Reply-To: <485A6EA5-6D58-42EA-B298-8571E97422DE@getmailspring.com>
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.
Best regards,
baolu
next prev parent reply other threads:[~2022-09-19 0:59 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 [this message]
2022-09-19 5:27 ` Mika Westerberg
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=4379585e-42e4-53d9-8ca4-bf5b8ff3c95d@linux.intel.com \
--to=baolu.lu@linux.intel.com \
--cc=iommu@lists.linux.dev \
--cc=joro@8bytes.org \
--cc=linux1394-devel@lists.sourceforge.net \
--cc=mika.westerberg@linux.intel.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox