From: Wolfram Sang <wsa@kernel.org>
To: Chris Murphy <lists@colorremedies.com>,
Mika Westerberg <mika.westerberg@linux.intel.com>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Jarkko Nikula <jarkko.nikula@linux.intel.com>
Cc: linux-i2c@vger.kernel.org
Subject: Re: intel-lpss 0000:00:15.1: idma64_irq: status=0x0, millions of lines spamming journal
Date: Tue, 25 Apr 2023 07:59:11 +0200 [thread overview]
Message-ID: <ZEdsLw+dJhdHVdEO@sai> (raw)
In-Reply-To: <47ff45c8-20da-4eac-acad-6d51353f95c6@app.fastmail.com>
[-- Attachment #1: Type: text/plain, Size: 879 bytes --]
CCing the designware maintainers. Not sure if it really is the I2C part
of lpss which regressed, though. There wasn't a change to the driver
since 6.3-rc1. The changes in rc1 seem unrelated to me, but I leave that
to the pros.
On Mon, Apr 24, 2023 at 05:51:15PM -0400, Chris Murphy wrote:
> Downstream bug has dmesg, lspci, acpidump attached
> https://bugzilla.redhat.com/show_bug.cgi?id=2188969
>
> The gist is repeating message:
>
> kernel: intel-lpss 0000:00:15.1: idma64_irq: status=0x0
>
> ~6800 times in a couple seconds, and in a few hours racked up over 3.3 million.
>
> 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. It does not appear in 6.2 series kernels or older.
>
>
> --
> Chris Murphy
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2023-04-25 5:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-24 21:51 intel-lpss 0000:00:15.1: idma64_irq: status=0x0, millions of lines spamming journal Chris Murphy
2023-04-25 5:59 ` Wolfram Sang [this message]
2023-04-25 7:01 ` Mika Westerberg
2023-04-25 17:14 ` Chris Murphy
2023-04-26 4:51 ` Mika Westerberg
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=ZEdsLw+dJhdHVdEO@sai \
--to=wsa@kernel.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=jarkko.nikula@linux.intel.com \
--cc=linux-i2c@vger.kernel.org \
--cc=lists@colorremedies.com \
--cc=mika.westerberg@linux.intel.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.