i801_smbus 0000:00:1f.4: Transaction timeout on 5.8.x
validatedev
Status: New User - Welcome
Joined: 06 Sep 2020
Posts: 1
Reply Quote
uname -r :
:: Code ::
5.8.0-7.1-liquorix-amd64


I see some errors on dmesg which was not found on vanilla or xanmod:

dmesg | grep "i801_smbus 0000:00:1f.4":
:: Code ::

[    0.476830] i801_smbus 0000:00:1f.4: SPD Write Disable is set
[    0.477329] i801_smbus 0000:00:1f.4: SMBus using PCI interrupt
[    0.689541] i801_smbus 0000:00:1f.4: Timeout waiting for interrupt!
[    0.689542] i801_smbus 0000:00:1f.4: Transaction timeout
[    0.691538] i801_smbus 0000:00:1f.4: Failed terminating the transaction
[    0.691609] i801_smbus 0000:00:1f.4: SMBus is busy, can't use it!


dmesg: https://drive.google.com/file/d/1fT5yOw_5WpyJmoHRmTuD9MPIt-J9Tf-I/view?usp=sharing
lsmod: https://drive.google.com/file/d/1VbZ6wjYuKMMJrJe6l2dZ98uNeo42OnPi/view?usp=sharing
Back to top
techAdmin
Status: Site Admin
Joined: 26 Sep 2003
Posts: 3990
Location: East Coast, West Coast? I know it's one of them.
Reply Quote
Show: inxi -bxz

so we can skip the guessing games.
Back to top
damentz
Status: Assistant
Joined: 09 Sep 2008
Posts: 851
Reply Quote
Is your system not booting? This module's responsibility is to access sensor data on your motherboard. If your sensor data still works then this error isn't important.

Also, are there any other errors around i801_smbus messages? From this Arch Linux forum, another module was fighting for the same resource and blacklisting i2c_i801 was the solution.
Back to top
damentz
Status: Assistant
Joined: 09 Sep 2008
Posts: 851
Reply Quote
I wanted to point out as well that my ThinkPad gets an error with the i801_smbus/i2c_i801 module.

If I leave the module running on my laptop, the laptop refuses to suspend, no errors in the kernel log. But if I unload the module and close the laptop lid, the laptop suspends properly and the thinkpad LED pulsates correctly, indicating it reached its sleep state correctly.

As far as sensor data goes, I didn't lose anything. My theory, like I mentioned last post, is that there's a new module that takes ownership of the resource i2c_i801 wants before it's able to query the hardware. Most likely the clearlinux patches reorder some hardware initialization, but so far there doesn't appear to be any downside to blacklisting the module if you get the "SMBus is busy, can't use it!" message.
Back to top
Display posts from previous:   

All times are GMT - 8 Hours