[lm-sensors] dme1737 error messages

Juerg Haefliger juergh at gmail.com
Tue Oct 9 20:21:03 CEST 2007


Hi Bobby,

On 10/9/07, Borislav Davitkov <davitkov at gmail.com> wrote:
> Unfortunately, the last bios update hp cared to offer is more than an year
> old. And as you might expect the bios is made to be foolproof to the point
> where you can't do really anything useful with it. I will never buy another
> preassembled branded pc ever. (It looked like a deal at the time :( )

Looks like you run into the same issue as
http://bugzilla.kernel.org/show_bug.cgi?id=6649.
I'm not an ACPI expert, by no means. I would take this to the
linux-acpi mailing list.
However, it looks to me like your DSDT has references to _TZ_.THRM
which is also declared external. So something else needs to be loaded
(?) that provides this method. Is it SSDT? I don't know, I don't even
know what SSDT is. I can only suggest to follow what one person
suggested in the bugzilla bug report: Try loading the cpufreq driver
and check if the error goes away.

As for the dme1737 errors. Can you send the output of 'dmesg -s64000'?

...juerg


>
> On 10/7/07, Borislav Davitkov <davitkov at gmail.com> wrote:
> > Sorry for the belated reply.
> >
> > Lots of network trouble lately. It has been almost a full week without
> internet here. I am seriously considering changing my ISP.
> > Now to the point. I'm sending you the i2cdump you wanted along with the
> system log. It's of a fresh boot just after the bootup messages. If you need
> something more verbose, you could tell me what options I should pass to the
> module.
> >
> > Btw, could you tell me what are the acpi error messages about. I have
> tried to look them up in vain. I get them quite often.
> >
> > About the dme errors, I noticed that they are more likely to happen when
> the system is under heavy load. My primary interest in the hwmon
> capabilities of my
> > motherboard arose because I have a P4 3.4GHz Prescott, which generates a
> lot of heat. It came with a very loud stock cooler and soon afterwards I
> replaced with a Scythe Ninja+. With the help of the new module I was finally
> able to put my new cooler to the test. During these tests I run two
> instances of cpuburn which bring the cpu load up to 100% and make the dme
> error messages appear more often. I use kima or ksensors to display the
> various temperatures. Under such a situation (cpu overload), the reported
> temperatures by kima would be -63 degC (maybe this is kima's way of dealing
> with its receiving no values) while ksensors just flashes signaling error.
> This happens just for a little while until (I guess) a new readout of the
> sensors is carried out. Then normal values are restored. These moments
> coincide with the timestamps of the dme error messages in the logs.
> >
> >
> > Hope I'm being helpful,
> > Bobby
> >
> >
> >
> > On 10/2/07, Juerg Haefliger < juergh at gmail.com> wrote:
> >
> > > Oh and could you please post the full content of the system log
> > > (relevant section only). Grepping for dme doesn't provide all the
> > > information.
> > >
> > > Thanks
> > > ...juerg
> > >
> > >
> > > On 9/27/07, Borislav Davitkov <davitkov at gmail.com> wrote:
> > > > Hi,
> > > >
> > > > Thanks for adding support for this chip.
> > > > I have a PTGD1-LA (Puffer) mobo.
> > > >
> http://h10025.www1.hp.com/ewfrf/wc/genericDocument?cc=us&docname=c00208497&lc=en#
> > > > It is made by ASUS for HP, so it has the A8000 chip.
> > > >
> > > > After updating my kernel to 2.6.23-rc7 and lm-sensors to 2.10.4 I
> managed to
> > > > get  it working. However, dmesg  shows these messages:
> > > >
> > > > dmesg| grep dme
> > > > dme1737 0-002e: Optional features: pwm3=yes, pwm5=no, pwm6=no,
> fan3=no,
> > > > fan4=yes, fan5=no, fan6=no.
> > > > dme1737 0-002e: Optional features: pwm3=yes, pwm5=no, pwm6=no,
> fan3=no,
> > > > fan4=yes, fan5=no, fan6=no.
> > > > dme1737 0-002e: Optional features: pwm3=yes, pwm5=no, pwm6=no,
> fan3=no,
> > > > fan4=yes, fan5=no, fan6=no.
> > > > dme1737 0-002e: Read from register 0x46 failed! Please report to the
> driver
> > > > maintainer.
> > > > dme1737 0-002e: Read from register 0x47 failed! Please report to the
> driver
> > > > maintainer.
> > > > dme1737 0-002e: Read from register 0x22 failed! Please report to the
> driver
> > > > maintainer.
> > > > dme1737 0-002e: Read from register 0x48 failed! Please report to the
> driver
> > > > maintainer.
> > > > dme1737 0-002e: Read from register 0x49 failed! Please report to the
> driver
> > > > maintainer.
> > > > dme1737 0-002e: Read from register 0x23 failed! Please report to the
> driver
> > > > maintainer.
> > > > dme1737 0-002e: Read from register 0x4a failed! Please report to the
> driver
> > > > maintainer.
> > > > dme1737 0-002e: Read from register 0x4b failed! Please report to the
> driver
> > > > maintainer.
> > > > dme1737 0-002e: Read from register 0x24 failed! Please report to the
> driver
> > > > maintainer.
> > > > dme1737 0-002e: Read from register 0x4c failed! Please report to the
> driver
> > > > maintainer.
> > > > dme1737 0-002e: Read from register 0x4d failed! Please report to the
> driver
> > > > maintainer.
> > > > dme1737 0-002e: Read from register 0x99 failed! Please report to the
> driver
> > > > maintainer.
> > > > dme1737 0-002e: Read from register 0x9b failed! Please report to the
> driver
> > > > maintainer.
> > > > dme1737 0-002e: Read from register 0x9c failed! Please report to the
> driver
> > > > maintainer.
> > > > dme1737 0-002e: Read from register 0x9a failed! Please report to the
> driver
> > > > maintainer.
> > > > dme1737 0-002e: Read from register 0x9d failed! Please report to the
> driver
> > > > maintainer.
> > > > dme1737 0-002e: Read from register 0x9e failed! Please report to the
> driver
> > > > maintainer.
> > > > dme1737 0-002e: Read from register 0x25 failed! Please report to the
> driver
> > > > maintainer.
> > > > dme1737 0-002e: Read from register 0x4e failed! Please report to the
> driver
> > > > maintainer.
> > > > dme1737 0-002e: Read from register 0x4f failed! Please report to the
> driver
> > > > maintainer.
> > > > dme1737 0-002e: Read from register 0x1f failed! Please report to the
> driver
> > > > maintainer.
> > > > dme1737 0-002e: Read from register 0x26 failed! Please report to the
> driver
> > > > maintainer.
> > > > dme1737 0-002e: Read from register 0x50 failed! Please report to the
> driver
> > > > maintainer.
> > > > dme1737 0-002e: Read from register 0x51 failed! Please report to the
> driver
> > > > maintainer.
> > > > dme1737 0-002e: Read from register 0x1d failed! Please report to the
> driver
> > > > maintainer.
> > > > dme1737 0-002e: Read from register 0x27 failed! Please report to the
> driver
> > > > maintainer.
> > > > dme1737 0-002e: Read from register 0x52 failed! Please report to the
> driver
> > > > maintainer.
> > > > dme1737 0-002e: Read from register 0x53 failed! Please report to the
> driver
> > > > maintainer.
> > > > dme1737 0-002e: Read from register 0x1e failed! Please report to the
> driver
> > > > maintainer.
> > > > dme1737 0-002e: Read from register 0x84 failed! Please report to the
> driver
> > > > maintainer.
> > > > dme1737 0-002e: Read from register 0x85 failed! Please report to the
> driver
> > > > maintainer.
> > > > dme1737 0-002e: Read from register 0x86 failed! Please report to the
> driver
> > > > maintainer.
> > > > dme1737 0-002e: Read from register 0x87 failed! Please report to the
> driver
> > > > maintainer.
> > > > dme1737 0-002e: Read from register 0x88 failed! Please report to the
> driver
> > > > maintainer.
> > > > dme1737 0-002e: Read from register 0x28 failed! Please report to the
> driver
> > > > maintainer.
> > > > dme1737 0-002e: Read from register 0x29 failed! Please report to the
> driver
> > > > maintainer.
> > > > dme1737 0-002e: Read from register 0x54 failed! Please report to the
> driver
> > > > maintainer.
> > > > dme1737 0-002e: Read from register 0x55 failed! Please report to the
> driver
> > > > maintainer.
> > > > dme1737 0-002e: Read from register 0x90 failed! Please report to the
> driver
> > > > maintainer.
> > > > dme1737 0-002e: Read from register 0x2a failed! Please report to the
> driver
> > > > maintainer.
> > > > dme1737 0-002e: Read from register 0x2b failed! Please report to the
> driver
> > > > maintainer.
> > > > dme1737 0-002e: Read from register 0x56 failed! Please report to the
> driver
> > > > maintainer.
> > > > dme1737 0-002e: Read from register 0x57 failed! Please report to the
> driver
> > > > maintainer.
> > > > dme1737 0-002e: Read from register 0x91 failed! Please report to the
> driver
> > > > maintainer.
> > > > dme1737 0-002e: Read from register 0x2e failed! Please report to the
> driver
> > > > maintainer.
> > > > dme1737 0-002e: Read from register 0x2f failed! Please report to the
> driver
> > > > maintainer.
> > > > dme1737 0-002e: Read from register 0x5a failed! Please report to the
> driver
> > > > maintainer.
> > > > dme1737 0-002e: Read from register 0x5b failed! Please report to the
> driver
> > > > maintainer.
> > > > dme1737 0-002e: Read from register 0x93 failed! Please report to the
> driver
> > > > maintainer.
> > > > dme1737 0-002e: Read from register 0x30 failed! Please report to the
> driver
> > > > maintainer.
> > > > dme1737 0-002e: Read from register 0x5f failed! Please report to the
> driver
> > > > maintainer.
> > > > dme1737 0-002e: Read from register 0x5c failed! Please report to the
> driver
> > > > maintainer.
> > > > dme1737 0-002e: Read from register 0x64 failed! Please report to the
> driver
> > > > maintainer.
> > > > dme1737 0-002e: Read from register 0x31 failed! Please report to the
> driver
> > > > maintainer.
> > > > dme1737 0-002e: Read from register 0x60 failed! Please report to the
> driver
> > > > maintainer.
> > > > dme1737 0-002e: Read from register 0x5d failed! Please report to the
> driver
> > > > maintainer.
> > > > dme1737 0-002e: Read from register 0x65 failed! Please report to the
> driver
> > > > maintainer.
> > > > dme1737 0-002e: Read from register 0x32 failed! Please report to the
> driver
> > > > maintainer.
> > > > dme1737 0-002e: Read from register 0x61 failed! Please report to the
> driver
> > > > maintainer.
> > > > dme1737 0-002e: Read from register 0x5e failed! Please report to the
> driver
> > > > maintainer.
> > > > dme1737 0-002e: Read from register 0x66 failed! Please report to the
> driver
> > > > maintainer.
> > > > dme1737 0-002e: Read from register 0x62 failed! Please report to the
> driver
> > > > maintainer.
> > > > dme1737 0-002e: Read from register 0x63 failed! Please report to the
> driver
> > > > maintainer.
> > > > dme1737 0-002e: Read from register 0x67 failed! Please report to the
> driver
> > > > maintainer.
> > > > dme1737 0-002e: Read from register 0x6a failed! Please report to the
> driver
> > > > maintainer.
> > > > dme1737 0-002e: Read from register 0x68 failed! Please report to the
> driver
> > > > maintainer.
> > > > dme1737 0-002e: Read from register 0x6b failed! Please report to the
> driver
> > > > maintainer.
> > > > dme1737 0-002e: Read from register 0x69 failed! Please report to the
> driver
> > > > maintainer.
> > > > dme1737 0-002e: Read from register 0x6c failed! Please report to the
> driver
> > > > maintainer.
> > > > dme1737 0-002e: Read from register 0x6d failed! Please report to the
> driver
> > > > maintainer.
> > > > dme1737 0-002e: Read from register 0x6e failed! Please report to the
> driver
> > > > maintainer.
> > > > dme1737 0-002e: Read from register 0x41 failed! Please report to the
> driver
> > > > maintainer.
> > > > dme1737 0-002e: Read from register 0x42 failed! Please report to the
> driver
> > > > maintainer.
> > > > dme1737 0-002e: Read from register 0x83 failed! Please report to the
> driver
> > > > maintainer.
> > > >
> > > > So I am reporting to the driver maintainer. :)
> > > > I will be more that happy if I could help in some way.
> > > >
> > > > Regards,
> > > > Borislav
> > > >
> > >
> >
> >
> >
>
>
>




More information about the lm-sensors mailing list