From: "Krzysztof Olędzki" <ole@ans.pl>
To: Heiner Kallweit <hkallweit1@gmail.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Guenter Roeck <linux@roeck-us.net>,
Bartosz Golaszewski <brgl@bgdev.pl>
Cc: stable@vger.kernel.org, linux-i2c@vger.kernel.org,
linux-hwmon@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Regression caused by "eeprom: at24: Probe for DDR3 thermal sensor in the SPD case" - "sysfs: cannot create duplicate filename"
Date: Sat, 6 Jul 2024 18:42:16 -0700 [thread overview]
Message-ID: <be8eb641-a16d-4fc5-b4cc-35c663c37df7@ans.pl> (raw)
In-Reply-To: <3365237d-5fb7-4cbd-a1c0-aff39433f5c2@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 983 bytes --]
On 02.07.2024 at 13:25, Heiner Kallweit wrote:
> On 23.06.2024 20:47, Krzysztof Olędzki wrote:
>> Hi,
>>
>> After upgrading kernel to Linux 6.6.34 on one of my systems, I noticed "sysfs: cannot create duplicate filename" and i2c registration errors in dmesg, please see below.
>>
>> This seems to be related to https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=linux-6.6.y&id=4d5ace787273cb159bfdcf1c523df957938b3e42 - reverting the change fixes the problem.
<CUT>
>
> Could you please test whether the attached two experimental patches fix the issue for you?
> They serialize client device instantiation per I2C adapter, and include the client device
> name in the check whether a bus address is busy.
Sadly, they crash the kernel.
I will get serial console attached there next week, so will be able to capture the full crash.
For now, I was able to obtain a photo. I'm very sorry for the quality, just wanted to provide
something for now.
Krzysztof
[-- Attachment #2: i2c-bug.png --]
[-- Type: image/png, Size: 743008 bytes --]
next prev parent reply other threads:[~2024-07-07 1:43 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-23 18:47 Regression caused by "eeprom: at24: Probe for DDR3 thermal sensor in the SPD case" - "sysfs: cannot create duplicate filename" Krzysztof Olędzki
2024-06-24 5:33 ` Guenter Roeck
2024-06-24 8:38 ` Krzysztof Olędzki
2024-06-24 14:54 ` Guenter Roeck
2024-06-24 16:23 ` Guenter Roeck
2024-06-24 20:58 ` Heiner Kallweit
2024-06-25 3:45 ` Guenter Roeck
2024-06-27 11:29 ` Krzysztof Olędzki
2024-06-27 12:12 ` Krzysztof Olędzki
2024-06-27 11:24 ` Krzysztof Olędzki
2024-06-29 21:56 ` Heiner Kallweit
2024-06-24 5:43 ` Greg Kroah-Hartman
2024-06-24 13:35 ` Guenter Roeck
2024-07-02 20:25 ` Heiner Kallweit
2024-07-07 1:42 ` Krzysztof Olędzki [this message]
2024-07-23 14:12 ` Krzysztof Olędzki
2024-08-03 17:19 ` Heiner Kallweit
2024-08-13 16:28 ` Krzysztof Olędzki
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=be8eb641-a16d-4fc5-b4cc-35c663c37df7@ans.pl \
--to=ole@ans.pl \
--cc=brgl@bgdev.pl \
--cc=gregkh@linuxfoundation.org \
--cc=hkallweit1@gmail.com \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=stable@vger.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