freeipmi-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Freeipmi-devel] ipmi-sensors crash


From: Al Chu
Subject: Re: [Freeipmi-devel] ipmi-sensors crash
Date: Wed, 18 Dec 2013 08:06:16 -0800

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 problem for your unique system.

For kicks, another fellow on the mailing recently had a segv problem and
it appeared it was related to this.  Possible for you too?

http://www.gnu.org/software/freeipmi/freeipmi-faq.html#Why-am-I-seeing-so-many-_0027internal-IPMI-error_0027-or-_0027driver-busy_0027-messages_003f

Al

On Wed, 2013-12-18 at 15:02 +0000, Dave Love wrote:
> 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 specific info
> that might be useful.  The --debug output is 120k compressed, so I
> haven't attached it.
> 
> (gdb) bt
> #0  0x00000000004050be in _calculate_record_ids (state_data=0x7fffffff4e10)
>     at ipmi-sensors.c:485
> #1  _display_sensors (state_data=0x7fffffff4e10) at ipmi-sensors.c:1162
> #2  0x0000800400008003 in ?? ()
> #3  0x00007fff00008005 in ?? ()
> #4  0x00000000006371b0 in ?? ()
> #5  0x00007fffffff5100 in ?? ()
> #6  0x0000000000000000 in ?? ()
> (gdb) l
> 480                                  "ipmi_sdr_parse_record_id_and_type: 
> %s\n",
> 481                                  ipmi_sdr_ctx_errormsg 
> (state_data->sdr_ctx));
> 482                 return (-1);
> 483               }
> 484   
> 485             if (state_data->prog_data->args->exclude_record_ids_length)
> 486               {
> 487                 int found_exclude = 0;
> 488                 
> 489                 for (j = 0; j < 
> state_data->prog_data->args->exclude_record_ids_length; j++)
> (gdb) p *state_data->prog_data->args
> Cannot access memory at address 0x7fff0000800d
> (gdb) p *state_data->prog_data
> Cannot access memory at address 0x7fff00008005
> (gdb) p *state_data
> $1 = {prog_data = 0x7fff00008005, ipmi_ctx = 0x6371b0, 
>   pstate = 0x7fffffff5100, hostname = 0x0, sdr_ctx = 0x637bd0, 
>   sensor_read_ctx = 0x648050, interpret_ctx = 0x0, output_headers = 0, 
>   column_width = {record_id = 5, sensor_name = 15, sensor_type = 23, 
>     sensor_units = 5}, oem_data = {manufacturer_id = 0, product_id = 0, 
>     ipmi_version_major = 0 '\000', ipmi_version_minor = 0 '\000'}, 
>   intel_node_manager = {node_manager_data_found = 0, 
>     nm_health_event_sensor_number = 0 '\000', 
>     nm_exception_event_sensor_number = 0 '\000', 
>     nm_operational_capabilities_sensor_number = 0 '\000', 
>     nm_alert_threshold_exceeded_sensor_number = 0 '\000'}}
> _______________________________________________
> Freeipmi-devel mailing list
> address@hidden
> https://lists.gnu.org/mailman/listinfo/freeipmi-devel
-- 
Albert Chu
address@hidden
Computer Scientist
High Performance Systems Division
Lawrence Livermore National Laboratory




reply via email to

[Prev in Thread] Current Thread [Next in Thread]