From: Baolu Lu <baolu.lu@linux.intel.com>
To: kobarity <kobarity@gmail.com>, Aditya Garg <gargaditya08@live.com>
Cc: "Berkel Jörg" <joerg.berkel@bfh.ch>,
"Robin Murphy" <robin.murphy@arm.com>,
"linux-input@vger.kernel.org" <linux-input@vger.kernel.org>,
"dmitry.torokhov@gmail.com" <dmitry.torokhov@gmail.com>,
"stable@vger.kernel.org" <stable@vger.kernel.org>,
"regressions@lists.linux.dev" <regressions@lists.linux.dev>,
"linux-spi@vger.kernel.org" <linux-spi@vger.kernel.org>,
"lukas@wunner.de" <lukas@wunner.de>,
"David Woodhouse" <dwmw2@infradead.org>,
"iommu@lists.linux.dev" <iommu@lists.linux.dev>,
"Joerg Roedel" <joro@8bytes.org>, "Will Deacon" <will@kernel.org>
Subject: Re: [REGRESSION] applespi from 6.12 onwards
Date: Mon, 12 May 2025 13:12:38 +0800 [thread overview]
Message-ID: <089b2370-23e4-4a22-bf57-886e46247a1f@linux.intel.com> (raw)
In-Reply-To: <eke7wmanw9xq.wl-kobarity@gmail.com>
On 5/11/25 21:31, kobarity wrote:
>
> Hi
>
> I'm also experiencing this problem on my MacBookPro14,3.
>
> Aditya Garg wrote:
>>
>> Hi Jörg
>>
>> Can you test the kernel here to see if this fixes your issue:
>>
>> https://github.com/t2linux/T2-Debian-and-Ubuntu-Kernel/actions/runs/14944200356
>>
>> Alternatively you can try compiling your own kernel with this patch:
>>
>> https://lore.kernel.org/all/0-v1-c26553717e90+65f-iommu_vtd_ss_wo_jgg@nvidia.com/
>
> As far as I have tried, this patch did not solve the problem.
>
> By bisecting, I found that this problem was introduced by commit
> 2031c469f816 ("iommu/vt-d: Add support for static identity domain").
> In fact, since this commit, it will panic at startup. This panic was
> fixed by commit 6e02a277f1db ("iommu/vt-d: Fix incorrect
> pci_for_each_dma_alias() for non-PCI devices"). So I applied commit
> 6e02a277f1db on commit 2031c469f816 and confirmed that the keyboard
> and touchpad is not working.
Have you tried to apply commit 64f792981e35 ("iommu/vt-d: Remove device
comparison in context_setup_pass_through_cb")?
>
> I also found that I can workaround this problem by reverting only the
> intel_iommu_attach_device() change in commit 2031c469f816 as in the
> attached patch, but I'm not sure if this is a reasonable fix.
>
Thanks,
baolu
next prev parent reply other threads:[~2025-05-12 5:17 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-07 7:18 [REGRESSION] applespi from 6.12 onwards Berkel Jörg
2025-05-07 16:31 ` Aditya Garg
2025-05-07 20:24 ` Berkel Jörg
2025-05-07 17:07 ` Aditya Garg
2025-05-08 2:15 ` Baolu Lu
2025-05-08 6:22 ` Dmitry Torokhov
2025-05-08 11:00 ` Aditya Garg
2025-05-08 11:29 ` Robin Murphy
2025-05-08 12:54 ` Aditya Garg
2025-05-09 15:23 ` Berkel Jörg
2025-05-10 9:57 ` Aditya Garg
2025-05-11 13:31 ` kobarity
2025-05-12 5:12 ` Baolu Lu [this message]
2025-05-12 12:16 ` kobarity
2025-05-13 1:37 ` Baolu Lu
2025-05-13 12:08 ` kobarity
2025-05-14 3:39 ` Baolu Lu
2025-05-09 2:47 ` Baolu Lu
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=089b2370-23e4-4a22-bf57-886e46247a1f@linux.intel.com \
--to=baolu.lu@linux.intel.com \
--cc=dmitry.torokhov@gmail.com \
--cc=dwmw2@infradead.org \
--cc=gargaditya08@live.com \
--cc=iommu@lists.linux.dev \
--cc=joerg.berkel@bfh.ch \
--cc=joro@8bytes.org \
--cc=kobarity@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=lukas@wunner.de \
--cc=regressions@lists.linux.dev \
--cc=robin.murphy@arm.com \
--cc=stable@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).