public inbox for linux-i2c@vger.kernel.org
 help / color / mirror / Atom feed
From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: Wolfram Sang <wsa@kernel.org>,
	Chris Murphy <lists@colorremedies.com>,
	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 10:01:09 +0300	[thread overview]
Message-ID: <20230425070109.GU66750@black.fi.intel.com> (raw)
In-Reply-To: <ZEdsLw+dJhdHVdEO@sai>

Hi Chris,

Would you be able to bisect this to a mainline commit?

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.

Also what does /proc/interrupts show for this?

On Tue, Apr 25, 2023 at 07:59:11AM +0200, Wolfram Sang wrote:
> 
> 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



  reply	other threads:[~2023-04-25  7:01 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 [this message]
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=20230425070109.GU66750@black.fi.intel.com \
    --to=mika.westerberg@linux.intel.com \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=jarkko.nikula@linux.intel.com \
    --cc=linux-i2c@vger.kernel.org \
    --cc=lists@colorremedies.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