Topic
  • 8 replies
  • Latest Post - ‏2012-01-11T23:28:53Z by Frank Fegert
Frank Fegert
Frank Fegert
8 Posts

Pinned topic Remove memory DLPAR operation fails (Debian 6.0.3)

‏2011-12-30T11:51:00Z |
Hello all,
 
i'm currently trying to get the whole DLPAR / LPM thing to work on our Debian (v6.0.3) Linux LPARs. I know Debian is not officially supported, but i still wanted to give it a try ;-) 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
Updated on 2012-01-11T23:28:53Z at 2012-01-11T23:28:53Z by Frank Fegert
  • jscheel
    jscheel
    61 Posts

    Re: Remove memory DLPAR operation fails (Debian 6.0.3)

    ‏2012-01-03T18:21:34Z  
     DLPAR memory remove requires a kernel of at least 2.6.26 if my recollection serves me well.  What kernel version are you running?
  • Frank Fegert
    Frank Fegert
    8 Posts

    Re: Remove memory DLPAR operation fails (Debian 6.0.3)

    ‏2012-01-03T20:41:24Z  
    • jscheel
    • ‏2012-01-03T18:21:34Z
     DLPAR memory remove requires a kernel of at least 2.6.26 if my recollection serves me well.  What kernel version are you running?
    Hello,
     
    thanks for the reply. As explained above i'm trying this with a 2.6.39 Kernel.
     
    Thanks & best regards,
     
    Frank Fegert
     
  • Brian_King
    Brian_King
    22 Posts

    Re: Remove memory DLPAR operation fails (Debian 6.0.3)

    ‏2012-01-04T15:27:11Z  
     Hello,
     
    Can you post your entire kernel config for review?
     
    Thanks,
     
    Brian
  • Frank Fegert
    Frank Fegert
    8 Posts

    Re: Remove memory DLPAR operation fails (Debian 6.0.3)

    ‏2012-01-05T10:11:38Z  
     Hello,
     
    Can you post your entire kernel config for review?
     
    Thanks,
     
    Brian
     Hello,
     
    thanks for the reply.  Please see .config for the complete kernel config.
    Also see this discussion on the debian-powerpc mailing list.
     
     Thanks & best regards,
     
    Frank Fegert
  • Brian_King
    Brian_King
    22 Posts

    Re: Remove memory DLPAR operation fails (Debian 6.0.3)

    ‏2012-01-05T16:37:49Z  
     Hello,
     
    thanks for the reply.  Please see .config for the complete kernel config.
    Also see this discussion on the debian-powerpc mailing list.
     
     Thanks & best regards,
     
    Frank Fegert
     Looking at the .config file you provided, I see CONFIG_SPARSEMEM_VMEMMAP=y. This config option is currently incompatible with memory DLPAR remove. Please disable this option and see if that resolves your issue.
  • Frank Fegert
    Frank Fegert
    8 Posts

    Re: Remove memory DLPAR operation fails (Debian 6.0.3)

    ‏2012-01-05T23:32:15Z  
     Looking at the .config file you provided, I see CONFIG_SPARSEMEM_VMEMMAP=y. This config option is currently incompatible with memory DLPAR remove. Please disable this option and see if that resolves your issue.
    Hello,
    thank you very much! Disabling CONFIG_SPARSEMEM_VMEMMAP did the trick! I still get the
    "Trying to free nonexistent resource <0000000080000000-0000000080ffffff>" messages
    from the kernel output but DLPAR memory removal seems to work now.
     
    Next step was giving LPM a try. This looked good from the HMC status messages at first,
    but the whole OS hang at/after the suspend/unsuspend operation. After several minutes
    of waiting - it eventually succeeded. The following kernel messages showed up around
    the time the OS continued to run:
     
    [ ... memory remove DLPAR here ... ]
    [ 1718.704600] Trying to free nonexistent resource <000000008f000000-000000008fffffff>
    [ 1966.342008] ------------[ cut here ]------------
    [ 1966.342043] WARNING: at /usr/src/linux-2.6-2.6.39/debian/build/source_powerpc_none/kernel/timer.c:1012
    [ 1966.342049] Modules linked in: loop serio ext3 jbd mbcache dm_round_robin dm_multipath scsi_dh dm_mod sd_mod crc_t10dif ibmvscsic scsi_transport_srp scsi_tgt scsi_mod ibmveth [last unloaded: scsi_wait_scan]
    [ 1966.342102] NIP: c0000000000a79a0 LR: c00000000003dddc CTR: 000000000178f500
    [ 1966.342108] REGS: c00000009ffc77e0 TRAP: 0700   Not tainted  (2.6.39-bpo.2-powerpc)
    [ 1966.342112] MSR: 8000000000021032 <ME,CE,IR,DR>  CR: 48000084  XER: 00000001
    [ 1966.342135] TASK = c00000009e994ab0[0] 'kworker/0:1' THREAD: c00000009e99c000 CPU: 5
    [ 1966.342140] GPR00: 0000000000000001 c00000009ffc7a60 c000000000828fb8 c000000000768b08
    [ 1966.342149] GPR04: 0000000000000001 0000000000000000 0000000000000012 0000001200000000
    [ 1966.342157] GPR08: 0000000000000012 c00000009ffc4000 0000000000000006 0000000000000001
    [ 1966.342166] GPR12: 0000000000000000 c00000000eea6c80 c00000009e99ff90 000000000ef04280
    [ 1966.342175] GPR16: 0000000000000000 0000000000000000 c000000000765f88 c000000000be4eb0
    [ 1966.342183] GPR20: c0000000007b2960 0000000000000020 0000000000000000 c000000000838300
    [ 1966.342191] GPR24: 0000000000000000 0000000000000000 c00000009b4e7c94 c00000009b4e7c9c
    [ 1966.342200] GPR28: 0000000000000040 0000000000000001 c000000000798840 c000000000768b08
    [ 1966.342251] NIP [c0000000000a79a0] .del_timer_sync+0x28/0x5c
    [ 1966.342270] LR [c00000000003dddc] .stop_topology_update+0x20/0x34
    [ 1966.342274] Call Trace:
    [ 1966.342287] [c00000009ffc7a60] [000000001c8e9d39] 0x1c8e9d39 (unreliable)
    [ 1966.342294] [c00000009ffc7ae0] [c00000000003dddc] .stop_topology_update+0x20/0x34
    [ 1966.342310] [c00000009ffc7b50] [c000000000023678] .__rtas_suspend_last_cpu+0x54/0x1cc
    [ 1966.342326] [c00000009ffc7c00] [c0000000000d475c] .generic_smp_call_function_interrupt+0x11c/0x264
    [ 1966.342335] [c00000009ffc7cf0] [c00000000002e7f8] .smp_message_recv+0x48/0xf4
    [ 1966.342345] [c00000009ffc7d70] [c00000000005c934] .xics_ipi_dispatch+0x74/0x130
    [ 1966.342357] [c00000009ffc7e10] [c0000000001030d0] .handle_irq_event_percpu+0xec/0x2f0
    [ 1966.342363] [c00000009ffc7f00] [c000000000106248] .handle_percpu_irq+0x84/0xd0
    [ 1966.342374] [c00000009ffc7f90] [c00000000001e7d0] .call_handle_irq+0x1c/0x2c
    [ 1966.342381] [c00000009e99fab0] [c00000000000f7b4] .do_IRQ+0x184/0x26c
    [ 1966.342387] [c00000009e99fb60] [c000000000004d30] hardware_interrupt_entry+0x18/0x1c
    [ 1966.342395] --- Exception: 501 at .arch_local_irq_restore+0x70/0x80
    [ 1966.342397]     LR = .cpu_idle+0x124/0x1d8
    [ 1966.342423] [c00000009e99fee0] [c00000000054afc4] .start_secondary+0x354/0x360
    [ 1966.342430] [c00000009e99ff90] [c0000000000092e8] .start_secondary_prolog+0x10/0x14
    [ 1966.342435] Instruction dump:
    [ 1966.342439] 7c0803a6 4e800020 7c0802a6 fbe1fff8 7c7f1b78 f8010010 f821ff81 78290464
    [ 1966.342449] 80090014 5400019e 7c0000d0 78000fe0 <0b000000> 7fe3fb78 4bfffea1 2f830000
    [ 1966.342461] ---[ end trace dcb8a21996018b78 ]---
    [ 1966.342466] calling ibm,suspend-me on cpu 5
    [ 1986.614322] EPOW <0x6240040000000b8 0x0 0x0>
    [ 1986.624019] RTAS: event: 1, Type: EPOW, Severity: 1
    [ 1986.627729] ibmvscsi 30000002: Re-enabling adapter!
    [ 1986.644364] ibmvscsi 30000003: Re-enabling adapter!
    [ 1989.073563] ibmvscsi 30000003: partner initialization complete
    [ 1989.073571] ibmvscsi 30000002: partner initialization complete
    [ 1989.073651] ibmvscsi 30000003: host srp version: 16.a, host partition vios2-p550-300 (2), OS 3, max io 262144
    [ 1989.075131] ibmvscsi 30000003: Client reserve enabled
    [ 1989.075145] ibmvscsi 30000003: sent SRP login
    [ 1989.075228] ibmvscsi 30000003: SRP_LOGIN succeeded
    [ 1989.075504] ibmvscsi 30000002: host srp version: 16.a, host partition vios1-p550-300 (1), OS 3, max io 262144
    [ 1989.075616] ibmvscsi 30000002: Client reserve enabled
    [ 1989.076232] ibmvscsi 30000002: sent SRP login
    [ 1989.076347] ibmvscsi 30000002: SRP_LOGIN succeeded
    [ 1990.818052] property parse failed in parse_next_property at line 225
    [ 1992.320326] property parse failed in parse_next_property at line 225

    Any thoughts about that one?
     
    Thanks & best regards,
     
    Frank Fegert
  • Brian_King
    Brian_King
    22 Posts

    Re: Remove memory DLPAR operation fails (Debian 6.0.3)

    ‏2012-01-11T20:46:15Z  
    Hello,
    thank you very much! Disabling CONFIG_SPARSEMEM_VMEMMAP did the trick! I still get the
    "Trying to free nonexistent resource <0000000080000000-0000000080ffffff>" messages
    from the kernel output but DLPAR memory removal seems to work now.
     
    Next step was giving LPM a try. This looked good from the HMC status messages at first,
    but the whole OS hang at/after the suspend/unsuspend operation. After several minutes
    of waiting - it eventually succeeded. The following kernel messages showed up around
    the time the OS continued to run:
     
    [ ... memory remove DLPAR here ... ]
    [ 1718.704600] Trying to free nonexistent resource <000000008f000000-000000008fffffff>
    [ 1966.342008] ------------[ cut here ]------------
    [ 1966.342043] WARNING: at /usr/src/linux-2.6-2.6.39/debian/build/source_powerpc_none/kernel/timer.c:1012
    [ 1966.342049] Modules linked in: loop serio ext3 jbd mbcache dm_round_robin dm_multipath scsi_dh dm_mod sd_mod crc_t10dif ibmvscsic scsi_transport_srp scsi_tgt scsi_mod ibmveth [last unloaded: scsi_wait_scan]
    [ 1966.342102] NIP: c0000000000a79a0 LR: c00000000003dddc CTR: 000000000178f500
    [ 1966.342108] REGS: c00000009ffc77e0 TRAP: 0700   Not tainted  (2.6.39-bpo.2-powerpc)
    [ 1966.342112] MSR: 8000000000021032 <ME,CE,IR,DR>  CR: 48000084  XER: 00000001
    [ 1966.342135] TASK = c00000009e994ab0[0] 'kworker/0:1' THREAD: c00000009e99c000 CPU: 5
    [ 1966.342140] GPR00: 0000000000000001 c00000009ffc7a60 c000000000828fb8 c000000000768b08
    [ 1966.342149] GPR04: 0000000000000001 0000000000000000 0000000000000012 0000001200000000
    [ 1966.342157] GPR08: 0000000000000012 c00000009ffc4000 0000000000000006 0000000000000001
    [ 1966.342166] GPR12: 0000000000000000 c00000000eea6c80 c00000009e99ff90 000000000ef04280
    [ 1966.342175] GPR16: 0000000000000000 0000000000000000 c000000000765f88 c000000000be4eb0
    [ 1966.342183] GPR20: c0000000007b2960 0000000000000020 0000000000000000 c000000000838300
    [ 1966.342191] GPR24: 0000000000000000 0000000000000000 c00000009b4e7c94 c00000009b4e7c9c
    [ 1966.342200] GPR28: 0000000000000040 0000000000000001 c000000000798840 c000000000768b08
    [ 1966.342251] NIP [c0000000000a79a0] .del_timer_sync+0x28/0x5c
    [ 1966.342270] LR [c00000000003dddc] .stop_topology_update+0x20/0x34
    [ 1966.342274] Call Trace:
    [ 1966.342287] [c00000009ffc7a60] [000000001c8e9d39] 0x1c8e9d39 (unreliable)
    [ 1966.342294] [c00000009ffc7ae0] [c00000000003dddc] .stop_topology_update+0x20/0x34
    [ 1966.342310] [c00000009ffc7b50] [c000000000023678] .__rtas_suspend_last_cpu+0x54/0x1cc
    [ 1966.342326] [c00000009ffc7c00] [c0000000000d475c] .generic_smp_call_function_interrupt+0x11c/0x264
    [ 1966.342335] [c00000009ffc7cf0] [c00000000002e7f8] .smp_message_recv+0x48/0xf4
    [ 1966.342345] [c00000009ffc7d70] [c00000000005c934] .xics_ipi_dispatch+0x74/0x130
    [ 1966.342357] [c00000009ffc7e10] [c0000000001030d0] .handle_irq_event_percpu+0xec/0x2f0
    [ 1966.342363] [c00000009ffc7f00] [c000000000106248] .handle_percpu_irq+0x84/0xd0
    [ 1966.342374] [c00000009ffc7f90] [c00000000001e7d0] .call_handle_irq+0x1c/0x2c
    [ 1966.342381] [c00000009e99fab0] [c00000000000f7b4] .do_IRQ+0x184/0x26c
    [ 1966.342387] [c00000009e99fb60] [c000000000004d30] hardware_interrupt_entry+0x18/0x1c
    [ 1966.342395] --- Exception: 501 at .arch_local_irq_restore+0x70/0x80
    [ 1966.342397]     LR = .cpu_idle+0x124/0x1d8
    [ 1966.342423] [c00000009e99fee0] [c00000000054afc4] .start_secondary+0x354/0x360
    [ 1966.342430] [c00000009e99ff90] [c0000000000092e8] .start_secondary_prolog+0x10/0x14
    [ 1966.342435] Instruction dump:
    [ 1966.342439] 7c0803a6 4e800020 7c0802a6 fbe1fff8 7c7f1b78 f8010010 f821ff81 78290464
    [ 1966.342449] 80090014 5400019e 7c0000d0 78000fe0 <0b000000> 7fe3fb78 4bfffea1 2f830000
    [ 1966.342461] ---[ end trace dcb8a21996018b78 ]---
    [ 1966.342466] calling ibm,suspend-me on cpu 5
    [ 1986.614322] EPOW <0x6240040000000b8 0x0 0x0>
    [ 1986.624019] RTAS: event: 1, Type: EPOW, Severity: 1
    [ 1986.627729] ibmvscsi 30000002: Re-enabling adapter!
    [ 1986.644364] ibmvscsi 30000003: Re-enabling adapter!
    [ 1989.073563] ibmvscsi 30000003: partner initialization complete
    [ 1989.073571] ibmvscsi 30000002: partner initialization complete
    [ 1989.073651] ibmvscsi 30000003: host srp version: 16.a, host partition vios2-p550-300 (2), OS 3, max io 262144
    [ 1989.075131] ibmvscsi 30000003: Client reserve enabled
    [ 1989.075145] ibmvscsi 30000003: sent SRP login
    [ 1989.075228] ibmvscsi 30000003: SRP_LOGIN succeeded
    [ 1989.075504] ibmvscsi 30000002: host srp version: 16.a, host partition vios1-p550-300 (1), OS 3, max io 262144
    [ 1989.075616] ibmvscsi 30000002: Client reserve enabled
    [ 1989.076232] ibmvscsi 30000002: sent SRP login
    [ 1989.076347] ibmvscsi 30000002: SRP_LOGIN succeeded
    [ 1990.818052] property parse failed in parse_next_property at line 225
    [ 1992.320326] property parse failed in parse_next_property at line 225

    Any thoughts about that one?
     
    Thanks & best regards,
     
    Frank Fegert
    Frank,
     
    This looks to be an issue in more recently kernels. I was able to reproduce the issue on one of my systems and submitted a fix upstream.
     
    http://lists.ozlabs.org/pipermail/linuxppc-dev/2012-January/095360.html
     
    Can you apply that patch to your kernel and see if it resolves the issue you are seeing?
     
    Thanks,
     
    Brian
  • Frank Fegert
    Frank Fegert
    8 Posts

    Re: Remove memory DLPAR operation fails (Debian 6.0.3)

    ‏2012-01-11T23:28:53Z  
    Frank,
     
    This looks to be an issue in more recently kernels. I was able to reproduce the issue on one of my systems and submitted a fix upstream.
     
    http://lists.ozlabs.org/pipermail/linuxppc-dev/2012-January/095360.html
     
    Can you apply that patch to your kernel and see if it resolves the issue you are seeing?
     
    Thanks,
     
    Brian
    Hello Brian,
     
    again, thank you very much! The suggested patch resolved the issue completely. The LPM suspend/resume worked without a hang and the remaining dmesg output appears to be purely informative:
     
     [  327.442844] calling ibm,suspend-me on cpu 5
    [  327.928767] EPOW <0x6240040000000b8 0x0 0x0>
    [  327.932863] RTAS: event: 2, Type: EPOW, Severity: 1
    [  327.933304] ibmvscsi 30000002: Re-enabling adapter!
    [  327.933308] ibmvscsi 30000003: Re-enabling adapter!
    [  328.382125] property parse failed in parse_next_property at line 225
    [  329.216426] ibmvscsi 30000003: partner initialization complete
    [  329.216552] ibmvscsi 30000003: host srp version: 16.a, host partition vios2-p550-222 (2), OS 3, max io 262144
    [  329.216673] ibmvscsi 30000003: Client reserve enabled
    [  329.216688] ibmvscsi 30000003: sent SRP login
    [  329.216762] ibmvscsi 30000003: SRP_LOGIN succeeded
    [  329.316401] ibmvscsi 30000002: partner initialization complete
    [  329.316493] ibmvscsi 30000002: host srp version: 16.a, host partition vios1-p550-222 (1), OS 3, max io 262144
    [  329.316642] ibmvscsi 30000002: Client reserve enabled
    [  329.316661] ibmvscsi 30000002: sent SRP login
    [  329.316743] ibmvscsi 30000002: SRP_LOGIN succeeded
    [  330.483790] property parse failed in parse_next_property at line 225
     
    Thanks & best regards,
     
    Frank Fegert