From: Jean Delvare <khali@linux-fr.org>
To: lm-sensors@vger.kernel.org
Subject: Re: [lm-sensors] dme1737 0-002e: Write to register 0x30 failed!
Date: Tue, 23 Oct 2007 12:22:08 +0000 [thread overview]
Message-ID: <20071023142208.6f03a703@hyperion.delvare> (raw)
In-Reply-To: <1642847378@web.de>
On Sun, 21 Oct 2007 21:37:26 +0200, Jean Delvare wrote:
> Juergen,
>
> On Sat, 20 Oct 2007 21:39:32 +0200, Juergen Bausa wrote:
> > > Von: Jean Delvare <khali@linux-fr.org>
> > > Juergen, if you load the "thermal" driver and look
> > > in /proc/acpi/thermal_zone, do you see a temperature reported, with the
> > > same value as one of the DME1737 temperature channels?
> >
> > Yes, I see a temperature, but its not the same.
> >
> > lisa:/home/jba# cat /proc/acpi/thermal_zone/THRM/temperature
> > temperature: 40 C
> > lisa:/home/jba# sensors
> > k8temp-pci-00c3
> > Adapter: PCI adapter
> > Core0 Temp:
> > +44°C
> > Core0 Temp:
> > +46°C
> > Core1 Temp:
> > +52°C
> > Core1 Temp:
> > +49°C
> >
> > dme1737-i2c-0-2e
> > Adapter: SMBus nForce2 adapter at 4c00
> > V5stby: +0.00 V (min = +0.00 V, max = +6.64 V) ALARM
> > Vccp: +1.09 V (min = +0.00 V, max = +2.99 V)
> > V3.3: +3.27 V (min = +0.00 V, max = +4.38 V)
> > V5: +4.93 V (min = +0.00 V, max = +6.64 V)
> > V12: +11.78 V (min = +0.00 V, max = +15.94 V)
> > V3.3stby: +3.28 V (min = +0.00 V, max = +4.38 V)
> > Vbat: +2.98 V (min = +0.00 V, max = +4.38 V)
> > Int Temp: +32°C (low = -127°C, high = +127°C)
> > CPU Temp: +30°C (low = -127°C, high = +127°C)
> > CPU_Fan: 0 RPM (min = 0 RPM)
> > ERROR: Can't get fan3 data!
> > ERROR: Can't get fan5 data!
> > ERROR: Can't get fan6 data!
> > CPU_PWM: 0 (enable = 1, freq = 25000 Hz)
> > ERROR: Can't get pwm5 data!
> > ERROR: Can't get pwm6 data!
> > cpu0_vid: +1.550 V (VRM Version 2.4)
> >
> > lisa:/home/jba#
>
> OK. It doesn't mean that ACPI doesn't get the temperatures from the
> DME1737 chip though, it could be adding some arbitrary offset. Can you
> please send me your DSDT table in private? I'll take a look.
OK, I've taken a look at the DSDT and it includes references to
hardware monitoring features all around the place:
Device (ASOC)
{
Name (_HID, "ATK0110")
Name (_UID, 0x01010110)
Name (MBIF, Package (0x08)
{
0x01,
"M2N8L",
0x01010101,
0x01010101,
0xC0010002,
0x01,
0x00,
0x00
})
Name (VBUF, Package (0x05)
{
0x04,
VCRE,
V333,
V500,
V120
})
Name (VCRE, Package (0x05)
{
0x06020000,
"Vcore Voltage",
0x05AA,
0x06D6,
0x01
})
Name (V333, Package (0x05)
{
0x06020001,
" +3.3 Voltage",
0x0BB8,
0x0E10,
0x01
})
Name (V500, Package (0x05)
{
0x06020002,
" +5.0 Voltage",
0x1194,
0x157C,
0x01
})
Name (V120, Package (0x05)
{
0x06020003,
"+12.0 Voltage",
0x2BC0,
0x3390,
0x01
})
Name (TBUF, Package (0x03)
{
0x02,
CPUT,
MBTP
})
Name (CPUT, Package (0x05)
{
0x06030000,
"CPU Temperature",
0x0384,
0x04E2,
0x00010001
})
Name (MBTP, Package (0x05)
{
0x06030001,
"MB Temperature",
0x02BC,
0x04E2,
0x00010001
})
Name (FBUF, Package (0x06)
{
0x03,
CPUF,
CHAF,
PWRF,
CHPF,
CH2F
})
Name (CPUF, Package (0x05)
{
0x06040000,
"CPU FAN Speed",
0x00,
0x0708,
0x00010001
})
Name (CHAF, Package (0x05)
{
0x06040001,
"CHASSIS FAN Speed",
0x00,
0x0708,
0x01
})
Name (PWRF, Package (0x05)
{
0x06040002,
"POWER FAN Speed",
0x00,
0x0708,
0x00
})
Name (CHPF, Package (0x05)
{
0x06040005,
"CHIPSET FAN Speed",
0x00,
0x0708,
0x00
})
Name (CH2F, Package (0x05)
{
0x06040006,
"CHASSIS2 FAN Speed",
0x00,
0x0708,
0x00
})
Name (QFAN, Package (0x05)
{
0x04060003,
"CPU Q-Fan Control",
0x00,
0x01,
0x01
})
Name (QFRO, Package (0x05)
{
0x04050004,
"CPU Q-Fan Ratio",
0x3C,
0x5A,
0x00
})
Name (QFTP, Package (0x05)
{
0x04030005,
"Temperature Range",
0x02,
0x50,
0x00010001
})
Name (QCFN, Package (0x05)
{
0x04060006,
"Chassis Q-Fan Control",
0x00,
0x01,
0x00
})
Name (QFCR, Package (0x05)
{
0x04050007,
"Chassis Q-Fan Ratio",
0x38,
0x64,
0x00
})
etc etc. This appears to be the half-standard ATK0110 implementation
for which a driver was posted to the lm-sensors list a few months ago.
Maybe for this motherboard you should use this driver rather than the
dme1737 driver. Adding Rudolf in Cc, I think he knows more about this
driver's status.
The DSDT also includes references to the nforce2's SMBus:
Device (SMB0)
{
Name (_ADR, 0x000A0001)
OperationRegion (SMCF, PCI_Config, 0x48, 0x10)
Field (SMCF, DWordAcc, NoLock, Preserve)
{
SMPM, 4,
SMT1, 28,
SMT2, 32
}
OperationRegion (SMCA, PCI_Config, 0x20, 0x08)
Field (SMCA, DWordAcc, NoLock, Preserve)
{
SB1, 32,
SB2, 32
}
OperationRegion (PDEV, PCI_Config, 0xE8, 0x04)
Scope (\)
{
Field (\_SB.PCI0.SMB0.PDEV, AnyAcc, NoLock, Preserve)
{
, 12,
ACIE, 1
}
}
Method (SMBB, 0, NotSerialized)
{
If (PCIA)
{
And (SB1, 0xFFFE, Local0)
}
Else
{
Store (0x4C00, Local0)
}
Return (Local0)
}
}
So at the very least I'd say it's not safe to use the i2c-nforce2 and
dme1737 drivers when the fan and thermal ACPI drivers are in use. But
it may even not be safe when these ACPI drivers aren't loaded, I don't
know.
That being said, I can't guarantee that the I/O errors you've seen are
related to this. There may _also_ be a second master on the SMBus
talking to whatever chip is at address 0x0d. So adding a retry
mechanism to i2c-nforce2 may still be a good idea.
> I also have an experimental (but safe) patch detecting possible
> conflicts between ACPI and hwmon drivers. Do you want to test it?
Hopefully the patch in question will also detect the conflict.
--
Jean Delvare
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
next prev parent reply other threads:[~2007-10-23 12:22 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-25 19:08 [lm-sensors] dme1737 0-002e: Write to register 0x30 failed! Juergen Bausa
2007-10-01 17:44 ` Juerg Haefliger
2007-10-01 19:22 ` Juergen Bausa
2007-10-01 21:39 ` Juerg Haefliger
2007-10-01 21:50 ` Jean Delvare
2007-10-08 18:31 ` Juergen Bausa
2007-10-09 7:03 ` Jean Delvare
2007-10-09 16:08 ` Juerg Haefliger
2007-10-09 19:41 ` Juergen Bausa
2007-10-10 17:12 ` Juerg Haefliger
2007-10-11 7:45 ` Jean Delvare
2007-10-17 18:56 ` Juergen Bausa
2007-10-17 19:43 ` Juerg Haefliger
2007-10-17 21:32 ` Jean Delvare
2007-10-18 4:53 ` Juerg Haefliger
2007-10-19 15:07 ` Jean Delvare
2007-10-20 19:28 ` Juergen Bausa
2007-10-20 19:39 ` Juergen Bausa
2007-10-21 18:40 ` Mark M. Hoffman
2007-10-21 19:14 ` Jean Delvare
2007-10-21 19:37 ` Jean Delvare
2007-10-22 16:02 ` Juerg Haefliger
2007-10-22 16:05 ` Juerg Haefliger
2007-10-23 12:08 ` Jean Delvare
2007-10-23 12:22 ` Jean Delvare [this message]
2007-10-23 20:44 ` Juergen Bausa
2007-10-23 21:54 ` Rudolf Marek
2007-10-24 8:48 ` Jean Delvare
2007-10-29 21:23 ` Rudolf Marek
2007-10-30 2:52 ` Juerg Haefliger
2007-10-31 2:40 ` Juerg Haefliger
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20071023142208.6f03a703@hyperion.delvare \
--to=khali@linux-fr.org \
--cc=lm-sensors@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.