* nodes in the cluster that don't have this bug.
Thanks!
Eric
On Fri, 2008-11-07 at 09:35 -0600, Corey Minyard wrote:
Can you try the following patch? I had a report of a similar problem
and this fixed it.
-corey
[elided
Eric J. Bowersox wrote:
On Fri, 2008-11-07 at 15:42 -0600, Corey Minyard wrote:
Maybe you are connecting to a different system over the LAN. The
easiest way to tell for sure would be to use the GUID, if your system
supports that.
I modified my test program to get the GUID from
Rather bizarre.
It's supposed to return the same information. I can think of three
things...
Maybe you are connecting to a different system over the LAN. The
easiest way to tell for sure would be to use the GUID, if your system
supports that.
It's a bug in the OpenIPMI. I kind of doubt
filename:
/lib/modules/2.6.16.46-x/kernel/drivers/char/ipmi/ipmi_si.ko
description:Interface to the IPMI driver for the KCS, SMIC, and BT
system interfaces.
author: Corey Minyard [EMAIL PROTECTED]
license:GPL
srcversion: 291DA36982724B8C82BE809
alias
Someone reported a bug, and I'm waiting on a response from that before
releasing the 2.6.25 patches. They are ready to go beyond that.
-corey
Carol Hebert wrote:
Cress, Andrew R wrote:
Corey,
Thanks. I had only tested it on 2.6.14 and earlier kernels, so it
does
need to be
Just a note, this patch is now in the mainstream kernel.
-corey
Nate Case wrote:
The current OF probing assumes that the resource is IORESOURCE_MEM.
This checks for the IORESOURCE_IO flag and behaves appropriately.
An I/O resource can exist with an ipmi device node on a legacy ISA bus.
Please ask this on the ipmitool list, you are much more likely to get
answers.
-corey
Lukasz Michalski wrote:
Hi,
I have FSC-1501 motherboard and ipmi does not detect fans RPM here.
Is there any way to make it work?
Here is a log from ipmi-si initialization:
-by: Corey Minyard [EMAIL PROTECTED]
---
drivers/char/ipmi/ipmi_si_intf.c | 10 --
1 file changed, 8 insertions(+), 2 deletions(-)
Seems reasonable to me, though I have no way to test this. -corey
Index: linux-2.6.25/drivers/char/ipmi/ipmi_si_intf.c
Signed-off-by: Robert P. J. Day [EMAIL PROTECTED]
Signed-off-by: Corey Minyard [EMAIL PROTECTED]
Index: linux-2.6.24/include/linux/ipmi.h
===
--- linux-2.6.24.orig/include/linux/ipmi.h
+++ linux-2.6.24/include/linux/ipmi.h
@@ -64,7
This patch makes the needlessly global ipmi_alloc_recv_msg() static.
Signed-off-by: Adrian Bunk [EMAIL PROTECTED]
Signed-off-by: Corey Minyard [EMAIL PROTECTED]
Index: linux-2.6.24/drivers/char/ipmi/ipmi_msghandler.c
===
--- linux
Cress, Andrew R wrote:
Corey,
I ran into a case that required ipmi_imb and CONFIG_COMPAT, and ipmi_imb
did not previously support it, so I have attached the updated source
with those changes.
I included the source files since they are created by the patch anyway.
Any comments?
Could a form
to pull this patch in
soon?
Thank you very much for all your help, :-)
Well, we can try, but it might be a little late.
Andrew, could we get this patch pushed to the mainstream kernel?
-corey
Carol Hebert
On Wed, 2008-02-13 at 10:22 -0600, Corey Minyard wrote:
From: Carol Hebert
Andrew Morton wrote:
On Thu, 03 Apr 2008 16:30:18 -0800 Carol Hebert [EMAIL PROTECTED] wrote:
Hi,
This reverse enumeration scheme is actually different from how the ipmi
driver has worked in the past. The BMCs in multinode systems were
historically named by the ipmi driver in the order
Nathan Scott wrote:
On Mon, 2008-03-17 at 20:21 -0500, Corey Minyard wrote:
This shouldn't significantly affect performance. kipmid runs at nice
level 19, meaning that basically everything else is more important
than
it. It could be made a little bit lower priority by setting
You are correct about the ‘*/FRU fields did not occur in the correct
order/*’ error, that's the source of the problem.
Section 17 of the IPMI Platform Management FRU Information Storage
Definition document states: FRU Information areas always appear in this
order and then states the order. The
Mark Meyer wrote:
It may be that the driver
is unable to find the channel due to it not being reported properly when
getting the channel info.
Ah. This would explain things as this IPMC firmware does not
implement the GetChannelInfo command (returns invalid command). I did
wonder about
[EMAIL PROTECTED] wrote:
Hello,
I am developing a firmware upgrade utility and am having trouble
accessing my ARTM through the system interface via the openIPMI driver
interface. The ARTM has a site ID of 0x0f (IPMB address 0x8e) and sits
on IPMB-L. When specifying channel 7 for the
From: Corey Minyard [EMAIL PROTECTED]
Allow the serial codecs to pass up the IPMI slave address of the
BMC if they know about it.
Signed-off-by: Corey Minyard [EMAIL PROTECTED]
---
Index: linux-2.6.24/drivers/char/ipmi/ipmi_serial.c
Thanks, this is queued up to be sent in the 2.6.26 merge window.
-corey
Jesper Juhl wrote:
On 17/02/2008, Robert P. J. Day [EMAIL PROTECTED] wrote:
Signed-off-by: Robert P. J. Day [EMAIL PROTECTED]
Thank you Robert.
This patch is now on my 'watch list' for the 2.6.26 merge window.
Matt Domsch wrote:
On Thu, Feb 14, 2008 at 12:30:51PM -0600, Corey Minyard wrote:
From: Konstantin Baydarov [EMAIL PROTECTED]
Atomics are a lot more efficient and neat than using a lock.
per_cpu variables are a lot more efficient and neat than using locks
for simple statistics
Peter Zijlstra wrote:
On Thu, 2008-02-14 at 12:30 -0600, Corey Minyard wrote:
+/* The command didn't have anyone waiting for it. */
+#define IPMI_STAT_unhandled_commands23
+
+/* Invalid data in an event. */
+#define IPMI_STAT_invalid_events24
From: Corey Minyard [EMAIL PROTECTED]
Lots of style fixes for the base IPMI driver. No functional changes.
Basically fixes everything reported by checkpatch and fixes the comment
style.
Signed-off-by: Corey Minyard [EMAIL PROTECTED]
Patch is too big for the list, per the Submitting Patches
From: Corey Minyard [EMAIL PROTECTED]
Lots of style fixes for the miscellaneous IPMI files. No functional
changes. Basically fixes everything reported by checkpatch and fixes
the comment style.
Signed-off-by: Corey Minyard [EMAIL PROTECTED]
Patch is too big for the list, per the Submitting
Andrew Morton wrote:
On Wed, 13 Feb 2008 10:30:48 -0600
Corey Minyard [EMAIL PROTECTED] wrote:
Enough bug fixes and changes that we need a new driver version.
Are none of them serious enough to warrant a 2.6.24.x backport?
No, nothing really terribly urgent. Just minor stuff
From: Corey Minyard [EMAIL PROTECTED]
Change a barrier to cpu_relax(), which is more appropriate for a
polling loop.
Signed-off-by: Corey Minyard [EMAIL PROTECTED]
---
Index: linux-2.6.24/drivers/char/ipmi/ipmi_poweroff.c
From: Corey Minyard [EMAIL PROTECTED]
Remove some unnecessary barriers.
Signed-off-by: Corey Minyard [EMAIL PROTECTED]
---
This can be folded into ipmi-dont-grab-locks-in-run-to-completion-mode.patch
Index: linux-2.6.24/drivers/char/ipmi/ipmi_msghandler.c
From: Corey Minyard [EMAIL PROTECTED]
Atomics are faster and neater than locked counters.
Signed-off-by: Corey Minyard [EMAIL PROTECTED]
---
Index: linux-2.6.24/drivers/char/ipmi/ipmi_si_intf.c
===
--- linux-2.6.24.orig/drivers
Andrew Morton wrote:
+for (i = 0; i IPMI_NUM_STATS; i++)
+atomic_set(intf-stats[i], 0);
And this is why it would be very hard for any architecture to ever
implement atomic_t as
struct atomic_t {
int counter;
spinlock_t lock;
};
The interface assumes
Wow, that system had been up a long time.
I can't use the patch as-is, as this code has been rewritten recently to
use atomics, but this needs to be fixed in several places. I'll work on
a patch for this.
Thanks,
-corey
Nathan Scott wrote:
Hi there,
I came across some negative values in
]
Signed-off-by: Corey Minyard [EMAIL PROTECTED]
---
--- linux-2.6.24.orig/drivers/firmware/dmi_scan.c 2008-01-30
11:21:55.0 -0800
+++ linux-2.6.24/drivers/firmware/dmi_scan.c2008-01-30 11:18:05.0
-0800
@@ -219,7 +219,7 @@ static void __init dmi_save_ipmi_device(
dev
From: Corey Minyard [EMAIL PROTECTED]
The run_to_completion mode was somewhat broken. Locks need to be
avoided in run_to_completion mode, and it shouldn't be used by normal
users, just internally for panic situations.
This patch removes locks in run_to_completion mode and removes the
user call
From: Corey Minyard [EMAIL PROTECTED]
Hold handling of ATTN until the upper layer has reported that it is
ready.
Signed-off-by: Corey Minyard [EMAIL PROTECTED]
Cc: Patrick Schoeller [EMAIL PROTECTED]
---
Index: linux-2.6.24/drivers/char/ipmi/ipmi_si_intf.c
From: Konstantin Baydarov [EMAIL PROTECTED]
Atomics are a lot more efficient and neat than using a lock.
Signed-off-by: Konstantin Baydarov [EMAIL PROTECTED]
Signed-off-by: Corey Minyard [EMAIL PROTECTED]
---
Index: linux-2.6.24/drivers/char/ipmi/ipmi_msghandler.c
From: Corey Minyard [EMAIL PROTECTED]
Atomics are faster and neater than locked counters.
Signed-off-by: Corey Minyard [EMAIL PROTECTED]
---
Index: linux-2.6.24/drivers/char/ipmi/ipmi_si_intf.c
===
--- linux-2.6.24.orig/drivers
Andrew Morton wrote:
The code forgot to initialise all of these.
It just so happens that the all-bits-zero pattern works correctly for all
current architectures, so the code should work OK. But there is no reason
(I hope) why an architecture cannot implement atomic_t as
struct atomic_t {
Andrew Morton wrote:
On Wed, 13 Feb 2008 10:23:42 -0600
Corey Minyard [EMAIL PROTECTED] wrote:
From: Corey Minyard [EMAIL PROTECTED]
The run_to_completion mode was somewhat broken. Locks need to be
avoided in run_to_completion mode, and it shouldn't be used by normal
users, just
-0800
To:
Corey Minyard [EMAIL PROTECTED]
To:
Corey Minyard [EMAIL PROTECTED]
CC:
openipmi-developer@lists.sourceforge.net
On Fri, 2008-01-18 at 22:47 -0600, Corey Minyard wrote:
If we take this patch, can you send this in standard patch format with a
patch header and signed-off
Jonathan Fournier wrote:
Hi,
I have a question regarding the ipmi_poweroff module use on ATCA blades.
What is supposed to be the behavior of an ATCA blade running Linux
with the ipmi_poweroff module loaded when the handles are pulled to
trigger an hotswap event?
Is ipmi_poweroff is
Matt Domsch wrote:
On Tue, Jan 22, 2008 at 06:50:31AM -0600, Matt Domsch wrote:
On Mon, Jan 21, 2008 at 09:40:59AM +0800, william cheng wrote:
Dear all,
We got some problem on modprobing the ipmi_si module on Dell
Power Edge 2600.
I've asked someone to look into
If we take this patch, can you send this in standard patch format with a
patch header and signed-off-by line? I'll need that to send it on.
However, I think there is another way to handle this. udev should be
able to order these however you like. You should be able to use the
device ID from
Bugs have been fixed in this code that might solve the problem. Is
there any way you can try a newer version of the library?
-corey
Dejan Muhamedagic wrote:
Hi,
This is on a openSUSE 10.3 and ipmi is:
OpenIPMI-devel-2.0.7-102
The backtrace:
Thread 1 (process 8787):
#0 0x in
, 2008 at 09:58:42AM -0600, Corey Minyard wrote:
Bugs have been fixed in this code that might solve the problem. Is there
any way you can try a newer version of the library?
Tried with the latest (2.0.13) from sourceforge. The same thing:
Thread 1 (process 12048):
#0 0x
The openipmi_conparms(7) man page defines this.
You can also do openipmish or ipmish and do help domain open for
information. There are a host of parameters, unfortunately.
For your particular configuration, you would do ./sample lan -P
password -H intelplus 10.10.12.25 The parameters are not
Jonathan Fournier wrote:
Hi there,
I have a question regarding an older revision of the serial IPMI
driver and the latest one.
From that patch:
http://osdir.com/ml/linux.kernel.openipmi/2006-06/msg4.html
http://osdir.com/ml/linux.kernel.openipmi/2006-06/msg4.html
I see that the
David Jenkins wrote:
I tried the following:
domain open fred -noipmbscan -noseteventrcvr smi 0
Still does a scan and doesn't find any FRU or SDR. I also tried
domain open domain0 -sdrs -frus -noipmbscan -noseteventrcvr smi 0
Also runs the channel scans and I believe no fru or sdr scans.
Well, localonly appears to be broken.
You can use -noipmbscan -noseteventrcvr to accomplish the same thing,
though. I'll fix the problem.
-corey
David Jenkins wrote:
I have an ATCA boad with a pigion point IPMC on board to connect to
the SHMC. The payload processor is a 8548 connected to
I'm not exactly sure what this means, where did you get this code? A few
notes here:
* ipmi_sensor_get_normal_min gets a double value, so you should
really be comparing with floating point values.
* 0 (or really 0.0) and negative values are valid sensor minimums.
* 0 (or 0.0, I
[EMAIL PROTECTED] wrote:
Here is my revision, but the results remain the same:
double sensorMin = 0.0;
if (!ipmi_is_sensor_scanning_enabled(states)) {
// Print Scanning disabled.
}
else if (ipmi_sensor_get_normal_min_specified(sensor)
0 == ipmi_sensor_get_normal_min(sensor,
[EMAIL PROTECTED] wrote:
Can OpenIPMI attempt multiple authentication methods for me?
Here is the scenario: I am using a certain privilege level and I set
up a connection with a particular authentication level (e.g. MD5). It
connects but has read errors (domain change handler has a read
be included as an example in the OpenIPMI package.
-corey
mvtrm_ipmi_resetter - External resource manager plugin for resetting
via IPMI
:version: 1.0.0
:author: Corey Minyard [EMAIL PROTECTED]
:organization: MontaVista Software
:copyright: Copyright 2007 MontaVista Software, Inc. All rights
From: Corey Minyard [EMAIL PROTECTED]
Add the standard IOCTLs to the IPMI driver for setting and getting
the pretimeout. Tested by Benoît Guillon.
Signed off by: Corey Minyard [EMAIL PROTECTED]
Cc: Benoît Guillon [EMAIL PROTECTED]
---
Index: linux-2.6.23/drivers/char/ipmi/ipmi_watchdog.c
value? BTW, is there a way to
change the timeout action (reset, etc.)?
Thanks,
Add the standard IOCTLs to the IPMI driver for setting and getting
the pretimeout.
Corey Minyard [EMAIL PROTECTED]
Index: linux-2.6.23/drivers/char/ipmi/ipmi_watchdog.c
A patch propagation was missed. The following patch should fix the
problem. The MPSC driver gets initialized multiple times, it appears,
and the driver has to ignore all but the first.
-corey
Prevent the console from being enabled twice.
Signed-off-by: Corey Minyard [EMAIL PROTECTED
that patch?
http://osdir.com/ml/linux.kernel.openipmi/2006-06/msg3.html
On Nov 9, 2007 3:58 PM, Corey Minyard [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED] wrote:
I'm not really sure. That actually hasn't been tested in its current
form, the patch was ported from something else
): Outgoing data: 5b([) 31(1) 38(8) 30(0) 30(0) 30(0)
31(1) 5d(]) 0a( )
ipmi_serial(ttyS4): codec initialization timed out, interface is not
usable
For serial terminal mode, send a carraige return along with the line
feed in case some systems need this.
Signed-off-by: Corey Minyard [EMAIL PROTECTED
would conflict. You can't have both (and there's not much
reason for both).
That doesn't explain the EINVAL error, though.
-corey
/jonathan
On Nov 7, 2007 12:49 PM, Corey Minyard [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED] wrote:
Jonathan Fournier wrote:
Oh but one other thing
You didn't provide very much information. What software did you use to
try to talk to it? What did it print? Why do you think you can get the
RAID controller status from the BMC (what do the docs say about it)?
I don't know anything about this system, but people from Intel do
subscribe to
I assume you tried the ppInvIANA option, too.
There is a debug option in the ipmi_serial module, try setting debug=7
and generate output.
I think I can get access to a 7101, I'll try it out. This hasn't been
tested on a 7101 yet.
-corey
Jonathan Fournier wrote:
Hi,
I'm using the
, Corey Minyard [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED] wrote:
Jonathan Fournier wrote:
I get this:
[EMAIL PROTECTED]:/root /etc/init.d/ipmi start
Starting ipmi drivers: Nov 6 20:29:00 localhost kernel: ipmi
message
handler version 39.1
Nov 6 20
-corey
Jonathan Fournier wrote:
I added the patch, it's not complaining that the option doesn't
exists, bit it stills time out...
How do I enable debug=7 ?
/jonathan
On Nov 6, 2007 4:17 PM, Corey Minyard [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED] wrote:
Jonathan Fournier wrote
Some versions of boards with PigeonPoint IPMI controllers have the
IANA numbers backwards in the OEM-specific commands. This patch adds
the ability to auto-detect this problem and to allow options to set
this.
Signed-off-by: Corey Minyard [EMAIL PROTECTED]
Index: linux-2.6.21/drivers/char/ipmi
outputs from /var/log/messages ?
On Nov 6, 2007 5:14 PM, Corey Minyard [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED] wrote:
BTW, I couldn't get access to a 7101, but if you can give me access I
could hack on it a little.
-corey
Jonathan Fournier wrote:
I added the patch
David Jenkins wrote:
I need to set non-default values for the KCS address, spacing, size,
and shift in ipmi_si_intf.c. I see that there are module params set
up to do this. However, I am compiling ipmi_si_intf.c into the
kernel not loading it as a module. Is there a way to set module
Yes, it's a problem, but wrong fix. Thanks, I'll send a patch for it.
-corey
Adrian Bunk wrote:
This patch removes obviously dead code spotted by the Coverity checker.
Signed-off-by: Adrian Bunk [EMAIL PROTECTED]
---
include/linux/ipmi_smi.h | 10 ++
1 file changed, 2
This release contains various bug fixes and cleanups. The only new feature is
adding 0.9 support. It is available at http://openipmi.sf.net
A major rework has been done to the SMBus (SSIF) driver. It is now quite stable
and works well. A significant change is philosophy was made to the driver
So you have a SAN/NAS on the network that has an IPMI interface, is that
correct?
Anyway, you have some OEM commands. You can send them directly with
ipmi_mc_send_command(). Or you can create OEM sensors/controls to
control them. The direct messages is definitely the simplest, but it
does
. Patch is in your sources and
currently running, but not installed in /lib/modules.
-corey
Stian Jordet wrote:
On tir, 2007-10-02 at 14:51 -0500, Corey Minyard wrote:
There is a big difference between the driver, which just passes messages
around mostly, and the sensor handling, which requires
with it) and I can get sensor readings (altough not
readable...). Although both fru and health commands quits with an
error message.
But, most important for me; getting sensor-readings human readable. In
one form or another. So far I have made these observations:
Corey Minyard wrote
The OpenIPMI library doesn't print anything, it goes through the log
interface and the application using the library prints it. The logs are
classified by type/severity, so you can easily suppress info type
messages in your application. The provided sample UIs print everything
by default, but
can't really tell you how, as that's
your code :).
-corey
Thanks
-Barani
Subject:
Re: [Openipmi-developer] How to avoid log messages display in the screen
From:
Corey Minyard [EMAIL PROTECTED]
Date:
Thu, 27 Sep 2007
baranidharan wrote:
Hii all,
In my application , i have the logging facility for the printf()
statemet , wherever i put
printf() statemet , that staemet write in to the my own log file, but i
am not able
write the OpenIPMI log messges (ipmi_log) in to my own log file , it's
directly
This is all OEM-specific and there is no standard for it. No one has
implemented any code in OpenIPMI to do this. All OpenIPMI could do for
you, at least at this point, is route messages to/from the server.
If you can get the information required and write the software, it is
possible to
baranidharan wrote:
Hii all,
How to implement the virtual media concept using Openipmi API.
Can you send me a run with --drawmsg run with openipmicmd?
Some BMCs will simply not respond to an invalid command instead of
returning an error code. OpenIPMI thinks it has lost a connection when
this occurs. This is, of course, a violation of the spec, but needs to
be accounted for. I'm
I think he's asking for the equivalent of ipmilan on Windows. That's a
tool that runs on the host and provides an IPMI LAN interface through
the host. I used this for testing before I had a system that had a real
LAN interface, and it became the IPMI simulator.
ipmilan is primarily for
The OpenIPMI library does not block except in cases where it calls
standard library functions that block. I believe the only instance of
that is name resolution (gethostbyname and friends).
The library is designed to always call a supplied callback if the
function that takes the callback does not
Deepak Gaur wrote:
Hi all,
I have following hardware configuration based on Pigeon Point BMC
PowerPC MPC8560 SCC --UARTIPMI Serial Interface(Terminal
Mode)BMR-AVR BMC
As I am not much aware about IPMI I shall be grateful if anyone can clear my
doubts
Software Available
the initial message, second
paragraph). Ipmitool finds states for these sensors so something is not
quite right. These sensors are in fact OEM; is there a different set of
state functions that I need to use for OEM?
Thanks again,
Jen
-Original Message-
From: Corey Minyard [mailto
[EMAIL PROTECTED] wrote:
# rpm -qa | grep -i ipmi
OpenIPMI-2.0.7-35.10
OpenIPMI-devel-2.0.7-35.10
ipmidrvr-2.6.9.42.ELsmp-15
ipmitool-1.8.9-2.7
ipmiutil-1.9.8-1
Ok, same as me.
ipmitool:
SMI Timeout | 85h | ok | 7.1 | State Deasserted
OpenIPMI (let me know if you want to see my
it
to a multi-indexed array in order to get that string. However, you'd
understand their code better than I, so I'll take your word for it :)
Thanks again for your help,
Jen
-Original Message-
From: Corey Minyard [mailto:[EMAIL PROTECTED]
Sent: Friday, July 27, 2007 2:54 PM
See the function read_sensor_states() in cmdlang/cmd_sensor.c. It gets
a reading and iterates through it. You really shouldn't be directly
using ipmi_get_reading_name(), you should use
ipmi_sensor_reading_name_string(). If there are OEM plugins that modify
these values, they may not exactly
[EMAIL PROTECTED] wrote:
Hii all,
ipmi_domain_close(domain, close_timeout, tmp_obj);
using the above function i am closing the lan connection, whether it stop,
the running operation_loop (os_hnd-operation_loop(os_hnd);)
You don't need to close and re-open the domain. First of all,
Well, this program has a race condition, because there is no guarantee
that ipmi_init() in first_thread runs before second_thread(). You
should alloc the os handler and call ipmi_init() in the main routine and
first_thread should just call the operation loop. I'm surprised the
program
[EMAIL PROTECTED] wrote:
Hii all,
Accessing SDRs for a system, i am using below code, whether it will give
SDRs information in a
system
//mycode.c
ipmi_sdr_info_t *sdrs;
rv = ipmi_sdr_info_alloc(domain, NULL, 0, 0, sdrs);
ipmi_sdr_fetch(sdrs, sdrs_fetched, tmp_obj);
Commands like help sensor will be quite handy. There are commands to
list all the sensors and get their current values, settings, etc.
-corey
[EMAIL PROTECTED] wrote:
Hii all,
using \'ipmish\' i want get the sensor related information pls give some
example.
Thanks
barani
[EMAIL PROTECTED] wrote:
Hii all,
int ipmi_mc_get_users(ipmi_mc_t *mc,
unsigned int channel,
unsigned int user,
ipmi_user_list_cb handler,
void *cb_data);
in the above
[EMAIL PROTECTED] wrote:
Hii all,
int ipmi_mc_get_users(ipmi_mc_t *mc,
unsigned int channel,
unsigned int user,
ipmi_user_list_cb handler,
void *cb_data);
Using the above
All those things are specific to an MC, some of them are specific to a
channel on an MC. So you have to do this on the right MC.
-corey
[EMAIL PROTECTED] wrote:
Hii all,
in a domain i have set of MCs.
The users, connection ,channel, are specfic to a MC (or) global to
The concept of parents and children is not the same as the entities
containment in the domain. Listing the entities in the domain will list
all of them, all parents and children. The parent/child relationships
are used to denote physical containment (like a memory chip being on a
memory
[EMAIL PROTECTED] wrote:
Hii all,
ipmi_domain_iterate_entities(domain,handle_entity,my_data);
Whether the above API will list all entities in the
domain?
Thanks,
barani
I will list all the entities in the domain at the time it is called.
When the domain is
[EMAIL PROTECTED] wrote:
Hii all,
the iterate function what is doing,
suppose my domian have the 10 entities ,whether it will call 10 times to the
handle_entity function
for different entity.pls tell me what this
\ipmi_domain_iterate_entities(domain, handle_entity,
[EMAIL PROTECTED] wrote:
Hii all,
using OpenIPMI API, i am going to get
remote (over the LAN) IPMI server hardware parameter
(like sensor details), anybody have sample code for
this,pls send me.
Using OpenIPMI API how to send request and receive response over LAN.
[EMAIL PROTECTED] wrote:
Hii all,
My requirement as follows,
from the localhost i am going to give the IPMI commands using OpenIPMI \
ipmicmd -k \\\f 0 4 2d 1\\\ lan 210.210.65.108 623 \\\none\\\
\\\user\\\ \\\uername\\\ \\\password\\\ \ to the remote IPMI enabled
server
(over the
I checked this out and it seems to work fine. This does seem a little
nicer than the way it was, so if this is the way the kernel is heading
I'll ack it.
-corey
Jan Engelhardt wrote:
Change Kconfig objects from menu, config into menuconfig so
that the user can disable the whole feature
David Jenkins wrote:
Corey,
Okay. I will go with OEM event.
Ok, thanks.
We received notification this week that Pigeon Point has implemented
hpm.1 (?) firmware upgrade method in their code.
They indicated that this is a true IPMI standard that others will be
using as well. I haven't
You are not trying to run OpenIPMI, you are trying to run ipmitool,
which is a different project. Please ask on that mailing list.
-corey
Rodrigo Ferreira Valentim wrote:
Hi.
I need to access IPMI from LAN in both Windows/Linux OS.
So I try to run OpenIpmi 1.8.9 in Ubuntu 7.0.4 and in
If you are using the SI driver, then there is nothing new that is not
already in Andrew's or Linus' kernel.
The SMB driver needs to be brought up to date, but that is just patch
monkeying.
The serial driver needs a lot of work. I could bring the current
version up to date, but that's not
That may be the case for OEM events (which have no standard defined MC)
or events from boards that are no longer in the system. If that's the
case, it's normal.
If the MC the event is from is still valid, then there's a problem. I
can't reproduce, it seems to work fine for me.
-Corey
Jesse
I haven't seen this problem, but it appears to be order related and
that's probably why I missed it.
I think the right answer is to move the call to uart_register_ldrv() out
of uart_configure_port() and move it into uart_add_one_port() after the
mutex-state is unlocked. However, I haven't
Ivánszky Gábor wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello,
I'm trying to use ipmi kernel driver on a HP Proliant ML110 G3.
As I see the latest openipmi supported kernel is 2.6.18, so I use a
2.6.18.8 (from kernel.org). I patched it with 2.6.18-v39.1 ipmi driver.
I got
801 - 900 of 979 matches
Mail list logo
