From: morris@wolfman.com (Jim Morris)
To: lm-sensors@vger.kernel.org
Subject: lm_sensors2/prog/detect sensors-detect
Date: Thu, 19 May 2005 06:24:02 +0000 [thread overview]
Message-ID: <200306271346.19491.morris@wolfman.com> (raw)
In-Reply-To: <20021107235845.0037e195.khali@linux-fr.org>
On Friday 27 June 2003 12:40 am, you wrote:
>
> I guess there were similar errors (Malformed UTF-8 character) for some
> other chipsets?
>
yes for instance...
Probing for `IPMI BMC KCS'
Trying address 0x0ca0...
Called inb with port235
After sysseek
After sysread, nrchars=1
Malformed UTF-8 character (unexpected non-continuation byte 0xff, immediately
after start byte 0xff) in ord at sensors-detect2.pl line 1358.
Read value with ord=0
Returning res%5
Failed!
> Anyway, I'm stumped. I was expecting your system to return UTF-8 chars
> from /dev/ports, and it doesn't seem so (or why would perl say they are
> malformed?) And if it returns regular chars, why are the values
> different from the ones obtained with a non-UTF-8 locale? I just don't
> understand.
This could be a bug in Perl and their partial UTF8 hack
>
> So from here I only see two possibilities:
>
> 1* Opening /dev/ports in binary mode solves the problem (which I doubt,
> since traditionally, Unix systems don't differenciate text and binary
> modes). Please grab the modified script that does this and tell me if it
> works:
> http://www.ensicaen.ismra.fr/~delvare/sensors-detect-k3
With UTF8......
Probing for `ITE IT8705F / IT8712F / SiS 950'
Trying address 0x0290...
Called inb with porte7
After sysseek
After sysread, nrchars=1
Malformed UTF-8 character (unexpected continuation byte 0x90, with no
preceding start byte) in ord at sensors-detect-k3 line 1358.
Read value with ord=0
Returning res\x144
Called inb with porte8
After sysseek
After sysread, nrchars=1
Malformed UTF-8 character (unexpected continuation byte 0x90, with no
preceding start byte) in ord at sensors-detect-k3 line 1358.
Read value with ord=0
Returning res\x144
Called inb with porte9
After sysseek
After sysread, nrchars=1
Malformed UTF-8 character (unexpected continuation byte 0x90, with no
preceding start byte) in ord at sensors-detect-k3 line 1358.
Read value with ord=0
Returning res\x144
Called inb with portf3
After sysseek
After sysread, nrchars=1
Malformed UTF-8 character (unexpected continuation byte 0x90, with no
preceding start byte) in ord at sensors-detect-k3 line 1358.
Read value with ord=0
Returning res\x144
Called inb with portf1
After sysseek
After sysread, nrchars=1
Read value with ord\x1552
Returning res!6
Called inb with portf1
After sysseek
After sysread, nrchars=1
Read value with ordf
Returning resf
Failed!
Probing for `IPMI BMC KCS'
Trying address 0x0ca0...
Called inb with port235
After sysseek
After sysread, nrchars=1
Malformed UTF-8 character (unexpected non-continuation byte 0xff, immediately
after start byte 0xff) in ord at sensors-detect-k3 line 1358.
Read value with ord=0
Returning res%5
Failed!
================================
Without UTF8
Probing for `ITE IT8705F / IT8712F / SiS 950'
Trying address 0x0290...
Called inb with porte7
After sysseek
After sysread, nrchars=1
Read value with ord%5
Returning res%5
Called inb with porte8
After sysseek
After sysread, nrchars=1
Read value with ord%5
Returning res%5
Called inb with porte9
After sysseek
After sysread, nrchars=1
Read value with ord%5
Returning res%5
Called inb with portf3
After sysseek
After sysread, nrchars=1
Read value with ord%5
Returning res%5
Called inb with portf1
After sysseek
After sysread, nrchars=1
Read value with ordy
Returning resy
Called inb with portf1
After sysseek
After sysread, nrchars=1
Read value with ord\x176
Returning res\x176
Called inb with portf2
After sysseek
After sysread, nrchars=1
Read value with ord\x17
Returning res\x17
Called inb with portf2
After sysseek
After sysread, nrchars=1
Read value with ord\x144
Returning res\x144
Success!
(confidence 8, driver `it87')
Probing for `IPMI BMC KCS'
Trying address 0x0ca0...
Called inb with port235
After sysseek
After sysread, nrchars=1
Read value with ord%5
Returning res%5
Failed!
--
Jim Morris
next prev parent reply other threads:[~2005-05-19 6:24 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-19 6:23 lm_sensors2/prog/detect sensors-detect Jean Delvare
2005-05-19 6:23 ` Jean Delvare
2005-05-19 6:23 ` Jean Delvare
2005-05-19 6:23 ` Jim Morris
2005-05-19 6:23 ` Jean Delvare
2005-05-19 6:23 ` Jim Morris
2005-05-19 6:23 ` Jean Delvare
2005-05-19 6:23 ` Jean Delvare
2005-05-19 6:23 ` Jean Delvare
2005-05-19 6:24 ` Jim Morris
2005-05-19 6:24 ` Jim Morris
2005-05-19 6:24 ` Jean Delvare
2005-05-19 6:24 ` Jim Morris
2005-05-19 6:24 ` Mark D. Studebaker
2005-05-19 6:24 ` Jim Morris
2005-05-19 6:24 ` Jean Delvare
2005-05-19 6:24 ` Jim Morris
2005-05-19 6:24 ` Jean Delvare
2005-05-19 6:24 ` Jean Delvare
2005-05-19 6:24 ` Jean Delvare
2005-05-19 6:24 ` Jim Morris [this message]
2005-05-19 6:24 ` Jean Delvare
2005-05-19 6:24 ` Jean Delvare
2005-05-19 6:24 ` Mark Studebaker
2005-05-19 6:24 ` Jean Delvare
2005-05-19 6:24 ` Jean Delvare
2005-05-19 6:24 ` Jean Delvare
2005-05-19 6:24 ` Mark Studebaker
2005-05-19 6:24 ` Jean Delvare
2005-05-19 6:24 ` Jean Delvare
2005-05-19 6:24 ` Mark Studebaker
2005-05-19 6:24 ` Jean Delvare
2005-05-19 6:24 ` Mark Studebaker
2005-05-19 6:24 ` Mark Studebaker
2005-05-19 6:24 ` Jean Delvare
2005-05-19 6:24 ` Mark Studebaker
2005-05-19 6:24 ` Mark Studebaker
2005-05-19 6:24 ` Mark Studebaker
2005-05-19 6:24 ` Jean Delvare
2005-05-19 6:24 ` Mark M. Hoffman
2005-05-19 6:24 ` Jean Delvare
2005-05-19 6:24 ` Mark M. Hoffman
2005-05-19 6:24 ` Mark Studebaker
2005-05-19 6:24 ` Jean Delvare
2005-05-19 6:24 ` Mark Studebaker
2005-05-19 6:24 ` Jean Delvare
2005-05-19 6:24 ` Jean Delvare
2005-05-19 6:24 ` Mark Studebaker
2005-05-19 6:24 ` Mark Studebaker
2005-05-19 6:24 ` Mark Studebaker
2005-05-19 6:24 ` Jean Delvare
2005-05-19 6:24 ` Jean Delvare
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=200306271346.19491.morris@wolfman.com \
--to=morris@wolfman.com \
--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.