From: Christian Zigotzky <chzigotzky@xenosoft.de>
To: Sven Peter <sven@kernel.org>
Cc: linux-i2c@vger.kernel.org,
linuxppc-dev <linuxppc-dev@lists.ozlabs.org>,
mad skateman <madskateman@gmail.com>,
"R.T.Dickinson" <rtd2@xtra.co.nz>,
hypexed@yahoo.com.au, Christian Zigotzky <info@xenosoft.de>
Subject: Re: i2c-pasemi messages since kernel 6.16
Date: Mon, 11 Aug 2025 18:59:43 +0200 [thread overview]
Message-ID: <5e0a55a9-10ff-4594-aada-34eb31b2d8aa@xenosoft.de> (raw)
In-Reply-To: <d4b0a847-0617-4735-b6a1-ff5375f166bd@kernel.org>
On 11 August 2025 at 06:12 pm, Sven Peter wrote:
> hi,
>
> On 10.08.25 18:47, Christian Zigotzky wrote:
>> Hello Sven,
>>
>> Since the kernel 6.16 we have the following messages during the boot.
>>
>> [ 9.459706] i2c-pasemi 0000:00:1c.0: NACK, status 0x08210100
>> [ 9.649736] i2c-pasemi 0000:00:1c.0: Issuing reset due to status
>> 0x08210100 (xfstatus 0x00000001)
>> [ 9.690696] i2c-pasemi 0000:00:1c.1: NACK, status 0x08210100
>> [ 9.708651] i2c-pasemi 0000:00:1c.1: Issuing reset due to status
>> 0x08210100 (xfstatus 0x00000001)
>> [ 9.892693] i2c-pasemi 0000:00:1c.2: NACK, status 0x08210100
>> [ 9.911535] i2c-pasemi 0000:00:1c.2: Issuing reset due to status
>> 0x08210100 (xfstatus 0x00000001)
>>
>> What exactly do these messages mean?
>
> Do you just see these messages or are there also any other issues like a
> device on the i2c bus not working anymore when it worked fine before?
> We added some additional logging recently and I suspect that this has
> always been happening and no one noticed.
>
>
>
> Sven
>
>
Hello Sven,
Thank you for your answer.
I just see these messages. There aren't any other issues.
Further information:
$ cat /proc/version
Linux version 6.12.22-powerpc64-smp (geeko@buildhost)
(powerpc64-suse-linux-gcc (SUSE Linux) 7.5.0, GNU ld (GNU Binutils;
devel:gcc / SLE-15) 2.43.1.20240828-150300.536) #1 SMP Tue Apr 8
09:47:26 CEST 2025
$ sudo dmesg | grep -i i2c
[ 5.032840] i2c_dev: i2c /dev entries driver
[ 5.440998] i2c i2c-9: Detected TI TMP423 chip at 0x4c
$ sudo i2cdetect -l
[sudo] password for christian:
i2c-3 i2c Radeon i2c bit bus 0x93 I2C adapter
i2c-10 i2c PA Semi SMBus adapter (0000:00:1c.1) I2C adapter
i2c-1 i2c Radeon i2c bit bus 0x91 I2C adapter
i2c-8 i2c card0-DP-1 I2C adapter
i2c-6 i2c Radeon i2c bit bus 0x96 I2C adapter
i2c-4 i2c Radeon i2c bit bus 0x94 I2C adapter
i2c-11 i2c PA Semi SMBus adapter (0000:00:1c.2) I2C adapter
i2c-2 i2c Radeon i2c bit bus 0x92 I2C adapter
i2c-0 i2c Radeon i2c bit bus 0x90 I2C adapter
i2c-9 i2c PA Semi SMBus adapter (0000:00:1c.0) I2C adapter
i2c-7 i2c Radeon i2c bit bus 0x97 I2C adapter
i2c-5 i2c Radeon i2c bit bus 0x95 I2C adapter
$ cat /proc/version
Linux version 6.16.0-powerpc64-smp (geeko@buildhost)
(powerpc64-suse-linux-gcc (SUSE Linux) 11.5.0, GNU ld (GNU Binutils;
devel:gcc / SLE-15) 2.43.1.20240828-150300.536) #1 SMP Mon Jul 28
06:44:21 CEST 2025
$ sudo dmesg | grep -i i2c
[sudo] password for christian:
[ 3.381852] i2c_dev: i2c /dev entries driver
[ 3.591326] i2c-pasemi 0000:00:1c.0: NACK, status 0x08210100
[ 3.604687] i2c-pasemi 0000:00:1c.0: Issuing reset due to status
0x08210100 (xfstatus 0x00000001)
[ 3.623181] i2c i2c-9: Detected TI TMP423 chip at 0x4c
[ 3.640313] i2c-pasemi 0000:00:1c.0: NACK, status 0x08210100
[ 3.653561] i2c-pasemi 0000:00:1c.0: Issuing reset due to status
0x08210100 (xfstatus 0x00000001)
[ 3.667314] i2c-pasemi 0000:00:1c.0: NACK, status 0x08210100
[ 3.680416] i2c-pasemi 0000:00:1c.0: Issuing reset due to status
0x08210100 (xfstatus 0x00000001)
[ 3.694312] i2c-pasemi 0000:00:1c.0: NACK, status 0x08210100
[ 3.708309] i2c-pasemi 0000:00:1c.1: NACK, status 0x08210100
[ 3.721268] i2c-pasemi 0000:00:1c.1: Issuing reset due to status
0x08210100 (xfstatus 0x00000001)
[ 3.735309] i2c-pasemi 0000:00:1c.1: NACK, status 0x08210100
[ 3.748276] i2c-pasemi 0000:00:1c.1: Issuing reset due to status
0x08210100 (xfstatus 0x00000001)
[ 3.762309] i2c-pasemi 0000:00:1c.1: NACK, status 0x08210100
[ 3.775289] i2c-pasemi 0000:00:1c.1: Issuing reset due to status
0x08210100 (xfstatus 0x00000001)
[ 3.789309] i2c-pasemi 0000:00:1c.1: NACK, status 0x08210100
[ 3.802265] i2c-pasemi 0000:00:1c.1: Issuing reset due to status
0x08210100 (xfstatus 0x00000001)
[ 3.816315] i2c-pasemi 0000:00:1c.1: NACK, status 0x08210100
[ 3.830308] i2c-pasemi 0000:00:1c.2: NACK, status 0x08210100
[ 3.843392] i2c-pasemi 0000:00:1c.2: Issuing reset due to status
0x08210100 (xfstatus 0x00000001)
[ 3.857308] i2c-pasemi 0000:00:1c.2: NACK, status 0x08210100
[ 3.870637] i2c-pasemi 0000:00:1c.2: Issuing reset due to status
0x08210100 (xfstatus 0x00000001)
[ 3.884307] i2c-pasemi 0000:00:1c.2: NACK, status 0x08210100
[ 3.897148] i2c-pasemi 0000:00:1c.2: Issuing reset due to status
0x08210100 (xfstatus 0x00000001)
[ 3.911309] i2c-pasemi 0000:00:1c.2: NACK, status 0x08210100
[ 3.924874] i2c-pasemi 0000:00:1c.2: Issuing reset due to status
0x08210100 (xfstatus 0x00000001)
[ 3.939307] i2c-pasemi 0000:00:1c.2: NACK, status 0x08210100
[ 9.335546] i2c-pasemi 0000:00:1c.0: Issuing reset due to status
0x08210100 (xfstatus 0x00000001)
sudo i2cdetect -l
[sudo] password for christian:
i2c-3 i2c Radeon i2c bit bus 0x93 I2C adapter
i2c-10 i2c PA Semi SMBus adapter (0000:00:1c.1) I2C adapter
i2c-1 i2c Radeon i2c bit bus 0x91 I2C adapter
i2c-8 i2c card0-DP-1 I2C adapter
i2c-6 i2c Radeon i2c bit bus 0x96 I2C adapter
i2c-4 i2c Radeon i2c bit bus 0x94 I2C adapter
i2c-11 i2c PA Semi SMBus adapter (0000:00:1c.2) I2C adapter
i2c-2 i2c Radeon i2c bit bus 0x92 I2C adapter
i2c-0 i2c Radeon i2c bit bus 0x90 I2C adapter
i2c-9 i2c PA Semi SMBus adapter (0000:00:1c.0) I2C adapter
i2c-7 i2c Radeon i2c bit bus 0x97 I2C adapter
i2c-5 i2c Radeon i2c bit bus 0x95 I2C adapter
Cheers,
Christian
prev parent reply other threads:[~2025-08-11 16:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-10 16:47 i2c-pasemi messages since kernel 6.16 Christian Zigotzky
2025-08-10 17:24 ` Christian Zigotzky
2025-08-11 16:12 ` Sven Peter
2025-08-11 16:59 ` Christian Zigotzky [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=5e0a55a9-10ff-4594-aada-34eb31b2d8aa@xenosoft.de \
--to=chzigotzky@xenosoft.de \
--cc=hypexed@yahoo.com.au \
--cc=info@xenosoft.de \
--cc=linux-i2c@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=madskateman@gmail.com \
--cc=rtd2@xtra.co.nz \
--cc=sven@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.