On Tue, 2010-06-01 at 13:12 -0700, Frank Steiner wrote: > Al Chu wrote > > > Hi Frank, > > > > This sounded familiar. There is this thread for not too long ago. > > > > http://*lists.gnu.org/archive/html/freeipmi-users/2010-05/msg00017.html > > Doh, I searched for the wrong keywords in the archive :-)
It happens to all of us :-) > Yes, that's the same bug and if I get Dave's mail right he is seeing > the bug on the X4500 and X4200. If it's a X4200M2, it has the same > firmware as the X4100M2, and for this one the bug is not fixed in > the recent update. > > > Same applies. I can give a patch a shot, and you can try it out?? It > > Of course I could, but I agree with you that it wouldn't be a good thing. Ok, when I get a chance, I'll try to come up with something. > I can work without the daemon of course and use cron and a endless > while-loop to reset the timer, and I guess that's better than patching > around such an obvious bug. > I succeeded in triggering the bug without the bmc-watchdog by just > accessing the watchdog remotely via "ipmi <machine> ... mc watchdog > get/reset". > Thus, Sun has no chance argueing it is some Linux problem with freeipmi etc. > And since we still have support for the X4100M2 I will demand a firmware > upgrade. Let's see what they do. > > I just wanted to make sure there was an obvious workaround that I missed :-) > Thanks! And I will let you know what comes out of the Sun support request! Thanks. PLMK what comes about the request, so I can update my documentation. Al > cu, > Frank > > > -- Albert Chu [email protected] Computer Scientist High Performance Systems Division Lawrence Livermore National Laboratory _______________________________________________ Freeipmi-devel mailing list [email protected] http://lists.gnu.org/mailman/listinfo/freeipmi-devel
