From: Baolu Lu <baolu.lu@linux.intel.com>
To: "Tian, Kevin" <kevin.tian@intel.com>,
Markus Rathgeb <maggu2810@gmail.com>
Cc: baolu.lu@linux.intel.com,
Linux regressions mailing list <regressions@lists.linux.dev>,
Will Deacon <will@kernel.org>,
David Woodhouse <dwmw2@infradead.org>,
Joerg Roedel <joro@8bytes.org>,
"iommu@lists.linux.dev" <iommu@lists.linux.dev>,
LKML <linux-kernel@vger.kernel.org>,
Jacob Pan <jacob.jun.pan@linux.intel.com>,
Adam Williamson <awilliam@redhat.com>
Subject: Re: [regression] usb and thunderbould are misbehaving or broken due to iommu/vt-d change
Date: Sun, 1 Sep 2024 17:12:12 +0800 [thread overview]
Message-ID: <b909bc01-327a-427b-9900-8f324a229770@linux.intel.com> (raw)
In-Reply-To: <BN9PR11MB5276F533DC882B182F1A4C268C972@BN9PR11MB5276.namprd11.prod.outlook.com>
On 2024/8/30 8:29, Tian, Kevin wrote:
>> From: Markus Rathgeb<maggu2810@gmail.com>
>> Sent: Thursday, August 29, 2024 4:34 PM
>>
>> With respect to my previous comment I tested to fix it myself (I am
>> not a kernel hacker and do not know anything about iommu etc.).
>>
>> After applying the following change to the v6.11-rc5 it seems to fix my
>> problem.
>> I can connect, disconnect and connect the dock and USB is working and
>> no DMAR error.
>>
> as said there was already a fix posted which is similar to below:
>
> https://lore.kernel.org/linux-iommu/20240815124857.70038-1-baolu.lu@linux.intel.com/
Above patch has been merged in v6.11-rc6. Please try the latest kernel
version.
Thanks,
baolu
prev parent reply other threads:[~2024-09-01 9:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-28 10:27 Linux regression tracking (Thorsten Leemhuis)
2024-08-29 0:53 ` Tian, Kevin
2024-08-29 6:21 ` Markus Rathgeb
2024-08-29 7:08 ` Markus Rathgeb
2024-08-29 7:23 ` Markus Rathgeb
2024-08-29 8:33 ` Markus Rathgeb
2024-08-30 0:29 ` Tian, Kevin
2024-09-01 9:12 ` Baolu Lu [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=b909bc01-327a-427b-9900-8f324a229770@linux.intel.com \
--to=baolu.lu@linux.intel.com \
--cc=awilliam@redhat.com \
--cc=dwmw2@infradead.org \
--cc=iommu@lists.linux.dev \
--cc=jacob.jun.pan@linux.intel.com \
--cc=joro@8bytes.org \
--cc=kevin.tian@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maggu2810@gmail.com \
--cc=regressions@lists.linux.dev \
--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
all inboxes | Powered by JetHome®