From: Andrey Borzenkov <arvidjaar@newmail.ru>
To: Rudolf Marek <r.marek@sh.cvut.cz>
Cc: Jean Delvare <khali@linux-fr.org>,
linux-kernel@vger.kernel.org, lm-sensors@lm-sensors.org
Subject: Re: [lm-sensors] 2.6.15: lm90 0-004c: Register 0x13 read failed (-1)
Date: Sun, 15 Jan 2006 23:58:34 +0300 [thread overview]
Message-ID: <200601152358.38095.arvidjaar@newmail.ru> (raw)
In-Reply-To: <43CAB1B7.6020903@sh.cvut.cz>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Sunday 15 January 2006 23:33, Rudolf Marek wrote:
>
> Well it seems this ali 15x3 has maybe same hardware bug? It was mentioned
> already here: http://www2.lm-sensors.nu/~lm78/readticket.cgi?ticket=2030
>
> > In the log below you can see that the ALI15X3 chip seems to keep in
> > idle-state without reporting "done", but it does not turn in "busy"
> > state. I patched the driver to do the reset procedure (with
> > ALI15X3_T_OUT) after the error, but afterwards, the chip turns to "busy"
> > state until next reboot.
>
This is already done in i2c-ali1535 in current kernel. So it looks like HW
issue that can be ignored at best. After reset SMBus continues to work. The
only question is, should we provide an option to shut up those errors;
assuming user knows (s)he has buggy controller there is no reason to spam
dmesg with known issue. Will patch be accepted? I will emit first occurence
of this error to let users know something is fishy and supress further ones.
But this has to wait for next week, it is already too late here.
Thank you for information
- -andrey
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)
iD8DBQFDyrd9R6LMutpd94wRAuNVAKCwq+yTwvFt6jYLS1wL5pIDr68IMwCbBHb+
yXAnHp+jzVFW1ddKVbZVkY8=
=ABky
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2006-01-15 20:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-14 19:23 2.6.15: lm90 0-004c: Register 0x13 read failed (-1) Andrey Borzenkov
2006-01-14 21:20 ` [lm-sensors] " Jean Delvare
2006-01-14 21:45 ` Andrey Borzenkov
2006-01-15 19:12 ` Andrey Borzenkov
2006-01-15 19:48 ` Andrey Borzenkov
2006-01-15 20:33 ` Rudolf Marek
2006-01-15 20:58 ` Andrey Borzenkov [this message]
2006-01-16 19:40 ` Andrey Borzenkov
2006-01-16 21:17 ` Rudolf Marek
2006-01-21 21:02 ` Andrey Borzenkov
2006-01-27 4:15 ` Andrey Borzenkov
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=200601152358.38095.arvidjaar@newmail.ru \
--to=arvidjaar@newmail.ru \
--cc=khali@linux-fr.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lm-sensors@lm-sensors.org \
--cc=r.marek@sh.cvut.cz \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).