From: khali@linux-fr.org (Jean Delvare)
To: lm-sensors@vger.kernel.org
Subject: [lm-sensors] DFI Lan Party SLI-DR Expert shuts off when it87 is
Date: Thu, 16 Mar 2006 09:13:47 +0000 [thread overview]
Message-ID: <QtmlAR8K.1142500427.0326340.khali@localhost> (raw)
In-Reply-To: <a33b5feb0603152333t5f7dcc28i24b235e39d595706@mail.gmail.com>
Hi Brian,
On 2006-03-16, Brian Hayward wrote:
> First off, when running sensors-detect, if I select "yes" for the next
> question, the computer turns off.
> Next adapter: SMBus nForce2 adapter at 1c40
> Do you want to scan it? (YES/no/selectively):
>
> The computer just powers down, as if I turned the switch off. No warning
> or anything.
>
> If I select NO to the 1c40 nForc2 option and then YES to all others - the
> computer does not power off until I modprobe it87.
>
> I've tried:
> modprobe it87
> modprobe it87 force_it87‘91,0x290
> Same problem either way, immediate shutdown.
Try modprobe it87 ignore=-1,0x2e.
> If I load all suggested modules _except_ it87, it does not shut down and
> it also does not show any CPU/Fanspeed redouts when I type "sensors".
>
> Do you have any suggestions?
This was reported already, on the same board. There is a mysterious chip
at address 0x2e on the SMBus which powers off the board when probed.
See: http://bugzilla.kernel.org/show_bug.cgi?idX89
A workaround was merged in 2.6.16-rc3 and 2.6.15.5. We yet have to come
up with a workaround for sensors-detect. The solution would be to detect
this motherboard (e.g. using dmidecode) and skip probing the faulty
address automatically.
--
Jean Delvare
prev parent reply other threads:[~2006-03-16 9:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-16 7:33 [lm-sensors] DFI Lan Party SLI-DR Expert shuts off when it87 is Brian Hayward
2006-03-16 7:39 ` Brian Hayward
2006-03-16 9:13 ` Jean Delvare [this message]
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=QtmlAR8K.1142500427.0326340.khali@localhost \
--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.