From: kress@hal.saar.de (Michael Kress)
To: lm-sensors@vger.kernel.org
Subject: [lm-sensors] Supermicro X6DH8-G2+ / sensors not working
Date: Sat, 14 Oct 2006 11:43:22 +0000 [thread overview]
Message-ID: <4530CD5A.2010602@hal.saar.de> (raw)
In-Reply-To: <451FF905.60001@hal.saar.de>
Hi Jean,
Jean Delvare schrieb:
> Looks alright. Did you try unloading and reloading the driver a couple
> time? If everything works OK for you I'll push the driver into -mm
> soon, so that it can receive wider testing.
>
sorry, it took a bit ... not because I tested for so long time... ;-)
I've been modprobe'ing und rmmod'ing the driver constantly for an hour
or so (every few seconds, with 'watch') and I can still receive the
expected results without any flaw, nothing irregular, no strange syslog
messages etc.
>> [root at matrix PC87427-platform-driver]# dmesg | tail -n 8
>> pc87427: readall_fan: dataÿff88003f09e540, nr=0
>> pc87427: readall_fan: dataÿff88003f09e540, nr=1
>> pc87427: readall_fan: dataÿff88003f09e540, nr=2
>> pc87427: readall_fan: dataÿff88003f09e540, nr=3
>> pc87427: readall_fan: dataÿff88003f09e540, nr=4
>> pc87427: readall_fan: dataÿff88003f09e540, nr=5
>> pc87427: readall_fan: dataÿff88003f09e540, nr=6
>> pc87427: readall_fan: dataÿff88003f09e540, nr=7
>>
>
> These are temporary debugging messages which I put in there to
> investigate an older bug, which of course never happened again. You can
> get rid of them by removing -DDEBUG in the Makefile and building the
> driver again. You can also replace -g with -O2 for faster and smaller
> code.
>
Debugging messages are gone now.
Thanks & have a nice weekend
Michael
--
Michael Kress, kress at hal.saar.de
http://www.michael-kress.de / http://kress.net
P E N G U I N S A R E C O O L
next prev parent reply other threads:[~2006-10-14 11:43 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-01 17:21 [lm-sensors] Supermicro X6DH8-G2+ / sensors not working Michael Kress
2006-10-04 13:15 ` Jean Delvare
2006-10-04 23:14 ` Michael Kress
2006-10-06 11:09 ` Jean Delvare
2006-10-07 7:35 ` Jean Delvare
2006-10-08 9:14 ` Michael Kress
2006-10-08 9:17 ` Jean Delvare
2006-10-08 10:25 ` Michael Kress
2006-10-08 10:59 ` Michael Kress
2006-10-08 12:21 ` Jean Delvare
2006-10-08 13:07 ` Michael Kress
2006-10-08 13:46 ` Jean Delvare
2006-10-08 14:42 ` Michael Kress
2006-10-08 17:03 ` Jean Delvare
2006-10-08 17:20 ` Michael Kress
2006-10-09 9:23 ` Jean Delvare
2006-10-09 18:03 ` Michael Kress
2006-10-09 20:03 ` Jean Delvare
2006-10-09 20:25 ` Michael Kress
2006-10-10 10:21 ` Jean Delvare
2006-10-14 11:43 ` Michael Kress [this message]
2006-10-14 16:49 ` Michael Kress
2006-10-15 9:03 ` Michael Kress
2006-10-15 12:03 ` Jean Delvare
2006-10-15 20:56 ` Michael Kress
2006-10-16 6:27 ` Jean Delvare
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=4530CD5A.2010602@hal.saar.de \
--to=kress@hal.saar.de \
--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.