* Re: [lm-sensors] dme1737 error messages
2007-10-01 18:51 [lm-sensors] dme1737 error messages Juerg Haefliger
@ 2007-10-01 21:46 ` Juerg Haefliger
2007-10-09 18:21 ` Juerg Haefliger
` (8 subsequent siblings)
9 siblings, 0 replies; 11+ messages in thread
From: Juerg Haefliger @ 2007-10-01 21:46 UTC (permalink / raw)
To: lm-sensors
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@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À0208497&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
>
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
^ permalink raw reply [flat|nested] 11+ messages in thread* Re: [lm-sensors] dme1737 error messages
2007-10-01 18:51 [lm-sensors] dme1737 error messages Juerg Haefliger
2007-10-01 21:46 ` Juerg Haefliger
@ 2007-10-09 18:21 ` Juerg Haefliger
2007-10-10 19:35 ` Juerg Haefliger
` (7 subsequent siblings)
9 siblings, 0 replies; 11+ messages in thread
From: Juerg Haefliger @ 2007-10-09 18:21 UTC (permalink / raw)
To: lm-sensors
Hi Bobby,
On 10/9/07, Borislav Davitkov <davitkov@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?idf49.
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@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@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@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À0208497&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
> > > >
> > >
> >
> >
> >
>
>
>
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
^ permalink raw reply [flat|nested] 11+ messages in thread* Re: [lm-sensors] dme1737 error messages
2007-10-01 18:51 [lm-sensors] dme1737 error messages Juerg Haefliger
2007-10-01 21:46 ` Juerg Haefliger
2007-10-09 18:21 ` Juerg Haefliger
@ 2007-10-10 19:35 ` Juerg Haefliger
2007-10-23 17:41 ` Juerg Haefliger
` (6 subsequent siblings)
9 siblings, 0 replies; 11+ messages in thread
From: Juerg Haefliger @ 2007-10-10 19:35 UTC (permalink / raw)
To: lm-sensors
Hi Borislav,
On 10/9/07, Borislav Davitkov <davitkov@gmail.com> wrote:
> Hi Juerg,
>
> Here is the output of dmesg.
>
> Regarding the acpi errors, I tried to modprobe acpi-cpufreq but I got:
> FATAL: Error inserting acpi_cpufreq
> (/lib/modules/2.6.23-rc7-gda8f153e-5-default/kernel/arch/i386/kernel/cpu/cpufreq/acpi-
> cpufreq.ko): No such device
Try enabling CONFIG_CPU_FREQ_DEBUG and recompile.
> Btw, examining the output of dmesg, you will see that the BIOS is really
> inadequate:
> PCI: BIOS Bug: MCFG area at e0000000 is not E820-reserved
> PCI: Not using MMCONFIG.
>
> PS: The second output is after I have loaded the cpu 100% and the usual
> dme1737 errors have showed up.
Can you also enable CONFIG_I2C_DEBUG_* and recompile the i2c modules?
...juerg
>
> On 10/9/07, Juerg Haefliger <juergh@gmail.com> wrote:
> > Hi Bobby,
> >
> > On 10/9/07, Borislav Davitkov <davitkov@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?idf49.
> > 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@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@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@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À0208497&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
> > > > > >
> > > > >
> > > >
> > > >
> > > >
> > >
> > >
> > >
> >
>
>
>
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
^ permalink raw reply [flat|nested] 11+ messages in thread* Re: [lm-sensors] dme1737 error messages
2007-10-01 18:51 [lm-sensors] dme1737 error messages Juerg Haefliger
` (2 preceding siblings ...)
2007-10-10 19:35 ` Juerg Haefliger
@ 2007-10-23 17:41 ` Juerg Haefliger
2007-10-23 17:52 ` Juerg Haefliger
` (5 subsequent siblings)
9 siblings, 0 replies; 11+ messages in thread
From: Juerg Haefliger @ 2007-10-23 17:41 UTC (permalink / raw)
To: lm-sensors
Hi Bobby,
On 10/20/07, Borislav Davitkov <davitkov@gmail.com> wrote:
> Hi Juerg,
>
> Here is another system log with the relevant debug messages. It gets
> interesting at line 8444, especially 8451, and then 8606...
Ok, it looks like every time you get the ACPI errors, a subsequent
dme1737 access returns a non-zero status (SMBus busy (02)) which in
turn results in a successful reset. So far so good. The 02 means the
following (from the ICH6 spec):
[... This bit can only be set by termination of a command. INTR is not
dependent on the INTREN bit (offset SMBASE + 02h, bit 0) of the Host
controller register (offset 02h). It is only dependent on the
termination of the command. If the INTREN bit is not set, then the
INTR bit will be set, although the interrupt will not be generated.
Software can poll the INTR bit in this non-interrupt case.
0 = Software clears this bit by writing a 1 to it. The ICH6 then
deasserts the interrupt or SMI#.
1 = The source of the interrupt or SMI# was the successful completion
of its last command. ...]
Now the problematic case is where you get a 'SMBus busy (01)' status .
The following reset does not succeed which makes sense, since the i810
driver is trying to clear a read-only bit. From the ICH6 spec, status
01 means:
[... HOST_BUSY — RO.
0 = Cleared by the ICH6 when the current transaction is completed.
1 = Indicates that the ICH6 is running a command from the host
interface. No SMB registers should be accessed while this bit is set,
except the BLOCK DATA BYTE Register. The BLOCK DATA BYTE Register can
be accessed when this bit is set only when the SMB_CMD bits in the
Host Control Register are programmed for Block command or I2C Read
command. This is necessary in order to check the DONE_STS bit. ...]
So in this case the SMBus controller is busy doing somebody else's
work! Every access by the dme1737 results in a unsuccessful reset
until the next ACPI error comes along. From that point on the SMBus
controller is not busy anymore and accepts subsequent dme1737
accesses. Smells like a collision between the dme1737 driver and ACPI.
So the bottom line is you have a broken BIOS causing the ACPI errors
and I believe ACPI and the dme1737 driver collide.
Here are a few suggestions of things you can try:
1) unload the fan and thermal modules and check if the dme1737 and
ACPI errors go away.
2) load the acpi_cpufreq module (don't know if your HW is supported
though) and check if the ACPI errors go away.
3) load the thermal module and do 'grep ""
/proc/acpi/thermal_zone/*/*' and send the output to the list.
4) send me the DSDT table (in private): cat /proc/acpi/dsdt > dsdt.aml
5) test Jean's patch that detects ACPI and hwmon collisions. Jean:
where can he pick it up?
> Do you have any news about a replacement bios for my motherboard?
Nope, couldn't find anything, sorry.
...juerg
> Bobby
>
>
> On 10/10/07, Juerg Haefliger <juergh@gmail.com> wrote:
> > Hi Borislav,
> >
> >
> > On 10/9/07, Borislav Davitkov <davitkov@gmail.com> wrote:
> > > Hi Juerg,
> > >
> > > Here is the output of dmesg.
> > >
> > > Regarding the acpi errors, I tried to modprobe acpi-cpufreq but I got:
> > > FATAL: Error inserting acpi_cpufreq
> > >
> (/lib/modules/2.6.23-rc7-gda8f153e-5-default/kernel/arch/i386/kernel/cpu/cpufreq/acpi-
> > > cpufreq.ko): No such device
> >
> > Try enabling CONFIG_CPU_FREQ_DEBUG and recompile.
> >
> >
> > > Btw, examining the output of dmesg, you will see that the BIOS is really
> > > inadequate:
> > > PCI: BIOS Bug: MCFG area at e0000000 is not E820-reserved
> > > PCI: Not using MMCONFIG.
> > >
> > > PS: The second output is after I have loaded the cpu 100% and the usual
> > > dme1737 errors have showed up.
> >
> > Can you also enable CONFIG_I2C_DEBUG_* and recompile the i2c modules?
> >
> > ...juerg
> >
> >
> > >
> > > On 10/9/07, Juerg Haefliger < juergh@gmail.com> wrote:
> > > > Hi Bobby,
> > > >
> > > > On 10/9/07, Borislav Davitkov <davitkov@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?idf49.
> > > > 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@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@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@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À0208497&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
> > > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > >
> > > > >
> > > > >
> > > >
> > >
> > >
> > >
> >
>
>
>
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
^ permalink raw reply [flat|nested] 11+ messages in thread* Re: [lm-sensors] dme1737 error messages
2007-10-01 18:51 [lm-sensors] dme1737 error messages Juerg Haefliger
` (3 preceding siblings ...)
2007-10-23 17:41 ` Juerg Haefliger
@ 2007-10-23 17:52 ` Juerg Haefliger
2007-10-24 8:46 ` Jean Delvare
` (4 subsequent siblings)
9 siblings, 0 replies; 11+ messages in thread
From: Juerg Haefliger @ 2007-10-23 17:52 UTC (permalink / raw)
To: lm-sensors
Hi Bobby,
On 10/20/07, Borislav Davitkov <davitkov@gmail.com> wrote:
> Just a brief follow-up. I did some further investigation. The errors seem to
> coincide with the acpi errors we discussed. The sequence is: The system is
> under heavy load, cpu starts heating up, i get the acpi error (which is
> somehow connected to TZ (thermal zone ?)), smbus busy, lm-sensors can't get
> a readout, hence the dme error messages.
> I logged the temperatures of my cpu. And compared this log with the system
> log. In a situation like the above the reported temperature is -0.063. This
> happened e.g. at 23:31:39. However at 23:31:46 and 23:41:48, the acpi error
> is reported last. Sometimes the acpi and dme error happen separately. So
> maybe the dme errors are caused by system overload, while the acpi errors
> are triggered by the rising temperature and probably by the thermal monitor
> feature of Prescotts. Which makes me think that it might be a bios bug or a
> kernel bug.
> For me it is hard to tell which is the cause and which is the effect and
> whether these errors are related or not and have two different but related
> causes - heat and high system load. One thing is certain if the system is
> not stressed out, these errors do not occur. It runs for days without a
> trace of them in the system log.
The dme1737 errors are because the SMBus is busy. The SMBus is busy
because ACPI is accessing it (I believe). The ACPI errors are due to a
broken BIOS/DSDT or more precisely due to a missing _TZ_ method. I
read somewhere (I believe on the linux acpi mailing list) that the
method might become available when loading the acpi_cpufreq module.
...juerg
> Bobby
>
>
> On 10/20/07, Borislav Davitkov <davitkov@gmail.com> wrote:
> > Hi Juerg,
> >
> > Here is another system log with the relevant debug messages. It gets
> interesting at line 8444, especially 8451, and then 8606...
> > Do you have any news about a replacement bios for my motherboard?
> >
> > Bobby
> >
> >
> >
> > On 10/10/07, Juerg Haefliger < juergh@gmail.com> wrote:
> > > Hi Borislav,
> > >
> > >
> > > On 10/9/07, Borislav Davitkov <davitkov@gmail.com> wrote:
> > > > Hi Juerg,
> > > >
> > > > Here is the output of dmesg.
> > > >
> > > > Regarding the acpi errors, I tried to modprobe acpi-cpufreq but I got:
> > > > FATAL: Error inserting acpi_cpufreq
> > > >
> (/lib/modules/2.6.23-rc7-gda8f153e-5-default/kernel/arch/i386/kernel/cpu/cpufreq/acpi-
> > > > cpufreq.ko): No such device
> > >
> > > Try enabling CONFIG_CPU_FREQ_DEBUG and recompile.
> > >
> > >
> > > > Btw, examining the output of dmesg, you will see that the BIOS is
> really
> > > > inadequate:
> > > > PCI: BIOS Bug: MCFG area at e0000000 is not E820-reserved
> > > > PCI: Not using MMCONFIG.
> > > >
> > > > PS: The second output is after I have loaded the cpu 100% and the
> usual
> > > > dme1737 errors have showed up.
> > >
> > > Can you also enable CONFIG_I2C_DEBUG_* and recompile the i2c modules?
> > >
> > > ...juerg
> > >
> > >
> > > >
> > > > On 10/9/07, Juerg Haefliger < juergh@gmail.com> wrote:
> > > > > Hi Bobby,
> > > > >
> > > > > On 10/9/07, Borislav Davitkov < davitkov@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?idf49.
> > > > > 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@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@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@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À0208497&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
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > >
> > > >
> > > >
> > > >
> > >
> >
> >
> >
>
>
>
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
^ permalink raw reply [flat|nested] 11+ messages in thread* Re: [lm-sensors] dme1737 error messages
2007-10-01 18:51 [lm-sensors] dme1737 error messages Juerg Haefliger
` (4 preceding siblings ...)
2007-10-23 17:52 ` Juerg Haefliger
@ 2007-10-24 8:46 ` Jean Delvare
2007-11-06 18:31 ` Juerg Haefliger
` (3 subsequent siblings)
9 siblings, 0 replies; 11+ messages in thread
From: Jean Delvare @ 2007-10-24 8:46 UTC (permalink / raw)
To: lm-sensors
On Tue, 23 Oct 2007 10:41:01 -0700, Juerg Haefliger wrote:
> 5) test Jean's patch that detects ACPI and hwmon collisions. Jean:
> where can he pick it up?
http://jdelvare.pck.nerim.net/sensors/acpi-conflict-check-2.6.23.patch
--
Jean Delvare
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
^ permalink raw reply [flat|nested] 11+ messages in thread* Re: [lm-sensors] dme1737 error messages
2007-10-01 18:51 [lm-sensors] dme1737 error messages Juerg Haefliger
` (5 preceding siblings ...)
2007-10-24 8:46 ` Jean Delvare
@ 2007-11-06 18:31 ` Juerg Haefliger
2007-11-06 21:07 ` Jean Delvare
` (2 subsequent siblings)
9 siblings, 0 replies; 11+ messages in thread
From: Juerg Haefliger @ 2007-11-06 18:31 UTC (permalink / raw)
To: lm-sensors
Hi Bobby,
On 11/4/07, Borislav Davitkov <davitkov@gmail.com> wrote:
> Hi Juerg,
>
> With acpi diabled, both kind of errors are gone (acpi errors, which is to be
> expected, and dme errors). I have another screenshot for you. However this
> also disables hyperthreading, and now I have only cpu0, whereas with acpi on
> I had cpu0 and cpu1.
You can specify acpi=ht to just enable enough ACPI for hyperthreading.
> With no hwmonitoring - only acpi errors.
> With dme1737 module loaded - acpi errors plus dme errors.
> With acpi off - no errors at all.
OK, so it's definitely ACPI that interferes with the dme1737 driver.
Not good. I'm surprised that removing the fan and thermal modules
didn't get rid of the ACPI errors. But then again I'm not an ACPI
expert so don't really know how it works and what to expect...
I recompiled the DSDT that you sent me and it's definitely broken. You
can try to fix it but again I don't know what you can expect from that
exercise. I also took a closer look at the DSDT and there's code that
accesses the dme1737 all over the place. It mocks around with temp
limits and PWM duty cycles and more. It's definitely *not* safe to use
the dme1737 driver, it's interfering with ACPI regulating the fans
based on the measured temps. Now why ACPI is controlling the fans
instead of letting the dme1737 chip take care of it is beyond me...
You'd have to ask the smart designers at ASUS :-)
Bottom line, I think you have 3 options:
1) Disable ACPI and use the dme1737 driver. In that case you loose the
automatic fan control unless you set it up yourself. Dangerous, you're
interfering with the way the machine is designed to work and might fry
it.
2) Take it to the ACPI mailing list and try to figure out what exactly
ACPI is doing and what needs to be fixed to get rid of the ACPI errors
(that still doesn't fix the dme1737/ACPI conflict issue).
3) If you're brave, you can keep using the dme1737 driver, ignore all
the erros and hope and pray it doesn't interfere with ACPI in a way
that puts the HW at risk.
Jean: Do you know where the whole ACPI/hwmon conflict issue is at? Do
we know what the problem is, when it occurs, and how to get around it?
...juerg
> After yet another round of googling about dsdt, acpi etc. I came upon the
> acpi mailing list archive:
> http://marc.info/?l=linux-acpi&m\x119376980121127&w=2
> This is just the last message of a lengthy thread, but the situation they
> are trying to address seems awfully like my own. Or maybe I am mistaken
> again?
> I have also enclosed the output of the grep you wanted but I don't think
> that the pwm is set to automatic.
>
> On 11/4/07, Juerg Haefliger <juergh@gmail.com> wrote:
> > Hi Bobby,
> >
> >
> > On 11/4/07, Borislav Davitkov <davitkov@gmail.com> wrote:
> > > Hi,
> > >
> > > It's me again :)
> > > I finally managed to pinpoint the moment the errors occur. Apparently
> this
> > > happens the moment the bios tries to change the pwm of the cpu fan,
> which in
> > > turn is triggered by reaching certain temperature levels. See the
> > > screenshot. CPU fan pwm has a range of 0-255. If CPU temperature is
> below
> > > 65, pwm is 96. The moment CPUt exceeds 65, pwm is increased to 149. If
> CPUt
> > > falls below 60, pwm is restored to 96. However if t continues to rise
> and
> > > reaches 72, pwm is set to max 255. I managed to find out these values by
> > > comparing logs of pwm and CPUt.
> > > I hope this additional info is somehow useful.
> >
> > Can you try to disable ACPi to rule it out? Add 'acpi=off' to the
> > kernel boot options in your grub menu.lst file. Check if you still get
> > the errors. If yes, it's definitely not ACPI.
> >
> > Also, is your dme1737 set to automatic PWM mode? Please run 'grep ""
> > /sys/class/hwmon/*/device/*' and send me the output. Check the value
> > of pwmX_enable for your CPU fan, if it reads '2' the dme1737 is in
> > automatic mode for this PWM and will control the PWM output
> > automatically depending on the assigned temp input. The BIOS isnot
> > involved at all.
> >
> > ...juerg
> >
> >
> >
> > >
> > > Bobby
> > >
> > >
> > > On 11/3/07, Borislav Davitkov <davitkov@gmail.com > wrote:
> > > > Hi Juerg,
> > > >
> > > > 1. Fan and thermal modules have no bearing to the errors (both acpi
> and
> > > dme). I tried all combinations of them loaded and unloaded.
> > > > 2. acpi_cpufreq is not the module for my processor. The module is
> > > p4-clockmod. Again irrelevant to the errors.
> > > > 3. I have a directory /proc/acpi/thermal_zone but there is nothing in
> it.
> > > > 4. I found this:
> > >
> http://gentoo-wiki.com/HOWTO_Fix_Common_ACPI_Problems#Diagnosing_a_Buggy_DSDT
> > > > Followed the instructions and it really turns out that I have a buggy
> dsdt
> > > (8 errors). However, my errors being quite not so trivial as those in
> the
> > > howto, it is beyond my powers to fix it.
> > > > 5. Tested Jean's patch and it does not help either.
> > > >
> > > > Bobby
> > > >
> > > >
> > > > On 10/23/07, Juerg Haefliger < juergh@gmail.com> wrote:
> > > > > Hi Bobby,
> > > > >
> > > > >
> > >
> ....................................................................
> > > > >
> > > > >
> > > > > So the bottom line is you have a broken BIOS causing the ACPI errors
> > > > > and I believe ACPI and the dme1737 driver collide.
> > > > >
> > > > > Here are a few suggestions of things you can try:
> > > > > 1) unload the fan and thermal modules and check if the dme1737 and
> > > > > ACPI errors go away.
> > > > > 2) load the acpi_cpufreq module (don't know if your HW is supported
> > > > > though) and check if the ACPI errors go away.
> > > > > 3) load the thermal module and do 'grep ""
> > > > > /proc/acpi/thermal_zone/*/*' and send the output to the list.
> > > > > 4) send me the DSDT table (in private): cat /proc/acpi/dsdt >
> dsdt.aml
> > > > > 5) test Jean's patch that detects ACPI and hwmon collisions. Jean:
> > > > > where can he pick it up?
> > > > >
> > > > > > Do you have any news about a replacement bios for my motherboard?
> > > > >
> > > > > Nope, couldn't find anything, sorry.
> > > > >
> > > > > ...juerg
> > > > >
> > > > >
> > > > > > Bobby
> > > > > >
> > > > > >
> > > > > > On 10/10/07, Juerg Haefliger <juergh@gmail.com > wrote:
> > > > > > > Hi Borislav,
> > > > > > >
> > > > > > >
> > > > > > > On 10/9/07, Borislav Davitkov < davitkov@gmail.com> wrote:
> > > > > > > > Hi Juerg,
> > > > > > > >
> > > > > > > > Here is the output of dmesg.
> > > > > > > >
> > > > > > > > Regarding the acpi errors, I tried to modprobe acpi-cpufreq
> but I
> > > got:
> > > > > > > > FATAL: Error inserting acpi_cpufreq
> > > > > > > >
> > > > > >
> > >
> (/lib/modules/2.6.23-rc7-gda8f153e-5-default/kernel/arch/i386/kernel/cpu/cpufreq/acpi-
> > > > > > > > cpufreq.ko): No such device
> > > > > > >
> > > > > > > Try enabling CONFIG_CPU_FREQ_DEBUG and recompile.
> > > > > > >
> > > > > > >
> > > > > > > > Btw, examining the output of dmesg, you will see that the BIOS
> is
> > > really
> > > > > > > > inadequate:
> > > > > > > > PCI: BIOS Bug: MCFG area at e0000000 is not E820-reserved
> > > > > > > > PCI: Not using MMCONFIG.
> > > > > > > >
> > > > > > > > PS: The second output is after I have loaded the cpu 100% and
> the
> > > usual
> > > > > > > > dme1737 errors have showed up.
> > > > > > >
> > > > > > > Can you also enable CONFIG_I2C_DEBUG_* and recompile the i2c
> > > modules?
> > > > > > >
> > > > > > > ...juerg
> > > > > > >
> > > > > > >
> > > > > > > >
> > > > > > > > On 10/9/07, Juerg Haefliger < juergh@gmail.com> wrote:
> > > > > > > > > Hi Bobby,
> > > > > > > > >
> > > > > > > > > On 10/9/07, Borislav Davitkov <davitkov@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?idf49.
> > > > > > > > > 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@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@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@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À0208497&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
> > > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > >
> > > >
> > > >
> > > >
> > >
> > >
> > >
> >
>
>
>
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
^ permalink raw reply [flat|nested] 11+ messages in thread* Re: [lm-sensors] dme1737 error messages
2007-10-01 18:51 [lm-sensors] dme1737 error messages Juerg Haefliger
` (6 preceding siblings ...)
2007-11-06 18:31 ` Juerg Haefliger
@ 2007-11-06 21:07 ` Jean Delvare
2007-11-06 21:20 ` Juerg Haefliger
2007-11-07 17:14 ` Jean Delvare
9 siblings, 0 replies; 11+ messages in thread
From: Jean Delvare @ 2007-11-06 21:07 UTC (permalink / raw)
To: lm-sensors
Hi Juerg,
On Tue, 6 Nov 2007 10:31:22 -0800, Juerg Haefliger wrote:
> Hi Bobby,
>
> On 11/4/07, Borislav Davitkov <davitkov@gmail.com> wrote:
> > Hi Juerg,
> >
> > With acpi diabled, both kind of errors are gone (acpi errors, which is to be
> > expected, and dme errors). I have another screenshot for you. However this
> > also disables hyperthreading, and now I have only cpu0, whereas with acpi on
> > I had cpu0 and cpu1.
>
> You can specify acpi=ht to just enable enough ACPI for hyperthreading.
>
>
> > With no hwmonitoring - only acpi errors.
> > With dme1737 module loaded - acpi errors plus dme errors.
> > With acpi off - no errors at all.
>
> OK, so it's definitely ACPI that interferes with the dme1737 driver.
> Not good. I'm surprised that removing the fan and thermal modules
> didn't get rid of the ACPI errors. But then again I'm not an ACPI
> expert so don't really know how it works and what to expect...
>
> I recompiled the DSDT that you sent me and it's definitely broken. You
> can try to fix it but again I don't know what you can expect from that
> exercise. I also took a closer look at the DSDT and there's code that
> accesses the dme1737 all over the place. It mocks around with temp
> limits and PWM duty cycles and more. It's definitely *not* safe to use
> the dme1737 driver, it's interfering with ACPI regulating the fans
> based on the measured temps. Now why ACPI is controlling the fans
> instead of letting the dme1737 chip take care of it is beyond me...
> You'd have to ask the smart designers at ASUS :-)
There's nothing fundamentally wrong with this, if the ACPI
implementation is correct. Why require an OS driver if they can do the
same in ACPI and it works on all OSes without user interaction?
Of course this also means that the user has almost no control over
what's going on, which is alright if things work well, but becomes a
problem if they don't. The worst thing is that almost all the time, the
ACPI stuff only exposes a small subset of the hardware monitoring
chip's features, which is very frustrating for computer enthusiasts.
> Bottom line, I think you have 3 options:
> 1) Disable ACPI and use the dme1737 driver. In that case you loose the
> automatic fan control unless you set it up yourself. Dangerous, you're
> interfering with the way the machine is designed to work and might fry
> it.
> 2) Take it to the ACPI mailing list and try to figure out what exactly
> ACPI is doing and what needs to be fixed to get rid of the ACPI errors
> (that still doesn't fix the dme1737/ACPI conflict issue).
> 3) If you're brave, you can keep using the dme1737 driver, ignore all
> the erros and hope and pray it doesn't interfere with ACPI in a way
> that puts the HW at risk.
>
> Jean: Do you know where the whole ACPI/hwmon conflict issue is at? Do
> we know what the problem is, when it occurs, and how to get around it?
The patch I posted (which will be in the next -mm kernel also) attempts
to detect the conflicts, and the hwmon and i2c (bus) drivers will
cooperate and refuse to load when a conflict is detected. This approach
relies on the fact that ACPI is supposed to declare which ports it may
access at run time. This may yield false negatives (if ACPI doesn't
declare port usage properly) and false positives (if ACPI declares
ports that it doesn't actually use.) So we're waiting to see the effect
of the patch on a large number of systems, if it is acceptable it will
go upstream.
It would be great if Borislav could try either my patch or the next -mm
kernel, and report whether the conflict is detected or not.
What we will do next, I'm not sure. In some cases it might be possible
to synchronize the hwmon driver accesses with the ACPI accesses, then
we can get both to cooperate. In other cases it probably won't be
possible and we'll have blacklist the hwmon driver, I fear. There is
also at least one known case where an "ACPI hwmon driver" can be
written on top of the ACPI code to expose all the features as regular
hwmon drivers do. All in all, the outcome will probably be highly
dependent upon the machine, as every ACPI implementation is different.
I'll keep the list updated when things progress, of course.
--
Jean Delvare
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
^ permalink raw reply [flat|nested] 11+ messages in thread* Re: [lm-sensors] dme1737 error messages
2007-10-01 18:51 [lm-sensors] dme1737 error messages Juerg Haefliger
` (7 preceding siblings ...)
2007-11-06 21:07 ` Jean Delvare
@ 2007-11-06 21:20 ` Juerg Haefliger
2007-11-07 17:14 ` Jean Delvare
9 siblings, 0 replies; 11+ messages in thread
From: Juerg Haefliger @ 2007-11-06 21:20 UTC (permalink / raw)
To: lm-sensors
Hi Jean,
On 11/6/07, Jean Delvare <khali@linux-fr.org> wrote:
> Hi Juerg,
>
> On Tue, 6 Nov 2007 10:31:22 -0800, Juerg Haefliger wrote:
> > Hi Bobby,
> >
> > On 11/4/07, Borislav Davitkov <davitkov@gmail.com> wrote:
> > > Hi Juerg,
> > >
> > > With acpi diabled, both kind of errors are gone (acpi errors, which is to be
> > > expected, and dme errors). I have another screenshot for you. However this
> > > also disables hyperthreading, and now I have only cpu0, whereas with acpi on
> > > I had cpu0 and cpu1.
> >
> > You can specify acpi=ht to just enable enough ACPI for hyperthreading.
> >
> >
> > > With no hwmonitoring - only acpi errors.
> > > With dme1737 module loaded - acpi errors plus dme errors.
> > > With acpi off - no errors at all.
> >
> > OK, so it's definitely ACPI that interferes with the dme1737 driver.
> > Not good. I'm surprised that removing the fan and thermal modules
> > didn't get rid of the ACPI errors. But then again I'm not an ACPI
> > expert so don't really know how it works and what to expect...
> >
> > I recompiled the DSDT that you sent me and it's definitely broken. You
> > can try to fix it but again I don't know what you can expect from that
> > exercise. I also took a closer look at the DSDT and there's code that
> > accesses the dme1737 all over the place. It mocks around with temp
> > limits and PWM duty cycles and more. It's definitely *not* safe to use
> > the dme1737 driver, it's interfering with ACPI regulating the fans
> > based on the measured temps. Now why ACPI is controlling the fans
> > instead of letting the dme1737 chip take care of it is beyond me...
> > You'd have to ask the smart designers at ASUS :-)
>
> There's nothing fundamentally wrong with this, if the ACPI
> implementation is correct. Why require an OS driver if they can do the
> same in ACPI and it works on all OSes without user interaction?
What I meant by my comment is that I don't understand why they don't
make use of the automatic fan control feature of the dme1737 chip.
That would be much simpler (setting up a couple of registers) and
wouldn't require implementing a closed-loop control algorithm SW. It's
an ASUS board and they do it for other motherboards, so why not on
this one? Maybe it's an HP requirement, I don't know...
> Of course this also means that the user has almost no control over
> what's going on, which is alright if things work well, but becomes a
> problem if they don't. The worst thing is that almost all the time, the
> ACPI stuff only exposes a small subset of the hardware monitoring
> chip's features, which is very frustrating for computer enthusiasts.
>
> > Bottom line, I think you have 3 options:
> > 1) Disable ACPI and use the dme1737 driver. In that case you loose the
> > automatic fan control unless you set it up yourself. Dangerous, you're
> > interfering with the way the machine is designed to work and might fry
> > it.
> > 2) Take it to the ACPI mailing list and try to figure out what exactly
> > ACPI is doing and what needs to be fixed to get rid of the ACPI errors
> > (that still doesn't fix the dme1737/ACPI conflict issue).
> > 3) If you're brave, you can keep using the dme1737 driver, ignore all
> > the erros and hope and pray it doesn't interfere with ACPI in a way
> > that puts the HW at risk.
> >
> > Jean: Do you know where the whole ACPI/hwmon conflict issue is at? Do
> > we know what the problem is, when it occurs, and how to get around it?
>
> The patch I posted (which will be in the next -mm kernel also) attempts
> to detect the conflicts, and the hwmon and i2c (bus) drivers will
> cooperate and refuse to load when a conflict is detected. This approach
> relies on the fact that ACPI is supposed to declare which ports it may
> access at run time. This may yield false negatives (if ACPI doesn't
> declare port usage properly) and false positives (if ACPI declares
> ports that it doesn't actually use.) So we're waiting to see the effect
> of the patch on a large number of systems, if it is acceptable it will
> go upstream.
>
> It would be great if Borislav could try either my patch or the next -mm
> kernel, and report whether the conflict is detected or not.
He claims he tested it and it didn't do anything. Bobby: Can you elaborate?
> What we will do next, I'm not sure. In some cases it might be possible
> to synchronize the hwmon driver accesses with the ACPI accesses, then
> we can get both to cooperate.
How can we achieve cooperation between the two?
> In other cases it probably won't be
> possible and we'll have blacklist the hwmon driver, I fear.
Uh-huh... Based on the motherboard/system type? How does that work?
> There is
> also at least one known case where an "ACPI hwmon driver" can be
> written on top of the ACPI code to expose all the features as regular
> hwmon drivers do. All in all, the outcome will probably be highly
> dependent upon the machine, as every ACPI implementation is different.
>
> I'll keep the list updated when things progress, of course.
Thanks, very much appreciated.
...juerg
> --
> Jean Delvare
>
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
^ permalink raw reply [flat|nested] 11+ messages in thread* Re: [lm-sensors] dme1737 error messages
2007-10-01 18:51 [lm-sensors] dme1737 error messages Juerg Haefliger
` (8 preceding siblings ...)
2007-11-06 21:20 ` Juerg Haefliger
@ 2007-11-07 17:14 ` Jean Delvare
9 siblings, 0 replies; 11+ messages in thread
From: Jean Delvare @ 2007-11-07 17:14 UTC (permalink / raw)
To: lm-sensors
Hi Juerg,
On Tue, 6 Nov 2007 13:20:22 -0800, Juerg Haefliger wrote:
> On 11/6/07, Jean Delvare wrote:
> > On Tue, 6 Nov 2007 10:31:22 -0800, Juerg Haefliger wrote:
> > > I recompiled the DSDT that you sent me and it's definitely broken. You
> > > can try to fix it but again I don't know what you can expect from that
> > > exercise. I also took a closer look at the DSDT and there's code that
> > > accesses the dme1737 all over the place. It mocks around with temp
> > > limits and PWM duty cycles and more. It's definitely *not* safe to use
> > > the dme1737 driver, it's interfering with ACPI regulating the fans
> > > based on the measured temps. Now why ACPI is controlling the fans
> > > instead of letting the dme1737 chip take care of it is beyond me...
> > > You'd have to ask the smart designers at ASUS :-)
> >
> > There's nothing fundamentally wrong with this, if the ACPI
> > implementation is correct. Why require an OS driver if they can do the
> > same in ACPI and it works on all OSes without user interaction?
>
> What I meant by my comment is that I don't understand why they don't
> make use of the automatic fan control feature of the dme1737 chip.
> That would be much simpler (setting up a couple of registers) and
> wouldn't require implementing a closed-loop control algorithm SW. It's
> an ASUS board and they do it for other motherboards, so why not on
> this one? Maybe it's an HP requirement, I don't know...
Sorry, I had misunderstood your question. I had not realized that the
ACPI code was implementing software fan control. I agree with you that
it's silly to do in software something that can be done much more
efficiently and reliably by the hardware. I have no clue why they did
that, but that's unfortunately not the first time I see this.
> (...)
> > What we will do next, I'm not sure. In some cases it might be possible
> > to synchronize the hwmon driver accesses with the ACPI accesses, then
> > we can get both to cooperate.
>
> How can we achieve cooperation between the two?
There's a mutex protecting the execution of AML code. If the hwmon
driver takes it when accessing the chip, at least we know that there
won't be conflicting I/O accesses. But this doesn't solve the possible
functional conflict if ACPI is doing really weird things. Maybe we'll
want to turn the hwmon driver read-only in some cases.
> > In other cases it probably won't be
> > possible and we'll have blacklist the hwmon driver, I fear.
>
> Uh-huh... Based on the motherboard/system type? How does that work?
That would be based on DMI data, I think. That's the last resort, I
hope that we can avoid blacklisting in most cases.
But it's really only ideas at this point, I did not start writing code
and many things can still be discussed on a case-by-case basis. I'll
try to fix my own system first, when I get time, and once this is done,
depending on the result, I'll see what I can do for other systems.
--
Jean Delvare
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
^ permalink raw reply [flat|nested] 11+ messages in thread