ismt-bus completion wait timed out issue

ismt-bus completion wait timed out issue

[Puneet Shenoy]

Hey Bill,

I see that you are the author of the i2c-ismt driver so thought will check with you on a issue that I have been seeing on my setup.

My setup has an Intel Atom S1220 Processor which has a PMBUS device on its SMBUS 2.0 controller (SMBus—Bus 0:D19:F0-1). 

Now while accessing(read/write) the PMBUS device, I see the following error messages:
[10799.333083] ismt_smbus 0000:00:13.1: completion wait timed out
[10800.337089] ismt_smbus 0000:00:13.1: completion wait timed out
[10801.341097] ismt_smbus 0000:00:13.1: completion wait timed out
[10802.345105] ismt_smbus 0000:00:13.1: completion wait timed out

All read/write access to the device fail when its in this state. The issue is hard to reproduce and happens once in a while.

I tried rmmod/modprobe the driver, but that doesn't help. I dumped the relevant registers that are dev_dbg'ed in the driver and compared the data between the failed and working cases and I don't see any difference. 
Once in a while when I am in the failed state, I see the In Progress Bit (Bit 0) in the MSTS (Master Status Register) being set but its not always the case.

Have you seen this issue before ? Any pointers on how to debug this ?

Appreciate any help.
Thanks
Puneet--
To unsubscribe from this list: send the line "unsubscribe linux-i2c" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: ismt-bus completion wait timed out issue

[sushil]

Puneet Shenoy <puneet@...> writes:

> 
> Hey Bill,
> 
> I see that you are the author of the i2c-ismt driver so thought will check 
with you on a issue that I have been
> seeing on my setup.
> 
> My setup has an Intel Atom S1220 Processor which has a PMBUS device on its 
SMBUS 2.0 controller (SMBus—Bus
> 0:D19:F0-1). 
> 
> Now while accessing(read/write) the PMBUS device, I see the following 
error messages:
> [10799.333083] ismt_smbus 0000:00:13.1: completion wait timed out
> [10800.337089] ismt_smbus 0000:00:13.1: completion wait timed out
> [10801.341097] ismt_smbus 0000:00:13.1: completion wait timed out
> [10802.345105] ismt_smbus 0000:00:13.1: completion wait timed out
> 
> All read/write access to the device fail when its in this state. The issue 
is hard to reproduce and happens
> once in a while.
> 
> I tried rmmod/modprobe the driver, but that doesn't help. I dumped the 
relevant registers that are
> dev_dbg'ed in the driver and compared the data between the failed and 
working cases and I don't see any
> difference. 
> Once in a while when I am in the failed state, I see the In Progress Bit 
(Bit 0) in the MSTS (Master Status
> Register) being set but its not always the case.
> 
> Have you seen this issue before ? Any pointers on how to debug this ?
> 
> Appreciate any help.
> Thanks
> Puneet--
> To unsubscribe from this list: send the line "unsubscribe linux-i2c" in
> the body of a message to majordomo@...
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 
> 

Puneet,
Did you get anything on this? 
Even i am also facing same error with smbus controller 2. 

ismt-bus completion wait timed out issue

[Puneet Shenoy]

Hey Bill,

I see that you are the author of the i2c-ismt driver so thought will check with you on a issue that I have been seeing on my setup.

My setup has an Intel Atom S1220 Processor which has a PMBUS device on its SMBUS 2.0 controller (SMBus—Bus 0:D19:F0-1). 

Now while accessing(read/write) the PMBUS device, I see the following error messages:
[10799.333083] ismt_smbus 0000:00:13.1: completion wait timed out
[10800.337089] ismt_smbus 0000:00:13.1: completion wait timed out
[10801.341097] ismt_smbus 0000:00:13.1: completion wait timed out
[10802.345105] ismt_smbus 0000:00:13.1: completion wait timed out

All read/write access to the device fail when its in this state. The issue is hard to reproduce and happens once in a while.

I tried rmmod/modprobe the driver, but that doesn't help. I dumped the relevant registers that are dev_dbg'ed in the driver and compared the data between the failed and working cases and I don't see any difference. 
Once in a while when I am in the failed state, I see the In Progress Bit (Bit 0) in the MSTS (Master Status Register) being set but its not always the case.

Have you seen this issue before ? Any pointers on how to debug this ?

Appreciate any help.
Thanks
Puneet--
To unsubscribe from this list: send the line "unsubscribe linux-i2c" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html