All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lou Gosselin <tech2009@evergrove.com>
To: lm-sensors@vger.kernel.org
Subject: Re: [lm-sensors] "No sensors found!" on Intel Entry Storage System
Date: Sat, 30 Jan 2010 20:27:21 +0000	[thread overview]
Message-ID: <4B649629.7080008@evergrove.com> (raw)
In-Reply-To: <1251523453.13079.32.camel@Ubuntu>

[-- Attachment #1: Type: text/plain, Size: 1092 bytes --]

The email didn't specify the range to dump, but thanks for the advice.
I'm attaching the output for 0x2e.
Let me know if you'd like anything else.


Jean Delvare wrote:
> Hi Lou,
>
> On Fri, 29 Jan 2010 19:17:06 -0500, Lou Gosselin wrote:
>   
>> I've attached two files.
>> sensors.txt shows the output that I get with sensors-detect and sensors.
>>
>> i2cbus.txt shows output for i2cdetect and i2cdump.
>> Let me point out that after running "i2cdump 0 0x6a", lmsensors was no 
>> longer responsive. Furthermore the machine failed to reboot until I did 
>> a cold boot.
>>     
>
> Let me point out that dumping random i2c chips is a very bad idea.
> Especially chips in the 0x86-0x6a range, are often clock chips which
> don't like being dumped at all...
>
>   
>> (...)
>> I'll give any suggestions a shot, or if you're willing, I can setup one 
>> of these machines for you to connect to.
>>     
>
> The chip I would like to see a dump of is the one at 0x2e. This will
> give us the chip ID of your SMSC chip. It's probably only a matter of
> adding the right ID to the driver.
>
>   


[-- Attachment #2: lmsensor.txt --]
[-- Type: text/plain, Size: 1443 bytes --]

intel-ss4200:~# i2cdump 0 0x2e
No size specified (using byte-data access)
WARNING! This program can confuse your I2C bus, cause data loss and worse!
I will probe file /dev/i2c-0, address 0x2e, mode byte
Continue? [Y/n]
     0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f    0123456789abcdef
00: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
10: 00 00 00 00 00 00 00 00 00 00 00 00 02 48 00 0f    ............?H.?
20: c0 57 c0 c3 bf fd 15 1a ff ff 40 11 b4 10 ff ff    ?W??????..@???..
30: 6b 6b 6b 30 0b 00 0f 00 40 00 48 f7 0f 00 5c 69    kkk0?.?.@.H??.\i
40: 05 00 00 18 00 ff 00 ff 00 ff 00 ff 00 ff 81 44    ?..?..........?D
50: 81 7f 81 4b ff ff ff ff ff ff ff ff 02 c2 c2 7b    ???K........???{
60: 7b 7b e8 88 6b 6b 6b 33 32 64 40 41 73 22 20 00    {{??kkk32d@As" .
70: 6b 6b 6b 00 00 00 00 00 00 00 30 00 00 00 ec 1c    kkk.......0...??
80: 7e a4 0f 00 00 6c 4c 2e cc 00 33 33 24 24 19 19    ~??..lL.?.33$$??
90: 04 04 04 04 0c 0c 0c 5a f1 c0 b5 00 ff 00 ff 00    ???????Z???.....
a0: 00 00 0c 00 00 ff ff 07 0b fe ff fe ff ff ff ff    ..?....???.?....
b0: ff 00 00 00 00 00 28 28 0e 0e 0f 0f 00 00 00 00    ......((????....
c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................
f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00    ................

[-- Attachment #3: Type: text/plain, Size: 153 bytes --]

_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

  parent reply	other threads:[~2010-01-30 20:27 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-29  5:24 [lm-sensors] "No sensors found!" on Intel Entry Storage System Tech2009
2009-08-29  8:30 ` Hubert Kario
2009-08-29 16:03 ` Tech2009
2009-09-01 18:26 ` Hubert Kario
2009-09-01 21:27 ` Tech2009
2009-09-02  0:23 ` Hubert Kario
2009-09-02  2:10 ` Juerg Haefliger
2009-09-02 19:29 ` Jean Delvare
2009-09-02 20:02 ` Juerg Haefliger
2010-01-29 13:46 ` Jean Delvare
2010-01-30  0:17 ` Lou Gosselin
2010-01-30  9:33 ` Jean Delvare
2010-01-30 20:27 ` Lou Gosselin [this message]
2010-01-31 13:05 ` Jean Delvare
2010-01-31 13:26 ` 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=4B649629.7080008@evergrove.com \
    --to=tech2009@evergrove.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.