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

Remove memory DLPAR operation fails for Debian 6.0.3 on IBM Power6 and Power7 Systems



Hello all,
 
i'm currently trying to get the whole DLPAR/LPM thing to work on our Debian
(v6.0.3) Linux LPARs. So far i've sucessfully converted the following RPMs
to DEB with alien: 
    devices.chrp.base.servicerm_2.3.0.0-11231
    dynamicrm_1.3.9-8
    librtas_1.3.6-4
    librtas-32bit_1.3.6-5
    libvpd2_2.1.3-4
    lsvpd_1.6.11-5
    rsct.core_3.1.0.7-11277
    rsct.core.utils_3.1.0.7-11277
    src_1.3.1.1-11277

The powerpc-utils were build from scratch with the most current sources from
SF.net (powerpc-ibm-utils_1.2.12-1). With several tweaks to a whole bunch of
scripts provided by the RPMs things look rather good now. I can sucessfully add
and remove processors, and i can successfully add memory. Upon memory removal i
get an error (see below) from the drmgr command. This is reproducible even if
drmgr is issued on the command line, so it's probably not a HMC or RSCT
communication problem. The memory seems to be sucessfully removed from the OS,
but since the HMC gets an error returned from the drmgr it does not seem to
update the LPAR information, which causes the OS and the HMC to have different
information about the guest OSs memory. E.g. after DLPAR remove memory the OS
has 1.5GB RAM, but the HMC still has 2GM RAM assigned to the LPAR.  The drmgr
command seems not to be able to write to /proc/ppc64/ofdt. For debugging i
added the second "Write to:" line appearing in the below error message to the
drmgr sources and tried to manually echo the string to /proc/ppc64/ofdt as the
root user. I still get the "Cannot allocate memory" error message. The OS and
NMON both show about 1.7GB of free memory, so a removal of 0.5GB should be
possible.
The kernel i use on the machine is a rebuild from the original Debian
2.6.39-bpo.2-powerpc kernel, with several PPC/PSERIES/IBM options enabled in
the .config. The  CONFIG_MEMORY_HOT* options are enabled (see below).  Does
anyone have an idea where the "Cannot allocate memory" message originates from
or what the problem might be here?
 
Thanks & best regards,
 
    Frank Fegert
 

#################################################################################
drmgr error ouput:
  ########## Dec 29 11:58:27 2011 ##########
drmgr: drslot_chrp_mem -r -c mem -q 2 -w 5 -d 1
Validating Memory DLPAR capability...yes.
Found 15 lmbs
Found 7 owning lmbs
AMS ballooning is not active
Removing 2 lmbs
AMS ballooning is not active
Found available lmb, LMB5, drc index 0x80000004
Attempting to offline lmb.
Marking /sys/devices/system/memory/memory4 offline
Updating of property
: Write to /proc/ppc64/ofdt failed: Cannot allocate memory
: Write to /proc/ppc64/ofdt failed: update_property 0xfffffff9 ibm,dynamic-memory 364
Attempting to online lmb.
Probing memory address 0x40000000
Probe failed:
File exists
AMS ballooning is not active
Found available lmb, LMB4, drc index 0x80000003
Attempting to offline lmb.
Marking /sys/devices/system/memory/memory3 offline
Updating of property
: Write to /proc/ppc64/ofdt failed: Cannot allocate memory
: Write to /proc/ppc64/ofdt failed: update_property 0xfffffff9 ibm,dynamic-memory 364
Attempting to online lmb.
Probing memory address 0x30000000
Probe failed:
File exists
AMS ballooning is not active
Found available lmb, LMB3, drc index 0x80000002
Attempting to offline lmb.
Marking /sys/devices/system/memory/memory2 offline
Updating of property
: Write to /proc/ppc64/ofdt failed: Cannot allocate memory
: Write to /proc/ppc64/ofdt failed: update_property 0xfffffff9 ibm,dynamic-memory 364
Attempting to online lmb.
Probing memory address 0x20000000
Probe failed:
File exists
AMS ballooning is not active
Found available lmb, LMB2, drc index 0x80000001
Attempting to offline lmb.
Marking /sys/devices/system/memory/memory1 offline
Updating of property
: Write to /proc/ppc64/ofdt failed: Cannot allocate memory
: Write to /proc/ppc64/ofdt failed: update_property 0xfffffff9 ibm,dynamic-memory 364
Attempting to online lmb.
Probing memory address 0x10000000
Probe failed:
File exists
AMS ballooning is not active
Could not find available lmb
Memory removal request failed
Removed 0 of 2 requested lmb(s)
Unable to hotplug remove the remaining 2 lmb(s)
########## Dec 29 11:58:27 2011 ##########

#################################################################################

root@host:/usr/src/linux-2.6-2.6.39/debian/build/build_powerpc_none_powerpc# egrep -i "PPC|PSERIES|POWER|IBM|MEMORY" .config | egrep -v "^# "
CONFIG_PPC64=y
CONFIG_PPC_BOOK3S_64=y
CONFIG_PPC_BOOK3S=y
CONFIG_POWER3=y
CONFIG_POWER4=y
CONFIG_PPC_FPU=y
CONFIG_PPC_STD_MMU=y
CONFIG_PPC_STD_MMU_64=y
CONFIG_PPC_MM_SLICES=y
CONFIG_PPC_HAVE_PMU_SUPPORT=y
CONFIG_PPC_PERF_CTRS=y
CONFIG_PPC=y
CONFIG_PPC_OF=y
CONFIG_PPC_UDBG_16550=y
CONFIG_PPC_DCR_MMIO=y
CONFIG_PPC_DCR=y
CONFIG_PPC_OF_PLATFORM_PCI=y
CONFIG_PPC_MSI_BITMAP=y
CONFIG_PPC_PSERIES=y
CONFIG_PPC_SPLPAR=y
CONFIG_PSERIES_MSI=y
CONFIG_PSERIES_ENERGY=y
CONFIG_PPC_SMLPAR=y
CONFIG_PPC_PMAC=y
CONFIG_PPC_PMAC64=y
CONFIG_PPC_MAPLE=y
CONFIG_PPC_PASEMI=y
CONFIG_PPC_PASEMI_MDIO=m
CONFIG_PPC_PS3=y
CONFIG_PPC_CELL=y
CONFIG_PPC_CELL_COMMON=y
CONFIG_PPC_CELL_NATIVE=y
CONFIG_PPC_IBM_CELL_BLADE=y
CONFIG_PPC_IBM_CELL_RESETBUTTON=y
CONFIG_PPC_IBM_CELL_POWERBUTTON=m
CONFIG_PPC_PMI=m
CONFIG_PPC_NATIVE=y
CONFIG_PPC_OF_BOOT_TRAMPOLINE=y
CONFIG_PPC_I8259=y
CONFIG_PPC_RTAS=y
CONFIG_PPC_RTAS_DAEMON=y
CONFIG_IBMVIO=y
CONFIG_IBMEBUS=y
CONFIG_PPC_970_NAP=y
CONFIG_PPC_INDIRECT_IO=y
CONFIG_CPU_FREQ_GOV_POWERSAVE=m
CONFIG_PPC_PASEMI_CPUFREQ=y
CONFIG_ARCH_ENABLE_MEMORY_HOTPLUG=y
CONFIG_ARCH_HAS_WALK_MEMORY=y
CONFIG_ARCH_ENABLE_MEMORY_HOTREMOVE=y
CONFIG_ARCH_SELECT_MEMORY_MODEL=y
CONFIG_SELECT_MEMORY_MODEL=y
CONFIG_HAVE_MEMORY_PRESENT=y
CONFIG_MEMORY_HOTPLUG=y
CONFIG_MEMORY_HOTPLUG_SPARSE=y
CONFIG_MEMORY_HOTREMOVE=y
CONFIG_ARCH_MEMORY_PROBE=y
CONFIG_PPC_HAS_HASH_64K=y
CONFIG_PPC_4K_PAGES=y
CONFIG_PPC_PCI_CHOICE=y
CONFIG_SCSI_IBMVSCSI=m
CONFIG_SCSI_IBMVSCSIS=m
CONFIG_SCSI_IBMVFC=m
CONFIG_SCSI_IBMVFC_TRACE=y
CONFIG_IBMVETH=m
CONFIG_IBM_NEW_EMAC=m
CONFIG_IBM_NEW_EMAC_RXB=128
CONFIG_IBM_NEW_EMAC_TXB=64
CONFIG_IBM_NEW_EMAC_POLL_WEIGHT=32
CONFIG_IBM_NEW_EMAC_RX_COPY_THRESHOLD=256
CONFIG_IBM_NEW_EMAC_RX_SKB_HEADROOM=0
CONFIG_IBM_NEW_EMAC_ZMII=y
CONFIG_IBM_NEW_EMAC_RGMII=y
CONFIG_IBM_NEW_EMAC_TAH=y
CONFIG_IBM_NEW_EMAC_EMAC4=y
CONFIG_IBMOL=m
CONFIG_PCMCIA_IBMTR=m
CONFIG_INPUT_POWERMATE=m
CONFIG_IPMI_POWEROFF=m
CONFIG_I2C_POWERMAC=m
CONFIG_POWER_SUPPLY=m
CONFIG_SENSORS_IBMAEM=m
CONFIG_SENSORS_IBMPEX=m
CONFIG_FB_IBM_GXT4500=m
CONFIG_SND_AC97_POWER_SAVE=y
CONFIG_SND_AC97_POWER_SAVE_DEFAULT=0
CONFIG_SND_HDA_POWER_SAVE=y
CONFIG_SND_HDA_POWER_SAVE_DEFAULT=0
CONFIG_SND_PPC=y
CONFIG_SND_POWERMAC=m
CONFIG_SND_POWERMAC_AUTO_DRC=y
CONFIG_HID_WACOM_POWER_SUPPLY=y
CONFIG_USB_EHCI_HCD_PPC_OF=y
CONFIG_USB_OHCI_HCD_PPC_OF_BE=y
CONFIG_USB_OHCI_HCD_PPC_OF_LE=y
CONFIG_USB_OHCI_HCD_PPC_OF=y
CONFIG_XZ_DEC_POWERPC=y
CONFIG_DEBUG_MEMORY_INIT=y
CONFIG_EVENT_POWER_TRACING_DEPRECATED=y
CONFIG_PPC_WERROR=y


Reply to: