Bug 2188969

Summary: kernel: intel-lpss 0000:00:15.1: idma64_irq: status=0x0, millions of lines spamming journal
Product: [Fedora] Fedora Reporter: Chris Murphy <bugzilla>
Component: kernelAssignee: Kernel Maintainer List <kernel-maint>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 41CC: acaringi, adscvr, airlied, alciregi, bskeggs, hdegoede, hpa, jarodwilson, jglisse, josef, kernel-maint, lgoncalv, linville, masami256, mchehab, ptalbert, steved
Target Milestone: ---Keywords: Reopened
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2025-12-16 17:05:53 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
dmesg
none
lspci -vvnn
none
acpidump
none
/proc/interrupts kernel-6.3.0 none

Description Chris Murphy 2023-04-23 20:53:44 UTC 
1. Please describe the problem:

thousands of lines intermittently dumped into the journal, over 3 million in a single boot
Apr 21 14:24:55 fovo.local kernel: intel-lpss 0000:00:15.1: idma64_irq: status=0x0


2. What is the Version-Release number of the kernel:

6.3.0-0.rc7.20230420gitcb0856346a60.59.fc39.x86_64+debug


3. Did it work previously in Fedora? If so, what kernel version did the issue
   *first* appear?  Old kernels are available for download at
   https://koji.fedoraproject.org/koji/packageinfo?packageID=8:

Does not happen in any 6.2 series kernel. I'll need to narrow down the first 6.3 series kernel it appears in.


4. Can you reproduce this issue? If so, please provide the steps to reproduce
   the issue below:


5. Does this problem occur with the latest Rawhide kernel? To install the
   Rawhide kernel, run ``sudo dnf install fedora-repos-rawhide`` followed by
   ``sudo dnf update --enablerepo=rawhide kernel``:

Yes

6. Are you running any modules that not shipped with directly Fedora's kernel?:

No


7. Please attach the kernel logs. You can get the complete kernel log
   for a boot with ``journalctl --no-hostname -k > dmesg.txt``. If the
   issue occurred on a previous boot, use the journalctl ``-b`` flag.

They are too large, there's ~27 journal files, 60M each. But the full logs aren't super helpful:

Unfiltered, first event appears without prior warning.

Apr 21 13:41:59 fovo.local wpa_supplicant[1052]: wlp0s20f3: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-43 noise=9999 txrate=780000
Apr 21 14:24:55 fovo.local kernel: intel-lpss 0000:00:15.1: idma64_irq: status=0x0
Apr 21 14:24:55 fovo.local kernel: intel-lpss 0000:00:15.1: idma64_irq: status=0x0
Apr 21 14:24:55 fovo.local kernel: intel-lpss 0000:00:15.1: idma64_irq: status=0x0
...snip thousands of identical lines


$ journalctl -b-1 | grep lpss
Apr 21 13:25:41 fovo.local kernel: intel-lpss 0000:00:15.0: enabling device (0000 -> 0002)
Apr 21 13:25:55 fovo.local kernel: intel-lpss 0000:00:15.0: WARN: Device release is not defined so it is not safe to unbind this driver while in use
Apr 21 13:25:55 fovo.local kernel: intel-lpss 0000:00:15.1: WARN: Device release is not defined so it is not safe to unbind this driver while in use
Apr 21 14:24:55 fovo.local kernel: intel-lpss 0000:00:15.1: idma64_irq: status=0x0
Apr 21 14:24:55 fovo.local kernel: intel-lpss 0000:00:15.1: idma64_irq: status=0x0
Apr 21 14:24:55 fovo.local kernel: intel-lpss 0000:00:15.1: idma64_irq: status=0x0
Apr 21 14:24:55 fovo.local kernel: intel-lpss 0000:00:15.1: idma64_irq: status=0x0


On kernel 6.2 series, the warnings don't appear.

Apr 22 14:21:19 fovo.local kernel: intel-lpss 0000:00:15.0: enabling device (0000 -> 0002)

That's the only message.


Hardware:
[    0.000000] DMI: LENOVO 20QDS3E200/20QDS3E200, BIOS N2HET73W (1.56 ) 12/06/2022
a.k.a. Lenovo Thinkpad X1 Carbon, 7th gen
Comment 1 Chris Murphy 2023-04-23 21:10:44 UTC 
A quick search of mainline kernel git log filtered for intel-lpss, nothing shows up since October. The problem does happen with 6.3-rc7 (release), but doesn't happen with 6.3-rc1.
Comment 2 Chris Murphy 2023-04-24 21:32:23 UTC 
Bug first appears in 6.3.0-0.rc2.20230317git38e04b3e4240.27.fc39.x86_64+debug

Last good version is 6.3.0-0.rc2.20230315git6015b1aca1a2.25.fc39.x86_64+debug

Bug appears in 6.3.0 release.
Comment 3 Chris Murphy 2023-04-24 21:34:49 UTC 
Created attachment 1959654 [details]
dmesg
Comment 4 Chris Murphy 2023-04-24 21:35:39 UTC 
Created attachment 1959655 [details]
lspci -vvnn
Comment 5 Chris Murphy 2023-04-24 21:36:53 UTC 
Created attachment 1959656 [details]
acpidump
Comment 6 Chris Murphy 2023-04-24 21:55:20 UTC 
Upstream email https://lore.kernel.org/linux-i2c/47ff45c8-20da-4eac-acad-6d51353f95c6@app.fastmail.com/T/#u
Comment 7 Chris Murphy 2023-04-25 17:00:43 UTC 
$ grep DMADEVICES /boot/config-6.3.0-0.rc2.20230315git6015b1aca1a2.25.fc39.x86_64+debug 
CONFIG_DMADEVICES=y
CONFIG_DMADEVICES_DEBUG=y
# CONFIG_DMADEVICES_VDEBUG is not set
$ grep DMADEVICES /boot/config-6.3.0-0.rc2.20230317git38e04b3e4240.27.fc39.x86_64+debug 
CONFIG_DMADEVICES=y
CONFIG_DMADEVICES_DEBUG=y
CONFIG_DMADEVICES_VDEBUG=y
Comment 8 Chris Murphy 2023-04-25 17:13:05 UTC 
Created attachment 1959838 [details]
/proc/interrupts kernel-6.3.0
Comment 9 Chris Murphy 2023-04-26 00:04:34 UTC 
https://gitlab.com/cki-project/kernel-ark/-/commit/9b58c93f4dba78d895238ea5c09540aa837d8736

CONFIG_DMADEVICES_VDEBUG=y is the direct result of the problem; but maybe the messages point to an actual problem. Thing is I have no idea how far back the problem could go to even entertain bisecting it.
Comment 10 Aoife Moloney 2023-11-23 01:41:53 UTC 
This message is a reminder that Fedora Linux 37 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 37 on 2023-12-05.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
'version' of '37'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version. Note that the version field may be hidden.
Click the "Show advanced fields" button if you do not see it.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 37 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.
Comment 11 Aoife Moloney 2024-01-15 12:11:54 UTC 
Fedora Linux 37 entered end-of-life (EOL) status on 2023-12-05.

Fedora Linux 37 is no longer maintained, which means that it
will not receive any further security or bug fix updates. As a result we
are closing this bug.

If you can reproduce this bug against a currently maintained version of Fedora Linux
please feel free to reopen this bug against that version. Note that the version
field may be hidden. Click the "Show advanced fields" button if you do not see
the version field.

If you are unable to reopen this bug, please file a new report against an
active release.

Thank you for reporting this bug and we are sorry it could not be fixed.
Comment 12 Chris Murphy 2024-09-24 23:01:23 UTC 
6.11.0-63.fc41.x86_64

Still happens, makes the debug kernel impractical to use.
Comment 13 Chris Murphy 2024-09-24 23:43:55 UTC 
Upstream recommended unsetting CONFIG_DMADEVICES_VDEBUG

https://lore.kernel.org/linux-i2c/20230426045127.GZ66750@black.fi.intel.com/
Comment 14 Adam Williamson (Red Hat non-Fedora) 2025-12-02 01:12:43 UTC 
This message is a reminder that Fedora Linux 41 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 41 on 2025-12-15.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
'version' of '41'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version. Note that the version field may be hidden.
Click the "Show advanced fields" button if you do not see it.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 41 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.
Comment 15 Samyak Jain (RedHat) 2025-12-16 17:05:53 UTC 
Fedora Linux 41 entered end-of-life (EOL) status on 2025-12-15.

Fedora Linux 41 is no longer maintained, which means that it
will not receive any further security or bug fix updates. As a result we
are closing this bug.

If you can reproduce this bug against a currently maintained version of Fedora Linux
please feel free to reopen this bug against that version. Note that the version
field may be hidden. Click the "Show advanced fields" button if you do not see
the version field.

If you are unable to reopen this bug, please file a new report against an
active release.

Thank you for reporting this bug and we are sorry it could not be fixed.