From: Juergen Bausa <Juergen.Bausa@web.de>
To: lm-sensors@vger.kernel.org
Subject: Re: [lm-sensors] dme1737 0-002e: Write to register 0x30 failed!
Date: Tue, 23 Oct 2007 20:44:17 +0000 [thread overview]
Message-ID: <1719565594@web.de> (raw)
In-Reply-To: <1642847378@web.de>
Juer, Jean,
> -----Ursprüngliche Nachricht-----
> Von: "Juerg Haefliger" <juergh@gmail.com>
> Gesendet: 18.10.07 06:53:47
> An: "Jean Delvare" <khali@linux-fr.org>
> CC: lm-sensors@lm-sensors.org
> Betreff: Re: [lm-sensors] 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\x021130
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
next prev parent reply other threads:[~2007-10-23 20:44 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-25 19:08 [lm-sensors] dme1737 0-002e: Write to register 0x30 failed! Juergen Bausa
2007-10-01 17:44 ` Juerg Haefliger
2007-10-01 19:22 ` Juergen Bausa
2007-10-01 21:39 ` Juerg Haefliger
2007-10-01 21:50 ` Jean Delvare
2007-10-08 18:31 ` Juergen Bausa
2007-10-09 7:03 ` Jean Delvare
2007-10-09 16:08 ` Juerg Haefliger
2007-10-09 19:41 ` Juergen Bausa
2007-10-10 17:12 ` Juerg Haefliger
2007-10-11 7:45 ` Jean Delvare
2007-10-17 18:56 ` Juergen Bausa
2007-10-17 19:43 ` Juerg Haefliger
2007-10-17 21:32 ` Jean Delvare
2007-10-18 4:53 ` Juerg Haefliger
2007-10-19 15:07 ` Jean Delvare
2007-10-20 19:28 ` Juergen Bausa
2007-10-20 19:39 ` Juergen Bausa
2007-10-21 18:40 ` Mark M. Hoffman
2007-10-21 19:14 ` Jean Delvare
2007-10-21 19:37 ` Jean Delvare
2007-10-22 16:02 ` Juerg Haefliger
2007-10-22 16:05 ` Juerg Haefliger
2007-10-23 12:08 ` Jean Delvare
2007-10-23 12:22 ` Jean Delvare
2007-10-23 20:44 ` Juergen Bausa [this message]
2007-10-23 21:54 ` Rudolf Marek
2007-10-24 8:48 ` Jean Delvare
2007-10-29 21:23 ` Rudolf Marek
2007-10-30 2:52 ` Juerg Haefliger
2007-10-31 2:40 ` Juerg Haefliger
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1719565594@web.de \
--to=juergen.bausa@web.de \
--cc=lm-sensors@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.