[lm-sensors] dme1737 0-002e: Write to register 0x30 failed!
khali at linux-fr.org
Tue Oct 23 14:08:49 CEST 2007
On Mon, 22 Oct 2007 09:02:37 -0700, Juerg Haefliger wrote:
> From the ACPI spec:
> Indicates that the transaction failed because the SMBus host
> reports that the SMBus is presently busy with some other
> transaction. For example, the Smart Battery might be
> sending charging information to the Smart Battery Charger.
Hmm, OK, that's really "bus busy" then. It may be related to this chip
at address 0x0d. Can't say more without detailed hardware
specifications of the system.
> > Depends on what kernel Juergen is running. Oleg Ryjkov has submitted
> > interesting patches that clean up this part of the i2c-nforce2 driver:
> > http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=4153549734cbdba24e9cf5eb200b70b7b1572e15
> > http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=d49584c4a37c7228e7778bcb60f79e7a08472fa8
> > These are already in Linus' tree for 2.6.24.
> Hmm... These patches add abort functionality in case the controller is
> locked. I don't think this is our problem here. In Juergen's case, any
> subsequent transaction after one that fails succeeds so it's a
> transient problem and not a hard lock.
The second patch if completely unrelated, agreed. But the first patch
changes how the driver polls for transaction status. While it is not
related to Juergen's problem, the timing change involved could affect
the code you want to add to retry the transaction when the bus is busy.
More information about the lm-sensors