From: Guenter Roeck <linux@roeck-us.net>
To: lm-sensors@vger.kernel.org
Subject: Re: [lm-sensors] Kernel errors for dme1737
Date: Tue, 11 Feb 2014 19:24:36 +0000 [thread overview]
Message-ID: <20140211192436.GA16188@roeck-us.net> (raw)
In-Reply-To: <CADLDEKtzZeoOyyUGe7Rug8n-c0oZ_n8Cqd=HFpPZdZWgYmJARg@mail.gmail.com>
On Tue, Feb 11, 2014 at 10:54:55AM +0100, Jürgen Fuchsberger wrote:
> Hi,
>
> On 02/11/2014 08:32 AM, Juerg Haefliger wrote:
> > Hi Juergen,
> >
> > You're likely to get better help by contacting the LM sensors mailing
> > list (cc'ed). I've been out of it for a bit.
>
> Thanks!
> >
> >
> >> Dear Juerg,
> >>
> >> I keep getting Errors of this kind:
> >>
> >> Feb 10 09:51:09 wegc203094 kernel: [ 156.372033] dme1737 1-002c: Read
> >> from register 0x6d failed! Please report to the driver maintainer.
> >> Feb 10 09:53:09 wegc203094 kernel: [ 276.472043] dme1737 1-002c: Read
> >> from register 0x69 failed! Please report to the driver maintainer.
> >
> > Can you post all messages from the driver from the time it was loaded?
>
> Feb 10 09:48:47 wegc203094 kernel: [ 8.368070] i2c i2c-1: Found a
> DME1737 chip at 0x2c (rev 0x8a).
> Feb 10 09:48:47 wegc203094 kernel: [ 8.384103] dme1737 1-002c:
> Optional features: pwm3=no, pwm5=no, pwm6=no, fan3=no, fan4=no, fan5=no,
> fan6=no.
> Feb 10 09:4
>
>
> > What's the model of the machine you're using?
> Hmm, unfortunately I don't know. Is there a way to find out without
> opening the server? (I mean by sw-tools?)
>
If this is a PC, "sudo dmidecode" might tell you a lot.
> > What do you get when running the sensors-detect script?
>
> ~ % sensors
>
>
sensors-detect, not sensors ;-).
Anyway, can you provide the output of "sudo i2cdump -y -f 1 0x2c" ?
That might actually help more.
Also, are the errors persistent or sporadic ?
Thanks,
Guenter
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
next prev parent reply other threads:[~2014-02-11 19:24 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-11 7:32 [lm-sensors] Kernel errors for dme1737 Juerg Haefliger
2014-02-11 9:54 ` Jürgen Fuchsberger
2014-02-11 19:24 ` Guenter Roeck [this message]
2014-02-12 8:52 ` Jürgen Fuchsberger
2014-02-12 9:37 ` Juerg Haefliger
2014-02-12 10:10 ` Jürgen Fuchsberger
2014-02-12 10:33 ` Juerg Haefliger
2014-02-12 11:07 ` Jürgen Fuchsberger
2014-02-12 11:54 ` Guenter Roeck
2014-02-12 12:05 ` Jean Delvare
2014-02-12 14:24 ` Guenter Roeck
2014-02-13 6:39 ` Jürgen Fuchsberger
2014-02-13 7:26 ` Guenter Roeck
2014-02-13 7:32 ` Jean Delvare
2014-02-17 14:33 ` Jürgen Fuchsberger
2014-02-17 14:42 ` Juerg Haefliger
2014-02-17 14:49 ` Jürgen Fuchsberger
2014-02-17 15:55 ` Jean Delvare
2014-02-18 7:25 ` Juerg Haefliger
2014-02-18 7:36 ` Jürgen Fuchsberger
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=20140211192436.GA16188@roeck-us.net \
--to=linux@roeck-us.net \
--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.