From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: Rolf Eike Beer <eike-kernel@sf-tec.de>
Cc: linux-parisc@vger.kernel.org
Subject: Re: Short notice: ipmi_si kills C8000
Date: Tue, 29 Oct 2013 17:41:51 +0100 [thread overview]
Message-ID: <20131029164151.GA10616@alpha.franken.de> (raw)
In-Reply-To: <236d3862441c13623a9fde73e6988591@sf-mail.de>
On Tue, Oct 29, 2013 at 11:41:08AM +0100, Rolf Eike Beer wrote:
> Oops, sorry, I misread the git log. I've now applied that patch to
no problem, maybe it's worth to send the fix to stable now it's
in 3.12
> 3.11.6 and the module loads fine. Am I supposed to see anything in
> the sysfs that I can query now?
I've played only with ipmitool, which gives something like
c8000:~# ipmitool sdr
Systemboard | 30 degrees C | ok
CPU 1 | 43 degrees C | ok
Ambient | 24.50 degrees C | ok
Main +12V | 12.25 Volts | ok
Main -12V | -12.45 Volts | ok
Main +5V | 5.00 Volts | ok
Main 3.3V | 3.35 Volts | ok
Battery +3V | 3.11 Volts | ok
Stdby +3.3V | 3.40 Volts | ok
Main +1.5V | 1.49 Volts | ok
VTT | 1.19 Volts | ok
Main +1.8V | 1.80 Volts | ok
FAN1 SYS | 6360 RPM | ok
FAN2 SYS | 6240 RPM | ok
FAN3 SYS | 6000 RPM | ok
FAN4 SYS | 6240 RPM | ok
FAN5 SYS | 5880 RPM | ok
FAN1 PSU | 2400 RPM | ok
FAN2 PSU | 2400 RPM | ok
SEL Level | 0 unspecified | ok
CPU 1 | 0x80 | ok
PSU | Not Readable | ns
PS1 | 0x02 | ok
FAN1 SYS | 0x01 | ok
FAN2 SYS | 0x01 | ok
FAN3 SYS | 0x01 | ok
FAN4 SYS | 0x01 | ok
FAN5 SYS | 0x01 | ok
FAN1 PSU | 0x01 | ok
FAN2 PSU | 0x01 | ok
Watchdog | 0x00 | ok
iRMC request | 0x00 | ok
System Mgmt SW | Not Readable | ns
local Mon. | 0x02 | ok
Pwr Btn override | 0x01 | ok
Software NMI | 0x00 | ok
System BIOS | Not Readable | ns
iRMC | Not Readable | ns
Thomas.
--
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea. [ RFC1925, 2.3 ]
next prev parent reply other threads:[~2013-10-29 16:41 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-26 14:26 Short notice: ipmi_si kills C8000 Rolf Eike Beer
2013-10-26 17:17 ` Jeroen Roovers
2013-10-28 10:56 ` Thomas Bogendoerfer
2013-10-29 9:37 ` Thomas Bogendoerfer
2013-10-29 10:41 ` Rolf Eike Beer
2013-10-29 16:41 ` Thomas Bogendoerfer [this message]
2013-10-29 17:14 ` Jeroen Roovers
2013-10-29 19:50 ` Helge Deller
2013-10-31 12:06 ` Thomas Bogendoerfer
2013-10-31 12:22 ` Helge Deller
2013-11-02 16:18 ` John David Anglin
2013-10-31 21:40 ` Rolf Eike Beer
2013-11-05 12:23 ` Rolf Eike Beer
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=20131029164151.GA10616@alpha.franken.de \
--to=tsbogend@alpha.franken.de \
--cc=eike-kernel@sf-tec.de \
--cc=linux-parisc@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox