From: "Chris Murphy" <lists@colorremedies.com>
To: "Mika Westerberg" <mika.westerberg@linux.intel.com>,
"Wolfram Sang" <wsa@kernel.org>,
"Andy Shevchenko" <andriy.shevchenko@linux.intel.com>,
"Jarkko Nikula" <jarkko.nikula@linux.intel.com>,
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 13:14:35 -0400 [thread overview]
Message-ID: <a08d27b1-6eed-4fba-a3e9-b3b6746c88c3@app.fastmail.com> (raw)
In-Reply-To: <20230425070109.GU66750@black.fi.intel.com>
On Tue, Apr 25, 2023, at 3:01 AM, Mika Westerberg wrote:
> Hi Chris,
>
> Would you be able to bisect this to a mainline commit?
Difficult in the near term.
> At least looking at the changes between v6.3-rc1 and v6.3-rc7 there is
> virtually nothing to any of these drivers involved. The log itself looks
> like:
>
> dev_vdbg(idma64->dma.dev, "%s: status=%#x\n", __func__, status);
>
> so this should not be enabled at all unless CONFIG_DMADEVICES_VDEBUG is
> set to y which seems odd in distro kernel.
$ 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
It follows the bug, though I'm not sure if this is the true source of the problem?
> Also what does /proc/interrupts show for this?
Attached to bug report.
https://bugzilla-attachments.redhat.com/attachment.cgi?id=1959838
--
Chris Murphy
next prev parent reply other threads:[~2023-04-25 17:15 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
2023-04-25 7:01 ` Mika Westerberg
2023-04-25 17:14 ` Chris Murphy [this message]
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=a08d27b1-6eed-4fba-a3e9-b3b6746c88c3@app.fastmail.com \
--to=lists@colorremedies.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=jarkko.nikula@linux.intel.com \
--cc=linux-i2c@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
--cc=wsa@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