Hi Stephane
One of our customers has reported that they get a kernel oops any time they
halt or shutdown nodes in their cluster. They tracked the problem back to
the
routine pfm_cpu_notify (in source file perfmon_hotplug.c).
They believe that the code:
/* call PMU module handler if any */
if (pfm_pmu_conf->hotplug_handler)
pfm_pmu_conf->hotplughandler(action,cpu)
is executed when pfm_pmu_conf is null. They have made the following
change:
/* call PMU module handler if any */
if (pfm_pmu_conf != NULL && pfm_pmu_conf->hotplug_handler )
pfm_pmu_conf->hotplughandler(action,cpu)
and retested and the kernel oops no longer occurs.
We are running with the 2.6.28 perfmon patch set but I checked and the code
is the same
in the 2.6.29 patch set. The 2.6.29 perfmon patches were not available
when we built the
kernel they are running. I now have the 2.6.29 perfmon patches ready to be
included in
Bull's next kernel build.
This change looks like a safer way to do this code to me, what do you think
??
Thanks
Gary
------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
perfmon2-devel mailing list
perfmon2-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/perfmon2-devel
