dme1737 0-002e: Write to register 0x30 failed!

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Juer, Jean,


> -----Urspr?ngliche Nachricht-----
> Von: "Juerg Haefliger" <juergh at gmail.com>
> Gesendet: 18.10.07 06:53:47
> An: "Jean Delvare" <khali at linux-fr.org>
> CC: lm-sensors at lm-sensors.org
> Betreff: Re:  dme1737 0-002e: Write to register 0x30 failed!


> 
> > >                                                                  That
> > > should definitely get retried. I can certainly do that at the dme1737
> > > level but I don't think that's the right place. Jean?
> >
> > Assuming that "busy" means that the nForce chip did not even attempt to
> > send the message (or lost arbitration, which is equivalent), this
> > specific error could be handled in i2c-nforce2, by retrying. The
> > problem is that you have to decide how many times you retry, and how
> > much time you wait between retries (there doesn't seem to be a way to
> > test if the SMBus is busy before trying, right?)
> 
> The i2c-nforce2 driver already spins for 10 msecs before deciding to
> give up. I'd just retry once after that and see what happens.
> 
> Juergen: Can you apply the attached patch and give it a whirl?
> 


Since i applied the patch I got no more errors.

Juergen
______________________________________________________________________
XXL-Speicher, PC-Virenschutz, Spartarife & mehr: Nur im WEB.DE Club!		
Jetzt testen! http://produkte.web.de/club/?mc=021130





[Index of Archives]     [Linux Kernel]     [Linux Hardware Monitoring]     [Linux USB Devel]     [Linux Audio Users]     [Linux Kernel]     [Linux SCSI]     [Yosemite Backpacking]

  Powered by Linux