From: Baolu Lu <baolu.lu@linux.intel.com>
To: Heiner Kallweit <hkallweit1@gmail.com>,
Robin Murphy <robin.murphy@arm.com>,
Joerg Roedel <jroedel@suse.de>,
Bjorn Helgaas <bhelgaas@google.com>,
Lorenzo Pieralisi <lpieralisi@kernel.org>,
Jason Gunthorpe <jgg@nvidia.com>
Cc: linux-acpi@vger.kernel.org, iommu@lists.linux.dev
Subject: Re: New "something fishy here" warning fires
Date: Thu, 13 Mar 2025 12:38:18 +0800 [thread overview]
Message-ID: <09bc17bd-4d25-4afd-8f6c-56707ea9bc92@linux.intel.com> (raw)
In-Reply-To: <3046c6a2-72a0-412e-a865-48dc129be0df@gmail.com>
On 3/13/25 03:34, Heiner Kallweit wrote:
> Since "iommu: Get DT/ACPI parsing into the proper probe path" I get the following
> on a N100-based mini pc. The warning pops up 4 times, for:
>
> PNP0C14:00
> PNP0C14:01
> PNP0C14:00
> PNP0C14:01
>
> Any other info you'd be interested in?
>
> [ +0.000139] Unpacking initramfs...
> [ +0.000690] ------------[ cut here ]------------
> [ +0.000028] acpi-wmi PNP0C14:00: late IOMMU probe at driver bind, something fishy here!
> [ +0.000041] WARNING: CPU: 1 PID: 1 at drivers/iommu/iommu.c:449 __iommu_probe_device+0x12b/0x530
> [ +0.000034] Modules linked in:
> [ +0.000024] CPU: 1 UID: 0 PID: 1 Comm: swapper/0 Not tainted 6.14.0-rc6-next-20250312+ #2
> [ +0.000029] Hardware name: Default string Default string/Default string, BIOS ADLN.M6.SODIMM.ZB.CY.015 08/08/2023
> [ +0.000032] RIP: 0010:__iommu_probe_device+0x12b/0x530
> [ +0.000019] Code: 68 00 74 28 4c 8b 73 50 4d 85 f6 75 03 4c 8b 33 48 89 df e8 d7 ec 00 00 4c 89 f2 48 c7 c7 b8 91 7b 9e 48 89 c6 e8 f5 3e 96 ff >
> [ +0.000055] RSP: 0000:ffffb031c006fc98 EFLAGS: 00010282
> [ +0.000021] RAX: 0000000000000000 RBX: ffff9469416c5010 RCX: 0000000000000000
> [ +0.000023] RDX: 0000000000000002 RSI: 0000000000000003 RDI: 00000000ffffffff
> [ +0.000023] RBP: ffffb031c006fcd8 R08: 0000000000000000 R09: ffffb031c006fae8
> [ +0.000023] R10: ffffffff9eb1ea68 R11: 0000000000000003 R12: ffffffff9e485280
> [ +0.000023] R13: ffffb031c006fd70 R14: ffff946940bb8ec0 R15: 0000000000000000
> [ +0.000023] FS: 0000000000000000(0000) GS:ffff946b18bec000(0000) knlGS:0000000000000000
> [ +0.000037] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
> [ +0.000020] CR2: 0000000000000000 CR3: 000000016c650001 CR4: 0000000000770ef0
> [ +0.000023] PKRU: 55555554
> [ +0.000012] Call Trace:
> [ +0.000010] <TASK>
> [ +0.000011] ? show_regs.part.0+0x1d/0x30
> [ +0.000019] ? show_regs.cold+0x8/0xd
> [ +0.000016] ? __iommu_probe_device+0x12b/0x530
> [ +0.000017] ? __warn.cold+0xc2/0x15e
> [ +0.000018] ? __iommu_probe_device+0x12b/0x530
> [ +0.000017] ? report_bug+0xe3/0x170
> [ +0.000016] ? console_unlock+0x7d/0x110
> [ +0.000018] ? __iommu_probe_device+0x12b/0x530
> [ +0.000016] ? __iommu_probe_device+0x12d/0x530
> [ +0.000017] ? handle_bug+0x116/0x170
> [ +0.000018] ? exc_invalid_op+0x18/0x70
> [ +0.000017] ? asm_exc_invalid_op+0x1b/0x20
> [ +0.000022] ? __iommu_probe_device+0x12b/0x530
> [ +0.000018] ? __iommu_probe_device+0x12b/0x530
> [ +0.000019] ? __pfx_probe_iommu_group+0x10/0x10
> [ +0.000017] probe_iommu_group+0x26/0x50
> [ +0.000016] bus_for_each_dev+0x79/0xd0
> [ +0.000020] iommu_device_register+0xbe/0x230
> [ +0.000021] intel_iommu_init+0xd76/0xf40
> [ +0.000016] ? _raw_spin_unlock_irqrestore+0x55/0x80
> [ +0.000022] ? __this_cpu_preempt_check+0x13/0x20
> [ +0.000018] ? lockdep_hardirqs_on+0x7d/0x110
> [ +0.000018] ? trace_hardirqs_on+0x5b/0xd0
> [ +0.000017] ? _raw_spin_unlock_irqrestore+0x3c/0x80
> [ +0.000020] ? __pfx_pci_iommu_init+0x10/0x10
> [ +0.000021] pci_iommu_init+0xd/0x40
>
The fix is here.
https://lore.kernel.org/linux-iommu/72a4853e7ef36e7c1c4ca171ed4ed8e1a463a61a.1741791691.git.robin.murphy@arm.com/
Thanks,
baolu
next prev parent reply other threads:[~2025-03-13 4:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-12 19:34 New "something fishy here" warning fires Heiner Kallweit
2025-03-13 4:38 ` Baolu Lu [this message]
2025-03-13 11:09 ` Robin Murphy
2025-03-13 11:49 ` Joerg Roedel
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=09bc17bd-4d25-4afd-8f6c-56707ea9bc92@linux.intel.com \
--to=baolu.lu@linux.intel.com \
--cc=bhelgaas@google.com \
--cc=hkallweit1@gmail.com \
--cc=iommu@lists.linux.dev \
--cc=jgg@nvidia.com \
--cc=jroedel@suse.de \
--cc=linux-acpi@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=robin.murphy@arm.com \
/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.