From: "Russell Johnson" <rjohnson@rtlogic.com>
To: linux-scsi@vger.kernel.org
Subject: megaraid battery status questions
Date: Thu, 9 Sep 2004 08:44:05 -0600 [thread overview]
Message-ID: <000701c4967b$747b7bd0$1e01a8c0@rtlogic.com> (raw)
I have been using the megaraid driver on a Dell system using the PERC4 for
several months now and have noticed that /proc/megaraid/hba0/battery-status
will report errors after reading it over time. If I reboot the system then
the battery status errors go away until I poll again. The BIOS for the
Megaraid doesn't report battery status errors in any of the tests I have
run. The errors I see include "low voltage" and "charge fail". In
addition, I have seen the same "errors" across several different systems so
it isn't just a single adapter or system that is failing.
My goal is to poll for both battery status and raid status on a periodic
basis (every 5 minutes or so). I have tried this on different kernels and
driver versions with the same result and I'm wondering if anyone else has
seen the same issue or found a solution. I started with a 2.4.21 kernel and
tried a 2.10.x driver. I'm currently running a 2.6.7 kernel with the 2.00.3
driver and the latest firmware I could find, dmesg reports "megaraid:
[350O:1.09]". I have written some code similar to recent posts with the
title "megaraid megaraid2-2.10.7 causing kernel panic" and it is reporting
the same failure on all of the above setups that I have tried. It seems
that the latest proper megaraid driver for kernel 2.6 versions might be the
2.20.3.1 version but it doesn't support the /proc files as the 2.0 and 2.10
drivers did. I'm not sure if the new driver supports the same ioctl I'm
using or not.
With my goal to poll raid status and battery status on a periodic basis,
does anyone have ideas on what mechanism I can use? Ioctl? Other programs?
I have also noticed that it seems that the megaraid mailbox will not accept
new commands while the inquiry3 command is being executed. Can anyone
verify that this is the case? I can't find any information on the command
and its limitations.
Thanks for any help!
Russ Johnson
next reply other threads:[~2004-09-09 14:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-09 14:44 Russell Johnson [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-09-13 13:07 megaraid battery status questions Mukker, Atul
2004-09-14 17:12 ` Russell Johnson
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='000701c4967b$747b7bd0$1e01a8c0@rtlogic.com' \
--to=rjohnson@rtlogic.com \
--cc=linux-scsi@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