I got a segv trying to run ipmi-sensors (1.3.4). It may be relevant
that the system is somewhat unusual -- four (Bull) servers glued
together to make a large SMP box.
I don't have time to debug it properly, but here's a backtrace, although
it may be junk, given the top of the stack. I can send s
Al Chu writes:
> Hi Dave,
>
> Huh ... I'm sorta at a loss. The state_data->prog_data data structure
> is pretty core. It's set once near the beginning in main and never
> written to again once the main code is executed,
The stack trace did suggest something had stomped on it. I'll try to
find
Albert Chu writes:
> Another thought, did you recompile the source? I'm wondering if maybe
> there's a linking issue with wrong library versions or what not. I've
> seen that happen with other users before.
I just built and installed the rpm, and it works on other nodes using
the same NFS root
d, but the other three Ambients are the same.)
2013-12-19 Dave Love
* ipmi-sensors/ipmi-sensors.c (_calculate_record_ids): Check
record numbr against array length.
* common/toolcommon/tool-sensor-common.h (MAX_SENSOR_RECORD_IDS):
Increase to 1024.
--- freeipmi-1.3.4/common/toolcommon/t
"Liebig, Holger" writes:
>>
>> I realized that the system that caused the crash has 601 sensors; really.
>> Patch attached.
>>
>
> [Liebig, Holger]
> Out of curiosity: since the sensor number is limited to 8 bit are
> these 601 SDR grouped with satellite controllers or different LUN's?
> And m
Albert Chu writes:
> On Thu, 2013-12-19 at 11:56 +0000, Dave Love wrote:
>> I realized that the system that caused the crash has 601 sensors; really.
>> Patch attached.
>
> Well how about that :-)
I should have apologized for not looking properly to start with, as the
s
The bmc-watchdog init script currently has only RedHat conventions.
This patch against the 0.7.4 version makes it consistent with the
ipmidetectd, to work on SuSE.
[Please copy any replies to me, as I'm not on the list.]
2009-01-14 Dave Love
* bmc-watchdog/freeipmi-bmc-watchdog.init:
I tried `bmc-info -D LAN_2_0 -W sun20' on x4100s with both ILOM 1.0 and
2.0.2.5 (the latest as of a few months ago). It gives `password
invalid' in both cases. (With LAN, -W endianseq works with both the 1.0
and 2.0 ILOMs, but it doesn't help with LAN_2_0.)
Is --debug output the right thing to s
Al Chu writes:
> Hey Dave,
>
> It's entirely possible there is another issue for your systems I never
> encountered before or a bug in the workaround code. If you could send
> the --debug output, that'd be great.
OK, appended.
> Ipmitool also elects to "hide"
> workarounds in its tools more of
ther people here get newer kit with
it on.
2009-06-09 Dave Love
* common/man/manpage-common-workaround-text.man: Tweak the Sun
stuff.
*** manpage-common-workaround-text.man 08 Apr 2009 21:47:05 +0100 1.6
--- manpage-common-workaround-text.man 09 Jun 2009 14:40:00 +0100
*
Al Chu writes:
> Hey Dave,
>
> Thanks for some of the clarifications. I'd like to keep the ordering
> the same b/c it's actually split up IPMI 1.5 vs. IPMI 2.0.
Ah, that wasn't immediately obvious.
> And some of the text was from folks at Sun. So I've done the below
> patch instead. Look goo
Al Chu writes:
> Hey Dave,
>
> Whew, I'm glad I have a relatively new sun board, this would have been
> tough to figure out :-)
Good. I could have offered to let you on here.
> Effectively, the "opensesspriv" workaround is also needed for the Sun
> boards. I've wrapped that workaround in as a
Al Chu writes:
> Hehe. It's funny you mention this. I had a request/comment on this
> topic just last week. First, please take a look at my original post on
> this for what I was thinking of supporting:
>
> http://www.mail-archive.com/freeipmi-devel@gnu.org/msg00710.html
For what it's worth,
Al Chu writes:
> A. Ok ... then in that case I should put:
>
> "Sun Fire 2200/4150/4450 with ELOM"
>
> I didn't understand that it was an ELOM thing.
I can't actually demonstrate that on the other systems, but I think it
must be the case; I assume ELOM has the same lan bugs on any system th
Al Chu writes:
> Actually, it seems the sun20 workarounds are working correctly. You are
> able to authenticate. The problem is ...
Yes. I was only meaning to say that the SOL seems to be broken.
>> # ipmiconsole -h ipmi101 -Wsun20
>> [error received]: SOL unavailable
>
> This typically mea
Al Chu writes:
> A. I take it you are using the hostrange feature as a "go get data
> faster" mechanism. I suppose I was thinking more about the
> buffer/consolidate options (-B, -C). Using them against a heterogenous
> environment didn't make too much sense to me.
Right. I have a script
Al Chu writes:
> Hey Dave,
>
>> Ah. solpayloadsize,sun20 did establish a connexion, but I think the
>> speed may be wrong as it appears dead once connected. On the other
>> hand, after disconnecting, that seems to have taken the ILOM off the
>> air... That is with the earliest ILOM, anyway, th
"Johnson, Bill" writes:
> I would be interested in any thoughts or comments back.
Like you're rudely abusing a GNU mailing list by advertising proprietary
software? I have conman (and others).
___
Freeipmi-devel mailing list
Freeipmi-devel@gnu
Solaris 10's cp doesn't have -d. This is against 0.8.4 source.
2010-04-30 Dave Love
* ipmi-pef-config/src/Makefile.am (install-exec-hook): Don't use
`cp -d'.
--- Makefile.am 2010/04/30 14:40:39 1.1
+++ Makefile.am 2010/04/30 14:41:04
@@ -78,4 +78,4 @@
install-exec-
Al Chu writes:
> Hey Dave,
>
> Actually, the patch broke things on Linux.
Sorry, I don't know what I was thinking that the two things were
equivalent. I'm obviously displaying a lack of sleep.
> After looking around, a
> suggestion on line was made to only create the link on install time
> rat
There's some runaway emboldening.
--- bmc-watchdog.8 2010/05/05 14:20:49 1.1
+++ bmc-watchdog.8 2010/05/05 14:21:07
@@ -93,7 +93,7 @@
.TP
\fB\-t\fR, \fB\-\-start\fR
Start BMC Watchdog Timer. Does nothing if the timer is currently
-running. Identical to \fB\-\-reset command when th
Frank Steiner writes:
> Al Chu wrote
>
>> Hi Frank, Dave,
>>
>> I finally got around to trying to develop that workaround into BMC
>> watchdog to get around the issue on the Sun motherboards you have. Do
>> you think you guys could try it out and make sure it works for you?
>>
>> http://ftp.gl
Al Chu writes:
> (Naturally, I added "confirmed to work around" based on the assumption
> you guys can confirm it for me :-)
I can't confirm it on either x4100 -- not x4100m2 -- (RedHat 5) or x4500
(Solaris). In each case, the daemon reports:
timer stopped by another process
stopping bmc-w
Frank Steiner writes:
> Seems to work fine on my X4100 M2 machines :-) Starts up, reports status
> correctly, resets etc.
Does it actually run indefinitely, though? I just realize I gave
incomplete info, as I see it work for a few cycles. Here's a sample of
the logged events with -e 60:
[J
Al Chu writes:
> Hmm. I don't know much about the openipmi kernel driver, but I know it
> can have it's own bmc-watchdog running. Are you sure it's not running
> it's own watchdog out of the kernel?
Oh, yes, there's an ipmi_watchdog module, but it's not loaded on my
GNU/Linux systems, and the
[Sorry, I thought I sent this earlier, but I'm harassed and losing
track.]
Al Chu writes:
> --- bmc-watchdog.c 16 Jun 2010 17:52:38 - 1.131
> +++ bmc-watchdog.c 17 Jun 2010 23:18:57 -
> @@ -1920,6 +1920,8 @@ _daemon_cmd (void)
> && reset_period < (retry_wait_ti
Al Chu writes:
>> says ps, where I need the -D on x4100 or x4200m2 to avoid
>>
>> bmc-watchdog: Get Watchdog Timer Error: BMC Busy
>
> Yeah, I'm certainly unsure of that one. Have you tried running w/o the
> IPMI kernel driver? I'm wondering if they don't together for you (don't
> work tog
Delayed reply I thought I'd sent:
Al Chu writes:
>> says ps, where I need the -D on x4100 or x4200m2 to avoid
>>
>> bmc-watchdog: Get Watchdog Timer Error: BMC Busy
>
> Yeah, I'm certainly unsure of that one. Have you tried running w/o the
> IPMI kernel driver? I'm wondering if they don't
I thought I'd replied to this before...
Albert Chu writes:
> Just want to clarify, you're saying this sleep(5) makes it work on the
> 4100?
Yes, to the limited extent I tested it, as I'm not interested in running
it on x4100. However, it seemed to be running on the x4500 initially,
with a simi
Albert Chu writes:
> Hey Dave, Frank,
>
> As discussed in the previous thread, there was a corner case in the
> bmc-watchdog workaround I previously did. I then discovered another
> corner case w/ the workaround.
>
> There is a new beta here.
That seems to run OK on my x4500 under Solaris -- th
Frank Steiner writes:
> sorry, I was away, but I'm going to test the new beta now. During my
> absense the Sun X4100M2 produced two strange things:
For what it's worth, the beta has been running OK on my x4500 for about
a week now with no restarts.
> Btw, Sun first refused to develop a firmware
Albert Chu writes:
> On the flip side, I've personally never tested on Solaris. So who knows
> if the "/dev/bmc" was really programmed correctly. I may have screwed
> up.
Well the watchdog daemon has been running OK since June 29 on my Solaris
system with the test freeipmi. I could potentiall
Frank Steiner writes:
> I think I have misunderstood your reply to Dave. I thought that the sun BMCs
> had general problems whenever the kernel modules are loaded.
I can't now remember what the problems were originally, or even whether
they were specific to Solaris (which is where I was interest
I assume this is what's intended:
2011-09-22 Dave Love
* bmc-device/bmc-device.8.pre.in: Fix typos.
Index: bmc-device/bmc-device.8.pre.in
===
--- bmc-device/bmc-device.8.pre.in (revision 7872)
+++ bmc-devic
On a current Red Hat 5 system I get a checksum mismatch:
$ wget
http://download.gluster.com/pub/freeipmi/1.0.7/freeipmi-1.0.7-1.src.rpm
--2011-10-11 14:22:18--
http://download.gluster.com/pub/freeipmi/1.0.7/freeipmi-1.0.7-1.src.rpm
Resolving download.gluster.com... 70.38.57.57
Connecti
Kaiwang Chen writes:
> Guess it's related to rpm version or something. I experienced many
> times with SRPMs from DAG repository. I just add --nomd5 to rpm
> command.
Ah, thanks. That may be useful, but not for rpmbuild. It does work to
rpm -i the srpm, rather than having to rpm2cpio.
___
Albert Chu writes:
> Hey Dave,
>
> Hmmm. I'm not entirely sure what the problem may be. RH5 vs RH6
> incompatability is a reasonable guess.
>
> If you download the tar.gz and instead do
>
> rpmbuild -ta freeipmi-1.0.7.tar.gz
>
> does that work for you?
Yes, it's just the srpm that I had a prob
37 matches
Mail list logo
