You are not logged in.

#1 2024-12-23 07:20:23

Anonymous0909
Member
Registered: 2024-03-16
Posts: 5

i2c Failed and SMBus Timeout

❯ sudo dmesg -l err
[    0.254486] ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.GPP2.WLAN._S0W], AE_ALREADY_EXISTS (20240827/dswload2-327)
[    0.254495] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20240827/psobject-220)
[    1.144164] hub 6-0:1.0: config failed, hub doesn't have any ports! (err -19)
[    1.165934] integrity: Problem loading X.509 certificate -65
[    1.165945] integrity: Problem loading X.509 certificate -65
[    5.761451] i2c i2c-9: SMBus Timeout!
[    5.761501] i2c i2c-9: Failed reset at end of transaction (01)
[    5.761636] i2c i2c-9: Failed! (01)
[    5.772588] i2c i2c-9: Failed! (01)
[    5.772690] i2c i2c-9: Failed! (01)
[    5.772779] i2c i2c-9: Failed! (01)
[    5.772865] i2c i2c-9: Failed! (01)
[    5.772953] i2c i2c-9: Failed! (01)
[    5.773041] i2c i2c-9: Failed! (01)
[    5.773130] i2c i2c-9: Failed! (01)
[    5.773218] i2c i2c-9: Failed! (01)
[    5.773313] i2c i2c-10: Failed! (05)
❯ sudo i2cdetect -F 1
Functionalities implemented by /dev/i2c-1:
I2C                              yes
SMBus Quick Command              no
SMBus Send Byte                  yes
SMBus Receive Byte               yes
SMBus Write Byte                 yes
SMBus Read Byte                  yes
SMBus Write Word                 yes
SMBus Read Word                  yes
SMBus Process Call               no
SMBus Block Write                yes
SMBus Block Read                 yes
SMBus Block Process Call         no
SMBus PEC                        no
I2C Block Write                  yes
I2C Block Read                   yes
SMBus Host Notify                no
10-bit addressing                yes
Target mode                      no
❯ sudo i2cdetect -y 0
Warning: Can't use SMBus Quick Write command, will skip some addresses
     0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
00:                                                 
10:                                                 
20:                                                 
30: -- -- -- 33 -- -- -- --                         
40:                                                 
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
60:                                                 
70:            
❯ lsmod | grep i2c
i2c_piix4              36864  0
i2c_smbus              20480  1 i2c_piix4
i2c_hid_acpi           12288  0
i2c_hid                45056  1 i2c_hid_acpi
i2c_dev                24576  0
i2c_algo_bit           20480  1 amdgpu

kernel: Linux none 6.12.6-2-cachyos #1 SMP PREEMPT_DYNAMIC Thu, 19 Dec 2024 21:23:18 +0000 x86_64 GNU/Linux

error with i2c, what could be the reason? other kernels have the same error.

Last edited by Anonymous0909 (2024-12-23 17:26:06)

Offline

#2 2024-12-23 09:41:49

seth
Member
Registered: 2012-09-03
Posts: 60,822

Re: i2c Failed and SMBus Timeout

Please use [code][/code] tags. Edit your post in this regard.

It might help to know what i2c-9 and i2c-10 are, please post the entire dmesg (or system journal), no just isolated error messages.
Do you also experience any symptoms (missing devices etc)?

Offline

#3 2024-12-23 17:30:15

Anonymous0909
Member
Registered: 2024-03-16
Posts: 5

Re: i2c Failed and SMBus Timeout

seth wrote:

Please use [code][/code] tags. Edit your post in this regard.

It might help to know what i2c-9 and i2c-10 are, please post the entire dmesg (or system journal), no just isolated error messages.
Do you also experience any symptoms (missing devices etc)?

i2c is essentially a router, it works like a bus, SMBus is built on i2c, it connects, detects, and controls devices, and as for devices, basically everything works except that I don't use it yet or don't know, but the driver is important and it would be nice to fix it.

Offline

#4 2024-12-23 18:08:43

seth
Member
Registered: 2012-09-03
Posts: 60,822

Re: i2c Failed and SMBus Timeout

Is that explanation from SquatGPT?
SMBus is an i2c derivate, not "built on it".

And that still leaves us at "Fix *what*?"
It's still not clear whether or what any problem is here.
You've posted some disconnected kernel/module messages from some undisclosed hardware.

Maybe try your luck at lkml…

Offline

#5 2024-12-24 06:13:42

Anonymous0909
Member
Registered: 2024-03-16
Posts: 5

Re: i2c Failed and SMBus Timeout

seth wrote:

Is that explanation from SquatGPT?
SMBus is an i2c derivate, not "built on it".

And that still leaves us at "Fix *what*?"
It's still not clear whether or what any problem is here.
You've posted some disconnected kernel/module messages from some undisclosed hardware.

Maybe try your luck at lkml…

I don't know why you're responding so aggressively or if I asked a stupid question, but I answered what i2c does, and I'm attaching a link to this module. https://www.kernel.org/doc/html/latest/i2c/index.html where else is it better described for what it is needed, about i2c-9 ic-10 it is simply not carrying any information at all, but it is unlikely that you will help with this problem considering how You're talking aggressively, considering that I asked for help, and about the core logs, well, that's actually the whole i2c log. There's nothing else from it. I don't even know what you want me to add.

Last edited by Anonymous0909 (2024-12-24 06:17:43)

Offline

#6 2024-12-24 10:22:39

seth
Member
Registered: 2012-09-03
Posts: 60,822

Re: i2c Failed and SMBus Timeout

I'm not aggressive and I didn't ask what i2c does, so I don't understand why you felt like posting what very much sounds something ChatGPT told you.
The open question still remains what your "problem" actually is.
Whether it's just some spurious messages in your journal because the bus is probing non-existing channels or there's an actual impact: something that doesn't work and that you maybe relate to those messages.

I don't even know what you want me to add

Post your complete system journal for the boot:

sudo journalctl -b | curl -F 'file=@-' 0x0.st

Offline

#7 2024-12-25 16:06:32

Anonymous0909
Member
Registered: 2024-03-16
Posts: 5

Re: i2c Failed and SMBus Timeout

seth wrote:

I'm not aggressive and I didn't ask what i2c does, so I don't understand why you felt like posting what very much sounds something ChatGPT told you.
The open question still remains what your "problem" actually is.
Whether it's just some spurious messages in your journal because the bus is probing non-existing channels or there's an actual impact: something that doesn't work and that you maybe relate to those messages.

I don't even know what you want me to add

Post your complete system journal for the boot:

sudo journalctl -b | curl -F 'file=@-' 0x0.st

http://0x0.st/8rlF.txt

Offline

#8 2024-12-25 17:08:17

seth
Member
Registered: 2012-09-03
Posts: 60,822

Re: i2c Failed and SMBus Timeout

1. same w/ the non-cachyos kernel or lts kernel?
==>>> 2. is there a parallel windows installation? <<====
3. do webcam, touchpad and keyboard work? Is there any indication on your side that this isn't just noise from the controller?

Offline

#9 2024-12-25 17:23:48

Anonymous0909
Member
Registered: 2024-03-16
Posts: 5

Re: i2c Failed and SMBus Timeout

seth wrote:

1. same w/ the non-cachyos kernel or lts kernel?
==>>> 2. is there a parallel windows installation? <<====
3. do webcam, touchpad and keyboard work? Is there any indication on your side that this isn't just noise from the controller?

1. yes, there is a nearby windows
2. on any core, such a log
3. I don't know, I have a relatively new device and something may not work, for example, I made a patch in the kernel because there was no driver for the microphone to work, and now I'm trying to make the microphone indicator work, I don't know if i2c SMBus can control this, but still, well, in general, nothing that doesn't work for I'm not there, at least not from what I use.
4. I don't know, but the error doesn't look like something that can be ignored, especially because it's SMBus and it's clearly a problem with some devices, I also tried to look through i2detect -y 9,10,11 and only at 11 there was some information, it looks like the problem is in the 9-10 device, but the strangest thing is that they are almost identical except for with the exception of the address, I attach the information

❯ sudo i2cdetect -l
i2c-0   i2c             Synopsys DesignWare I2C adapter         I2C adapter
i2c-1   i2c             Synopsys DesignWare I2C adapter         I2C adapter
i2c-2   i2c             AMDGPU DM i2c hw bus 0                  I2C adapter
i2c-3   i2c             AMDGPU DM i2c hw bus 1                  I2C adapter
i2c-4   i2c             AMDGPU DM i2c hw bus 2                  I2C adapter
i2c-5   i2c             AMDGPU DM i2c hw bus 3                  I2C adapter
i2c-6   i2c             AMDGPU DM aux hw bus 0                  I2C adapter
i2c-7   i2c             AMDGPU DM aux hw bus 2                  I2C adapter
i2c-8   i2c             AMDGPU DM aux hw bus 3                  I2C adapter
i2c-9   smbus           SMBus PIIX4 adapter port 0 at 0b00      SMBus adapter
i2c-10  smbus           SMBus PIIX4 adapter port 2 at 0b00      SMBus adapter
i2c-11  smbus           SMBus PIIX4 adapter port 1 at 0b20      SMBus adapter

❯ sudo i2cdetect -y 9
     0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
00:                         -- -- -- -- -- -- -- -- 
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
70: -- -- -- -- -- -- -- --                         

❯ sudo i2cdetect -y 10
     0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
00:                         -- -- -- -- -- -- -- -- 
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
70: -- -- -- -- -- -- -- --                         

❯ sudo i2cdetect -y 11
     0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
00:                         08 09 0a 0b 0c 0d 0e 0f 
10: 10 11 12 13 14 15 16 17 18 19 1a 1b 1c 1d 1e 1f 
20: 20 21 22 23 24 25 26 27 28 29 2a 2b 2c 2d 2e 2f 
30: 30 31 32 33 34 35 36 37 38 39 3a 3b 3c 3d 3e 3f 
40: 40 41 42 43 44 45 46 47 48 49 4a 4b 4c 4d 4e 4f 
50: 50 51 52 53 54 55 56 57 58 59 5a 5b 5c 5d 5e 5f 
60: 60 61 62 63 64 65 66 67 68 69 6a 6b 6c 6d 6e 6f 
70: 70 71 72 73 74 75 76 77        

PS: I'm sorry for my poor English.

Last edited by Anonymous0909 (2024-12-25 17:27:53)

Offline

Board footer

Powered by FluxBB