From: "Jean Delvare" <khali@linux-fr.org>
To: linux-kernel@vger.kernel.org
Cc: "Ryan Richter" <ryan@tau.solarneutrino.net>,
"Erik Mouw" <erik@harddisk-recovery.com>,
"Nick Warne" <nick@linicks.net>
Subject: Re: Random reboots
Date: Wed, 15 Feb 2006 17:20:37 +0100 (CET) [thread overview]
Message-ID: <ARSSpsNs.1140020437.1823510.khali@localhost> (raw)
In-Reply-To: <20060215160036.GB17864@tau.solarneutrino.net>
Ryan,
On 2006-02-15, Ryan Richter wrote:
> It's a Tyan S2880, and I'm using their sensors.conf:
>
> ftp://ftp.tyan.com/software/lms/lms_s2880.tgz
>
> Here's what sensors reports:
>
> w83627hf-isa-0290
> Adapter: ISA adapter
> VCore 1: +1.54 V (min = +1.47 V, max = +1.62 V) ALARM
> VCore 2: +1.54 V (min = +1.47 V, max = +1.62 V) ALARM
> +3.3V: +3.33 V (min = +3.14 V, max = +3.46 V)
> +5V: +4.97 V (min = +4.73 V, max = +5.24 V)
> +12V: +4.56 V (min = +10.82 V, max = +13.19 V)
> -12V: -2.25 V (min = -13.18 V, max = -10.88 V)
> -5V: -3.94 V (min = -5.25 V, max = -4.75 V)
> V5SB: +5.51 V (min = +4.73 V, max = +5.24 V)
> VBat: +1.28 V (min = +2.40 V, max = +3.60 V)
> fan1: 4354 RPM (min = -1 RPM, div = 2)
> fan2: 3479 RPM (min = 5273 RPM, div = 2)
> fan3: 0 RPM (min = 30681 RPM, div = 2)
> temp1: +77°C (high = -128°C, hyst = -128°C) sensor = thermistor
> temp2: +77.5°C (high = +80°C, hyst = +75°C) sensor = thermistor
> temp3: +77.5°C (high = +80°C, hyst = +75°C) sensor = thermistor
> vid: +1.550 V (VRM Version 2.4)
There's one chip missing. If memory serves, this board has two hardware
monitoring chips: one Winbond Super-I/O and one LM85-compatible SMBus
chip. You are missing the i2c-amd756 driver in your kernel build
(CONFIG_I2C_AMD756) which prevents you from accessing that second chip.
Additionally, the Winbond Super-I/O chips are better supported by the
newer w83627hf driver than by the w83781d you are using.
So, you should change your kernel configuration to:
CONFIG_I2C_AMD756=y
#CONFIG_SENSORS_W83781D is not set
CONFIG_SENSORS_W83627HF=y
Then you'll probably have much better results - even if the
configuration file might need additional tweaking.
> Still, I don't see why the new kernel shouldn't be stable if 2.6.11.3
> was.
If not software regression, the aging of your hardware might have caused
it, as I mentioned earlier. But you are free to believe in the
hypothesis you prefer, given that we are not currently able to
demonstrate it anyway ;)
--
Jean Delvare
next prev parent reply other threads:[~2006-02-15 16:23 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-13 21:04 Random reboots Ryan Richter
2006-02-13 21:10 ` anders
2006-02-13 21:22 ` Ryan Richter
[not found] ` <7c3341450602131332x2fcd7d8co@mail.gmail.com>
2006-02-13 21:39 ` Ryan Richter
2006-02-13 21:49 ` Ryan Richter
2006-02-14 8:54 ` Erik Mouw
2006-02-14 13:29 ` Ryan Richter
2006-02-14 14:47 ` Nick Warne
2006-02-14 22:22 ` Jean Delvare
2006-02-15 14:28 ` Ryan Richter
2006-02-15 15:11 ` linux-os (Dick Johnson)
2006-02-15 15:13 ` Ryan Richter
2006-02-15 15:41 ` Jean Delvare
2006-02-15 16:00 ` Ryan Richter
2006-02-15 16:20 ` Jean Delvare [this message]
2006-02-15 16:30 ` Ryan Richter
2006-02-15 18:46 ` Ryan Richter
2006-02-27 20:35 ` Ryan Richter
-- strict thread matches above, loose matches on Subject: below --
2001-04-24 16:18 random reboots Nathan Walp
2001-04-26 1:36 ` Petr Vandrovec
2001-04-26 1:52 ` Nathan Walp
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=ARSSpsNs.1140020437.1823510.khali@localhost \
--to=khali@linux-fr.org \
--cc=erik@harddisk-recovery.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nick@linicks.net \
--cc=ryan@tau.solarneutrino.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox