From: Heiner Kallweit <hkallweit1@gmail.com>
To: "Wolfram Sang" <wsa+renesas@sang-engineering.com>,
"Mateusz Jończyk" <mat.jonczyk@o2.pl>,
"Jean Delvare" <jdelvare@suse.de>,
linux-kernel@vger.kernel.org, linux-i2c@vger.kernel.org,
ruirui.yang@linux.dev, "Wolfram Sang" <wsa@kernel.org>
Subject: Re: [Regression] dmesg warnings after "i2c: smbus: Support up to 8 SPD EEPROMs"
Date: Wed, 1 May 2024 11:57:34 +0200 [thread overview]
Message-ID: <6a8f1302-1905-4bc4-84b0-a00558ebecdb@gmail.com> (raw)
In-Reply-To: <20240501072744.2xm4v3idjjsehwkq@ninjato>
On 01.05.2024 09:27, Wolfram Sang wrote:
>
> Adding Heiner...
>
> On Tue, Apr 30, 2024 at 09:39:03PM +0200, Mateusz Jończyk wrote:
>> Hello,
>>
>> I have received a regression report on
>> commit 13e3a512a29001c ("i2c: smbus: Support up to 8 SPD EEPROMs")
>> as I was subscribed to some kernel Bugzilla thread and I'm posting it here
>> to make you aware of it.
>>
>> This thread was
>>
>> Bug 213345 - i801_smbus: Timeout waiting for interrupt, driver can't access SMBus
>>
>> ruirui.yang@linux.dev on 2024-04-19 08:22:57 UTC wrote:
>>> I got similar issue on thinkpad X1 gen9 with latest 6.9.0-rc4+
>>> Git bisect the first bad commit is "13e3a512a29001c i2c: smbus: Support up to 8 SPD EEPROMs
>>> "
Thanks for the report. Repeating what I just commented in bugzilla:
The mentioned commit showed up in 6.8 only, but the problem reports
date back to at least 5.12. Original bug report in bugzilla is from
2021. So I don't think this commit is the culprit.
What is the latest known good kernel version?
How about LTS version 6.6?
>>>
>>> modprobe without param:
>>> [ 1290.401393] i801_smbus 0000:00:1f.4: SPD Write Disable is set
>>> [ 1290.401486] i801_smbus 0000:00:1f.4: SMBus using PCI interrupt
>>> [ 1290.403340] i801_smbus 0000:00:1f.4: SMBus is busy, can't use it!
>>> [ 1290.403383] i801_smbus 0000:00:1f.4: SMBus is busy, can't use it!
>>> [ 1290.403410] i801_smbus 0000:00:1f.4: SMBus is busy, can't use it!
>>> [ 1290.403437] i801_smbus 0000:00:1f.4: SMBus is busy, can't use it!
>>> [ 1290.403465] i801_smbus 0000:00:1f.4: SMBus is busy, can't use it!
>>> [ 1290.403492] i801_smbus 0000:00:1f.4: SMBus is busy, can't use it!
>>> [ 1290.403519] i801_smbus 0000:00:1f.4: SMBus is busy, can't use it!
>>> [ 1290.403546] i801_smbus 0000:00:1f.4: SMBus is busy, can't use it!
>>>
>>> with param
>>> [ 1314.568785] i801_smbus 0000:00:1f.4: Interrupt disabled by user
>>> [ 1314.568837] i801_smbus 0000:00:1f.4: SPD Write Disable is set
>>> [ 1314.568894] i801_smbus 0000:00:1f.4: SMBus using po*lling
>>> [ 1314.570230] i801_smbus 0000:00:1f.4: SMBus is busy, can't use it!
>>> [ 1314.570257] i801_smbus 0000:00:1f.4: SMBus is busy, can't use it!
>>> [ 1314.570283] i801_smbus 0000:00:1f.4: SMBus is busy, can't use it!
>>> [ 1314.570310] i801_smbus 0000:00:1f.4: SMBus is busy, can't use it!
>>> [ 1314.570336] i801_smbus 0000:00:1f.4: SMBus is busy, can't use it!
>>> [ 1314.570362] i801_smbus 0000:00:1f.4: SMBus is busy, can't use it!
>>> [ 1314.570389] i801_smbus 0000:00:1f.4: SMBus is busy, can't use it!
>>> [ 1314.570415] i801_smbus 0000:00:1f.4: SMBus is busy, can't use it!
>>
>> Link: https://bugzilla.kernel.org/show_bug.cgi?id=213345
>>
>> The param mentioned was i2c-i801.disable_features=0x10, which disables interrupt usage
>> of this driver.
>>
>> Please decide if this is serious enough to warrant a revert.
>>
>> Greetings,
>> Mateusz
>>
>>
Heiner
prev parent reply other threads:[~2024-05-01 9:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-30 19:39 [Regression] dmesg warnings after "i2c: smbus: Support up to 8 SPD EEPROMs" Mateusz Jończyk
2024-05-01 7:27 ` Wolfram Sang
2024-05-01 9:57 ` Heiner Kallweit [this message]
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=6a8f1302-1905-4bc4-84b0-a00558ebecdb@gmail.com \
--to=hkallweit1@gmail.com \
--cc=jdelvare@suse.de \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mat.jonczyk@o2.pl \
--cc=ruirui.yang@linux.dev \
--cc=wsa+renesas@sang-engineering.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).