 |
≫ |
|
|
|
パッチ名: PHNE_36237
パッチ摘要: s700_800 11.11 IETHER 1000Base-SX/T B.11.11.0[4-14]パッチ
作成日: 07/07/23
公開日: 07/08/31
ハードウェアプラットフォームおよびOSリリース:
s700: 11.11
s800: 11.11
現象:
PHNE_36237:
1. (SR:8606480881 CR:JAGag34933)
高トラフィック時に、iether PCI-Xコントローラがハングすることがあります。
2. (SR:8606480892 CR:JAGag34942)
/etc/rc.config.d/hpietherconfファイル内に指定されている
send_max_bufs/recv_max_bufsパラメータのサポート範囲が不正です。
3. (SR:8606490234 CR:JAGag42694)
ユーザーが、VPD内のアセットタグを変更/更新できません。
4. (SR:8606492564 CR:JAGag44735)
トラフィックが非常に少ない場合、(AB290AやAB545Aのような)マルチポートネ
ットワークインタフェースカードでのパケット処理に時間がかかり過ぎます。
この種の遅れは、通常、pingやNFSアプリケーションに悪影響を与えます。
再送機能を持つプロトコル(TCPアプリケーションやNFSのようなアプリケーシ
ョン)の場合は再送が行われる可能性があります。たとえば、MTUの設定値が
1500で、pingパケットサイズが6000/9000バイトの場合、一部のping応答が最
大1秒遅れることがあります。
5. (SR:8606459418 CR:JAGag15548)
カードからブロードキャスト/マルチキャスト宛てに送信されたループバック
パケットのフラグメントチェーンのコピーを作成(copymsg)できない場合、
ドライバが着信破棄カウンタを増分しません。
6. (SR:8606462165 CR:JAGag18057)
カードからブロードキャスト/マルチキャスト/その固有macアドレス宛てに送
信されたループバックパケットが着信しても、mib統計内の着信オクテットカ
ウンタが増分されません。
7. (SR:8606462689 CR:JAGag18545)
高トラフィック時に、AD331A ietherインタフェースカードがFCSエラーを報告
することがあります。
8. (SR:8606472222 CR:JAGag27118)
APAでの変更により、カードが実行するリセットフェーズで、解放済みのバッ
ファが再使用されます。
9. (SR:8606475976 CR:JAGag30277)
ドライバがEEPROMのチェックサムをチェックしないため、EEPROMが無効でもエ
ラーにならないことがあります。
10.(SR:8606492479 CR:JAGag44650)
システムリブートまたは電源の再投入直後に、A7011A/AD332Aカード上で複数
のリンクフラップ(リンクup/downイベント)が起きると、スイッチが、それら
のカードと接続されているスイッチポートを使用不可にすることがあります。
これまでにこの現象が起きたのは、Cisco Catalyst 4500シリーズとCisco
Catalyst 6500シリーズのスイッチだけです。
11.(SR:8606440200 CR:JAGaf98099)
ietherドライバが、lanadminコマンドを使ってカードのMDCを表示しません。
12.(SR:8606443267 CR:JAGag00939)
チェックサムが0x0000のTCPパケットがチェックサム0xffffとして送信される
ため、非HP-UXリモートホストによって破棄されることがあります。この現象
が起きるのは、送信チェックサムオフロードがオンの場合だけです。
13.(SR:8606492566 CR:JAGag44737)
高トラフィック時に、iether駆動インタフェースカードに対して複数のリセッ
ト操作を同時に行うと、システムパニック(MCA)が起きることがあります。
14.(SR:8606492587 CR:JAGag44758)
CIMProvider/LANProviderやその他のユーザーアプリケーションが、ietherデ
バイスのVPD(Vital Product Data)を取り出せません。
問題点の説明:
PHNE_36237:
1. (SR:8606480881 CR:JAGag34933)
高負荷時に、コントローラがPCI-Xバスのマスタリングを中止していたため、
ハングが起きていました。
解決方法:
ハングを検出し、かつ、コントローラをリセットしてハングをクリアするよう
にドライバを修正しました。また、リセットしてハングをクリアしたら、以後
ハングが起きないように、ドライバは各フレームの送信DMAバッファのサイズ
を512バイトに制限し始めます。また、オプションとして、このハング検出お
よびリセット機構とは無関係に、ユーザーは強制的にドライバに送信バッファ
サイズを512バイトに制限させることもできます。それには、"lanadmin
-X tx512_bufs <value> <ppa>"コマンドを使用するか、
/etc/rc.config.d/hpietherconf内のHP_IETHER_TX_512B_BUFパラメータを1に
設定します。
2. (SR:8606480892 CR:JAGag34942)
iether PCI-Xベースカードでのsend_max_bufs/recv_max_bufsの最大値は、
"64"ではなく"63"です。
解決方法:
ietherドライバおよび/etc/rc.config.d/hpietherconfファイル内の
send_max_bufs/recv_max_bufsの不正な範囲を修正しました。また、以下のパ
ラメータのヘルプテキストに必要な情報を追加しました。
- HP_IETHER_SEND_COAL_TICKS
- HP_IETHER_RECV_COAL_TICKS
- HP_IETHER_SEND_MAX_BUFS
- HP_IETHER_RECV_MAX_BUFS
3. (SR:8606490234 CR:JAGag42694)
ietherドライバは、アセットタグの変更を認めませんでした。
解決方法:
VPD内のアセットタグの変更を認めるようにietherドライバを修正しました。
アセットタグを変更するには、lanadminコマンド"lanadmin -X
write_asset_tag <value> <ppa>"を使用します。
4. (SR:8606492564 CR:JAGag44735)
CPUの使用を減らし、パフォーマンスを向上させるために、ietherドライバは
割り込みに対して非同期に応答していました。ところが、この方法では、特に
低トラフィックの場合、フレーム処理が遅れることがあります。
解決方法:
受信したフレームの処理が遅れないように、インタフェースカードからの割り
込みに対して同期的に応答するようにietherドライバを修正しました。
5. (SR:8606459418 CR:JAGag15548)
ドライバはcopymsgを使って、カードからブロードキャスト/マルチキャスト宛
てに送信されたループバックパケットのフラグメントチェーンのコピーを作成
します。ところが、フラグメントチェーンのコピーに失敗した場合、ドライバ
は着信破棄カウンタを増分せずにそれらのパケットを破棄していました。
解決方法:
パケットを破棄する場合は着信破棄カウンタを増分するようにietherドライバ
のコードを修正しました。
6. (SR:8606462165 CR:JAGag18057)
現在のilan_iftデータ構造には、ループバックパケットのInOctetsカウンタに
対応するフィールドがありませんでした。
解決方法:
ループバックパケットのInOctetsカウンタをilan_ift構造に追加し、そのカウ
ンタを増分するようにコードを修正しました。
7. (SR:8606462689 CR:JAGag18545)
リセット操作を行うには追加のコントローラ設定が必要です。そうでないと、
高トラフィックの場合、FCSエラーが起きることがあります。
解決方法:
コントローラをリセットする前に適切なコントローラ設定を行うようにiether
ドライバを修正しました。
8. (SR:8606472222 CR:JAGag27118)
このパニックの原因は、ietherドライバがデータ構造に正しくアクセスしてい
なかったためです。
解決方法:
データ構造に正しくアクセスするようにietherドライバを修正しました。
9. (SR:8606475976 CR:JAGag30277)
ドライバはEEPROMのチェックサムをチェックしなかったため、EEPROMのエラー
を簡単には検出できませんでした。
解決方法:
EEPROMのチェックサムをチェックするようにドライバを修正しました。これで、
ドライバはEEPROMのエラーを簡単に検出できます。
10.(SR:8606492479 CR:JAGag44650)
EDCがB-4628のA7011A、およびEDCが1-4628のAD332Aの場合、EEPROMの設定が不
適切だったため、リブート時や電源再投入時にノイズの影響を受けることがあ
りました。
解決方法:
カード上のEEPROMの内容を更新することによって、この問題を解決できます。
以下のアダプタ上のEEPROMの内容を修正するスクリプトを用意しました。
1) EDCがB-4628のA7011A
2) EDCが1-4628のAD332A
EDCがB-4628より旧いA7011Aアダプタでは、この問題は起きません。また、EDC
がB-4628より新しい7011Aアダプタ、およびEDCが1-4628より新しいAD332Aアダ
プタの場合は、このスクリプトを実行する必要はありません。これらのEDCの
アダプタの場合、製造時に、必要なEEPROMの更新が行われています。このパッ
チは、カード上のEEPROMの内容を更新する機能を提供します。"eeflip.sh"ス
クリプトファイルについては、HPサポートに問い合わせてください。
11.(SR:8606440200 CR:JAGaf98099)
MDC情報は、EEPROM内のカードのVPDから入手できます。ところが、ietherドラ
イバはこの情報をカードのVPDから取り出しませんでした。
解決方法:
"lanadmin -x vpd <ppa>"コマンドを使ってカードのMDCを表示するように
ietherドライバを修正しました。
12.(SR:8606443267 CR:JAGag00939)
ietherドライバがパケットタイプをTCPとして設定していなかったため、カー
ドはそのパケットタイプをUDPとみなしてチェックサム0x0000を0xffffに変換
していました。その結果、受信ホストがそれをチェックサムエラーとみなすこ
とがありました。
解決方法:
パケットタイプを適切に設定するようにietherドライバを修正しました。これ
で、カードはすべてのパケットタイプのチェックサムを正しく計算します。
13.(SR:8606492566 CR:JAGag44737)
リセット操作とデータ転送操作間の競合により、システムがクラッシュ(MCA)
することがありました。
解決方法:
カードがシステムによって解放されたホストメモリーにアクセスする可能性を
減らすために、リセット操作とデータ転送操作との同期を取るようにietherド
ライバを修正しました。
14.(SR:8606492587 CR:JAGag44758)
ietherドライバは、ユーザーアプリケーションがカードのVPDにアクセスする
ための機構をサポートしていませんでした。
解決方法:
アプリケーションがデバイスのVPDにアクセスできるようにietherドライバを
修正しました。"lanadmin -x vpd <#ppa>"を使ってVPDを取り出すこともでき
ます。
-----------------------------------------------------------------------------
Patch Name: PHNE_36237
Patch Description: s700_800 11.11 IETHER 1000Base-SX/T B.11.11.0[4-14] patch
Creation Date: 07/07/23
Post Date: 07/08/31
Hardware Platforms - OS Releases:
s700: 11.11
s800: 11.11
Products:
HP PCI Gigabit Ethernet Driver IETHER B.11.11.04 B.11.11.05
B.11.11.07 B.11.11.09 B.11.11.11 B.11.11.13 B.11.11.14
Filesets:
IETHER-DRV.IETHER-KRN,fr=B.11.11.04,fa=HP-UX_B.11.11_64,v=HP
IETHER-DRV.IETHER-KRN,fr=B.11.11.05,fa=HP-UX_B.11.11_64,v=HP
IETHER-DRV.IETHER-KRN,fr=B.11.11.07,fa=HP-UX_B.11.11_64,v=HP
IETHER-DRV.IETHER-KRN,fr=B.11.11.09,fa=HP-UX_B.11.11_64,v=HP
IETHER-DRV.IETHER-KRN,fr=B.11.11.11,fa=HP-UX_B.11.11_64,v=HP
IETHER-DRV.IETHER-KRN,fr=B.11.11.13,fa=HP-UX_B.11.11_64,v=HP
IETHER-DRV.IETHER-KRN,fr=B.11.11.14,fa=HP-UX_B.11.11_64,v=HP
IETHER-DRV.IETHER-RUN,fr=B.11.11.04,fa=HP-UX_B.11.11_64,v=HP
IETHER-DRV.IETHER-RUN,fr=B.11.11.05,fa=HP-UX_B.11.11_64,v=HP
IETHER-DRV.IETHER-RUN,fr=B.11.11.07,fa=HP-UX_B.11.11_64,v=HP
IETHER-DRV.IETHER-RUN,fr=B.11.11.09,fa=HP-UX_B.11.11_64,v=HP
IETHER-DRV.IETHER-RUN,fr=B.11.11.11,fa=HP-UX_B.11.11_64,v=HP
IETHER-DRV.IETHER-RUN,fr=B.11.11.13,fa=HP-UX_B.11.11_64,v=HP
IETHER-DRV.IETHER-RUN,fr=B.11.11.14,fa=HP-UX_B.11.11_64,v=HP
Automatic Reboot?: Yes
Status: General Release
Critical:
Yes
PHNE_36237: HANG PANIC
PHNE_32251: PANIC HANG ABORT
PHNE_31153: HANG PANIC
PHNE_29947: HANG PANIC
Category Tags:
defect_repair hardware_enablement general_release critical
panic halts_system
Path Name: /hp-ux_patches/s700_800/11.X/PHNE_36237
Symptoms:
PHNE_36237:
1. ( SR: 8606480881 CR: JAGag34933 )
Under certain high traffic conditions, iether PCI-X
controllers may hang.
2. ( SR: 8606480892 CR: JAGag34942 )
The supported ranges for the send_max_bufs and
recv_max_bufs parameters are incorrectly specified in
/etc/rc.config.d/hpietherconf file.
3. ( SR: 8606490234 CR: JAGag42694 )
The asset tag in the VPD could not be changed/updated by
the user.
4. ( SR: 8606492564 CR: JAGag44735)
Under very low traffic conditions, delays are seen in
processing packets on some of the multi-port network
interface-cards (like AB290A and AB545A). Typically ping
and NFS applications suffer this type of a delay.
Retransmissions may be seen when the protocols has such
capabilities (TCP applications or applications like NFS).
For example when MTU is configured at 1500, and a ping of
size 6000 or 9000 bytes is requested, a delay of up to 1
sec has been observed in a few of the ping responses.
5. ( SR: 8606459418 CR: JAGag15548 )
The inbound discard counter is not incremented in the case
when the driver uses copymsg to make a copy of fragment
chain of a loopback packet, which is sent by this card and
destined to broadcast or multicast, and the copymsg fails
for the fragment chain.
6. ( SR: 8606462165 CR: JAGag18057 )
The loopback packets, which are sent by the card and
destined to broadcast, multicast, or its own mac address,
are not counted in the Inbound octets counter in mibstats.
7. ( SR: 8606462689 CR: JAGag18545 )
AD331A iether interface card may report FCS errors under
heavy traffic conditions.
8. ( SR: 8606472222 CR: JAGag27118 )
Due to changes in APA, the reset phase executed by the card
causes the reuse of the freed buffer.
9. ( SR: 8606475976 CR: JAGag30277 )
The driver did not verify the EEPROM checksum which can
lead to errors if the EEPROM is invalid.
10. ( SR: 8606492479 CR: JAGag44650 )
Switches may disable the switch ports to which A7011A or
AD332A cards are connected to, if the cards experience
multiple link-flaps (link up/down events) in short
duration of time after system reboot or power cycle.
This behavior has been observed with Cisco Catalyst 4500
series and Cisco Catalyst 6500 series switches so far.
11. ( SR: 8606440200 CR: JAGaf98099 )
iether driver does not display card's MDC using lanadmin
command.
12. ( SR: 8606443267 CR: JAGag00939 )
TCP packets whose checksum is 0x0000 are transmitted with a
checksum 0xffff resulting in possible rejection by the non
HP-UX remote host. This behavior is only seen when the
transmit checksum offload is turned on.
13. ( SR: 8606492566 CR: JAGag44737 )
Multiple simultaneous reset operations of an iether driven
interface card under heavy traffic conditions may result in
system panic (MCA).
14. ( SR: 8606492587 CR: JAGag44758 )
CIMProvider/LANProvider and other user applications cannot
retrieve Vital Product Data (VPD) of an iether device.
PHNE_34742:
1. ( SR: 8606436847 CR: JAGaf95094 )
Under very low inbound traffic rates, ping command with
iether and SCSI combo card, AB290 could experience slight
delay
PHNE_32251:
1. ( SR: 8606357647 CR: JAGaf18347 )
With heavy UDP traffic, an iether interface may encounter
a large number of Outbound Discards, causing throughput
degradation.
2. ( SR: 8606406733 CR: JAGaf66639 )
The netfmt(1M) "nice" option formats IETHER subsystem nettl
(1M) trace files both in nice format and raw format.
3. ( SR: 8606406289 CR: JAGaf66197 )
The iether driver does not support RFC 2863 compliant
64-bit MIB statistics.
4. ( SR: 8606397272 CR: JAGaf57254 )
Setting Jumbo MTU on an interface that is currently LINK
DOWN fails though the interface may later come up at 1000
Mbps.
5. ( SR: 8606395574 CR: JAGaf55583 )
Under certain circumstances, an iether driver may not copy a
broadcast packet to the local host when it is transmitted
over an interface configured with VLAN.
6. ( SR: 8606368522 CR: JAGaf29084 )
netfmt(1M) when invoked with the "nice" option may core
dump when attempting to format IETHER subsystem nettl(1M)
traces.
7. ( SR: 8606415353 CR: JAGaf75207 )
iether driver interfaces report Deferred Transmissions in
full-duplex mode, conflicting with user perception that
deferred transmissions can only occur in half-duplex mode.
8. ( SR: 8606409332 CR: JAGaf69228 )
The iether driver prints an unnecessary LINK DOWN NetTL
ERROR message during the Resume operation.
9. ( SR: 8606411269 CR: JAGaf71151 )
Under rare conditions, iether driver interfaces may
experience a flurry of interrupts during boot, causing the
system to hang.
10.( SR: 8606393080 CR: JAGaf53139 )
Outbound Discards (ifOutDiscards) MIB counter is not being
updated by the driver to reflect transmit frames dropped by
the card because of lack of space.
11.( SR: 8606421138 CR: JAGaf80967 )
In an unlikely event that a hardware error occurs on a
Gigabit Ethernet controller, the checksum computation
that is offloaded to the controller may cause a frame
to be transmitted with incorrect contents which may be
accepted by the receiver as valid data.
12.( SR: 8606429128 CR: JAGaf88594 )
Some vPar configurations with more than 4GB memory could
cause system panic. The stack trace could look like the
one below:
iether_ilan_trace+0xc4
iether_do_attach+0x32c
iether_attach+0x24
run_attach+0x2c
wsio_claim+0x1a8
pci_cdio_config+0xac
gio_scan_subtree+0xf0
gio_scan_subtree_real+0x18c
gio_scan_subtree+0x270
gio_scan_subtree_real+0x18c
gio_scan_subtree+0x270
gio_scan_subtree_real+0x18c
gio_scan_subtree+0x270
gio_scan_subtree_real+0x18c
PHNE_31153:
1. ( SR: 8606319198 CR: JAGae81688 )
The commands lanadmin -x speed <ppa>, lanadmin -x fctrl
<ppa> and lanadmin -x <ppa> return "ERROR: Could not
process request" for non-root users.
2. ( SR: 8606361203 CR: JAGaf21893 )
The MIB statistic "ifOutQlen" of an iether interface may
overcount the number of outstanding packets to be
transmitted.
3. ( SR: 8606361432 CR: JAGaf22122 )
When IEtherenh-00 product is installed (Enables TCP
segmentation offload), the driver might drop packets
under certain circumstances resulting in TCP
retransmissions.
4. ( SR: 8606366309 CR: JAGaf26913 )
Suspend/Resume/Reset operation on iether interface
while the interface is being used for data traffic
might cause system panic.
Stack Trace:
iether_recv+0xe0
iether_isr+0x2e0
sapic_interrupt+0x70
external_interrupt+0xc90
bubbledown+0x0
tracer_return_to_c_func+0x110
5. ( SR: 8606387043 CR: JAGaf47196 )
Resetting/Resuming the iether interface during data
traffic might cause system panic.
Stack Trace:
iether_recv+0x3a0
iether_isr+0x88
sapic_interrupt+0x34
mp_ext_interrupt+0x458
ihandler+0x91c
6. ( SR: 8606365664 CR: JAGaf26294 )
The iether interface may hang during heavy traffic.
7. ( SR: 8606385994 CR: JAGaf46148 )
In an unlikely event that a hardware error occurs on a
Gigabit Ethernet controller, the checksum computation
that is offloaded to the controller might not catch and
discard incorrect data in a received frame.
8. ( SR: 8606359784 CR: JAGaf20480 )
Errors during initialization of an iether interface may
cause system panic.
PHNE_29947:
1. ( SR: 8606342571 CR: JAGaf03465 )
When a large number of multicast addresses are enabled on an
interface, an application retrieving the multicast list from
that interface may see an incomplete list or incorrect
addresses.
2. ( SR: 8606338266 CR: JAGae99228 )
An iether interface may incorrectly drop padded TCP/UDP
packets that are <= 60 bytes long. The checksum failures
(reported by 'netstat') may cause some applications to
hang.
3. ( SR: 8606356446 CR: JAGaf17154 )
An iether interface may incorrectly drop padded TCP/UDP
packets that are > 60 bytes long. The checksum failures
(reported by 'netstat') may cause some applications to
hang.
4. ( SR: 8606333258 CR: JAGae94353 )
Link may hang during Jumbo Frame Traffic.
5. ( SR: 8606340381 CR: JAGaf01300 )
Receive checksum failures may result with Jumbo MTU.
6. ( SR: 8606344393 CR: JAGaf05243 )
iether interfaces show low TCP/UDP request/response rate.
7. ( SR: 8606346136 CR: JAGaf06963 )
The system might panic(Data TLB Fault) during iether
interface card initialization.
Stack Trace:
IP Function Name
0xe0000000004f5520 post_hndlr+0xc20
0xe0000000004f9240 vm_hndlr+0x220
0xe000000001085780 bubbledown
0xe0000000004fe550 kfree+0x130
0xe000000000baa2a0 iether_ilan_initialize+0x1770
0xe000000000ba82d0 iether_ilan_init+0x840
0xe000000000778c30 wsio_claim+0x730
0xe0000000007e6460 pci_cdio_init+0x11f0
0xe00000000094bd30 io_scan+0x1270
0xe00000000094c0c0 gio_scan_subtree_real+0x1f0
0xe00000000094ba80 io_scan+0xfc0
0xe00000000094c0c0 gio_scan_subtree_real+0x1f0
0xe00000000094ba80 io_scan+0xfc0
0xe00000000094c0c0 gio_scan_subtree_real+0x1f0
0xe00000000094ba80 io_scan+0xfc0
0xe00000000094adc0 io_scan+0x300
0xe000000000961e60 dev_config_install+0x1740
0xe0000000003696b0 prop_get+0xf70
0xe0000000006fdb70 spec_ioctl+0x1d0
8. ( SR: 8606349728 CR: JAGaf10547 )
Hooks to support TCP Segmentation Offload(TSO) Enhancement
product are not present.
9. ( SR: 8606274100 CR: JAGae38178 )
The ioscan description string does not display the part
number and interface type (e.g., "Adapter", "Core" etc).
10. ( SR: 8606354363 CR: JAGaf15157 )
The system might panic (Data TLB fault) after resetting
the iether interface card.
Stack Trace:
panic+0xa0
lwp_sa_procinit_stub32+0x33db4
interrupt+0x208
$ihndlr_rtn+0x0
iether_recv+0x13c
iether_isr+0x120
sapic_interrupt+0x2c
mp_ext_interrupt+0x3c0
ivti_patch_to_nop3+0x0
idle+0x9f0
swidle_exit+0x0
Defect Description:
PHNE_36237:
1. ( SR: 8606480881 CR: JAGag34933 )
During heavy load, the controller stops mastering the
PCI-X bus, resulting in the hang.
Resolution:
The driver has been modified to detect the hang and to
reset the controller to clear the hang. Additionally, after
the reset to clear the hang, the driver starts limiting
the size of each frame's transmit DMA buffer(s) to 512
bytes in an attempt to prevent future occurrences of the
hang. Optionally, users can force the driver to limit the
transmit buffer size to 512 bytes, independent of the
hang detection and reset mechanism, using the 'lanadmin
-X tx512_bufs <value> <ppa>' command or by setting the
HP_IETHER_TX_512B_BUF parameter in
the /etc/rc.config.d/hpietherconf to 1.
2. ( SR: 8606480892 CR: JAGag34942 )
The maximum value for send_max_bufs and recv_max_bufs
on iether PCI-X based cards is "63" and not "64".
Resolution:
The incorrect range for send_max_bufs and recv_max_bufs
has been corrected in the iether driver. It has also been
fixed in the /etc/rc.config.d/hpietherconf file. In
addition, the help text for the following parameters
- HP_IETHER_SEND_COAL_TICKS
- HP_IETHER_RECV_COAL_TICKS
- HP_IETHER_SEND_MAX_BUFS
- HP_IETHER_RECV_MAX_BUFS
has been modified to provide additional information.
3. ( SR: 8606490234 CR: JAGag42694 )
iether driver did not allow modification of the asset tag.
Resolution: The iether driver has been modified to allow
changing the asset tag in the VPD. This can be done using
the lanadmin command "lanadmin -X write_asset_tag <value>
<ppa>".
4. ( SR: 8606492564 CR: JAGag44735 )
iether driver acknowledges the interrupts asynchronously
in order to reduce CPU utilization and improve
performance. However, this mechanism might delay
processing of frames especially during slow traffic
situations.
Resolution:
iether driver is modified to acknowledge the interrupts
from the interface card synchronously to avoid delays in
processing the received frames.
5. ( SR: 8606459418 CR: JAGag15548 )
In the case of loopback packets, which are sent by the
card and destined to broadcast or multicast, driver makes
a copy of fragment chain using copymsg. If the copymsg
fails for the fragment chain, these packets are silently
discarded without incrementing the inbound discard counter.
Resolution: iether driver now increments the inbound
discard counter for this case.
6. ( SR: 8606462165 CR: JAGag18057 )
The current ilan_ift data structure does not have any
field to accommodate this counter for loopback packets.
Resolution: Add InOctets counters for loopback packets in
ilan_ift structure and increment InOctets counters for the
loopback Packets.
7. ( SR: 8606462689 CR: JAGag18545 )
Additional controller settings are required for a reset
operation. Otherwise, FCS errors might result during heavy
traffic conditions.
Resolution: iether driver is modified to perform
appropriate controller settings prior to resetting the
controller.
8. ( SR: 8606472222 CR: JAGag27118 )
This panic is due to incorrect access of the data
structure in the iether driver.
Resolution: The iether driver has been modified to access
the data structure correctly.
9. ( SR: 8606475976 CR: JAGag30277 )
EEPROM checksum validation was not done by the driver
which made finding errors in the EEPROM difficult.
Resolution: EEPROM validation is now done by the driver
which makes detecting errors in the EEPROM easier.
10. ( SR: 8606492479 CR: JAGag44650 )
A7011A with EDC B-4628 and AD332A with EDC 1-4628 are
susceptible to noise during reboot or power cycle due to
incorrect EEPROM settings.
Resolution: This issue can be fixed by updating the EEPROM
content on the card. A script is available to fix the
EEPROM content on the following adapters
1. A7011A with EDC B-4628
2. AD332A with EDC 1-4628
A7011A adapters with EDC's prior to B-4628 are not
impacted. And also, A7011A with EDC later than B-4628 and
AD332A adapter with EDC's later than 1-4628 do not require
the script to be executed. These later EDCs have had the
needed EEPROM update performed during manufacturing.
This patch provides the capability to update the EEPROM
content on the card. Please contact HP support for
the "eeflip.sh" script file.
11. ( SR: 8606440200 CR: JAGaf98099 )
MDC information is available in the card's VPD in the
EEPROM. iether driver did not retrieve this information
from the card's VPD.
Resolution: iether driver has been modified to display
card's MDC. The MDC of the card can be viewed by
using "lanadmin -x vpd <ppa>" command.
12. ( SR: 8606443267 CR: JAGag00939 )
iether driver is not setting the packet type as TCP and
hence card assumes it as UDP and converts a 0x0000
checksum to 0xffff which might be considered as checksum
error by the receiving hosts.
Resolution: iether driver is modified to set the packet
type appropriately in order for the card to compute
checksum for all types of packets correctly.
13. ( SR: 8606492566 CR: JAGag44737 )
A race condition between the reset operation and data
transfer can cause system crash (MCA).
Resolution: iether driver is modified to synchronize the
reset and data transfer operations to reduce the
probability of the card accessing the host memory that was
freed by the system.
14. ( SR: 8606492587 CR: JAGag44758 )
iether driver did not provide a mechanism to access the
Vital Product Data (VPD) of the card for the user
applications.
Resolution: iether driver is modified to allow
applications to access the Vital Product Data (VPD) of the
device. The VPD can also be retrieved using lanadmin -x
vpd <#ppa>.
PHNE_34742:
1. ( SR: 8606436847 CR: JAGaf95094 )
The iether driver might delay reading an incoming packet
under very low traffic conditions. For example, a slight
delay might be seen while executing ping command.
Resolution:
Driver is modified to read incoming packets immediately.
PHNE_32251:
1. ( SR: 8606357647 CR: JAGaf18347 )
The driver was not processing transmit completions in a
timely fashion, resulting in transmit queue overrun. Sub-
gigabit speeds and lower PCI bus speeds may aggravate this
problem.
Resolution:
The iether driver has been modified to process transmit
completions more often to avoid overruns.
2. ( SR: 8606406733 CR: JAGaf66639 )
The iether driver subsystem formatter incorrectly returns
failure after successfully performing nice formatting,
causing it to be called a second time to do raw formatting.
Resolution:
The iether driver now returns success when nice formatting
completes without errors.
3. ( SR: 8606406289 CR: JAGaf66197 )
The driver did not support 64-bit MIB statistics earlier.
Resolution:
The driver now support 64-bit MIB statistics.
4. ( SR: 8606397272 CR: JAGaf57254 )
The driver adopted a conservative approach of not allowing
setting Jumbo MTU if the link is down because of the
possibility of the link coming up at 10/100 Mbps, speeds at
which Jumbo MTU is not supported.
Resolution:
The driver will now allow setting Jumbo MTU when the link
is down unless the user-requested speed is 10/100 Mbps.
5. ( SR: 8606395574 CR: JAGaf55583 )
The driver failed to set a necessary flag in the VLAN
broadcast packet that is required to loop back the packet.
Resolution:
The iether driver is modified to set the necessary flag.
6. ( SR: 8606368522 CR: JAGaf29084 )
The iether driver is not passing the right number of
parameters while invoking formatter's subsystem function
in "nice" mode.
Resolution:
The iether driver has been modified to pass in all the
arguments to the formatter subsystem.
7. ( SR: 8606415353 CR: JAGaf75207 )
In full-duplex mode, the device adds to the Deferred
Transmissions counter, the number of times a frame's
transmission was delayed due to flow-control.
Resolution:
The iether driver has been modified not to count deferred
transmissions when operating in full-duplex mode.
8. ( SR: 8606409332 CR: JAGaf69228 )
The iether driver was not marking the interface as down
during the Suspend operation, resulting in the detection of
a false link state change during the subsequent Resume
operation.
Resolution:
The iether driver has been modified to avoid printing the
unnecessary LINK DOWN error message during Resume operation.
9. ( SR: 8606411269 CR: JAGaf71151 )
Due to the algorithm used in the iether driver, if a link
state change interrupt occurs during early boot, it may go
unacknowledged indefinitely, causing an interrupt flurry
which may halt boot progress.
Resolution:
The iether driver's interrupt service routine was modified
to handle and acknowledge a link state change in a timely
manner during boot.
10.( SR: 8606393080 CR: JAGaf53139 )
The driver was not adding to Outbound Discards
(ifOutDiscards), frames that were discarded due to lack of
space.
Resolution:
The driver is modified to update the Outbound Discards
(ifOutDiscards) MIB counter with the number of the packets
dropped because of lack of space.
11.( SR: 8606421138 CR: JAGaf80967 )
Checksum Offload (CKO) is a performance feature that
alleviates the burden of TCP checksum computation from
the host CPU by offloading the computation to the card.
Changes have been implemented to disable the CKO feature
on iether interfaces by default, but an option is
provided to allow administrators to turn the feature
ON or OFF.
Resolution:
There are two separate control flags that
enable you to turn CKO ON or OFF, one for the transmit
side and one for the receive side. These flags are
configurable via the HP-UX lanadmin -X command or by
editing the config file, /etc/rc.config.d/hpietherconf.
The new parameters for the config file are
HP_IETHER_SEND_CKO and HP_IETHER_RECV_CKO. The default
CKO for transmit and receive is now set to OFF. Note
that the default behavior has changed from the previous
driver version. See "Special Installation Instructions" for
how to restore the previous behavior.
12.( SR: 8606429128 CR: JAGaf88594 )
The iether driver is using an incorrect parameter type,
which could cause system crash with some vPar
configurations.
Resolution:
iether driver is modified to use the correct parameter type.
PHNE_31153:
1. ( SR: 8606319198 CR: JAGae81688 )
The IOCTL used to retrieve speed and flow control
information from the driver is errored back by the
kernel for non-root users.
Resolution:
To retrieve speed and flow control from the driver,
lanadmin now uses a new IOCTL for which the kernel
does not perform superuser checks. This patch "ONLY"
pre-enables the fix. The fix will be fully enabled
when the LAN Products cumulative patch, PHNE_32396,
is installed along with this patch.
2. ( SR: 8606361203 CR: JAGaf21893 )
For ifOutQlen, iether is reporting the number of hardware
descriptors queued at the controller. Since there could
be more than one descriptor per packet there is a
possibility of overcounting.
Resolution:
The driver is modified such that the MIB ifOutQlen of
an interface now holds the number of outstanding packets
in the transmit queue.
3. ( SR: 8606361432 CR: JAGaf22122 )
The iether driver discards an outbound packet if its
protocol header (Ethernet, IP or TCP) spans multiple
descriptors because the iether device cannot handle
such packets.
Resolution:
The driver was modified to coalesce packets that have
protocol headers spanning multiple descriptors.
4. ( SR: 8606366309 CR: JAGaf26913 )
Under certain circumstances iether was not checking for
a valid driver state before processing received packets.
Resolution:
iether ensures that the driver state is valid before
processing the received packets.
5. ( SR: 8606387043 CR: JAGaf47196 )
The reset/resume operation on the iether interface
causes the receive buffers to be replenished. There
is a possibility that a packet could be received and
processed while the receive buffers are being
replenished, which is inappropriate and could lead to
system panic.
Resolution:
Avoid replenishing the receive buffers as part of reset
operation.
6. ( SR: 8606365664 CR: JAGaf26294 )
The transmit and receive descriptor control settings for
the device were programmed incorrectly by the driver.
Resolution:
The transmit and receive descriptor control settings
have been rectified.
7. ( SR: 8606385994 CR: JAGaf46148 )
Checksum Offload (CKO) is a performance feature that
alleviates the burden of TCP checksum computation from
the host CPU by offloading the computation to the card.
Changes have been implemented to allow administrators
to turn ON or OFF the CKO feature. Notice that the
checksum validation is always performed by the transport
layer using the computed checksum regardless whether the
CKO is ON or OFF.
Resolution: There are two separate control flags that enable
you to turn CKO ON or OFF, one for the transmit side and
one for the receive side. These flags are configurable
via the HP-UX lanadmin -X command or by editing the
config file, /etc/rc.config.d/hpietherconf. The new
parameters for the config file are HP_IETHER_SEND_CKO
and HP_IETHER_RECV_CKO. The default CKO for transmit is
set to ON. The default CKO for receive is set to OFF.
Note that the default behavior has changed from the
previous driver. See "Special Installation Instructions"
for how to restore the previous behavior.
8. ( SR: 8606359784 CR: JAGaf20480 )
In the error path, the driver was attempting to free an
uninitialized data structure before it was allocated.
Resolution:
The driver now verifies that the data structure is
allocated before attempting to free it.
PHNE_29947:
1. ( SR: 8606342571 CR: JAGaf03465 )
When an application tries to retrieve the list of multicast
addresses enabled on an interface, the driver may return a
truncated list if the number of addresses enabled is huge,
resulting in potential application data corruption.
Resolution:
The driver has been modified to return correct and complete
multicast addresses list.
2. ( SR: 8606338266 CR: JAGae99228 )
The iether driver incorrectly included Ethernet pad bytes
during checksum computation of received TCP/UDP packets. If
a TCP/UDP packet received from the network has non-zero
padding, the computed checksum is incorrect and the packet
is dropped.
Resolution:
The iether driver has been modified to not include Ethernet
pad bytes, if any, during checksum computation of TCP/UDP
frames received from the network.
3. ( SR: 8606356446 CR: JAGaf17154 )
The driver was assuming that frames > 60 bytes are not
padded.
Resolution:
The driver has been modified to read the total length
field in the IP header to determine if a frame is padded
or not.
4. ( SR: 8606333258 CR: JAGae94353 )
Under certain conditions, the send and receive engines on
the controller may hang.
Resolution:
The driver has been modified to avoid the condition leading
to the controller hang.
5. ( SR: 8606340381 CR: JAGaf01300 )
The driver was violating the controller specification on
where to read a Jumbo frame's receive checksum.
Resolution:
Checksum for received Jumbo Frames will now be read from
the correct location.
6. (SR: 8606344393 CR: JAGaf05243 )
During certain request/response type traffic conditions,
the iether driver was missing receive interrupts that
resulted in packets being handled after a long delay.
Resolution:
iether has been modified to prevent delayed handling of
received packets.
7. (SR: 8606346136 CR: JAGaf06963 )
The driver was attempting to free a non-existent buffer
in an initialization error path.
Resolution:
The driver has been modified to avoid freeing an
unallocated buffer.
8. (SR: 8606349728 CR: JAGaf10547 )
The driver did not have hooks to support the TCP
Segmentation Offload (TSO) feature.
Resolution:
Hooks to support TSO have been added.
9. ( SR: 8606274100 CR: JAGae38178 )
The driver did not implement the enhanced ioscan string.
Resolution:
Part number and additional information about an iether
interface have been added to the ioscan string.
10. ( SR: 8606354363 CR: JAGaf15157 )
The driver was accessing the buffer from a stale
receive descriptor.
Resolution:
The driver has been modified to avoid accessing the
stale buffers.
Enhancement:
No
SR:
8606342571 8606338266 8606356446 8606333258 8606340381
8606344393 8606346136 8606349728 8606274100 8606354363
8606319198 8606361203 8606361432 8606366309 8606387043
8606365664 8606385994 8606359784 8606357647 8606406733
8606406289 8606397272 8606395574 8606368522 8606415353
8606409332 8606411269 8606393080 8606421138 8606429128
8606436847 8606480881 8606480892 8606490234 8606492564
8606459418 8606462165 8606462689 8606472222 8606475976
8606492479 8606440200 8606443267 8606492566 8606492587
Patch Files:
IETHER-DRV.IETHER-KRN,fr=B.11.11.04,fa=HP-UX_B.11.11_64,
v=HP:
IETHER-DRV.IETHER-KRN,fr=B.11.11.05,fa=HP-UX_B.11.11_64,
v=HP:
IETHER-DRV.IETHER-KRN,fr=B.11.11.07,fa=HP-UX_B.11.11_64,
v=HP:
IETHER-DRV.IETHER-KRN,fr=B.11.11.09,fa=HP-UX_B.11.11_64,
v=HP:
IETHER-DRV.IETHER-KRN,fr=B.11.11.11,fa=HP-UX_B.11.11_64,
v=HP:
IETHER-DRV.IETHER-KRN,fr=B.11.11.13,fa=HP-UX_B.11.11_64,
v=HP:
IETHER-DRV.IETHER-KRN,fr=B.11.11.14,fa=HP-UX_B.11.11_64,
v=HP:
/usr/conf/lib/libiether.a
IETHER-DRV.IETHER-RUN,fr=B.11.11.04,fa=HP-UX_B.11.11_64,
v=HP:
IETHER-DRV.IETHER-RUN,fr=B.11.11.05,fa=HP-UX_B.11.11_64,
v=HP:
IETHER-DRV.IETHER-RUN,fr=B.11.11.07,fa=HP-UX_B.11.11_64,
v=HP:
IETHER-DRV.IETHER-RUN,fr=B.11.11.09,fa=HP-UX_B.11.11_64,
v=HP:
IETHER-DRV.IETHER-RUN,fr=B.11.11.11,fa=HP-UX_B.11.11_64,
v=HP:
IETHER-DRV.IETHER-RUN,fr=B.11.11.13,fa=HP-UX_B.11.11_64,
v=HP:
IETHER-DRV.IETHER-RUN,fr=B.11.11.14,fa=HP-UX_B.11.11_64,
v=HP:
/usr/lib/lanadmin/libdsiether.1
/usr/lib/libfmiether.1
/usr/lib/nls/msg/C/dsiether.cat
/usr/lib/nls/msg/C/fmiether.cat
/sbin/init.d/hpiether
/usr/newconfig/etc/rc.config.d/hpietherconf
what(1) Output:
IETHER-DRV.IETHER-KRN,fr=B.11.11.04,fa=HP-UX_B.11.11_64,
v=HP:
/usr/conf/lib/libiether.a:
iether_ilan Version: 1 Jun 18 2007
iether Revision: PHNE_36237 B.11.11.15 Jun 18 2007
IETHER-DRV.IETHER-RUN,fr=B.11.11.04,fa=HP-UX_B.11.11_64,
v=HP:
/usr/lib/lanadmin/libdsiether.1:
$Revision: jazz @ 20070618.17:51:53PDT; jmkvw -proj
lan -RW -c Task: phne_36237 braghave_phne_36
237 r11.11(R11.11_BL2007_0516) cup2_braghave
_phne_36237(auto) ;
/usr/lib/libfmiether.1:
$Revision: jazz @ 20070321.03:16:10PDT; jmkvw -proj
integ -RW -share -c Vw for R11.11_BL2007_032
0 build r11.11_bl2007_0320 r11.11(R11.11_BL2
007_0320) ;
/usr/lib/nls/msg/C/dsiether.cat:
None
/usr/lib/nls/msg/C/fmiether.cat:
None
/sbin/init.d/hpiether:
None
/usr/newconfig/etc/rc.config.d/hpietherconf:
hpietherconf $Revision: 1.1 $ 06/12/07 - B.11.11.15
- PHNE_36237
cksum(1) Output:
IETHER-DRV.IETHER-KRN,fr=B.11.11.04,fa=HP-UX_B.11.11_64,
v=HP:
3375149949 652358 /usr/conf/lib/libiether.a
IETHER-DRV.IETHER-RUN,fr=B.11.11.04,fa=HP-UX_B.11.11_64,
v=HP:
437154279 200704 /usr/lib/lanadmin/libdsiether.1
846856563 20480 /usr/lib/libfmiether.1
1992569616 12769 /usr/lib/nls/msg/C/dsiether.cat
1853477058 4537 /usr/lib/nls/msg/C/fmiether.cat
2032474821 12290 /sbin/init.d/hpiether
3285638521 6818 /usr/newconfig/etc/rc.config.d/hpietherconf
Patch Conflicts: None
Patch Dependencies:
s700: 11.11: PHNE_32396
s800: 11.11: PHNE_32396
Hardware Dependencies: None
Other Dependencies: None
Supersedes:
PHNE_34742 PHNE_32251 PHNE_31153 PHNE_29947
Equivalent Patches: None
Patch Package Size: 320 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 PHNE_36237
5. Run swinstall to install the patch:
swinstall -x autoreboot=true -x patch_match_target=true \
-s /tmp/PHNE_36237.depot
By default swinstall will archive the original software in
/var/adm/sw/save/PHNE_36237. 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 PHNE_36237.text file is
available in the product readme:
swlist -l product -a readme -d @ /tmp/PHNE_36237.depot
To put this patch on a magnetic tape and install from the
tape drive, use the command:
dd if=/tmp/PHNE_36237.depot of=/dev/rmt/0m bs=2k
Special Installation Instructions:
The fix for JAGaf46148(8606385994) adds new parameters to
the hpietherconf file. The updated file is delivered in
the new /usr/newconfig/etc/rc.config.d/hpietherconf file.
If you wish to use the new file, merge the
contents of the existing /etc/rc.config.d/hpietherconf
with the new file.
There are two ways to change the CKO setting, via lanadmin
-X command and the (SEND/RECV)_CKO variables in the
config file.
In previous versions of the driver, the CKO defaults were
different and equivalent to CKO ON for both the transmit
and receive sides. To achieve these same settings with this
driver, set both HP_IETHER_SEND_CKO and HP_IETHER_RECV_CKO
to ON in the /etc/rc.config.d/hpietherconf file. The
previous defaults will then be permanently in effect after
the next reboot.
The same setting can be achieved temporarily by using the
lanadmin -X command. The lanadmin commands are:
lanadmin -X send_cko_on <ppa>
lanadmin -X recv_cko_on <ppa>
The fix for JAGag34942 (SR 8606480892) modifies the help
text for the following parameters.
1. HP_IETHER_SEND_COAL_TICKS
2. HP_IETHER_RECV_COAL_TICKS
3. HP_IETHER_SEND_MAX_BUFS
4. HP_IETHER_RECV_MAX_BUFS
The updated file is delivered in the
path /usr/newconfig/etc/rc.config.d/hpietherconf. If you
wish to use the new updated file, merge the contents of
the existing /etc/rc.config.d/hpietherconf with the new
file.
The fix for JAGag34933 (SR 8606480881) involves adding
a new parameter in the hpietherconf file. The updated
hpietherconf file is delivered
in /usr/newconfig/etc/rc.config.d directory. The new
parameter is HP_IETHER_TX_512B_BUF and its default value is
0. To enable 512 byte maximum transmit buffer size limit,
user needs to set the value of HP_IETHER_TX_512B_BUF
parameter to 1. In order to do so, user needs to merge the
contents of the existing /etc/rc.config.d/hpietherconf
file with the new file. Please note that once you have
merged and enabled HP_IETHER_TX_512B_BUF, it will be
persistent across reboots. This parameter is only
applicable for iether PCI-X interfaces.
|
