linux-kernel - [Regression] dmesg warnings after "i2c: smbus: Support up to 8 SPD EEPROMs"

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <53582ef1-6d05-4379-a445-5f879cd676b8@o2.pl>
Date: Tue, 30 Apr 2024 21:39:03 +0200
From: Mateusz Jończyk <mat.jonczyk@...pl>
To: Jean Delvare <jdelvare@...e.de>
Cc: linux-kernel@...r.kernel.org, linux-i2c@...r.kernel.org,
 ruirui.yang@...ux.dev, Wolfram Sang <wsa@...nel.org>
Subject: [Regression] dmesg warnings after "i2c: smbus: Support up to 8 SPD
 EEPROMs"

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@...ux.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
> "
> 
> 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