All of lore.kernel.org
 help / color / mirror / Atom feed
From: khali@linux-fr.org (Jean Delvare)
To: lm-sensors@vger.kernel.org
Subject: [lm-sensors] Question on my mainboard
Date: Fri, 31 Mar 2006 10:27:09 +0000	[thread overview]
Message-ID: <20060331122709.45c81c66.khali@linux-fr.org> (raw)
In-Reply-To: <200603282150.16130.dieter.jurzitza@t-online.de>

Hi Dieter,

> I am using several Tyan Tiger 2460 motherboards since quite a while. And I am 
> observing a strange behaviour someone in the list (might) have a clue about.
> 
> I am reading the sensors data periodically every 10 seconds. After an 
> undefined time (maybe one week, maybe one day, maybe three weeks) sensors 
> "hangs" after start and cannot be killed any more. A manual call to sensors 
> ends in a hang as well (of sensors, the board is running on).
> 
> What is my configuration:
> I am loading 
> MODULE_0=i2c-amd756
> MODULE_1=i2c-isa
> MODULE_2=w83781d
> MODULE_3îprom
> MODULE_4=w83627hf
> (in this sequence).
> 
> By recommendation from Tyan I use the line:
> options w83781d force_w83782d=0,0x2d force_subclients=0,0x2d,0x48,0x49 
> force_w83627hf=0,0x2c force_subclients=0,0x2c,0x4a,0x4b init=0
> 
> in /etc/modprobe.conf.local

This doesn't make much sense. You ask the w83781d driver to take care
of the W83627HF chip, but also load the w83627hf driver. Both drivers
will attempt to handle the same chip, this might explain the deadlock.

I'd suggest that you try without loading the w83627hf driver. If the
w83781d driver is able to handle both chips (the W83782D and the
W83627HF) then the w83627hf driver is not needed at all.

-- 
Jean Delvare


  parent reply	other threads:[~2006-03-31 10:27 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-28 19:50 [lm-sensors] Question on my mainboard Dieter Jurzitza
2006-03-30 21:45 ` Rudolf Marek
2006-03-31 10:27 ` Jean Delvare [this message]
2006-03-31 14:50 ` Steven Timm
2006-03-31 19:32 ` Dieter Jurzitza
2006-04-02 18:18 ` Dieter Jurzitza
2006-04-05  8:28 ` Rudolf Marek
2006-04-09 10:16 ` Dieter Jurzitza
2006-04-09 10:29 ` Rudolf Marek
2006-04-18 18:43 ` Dieter Jurzitza
2006-04-18 20:30 ` Rudolf Marek
2006-04-18 20:53 ` Dieter Jurzitza

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=20060331122709.45c81c66.khali@linux-fr.org \
    --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.