Albert Chu ch...@llnl.gov writes:
On Thu, 2013-12-19 at 11:56 +, 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
stack had been
Ping me after the new year and we can look at it more. I'd like to see
the debug output of a --bridge-sensors with one of those ambient
sensors.
That's the one I expected to work. Not what's going on. Could be some
subtle bug ... or possibly an internal timeout or something.
Al
On Fri,
I realized that the system that caused the crash has 601 sensors; really.
Patch attached.
The sensors are still showing N/A, though. --debug output for one of
them also attached. The normal output for it is:
ID | Name | Type| Reading| Units | Event
4233 | Ambient Temp. |
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 models the SDR the
complete SMP Box with
Liebig, Holger holger.lie...@ts.fujitsu.com 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
On Thu, 2013-12-19 at 11:56 +, Dave Love wrote:
I realized that the system that caused the crash has 601 sensors; really.
Patch attached.
Well how about that :-)
The sensors are still showing N/A, though. --debug output for one of
them also attached. The normal output for it is:
ID
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, which may include
threads if you're doing hostranges. Dunno if the threading could be
part of the
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.
Al
On Wed, 2013-12-18 at 21:40 +, Dave Love wrote:
Al Chu ch...@llnl.gov writes:
Hi Dave,
Huh ...
