From: Guenter Roeck <linux@roeck-us.net>
To: lm-sensors@vger.kernel.org
Subject: Re: [lm-sensors] sensors command now hangs [update 2]
Date: Tue, 18 Feb 2014 04:07:59 +0000 [thread overview]
Message-ID: <5302DC9F.2010804@roeck-us.net> (raw)
In-Reply-To: <53027C66.60608@gmail.com>
On 02/17/2014 04:43 PM, David Anderson wrote:
> Not using Noveau driver at all here.
> lsmod |grep nov
> shows nothing. I just thought it was interesting that someone
> else had a hanging sensors command.
>
Hi David,
That grep wont help much, as it is nouveau (with an added u),
not noveau.
> On 02/17/2014 03:17 PM, Guenter Roeck wrote:
>
>> 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 ?
>
> The only change I can think of
> was to move from Ubuntu 13.04 to
> Ubuntu 13.10.
>
Right now I have no idea what may be different. 13.4 is the 3.8 kernel
if I remember correctly, and 13.10 should be 3.11. I did a quick diff
in the relevant drivers but did not see anything that might cause
the problem.
To find out what exactly is hanging, you might try something like
cd /sys/class/hwmon
for d in *
do
(echo $d:
cd $d
if [ ! -f name ]
then
cd device
fi
ls
grep . *
)
done
The last line of output should show the attribute causing the hang,
or rather the one accessed before it.
Guenter
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
prev parent reply other threads:[~2014-02-18 4:07 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
2014-02-18 0:43 ` David Anderson
2014-02-18 4:07 ` Guenter Roeck [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=5302DC9F.2010804@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.