 |
≫ |
|
|
|
パッチ名: PHKL_34795
パッチ摘要: s700_800 11.23 累積IPMIドライバパッチ
作成日: 07/01/19
公開日: 07/02/07
ハードウェアプラットフォームおよびOSリリース:
s700: 11.23
s800: 11.23
現象:
PHKL_34795:
1.(SR:8606442062 CR:JAGaf99727)
IPMIブリッジドコマンドインタフェースがサポートされないため、entry-
classサーバーの管理性が制限されます。
2.(SR:8606451873 CR:JAGag08762)
IPMI KCSインタフェースが異常な状態になるため、すべてのIPMIコマンドがエ
ラーになります。
3.(SR:8606456562 CR:JAGag12962)
ブート時に、ある仮想パーティションが次のようなスタックトレースでパニッ
クになります。
Stack Trace:
IP Function Name
0xe000000000bb9420 bad_news+0x950
0xe000000000bb8440 bubbledown
0xe0000000013ae100 spinlock+0x40
0xe000000000ee71f0 bt_wakeup+0x40
0xe0000000014f6820 vp_iosapic_is_designated+0x360
0xe0000000014f6c60 vp_iosapic_redirection_isr+0x120
0xe0000000014f6b60 vp_iosapic_redirection_isr+0x20
0xe0000000014fd260 vp_register_isr+0x3a0
0xe000000000805150 external_interrupt+0x3b0
0xe000000000bb8440 bubbledown
0xe000000000ee6400 bt_InterfaceInit_interrupt+0x20
0xe000000000ee2840 ipmi_isrlink_vpar+0xa0
0xe000000000ee9770 ipmi_vpar_dthread+0xc0
4.(SR:8606469050 CR:JAGag24301)
IPMIコマンドが、指定した時間より遅くタイムアウトすることがあります。
5.(SR:8606470542 CR:JAGag25625)
カーネルデバッガがIPMIドライバのシンボルを識別しません。
問題点の説明:
PHKL_34795:
1.(SR:8606442062 CR:JAGaf99727)
IPMIドライバはブリッジドコマンドをサポートしていませんでした。
解決方法:
ブリッジドコマンドインタフェースをサポートするようにIPMIドライバを修正
しました。
2.(SR:8606451873 CR:JAGag08762)
IPMIドライバのエラー処理シーケンスはIPMI仕様に従っていませんでした。
解決方法:
IPMI仕様どおりにエラー処理を行うようにIPMIドライバを修正しました。
3.(SR:8606456562 CR:JAGag12962)
IPMIドライバの初期化時に、競合が起きていました。
解決方法:
IPMIドライバの初期化を直列化しました。
4.(SR:8606469050 CR:JAGag24301)
複数のIPMIスレッドが同じ休眠チャネルを使用していました。
解決方法:
スレッドごとに一意の休眠チャネルを割り当てるようにIPMIドライバを修正し
ました。
5.(SR:8606470542 CR:JAGag25625)
IPMIドライバモジュールが、デバッガをサポートするように生成されていませ
んでした。
解決方法:
デバッガをサポートするようにIPMIドライバモジュールを生成し直しました。
-----------------------------------------------------------------------------
Patch Name: PHKL_34795
Patch Description: s700_800 11.23 Cumulative IPMI driver patch
Creation Date: 07/01/19
Post Date: 07/02/07
Hardware Platforms - OS Releases:
s700: 11.23
s800: 11.23
Products: N/A
Filesets:
OS-Core.CORE2-KRN,fr=B.11.23,fa=HP-UX_B.11.23_IA,v=HP
OS-Core.CORE2-KRN,fr=B.11.23,fa=HP-UX_B.11.23_PA,v=HP
Automatic Reboot?: Yes
Status: General Release
Critical:
Yes
PHKL_34795: PANIC
PHKL_33433: HANG CORRUPTION
PHKL_32262: OTHER
vPar systems with ipmi will not boot without
this patch.
This patch includes various IPMI driver fixes
for vPar and non-vPar systems.
Category Tags:
defect_repair hardware_enablement general_release critical
panic halts_system corruption
Path Name: /hp-ux_patches/s700_800/11.X/PHKL_34795
Symptoms:
PHKL_34795:
( SR:8606442062 CR:JAGaf99727 )
Manageability of entry-class servers is limited due to
lack of support for the IPMI bridged command interface.
( SR:8606451873 CR:JAGag08762 )
IPMI KCS interface enters a state which causes all IPMI
commands to fail.
( SR:8606456562 CR:JAGag12962 )
During boot a virtual partition panics with a stack trace
similar to:
Stack Trace:
IP Function Name
0xe000000000bb9420 bad_news+0x950
0xe000000000bb8440 bubbledown
0xe0000000013ae100 spinlock+0x40
0xe000000000ee71f0 bt_wakeup+0x40
0xe0000000014f6820 vp_iosapic_is_designated+0x360
0xe0000000014f6c60 vp_iosapic_redirection_isr+0x120
0xe0000000014f6b60 vp_iosapic_redirection_isr+0x20
0xe0000000014fd260 vp_register_isr+0x3a0
0xe000000000805150 external_interrupt+0x3b0
0xe000000000bb8440 bubbledown
0xe000000000ee6400 bt_InterfaceInit_interrupt+0x20
0xe000000000ee2840 ipmi_isrlink_vpar+0xa0
0xe000000000ee9770 ipmi_vpar_dthread+0xc0
( SR:8606469050 CR:JAGag24301 )
IPMI command may take longer than expected to timeout.
( SR:8606470542 CR:JAGag25625 )
Kernel debugger does not understand IPMI driver symbols.
PHKL_33433:
( SR:8606404785 CR:JAGaf64706 )
One vPar appears hung early in boot (or shutdown) and
the IPMI calls fail on the other vPars in the nPar.
This causes users of IPMI (the kernel and system
management software) to retry a message or results
in the loss of debug chassis codes.
( SR:8606403948 CR:JAGaf63872 )
vPar IPMI messages time out too soon during early boot
or shutdown.
The failed IPMI calls can result in debug chassis codes
(indicating forward progress) not getting logged.
( SR:8606401054 CR:JAGaf61003 )
Runtime IPMI message times out and returns failure too
early (did not spend its allotted time).
This causes users of IPMI (the kernel and system
management software) to retry a message or results
in the loss of debug chassis codes.
PHKL_32262:
( SR:8606380939 CR:JAGaf41157 )
Hardware enablement: This product update enables
support for virtual partitions in the IPMI driver.
vPar systems with IPMI will not boot without this
update.
( SR:8606389337 CR:JAGaf49485 )
PA ignite ux golden image installs using the
11.23.0409 install kernel are missing the IPMI
driver.
( SR:8606390054 CR:JAGaf50200 )
Wrong IPMI response returned.
( SR:8606393041 CR:JAGaf53100 )
IPMI man page is not needed.
( SR:8606398316 CR:JAGaf58298 )
IPMI commands stop working on a cellular
system.
Defect Description:
PHKL_34795:
( SR:8606442062 CR:JAGaf99727 )
IPMI driver does not support bridged commands.
Resolution:
IPMI driver now supports bridged command interface.
( SR:8606451873 CR:JAGag08762 )
IPMI driver does not follow the error handling sequence
required by the IPMI specification.
Resolution:
IPMI driver follows the IPMI specification for
error handling.
( SR:8606456562 CR:JAGag12962 )
Race condition during initialization in the IPMI driver.
Resolution:
IPMI driver initialization serialized.
( SR:8606469050 CR:JAGag24301 )
More than one IPMI thread uses the same sleep channel.
Resolution:
IPMI driver assigns a unique sleep channel to every thread.
( SR:8606470542 CR:JAGag25625 )
IPMI driver module not built with debugger support.
Resolution:
IPMI driver module now includes debugger support.
PHKL_33433:
( SR:8606404785 CR:JAGaf64706 )
One vPar is in early boot (or shutdown) trying to get an
IPMI response. The response is not returned due to
a corner case (the vPar Monitor is looking in its own
buffers for the response rather than going to hardware).
The bit indicting a response is available does not get
cleared so the vPar keeps trying to get a response and
appears hung.
This ties up a lock, keeping the other vPars in the nPar
from sending IPMI messages.
This has only been seen on systems with a large number of
OS instances (for instance 4 nPars each with 8 vPars)
during reboot stress testing.
Resolution:
Use a flag to tell the vPar Monitor to go to hardware for
the response so the Monitor does not rely on the system
state, which could change.
( SR:8606403948 CR:JAGaf63872 )
When there is high IPMI traffic the contention for the IPMI
vPar lock can cause early boot or shutdown messages to
time out too early trying to get the lock.
Resolution:
Allow the messages more time to get the lock.
( SR:8606401054 CR:JAGaf61003 )
The IPMI driver time keeping when a message waits for
driver resources could cause a message to time
out too soon. This is rare under normal operations
but exposed more readily under test circumstances.
Resolution:
Correct the driver time keeping so it does not time
out too soon.
PHKL_32262:
( SR:8606380939 CR:JAGaf41157 )
This product update enables support for virtual
partitions in the IPMI driver.
Resolution:
The IPMI driver was updated to make it aware of
virtual partitions, and to support future enablement
of the Integrity VM product's ability to send
chassis codes.
( SR:8606389337 CR:JAGaf49485 )
ioscan shows IPMI as unclaimed.
Resolution:
Use a newer (post 11.23.0409) PA install kernel for Golden
Image installs or use this IPMI patch which has an added
iux_postload script that will add IPMI into the system file
if the IPMI hardware is on the system.
( SR:8606390054 CR:JAGaf50200 )
IPMI could return the wrong response on systems under
IPMI stress that have IPMI requests timing out.
Resolution:
Increased the number of IPMI request identifiers so that
a request will not incorrectly match a timed-out response.
( SR:8606393041 CR:JAGaf53100 )
IPMI man page information is not applicable for end users.
Resolution:
Removed man page.
( SR:8606398316 CR:JAGaf58298 )
The IPMI driver sends too many requests at one time to the
Management Processor. On cellular systems with multiple OS
instances running, the total number of requests sent can
overload the Management Processor and cause it to
disconnect.
Resolution:
Limit the number of requests the driver sends.
Enhancement:
No
SR:
8606442062 8606451873 8606456562 8606469050 8606470542
8606404785 8606403948 8606401054 8606380939 8606389337
8606390054 8606393041 8606398316
Patch Files:
OS-Core.CORE2-KRN,fr=B.11.23,fa=HP-UX_B.11.23_IA,v=HP:
/usr/conf/lib/libipmi.a(bt.o)
/usr/conf/lib/libipmi.a(bt_vpar.o)
/usr/conf/lib/libipmi.a(ipmi.o)
/usr/conf/lib/libipmi.a(ipmi_daemon.o)
/usr/conf/lib/libipmi.a(ipmi_dbg.o)
/usr/conf/lib/libipmi.a(ipmi_psm.o)
/usr/conf/lib/libipmi.a(ipmi_system_state.o)
/usr/conf/lib/libipmi.a(ipmi_watchdog.o)
/usr/conf/lib/libipmi.a(kcs.o)
/usr/conf/lib/libipmi.a(libipmi.modmeta.o)
OS-Core.CORE2-KRN,fr=B.11.23,fa=HP-UX_B.11.23_PA,v=HP:
/usr/conf/lib/libipmi.a(bt.o)
/usr/conf/lib/libipmi.a(bt_vpar.o)
/usr/conf/lib/libipmi.a(ipmi.o)
/usr/conf/lib/libipmi.a(ipmi_daemon.o)
/usr/conf/lib/libipmi.a(ipmi_dbg.o)
/usr/conf/lib/libipmi.a(ipmi_psm.o)
/usr/conf/lib/libipmi.a(kcs.o)
/usr/conf/lib/libipmi.a(libipmi.modmeta.o)
what(1) Output:
OS-Core.CORE2-KRN,fr=B.11.23,fa=HP-UX_B.11.23_IA,v=HP:
/usr/conf/lib/libipmi.a(bt.o):
bt.c $Date: 2007/01/16 14:34:01 $Revision: r11.23/4
PATCH_11.23 (PHKL_34795)
/usr/conf/lib/libipmi.a(bt_vpar.o):
bt_vpar.c $Date: 2007/01/16 14:34:07 $Revision: r11.
23/4 PATCH_11.23 (PHKL_34795)
/usr/conf/lib/libipmi.a(ipmi.o):
ipmi.c $Date: 2007/01/16 14:34:12 $Revision: r11.23/
3 PATCH_11.23 (PHKL_34795)
/usr/conf/lib/libipmi.a(ipmi_daemon.o):
ipmi_daemon.c $Date: 2005/05/03 14:35:08 $Revision:
r11.23/2 PATCH_11.23 (PHKL_32262)
/usr/conf/lib/libipmi.a(ipmi_dbg.o):
ipmi_dbg.c $Date: 2007/01/16 14:34:18 $Revision: r11
.23/1 PATCH_11.23 (PHKL_34795)
/usr/conf/lib/libipmi.a(ipmi_psm.o):
ipmi_psm.c $Date: 2007/01/16 14:34:23 $Revision: r11
.23/3 PATCH_11.23 (PHKL_34795)
/usr/conf/lib/libipmi.a(ipmi_system_state.o):
ipmi_system_state.c $Date: 2005/05/03 14:39:14 $Revi
sion: r11.23/2 PATCH_11.23 (PHKL_32262)
/usr/conf/lib/libipmi.a(ipmi_watchdog.o):
ipmi_watchdog.c $Date: 2005/05/03 14:47:06 $Revision
: r11.23/2 PATCH_11.23 (PHKL_32262)
/usr/conf/lib/libipmi.a(kcs.o):
kcs.c $Date: 2007/01/16 14:34:26 $Revision: r11.23/2
PATCH_11.23 (PHKL_34795)
/usr/conf/lib/libipmi.a(libipmi.modmeta.o):
libipmi.modmeta $Date: 2007/01/16 14:34:29 $Revision
: r11.23/1 PATCH_11.23 (PHKL_34795)
OS-Core.CORE2-KRN,fr=B.11.23,fa=HP-UX_B.11.23_PA,v=HP:
/usr/conf/lib/libipmi.a(bt.o):
bt.c $Date: 2007/01/16 14:34:01 $Revision: r11.23/4
PATCH_11.23 (PHKL_34795)
/usr/conf/lib/libipmi.a(bt_vpar.o):
bt_vpar.c $Date: 2007/01/16 14:34:07 $Revision: r11.
23/4 PATCH_11.23 (PHKL_34795)
/usr/conf/lib/libipmi.a(ipmi.o):
ipmi.c $Date: 2007/01/16 14:34:12 $Revision: r11.23/
3 PATCH_11.23 (PHKL_34795)
/usr/conf/lib/libipmi.a(ipmi_daemon.o):
ipmi_daemon.c $Date: 2005/05/03 14:35:08 $Revision:
r11.23/2 PATCH_11.23 (PHKL_32262)
/usr/conf/lib/libipmi.a(ipmi_dbg.o):
ipmi_dbg.c $Date: 2007/01/16 14:34:18 $Revision: r11
.23/1 PATCH_11.23 (PHKL_34795)
/usr/conf/lib/libipmi.a(ipmi_psm.o):
ipmi_psm.c $Date: 2007/01/16 14:34:23 $Revision: r11
.23/3 PATCH_11.23 (PHKL_34795)
/usr/conf/lib/libipmi.a(kcs.o):
kcs.c $Date: 2007/01/16 14:34:26 $Revision: r11.23/2
PATCH_11.23 (PHKL_34795)
/usr/conf/lib/libipmi.a(libipmi.modmeta.o):
libipmi.modmeta $Date: 2007/01/16 14:34:29 $Revision
: r11.23/1 PATCH_11.23 (PHKL_34795)
cksum(1) Output:
OS-Core.CORE2-KRN,fr=B.11.23,fa=HP-UX_B.11.23_IA,v=HP:
2278613725 68696 /usr/conf/lib/libipmi.a(bt.o)
3316025150 23288 /usr/conf/lib/libipmi.a(bt_vpar.o)
3789310915 60944 /usr/conf/lib/libipmi.a(ipmi.o)
4009792247 5256 /usr/conf/lib/libipmi.a(ipmi_daemon.o)
237783653 149080 /usr/conf/lib/libipmi.a(ipmi_dbg.o)
4101726559 85560 /usr/conf/lib/libipmi.a(ipmi_psm.o)
2491720543 7424 /usr/conf/lib/libipmi.a(ipmi_system_state.o)
124662710 15816 /usr/conf/lib/libipmi.a(ipmi_watchdog.o)
279241033 25896 /usr/conf/lib/libipmi.a(kcs.o)
3890695991 2248 /usr/conf/lib/libipmi.a(libipmi.modmeta.o)
OS-Core.CORE2-KRN,fr=B.11.23,fa=HP-UX_B.11.23_PA,v=HP:
1460688188 44216 /usr/conf/lib/libipmi.a(bt.o)
574778164 15784 /usr/conf/lib/libipmi.a(bt_vpar.o)
984613183 34552 /usr/conf/lib/libipmi.a(ipmi.o)
3040403954 4152 /usr/conf/lib/libipmi.a(ipmi_daemon.o)
1268715499 301472 /usr/conf/lib/libipmi.a(ipmi_dbg.o)
1947341018 45336 /usr/conf/lib/libipmi.a(ipmi_psm.o)
2439146436 16048 /usr/conf/lib/libipmi.a(kcs.o)
2358430516 2408 /usr/conf/lib/libipmi.a(libipmi.modmeta.o)
Patch Conflicts: None
Patch Dependencies:
s700: 11.23: PHKL_31500
s800: 11.23: PHKL_31500
Hardware Dependencies: None
Other Dependencies: None
Supersedes:
PHKL_33433 PHKL_32262
Equivalent Patches: None
Patch Package Size: 330 KBytes
Installation Instructions:
Please review all instructions and the Hewlett-Packard
SupportLine User Guide or your Hewlett-Packard support terms
and conditions for precautions, scope of license,
restrictions, and, limitation of liability and warranties,
before installing this patch.
------------------------------------------------------------
1. Back up your system before installing a patch.
2. Login as root.
3. Copy the patch to the /tmp directory.
4. Move to the /tmp directory and unshar the patch:
cd /tmp
sh PHKL_34795
5. Run swinstall to install the patch:
swinstall -x autoreboot=true -x patch_match_target=true \
-s /tmp/PHKL_34795.depot
By default swinstall will archive the original software in
/var/adm/sw/save/PHKL_34795. If you do not wish to retain a
copy of the original software, include the patch_save_files
option in the swinstall command above:
-x patch_save_files=false
WARNING: If patch_save_files is false when a patch is installed,
the patch cannot be deinstalled. Please be careful
when using this feature.
For future reference, the contents of the PHKL_34795.text file is
available in the product readme:
swlist -l product -a readme -d @ /tmp/PHKL_34795.depot
To put this patch on a magnetic tape and install from the
tape drive, use the command:
dd if=/tmp/PHKL_34795.depot of=/dev/rmt/0m bs=2k
Special Installation Instructions: None
|
