All of lore.kernel.org
 help / color / mirror / Atom feed
From: Guenter Roeck <linux@roeck-us.net>
To: lm-sensors@vger.kernel.org
Subject: Re: [lm-sensors] sensors command now hangs [update 2]
Date: Mon, 17 Feb 2014 23:17:09 +0000	[thread overview]
Message-ID: <53029875.5040907@roeck-us.net> (raw)
In-Reply-To: <53027C66.60608@gmail.com>

On 02/17/2014 01:17 PM, David Anderson wrote:
> Well, even without ipmi sensors hangs up
> at (hand typing this) after just 6 hours:
>
> ...
> w83795adg-i2c-0-27
> Adapter: SMBus I801 at 0400
>
>
>
> Google search shows someone using redhat has a hanging
> sensors command too :
>
> https://bugzilla.redhat.com/show_bug.cgi?id\x1051274
>
> Note there the apparent workaround of nouveau.runrpm=0
> on the kernel command line.
> I'm using Nvidia driver  319.60 for the GTX 760
>

Hi David,

That looks like a different problem, though, unless you
access the nouveau sensor after all. Is it instantiated
in your system ?

To be sure to exclude this, you could try the command line
workaround. Note, though, that it is nouveau.runpm,
not nouveau.runrpm.

Overall I am quite puzzled, as you mentioned earlier that
you also see the hang with the w83627hf driver loaded.
I can not really imagine why (and how) either of those
drivers can end up in a 'hang' condition.

I think I already asked this - in your original e-mail,
you mentioned that the sensors command 'now hangs', and that
only started happening some time ago. What did you change -
if anything - in your system before this started to happen ?

Thanks,
Guenter


_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

  reply	other threads:[~2014-02-17 23:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-17 21:17 [lm-sensors] sensors command now hangs [update 2] David Anderson
2014-02-17 23:17 ` Guenter Roeck [this message]
2014-02-18  0:43 ` David Anderson
2014-02-18  4:07 ` Guenter Roeck

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=53029875.5040907@roeck-us.net \
    --to=linux@roeck-us.net \
    --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.