Carol Hebert wrote: > Hi Corey, > > This latest patch worked great on my 2-node system! :-D I'll try to > get some time on a 4-node and 8-node system asap to test it out on them > as well. > > I've listed below how ipmi and the BMCs are now represented in sysfs. > Do you still want me to continue working on trying to get some unique > BMC device ID/GUID change made in the f/w as well (and in the process > find out what we have now ;-}? I'm also working on finding out whether > or not it's guaranteed that the BMCs are listed in node order in the > SMBIOS table. > It's probably best to get the unique device id in the firmware. That is the only sure way to know that a specific IPMI device maps to a specific node's BMC, and IMHO it's the right way to do things. > Thanks very much for your help and for making my day! :-D > You are welcome.
-Corey > Carol Hebert > > ------------ > > /sys/class/ipmi/ipmi1/device > /sys/class/ipmi/ipmi1/dev > /sys/class/ipmi/ipmi1/uevent > /sys/class/ipmi/ipmi1/subsystem > /sys/class/ipmi/ipmi0 > /sys/class/ipmi/ipmi0/device > /sys/class/ipmi/ipmi0/dev > /sys/class/ipmi/ipmi0/uevent > /sys/class/ipmi/ipmi0/subsystem > /sys/bus/pci/drivers/ipmi_si > /sys/bus/pci/drivers/ipmi_si/new_id > /sys/bus/pci/drivers/ipmi_si/bind > /sys/bus/pci/drivers/ipmi_si/unbind > /sys/bus/pci/drivers/ipmi_si/module > /sys/bus/platform/drivers/ipmi_si > /sys/bus/platform/drivers/ipmi_si/ipmi_si.1 > /sys/bus/platform/drivers/ipmi_si/ipmi_si.0 > /sys/bus/platform/drivers/ipmi_si/bind > /sys/bus/platform/drivers/ipmi_si/unbind > /sys/bus/platform/drivers/ipmi > /sys/bus/platform/drivers/ipmi/ipmi_bmc.0007.33 > /sys/bus/platform/drivers/ipmi/ipmi_bmc.0007.32 > /sys/bus/platform/drivers/ipmi/bind > /sys/bus/platform/drivers/ipmi/unbind > /sys/bus/platform/devices/ipmi_bmc.0007.33 > /sys/bus/platform/devices/ipmi_si.1 > /sys/bus/platform/devices/ipmi_bmc.0007.32 > /sys/bus/platform/devices/ipmi_si.0 > /sys/devices/platform/ipmi_bmc.0007.33 > /sys/devices/platform/ipmi_bmc.0007.33/ipmi1 > /sys/devices/platform/ipmi_bmc.0007.33/guid > /sys/devices/platform/ipmi_bmc.0007.33/aux_firmware_revision > /sys/devices/platform/ipmi_bmc.0007.33/product_id > /sys/devices/platform/ipmi_bmc.0007.33/manufacturer_id > /sys/devices/platform/ipmi_bmc.0007.33/additional_device_support > /sys/devices/platform/ipmi_bmc.0007.33/ipmi_version > /sys/devices/platform/ipmi_bmc.0007.33/firmware_revision > /sys/devices/platform/ipmi_bmc.0007.33/revision > /sys/devices/platform/ipmi_bmc.0007.33/provides_device_sdrs > /sys/devices/platform/ipmi_bmc.0007.33/device_id > /sys/devices/platform/ipmi_bmc.0007.33/driver > /sys/devices/platform/ipmi_bmc.0007.33/bus > /sys/devices/platform/ipmi_bmc.0007.33/subsystem > /sys/devices/platform/ipmi_bmc.0007.33/modalias > /sys/devices/platform/ipmi_bmc.0007.33/power > /sys/devices/platform/ipmi_bmc.0007.33/power/wakeup > /sys/devices/platform/ipmi_bmc.0007.33/power/state > /sys/devices/platform/ipmi_bmc.0007.33/uevent > /sys/devices/platform/ipmi_si.1 > /sys/devices/platform/ipmi_si.1/ipmi:ipmi1 > /sys/devices/platform/ipmi_si.1/bmc > /sys/devices/platform/ipmi_si.1/driver > /sys/devices/platform/ipmi_si.1/bus > /sys/devices/platform/ipmi_si.1/subsystem > /sys/devices/platform/ipmi_si.1/modalias > /sys/devices/platform/ipmi_si.1/power > /sys/devices/platform/ipmi_si.1/power/wakeup > /sys/devices/platform/ipmi_si.1/power/state > /sys/devices/platform/ipmi_si.1/uevent > /sys/devices/platform/ipmi_bmc.0007.32 > /sys/devices/platform/ipmi_bmc.0007.32/ipmi0 > /sys/devices/platform/ipmi_bmc.0007.32/guid > /sys/devices/platform/ipmi_bmc.0007.32/aux_firmware_revision > /sys/devices/platform/ipmi_bmc.0007.32/product_id > /sys/devices/platform/ipmi_bmc.0007.32/manufacturer_id > /sys/devices/platform/ipmi_bmc.0007.32/additional_device_support > /sys/devices/platform/ipmi_bmc.0007.32/ipmi_version > /sys/devices/platform/ipmi_bmc.0007.32/firmware_revision > /sys/devices/platform/ipmi_bmc.0007.32/revision > /sys/devices/platform/ipmi_bmc.0007.32/provides_device_sdrs > /sys/devices/platform/ipmi_bmc.0007.32/device_id > /sys/devices/platform/ipmi_bmc.0007.32/driver > /sys/devices/platform/ipmi_bmc.0007.32/bus > /sys/devices/platform/ipmi_bmc.0007.32/subsystem > /sys/devices/platform/ipmi_bmc.0007.32/modalias > /sys/devices/platform/ipmi_bmc.0007.32/power > /sys/devices/platform/ipmi_bmc.0007.32/power/wakeup > /sys/devices/platform/ipmi_bmc.0007.32/power/state > /sys/devices/platform/ipmi_bmc.0007.32/uevent > /sys/devices/platform/ipmi_si.0 > /sys/devices/platform/ipmi_si.0/ipmi:ipmi0 > /sys/devices/platform/ipmi_si.0/bmc > /sys/devices/platform/ipmi_si.0/driver > /sys/devices/platform/ipmi_si.0/bus > /sys/devices/platform/ipmi_si.0/subsystem > /sys/devices/platform/ipmi_si.0/modalias > /sys/devices/platform/ipmi_si.0/power > /sys/devices/platform/ipmi_si.0/power/wakeup > /sys/devices/platform/ipmi_si.0/power/state > /sys/devices/platform/ipmi_si.0/uevent > > > # ls -l /dev/ipmi* > crw------- 1 root root 252, 0 Oct 18 11:52 /dev/ipmi0 > crw------- 1 root root 252, 1 Oct 18 11:52 /dev/ipmi1 > > > On Tue, 2006-10-17 at 17:22 -0500, Corey Minyard wrote: > >> Corey Minyard wrote: >> >>>> Please let me know what I can do to help. In the meantime, I'll take a >>>> look at the current code and try to figure out why it's still oopsing. >>>> >>>> >>> I thought the oops was fixed. If not, can you send one? >>> >>> As far as things you can do, I'm not really sure. I don't have enough >>> details on how this hardware works to design a solution. This is really >>> nitty-gritty detail information, like how the nodes map their BMC >>> addresses and how the SMBIOS table is populated. If the BMCs appeared >>> in the SMBIOS tables in node order, then the solution is very easy, just >>> detect and add 1 for each. I could just print a warning at startup when >>> it detects this and it would probably cover a multitude of future evils :-). >>> >>> >>> >> I thought about this some more, and it's a good idea, I believe to do >> this. The patch was easy, and I have tested it using a simulator. >> >> Note that I found a bug in the product id stuff. It may be that your >> BMCs don't have a *device* GUID or at least a unique device GUID. (Note >> that a device GUID is different than a system GUID, and your system may >> only have a system GUID. The system GUID is supposed to be the same for >> the entire system, but each BMC is supposed to have its own unique >> device GUID if it supports that). I was passing a 16-bit value as an >> unsigned char in the compare routine, so it never matched based on >> product/device id. So with this patch, either you will get the previous >> behavior (if your system supports device GUIDs) or all the BMCs will >> appear to be the a single BMC with multiple interfaces to it (if device >> GUIDs are not supported). >> >> This patch replaces the previous one I sent you. >> >> -Corey >> >> > > > ------------------------------------------------------------------------- > Using Tomcat but need to do more? Need to support web services, security? > Get stuff done quickly with pre-integrated technology to make your job easier > Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 > _______________________________________________ > Openipmi-developer mailing list > Openipmi-developer@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/openipmi-developer > ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Openipmi-developer mailing list Openipmi-developer@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openipmi-developer
