New kernels

[xeno74]

a/drivers/i2c/busses/i2c-pasemi-core.c

Code: Select all

 	/* If any badness happened or there is data in the FIFOs, reset the FIFOs */
 	if ((status & (SMSTA_MRNE | SMSTA_JMD | SMSTA_MTO | SMSTA_TOM | SMSTA_MTN | SMSTA_MTA)) ||
-	    !(status & SMSTA_MTE))
+	    !(status & SMSTA_MTE)) {
+		dev_warn(smbus->dev, "Issuing reset due to status 0x%08x (xfstatus 0x%08x)\n",
+			 status, reg_read(smbus, REG_XFSTA));
 		pasemi_reset(smbus);
+	}

[xeno74]

I have found the changes because of the i2c messages:

New:

- pasemi: improve error handling in reset, smbus clear, timeouts (i2c-for-6.16-rc1)
- pasemi: cleanups and refactorings (i2c-for-6.16-rc1)

• i2c: pasemi: Log bus reset causes
• i2c: pasemi: Improve error recovery
• i2c: pasemi: Improve timeout handling
• i2c: pasemi: Enable the unjam machine
• i2c: pasemi: Sort includes alphabetically
• i2c: pasemi: Use correct bits.h include

[xeno74]

Hi All,

The merge window is over. Linus Torvalds has released the RC1 of kernel 6.17 for testing yesterday.

I compiled it for X1000 and e5500 machines (X5000/20, X5000/40, Mirari, and QEMU VMs) yesterday.

Download and further information: github.com



Please test the kernels.

Thanks,
Christian

[Hypex]

I have found the changes because of the i2c messages:

Okay great. That's very informative. Now I wonder if they are just harmless or I have a slight hardware issue.

I'm also considering if it's worth booting a 6.15 kernel in debug mode. If there are extra i2c debug options.To see if it outputs similar messages.

[Hypex]

Hi All,

The merge window is over. Linus Torvalds has released the RC1 of kernel 6.17 for testing yesterday.

So tested on Fienix. Worked fine. No obvious issues and modules loaded fine so far as I could tell.

Checked new i2c output. Still seems a bit talkative. But has no reset messages like before.

Code: Select all

[    8.943926] i2c_dev: i2c /dev entries driver
[    9.058590] i2c-pasemi 0000:00:1c.0: NACK, status 0x08210100
[    9.080763] i2c i2c-8: Detected TI TMP423 chip at 0x4c
[    9.090766] i2c-pasemi 0000:00:1c.0: NACK, status 0x08210100
[    9.095767] i2c-pasemi 0000:00:1c.0: NACK, status 0x08210100
[    9.109775] i2c-pasemi 0000:00:1c.0: NACK, status 0x08210100
[    9.162766] i2c-pasemi 0000:00:1c.1: NACK, status 0x08210100
[    9.205763] i2c-pasemi 0000:00:1c.1: NACK, status 0x08210100
[    9.490767] i2c-pasemi 0000:00:1c.1: NACK, status 0x08210100
[    9.507584] i2c-pasemi 0000:00:1c.1: NACK, status 0x08210100
[    9.542739] i2c-pasemi 0000:00:1c.1: NACK, status 0x08210100
[    9.618636] i2c-pasemi 0000:00:1c.2: NACK, status 0x08210100
[    9.636765] i2c-pasemi 0000:00:1c.2: NACK, status 0x08210100
[    9.654765] i2c-pasemi 0000:00:1c.2: NACK, status 0x08210100
[    9.672764] i2c-pasemi 0000:00:1c.2: NACK, status 0x08210100
[    9.690762] i2c-pasemi 0000:00:1c.2: NACK, status 0x08210100

[xeno74]

Hi Hypex,

Thanks a lot for testing!

FYI:

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

Have you noticed any issues with the i2c buses?

I checked the i2c buses with i2cdetect -l but I haven’t found any issues yet.

Cheers,
Christian

[Hypex]

Have you noticed any issues with the i2c buses?

I haven't but I don't know what to look for either.

I just installed i2cdetect to check. I've started collecting data and output. It seems to be fine apart from NACK messages in system log.

However, I've collected a lot of output which I think will be too distracting here, so will open a new thread later and post my findings.

[xeno74]

Hi All,

Linus Torvalds has released the RC2 of kernel 6.17 for testing.

I have compiled it for X1000 and e5500 machines (X5000/20, X5000/40, Mirari, and QEMU VMs).

Download and further information: github.com



Please test the kernels.

Thanks,
Christian

[Hypex]

Linus Torvalds has released the RC2 of kernel 6.17 for testing.

Okay so I've just tested it on Zesty MATE after installing it earlier. Kernel is stable with no issues. Typing this from it now.

The piix4 driver loads up but the info is telling. It complains about the SMBus Host Controller not being enabled. I've grepped out some lines that stand out to me:

Code: Select all

amigaone@ubuntu:~$ dmesg | grep -e i2c -e 16550 -e smbus
[    0.414031] Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
[    0.415955] serial8250.0: ttyS0 at I/O 0x8703f8 (irq = 73, base_baud = 8333333) is a 16550A
[    0.416789] serial8250.0: ttyS1 at I/O 0x8702f8 (irq = 74, base_baud = 8333333) is a 16550A
[    0.418224] 0000:00:1d.0: ttyS0 at I/O 0x8703f8 (irq = 73, base_baud = 8333333) is a 16550A
[    0.418966] 0000:00:1d.1: ttyS1 at I/O 0x8702f8 (irq = 74, base_baud = 8333333) is a 16550A
[    4.003154] i2c_dev: i2c /dev entries driver
[    4.113752] i2c-pasemi 0000:00:1c.0: NACK, status 0x08210100
[    4.133238] i2c-pasemi 0000:00:1c.0: Issuing reset due to status 0x08210100 (xfstatus 0x00000001)
[    4.146721] i2c i2c-8: Detected TI TMP423 chip at 0x4c
[    4.237929] i2c-pasemi 0000:00:1c.0: NACK, status 0x08210100
[    4.237939] i2c-pasemi 0000:00:1c.0: Issuing reset due to status 0x08210100 (xfstatus 0x00000001)
[    4.238729] i2c-pasemi 0000:00:1c.0: NACK, status 0x08210100
[    4.257527] i2c-pasemi 0000:00:1c.0: Issuing reset due to status 0x08210100 (xfstatus 0x00000001)
[    4.277628] i2c-pasemi 0000:00:1c.0: NACK, status 0x08210100
[    4.296717] i2c-pasemi 0000:00:1c.1: NACK, status 0x08210100
[    4.336393] i2c-pasemi 0000:00:1c.1: Issuing reset due to status 0x08210100 (xfstatus 0x00000001)
[    4.347723] i2c-pasemi 0000:00:1c.1: NACK, status 0x08210100
[    4.358022] i2c-pasemi 0000:00:1c.1: Issuing reset due to status 0x08210100 (xfstatus 0x00000001)
[    4.369538] i2c-pasemi 0000:00:1c.1: NACK, status 0x08210100
[    4.402603] i2c-pasemi 0000:00:1c.1: Issuing reset due to status 0x08210100 (xfstatus 0x00000001)
[    4.425230] i2c-pasemi 0000:00:1c.1: NACK, status 0x08210100
[    4.463464] i2c-pasemi 0000:00:1c.1: Issuing reset due to status 0x08210100 (xfstatus 0x00000001)
[    4.489708] i2c-pasemi 0000:00:1c.1: NACK, status 0x08210100
[    4.516343] i2c-pasemi 0000:00:1c.2: NACK, status 0x08210100
[    4.568964] i2c-pasemi 0000:00:1c.2: Issuing reset due to status 0x08210100 (xfstatus 0x00000001)
[    4.583718] i2c-pasemi 0000:00:1c.2: NACK, status 0x08210100
[    4.597751] i2c-pasemi 0000:00:1c.2: Issuing reset due to status 0x08210100 (xfstatus 0x00000001)
[    4.612716] i2c-pasemi 0000:00:1c.2: NACK, status 0x08210100
[    4.627033] i2c-pasemi 0000:00:1c.2: Issuing reset due to status 0x08210100 (xfstatus 0x00000001)
[    4.642629] i2c-pasemi 0000:00:1c.2: NACK, status 0x08210100
[    4.657077] i2c-pasemi 0000:00:1c.2: Issuing reset due to status 0x08210100 (xfstatus 0x00000001)
[    4.671714] i2c-pasemi 0000:00:1c.2: NACK, status 0x08210100
[    5.037092] snd_serial_u16550 snd_serial_u16550.0: no UART detected at 0x1
[   19.189237] piix4_smbus 0000:05:14.0: SMBus Host Controller not enabled!
[   19.800019] i2c-pasemi 0000:00:1c.0: Issuing reset due to status 0x08210100 (xfstatus 0x00000001)

Some more info:

Code: Select all

amigaone@ubuntu:~$ uname -a
Linux ubuntu 6.17.0-rc2-powerpc64-smp #1 SMP Mon Aug 18 06:41:30 CEST 2025 ppc64 ppc64 ppc64 GNU/Linux
amigaone@ubuntu:~$ lsmod
Module                  Size  Used by
i2c_piix4              20480  0
snd_hda_codec_idt      53248  1
snd_hda_codec_generic    90112  1 snd_hda_codec_idt
snd_hda_codec_atihdmi    16384  1
snd_hda_codec_hdmi     45056  1 snd_hda_codec_atihdmi
snd_hda_intel          36864  4
snd_intel_dspcfg       12288  1 snd_hda_intel
snd_hda_codec         135168  5 snd_hda_codec_generic,snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec_atihdmi,snd_hda_codec_idt
snd_hda_core           98304  6 snd_hda_codec_generic,snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec,snd_hda_codec_atihdmi,snd_hda_codec_idt

[xeno74]

Okay so I've just tested it on Zesty MATE after installing it earlier. Kernel is stable with no issues. Typing this from it now.

Great! Many thanks for testing!