|
Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com |
From: IT Resource Center (support_feedback
us-support.external.hp.com)Date: Sun Oct 28 2001 - 09:40:37 CST
HP Support Information Digests
===============================================================================
o IT Resource Center World Wide Web Service
---------------------------------------------------
If you subscribed through the IT Resource Center and would
like to be REMOVED from this mailing list, access the
IT Resource Center on the World Wide Web at:
http://www.itresourcecenter.hp.com/
Login using your IT Resource Center User ID and Password.
Then select Support Information Digests (located under
Maintenance and Support). You may then unsubscribe from the
appropriate digest.
To download a patch referenced below, access the
IT Resource Center on the World Wide Web at:
http://www.itresourcecenter.hp.com/
Login using your IT Resource Center User ID and Password.
Then select Individual Patches (under Maintenance and Support)
to access the patch. You may also download a patch via anonymous
ftp(1) from ftp.itrc.hp.com.
===============================================================================
Digest Name: weekly HP-UX series 700 11.X patch digest
Created: Sun Oct 28 3:05:21 PST 2001
Table of Contents:
Document ID Title
--------------- -----------
PHNE_25079 s700_800 11.04 (VVOS) telnet kernel and telnetd(1M) patch
PHNE_25076 s700_800 11.04 (VVOS) LAN product cumulative patch
PHNE_25073 s700_800 11.04 (VVOS) 4 port PCI 100BT cumulative patch
PHNE_25072 s700_800 11.04 (VVOS) PCI 100BT lan cumulative patch
PHNE_25070 s700_800 11.04 (VVOS) EISA 100BT patch
PHNE_25069 s700_800 11.04 (VVOS) patch for EISA 100VG-AnyLAN product
PHKL_25453 s700_800 11.11 early boot, Psets, vPar, Xserver core dumps
PHKL_25154 s700_800 11.04 (VVOS) PCI cumulative patch
PHKL_25055 s700_800 11.04 (VVOS) Cumulative gang scheduling patch
PHKL_25054 s700_800 11.04 (VVOS) VxFS 3.1 cumulative patch
PHKL_25048 s700_800 11.04 (VVOS) SCSI IO Subsystem Cumulative Patch
PHKL_25047 s700_800 11.04 (VVOS) panic, fails for coredump, drivers
PHKL_25039 s700_800 11.04 (VVOS) Directed range,PIOP,PAT.
PHKL_25035 s700_800 11.04 (VVOS) syscall, msem_lock, umask cumulative
PHCO_25061 s700_800 11.04 (VVOS) LVM commands cumulative patch
PHCO_24693 s700_800 11.00 more(1) patch
PHSS_25521 s700_800 11.X Fortran90 from B.11.01.40 to B.11.01.45
PHCO_25527 s700_800 11.00 libpam and libpam_unix cumulative patch
PHNE_24307 s700_800 11.00 1000Base-SX/T B.11.00.[02-11] cumul. patch
PHCO_24692 s700_800 11.00 /usr/lbin/getNAME patch
PHSS_25517 s700_800 11.00 OV SA1.0X Consolidated Patch Oct2001
PHSS_25474 s700_800 11.20 B6061AA MLIB 8.0 Cumulative Patch
PHKL_25506 s700_800 11.11 asyncio driver patch
PHCO_24942 s700_800 11.11 libc cumulative patch
PHSS_24827 s700_800 11.00 Predictive C.11.AA cumulative patch
PHNE_25078 s700_800 11.04 (VVOS) arp(1M) patch
PHNE_25075 s700_800 11.04 (VVOS) Streams Pty cumulative patch
PHKL_25525 s700_800 11.00 Probe,IDDS,PM,VM,PA-8700,asyncio,T600,FS
PHKL_25475 s700_800 11.00 PM cumulative patch
PHKL_25053 s700_800 11.04 (VVOS) FCMS Driver Patch
PHKL_25049 s700_800 11.04 (VVOS) JFS 3.1 cuml corruption and panic fix
The documents are listed below.
-------------------------------------------------------------------------------
Document ID: PHNE_25079
Date Loaded: 20011026
Title: s700_800 11.04 (VVOS) telnet kernel and telnetd(1M) patch
Patch Name: PHNE_25079
Patch Description: s700_800 11.04 (VVOS) telnet kernel and telnetd(1M) patch
Creation Date: 01/10/11
Post Date: 01/10/26
Hardware Platforms - OS Releases:
s700: 11.04
s800: 11.04
Products: N/A
Filesets:
Networking.NET2-KRN,fr=B.11.04,fa=HP-UX_B.11.04_32,v=HP
Networking.NET2-KRN,fr=B.11.04,fa=HP-UX_B.11.04_64,v=HP
InternetSrvcs.INETSVCS-RUN,fr=B.11.04,fa=HP-UX_B.11.04_32/64,v=HP
OS-Core.CORE-KRN,fr=B.11.04,fa=HP-UX_B.11.04_32/64,v=HP
ProgSupport.C-INC,fr=B.11.04,fa=HP-UX_B.11.04_32/64,v=HP
InternetSrvcs.INET-ENG-A-MAN,fr=B.11.04,fa=HP-UX_B.11.04_32/64,v=HP
Automatic Reboot?: Yes
Status: General Release
Critical:
Yes
PHNE_25079: MEMORY_LEAK HANG
Based on HP-UX Patch PHNE_22159:HANG MEM_LEAK
Memory leak in telnetd
Based on HP-UX Patch PHNE_21952: HANG
Memory leak in telnetd
PHNE_23027: PANIC
Based on HP-UX Patch PHNE_20936: PANIC
If minor number exceeds boundary value system
panics.
PHNE_18907: PANIC HANG
Based on HP-UX Patch PHNE_16546: PANIC
While rebooting system, telnet caused a panic
Based on HP-UX Patch PHNE_14957: PANIC
1. There was occasional system panics due to
telnetd.
Based on HP-UX Patch PHNE_14818: PANIC
System panics with a data page fault.
Based on HP-UX Patch PHNE_14424: HANG
1.The telnet sub system completely unusable.
Category Tags:
defect_repair enhancement general_release critical panic
halts_system memory_leak
Path Name: /hp-ux_patches/s700_800/11.X/PHNE_25079
Symptoms:
PHNE_25079:
Ported HP-UX patch PHNE_22159 to VVOS
Based on HP-UX patch PHNE_22159:
SR 8606182980 / CR JAGad52196
1. telnetd does not close connection if stty 0 is given.
SR 8606176054 / CR JAGad45294
2. Memory leak as telnetd does not manage telnet queues
properly.
SR 8606157405 / CR JAGad26736
3. telnet daemon sets the pty speed to 0 if the telnet
client speed is > 38400
SR 8606114446 / CR JAGac29210
4. telnet hangs with "Reflection", a terminal emulation
software used by Windows telnet client.
SR 1653304360 / CR JAGab16743
5. Single byte write to DTC over telnet degraded by 10.20
to 11.0 update
Based on HP-UX patch PHNE_21952:
SR 8606145850 / JAGad15186:
1. Memory leak in telnetd.
PHNE_23027:
Ported HP-UX patch PHNE_21822 to VVOS
Based on HP-UX patch PHNE_21822:
SR 8606140594 / JAGad09955:
1. Telnetd connection fails intermittently with a message
in syslog which says "Baud Rate set to 0, connection
closed"
SR 8606126240 / JAGac56805:
2. Intermittent telnetd connection failure due to unflushed
pty
CR JAGab21120:
3. When a system is cold installed with May 1999 Extension
Pack(9905) and later removed, telnet stops functioning.
Based on HP-UX patch PHNE_20936:
SR 8606134274 / CR JAGab75328:
1. telnetd does not close connection if stty 0 is given.
SR 8606134275 / CR JAGab70058:
2. 11.0 telnetd: TELS/TELM driver code needs to
include flow-control checks.
SR 8606134276 / CR JAGab53771:
3. panic in telnets_open when minor number passed
is beyond nstrtel value.
SR 8606134273 / CR JAGab50706:
4. Memory leak in telnet streams module.
Based on HP-UX patch PHNE_19298:
1. Inetd gives the error message "telnet/tcp:bind:Address
already in use".
2. No help to generate telnet pty files.
PHNE_19127:
Ported HP-UX patch PHNE_18527 to VVOS
Based on HP-UX patch PHNE_18527:
1. Misaligned error messages in log files while installing
the telnetd patch PHNE_14957.
2. Bad system call in the postinstall script.
3. Backup directory should not be created under /dev/pts.
4. Backup directory should not be removed if not empty.
PHNE_18907:
Ported HP-UX patch PHNE_16546 to VVOS
Based on HP-UX patch PHNE_16546:
1. At hp-ux 11.0 telnet connections hang in connection
phase.
2. While rebooting a system, there was a panic due to
telnet.
Based on HP-UX patch PHNE_14957:
1. utmp file format limits number of telnet login sessions
to 1000.
2. Telnet should detect that the pseudo drivers telm and
tels are not in kernel.
3. telnetd displays login prompt before system id string.
4. At 11.0 there was a panic due to telnetd.
Based on HP-UX patch PHNE_14819:
1. Sending a block of data over telnet connection
causes it to close
Based on HP-UX patch PHNE_14818:
1. Telnet causes system panic in putbq telnet_route_data
on a 11.0 system.
2. memory leak in telnet.
Based on HP-UX patch PHNE_14424:
1.inetd failed to fork telnetd with the error,
"telnet/tcp: bind: Address already in use".
Defect Description:
PHNE_25079:
Ported HP-UX patch PHNE_22159 to VVOS
Based on HP-UX patch PHNE_22159:
SR 8606182980 / CR JAGad52916
1. Setting stty 0 results in zero byte msgblk which was
ignored.
Resolution:
stty 0 results in zero byte msgblk which is now processed
to close the telnet connection.
SR 8606176054 / CR JAGad45294
2. If the connection is closed while telnet is doing option
negotiation, memory is not freed.
Resolution:
Code has been modified to free memory whenever connection
is closed.
SR 8606157405 / CR JAGad26736
3. If any telnet client requests for baud rate > 38400,
the telnet daemon resets the value.
Resolution:
If any request for Baud rate arrives, which is greater
than the maximum, i.e 38400, then the telnet daemon
resets the Baud rate value to the lowest value instead
of setting it to zero.
SR 8606114446 / CR JAGac29210
4. While displaying quite large files using "Reflection",
a terminal emulation software, the application hangs.
Resolution:
Flow control has been properly enabled which solved
this problem.
SR 1653304360 / CR JAGab16743
5. With TCP_NODELAY option, single byte packets from telnetd
clogged the network.
Resolution:
Buffering is implemented in telnetd so that it no more
writes single byte packets to the network.
Based on HP-UX patch PHNE_21952:
SR 8606145850 / JAGad15186:
1. Memory chunks are not freed when telnet exits.
Resolution:
Steps have been taken to free unwanted memory and the
code has been modified accordingly.
PHNE_23027:
Ported HP-UX patch PHNE_21822 to VVOS
Based on HP-UX patch PHNE_21822:
SR 8606140594 / JAGad09955:
1. Telnetd connections occasionally get closed. This problem
is found in patch PHNE_20936 where the fix for 8606140594
generates this wrong behaviour. The fix for 8606140594
has been removed in this patch.
Resolution:
The fix for 8606140594 has been removed and the problem
is avoided.
SR 8606126240 / JAGac56805:
2. Telnetd connections intermittently failed because it
ended up using an active pty instead of procuring a
free pty.
Resolution:
The root cause was because of persistent links in the
streams. Telnetd creates only non-persistent links now
and thereby solves the problem of ending up using
same pty across different connections.
CR JAGab21120:
3. When May 1999 Extension Pack(9905) is cold installed and
later removed, telnetd looks for old device files and
since those files are not present, telnetd ceases to
work.
Resolution:
We are providing a warning in the patch script alerting
the user to run /sbin/insf manually to regenerate the
device files if for any reason the script fails to do
so and thereby avoids potential problems that could
arise because of old file names versus new file names.
Based on HP-UX patch PHNE_20936:
1. Setting stty 0 results in zero byte msgblk which was
ignored.
Resolution:
stty 0 results in zero byte msgblk which is now processed
to close the telnet connection.
2. TELS/TELM code needed flow control checks.
Resolution:
Flow control related checks have been introduced.
3. If minor number exceeds boundary value, system panics.
Resolution:
Boundary check for minor number values is introduced.
4. telnet streams module fails to free some memory.
Resolution:
Code has been modified to free unwanted allocated memory
chunks.
Based on HP-UX patch PHNE_19298:
1. As telnetd was exiting without unlinking the persistent
links, inetd was unable to spawn telnetd and
it displayed the error message.
Resolution:
The code has been modified so that telnetd unlinks all
the persistent links before exiting.
2. Patch scripts do not provide enough information to
create telnet pty files.
Resolution:
The postremove script has been modified to include
details for generating telnet pty files.
PHNE_19127:
Ported HP-UX patch PHNE_18527 to VVOS
Based on HP-UX patch PHNE_18527:
1. Error messages from the control scripts of PHNE_14957
were not properly aligned in the log files.
Resolution:
The scripts have been modified to properly align the
error messages in the log files by ensuring that the
messages begin from tenth column.
2. postinstall script was running insf command which is
not encouraged.
Resolution:
insf command should be run to create telnet tty files.
This command should not be run from the postinstall
script but should be done from configure script because
in an OS update scenario this can result in core dump.
3. Patch script creates a backup directory to save the
existing telnet tty files which should not be done
in /dev/pts.
Resolution:
The backup directory is not created anymore under
/dev/pts. The directory is created now under /var/adm/sw.
4. Patch script removes the backup directory though it was
not empty.
Resolution:
The backup directory is no more removed if it has any
files or directories entries.
PHNE_18907:
Ported HP-UX patch PHNE_16546 to VVOS
Based on HP-UX patch PHNE_16546:
1. telnet sessions to a hp-ux 11.0 m/c hang occassionaly.
2. While rebooting a system, there was a panic due to
telnet.
Based on HP-UX patch PHNE_14957:
1. The number of telnet login sessions were limited to
1000 as the member ut_line of utmp structure allowed
for device names only 4 characters long.
2. Telnet was detecting the absence of the pseudo device
drivers telm and tels, but displayed a message which
was not clear.
3. telnetd displays login prompt before system id string.
4. At 11.0 there was a panic due to telnetd.
Based on HP-UX patch PHNE_14819:
1. When a block of data is sent the getmsg() returns a
M_STARTI message. This condition was not handled in
telnetd.
Based on HP-UX patch PHNE_14818:
1. System panics when telnet tries to put null data on to
the queue.
2. Nullifying the message without freeing mp->b_cont causes
memory leak.
Based on HP-UX patch PHNE_14424:
1.The streams modules were not properly unlinked when
telnetd exited.
SR:
8606182980 8606176054 8606157405 8606114446 1653304360
8606145850 8606140594 8606126240 8606134274 8606134275
8606134276 8606134273 5003432294 1653257162 5003454538
4701425793 4701425785 1653248013 5003441964 5003413112
Patch Files:
Networking.NET2-KRN,fr=B.11.04,fa=HP-UX_B.11.04_32,v=HP:
/usr/conf/lib/libtelnet.a
Networking.NET2-KRN,fr=B.11.04,fa=HP-UX_B.11.04_64,v=HP:
/usr/conf/lib/libtelnet.a
InternetSrvcs.INETSVCS-RUN,fr=B.11.04,
fa=HP-UX_B.11.04_32/64,v=HP:
/usr/lbin/net_daemons/telnetd
OS-Core.CORE-KRN,fr=B.11.04,fa=HP-UX_B.11.04_32/64,v=HP:
/usr/conf/h/nvs.h
ProgSupport.C-INC,fr=B.11.04,fa=HP-UX_B.11.04_32/64,v=HP:
/usr/include/sys/nvs.h
InternetSrvcs.INET-ENG-A-MAN,fr=B.11.04,
fa=HP-UX_B.11.04_32/64,v=HP:
/usr/share/man/man1m.Z/telnetd.1m
what(1) Output:
Networking.NET2-KRN,fr=B.11.04,fa=HP-UX_B.11.04_32,v=HP:
/usr/conf/lib/libtelnet.a:
str_telnet.c: PHNE_22159
str_telnet.c $Revision: 1.2.118.6 $ $Date: 2000/06/0
8 10:12:57 $
Networking.NET2-KRN,fr=B.11.04,fa=HP-UX_B.11.04_64,v=HP:
/usr/conf/lib/libtelnet.a:
str_telnet.c: PHNE_22159
str_telnet.c $Revision: 1.2.118.6 $ $Date: 2000/06/0
8 10:12:57 $
InternetSrvcs.INETSVCS-RUN,fr=B.11.04,
fa=HP-UX_B.11.04_32/64,v=HP:
/usr/lbin/net_daemons/telnetd:
$Revision: Hewlett-Packard ISSL Level vvos_rose42 $
$Header: Hewlett-Packard ISSL Release vvos_r
ose $ $Date: Mon Oct 22 09:37:15 EDT 2001 $
Copyright (c) 1983, 1986 Regents of the University o
f California.
$Source: net/INETSVCS/telnetd/telnetd.c, hpuxcmdnet,
vvos_rose, rose0254 $ $Date: 01/10/09 06:44
:57 $ $Revision: 1.21.2.8 PATCH_11.04 (PHNE_
25079) $
telnetd.c $Revision: 1.29.214.16 $ $Date: 2000/06/08
23:40:02 $
telnetd.c 5.31 (Berkeley) 2/23/89
authenc.c 8.1 (Berkeley) 6/4/93
OS-Core.CORE-KRN,fr=B.11.04,fa=HP-UX_B.11.04_32/64,v=HP:
/usr/conf/h/nvs.h:
nvs.h: $Revision: 1.4.105.2 $ $Date: 97/04/26 13:50:
52 $
ProgSupport.C-INC,fr=B.11.04,fa=HP-UX_B.11.04_32/64,v=HP:
/usr/include/sys/nvs.h:
nvs.h: $Revision: 1.4.105.2 $ $Date: 97/04/26 13:50:
52 $
InternetSrvcs.INET-ENG-A-MAN,fr=B.11.04,
fa=HP-UX_B.11.04_32/64,v=HP:
/usr/share/man/man1m.Z/telnetd.1m:
None
cksum(1) Output:
Networking.NET2-KRN,fr=B.11.04,fa=HP-UX_B.11.04_32,v=HP:
1476283019 34620 /usr/conf/lib/libtelnet.a
Networking.NET2-KRN,fr=B.11.04,fa=HP-UX_B.11.04_64,v=HP:
2431425118 69590 /usr/conf/lib/libtelnet.a
InternetSrvcs.INETSVCS-RUN,fr=B.11.04,
fa=HP-UX_B.11.04_32/64,v=HP:
142421960 45056 /usr/lbin/net_daemons/telnetd
OS-Core.CORE-KRN,fr=B.11.04,fa=HP-UX_B.11.04_32/64,v=HP:
1064391964 2512 /usr/conf/h/nvs.h
ProgSupport.C-INC,fr=B.11.04,fa=HP-UX_B.11.04_32/64,v=HP:
1064391964 2512 /usr/include/sys/nvs.h
InternetSrvcs.INET-ENG-A-MAN,fr=B.11.04,
fa=HP-UX_B.11.04_32/64,v=HP:
4247421202 10285 /usr/share/man/man1m.Z/telnetd.1m
Patch Conflicts: None
Patch Dependencies:
s700: 11.04: PHCO_22931
s800: 11.04: PHCO_22931
Hardware Dependencies: None
Other Dependencies: None
Supersedes:
PHNE_19127 PHNE_18907 PHNE_23027
Equivalent Patches:
PHNE_22159:
s700: 11.00
s800: 11.00
Patch Package Size: 220 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_25079
5. Run swinstall to install the patch:
swinstall -x autoreboot=true -x patch_match_target=true \
-s /tmp/PHNE_25079.depot
By default swinstall will archive the original software in
/var/adm/sw/save/PHNE_25079. If you do not wish to retain a
copy of the original software, use the patch_save_files option:
swinstall -x autoreboot=true -x patch_match_target=true \
-x patch_save_files=false -s /tmp/PHNE_25079.depot
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_25079.text file is
available in the product readme:
swlist -l product -a readme -d /tmp/PHNE_25079.depot
To put this patch on a magnetic tape and install from the
tape drive, use the command:
dd if=/tmp/PHNE_25079.depot of=/dev/rmt/0m bs=2k
Special Installation Instructions:
The 'insf' patch PHCO_22931 or its superseding
patch if any MUST be installed prior to the
installation of this telnetd patch, for this patch
to work.
Please note, after installation of PHNE_25079 the
naming convention for /dev/pts/t* changes from
/dev/pts/tnumber to /dev/pts/tcharacter to allow
creation of more than 1000 telnet device files.
Consequently the first telnetd device file is
renamed from /dev/pts/t0 to /dev/pts/ta.
NOTE:
For getting more user logins, the kernel configuration
parameter 'nstrtel' needs to be modified to the desired
number and rebuild the kernel. Ensure that the extra
telnet pseudo ttys are created by doing 'insf -d tels'.
-----End of Document ID: PHNE_25079------------------------------------------
Document ID: PHNE_25076
Date Loaded: 20011026
Title: s700_800 11.04 (VVOS) LAN product cumulative patch
Patch Name: PHNE_25076
Patch Description: s700_800 11.04 (VVOS) LAN product cumulative patch
Creation Date: 01/10/01
Post Date: 01/10/26
Hardware Platforms - OS Releases:
s700: 11.04
s800: 11.04
Products: N/A
Filesets:
Networking.LAN2-KRN,fr=B.11.04,fa=HP-UX_B.11.04_64,v=HP
Networking.LAN2-KRN,fr=B.11.04,fa=HP-UX_B.11.04_32,v=HP
Networking.LAN-RUN,fr=B.11.04,fa=HP-UX_B.11.04_32/64,v=HP
Networking.NW-ENG-A-MAN,fr=B.11.04,fa=HP-UX_B.11.04_32/64,v=HP
Automatic Reboot?: Yes
Status: General Release
Critical:
Yes
PHNE_25076: PANIC HANG
Based on HP-UX Patch PHNE_24413: PANIC
Symptom 2 and 4 fix panics.
Based on HP-UX Patch PHNE_22962: PANIC HANG
Symptoms 4 Fixes a panic, 6 Fixes a hang.
Based on HP-UX Patch PHNE_22353: PANIC HANG
Symptoms 3, 5, 6, 7, 8 fix panics.
Symptom 9 fixes a hang.
PHNE_22825: OTHER PANIC CORRUPTION MEMORY_LEAK HANG
Based on HP-UX Patch PHNE_21905: PANIC HANG
MEMORY_LEAK CORRUPTION
Symptom 2 fixes a hang due to memory leak.
Symptom 7 fixes a panic due to data corruption.
Based on HP-UX Patch PHNE_21217: PANIC HANG
MEMORY_LEAK
Symptom 4 fixes a panic.
Symptom 11 fixes hang & memory leak.
Based on HP-UX Patch PHNE_20657: PANIC
Symptom 6 fixes a panic.
Based on HP-UX Patch PHNE_19766: PANIC HANG OTHER
Without this patch, packets which are sent
out by an interface will not be seen by
the promiscuous mode application.
Symptom 2 can cause system hang or panic.
Symptom 4 can cause system panic.
Based on HP-UX Patch PHNE_19754: HANG
Type 2 DLPI applications on ethernet links will
not work without this patch.
Based on HP-UX Patch PHNE_19081: PANIC
PHNE_18560: ABORT OTHER PANIC CORRUPTION MEMORY_LEAK HANG
Based on HP-UX Patch PHNE_18409: PANIC
Based on HP-UX Patch PHNE_17113: PANIC HANG OTHER
Auto-port Aggregation product depends on this patch.
Symptoms 4, 8 and 13 can cause system panic.
Symptom 9 causes system hang.
Based on HP-UX Patch PHNE_16990: PANIC HANG
Symptoms 1 and 3 are system hangs.
Symptoms 2, 4, 5, 6 and 7 are system panics.
Based on HP-UX Patch PHNE_15969: OTHER
HP Auto-Port Aggregation Software will not work
without this patch.
Based on HP-UX Patch PHNE_15591: HANG OTHER
Symptom 2 is system hang.
With symptom 3, SNA is not able to configure Token
Ring interfaces with lanadmin.
Based on HP-UX Patch PHNE_14370: PANIC OTHER
Symptom 1 fixes a Panic.
Without fix 4, DLPI type 2 applications (e.g. SNA)
won't work over non-CKO FDDI.
Without fix 5, ip multicast won't work for Token
Ring.
Without fix 8, "lanadmin" becomes unusable on
large lan configurations.
Based on HP-UX Patch PHNE_14106: PANIC MEMORY_LEAK
ABORT CORRUPTION
Symptom 4 is corruption with in the process, but
it does not affect the system as such.
Symptom 3 and 6 are ABORT symptoms.
Symptom 9 and 13 cause system panic.
Based on HP-UX Patch PHNE_14027: OTHER
This patch is being made critical since all the
patches released in the 11.0 SR have to be
critical.
Category Tags:
defect_repair enhancement general_release critical panic
halts_system corruption memory_leak
Path Name: /hp-ux_patches/s700_800/11.X/PHNE_25076
Symptoms:
PHNE_25076:
Ported HP-UX patch PHNE_24413 to VVOS
Based on HP-UX patch PHNE_24413:
1. DLPI drops non IP multicast packets for EISA Token ring.
2. Panic in rif_putq().
3. The fddi links dropped during blast test.
4. Spinlock/Deadlock panic for lanc_lookup_lock in
lanc_remove_protocol.
5. IP multicast rcved on FDDI is broadcast forwarded
back to FDDI.
Based on HP-UX patch PHNE_22962:
1. DLPI does not keep track of dropped packets.
2. DLPI requeues packets in raw mode. This is not
neccessary.
3. DLPI test failed for token ring interface.
4. NIO Token ring driver reports
"Hard error on CTL_CCMD=0x1060" in syslog file.
5. DLPI reuses mblks without adjusting the size.
6. On recieving a badly formatted trailer protocol
frame system crashes.
Based on HP-UX patch PHNE_22353:
1. When the PPA number given as a lanadmin argument
is wrong, lanadmin displays the information about the
interface with PPA number 0.
2. When the Station Address value given as an
argument to lanadmin was too large, lanadmin was not
returning non-zero value indicating the failure to set
the Station address.
3. The system panics when trying to run the
promiscuous tests on Core Ethernet interface.
4. When one or more data lines(DI-A,DI-B, DO-A, or
DO-B) of the AUI port had been severed but the other
lines are still connected, LASI based systems will
panic after network activity.
5. System panics with "Data Page Fault".
6. System may panic when user kills a promiscuous
application.
7. Turning off the promiscuous mode panics the system.
8. System panics as it runs out of Kernel virtual
space. The following panic message is displayed.
"panic: Out of kernel virtual space".
9. Broadcast storm on Gigabit ports hangs system.
PHNE_22825:
Ported HP-UX patch PHNE_22331 to VVOS
Based on HP-UX patch PHNE_22331:
1. lanscan usage string does not contain option "q".
2. ER: Need a command line option to display information
which is available from lanadmin in interactive mode.
3. Incorrect reference in "SEE ALSO" section of lanadmin
man page.
4. Usage strings for x/X options for lanadmin incorrect.
5. /sbin/init.d/hpether script fails if more then 10
cards are present on the system.
Based on HP-UX patch PHNE_21905:
1. Data loss over serial line with unterminated Core
10BT card.
2. Under low memory conditions, HP-PB 10BT can cause
system hang.
3. HP-PB 10BT reports incorrect MIB statistics causing
Service Guard to misbehave.
4. Lanadmin manpage information for "-m" option is
incorrect.
5. Link between landiag and lanadmin is broken in patches.
6. ER: lanscan -q is broken for NIO FDDI Fail-Over groups.
7. System panic in t2_kftslis().
8. DLPI returns unexpected error acknowledgement.
Based on HP-UX patch PHNE_21217:
1. T2 XID/TEST tests fail.
2. DLPI does not check for invalid multicast
address for FDDI.
3. lanc fails to prevent setting Station Address to
a multicast MAC address.
4. System panic during disable multicast request.
5. IP multicasting problem in Token Ring.
6. ER: lanc support for filtering IEEESAP_HP packets
on 10.20.
7. APA_EVENT_NON_IP_LOGGED not correctly implemented
for TR
8. lanadmin command fails on machines with many
interfaces.
9. Q4 debug information wrong in 11.00.
10. lanadmin -A causes system panic.
Based on HP-UX patch PHNE_20657:
1. ER: Support for APA in DLPI.
2. Unable to change PMTU when interface is
configured as SNAP
3. Problem with DL_SUBS_BIND_REQ.
4. DLPI needs to send link up/link down messages
to upper layers when MAC address changes.
5. ER: Source MAC address should be filled by DLPI
on every outbound path.
6. Panic with lanc_ether_trail_mblk_intr on top
of stack.
7. ER: Lan Monitor support in DLPI.
8. DLPI does not propogate LINK UP/DOWN events to
all attached IP streams.
9. OTS fails to switch interfaces when a
MC/Service Guard failover happens.
Based on HP-UX patch PHNE_19766:
1. HP-PB 10BT and Core 10BT drivers do not receive packets
they transmit, when in promiscuous mode.
2. I/O slowdown or hang because of HP-PB 10BT absorbing a
large number of IOVRs.
3. Ethernet cards setup incomplete after reboot.
4. HP-PB 10BT panic during reboot.
5. Service Guard test fails on HP-PB 10BT interface.
6. 'ifconfig' on HP-PB token ring card failed.
Based on HP-UX patch PHNE_19754:
1. The connection oriented DLPI applications may hang
on an Ethernet link.
Based on HP-UX patch PHNE_19081:
1. On a token ring LAN, an ARP packet with incorrect header
fields may cause a panic.
2. The network interface status is not updated when the
cable is diconnected.
3. DLPI applications failed to send data using
DL_UNITDATA_REQ primitive over ethernet links
which support checksum offload feature.
4. Functional addresses are not working for PCI token ring.
5. The system may panic if a TEST/XID packet is received.
6. Auto-Port aggregation product generates redundant
console messages.
7. When the SNA protocol stack is in uniprocessor
emulation mode, an inbound packet to one of its streams
that is closing could potentially panic the system.
8. When a Core-Ethernet NIC is neither connected to a
network nor terminated, then real-time applications could
see performance degradation every 5 seconds.
PHNE_18560:
Ported HP-UX patch PHNE_18409 to VVOS
Based on HP-UX patch PHNE_18409:
1. A system configured with a Core-Ethernet NIC sometimes
panics with a data page fault or with the message
"panic: mclfree".
2. A system panic with the message "SPINLOCK DEADLOCK"
in the HP-PB Ethernet driver.
Based on HP-UX patch PHNE_17113:
1. Inability to install the Auto-Port Aggregation (APA)
product from the February 1999 Application Release.
2. Using the DLPI_SET_RIF_ON ioctl in a 32 bit
application running on a 64 bit system results in
an ENXIO error return.
3. Systems using the built-in 10 Mb/s LAN through an
external MAU may see an excessive number of resets.
Applications trying to transmit a packet could see an
ENOLINK error return.
4. A system with HP-PB 10 Mb/s ethernet may panic under
heavy load when available memory is low.
5. The MTU of built-in and HP-PB 10 Mb/s ethernet links
cannot be adjusted.
6. The MIB counter ifInDiscards for HP-PB 10 Mb/s ethernet
is abnormally high even though the link is
operating normally.
7. lanadmin(1M) reports ifOper as down for an HP-PB 10 Mb/s
ethernet interface even though the link is operational.
8. Resetting an HP-PB 10 Mb/s ethernet interface when
it is hung can cause a system panic.
9. Attempting to unbind a protocol (e.g., executing
ifconfig unplumb on an interface or issuing the
DL_UNBIND_REQ primitive) when an inbound packet is
being processed on the stream, can cause a system hang.
10. Links are unable to receive packets they transmit when
in promiscuous mode.
11. "lanscan -v" dumps core if the system has the Auto-Port
Aggregation (APA) product installed.
12. ping(1M) requests receive no response when source
routing is turned off on Token Ring interfaces.
13. System panics on receiving a trailer encapsulated
packet from mblk drivers.
Based on HP-UX patch PHNE_16990:
1. An MP system under heavy networking load can
panic or hang.
2. An application cannot enable more than 16 multicast
addresses per stream.
3. Turning off promiscuous mode on interfaces that use
sleep/wakeup can cause system panic.
4. Turning on multicast promiscuous mode on a bound stream
causes all unicast packets to be dropped for that stream
until the multicast promiscuous mode is turned off.
5. An inbound IP packet with no IP header causes system
panic.
6. Disabling multicast addresses on an interface that uses
sleep/wakeup can cause system panic.
7. Starting or stopping mrouted under heavy outbound IP
traffic can cause system panic.
8. Performance of applications that use promiscuous mode is
enhanced by this patch.
Based on HP-UX patch PHNE_15969:
1. Support needed for HP Auto-Port Aggregation Software.
2. linkloop has hardcoded limits for -s option.
3. Needed run-time switch to turn on/off Inbound Packet
Scheduling in dlpi pseudo driver.
4. With PHNE_15591, swverify(1M) on the Networking product
fails with errors similar to the following:
ERROR: Control file "unconfigure" should have size
"545" bytes but the actual size is "555" bytes.
ERROR: Control file "verify" should have size "2117"
bytes but the actual size is "1807" bytes.
ERROR: Fileset "Networking.LAN-RUN,l=/,r=B.11.00" had
file errors.
5. Linkloop did not work with those ethernet links which
support checksum offload feature.
Based on HP-UX patch PHNE_15591:
1. Increased scalability by doing Inbound Packet Scheduling
in DLPI.
2. System appears to hang with certain DLPI applications.
3. The lanadmin(1M) -b/-B options are not working.
4. swverify(1M) logs a large number of errors when the
system does not have hardware supported by the lan2 and
lan3 drivers (e.g., built-in 10 Mb/s Ethernet, HP-PB
Ethernet, EISA 10 Mb/s Ethernet). An example of an
error message logged is:
ERROR: The LLA device files are not installed correctly.
Based on HP-UX patch PHNE_14632:
1. No DELETE multicast requests were sent down to the
driver when application issued a DELETE on a previously
added multicast address.
2. Lanadmin fails to change MAC address for the Token Ring
Interface.
3. dmesg shows debug message for the Token Ring Interface.
4. lanadmin needs easier way to reset MAC address to
default.
Based on HP-UX patch PHNE_14370:
1. Panic with kernel stack overflow during ServiceGuard
switch over.
2. DLPI command after DL_HP_HW_RESET may get ENXIO
error.
3. Need MBLK support for Token Ring Drivers.
4. DLPI type 2 won't work over FDDI devices that do not
support the Checksum Offload feature (e.g. HSC and
EISA FDDI)
5. IP multicast doesn't work for Token Ring devices.
6. Incorrect handling of promiscuous data by different
LAN drivers.
7. IP Multicast does not work for drivers supporting
checksum offload.
8. Lanadmin doesn't work on a system with large number
of lan cards.
Based on HP-UX patch PHNE_14106:
1. Lanscan does not recognize HyperFabric cards.
2. lanadmin does not support mode and speed changes for
100BT cards.
3. lanadmin won't work with lan0 when atm card /
Hyperfabric driver is present.
4. lanadmin Unable to access PPA Number on 11.0 64 bit T600
LR+extension software bundle.
5. ATM interface named "el1000" is not displayed properly
by lanscan.
6. lanscan -v report shared library error against ATM NICs.
7. HP 9000/UX ARP implementation causes caching of the
least optimal path to a remote host on a multiple-ring
Token Ring network.
8. DLPI performance enhancement.
9. linkloop (1m) causes memory leak and panic.
10. DL_HP_MULTICAST_REQ/ACK support for drivers supporting
IP level multicasting.
11. Cannot send out files that are more than 1492 bytes over
Ethernet with SNAP encapsulation.
12. The XID and TEST packet failed on DLPI type 2 service
over mblk based drivers.
13. The DLPI stream bound to IEEE 802.2 saps (sap < 256)
with DL_SUBS_BIND_REQ do not work correctly and could
potentially panic the system.
14. linkloop returns ERANGE if MTU of link changed.
Based on HP-UX patch PHNE_14027:
1. PHNE_13076 which was released in the 11.0 SR release,
is not tagged as critical. A patch should have critical
category tag to get released in 11.0 SR Extension
Software media.
Based on HP-UX patch PHNE_13076:
1. SIO/WSIO dependency is missing for HP-PB and
Built-in ethernet drivers.
2. lanadmin command fails after sufficient changing of
PPA/display commands when the LANG environment
variable is set.
3. TCP packets are delayed.
Defect Description:
PHNE_25076:
Ported HP-UX patch PHNE_24413 to VVOS
Based on HP-UX patch PHNE_24413:
Fix Summary:
For Token: 1,2
For FDDI: 5
Common to all products: 3, 4
1. CR:JAGad64041 SR:8606194835
DLPI drops Non-IP Multicast packets for Token Ring.
Resolution:
On recieving a Multicast packet for token ring DLPI now
checks for IP and Non-IP multicast MAC addresses
that are being listened to.
2. CR:JAGad58592 SR:8606189377
Panic in rif_putq().
Trace looks as follows:
panic+0x14
report_trap_or_int_and_panic+0x80
interrupt+0x1d4
$ihndlr_rtn+0x0
rif_putq+0x1dc
hp_dlpi_mblk_intr_put+0x594
streams_put_release+0x1cc
hp_dlpi_mblk_intr+0x4c
pcitr_recv_complete+0xe68
pcitr_isr+0x33c
sapic_interrupt+0x2c
mp_ext_interrupt+0x34c
ivti_patch_to_nop3+0x0
idle+0x184
swidle_exit+0x0
or
crash event was a panic
panic+0x14
report_trap_or_int_and_panic+0x80
interrupt+0x1d4
$ihndlr_rtn+0x0
bcmp_checkitout+0x18
rif_searchq+0x38
rif_putq+0x1f0
hp_dlpi_mblk_intr_put+0x594
streams_put_release+0x1cc
hp_dlpi_mblk_intr+0x4c
pcitr_recv_complete+0xe68
pcitr_isr+0x33c
sapic_interrupt+0x2c
mp_ext_interrupt+0x34c
ivti_patch_to_nop3+0x0
idle+0x954
swidle_exit+0x0
Resolution:
Protected the read and write to rif_queue using
locking machanism.
3. CR:JAGad64335 SR:8606195129
The fddi links dropped during blast test.
Resolution:
On receiving a linkup/linkdown event from the driver
DLPI sends a return value back to the driver saying
it is able to intimate the upper module of this event.
4. CR:JAGad54952 SR:8606185750
Spinlock/Deadlock for lanc_lookup_lock in while trying
to remove a protocol that is logged.
Trace looks as follows
panic+0x10
too_much_time+0x238
wait_for_lock_spinner+0x2f4
wait_for_lock_4way+0x2c
sl_retry+0x18
lanc_remove_protocol+0xb8
lanc_lla_close+0x2d0
closef+0x68
exit+0x214
rexit+0x20
syscall+0x75c
$syscallrtn+0x0
Resolution:
Handled by changing the locking implementation for
logging and removing protocols.
5. CR: JAGad73103 SR:8606203925
IP multicast rcved on FDDI is broadcast forwarded
back to FDDI.
Resolution:
MAC address of FDDI packet is checked for Multicast
bit and appropriate information is forwarded to IP.
Based on HP-UX patch PHNE_22962:
Fix Summary:
For ETHER: 6
FOR TOKEN: 3
Common to all products: 1, 2, 4, 5
1. CR: JAGad37106 SR:8606167823
DLPI does not track dropped packets.
Resolution:
Updated the statistics of the interface on events
of packet discard and recieve.
2. CR: JAGad37107 SR:8606167824
DLPI should not attempt to requeue in raw mode
Resolution:
Disabled the requeuing of packets when DLPI used in
raw mode.
3. CR: JAGad21664 SR:8606152325
DLPI multicast test failed for token ring interface.
Resolution:
This is due to call of DL_ENABMULTI_REQ failed by
DLPI. This is handled by DLPI checking the right list
that is passed from the driver on completion of
request.
4. CR: JAGad23566 SR:8606154248
NIO Token ring driver reports
"Hard error on CTL_CCMD=0x1060" in syslog.
Resolution:
This was due to race condition between checking the
protocol logged and the driver actually logging the
protocol. Handled by locking while the driver is
yet to finish logging the protocol.
5. CR: JAGad41174 SR:8606171911
DLPI reuses mblks without adjusting the size when it
converts struct DL_BIND_REQ to the struct
DL_HP_BIND_REQ.
Resolution:
The size is adjusted to accommodate DL_HP_BIND_REQ
struct.
6. CR:JAGad55423 SR: 8606186218
On receiving a bad formatted TRAILER protocol frame the
system crashes.
Resolution:
The badly formatted packet is detected and dropped.
Based on HP-UX patch PHNE_22353:
Fix Summary:
For ETHER: 3
Common to all products: 1, 2, 4, 5, 6, 7, 8, 9
1. CR: JAGad31160 SR: 8606161844
When a wrong ppa number was passed as parameter to
lanadmin, it displays the value corresponding to
PPA 0.
2. CR: JAGab75792
When the station Address argument passed to lanadmin
is too long, lanadmin does not display any error
message and does not return the value indicating the
failure of the command. This was causing problem for
the driver specific configuration scripts as they were
not able to detect the failure but the card also was
not getting configured.
Resolution:
lanadmin will now print an error message for the long
mac address and will exit with -1.
3. CR: JAGad38176 SR: 8606168898
The system was panicing while running the promiscuous
mode tests. The panic was because of a window, where the
promisc stream can be freed but still hp_dlpi_intr tries
to access it.
Resolution:
The Core Ethernet code is modified to take care of the
problem by checking the content of the variable before
it was being used.
4. CR JAGad35507 SR 8606166220
When transmit line being severed and the
receive lines being intact, the card will still receive
packets from the wire. So when the driver sends out a
loopback packet in the reset path, it assumes any
response to be the loopback packet response. So, it
assumes success of loopback even though the packet it
received was not a loopback packet. This causes the
driver to come online. The next transmit will again
timeout causing another reset. These continuous resets
lead to the bus timeout and hence the panic.
Resolution:
Ensure that the packet received in lan2_process_looper
is really a loopback packet.
5. CR JAGad27778 SR 8606158448
System may panic when packets with no data is passed
up to the IP and when the packets have MSG_CKO flag
turned on. The panic can occur when the application
receives unitdata packets.
Resolution:
Any packet with no data is dropped at DLPI level.
6. CR JAGad39929 SR 8606170665
When a promiscuous application is killed abruptly,
DLPI sends a DL_PROMISCOFF_REQ, on which driver
could sleep. DLPI tries to access data during
wakeup to complete the request and inadvertently
accesses the element of a structure which may
not be available for this particular request,
causing the system to panic.
Resolution:
The data which DLPI accesses during wakeup is
done depending on the request, instead of
doing it at the common place, there by looking
into data which will be available only for this
request.
7. CR JAGac40857 SR 8606125467
When a application in promiscuous mode turns
off the promiscuous mode or is killed, driver may
still pass the promiscuous mode packet to DLPI,
but the promiscuous stream may no longer be
available when DLPI tries to send the packet
up-stream, causing the system to panic.
Resolution:
The validity of the promiscuous stream is
checked before DLPI sends packets upstream.
8. CR JAGad03223 SR 8606134083
System runs out of kernel virtual memory
space as packets are queued up in streams
above the driver. DLPI is not the primary
culprit in this defect but during the time of
investigation, it was found that there is
a possibility of DLPI's internal queues
could grow unbound.
Resolution:
DLPI's internal queue is flow controlled to
avoid the queue from growing unbound.
9. CR JAGad09699 SR 8606140332
System may hang when there is a broadcast
storm making the queues to grow unbound
and eventually hanging the system. The
problem was with STREAMS which can allow
the queues to grow without limits.
Resolution:
DLPI uses new STREAMS function 'sq_canput'
which flow control the streams.
PHNE_22825:
Ported HP-UX patch PHNE_22331 to VVOS
Based on HP-UX patch PHNE_22331:
Fix Summary:
For ETHER : 5
Common for all products: 1,2,3,4.
1. CR: JAGac46780 SR: 8606126024
Though the support for "q" option was already
added to lanscan, the usage string was not reflecting
the same.
Resolution:
Modified the usage string to add "q" in the options
available.
2. CR: JAGad09461 SR: 8606140139
There is no command line option to get the statistics
and some other information related to a lan card from
lanadmin.
Resolution:
"-g" command line option is added to display information
which was ealier obtained by "display" option in
interactive mode. The lanadmin manpage is also modified
to give more information on new option.
3. CR: JAGaa94099
The "SEE ALSO" section of lanadmin manpage was referring
to "DARPA Requests for Comments" which should be
"IETF Requests for Comments"
Resolution:
Man page is modified.
4. CR: JAGad29655 SR: 8606160333
The lanadmin usage string for x and X option was
referring to "Network Management ID" instead of PPA
Number.
Resolution:
Modified the usage string.
5. CR:JAGad30864 SR:8606161548
The problem is due to improper lanscan -ip output for
the lan cards with instance number >9.
Resolution:
The script has been modified to use lanscan output
instead of "lanscan -ip output" to get the required
information.
Based on HP-UX patch PHNE_21905:
Fix Summary:
For ETHER: 1,2,3.
For FDDI: 6.
Common for all Products: 4,5,7,8.
1. CR: JAGab46943 SR:5003459701
An unterminated/disconnected Core 10BT card
causes data loss over the serial port. This
is because when the card is disconnected,
the driver periodically tries to reset the
card. The reset of the card involves many
calls to busywait, which leads to poor serial
I/O performance.
Resolution:
The resolution is to eliminate some of the
busywait calls in the reset path.
2. CR: JAGad02482 SR: 8606133337
If the memory allocation fails during compression
of outbound packets HP-PB 10BT driver was dropping
the packet but not freeing the memory appropriately.
This could lead to memory leak.
Resolution:
HP-PB 10BT will now free the memory appropriately
when it does not get memory to compress outbound
packets.
3. CR: JAGad13235 SR: 8606143902
The MIB statistics were being updated for a HP-PB
10BT card even when the cable was disconnected.
This was causing the Service Guard to misbehave
as it depends on the MIB statistics to detect the
failure or recovery of LAN cards.
Resolution:
The statistics now gets updated when the packet is
successfully processed and transmitted.
4. CR: JAGac88749 SR:8606129845
lanadmin manpage had incorrect information about
-m option. The man page for "-m" option was as
follows
-m Display the current MTU size of the interface
corresponding to PPA. You must have superuser
privileges.
Resolution:
The fix is to remove "You must have superuser
privileges." for -m option from lanadmin man page.
5. CR:JAGad21159/JAGad10603 SR:8606151820/8606141242
The patches on 11.0 were missing the link between
lanadmin and landiag. Due to this, the modifications
released in patch for lanadmin were not reflected by
landiag command.
Resolution:
The fix is to create a hard link between lanadmin and
landiag.
6. CR:JAGad04612 SR:8606135478
To fix out-bound checksum offload problem
with HP-PB FDDI when aggregated, Lan Monitor applied
a short term workaround. This resulted in HP-PB
FDDI port based aggregates not being shown on lanscan
output.
Resolution:
The fix introduces a new features bit -
DRV_CKO_SR71_FLAVOR, for HP-PB FDDI to set and DLPI
checks this features bit rather than looking for
driver name to determine if SR-71 flavor of
checksum offload is being used.
7. CR:JAGad14400 SR:8606145062
An operator precedence problem led to a DLPI type 2 log
lock being freed twice. This caused memory corruption
and eventually a data page fault panic.
Resolution:
The operator precedence was set right to take care
of this corruption.
8. CR:JAGad13239 SR:8606143906
DLPI returns DL_ERROR_ACK in the
unitdata path, which is not in conformance with
DLPI standard. As this error is not expected in
this path, Service Gaurd used to report strange
primitive error when DL_UNITDATA_REQ fails.
Resolution:
The unitdata path was changed to return only
DL_UDERROR_IND for failures in DL_UNITDATA_REQ.
Based on HP-UX patch PHNE_21217:
Fix Summary:
For FDDI: 2.
For ETHER: 3.
For Token Ring: 4, 5.
Common for all products: 1, 6, 7, 8, 9, 10.
1. JAGab69560: T2 XID/TEST scaffold tests fail, because
the T2 code in DLPI, assumes that the XID/TEST data
is present in first mbuf, but there is a possibility
that the first mbuf only contains the LLC header and
the XID data is present in second mbuf. This assumption
was wrong, which created unexpected response from
DLPI to an application.
Resolution:
The T2 code has been changed to take care of this
situation, where the XID data can be present in the
second mbuf.
2. JAGac88801: When Enable/Disable multicast address
request was sent, DLPI does not check for invalid
multicast addresses for FDDI driver, so, if an
application tries to enable a invalid multicast address,
on a FDDI link, it succeeds.
Resolution:
The code change done to resolve this defect, checks
for the device type of FDDI when it tries to enable
a valid multicast address.
3. JAGac95565: lanc fails to prevent setting Station
Address to a multicast MAC address. As the check
done to prevent this from happening, checks for the
device type of DEV_8023, but some ethernet drivers
set the device type to DEV_ETHER, so this checking
fails to prevent setting multicast address as the
station address when the drivers set the device type
to DEV_ETHER.
Resolution:
The checking done when trying to change the station
address now includes the check for device type of
DEV_ETHER.
4. JAGac86212: System paniced when disable multicast
request was sent to a Token Ring interface. The
Token Ring mulitcast address is not stored in
global list of mulitcast addresses maintained
by DLPI, but when disable mulitcast address is
sent, the DLPI module tries to find out the
address in the list, there by manipulating invalid
entries in the multicast list, thus causing the
system to panic.
The stack trace for the panic:
0x00050d34 (panic+0x4c)
0x0009968c (report_trap_or_int_and_panic+0x8c)
0x0009d560 (interrupt+0x3c0)
0x000b2f6c (set_protid_registers+0xa28)
0x00591dc4 (hp_dlpi_process_wakeup+0x51c)
0x00591558 (hp_dlpi_wakeup_put+0x30)
0x00630818 (streams_put+0x1e0)
0x005914c8 (hp_dlpi_wakeup+0x200)
0x008784c0 (pcitr_process_srb_response+0x238)
0x0088450c (function name is not available)
0x00883d58 (function name is not available)
0x00883878 (pcitr_isr+0x638)
0x0025c80c (sapic_interrupt+0x34)
0x0009d0b0 (mp_ext_interrupt+0x268)
0x000b2f48 (set_protid_registers+0xa04)
0x0033a36c (idle+0x115c)
0x000b1f7c (getproc_info+0x28)
Resolution:
The manipulation of the list is done depending on the
return value of a macro which searches the list
for possible match in multicast address. For TR
this match operation will fail, there by preventing
the list from being manipulated.
5. JAGac86794: The output routines in DLPI, do wrong
checks to find the Token Ring multicast address.
There are two separate checks done depending on
the MAC type of the card. For token ring cards,
the check is done on the functional address, but
in addition to this the address is searched in
DLPI global multicast address list, there by
undoing the previous check.
Resolution:
Depending on the MAC type of the card, only
one of the above mentioned check is done and
ensuring the relevant multicast addresses are
searched.
6. JAGad00107: ER: Support for filtering IEEESAP_HP
packets in lanc.
Resolution:
This enhancement has been done in lanc to support
filtering for IEEESAP_HP packets.
7. JAGad00334: DLPI event APA_EVENT_NON_IP_LOGGED is
not correctly implemented for Token Ring interface.
The dlpi_event() function uses small-endian format
to check for IP multi-cast address comparison.
Resolution:
The function is converted to check for IP multicast
addresses in wire format(big-endian) for Token Ring
interfaces.
8. JAGad01906: lanadmin command has a predefined buffer
size, to read data from the stream. This buffer size
is insufficient for machines which mave more than
20 interfaces. When it tries to read the hwift's
of the interfaces from the system, it leaves out
some data on the stream head because it reads less
data than what is available. This causes the subsequent
operations fail.
Resolution:
The buffer size is redefined to accommodate larger
amount of data.
9. JAGac87773: The DLPI data structure hp_dlpi_data_t
has been changed, but the debug information available
does not reflect this change.
Resolution:
Redefined the hp_dlpi_data_t to hp_dlpi_data_t_2
for debug purpose so that it can override the
original definition and reflect the change in
data structure. The redefinition is only for
debug purpose.
10. JAGad08366: Changing the MAC address can cause
system panic. The disable multicast requests
are sent when the driver is still on ICS, and
driver tries to hold a lock which is already
held.
Resolution:
When the driver wakesup DLPI, it used to send
upper layers of the change in link state to down,
which caused the upper layer to send disable
multicast requests when the driver is still on
ICS. But now DLPI instead of sending the link
down indication as soon as it wakes up, it puts
the indication in its own queue which later can
be processed by DLPI's service routine, thus
avoiding the senario where the whole thread runs
on ICS.
Based on HP-UX patch PHNE_20657:
1. JAGac56887 ER: Changes needed in DLPI to support APA
features.
Resolution:
Changes are made to DLPI to support some
functionalities of APA. The changes done were
addition of new IOCTL's APA_SET_DEFAULT_CONFIG_MODE,
APA_GET_DLPI_VERSION &
APA_EVENT_SET_DEFAULT_CONFIG_MODE.
2. JAGac39764: The DLPI function hp_dlpi_subs_bind()
is taking the MTU value from a constant, instead of
from the hw_ift structure to use for the SNAP
encapsulation. The hp_dlpi_subs_bind() was taking
its value from a constant SNAP8023_MTU. But when
the MTU value changes, as in case of Jumbo frames,
the DLPI internal data structure does not reflect
the change which causes this problem.
Resolution:
The MTU value is taken from interface's hw_ift
structure to reflect the current MTU value.
3. JAGac56915: Problem with DL_SUBS_BIND_REQ
Resolution:
Update the DLPI internal data structure only after
the protocol logging is successful.
4. JAGac56732: When MAC/PHY address changes on a link,
user had to bring the link down and then up to
generate the ARP request, but this needs to be done
by DLPI, because when APA is installed on the
machine, and the link where the MAC address has
changed is present in the aggregate as a primary link,
then when user brings the link down, APA thinks that
that the has gone down and tries to use the secondary
as its primary link, which again, brings the secondary
link down to change its MAC address, this causes a
ripple effect and the aggregate goes down.
Resolution:
Changed DLPI to generate the ARP packet whenever
MAC address changes and there by bypassing APA.
5. JAGac78533: The current implementation of DLPI
fills the source MAC address for outbound packets
in some of the outbound paths, but this created
problem when using APA, where the aggregate had
a single MAC address. When the packets from
the aggregate reaches the driver, the driver
again fills up the source MAC address which can
differ for different links in the aggregate. This
created problem with the switches.
Resolution:
DLPI has been modified to fill the source MAC
address for every outbound packet in all the
paths, and also letting the driver know that
DLPI is doing so, by setting a features bit in
the hwift structure of the driver. If the bit
is set then, the driver knows that DLPI has
filled the source MAC address and it need not
fill it again.
6. JAGac39928: The operator precedence is not
checked properly before trying to log the
trailer protocol address in lanc_init().
Resolution:
The code has been modified to explicitly
enforce precedence in proper manner.
7. JAGac79105: Lan Monitor Support in DLPI:
Resolution:
The following changes were made to DLPI for
Lan Monitor support:
1. Support for binding protocol kind LAN_CANON that
will enable receiving poll packets by Lan Monitor
aggregated ports.
2. Handle events DL_EVENT_INTERFACE_DOWN,
DL_EVENT_INTERFACE_UP from drivers and
APA_EVENT_PROTOCOL_LOGGED from Lan Monitor.
8. JAGac78287: DLPI does not propogate Link UP/DOWN
events to all attached IP streams on an interface.
Resolution:
DLPI used to send link UP/DOWN events to the
first attached IP stream on a interface. The
behaviour is changed with this patch to send link
UP/DOWN events to all the IP streams attached
to a interface.
9. JAGac86142: OTS when used along with Service Guard
fails to switch interfaces when the primary link
goes down. When OTS switches from one interface
to another, it tried to move all the multicast
addressess from the original interface to the new
one, but DLPI fails to remove all the multicast
addressess enabled on the stream, but error is not
returned about the failure of switching. When OTS tries
to enable the same multicast address again on the
new interface, the request fails, so OTS marks
the interface down. DLPI fails to allocate
mblk of proper size for disable multicast request.
Resolution:
DLPI allocates mblk of proper size of disable
multicast address request.
Based on HP-UX patch PHNE_19766:
1. HP-PB 10BT and Core 10BT drivers did not loopback
outbound packets while in promiscuous mode. So, the
stream which turned on the promiscuous mode didn't
receive the outbound packets.
Resolution:
Drivers now will loopback the outbound packets to DLPI
and DLPI will send the packets upstream.
2. HP-PB 10BT was exhausting available IOVRs resulting
into unavailibility of IOVRs for use and thus causing
slow I/O or hang. This happens as many small mblks are
being transferred down from the TCP/ IP layers.
Resolution:
An additional check has been introduced to find if the
number of mblks per frame coming to driver are more than
8 and compress them if greater than 8, hence eliminating
the need for multiple mblks.
3. Ethernet card does not get initialized as per the
settings specified in configuration file upon reboot.
The problem is seen for the cards whose information
in the configuration file is at index greater than
the number of cards in the system.
Resolution:
Fix includes reading complete configuration information
by correct manuplation of index counter in the init
script.
4. HP-PB 10BT can panic the kernel under low memory
condition at boot time. The panic happens due to access
of NULL pointer returned by memory allocation function.
Resolution:
Fix is to check the return value from memory allocation
function and leave the card in un-initialized state if
the return value is NULL at boot time.
5. The Service Guard test does not pass as HP-PB 10BT
driver does not send the NMV_LINKUP event.
Resolution:
Fix is to send the NMV_LINKUP mib event to lanc.
6. Token Ring requires token_arp module to be configured
on the system to work. PHNE_18409 takes care of adding
token_arp module to system file, but the superseding
patches PHNE_19081 and PHNE_19754 do not take care of
this.
Resolution:
Addition of token_arp module to system file is
re-introduced in this patch to fix the problem.
Based on HP-UX patch PHNE_19754:
1. Connection oriented DLPI applications on an Ethernet
link could hang while waiting for a DL_DISCONNECT_IND
message to arrive, because of a defect in DLPI code.
Resolution:
This defect has been fixed by ensuring the correct
sequence of break statements.
Based on HP-UX patch PHNE_19081:
1. If an arp packet is sent with incorrect header field
values on a token ring LAN, it might result in a system
panic.
Resolution:
DLPI has been fixed to check for the correctness of
header fields in an arp packet on a token ring LAN.
2. A cable disconnect did not result in a link down event
being sent upstream.
Resolution:
A link down event is now sent upstream.
3. In outbound path involving DL_UNITDATA_REQ DLPI
primitive, checksum offload processing needed
initialization of the fields of a structure.
Resolution:
This problem has been fixed by initializing
the fields of the above structure.
4. When a request to enable a token ring functional address
is received, DLPI fails to process it correctly.
Resolution:
DLPI processing of token ring functional addresses has
been corrected.
5. When a type 2 DLPI connection was automatically
responding to a TEST/XID packet, an incorrect
typecasting of a pointer caused system panic.
Resolution:
Typecasting of the pointer is being done correctly.
6. Auto-port Aggregation product was sending redundant
messages to the console.
Resolution:
These messages are no longer sent to the console.
7. The Streams framework reschedules procesing of a packet
on the destination processor, if the stream is in
uniprocessor emulation mode. When processing of the
packet is resumed, it did not check if the stream is
still open. This resulted in a system panic.
Resolution:
DLPI now uses the Streams interface that does these
checks.
8. When a Core-Ethernet NIC is neither connected to a
LAN nor terminated, the Core-Ethernet driver detects
the loss of carrier and begins to continuously reset
the card. As part of the resets, the driver calls the
system busywait routine that makes the CPU spin for
a fixed period of time, for a total of up to 20
milli-second per reset. As a result real time
applications detect a 20 milli-second delay in
completion of their operations, once every 5 seconds.
Resolution:
A global variable lan2_no_reset_on_disconnect has been
made available to be set using adb(1M) command. By
default this variable is set to 0 and there is no
change in the behaviour of the Core-Ethernet driver.
When this variable is set to a non-zero value using
adb(1M), the Core-Ethernet driver will skip all driver
initiated card resets. This will result in busywait
routine not being called and hence avoid affecting
the performance of real time applications. This
variable can be set using the adb(1M) command
(as super-user) :
# adb -w /stand/vmunix /dev/mem
# lan2_no_reset_on_disconnect/W 1
and then exit adb.
When this variable is set, the Core-Ethernet driver
will not be able to detect a cable reconnect event.
Hence this solution should be used only when both the
following conditions are true:
- the Core-Ethernet NIC is not used and not connected
to a network
- the Core-Ethernet NIC cannot be terminated
- real time application performance is impacted as
described above.
When normal usage of the Core-Ethernet NIC on a network
is desired, the Core-Ethernet NIC should be connected
to a functional network ( or terminated ) and a
driver/card reset initiated using the lanadmin(1M)
command. This action will restore the driver to it's
default behaviour, also resetting the value of the
global variable lan2_no_reset_on_disconnect to 0.
PHNE_18560:
Ported HP-UX patch PHNE_18409 to VVOS
Based on HP-UX patch PHNE_18409:
1. The Core-Ethernet lan interface did an extra DMA to a
receive frame descriptor under the following condition:
when the Core-Ethernet lan interface has used up the
last available receive frame descriptor, it generates a
"Frame Received" interrupt and also a "Receiver Not
Ready" interrupt. After processing each of these
interrupts, the driver attempted to start the receive
engine with a new pool of receive frame descriptors
if the receive engine status showed "Not Ready".
Sometimes this could result in the same pool of buffers
being set up twice for DMA. This caused corruption of
the 256 byte bucket. The system paniced on the next 256
byte allocation request.
Resolution:
The Core-Ethernet driver has been corrected to start
the receive engine only on receipt of a "Receive unit
Not Ready" interrupt.
2. A driver returns a negative pointer value when it can
not complete a control request immediately. The DLPI
checks the negative return value to unlock the driver
lock. The return value needs to be a 64bit quantity on
a 64bit system. One of the functions that receives this
value and passes it to the DLPI did not have the right
prototype. This caused the driver lock to be held
forever resulting in the lock deadlock.
Resolution:
The lan common routine has been modified to have the
correct prototype.
Based on HP-UX patch PHNE_17113:
1. Enhancements to the functionality of the Auto-Port
Aggregation (APA) product have a dependency on this
version of DLPI.
2. DLPI, when running on a 64 bit kernel, did not recognize
the ioctls DLPI_SET_RIF_ON, DLPI_SET_RIF_OFF and
DLPI_RIF_INFO from 32 bit applications.
3. When the built-in 10 Mb/s LAN interface returned a
"No carrier" status along with a "Late collision"
on a transmit request, the driver treated the
situation as a carrier loss and reset the interface.
Resolution:
The driver treats the situation as a late collision.
4. The driver did not check the return value from a
buffer copy function.
Resolution:
The driver now checks for the return value and
sends the packet upstream only if the copy is
successful.
5. Built-in and HP-PB 10 Mb/s ethernet did not support
changing the MTU.
6. The filter implementation in the HP-PB 10 Mb/s ethernet
card firmware incorrectly incremented the bad address
counter.
Resolution:
The fix is to ignore the bad address counter while
computing the ifInDiscards statistic.
7. The HP-PB 10 Mb/s ethernet driver initialization code
did not mark ifOper up when initialization was complete.
8. The HP-PB 10 Mb/s ethernet driver incorrectly
reused memory it freed.
9. DLPI incorrectly called a STREAMS interface to
clean up the queues when a protocol is unbound,
an interface is detached from the stream, or a
stream is closed.
Resolution:
DLPI no longer calls the interface. The STREAMS
framework now cleans up the queues by itself.
10. Drivers did not loopback outbound packets while in
promiscuous mode. DLPI did not have the filter to
send such packets upstream.
Resolution:
DLPI now has the required filter. Drivers will
individually release patches or application releases
to support looping back outbound packets in
promiscuous mode. This patch would be a prerequisite
dependency.
11. lanscan passed an incorrect data structure to the
APA lanscan shared library.
12. An ARP reply received by a Token Ring interface with
source routing disabled was not sent by DLPI to the ARP
resolver in a proper form.
13. The link level functionality to receive a trailer
encapsulated packet was not provided for the
mblk drivers.
Based on HP-UX patch PHNE_16990:
1. Under heavy networking load, DLPI wakeup data structures
were getting corrupted in certain situations.
2. DLPI had a limit of 16 on the number of multicast
addresses that could be enabled per stream. This limit
has been removed by this patch.
3. The promiscuous level was not saved correctly during
sleep processing.
4. DLPI was incorrectly dropping unicast packets even for
a bound stream while in multicast promiscuous mode. It is
only supposed to do so for unbound streams.
5. DLPI was incorrectly assuming that every inbound packet
has data after link level header.
6 An incorrect argument was passed to a macro that searches
for multicast addresses in a global list.
7. DLPI was not handling errors correctly when an attempt
was made to send an IP packet while a control request
was pending.
8. Performance of promiscuous mode applications is enhanced
by avoiding a full copy of the packet.
Based on HP-UX patch PHNE_15969:
1. DLPI has been enhanced to support HP Auto-Port
Aggregation Software.
2. linkloop has been modified to use mtu size limit as in
dl_ppa_info.
3. It has been observed that Inbound Packet Scheduling
improved network performance only when the ratio of CPUs
to NIC cards is high. Hence, a run time switch has been
provided to be able to turn it on/off as desired. It is
turned off by default.
4. PHNE_15591 corrected several problems with the control
scripts included with the Networking product. The
Software Distributor product (SD-UX) overwrote some
of the changes that the patch made to the control
scripts. This resulted in the error messages listed
in the "Symptoms" field. PHNE_15969 uses a different
mechanism to modify the product control scripts,
thereby eliminating the overwrite problem.
5. Checksum offload ethernet drivers expect 8 bytes
of checksum information for each outbound packet. This
information was not handled correctly for test packets
that are used by linkloop. The problem is corrected in
PHNE_15969.
Based on HP-UX patch PHNE_15591:
1. A LAN interface is bound to a specific processor for
handling its interrupts. Every packet coming in through
this interface will be processed by that processor
initially. If the time spent on processing each inbound
packet is not reasonably short, the processor could
become a bottleneck. Inbound Packet Scheduling allows
DLPI to pick a processor that may be different from the
one handling the interrupt to process the packet up
the networking stack. This can result in performance
and scalability improvements, especially if the processor
selected is the same as the one running an application
that is to receive the packet.
2. Under heavy load, a LAN driver may return an
ENOBUFS error to DLPI for each outbound packet.
DLPI passes these error messages upstream. If the
application does not read these messages, they
will remain in the Streams head and consume
memory resources. This eventually consumes all
available memory and the system appears to hang.
3. When -X/-x options were added to lanadmin, a defect
was introduced in parsing options. Due to this,
the -b/-B options fail to work.
4. The verify control scripts supplied with the Networking
product checked for the existence of the hardware
supported by the lan2 and lan3 drivers and logged
errors, warnings, and notes if these were not found.
Newer HP-9000 systems have 100Base-T interfaces, for
example, and these errors/warnings/notes are
inappropriate. The scripts have been changed to no
longer require the presence of the earlier hardware.
Based on HP-UX patch PHNE_14632:
1. Multicast Delete requests were not sent down to the
hardware level by LANC. This resulted in stale
multicast addresses enabled in the hardware. This has
been corrected.
2. For Token Ring, if the stream is not bound, the
DL_SET_PHYS_ADDR_REQ request comes with 6 bytes mac
address. Currently it is rejected in hp_dlpi_control
if the mac address is not 6 + RIF_SIZE.
3. Some debug printf's for a dlpi fix (in PHNE_14370) was
mistakenly left in the production code. Note that the
messages by default also go into syslog file.
4. lanadmin -A is enhanced to reset the MAC address to
default. When the address string is DEFAULT, lanadmin
restores the default address for the card.
Based on HP-UX patch PHNE_14370:
1. During the Service Guard switch over from one
interface to another, the transport code has a
window where an IRE has been marked off, but its arp
cache is around. At this time for a packet going
out to this removed interface, ip would not find an
IRE for it and will try to forward it. Since the
arp cache entry for it can be found, the packet will
be sent down with the stale mac address. When the
driver gets this packet, it loops back upward, and
ip in turn forwards down again. This looping repeats
until Time To Live expires and the packet gets freed.
Since this is an mbuf driver, the freeing will go
through all the wrapper free routines, and
eventually causes stack overflow panic.
2. Process issuing DL_HP_HW_RESET was getting woken up
after PORT_RESET phase of reset process. If a DLPI
request is issued immediately after DL_HP_HW_RESET,
ENXIO may be returned if the driver has not finished
the whole reset process. PORT_RESET phase is now
modified to wake up all entries in cmd_q other than
the one corresponding to RESET process. The RESET
process will be woken up by the process_looper after
the loopback test.
3. Enhanced LANC to support MBLK message buffers for
Token Ring Drivers.
4. The type 2 code has always assumed that the FDDI
drivers support CKO feature. So when it builds the
LLC header for FDDI, the CKO info is always
prepended to it. This is incorrect for some recently
introduced FDDI's that do not support CKO.
5. For Token Ring, DLPI returns incorrect
dl_addr_length in the dl_info_ack, thus the
subsequent DL_ENABMULTI_REQ request will fail due to
the wrong dl_addr_length in the request. Other
fixes are also included to support ip multicast for
Token Ring. For 11.0 Token Ring, since lanscan, arp
output, and lanadmin all present the MAC address in
wire format, the MAC address in any request to DLPI
is supposed to be in wire format. However, an
exception was found for the case of ip multicast.
DLPI fixes include the following
- Bit swap the mac address in the DL_ENABMULTI_REQ
and DL_DISABMULTI_REQ before passing it to the
driver.
- Bit swap the mac address for the outbound and
inbound ip multicast packets.
- Treat Token Ring's functional address as a legal
multicast address for the inbound packets.
6. The promiscuous mode data filtering and routing of
the same for the "unfiltered" stream was not
supported at LANC/DLPI level. Individual drivers
implemented this in different ways which lead to
incorrect behaviour. By supporting this at
LANC/DLPI level, drivers could directly use this
feature rather than implementing this at driver
level.
7. If a packet is a broadcast packet or a multicast
packet, DLPI takes normal path instead of fast path.
In normal path, checksum offload is not handled
properly. That is, it does not prepend the cko_info
block to the mblk, though MSGCKO is turned on in the
b_flag. When MSGCKO is turned on, IP assumes the
first 8 bytes as cko_info block and uses it and this
results in IP dropping the packets as bad header.
8. When there are huge number of interface cards
installed on the system(For example: on 64bit
system, more than 11), lanadmin does not work
properly due to insufficient allocation of buffer to
retrieve the information regarding all the interface
cards.
Based on HP-UX patch PHNE_14106:
1. Lanscan is enhanced to recognize the MAC type of
HyperFabric cards.
2. An enhancement has been made in lanadmin to get and set
driver specific options. This will support speed and
mode changes for 100BT cards.
3. When multiple interface cards exist on the system with
the same PPA number and only one of them support DLPI,
but one which is not supporting the DLPI is ahead of the
supporting the DLPI in the list, this problem happens.
This is because, not proper conditions being used while
searching the list for the required PPA.
4. When there are huge number of interface cards installed
on the system(For example: on 64bit system, more than
11), lanadmin does not work properly due to insufficient
allocation of buffer to retrieve the information
regarding all the interface cards.
5. The ATM interfaces up to el900 are well recognized at
upper level (IP), but not el1000 or more. This is
because, in lanscan command, the number of digits to use
for display from the PPA/NMID is hard coded as 3.
6. When ATM card is installed on a system, lanscan -v
command reports that it can not open a shared library
/usr/lib/lanscan/libpeatm.sl. This is because, HP DLPI
do not support ATM drivers and they have their own DLPI
layer and hence ATM drivers do not supply the shared
library used by lanscan command. The lanscan command
needs to check whether the corresponding driver supports
HP DLPI or not. Only for those driver supporting HP
DLPI, lanscan should open the shared library.
7. HP 9000/UX Token Ring does not conform to the IBM Token
Ring Network Architecture Specification with respect to
maintaining the source routing information to an
off-ring system which maybe compliant with the same
specification.
8. DLPI performance enhancement by code path reduction on
outbound and inbound fast path (IP uses it).
9. Due to a defect in hp_dlpi_close/detach some amount of
memory was not being freed. This was causing memory
leak. Also in hp_dlpi_close/detach the driver was
accessing memory which was already freed. This was
causing a panic.
10. For drivers supporting IP level multicasting, the
multicast address list is stored in a separate list.
Hence dlpi should check if the driver supports IP level
multicasting. If so it should return the multicast
address list from this list while processing
DL_HP_MULTICAST_REQ.
11. When a stream bound to SNAP for ethernet, the mtu was
not adjusted and remains to be 1500 (should be 1492).
The TCP and IP send data based on the wrong size of mtu,
which will exceed the driver can take and cause the
incomplete data to be sent and be rejected in the
received site.
12. In t2_t1_xid_auto_res() routine, the PUT_MQUAD() macro
is being used. This macro is of multi-line code, thus
it needs a parenthesis around it.
13. In hp_dlpi_subs_bind() routine, t2_log() is called with
hp_dlpi_intr() for the mblk driver, and
hp_dlpi_mblk_intr() for the mbuf driver. The
hp_dlpi_intr() and hp_dlpi_mblk_intr() should be
reversed.
14. "linkloop" does not check the MTU on the PPA prior to
sending out the test frame. If the customer has changed
the MTU of the link, linkloop will fail unless the MTU
size (or less) is specified via the -s parameter. This
causes the MC/ServiceGuard cmlogconfig to fail when it
shouldn't. The fix would be check the mtu size via
DL_HP_PPA_REQ (dl_mtu) or DL_INFO_REQ (dl_max_sdu)
rather than using the default size for the mac type.
Based on HP-UX patch PHNE_14027:
1. PHNE_13076 is not a critical patch. However since this
patch has to be released in 11.0 SR Extension media it
has to be tagged critical. Hence releasing a new patch
superseding PHNE_13076 and tagging it as critical.
Based on HP-UX patch PHNE_13076:
1. The sio/wsio dependency is missing from the master
files of HP-PB and Built-in ethernet drivers.
Consequently, if other drivers, e.g., stape, which
specify this dependency are removed from
/stand/system, sio/wsio also disappears and an
unbootable kernel results.
2. Functions in lanadmin shared libraries for HP-PB and
Built-in ethernet drivers, open catalog files using
catopen() but do not close the same on return.
Hence, when lanadmin invokes these functions within
the lanadmin shared libraries, for a reasonably
large number of times, number of open files will
cross maxfiles limit causing a failure in the next
catopen(). However this failure occurs only when
the LANG environment variable is set as that would
result in some appropriate catalog file being
opened. If the LANG variable is not set ( unset )
no catalog files are opened and the default messages
are printed and the problem does not occur.
3. A DLPI routine saves data from an uninitialized
32bit variable, which could be a random value. If
this DLPI data happens to match two particular
values, then the Ethernet driver cannot successfully
deliver the IP packets until this DLPI data is
changed. This results in the delay in delivering
TCP packets.
SR:
8606194835 8606189377 8606195129 8606185750 8606203925
8606167823 8606167824 8606152325 8606154248 8606171911
8606186218 8606161844 8606168898 8606166220 8606158448
8606170665 8606125467 8606134083 8606140332 8606126024
8606140139 8606160333 8606161548 8606133337 8606143902
8606129845 8606151820 8606141242 8606135478 8606145062
8606143906 8606129886 8606130675 8606128665 8606129248
8606130949 8606131180 8606132758 8606129439 8606139097
8606126322 8606124381 8606126350 8606126167 8606127732
8606124545 8606128305 8606127485 8606128595 8606114057
8606104232 8606103762 8606101233 8606111864 5003459701
1653294488 4701431064 4701431072 5003461681 4701423897
5003451328 5003251215 5000699934 5003419895 4701400879
5003412817 1653251025 5003388603 5003387050 5003320655
1653249565 1653230078 4701374710
Patch Files:
Networking.LAN2-KRN,fr=B.11.04,fa=HP-UX_B.11.04_64,v=HP:
/usr/conf/master.d/lan
/usr/conf/lib/liblan.a
/usr/conf/lib/lan_dbg0.o
Networking.LAN2-KRN,fr=B.11.04,fa=HP-UX_B.11.04_32,v=HP:
/usr/conf/master.d/lan
/usr/conf/lib/liblan.a
/usr/conf/lib/lan_dbg0.o
Networking.LAN-RUN,fr=B.11.04,fa=HP-UX_B.11.04_32/64,v=HP:
/usr/sbin/linkloop
/usr/sbin/lanscan
/usr/sbin/lanadmin
/usr/sbin/landiag
/usr/lib/lanadmin/libdslan2.1
/usr/lib/lanadmin/libdslan3.1
/usr/lib/nls/msg/C/lanadmin.cat
/usr/lib/nls/msg/C/lanscan.cat
/sbin/init.d/hpether
Networking.NW-ENG-A-MAN,fr=B.11.04,fa=HP-UX_B.11.04_32/64,
v=HP:
/usr/share/man/man1m.Z/lanadmin.1m
/usr/share/man/man1m.Z/lanscan.1m
what(1) Output:
Networking.LAN2-KRN,fr=B.11.04,fa=HP-UX_B.11.04_64,v=HP:
/usr/conf/master.d/lan:
PHNE_21217 $Revision: 1.3.118.3 $
/usr/conf/lib/liblan.a:
lanc_input.c: PHNE_22962 Oct 18 2001 15:44:39
lan_token.c: PHNE_18409 Oct 18 2001 15:44:45
LAN: liblan: PHNE_24413 Oct 18 2001 15:44:49
lanc.c: PHNE_24413 Oct 18 2001 15:44:49
lan_t2.c: PHNE_21217 : DRV_NO_MAC_CONVERT and other
changes Oct 18 2001 15:44:52
lan_dlpi.c: PHNE_24413 Oct 18 2001 15:45:45
$Source: kern/sio/lan3.c, hpuxsysio, vvos_rose, rose
0179 $ $Date: 00/12/27 05:31:28 $ $Revision:
1.8.1.8 PATCH_11.04 (PHNE_22825) $
lan2.c: PHNE_22353 Date:Oct 18 2001 15:46:18
/usr/conf/lib/lan_dbg0.o:
None
Networking.LAN2-KRN,fr=B.11.04,fa=HP-UX_B.11.04_32,v=HP:
/usr/conf/master.d/lan:
PHNE_21217 $Revision: 1.3.118.3 $
/usr/conf/lib/liblan.a:
lanc_input.c: PHNE_22962 Oct 18 2001 13:46:29
lan_token.c: PHNE_18409 Oct 18 2001 13:46:42
LAN: liblan: PHNE_24413 Oct 18 2001 13:46:51
lanc.c: PHNE_24413 Oct 18 2001 13:46:51
lan_t2.c: PHNE_21217 : DRV_NO_MAC_CONVERT and other
changes Oct 18 2001 13:46:59
lan_dlpi.c: PHNE_24413 Oct 18 2001 13:47:55
$Source: kern/sio/lan3.c, hpuxsysio, vvos_rose, rose
0179 $ $Date: 00/12/27 05:31:28 $ $Revision:
1.8.1.8 PATCH_11.04 (PHNE_22825) $
lan2.c: PHNE_22353 Date:Oct 18 2001 13:48:37
/usr/conf/lib/lan_dbg0.o:
None
Networking.LAN-RUN,fr=B.11.04,fa=HP-UX_B.11.04_32/64,v=HP:
/usr/sbin/linkloop:
$Revision: Hewlett-Packard ISSL Level vvos_rose42 $
$Header: Hewlett-Packard ISSL Release vvos_r
ose $ $Date: Thu Oct 18 12:46:48 EDT 2001 $
$Source: net/lanlink/LAN/linkloop/linkloop.c, hpuxcm
dnet, vvos_rose, rose0158 $ $Date: 99/06/08
10:49:49 $ $Revision: 1.22 PATCH_11.04 (PHNE
_18560) $
LAN: Version: B.11.00 $Date: 97/10/15 10:44:26 $
/usr/sbin/lanscan:
lanscan.c: PHNE_22331
LAN: Version: B.11.00 $Date: 97/10/15 10:44:26 $
vmmap.o $Revision: 82.2 $
/usr/sbin/lanadmin:
$Revision: Hewlett-Packard ISSL Level vvos_rose42 $
$Header: Hewlett-Packard ISSL Release vvos_r
ose $ $Date: Thu Oct 18 12:46:48 EDT 2001 $
$Source: net/lanlink/LAN/lanadmin/lanadmin.c, hpuxcm
dnet, vvos_rose, rose0257 $ $Date: 01/10/12
16:56:33 $ $Revision: 1.23 PATCH_11.04 (PHNE
_25076) $
LAN: Version: B.11.00 $Date: 97/10/15 10:44:26 $
lanadmin_mg.c: PHNE_15969 98/09/15
/usr/sbin/landiag:
$Revision: Hewlett-Packard ISSL Level vvos_rose42 $
$Header: Hewlett-Packard ISSL Release vvos_r
ose $ $Date: Thu Oct 18 12:46:48 EDT 2001 $
$Source: net/lanlink/LAN/lanadmin/lanadmin.c, hpuxcm
dnet, vvos_rose, rose0257 $ $Date: 01/10/12
16:56:33 $ $Revision: 1.23 PATCH_11.04 (PHNE
_25076) $
LAN: Version: B.11.00 $Date: 97/10/15 10:44:26 $
lanadmin_mg.c: PHNE_15969 98/09/15
/usr/lib/lanadmin/libdslan2.1:
dslan2.c for PHNE_18409 Feb 26 2001 14:14:31
/usr/lib/lanadmin/libdslan3.1:
dslan3.c for PHNE_18409 Feb 26 2001 14:14:37
/usr/lib/nls/msg/C/lanadmin.cat:
None
/usr/lib/nls/msg/C/lanscan.cat:
None
/sbin/init.d/hpether:
hpether: PHNE_22331 $Revision: 1.4.119.1 $ $Date: 96
/10/01 12:11:36 $
Networking.NW-ENG-A-MAN,fr=B.11.04,fa=HP-UX_B.11.04_32/64,
v=HP:
/usr/share/man/man1m.Z/lanadmin.1m:
None
/usr/share/man/man1m.Z/lanscan.1m:
None
cksum(1) Output:
Networking.LAN2-KRN,fr=B.11.04,fa=HP-UX_B.11.04_64,v=HP:
1235788784 4094 /usr/conf/master.d/lan
885139375 706294 /usr/conf/lib/liblan.a
1544944058 302568 /usr/conf/lib/lan_dbg0.o
Networking.LAN2-KRN,fr=B.11.04,fa=HP-UX_B.11.04_32,v=HP:
1235788784 4094 /usr/conf/master.d/lan
1237163255 379628 /usr/conf/lib/liblan.a
2732829674 243544 /usr/conf/lib/lan_dbg0.o
Networking.LAN-RUN,fr=B.11.04,fa=HP-UX_B.11.04_32/64,v=HP:
1216609738 28672 /usr/sbin/linkloop
3051018691 40960 /usr/sbin/lanscan
3796755368 53248 /usr/sbin/lanadmin
3796755368 53248 /usr/sbin/landiag
3715210576 16384 /usr/lib/lanadmin/libdslan2.1
2310738438 16384 /usr/lib/lanadmin/libdslan3.1
2340268250 6631 /usr/lib/nls/msg/C/lanadmin.cat
595530027 2173 /usr/lib/nls/msg/C/lanscan.cat
1108542347 5272 /sbin/init.d/hpether
Networking.NW-ENG-A-MAN,fr=B.11.04,fa=HP-UX_B.11.04_32/64,
v=HP:
678949585 5276 /usr/share/man/man1m.Z/lanadmin.1m
2207105967 1909 /usr/share/man/man1m.Z/lanscan.1m
Patch Conflicts: None
Patch Dependencies:
s700: 11.04: PHNE_18347
s800: 11.04: PHNE_18347
Hardware Dependencies: None
Other Dependencies: None
Supersedes:
PHNE_18560 PHNE_22825
Equivalent Patches:
PHNE_24413:
s700: 11.00
s800: 11.00
Patch Package Size: 1890 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_25076
5. Run swinstall to install the patch:
swinstall -x autoreboot=true -x patch_match_target=true \
-s /tmp/PHNE_25076.depot
By default swinstall will archive the original software in
/var/adm/sw/save/PHNE_25076. If you do not wish to retain a
copy of the original software, use the patch_save_files option:
swinstall -x autoreboot=true -x patch_match_target=true \
-x patch_save_files=false -s /tmp/PHNE_25076.depot
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_25076.text file is
available in the product readme:
swlist -l product -a readme -d /tmp/PHNE_25076.depot
To put this patch on a magnetic tape and install from the
tape drive, use the command:
dd if=/tmp/PHNE_25076.depot of=/dev/rmt/0m bs=2k
Special Installation Instructions: None
-----End of Document ID: PHNE_25076------------------------------------------
Document ID: PHNE_25073
Date Loaded: 20011026
Title: s700_800 11.04 (VVOS) 4 port PCI 100BT cumulative patch
Patch Name: PHNE_25073
Patch Description: s700_800 11.04 (VVOS) 4 port PCI 100BT cumulative patch
Creation Date: 01/10/09
Post Date: 01/10/26
Hardware Platforms - OS Releases:
s700: 11.04
s800: 11.04
Products:
J4254AA B.11.04.00 B.11.04.01 B.11.04.02
A5506A B.11.04.00 B.11.04.01 B.11.04.02
A5506B B.11.04.02
Filesets:
100BASE-T.100BT-KRN,fr=B.11.04.00,fa=HP-UX_B.11.04_64,v=HP
100BASE-T.100BT-KRN,fr=B.11.04.01,fa=HP-UX_B.11.04_64,v=HP
100BASE-T.100BT-KRN,fr=B.11.04.02,fa=HP-UX_B.11.04_64,v=HP
100BASE-T.100BT-KRN,fr=B.11.04.00,fa=HP-UX_B.11.04_32,v=HP
100BASE-T.100BT-KRN,fr=B.11.04.01,fa=HP-UX_B.11.04_32,v=HP
100BASE-T.100BT-KRN,fr=B.11.04.02,fa=HP-UX_B.11.04_32,v=HP
100BASE-T.100BT-RUN,fr=B.11.04.00,fa=HP-UX_B.11.04_32/64,v=HP
100BASE-T.100BT-RUN,fr=B.11.04.01,fa=HP-UX_B.11.04_32/64,v=HP
100BASE-T.100BT-RUN,fr=B.11.04.02,fa=HP-UX_B.11.04_32/64,v=HP
Automatic Reboot?: Yes
Status: General Release
Critical:
Yes
PHNE_25073: PANIC MEMORY_LEAK
Based on PHNE_24007: PANIC MEMORY_LEAK
PHNE_22982: PANIC
Based on PHNE_22728: PANIC
Based on PHNE_21887: PANIC
Based on PHNE_20423: PANIC
Category Tags:
defect_repair hardware_enablement enhancement
general_release critical panic memory_leak
Path Name: /hp-ux_patches/s700_800/11.X/PHNE_25073
Symptoms:
PHNE_25073:
Port HP-UX patch PHNE_24007 (4 port PCI 100BT) to VVOS.
Based on HP-UX patch PHNE_24007:
1. Link not coming up if switch is rebooted when
speed/duplex value at both ends are set manually.
2. System panics with Data Page Fault.
3. Memory leak in btlan3-6 and btlan drivers.
4. Setuid bit is set for lanadmin library.
PHNE_22982:
Port HP-UX patch PHNE_22728 (4 port PCI 100BT) to VVOS.
Based on HP-UX patch PHNE_22728:
1. 100BT is randomly missing packets.
2. System panics due to instruction page fault.
3. 'netfmt' on 100BT traces causes SIGSEGV while running
HP_APA LAN_MONITOR
4. 100BT card hangs occasionally. The card is unable to
receive any frames.
5. 4 port card fails to reconnect at 100 Full Duplex if a
cable of bad length (35 - 41m) is connected.
6. A false link down event is reported by the driver.
Based on HP-UX patch PHNE_21887:
1. lanadmin -A to change MAC address causes panic:
wait_for_lock
2. Performance degradation & higher CPU utilization with
the 4 port cards.
Based on HP-UX patch PHNE_20423:
1. Start up scripts fail if there are 10 or more lan cards.
2. btlan interface hangs after 36 hours of testing.
3. Nettl displays incorrect informative message about
speed and mode.
4. ER: Display capabilities of the switch after auto
negotiation completion.
5. The driver panics with "spinlock held too long"
message.
6. The driver startup script hpbtlan does not set ppa
and fails to configure the card.
7. SAM does not support altering speed (10 or 100Mbps) and
duplex mode (half or full) settings on the interface.
8. Applications (including lanadmin) receive 10 for 10Mbps
or 100 for 100Mbps for the speed value in the ifSpeed
field of the mib structure. lanadmin therefore displays
10 or 100 for the interface (link) speed.
9. 'lanadmin -x [ppa]' display does not indicate whether
the card is running in auto-negotiation or manual mode.
10.Lanadmin cannot alter the Maximum Transmission Unit (MTU)
size value of the interface.
11.Applications do not receive outbound traffic from the
interface when they enable promiscuous mode on the
interface.
12.Outbound queue length can become negative after clearing
net statistics using lanadmin.
13.Collisions are not detected by btlan driver.
14.The actual link configuration does not reflect what is
manually configured in /etc/rc.config.d/hpbtlanconf.
15.Wrong message is logged in dmesg as "Unable to setup
Read / write prefetch lengths".
16.lanadmin statistics are not updated & cleared correctly.
Defect Description:
PHNE_25073:
Port HP-UX patch PHNE_24007 (4 port PCI 100BT) to VVOS.
Based on HP-UX patch PHNE_24007:
1. JAGad54220:
Link not coming up if switch is rebooted when
speed/duplex value at both ends are set manually.
Driver was clearing all the bits in the BMCR if the
speed/duplex value were set manually. So the card was
getting set to 10HD and since the other end is also
manually set, the link was not coming up.
Resolution:
Now the driver sets the speed and duplex value in the
BMCR based on the value set by the user.
2. JAGad08759:
System panics with Data Page Fault.
wsio_allocate_shared_memory() call made to allocate and
map the transmit descriptor ring seems to have returned
NULL. The driver was not checking the return value of
the call and was calling bzero to init the memory
allocated and this causes a panic.
Stack Trace :
panic+0x14
report_trap_or_int_and_panic+0x80
trap+0xdb8
nokgdb+0x8
bzero_prefetch_sl_method+0x18
_btlan3_init+0x8c
isc_table_traverse+0x70
wsio_init_end+0x10
io_virt_mode_config+0xe8
main+0x128
$vstart+0x48
istackatbase+0x84
Resolution:
The fix is to check the return value of all memory
allocation and mapping calls in the driver init function.
3. JAGad54435:
Memory leak in btlan3-6 and btlan drivers.
The memory leak in 2k byte bucket is tied to inbound
errors and an uninitialized local variable.
That uninitialized local variable in the receive path
resulted in memory leak sometimes when processing frames
received with errors. This variable is required only in
the case of normal frames.
Resolution:
The fix is to check this variable only when processing
frames received without errors.
4. JAGad66231:
btlan3-6 and btlan drivers lanadmin libraries have their
setuid bit set. Setting this bit is not required and may
cause problems that are not foreseen.
Resolution:
The file permissions have been modified so the setuid
bit is not set.
PHNE_22982:
Port HP-UX patch PHNE_22728 (4 port PCI 100BT) to VVOS.
Based on HP-UX patch PHNE_22728:
1. JAGad03897:
When there is a transient overload, the 100BT NIC runs
out of receive descriptors and drops packets. Typically
this is caused by bursty traffic where several hundred
packets are sent to the NIC within a few millisecs.
Resolution:
The number of receive descriptors have been doubled.
2. JAGad24136:
The data portion of the receive buffers was not cacheline
aligned.
Stack trace follows,
A. Original Dump:
freeb_pullupmsg+0x2c4
freeb+0xe4c
freemsg+0x18
ip_rput_local+0x1b80
ip_rput+0x40c
putnext+0x228
hp_dlpi_unitdata_in+0x58
chp_dlpi_mblk_intr_put+0x17c
streams_put_release+0x398
hp_dlpi_mblk_intr+0x7c
lanc_ether_ics+0x230
btlan_receive_frame+0x550
btlan_isr+0x120
dino_isr+0x184
up_ext_interrupt+0x1e0
ivti_patch_to_nop2+0x0
idle+0x5ac
swidle_exit+0x0
B. jaguar:
freeb_pullupmsg+0x2c4
freeb+0xe4c
soreceive+0x12cc
recvit+0x1d4
recvfrom+0x94
syscall+0x758
$syscallrtn+0x0
C. kabalah:
freeb+0xb64
freemsg+0x18
lanc_802_2_ics+0x130
btlan_receive_frame+0x590
btlan_isr+0x120
dino_isr+0x184
mp_ext_interrupt+0x378
ivti_patch_to_nop3+0x0
idle+0x598
swidle_exit+0x0
Resolution:
The 100BT driver now ensures the receive buffers data is
cacheline aligned.
3. JAGad28394:
Wrong number of arguments are passed to a function in the
formatter.
Resolution:
The correct number of arguments are now passed to the
function in the formatter.
4. JAGad33760:
When a very high number of receive errors occur the
driver will lose descriptors. Eventually the card will
no longer be able to receive frames.
Resolution:
The driver now handles receiving errors correctly.
5. JAGad41701:
The national phy chip sets itself to autonegotiate after
reset at cable reconnect time irrespective of the mode
the interface is set to. If the cable length happens to
fall between the 35 to 41 meter range, auto negotiation
fails and the card fails to establish a valid link.
Resolution:
The national phy chip was set to autonegotiate after
reset only if the interface is set to auto-negotiation
mode. Auto-negotiation by the PHY chip is turned off in
all other modes.
6. JAGad40611:
The LXT970 chip is reporting a false link down event if
the symbol error rate increases over a certain limit.
Resolution:
There are two modes in which the LXT970 phy can be
programmed to report a link down event.
1) When the symbol error rate increases over a certain
limit.
2) If the phy loses the scrambler lock.
By default, the LXT970 phy was programmed to operate
in mode 1 where as the DP83840 phy operates in mode 2.
This fix sets the LXT970 phy to operate in mode 2.
As in the case of the DP83840 phy, the fix allows the
MAC to check the symbol errors and report them as FCS
errors. The LXT970 phy operating in mode 2 will not
report false link down events.
Based on HP-UX patch PHNE_21887:
1. JAGad05541: The problem is due to waking up a dlpi
thread while holding spinlock on ICS.
Resolution:
The driver now releases spinlock when it wakes up dlpi
thread in transmit completion function.
2. JAGad04850:
Non-optimal cache alignment value in driver caused
performance degradation & higher CPU utilization.
Resolution:
The cache alignment value is now set to the cache line
size of the system.
Based on HP-UX patch PHNE_20423:
1. JAGac16214: The hpbtlan script greps for a particular
PPA, but this will match for multiple instances if
there are more than 10 cards.(eg, the script greps for
lan1, this will match lan1, lan10, lan11.. etc).
Resolution:
The script is modified so that it will match for only
one instance. The script now greps for "lan<num> ".
2. JAGac12427: The transmit engine of btlan hangs under
following condition - Whenever the driver receives a
packet containing more than 6 mbufs, it tries to coalesce
this packet into one. If the memory allocation fails,
then this packet is queued for transmit as it is, with
out coalescing. This can stall the transmit engine if
the number of mbufs queued needs more transmit
descriptors than what the driver has.
Resolution:
The driver drops the packet in this condition.
3. JAGab81818: The nettl logging message about speed and
mode displays wrong values.
Resolution:
The driver is modified to display correct speed and mode.
4. JAGab64404(ER): The driver was not logging the abilities
of the remote partner after auto negotiation.
Resolution:
The driver is modified to log the capabilities of remote
partner after auto negotiation completion.
5. JAGab71953: The driver holds the lock while resetting
transmit list which sometimes could take long time.
Resolution:
The driver resets the transmit list without acquiring
the lock.
6.JAGab63191: The problem occurs due to an error in hpbtlan
startup script.
Resolution:
The error is fixed in hpbtlan start up script.
7.JAGab64699: No supporting ioctls were implemented in the
driver for SAM to use.
Resolution:
Implemented the required ioctls that the corresponding
code in SAM uses.
8.JAGab64974: The driver stores 10 for 10Mbps and 100 for
100Mbps in its local mib related data structures.
Resolution:
Modified driver code to store 10000000 for 10Mbps and
100000000 for 100Mbps in its local mib data structures.
9.JAGab64383: The driver did not provide ioctls for
lanadmin to use to obtain the information about the mode
(autonegotiation or manual) mode in which it was
operating.
Resolution:
The driver implemented the new ioctl for obtaining the
above mode information.
10.JAGab43887:The driver did not implement ioctl for
lanadmin to use to alter the MTU size value on the
interface.
Resolution:
The driver implemented the new ioctl for changing the
MTU size value for the interface.
11.JAGaa22977:The driver did not implement appropriate
functionality which would return a copy of the
transmitted packet to the upper protocols.
Resolution:
The driver implemented appropriate functionality
which would return a copy of the transmitted packet to
the upper protocols.
12.JAGaa95732:The driver used to erroneously zero the
outbound queue length when clear stat command was
issued. Later when a queued packet was transmitted
successfully the driver decrements the queue length by
one, thus making the counter negative.
Resolution:
The code is modified, not to zero out the out bound
queue length when net statistics clear command is
issued.
13.JAGab64688:The checking for collisions in the driver
was incorrect.The driver used to check for error
summary bit only. This causes collision detection to
go un-noticed.
Resolution:
The driver is modified to check for any and all the
error conditions that can occur during transmission.
14.JAGab70552:The array of link configuration data in
/etc/rc.config.d/hpbtlanconf was non-sequential
which the startup script (/sbin/init.d/hpbtlan)
could not handle correctly.
Resolution:
The startup script (/sbin/init.d/hpbtlan) is modified
to skip over the missing indices in the array and work
through all that are provided.
15.JAGab72844: message logged Unable to setup Read /
write prefetch lengths.
Resolution:
Now the message is no more logged.
16.JAGab70255: Driver reports bad statistics via netstat
and lanadmin.
Resolution:
The driver is modified to update all the statistics
that are supported by the card.
SR:
8606185018 8606139460 8606185233 8606197035 8606171347
8606172441 8606164461 8606159065 8606154819 8606134762
8606136416 8606135717 8606113954 8606113907 8606109120
1653292060 8606101629 4701430140 5003467001 1653286500
5003432179 4701414177 8606103616 8606105029 8606103478
Patch Files:
100BASE-T.100BT-KRN,fr=B.11.04.00,fa=HP-UX_B.11.04_64,v=HP:
100BASE-T.100BT-KRN,fr=B.11.04.01,fa=HP-UX_B.11.04_64,v=HP:
100BASE-T.100BT-KRN,fr=B.11.04.02,fa=HP-UX_B.11.04_64,v=HP:
/usr/conf/lib/libbtlan.a
/usr/conf/lib/btlan_q4.o
100BASE-T.100BT-KRN,fr=B.11.04.00,fa=HP-UX_B.11.04_32,v=HP:
100BASE-T.100BT-KRN,fr=B.11.04.01,fa=HP-UX_B.11.04_32,v=HP:
100BASE-T.100BT-KRN,fr=B.11.04.02,fa=HP-UX_B.11.04_32,v=HP:
/usr/conf/lib/libbtlan.a
/usr/conf/lib/btlan_q4.o
100BASE-T.100BT-RUN,fr=B.11.04.00,fa=HP-UX_B.11.04_32/64,
v=HP:
100BASE-T.100BT-RUN,fr=B.11.04.01,fa=HP-UX_B.11.04_32/64,
v=HP:
100BASE-T.100BT-RUN,fr=B.11.04.02,fa=HP-UX_B.11.04_32/64,
v=HP:
/usr/lib/lanadmin/libdsbtlan.1
/usr/lib/lanadmin/libdsbtlan.sl
/usr/lib/libfmtbtlan.1
/usr/lib/libfmtbtlan.sl
/usr/lib/nls/msg/C/fmtbtlan.cat
/usr/sbin/hpbtlan_init
/sbin/init.d/hpbtlan
/sbin/rc2.d/S333hpbtlan
/usr/lib/nls/msg/C/dsbtlan.cat
/usr/newconfig/etc/rc.config.d/hpbtlanconf
what(1) Output:
100BASE-T.100BT-KRN,fr=B.11.04.00,fa=HP-UX_B.11.04_64,v=HP:
/usr/conf/lib/libbtlan.a:
100BT : btlan.c PCI 4 PORT 100BASE-T PHNE_24007 B.11
.00.04 $Revision: 1.76 $ $Date: 2001/04/01 1
4:07:59 $
/usr/conf/lib/btlan_q4.o:
None
100BASE-T.100BT-KRN,fr=B.11.04.00,fa=HP-UX_B.11.04_32,v=HP:
/usr/conf/lib/libbtlan.a:
100BT : btlan.c PCI 4 PORT 100BASE-T PHNE_24007 B.11
.00.04 $Revision: 1.76 $ $Date: 2001/04/01 1
4:07:59 $
/usr/conf/lib/btlan_q4.o:
None
100BASE-T.100BT-RUN,fr=B.11.04.00,fa=HP-UX_B.11.04_32/64,
v=HP:
/usr/lib/lanadmin/libdsbtlan.1:
libdsbtlan.sl: Version: B.11.00 $Date: 2000/08/31 16
:06:18 $
/usr/lib/lanadmin/libdsbtlan.sl:
libdsbtlan.sl: Version: B.11.00 $Date: 2000/08/31 16
:06:18 $
/usr/lib/libfmtbtlan.1:
BTLAN: Version: B.11.00 $Date: 2000/01/18 15:5
9:37 $
/usr/lib/libfmtbtlan.sl:
BTLAN: Version: B.11.00 $Date: 2000/01/18 15:5
9:37 $
/usr/lib/nls/msg/C/fmtbtlan.cat:
None
/usr/sbin/hpbtlan_init:
hpbtlan_init $Revision: 1.1 $ $Date: 99/12/20 10:39
:34 $
/sbin/init.d/hpbtlan:
hpbtlan $Revision: 1.2 $ $Date: 2000/09/13 09:53:32
$
/sbin/rc2.d/S333hpbtlan:
hpbtlan $Revision: 1.2 $ $Date: 2000/09/13 09:53:32
$
/usr/lib/nls/msg/C/dsbtlan.cat:
None
/usr/newconfig/etc/rc.config.d/hpbtlanconf:
hpbtlanconf $Revision: 1.2 $ $Date: 2000/03/02 10:14
:44 $
cksum(1) Output:
100BASE-T.100BT-KRN,fr=B.11.04.00,fa=HP-UX_B.11.04_64,v=HP:
74118403 121748 /usr/conf/lib/libbtlan.a
1437153964 227168 /usr/conf/lib/btlan_q4.o
100BASE-T.100BT-KRN,fr=B.11.04.00,fa=HP-UX_B.11.04_32,v=HP:
688980068 70900 /usr/conf/lib/libbtlan.a
1988136143 183272 /usr/conf/lib/btlan_q4.o
100BASE-T.100BT-RUN,fr=B.11.04.00,fa=HP-UX_B.11.04_32/64,
v=HP:
4248413760 28672 /usr/lib/lanadmin/libdsbtlan.1
4248413760 28672 /usr/lib/lanadmin/libdsbtlan.sl
3532053831 12288 /usr/lib/libfmtbtlan.1
3532053831 12288 /usr/lib/libfmtbtlan.sl
3467707698 14341 /usr/lib/nls/msg/C/fmtbtlan.cat
799983117 5994 /usr/sbin/hpbtlan_init
904187253 8249 /sbin/init.d/hpbtlan
904187253 8249 /sbin/rc2.d/S333hpbtlan
2624246182 3996 /usr/lib/nls/msg/C/dsbtlan.cat
2567160831 1270 /usr/newconfig/etc/rc.config.d/hpbtlanconf
Patch Conflicts: None
Patch Dependencies:
s700: 11.04: PHNE_21156 PHNE_18560
s800: 11.04: PHNE_21156 PHNE_18560
Hardware Dependencies: None
Other Dependencies: None
Supersedes:
PHNE_22982
Equivalent Patches:
PHNE_24007:
s700: 11.00
s800: 11.00
Patch Package Size: 710 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_25073
5. Run swinstall to install the patch:
swinstall -x autoreboot=true -x patch_match_target=true \
-s /tmp/PHNE_25073.depot
By default swinstall will archive the original software in
/var/adm/sw/save/PHNE_25073. If you do not wish to retain a
copy of the original software, use the patch_save_files option:
swinstall -x autoreboot=true -x patch_match_target=true \
-x patch_save_files=false -s /tmp/PHNE_25073.depot
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_25073.text file is
available in the product readme:
swlist -l product -a readme -d /tmp/PHNE_25073.depot
To put this patch on a magnetic tape and install from the
tape drive, use the command:
dd if=/tmp/PHNE_25073.depot of=/dev/rmt/0m bs=2k
Special Installation Instructions:
A new version of file /etc/rc.config.d/hpbtlanconf
is delivered as part of this patch,
as /usr/newconfig/etc/rc.config.d/hpbtlanconf file.
If you have edited /etc/rc.config.d/hpbtlanconf file,
you may want to merge these files.
To set speed and duplex via SAM, users need to install SAM
patch: PHCO_22107
ifconfig down/up is needed while changing MTU using
lanadmin -[M|R] options.
-----End of Document ID: PHNE_25073------------------------------------------
Document ID: PHNE_25072
Date Loaded: 20011026
Title: s700_800 11.04 (VVOS) PCI 100BT lan cumulative patch
Patch Name: PHNE_25072
Patch Description: s700_800 11.04 (VVOS) PCI 100BT lan cumulative patch
Creation Date: 01/10/08
Post Date: 01/10/26
Hardware Platforms - OS Releases:
s700: 11.04
s800: 11.04
Products:
B5509BA B.11.04.01 B.11.04.02 B.11.04.03 B.11.04.04
B5509BA B.11.04.05
J4253AA B.11.04.01 B.11.04.02 B.11.04.03 B.11.04.04
J4253AA B.11.04.05
A5230A B.11.04.01 B.11.04.02 B.11.04.03 B.11.04.04
A5230A B.11.04.05
Filesets:
100BT-PCI-KRN.100BT-KRN64,fr=B.11.04.01,fa=HP-UX_B.11.04_64,v=HP
100BT-PCI-KRN.100BT-KRN64,fr=B.11.04.02,fa=HP-UX_B.11.04_64,v=HP
100BT-PCI-KRN.100BT-KRN64,fr=B.11.04.03,fa=HP-UX_B.11.04_64,v=HP
100BT-PCI-KRN.100BT-KRN64,fr=B.11.04.04,fa=HP-UX_B.11.04_64,v=HP
100BT-PCI-KRN.100BT-KRN64,fr=B.11.04.05,fa=HP-UX_B.11.04_64,v=HP
100BT-PCI-KRN.100BT-KRN32,fr=B.11.04.01,fa=HP-UX_B.11.04_32,v=HP
100BT-PCI-KRN.100BT-KRN32,fr=B.11.04.02,fa=HP-UX_B.11.04_32,v=HP
100BT-PCI-KRN.100BT-KRN32,fr=B.11.04.03,fa=HP-UX_B.11.04_32,v=HP
100BT-PCI-KRN.100BT-KRN32,fr=B.11.04.04,fa=HP-UX_B.11.04_32,v=HP
100BT-PCI-KRN.100BT-KRN32,fr=B.11.04.05,fa=HP-UX_B.11.04_32,v=HP
100BT-PCI-RUN.100BT-INIT,fr=B.11.04.01,fa=HP-UX_B.11.04_32/64,v=HP
100BT-PCI-RUN.100BT-INIT,fr=B.11.04.02,fa=HP-UX_B.11.04_32/64,v=HP
100BT-PCI-RUN.100BT-INIT,fr=B.11.04.04,fa=HP-UX_B.11.04_32/64,v=HP
100BT-PCI-RUN.100BT-INIT,fr=B.11.04.05,fa=HP-UX_B.11.04_32/64,v=HP
100BT-PCI-RUN.100BT-RUN,fr=B.11.04.01,fa=HP-UX_B.11.04_32/64,v=HP
100BT-PCI-RUN.100BT-RUN,fr=B.11.04.02,fa=HP-UX_B.11.04_32/64,v=HP
100BT-PCI-RUN.100BT-RUN,fr=B.11.04.04,fa=HP-UX_B.11.04_32/64,v=HP
100BT-PCI-RUN.100BT-RUN,fr=B.11.04.05,fa=HP-UX_B.11.04_32/64,v=HP
100BT-PCI-FMT.100BT-FORMAT,fr=B.11.04.01,fa=HP-UX_B.11.04_32/64,v=HP
100BT-PCI-FMT.100BT-FORMAT,fr=B.11.04.02,fa=HP-UX_B.11.04_32/64,v=HP
100BT-PCI-FMT.100BT-FORMAT,fr=B.11.04.04,fa=HP-UX_B.11.04_32/64,v=HP
100BT-PCI-FMT.100BT-FORMAT,fr=B.11.04.05,fa=HP-UX_B.11.04_32/64,v=HP
Automatic Reboot?: Yes
Status: General Release
Critical:
Yes
PHNE_25072: PANIC MEMORY_LEAK
Based on PHNE_24006: PANIC MEMORY_LEAK
PHNE_22980: PANIC
Based on PHNE_22542: PANIC
Based on PHNE_21682: PANIC
Category Tags:
defect_repair enhancement general_release critical panic
memory_leak
Path Name: /hp-ux_patches/s700_800/11.X/PHNE_25072
Symptoms:
PHNE_25072:
Port HP-UX patch PHNE_24006 (PCI 100BT lan) to VVOS
Based on HP-UX patch PHNE_24006:
1. System panics with Data Page Fault.
2. Memory leak in btlan3-6 and btlan drivers.
3. Link not coming up if switch is rebooted when
speed/duplex value at both ends are set manually.
4. E.R: Keep information about which CPU will handle our
interrupts in the ift for debugging.
5. Setuid bit is set for lanadmin library.
PHNE_22980:
Port HP-UX patch PHNE_22542 (PCI 100BT lan) to VVOS
Based on HP-UX patch PHNE_22542:
1. 100BT is randomly missing packets.
2. System panics due to instruction page fault.
3. 'netfmt' on 100BT traces causes SIGSEGV while running
HP_APA LAN_MONITOR
4. 100BT card hangs occasionally. The card is unable to
receive any frames.
Based on HP-UX patch PHNE_21682:
1. lanadmin -A to change MAC address causes panic:
wait_for_lock
Based on HP-UX patch PHNE_20442:
1. Wrong message is logged in dmesg as "Unable to setup
Read / write prefetch lengths".
2. Wrong nettl informative message being logged when speed
is changed using lanadmin.
3. lanadmin statistics are not updated & cleared correctly.
Based on HP-UX patch PHNE_19079:
1. The inbound octet count displayed by lanadmin is always
zero.
2. SAM does not support altering speed (10 or 100Mbps) and
duplex mode (half or full) settings on the interface.
3. Applications (including lanadmin) receive 10 for 10Mbps
or 100 for 100Mbps for the speed value in the ifSpeed
field of the mib structure. lanadmin therefore displays
10 or 100 for the interface (link) speed.
4. 'lanadmin -x [nmid]' display does not indicate whether
the card is running in auto-negotiation or manual mode.
5. lanadmin cannot alter the Maximum Transmission Unit (MTU)
size value of the interface.
6. Applications do not receive outbound traffic from the
interface when they enable promiscuous mode on the
interface.
7. Outbound queue length can become negative after clearing
net statistics using lanadmin.
8. Collisions are not detected by btlan driver.
9. IP Multicasting problems with 100BT when cable is
disconnected and reconnected.
10. The actual link configuration does not reflect what is
manually configured in /etc/rc.config.d/hppci100conf.
Defect Description:
PHNE_25072:
Port HP-UX patch PHNE_24006 (PCI 100BT lan) to VVOS
Based on HP-UX patch PHNE_24006:
1. JAGad08759:
wsio_allocate_shared_memory() call made to allocate and
map the transmit descriptor ring seems to have returned
NULL. The driver was not checking the return value of
the call and was calling bzero to init the memory
allocated and this causes a panic.
Resolution:
The fix is to check the return value of all memory
allocation and mapping calls in the driver init function.
Stack trace follows:
panic+54
report_trap_or_int_and_panic+80
report_trap_or_int_and_panic+0x002c
trap+0xDB8
$call_trap+40
bzero_prefetch_sl_method+18
_btlan3_init+8C
isc_table_traverse+70
wsio_init_end+10
io_virt_mode_config+0xE8
io_virt_mode_config+0x00ac
main+128
$vstart+48
$locore+94
2. JAGad54435:
The memory leak in 2k byte bucket is tied to inbound
errors and an uninitialized local variable.
An uninitialized local variable in the receive path
resulted in memory leak sometimes when processing frames
received with errors. This variable is required only in
the case of normal frames.
Resolution:
The fix is to check this variable only when processing
frames received without errors.
3. JAGad54220:
Link not coming up if switch is rebooted when
speed/duplex value at both ends are set manually.
Driver was clearing all the bits in the BMCR if the
speed/duplex value were set manually. So the card was
getting set to 10HD and since the other end is also
manually set, the link was not coming up.
Resolution:
Now the driver sets the speed and duplex value in the
BMCR based on the value set by the user.
4. JAGad49787:
The CPU to which our interrupts are tied is not known
currently by looking at the ift structure.
Resolution:
This information is now stored in the eim field of
the ift structure.
5. JAGad66231:
btlan* lanadmin libraries have their setuid bit set.
Setting this bit is not required and may cause problems
that are not foreseen.
Resolution:
The file permissions are set in the psf file of a patch.
The psf files will not have this bit set now.
PHNE_22980:
Port HP-UX patch PHNE_22542 (PCI 100BT lan) to VVOS
Based on HP-UX patch PHNE_22542:
1. JAGad03897:
If 100BT NIC does not have access to an available
receive buffer the card will drop packets.
Resolution:
The driver doubled the number of receive buffers
available for the card.
2. JAGad24136:
The data portion of the receive buffers was not cacheline
aligned.
Stack trace follows,
A. Original Dump:
freeb_pullupmsg+0x2c4
freeb+0xe4c
freemsg+0x18
ip_rput_local+0x1b80
ip_rput+0x40c
putnext+0x228
hp_dlpi_unitdata_in+0x58
chp_dlpi_mblk_intr_put+0x17c
streams_put_release+0x398
hp_dlpi_mblk_intr+0x7c
lanc_ether_ics+0x230
btlan_receive_frame+0x550
btlan_isr+0x120
dino_isr+0x184
up_ext_interrupt+0x1e0
ivti_patch_to_nop2+0x0
idle+0x5ac
swidle_exit+0x0
B. jaguar:
freeb_pullupmsg+0x2c4
freeb+0xe4c
soreceive+0x12cc
recvit+0x1d4
recvfrom+0x94
syscall+0x758
$syscallrtn+0x0
C. kabalah:
freeb+0xb64
freemsg+0x18
lanc_802_2_ics+0x130
btlan_receive_frame+0x590
btlan_isr+0x120
dino_isr+0x184
mp_ext_interrupt+0x378
ivti_patch_to_nop3+0x0
idle+0x598
swidle_exit+0x0
Resolution:
The 100BT driver now ensures the receive buffers data is
cacheline aligned.
3. JAGad28394:
Wrong number of arguments are passed to a function in the
formatter.
Resolution:
The correct number of arguments are now passed to the
function in the formatter.
4. JAGad33760:
When a very high number of receive errors occur the
driver will lose descriptors. Eventually the card will
no longer be able to receive frames.
Resolution:
The driver now handles receiving errors correctly.
Based on HP-UX patch PHNE_21682:
1. JAGad05541: The problem is due to waking up a dlpi
thread while holding spinlock on ICS.
Resolution:
The driver now releases spinlock when it wakes up dlpi
thread in transmit completion function.
Based on HP-UX patch PHNE_20442:
1. JAGab72844: message logged Unable to setup Read /
write prefetch lengths.
Resolution:
Now the message is no more logged.
2. JAGab81818: When speed is changed the informative
message logged is not correct.
Resolution:
A correct message is now logged when speed is changed.
3. JAGab70255: Driver reports bad statistics via netstat
and lanadmin.
Resolution:
The driver is modified to update all the statistics
that are supported by the card.
Based on HP-UX patch PHNE_19079:
1. The driver did not properly increment the inbound octet
count.
Resolution:
The driver increments the inbound octet count when a
a packet is received.
2. No supporting ioctls were implemented in the driver for
SAM to use.
Resolution:
Implemented the required ioctls that the corresponding
code in SAM uses.
3. The driver stores 10 for 10Mbps and 100 for 100Mbps in
its local mib related data structures.
Resolution:
Modified driver code to store 10000000 for 10Mbps and
100000000 for 100Mbps in its local mib data structures.
4. The driver did not provide ioctls for lanadmin to use to
obtain the information about the mode (autonegotiation or
manual) mode in which it was operating.
Resolution:
The driver implemented the new ioctl for obtaining the
above mode information.
5. The driver did not implement ioctl for lanadmin to use to
alter the MTU size value on the interface.
Resolution:
The driver implemented the new ioctl for changing the MTU
size value for the interface.
6. The driver did not implement appropriate functionality
which would return a copy of the transmitted packet to
the upper protocols.
Resolution:
The driver implemented appropriate functionality
which would return a copy of the transmitted packet to
the upper protocols.
7. The driver used to erroneously zero the outbound queue
length when clear stat command was issued. Later when a
queued packet was Transmitted successfully the driver
decrements the queue length by one, thus making the
counter negative.
Resolution:
The code is modified, not to zero out the out bound queue
length when net statistics clear command is issued.
8. The checking for collisions in the driver was incorrect.
The driver used to check for error summary bit only.
This causes collision detection to go un-noticed.
Resolution:
The driver is modified to check for any and all the
error conditions that can occur during transmission.
9.IP Multicast addresses were lost when there is a cable
disconnect and reconnect. This is due to driver state
being still down when the link up state is notified to
upper layer.
Resolution:
The driver state is changed to on line before the link
up state is notified to upper layers.
10. The array of link configuration data in
/etc/rc.config.d/hppci100conf was non-sequential
which the startup script (/sbin/init.d/hppci100)
could not handle correctly.
Resolution:
The startup script (/sbin/init.d/hppci100) is modified
to skip over the missing indices in the array and work
through all that are provided
SR:
8606185018 8606139460 8606185233 8606180566 8606197035
8606164461 8606159065 8606134762 8606154819 8606136416
8606105029 8606109120 8606103478 5003432179 1653286500
4701414177 5003467001 4701430140 5003463430 8606103616
Patch Files:
100BT-PCI-KRN.100BT-KRN64,fr=B.11.04.01,fa=HP-UX_B.11.04_64,
v=HP:
100BT-PCI-KRN.100BT-KRN64,fr=B.11.04.02,fa=HP-UX_B.11.04_64,
v=HP:
100BT-PCI-KRN.100BT-KRN64,fr=B.11.04.03,fa=HP-UX_B.11.04_64,
v=HP:
100BT-PCI-KRN.100BT-KRN64,fr=B.11.04.04,fa=HP-UX_B.11.04_64,
v=HP:
100BT-PCI-KRN.100BT-KRN64,fr=B.11.04.05,fa=HP-UX_B.11.04_64,
v=HP:
/usr/conf/lib/libbtlan5.a
/usr/conf/lib/btlan5_dbg.o
100BT-PCI-KRN.100BT-KRN32,fr=B.11.04.01,fa=HP-UX_B.11.04_32,
v=HP:
100BT-PCI-KRN.100BT-KRN32,fr=B.11.04.02,fa=HP-UX_B.11.04_32,
v=HP:
100BT-PCI-KRN.100BT-KRN32,fr=B.11.04.03,fa=HP-UX_B.11.04_32,
v=HP:
100BT-PCI-KRN.100BT-KRN32,fr=B.11.04.04,fa=HP-UX_B.11.04_32,
v=HP:
100BT-PCI-KRN.100BT-KRN32,fr=B.11.04.05,fa=HP-UX_B.11.04_32,
v=HP:
/usr/conf/lib/libbtlan5.a
/usr/conf/lib/btlan5_dbg.o
100BT-PCI-RUN.100BT-INIT,fr=B.11.04.01,
fa=HP-UX_B.11.04_32/64,v=HP:
100BT-PCI-RUN.100BT-INIT,fr=B.11.04.02,
fa=HP-UX_B.11.04_32/64,v=HP:
100BT-PCI-RUN.100BT-INIT,fr=B.11.04.04,
fa=HP-UX_B.11.04_32/64,v=HP:
100BT-PCI-RUN.100BT-INIT,fr=B.11.04.05,
fa=HP-UX_B.11.04_32/64,v=HP:
/usr/sbin/hppci100_init
/usr/newconfig/etc/rc.config.d/hppci100conf
/sbin/init.d/hppci100
100BT-PCI-RUN.100BT-RUN,fr=B.11.04.01,
fa=HP-UX_B.11.04_32/64,v=HP:
100BT-PCI-RUN.100BT-RUN,fr=B.11.04.02,
fa=HP-UX_B.11.04_32/64,v=HP:
100BT-PCI-RUN.100BT-RUN,fr=B.11.04.04,
fa=HP-UX_B.11.04_32/64,v=HP:
100BT-PCI-RUN.100BT-RUN,fr=B.11.04.05,
fa=HP-UX_B.11.04_32/64,v=HP:
/usr/lib/nls/msg/C/dsbtlan5.cat
/usr/lib/lanadmin/libdsbtlan5.sl
100BT-PCI-FMT.100BT-FORMAT,fr=B.11.04.01,
fa=HP-UX_B.11.04_32/64,v=HP:
100BT-PCI-FMT.100BT-FORMAT,fr=B.11.04.02,
fa=HP-UX_B.11.04_32/64,v=HP:
100BT-PCI-FMT.100BT-FORMAT,fr=B.11.04.04,
fa=HP-UX_B.11.04_32/64,v=HP:
100BT-PCI-FMT.100BT-FORMAT,fr=B.11.04.05,
fa=HP-UX_B.11.04_32/64,v=HP:
/usr/lib/libfmtbtlan5.sl
/usr/lib/nls/msg/C/fmtbtlan5.cat
what(1) Output:
100BT-PCI-KRN.100BT-KRN64,fr=B.11.04.01,fa=HP-UX_B.11.04_64,
v=HP:
/usr/conf/lib/libbtlan5.a:
100BT : btlan5.c PCI 100BT Cleanup PHNE_24006 B.11.0
0.08 $Revision: 1.77 $ $Date: 2001/05/08 15:
00:00 $
/usr/conf/lib/btlan5_dbg.o:
None
100BT-PCI-KRN.100BT-KRN32,fr=B.11.04.01,fa=HP-UX_B.11.04_32,
v=HP:
/usr/conf/lib/libbtlan5.a:
100BT : btlan5.c PCI 100BT Cleanup PHNE_24006 B.11.0
0.08 $Revision: 1.77 $ $Date: 2001/05/08 15:
00:00 $
/usr/conf/lib/btlan5_dbg.o:
None
100BT-PCI-RUN.100BT-INIT,fr=B.11.04.01,
fa=HP-UX_B.11.04_32/64,v=HP:
/usr/sbin/hppci100_init:
hppci100_init $Revision: 1.9 $ $Date: 99/08/18 19:4
7:12 $
/usr/newconfig/etc/rc.config.d/hppci100conf:
: hppci100conf
/sbin/init.d/hppci100:
: hppci100
100BT-PCI-RUN.100BT-RUN,fr=B.11.04.01,
fa=HP-UX_B.11.04_32/64,v=HP:
/usr/lib/nls/msg/C/dsbtlan5.cat:
None
/usr/lib/lanadmin/libdsbtlan5.sl:
libdsbtlan5.sl: Version: B.11.00 $Date: 2000/08/31 1
6:06:18 $
100BT-PCI-FMT.100BT-FORMAT,fr=B.11.04.01,
fa=HP-UX_B.11.04_32/64,v=HP:
/usr/lib/libfmtbtlan5.sl:
BTLAN5: Version: B.11.00 $Date: 99/11/18 14:36
:48 $
/usr/lib/nls/msg/C/fmtbtlan5.cat:
None
cksum(1) Output:
100BT-PCI-KRN.100BT-KRN64,fr=B.11.04.01,fa=HP-UX_B.11.04_64,
v=HP:
3355192240 122164 /usr/conf/lib/libbtlan5.a
4249052873 227200 /usr/conf/lib/btlan5_dbg.o
100BT-PCI-KRN.100BT-KRN32,fr=B.11.04.01,fa=HP-UX_B.11.04_32,
v=HP:
644869619 71268 /usr/conf/lib/libbtlan5.a
2100701390 183312 /usr/conf/lib/btlan5_dbg.o
100BT-PCI-RUN.100BT-INIT,fr=B.11.04.01,
fa=HP-UX_B.11.04_32/64,v=HP:
1031270085 6222 /usr/sbin/hppci100_init
4125104724 1288 /usr/newconfig/etc/rc.config.d/hppci100conf
1373922103 8359 /sbin/init.d/hppci100
100BT-PCI-RUN.100BT-RUN,fr=B.11.04.01,
fa=HP-UX_B.11.04_32/64,v=HP:
2624246182 3996 /usr/lib/nls/msg/C/dsbtlan5.cat
3518895204 28672 /usr/lib/lanadmin/libdsbtlan5.sl
100BT-PCI-FMT.100BT-FORMAT,fr=B.11.04.01,
fa=HP-UX_B.11.04_32/64,v=HP:
526315453 12288 /usr/lib/libfmtbtlan5.sl
2881009131 14621 /usr/lib/nls/msg/C/fmtbtlan5.cat
Patch Conflicts: None
Patch Dependencies:
s700: 11.04: PHNE_21156 PHNE_18560
s800: 11.04: PHNE_21156 PHNE_18560
Hardware Dependencies: None
Other Dependencies: None
Supersedes:
PHNE_22980
Equivalent Patches:
PHNE_24006:
s700: 11.00
s800: 11.00
Patch Package Size: 720 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_25072
5. Run swinstall to install the patch:
swinstall -x autoreboot=true -x patch_match_target=true \
-s /tmp/PHNE_25072.depot
By default swinstall will archive the original software in
/var/adm/sw/save/PHNE_25072. If you do not wish to retain a
copy of the original software, use the patch_save_files option:
swinstall -x autoreboot=true -x patch_match_target=true \
-x patch_save_files=false -s /tmp/PHNE_25072.depot
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_25072.text file is
available in the product readme:
swlist -l product -a readme -d /tmp/PHNE_25072.depot
To put this patch on a magnetic tape and install from the
tape drive, use the command:
dd if=/tmp/PHNE_25072.depot of=/dev/rmt/0m bs=2k
Special Installation Instructions:
A new version of file /etc/rc.config.d/hppci100conf
was delivered as a part of this patch, PHNE_25072 which is
/usr/newconfig/etc/rc.config.d/hppci100conf. If you
edit /etc/rc.config.d/hppci100conf you may want to
merge the files.
To set speed and duplex via SAM, users need to install SAM
patch: PHCO_22107
ifconfig down/up is needed while changing MTU using
lanamdin -[M|R] options.
-----End of Document ID: PHNE_25072------------------------------------------
Document ID: PHNE_25070
Date Loaded: 20011026
Title: s700_800 11.04 (VVOS) EISA 100BT patch
Patch Name: PHNE_25070
Patch Description: s700_800 11.04 (VVOS) EISA 100BT patch
Creation Date: 01/09/12
Post Date: 01/10/26
Hardware Platforms - OS Releases:
s700: 11.04
s800: 11.04
Products:
EISA100BT B.11.04.01 B.11.04.02 B.11.04.03 B.11.04.04
Filesets:
100BT-EISA-KRN.100BT-KRN,fr=B.11.04.01,fa=HP-UX_B.11.04_32,v=HP
100BT-EISA-KRN.100BT-KRN,fr=B.11.04.02,fa=HP-UX_B.11.04_32,v=HP
100BT-EISA-KRN.100BT-KRN,fr=B.11.04.03,fa=HP-UX_B.11.04_32,v=HP
100BT-EISA-KRN.100BT-KRN,fr=B.11.04.04,fa=HP-UX_B.11.04_32,v=HP
100BT-EISA-RUN.100BT-RUN,fr=B.11.04.01,fa=HP-UX_B.11.04_32,v=HP
100BT-EISA-RUN.100BT-RUN,fr=B.11.04.02,fa=HP-UX_B.11.04_32,v=HP
100BT-EISA-RUN.100BT-RUN,fr=B.11.04.03,fa=HP-UX_B.11.04_32,v=HP
100BT-EISA-RUN.100BT-RUN,fr=B.11.04.04,fa=HP-UX_B.11.04_32,v=HP
100BT-EISA-RUN.100BT-INIT,fr=B.11.04.01,fa=HP-UX_B.11.04_32,v=HP
100BT-EISA-RUN.100BT-INIT,fr=B.11.04.02,fa=HP-UX_B.11.04_32,v=HP
100BT-EISA-RUN.100BT-INIT,fr=B.11.04.03,fa=HP-UX_B.11.04_32,v=HP
100BT-EISA-RUN.100BT-INIT,fr=B.11.04.04,fa=HP-UX_B.11.04_32,v=HP
100BT-EISA-FMT.100BT-FORMAT,fr=B.11.04.01,fa=HP-UX_B.11.04_32,v=HP
100BT-EISA-FMT.100BT-FORMAT,fr=B.11.04.02,fa=HP-UX_B.11.04_32,v=HP
100BT-EISA-FMT.100BT-FORMAT,fr=B.11.04.03,fa=HP-UX_B.11.04_32,v=HP
100BT-EISA-FMT.100BT-FORMAT,fr=B.11.04.04,fa=HP-UX_B.11.04_32,v=HP
Automatic Reboot?: Yes
Status: General Release
Critical:
Yes
PHNE_25070: HANG
Based on PHNE_23981: HANG
PHNE_22985: PANIC
Based on PHNE_19200: PANIC
PHNE_18790: PANIC
Based on PHNE_16154: PANIC
Based on PHNE_13543: OTHER
Multicast & Promiscuous mode not working
Category Tags:
defect_repair enhancement general_release critical panic
halts_system
Path Name: /hp-ux_patches/s700_800/11.X/PHNE_25070
Symptoms:
PHNE_25070:
port of HP-UX patch PHNE_23981 (EISA 100BT) to VVOS.
Based on HP-UX patch PHNE_23981:
1. EISA FDDI driver hangs because of EISA 100BT's
bus locking. -- JAGad50169
2. Reproducible system hang in oim_open() when
starting SAP. -- JAGad54480
3. suid bit set to lanadmin library. -- JAGad67830
PHNE_22985:
port of HP-UX patch PHNE_19200 (EISA 100BT) to VVOS.
Based on HP-UX patch PHNE_19200:
1. EISA100BT sends corrupted MAC address for DLPI
test-xid requests. -- JAGaa41098
2. linkloop to self doesn't return error when cable is not
connected. -- JAGab03857
3. IP multicast datagrams looped back in the driver.
-- JAGaa41968
4. EISA100BT driver doesn't set ifOper status correctly
in the MIB structure. -- JAGaa21367
5. Some required EISA100BT structures are not available
for Q4. -- JAGaa21642
6. Automatic speed configuration doesn't work for EISA100BT.
-- JAGab46349
7. EISA100BT start-up doesn't give a warning when set to
full duplex. -- JAGaa21652
8. Setting the speed is not possible in hpeisabtconf file.
-- JAGab65054
9. nettl traces are not formatted correctly. -- JAGab64926
10. Minimum frame length in 10BT mode should be 60 bytes
instead of 64 bytes. -- JAGab64392
11. ER: Allow the MTU size configuration using lanadmin.
-- JAGab64413
12. ER: IOCTL support is required for speed and duplex
setting using SAM. -- JAGab64697
13. EISA100BT generates duplicate packets under heavy load.
-- JAGab64911
14. Service Guard doesn't work with new interface naming
convention. -- JAGab64435
15. Startup script does not allow for non-sequential arrays.
-- JAGab70575
16. Panic with 'Already Owns this Spinlock' on EISA 100BT.
-- JAGab68637
17. "lanadmin -S 0" command hangs.
-- JAGab72670
18. DLPI primitive to set physical address succeeds even
for invalid values -- JAGab84309
19. Driver does not return error for invalid multicast
addresses. -- JAGab84311
20. Card does not work in loopback mode with changed MAC
address in hpeisabtconf. -- JAGad09607
PHNE_18790:
Repackage HP-UX patch PHNE_16403 for VVOS.
Based on HP_UX patch PHNE_16403:
1. Performance degradation.
Based on HP-UX patch PHNE_16154:
1. EISA 100BASE-T card does not come up on 715/100/E
workstations.
2. When there is heavy network traffic, EISA 100BASE-T
card does not come up at boot time.
3. EISA 100BASE-T panics on D and C class with Data
Page fault under heavy load.
Based on HP-UX patch PHNE_13543:
1. SAP promiscuous mode and layer2 multicast are not
supported.
2. EISA 100BT returns current MAC address to a factory
MAC address request.
3. Startup scripts to alter the MAC address or the
duplex mode will not function.
Defect Description:
PHNE_25070:
Port HP-UX patch PHNE_23981 (EISA 100BT) to VVOS.
Based on HP-UX patch PHNE_23981:
1. EISA 100BT was holding bus unnecessarily because of
which EISA FDDI driver was hanging.
Resolution:
Unnecessary bus locking has been removed.
2. In the oim_open() function, a linked list was
processed improperly in a while loop.
Resolution:
Processing of the linked list has been modified in
the while loop.
3. The lanadmin library was set with suid bit.
Resolution:
File permissions have been modified.
PHNE_22985:
port of HP-UX patch PHNE_19200 (EISA 100BT) to VVOS.
Based on HP-UX patch PHNE_19200:
1. An upper layer didn't set the source MAC address
while passing the packet to the driver and driver
expected MAC address to be set by upper layer.
Resolution:
Modified transmit path to copy source MAC address
for outbound packets.
2. Driver was not checking interface status for
loopback packets.
Resolution:
Code is modified to check interface status before
looping back the packet.
3. Driver didn't check whether it needs to loop back
the multicast packet to the local host.
Resolution:
The code was modified to check whether driver needs
to loop back the multicast packet.
4. EISA100BT driver was not consistent in setting ifOper
Status in the MIB with respect to lanscan.
Resolution:
Modified code to have consistency for lanadmin &
lanscan states.
5. Some required EISA100BT structures are not available
for Q4.
Resolution:
Added the necessary structures that are required for
Q4 support.
6. EISA100BT start-up script was not passing the speed
value to the 'lanadmin' command.
Resolution:
Start-up script was modified to pass the speed value
to the 'lanadmin' command.
7. EISA100BT start-up script didn't check for full duplex
mode setting.
Resolution:
Added a check for invalid duplex mode.
8. hpeisabtconf file didn't support SPEED variable.
Resolution:
Added SPEED variable in hpeisabtconf file.
9. EISA100BT subsystem formatter was not able to
format the packets properly.
Resolution:
Rewrote the subsystem formatter to fix formatting
problems.
10. EISA100BT driver supported a minimum packet length
of 64 bytes in 10BT mode instead of the standard 60
bytes.
Resolution:
Modified the driver to support a minimum packet
length of 60 bytes instead of 64 bytes.
11. ER: Allow the MTU size configuration using lanadmin.
Resolution:
Added new IOCTL requests to support set/reset MTU
values.
12. ER: IOCTL support is required for speed and duplex
setting using SAM.
Resolution:
Modified driver to support additional ioctl requests
that are required for SAM support.
13. EISA100BT card was sending duplicate packets under
heavy UDP traffic.
Resolution:
Modified transmit path to flush/purge the data in the
cache and synchronized shared memory access between
card and memory.
14. While changing the driver to new naming convention,
the ifDescr MIB variable was not modified to reflect the
same.
Resolution:
Modified the ifDescr MIB variable to use the new naming
convention.
15. Startup script was not able to recognize interface
entries in non-sequential order in file
/etc/rc.config.d/hpeisabtconf
Resolution:
Startup script is modified to process all interface
entries in file /etc/rc.config.d/hpeisabtconf, even
if they are in non-sequential order.
16. The panic happens when the driver receives a
SET_SPEED ioctl when there are pending inbound
packets.
Resolution:
Modified the code to release lock and
reclaim it again after processing pending inbound
packets.
17. Driver used to return negative value for invalid speed
values, due to which DLPI sleeps, and hence the lanadmin
command used to hang.
Resolution:
The driver now returns EINVAL to DLPI in case of an
invalid speed value.
18. The DLPI primitive to set physical address succeeds
even for invalid values (all bits 0's or 1's).
Resolution:
A check has been added for these invalid addresses.
19. Driver returns success for invalid multicast hardware
addresses which do not have the least significant bit
of the first byte set.
Resolution:
A check is now made to ensure that this bit is set.
20. Card does not work in loopback mode with changed MAC
address in hpeisabtconf. Card was sending a loop back
packet to sense speed with new MAC address and was
not getting this packet back.
Resolution:
Card will send a loop back packet with Factory MAC
address to sense speed. After loopback test card
will be set with new MAC address.
PHNE_18790:
Repackage HP-UX patch PHNE_16403 for VVOS.
Based on HP-UX patch PHNE_16403:
1. A busy-wait in the performance path caused the
performance degradation.
Based on HP-UX patch PHNE_16154:
1. The driver did not set the speed correctly in 10Mb mode.
This occurred mainly on 715/100/E systems.
2. The driver sent a loopback packet without sensing the
media speed. The default speed was set to 100Mb. So,
under heavy network traffic the driver failed to receive
the loopback packet in 10Mb mode.
3. The driver did not do proper MP synchronization.
Based on HP-UX patch PHNE_13543:
1. Specific code for support of Promiscuous mode, layer2
multicast did not exist.
2. Returned incorrectly the current MAC address instead
of factory MAC address.
3. Wrong variable name in hpeisabtconf.
SR:
8606180948 8606185278 8606198641 8606164026 5003397125
5003451450 5003440230 1653289090 1653296236 4701430116
5003434928 1653311423 8606103630 8606102706 8606104897
8606112070 8606112072 8606140285 1653275446 1653264465
1653267237 1653263970 1653253013 1653250639 1653249318
Patch Files:
100BT-EISA-KRN.100BT-KRN,fr=B.11.04.01,fa=HP-UX_B.11.04_32,
v=HP:
100BT-EISA-KRN.100BT-KRN,fr=B.11.04.02,fa=HP-UX_B.11.04_32,
v=HP:
100BT-EISA-KRN.100BT-KRN,fr=B.11.04.03,fa=HP-UX_B.11.04_32,
v=HP:
100BT-EISA-KRN.100BT-KRN,fr=B.11.04.04,fa=HP-UX_B.11.04_32,
v=HP:
/usr/conf/lib/libbtlan0.a
100BT-EISA-RUN.100BT-RUN,fr=B.11.04.01,fa=HP-UX_B.11.04_32,
v=HP:
100BT-EISA-RUN.100BT-RUN,fr=B.11.04.02,fa=HP-UX_B.11.04_32,
v=HP:
100BT-EISA-RUN.100BT-RUN,fr=B.11.04.03,fa=HP-UX_B.11.04_32,
v=HP:
100BT-EISA-RUN.100BT-RUN,fr=B.11.04.04,fa=HP-UX_B.11.04_32,
v=HP:
/usr/lib/nls/msg/C/dsbtlan0.cat
/usr/lib/lanadmin/libdsbtlan0.sl
100BT-EISA-RUN.100BT-INIT,fr=B.11.04.01,fa=HP-UX_B.11.04_32,
v=HP:
100BT-EISA-RUN.100BT-INIT,fr=B.11.04.02,fa=HP-UX_B.11.04_32,
v=HP:
100BT-EISA-RUN.100BT-INIT,fr=B.11.04.03,fa=HP-UX_B.11.04_32,
v=HP:
100BT-EISA-RUN.100BT-INIT,fr=B.11.04.04,fa=HP-UX_B.11.04_32,
v=HP:
/usr/sbin/hpeisabt_init
/usr/newconfig/etc/rc.config.d/hpeisabtconf
/sbin/init.d/hpeisabt
100BT-EISA-FMT.100BT-FORMAT,fr=B.11.04.01,
fa=HP-UX_B.11.04_32,v=HP:
100BT-EISA-FMT.100BT-FORMAT,fr=B.11.04.02,
fa=HP-UX_B.11.04_32,v=HP:
100BT-EISA-FMT.100BT-FORMAT,fr=B.11.04.03,
fa=HP-UX_B.11.04_32,v=HP:
100BT-EISA-FMT.100BT-FORMAT,fr=B.11.04.04,
fa=HP-UX_B.11.04_32,v=HP:
/usr/lib/libeisa100btfmt.sl
what(1) Output:
100BT-EISA-KRN.100BT-KRN,fr=B.11.04.01,fa=HP-UX_B.11.04_32,
v=HP:
/usr/conf/lib/libbtlan0.a:
FILESET EISA100BT: libbtlan0: Version: B.11.00.04 P
HNE_23981 $Date: 2001/04/24 21:30:12 $
100BT-EISA-RUN.100BT-RUN,fr=B.11.04.01,fa=HP-UX_B.11.04_32,
v=HP:
/usr/lib/nls/msg/C/dsbtlan0.cat:
None
/usr/lib/lanadmin/libdsbtlan0.sl:
EISA100BT LANADMIN: libdsbtlan0: Version: A.11.00.0
3 PHNE_19200 $Date: 99/09/06 05:19:08 $
100BT-EISA-RUN.100BT-INIT,fr=B.11.04.01,fa=HP-UX_B.11.04_32,
v=HP:
/usr/sbin/hpeisabt_init:
None
/usr/newconfig/etc/rc.config.d/hpeisabtconf:
None
/sbin/init.d/hpeisabt:
None
100BT-EISA-FMT.100BT-FORMAT,fr=B.11.04.01,
fa=HP-UX_B.11.04_32,v=HP:
/usr/lib/libeisa100btfmt.sl:
EISA100BT NETTL: libeisa100btfmt: Version: A.11.00.
03 PHNE_19200 $Date: 99/09/06 05:16:31 $
cksum(1) Output:
100BT-EISA-KRN.100BT-KRN,fr=B.11.04.01,fa=HP-UX_B.11.04_32,
v=HP:
3019403093 305000 /usr/conf/lib/libbtlan0.a
100BT-EISA-RUN.100BT-RUN,fr=B.11.04.01,fa=HP-UX_B.11.04_32,
v=HP:
3862894740 3138 /usr/lib/nls/msg/C/dsbtlan0.cat
3398510434 36864 /usr/lib/lanadmin/libdsbtlan0.sl
100BT-EISA-RUN.100BT-INIT,fr=B.11.04.01,fa=HP-UX_B.11.04_32,
v=HP:
780528253 5258 /usr/sbin/hpeisabt_init
340626021 1254 /usr/newconfig/etc/rc.config.d/hpeisabtconf
2418239947 7667 /sbin/init.d/hpeisabt
100BT-EISA-FMT.100BT-FORMAT,fr=B.11.04.01,
fa=HP-UX_B.11.04_32,v=HP:
2724574513 16384 /usr/lib/libeisa100btfmt.sl
Patch Conflicts: None
Patch Dependencies:
s700: 11.04: PHNE_18560
s800: 11.04: PHNE_18560
Hardware Dependencies: None
Other Dependencies: None
Supersedes:
PHNE_18790 PHNE_22985
Equivalent Patches:
PHNE_23981:
s700: 11.00
s800: 11.00
Patch Package Size: 420 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_25070
5. Run swinstall to install the patch:
swinstall -x autoreboot=true -x patch_match_target=true \
-s /tmp/PHNE_25070.depot
By default swinstall will archive the original software in
/var/adm/sw/save/PHNE_25070. If you do not wish to retain a
copy of the original software, use the patch_save_files option:
swinstall -x autoreboot=true -x patch_match_target=true \
-x patch_save_files=false -s /tmp/PHNE_25070.depot
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_25070.text file is
available in the product readme:
swlist -l product -a readme -d /tmp/PHNE_25070.depot
To put this patch on a magnetic tape and install from the
tape drive, use the command:
dd if=/tmp/PHNE_25070.depot of=/dev/rmt/0m bs=2k
Special Installation Instructions:
1. A new copy of the hpeisabtconf file is provided
under the directory /usr/newconfig/etc/rc.config.d.
This new hpeisabtconf is modified to support new
speed/duplex setting options for startup script.
Copy this configuration file and incorporate any
previous modifications to the
/etc/rc.config.d/hpeisabtconf file to this new
copy and replace the working configuration file
/etc/rc.config.d/hpeisabtconf with it.
2. The speed and duplex setting using SAM will work only
if the SAM patch PHCO_22107 or any patch superseding
it and, the lan common patch PHNE_18560 or any patch
superseding it is installed.
-----End of Document ID: PHNE_25070------------------------------------------
Document ID: PHNE_25069
Date Loaded: 20011026
Title: s700_800 11.04 (VVOS) patch for EISA 100VG-AnyLAN product
Patch Name: PHNE_25069
Patch Description: s700_800 11.04 (VVOS) patch for EISA 100VG-AnyLAN product
Creation Date: 01/09/10
Post Date: 01/10/26
Hardware Platforms - OS Releases:
s700: 11.04
s800: 11.04
Products:
100VG-EISA-KRN B.11.04.00;
100VG-EISA-RUN B.11.04.00;
Filesets:
100VG-EISA-KRN.100VG-KRN,fr=B.11.04.00,fa=HP-UX_B.11.04_32,v=HP
100VG-EISA-RUN.100VG-RUN,fr=B.11.04.00,fa=HP-UX_B.11.04_32,v=HP
100VG-EISA-RUN.100VG-INIT,fr=B.11.04.00,fa=HP-UX_B.11.04_32,v=HP
Automatic Reboot?: Yes
Status: General Release
Critical:
Yes
PHNE_25069: PANIC
PHNE_18453: PANIC
Category Tags:
defect_repair enhancement general_release critical panic
Path Name: /hp-ux_patches/s700_800/11.X/PHNE_25069
Symptoms:
PHNE_25069:
Repackaged HP-UX patch PHNE_22814 for VVOS.
Based on HP-UX patch PHNE_22814:
1. JAGad04670
Panic due to spinlock already owned when sending MIB
event up.
2. JAGab64411
ER: User should be allowed to configure MTU value for
EISA 100VG card.
3. JAGab64916
256 byte memory bucket corruption during heavy traffic,
which might result in system panic.
4. JAGab70602
Start-up script fails when non-sequential array indices
for interfaces are present in the configuration file.
PHNE_18453:
Repackaged HP-UX patch PHNE_15477 for VVOS.
Based on HP-UX patch PHNE_15477:
1. 100vg driver is logging messages and filling up message
buffer.
2. Disconnect of cable from the 10bt port on 100vg card
causes system panic.
3. lanadmin Operating Status on 100vg eisa
shows DOWN and will not reset.
4. Lanadmin fails after sufficient changing of nmid/display
commands.
5. lanadmin -A does not work correctly on 11.00.
Defect Description:
PHNE_25069:
Repackaged HP-UX patch PHNE_22814 for VVOS.
Based on HP-UX patch PHNE_22814:
1. JAGad04670
The driver makes a call to lanc subsystem without
releasing the driver's lock while sending MIB event up.
That subsystem in turn will send a request to the driver.
The driver will then try to acquire the driver's lock
again, resulting in "already owned spinlock" panic.
Resolution:
The driver releases the spinlock before making call to
lanc subsystem while sending MIB event up.
2. JAGab64411
ER: User should be allowed to configure MTU value for
EISA 100VG card.
Resolution:
Functionality has been added to allow setting of the
MTU value through lanadmin.
3. JAGab64916
When the card is reset during heavy traffic, the Receive
and Transmit buffers are freed before disabling the
RX/TX engine of the card. Hence the card continues DMA
to the freed buffer, resulting in corruption of the
256 byte kmem bucket.
Resolution:
The receive and transmit buffers are freed after
disabling the RX/TX engine of the card.
4. JAGab70602
The start-up script fails when non-sequential array
indices for interfaces are present in the
configuration file.
Resolution:
The start-up script has been modified to cope with
non-sequential array index values.
PHNE_18453:
Repackaged HP-UX patch PHNE_15477 for VVOS.
Based on HP-UX patch PHNE_15477:
1. 100vg driver is logging message recv_pkts<0 and
send_pkts<0 in vgal0_isr().
2. 100vg panic on cable disconnect. Driver was
trying to lock when it was already locked.
3. lanadmin Operating Status on 100vg eisa
shows DOWN and will not reset. Driver didn't have code
to bring interface UP/DOWN.
4. Catopen() is called repeatedly in dsname() without
closing it, before returning from this function.
This causes the number of open file descriptors to
exceed the maxfile limit, and after this lanadmin
fails.
5. Reset path, which was called after setting up the
new MAC address, used to overwrite with factory address.
SR:
8606135536 1653296038 5003436899 8606103634 1653252593
5003413971
Patch Files:
100VG-EISA-KRN.100VG-KRN,fr=B.11.04.00,fa=HP-UX_B.11.04_32,
v=HP:
/usr/conf/master.d/vglan0
/usr/conf/lib/vgal0_q4.o
/usr/conf/lib/lib100vg.a
100VG-EISA-RUN.100VG-RUN,fr=B.11.04.00,fa=HP-UX_B.11.04_32,
v=HP:
/usr/lib/lanadmin/libdsvglan0.sl
100VG-EISA-RUN.100VG-INIT,fr=B.11.04.00,fa=HP-UX_B.11.04_32,
v=HP:
/sbin/init.d/hpvgal
what(1) Output:
100VG-EISA-KRN.100VG-KRN,fr=B.11.04.00,fa=HP-UX_B.11.04_32,
v=HP:
/usr/conf/master.d/vglan0:
None
/usr/conf/lib/vgal0_q4.o:
None
/usr/conf/lib/lib100vg.a:
vgal0.h $Revision: 1.3 $ $Date: 99/01/04 01:25:44 $
vgal0.c $Revision: 1.16 $ $Date: 2000/06/07 22:16:25
$
FILESET 100VG: lib 100vg: Version: B.11.00.02 PHNE_2
2814
100VG-EISA-RUN.100VG-RUN,fr=B.11.04.00,fa=HP-UX_B.11.04_32,
v=HP:
/usr/lib/lanadmin/libdsvglan0.sl:
FILE: dsvglan0.c Version: B.11.00.02 DART47
100VG-EISA-RUN.100VG-INIT,fr=B.11.04.00,fa=HP-UX_B.11.04_32,
v=HP:
/sbin/init.d/hpvgal:
hpvgal $Revision: 1.3 $ $Date: 2000/06/08 01:59:47 $
cksum(1) Output:
100VG-EISA-KRN.100VG-KRN,fr=B.11.04.00,fa=HP-UX_B.11.04_32,
v=HP:
2639339491 3749 /usr/conf/master.d/vglan0
2817467466 151408 /usr/conf/lib/vgal0_q4.o
3975057099 40528 /usr/conf/lib/lib100vg.a
100VG-EISA-RUN.100VG-RUN,fr=B.11.04.00,fa=HP-UX_B.11.04_32,
v=HP:
3767755544 16384 /usr/lib/lanadmin/libdsvglan0.sl
100VG-EISA-RUN.100VG-INIT,fr=B.11.04.00,fa=HP-UX_B.11.04_32,
v=HP:
1620814658 5370 /sbin/init.d/hpvgal
Patch Conflicts: None
Patch Dependencies: None
Hardware Dependencies: None
Other Dependencies: None
Supersedes:
PHNE_18453
Equivalent Patches:
PHNE_22814:
s700: 11.00
s800: 11.00
Patch Package Size: 250 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_25069
5. Run swinstall to install the patch:
swinstall -x autoreboot=true -x patch_match_target=true \
-s /tmp/PHNE_25069.depot
By default swinstall will archive the original software in
/var/adm/sw/save/PHNE_25069. If you do not wish to retain a
copy of the original software, use the patch_save_files option:
swinstall -x autoreboot=true -x patch_match_target=true \
-x patch_save_files=false -s /tmp/PHNE_25069.depot
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_25069.text file is
available in the product readme:
swlist -l product -a readme -d /tmp/PHNE_25069.depot
To put this patch on a magnetic tape and install from the
tape drive, use the command:
dd if=/tmp/PHNE_25069.depot of=/dev/rmt/0m bs=2k
Special Installation Instructions: None
-----End of Document ID: PHNE_25069------------------------------------------
Document ID: PHKL_25453
Date Loaded: 20011025
Title: s700_800 11.11 early boot, Psets, vPar, Xserver core dumps
Patch Name: PHKL_25453
Patch Description: s700_800 11.11 early boot, Psets, vPar, Xserver core dumps
Creation Date: 01/10/24
Post Date: 01/10/25
Hardware Platforms - OS Releases:
s700: 11.11
s800: 11.11
Products: N/A
Filesets:
OS-Core.CORE2-KRN,fr=B.11.11,fa=HP-UX_B.11.11_32,v=HP
OS-Core.CORE2-KRN,fr=B.11.11,fa=HP-UX_B.11.11_64,v=HP
Automatic Reboot?: Yes
Status: General Release
Critical:
Yes
PHKL_25453: OTHER
Xservers may core dump.
PHKL_23609: PANIC
Superdome machines may panic early in boot with
"Data and/or code translations improperly disabled"
message. This patch resolves this panic during
early boot.
Category Tags:
defect_repair hardware_enablement enhancement
general_release critical panic
Path Name: /hp-ux_patches/s700_800/11.X/PHKL_25453
Symptoms:
PHKL_25453:
( SR:8606186988 CR:JAGad56198 )
After CDE comes up when trying to enter username/password
the Xserver core dumps. It also core dumped when using
x11start.
If the customer disables one of the CPUs the Xserver
does not core dump.
PHKL_24550:
( SR:8606200799 CR:JAGad69975 )
This patch is a member of a set of patches needed to enable
the HP-UX Processor Sets product (PROCSETS). When PROCSETS
product is installed, it will install the full set of
required patches for that product, including this patch.
If the HP-UX Processor Sets product is not installed, this
change will have no impact on your system.
( SR:8606199576 CR:JAGad68763 )
This patch is a member of a set of patches needed to enable
the HP-UX Virtual Partitions product Sets. When the HP-UX
Virtual Partitions product (VPARSBASE or T1335AA) is
installed, it will install the full set of required patches
for that product, including this patch.
If the HP-UX Virtual Partitions product is not installed,
this change will have no impact on your system.
PHKL_23609:
( SR:8606169455 CR:JAGad38730 )
Some Superdome machines randomly panic very early in the
boot process.
Defect Description:
PHKL_25453:
( SR:8606186988 CR:JAGad56198 )
The graphics Block TLB entry is not set up on non-monarch
processors. When the X Server migrates off the monarch
processor, there is no valid TLB entry on the processor it
moves to. When the X Server tries to access an address that
should be covered by the Block TLB entry it gets a data page
fault and dumps core.
Resolution:
Moved the Graphics Block TLB initialization of non-monarch
processors from phase 1 to phase 2 of MP configuration so
that the entries get populated correctly on non-monarch
processors.
PHKL_24550:
( SR:8606200799 CR:JAGad69975 )
This patch contains minor enhancements required to support
the HP-UX Processor Sets product.
Resolution:
Enhancements added to provide initialization of Processor
Sets product in early system boot path.
( SR:8606199576 CR:JAGad68763 )
This patch contains minor enhancements required to support
the HP-UX Virtual Partitions product.
Resolution:
Enhancements added to support CPU migration.
PHKL_23609:
( SR:8606169455 CR:JAGad38730 )
Data and/or code translations are improperly disabled.
Resolution:
Set the OS tick interval to a longest possible value during
initializing non_monarch CPU's interval timer.
SR:
8606169455 8606186988 8606199576 8606200799
Patch Files:
OS-Core.CORE2-KRN,fr=B.11.11,fa=HP-UX_B.11.11_32,v=HP:
/usr/conf/lib/libinit-pdk.a(boot_machdep.o)
/usr/conf/lib/libsvc-pdk.a(trap.o)
OS-Core.CORE2-KRN,fr=B.11.11,fa=HP-UX_B.11.11_64,v=HP:
/usr/conf/lib/libinit-pdk.a(boot_machdep.o)
/usr/conf/lib/libsvc-pdk.a(trap.o)
what(1) Output:
OS-Core.CORE2-KRN,fr=B.11.11,fa=HP-UX_B.11.11_32,v=HP:
/usr/conf/lib/libinit-pdk.a(boot_machdep.o):
boot_machdep.c $Date: 2001/10/05 02:18:39 $Revision:
r11.11/5 PATCH_11.11 (PHKL_25453)
/usr/conf/lib/libsvc-pdk.a(trap.o):
trap.c $Date: 2001/03/27 15:46:15 $Revision: r11.11/
2 PATCH_11.11 (PHKL_23609)
OS-Core.CORE2-KRN,fr=B.11.11,fa=HP-UX_B.11.11_64,v=HP:
/usr/conf/lib/libinit-pdk.a(boot_machdep.o):
None
/usr/conf/lib/libsvc-pdk.a(trap.o):
trap.c $Date: 2001/03/27 15:46:15 $Revision: r11.11/
2 PATCH_11.11 (PHKL_23609)
cksum(1) Output:
OS-Core.CORE2-KRN,fr=B.11.11,fa=HP-UX_B.11.11_32,v=HP:
398744407 80772 /usr/conf/lib/libinit-pdk.a(boot_machdep.o)
2279688430 31440 /usr/conf/lib/libsvc-pdk.a(trap.o)
OS-Core.CORE2-KRN,fr=B.11.11,fa=HP-UX_B.11.11_64,v=HP:
1985457881 177744 /usr/conf/lib/
libinit-pdk.a(boot_machdep.o)
735326878 59984 /usr/conf/lib/libsvc-pdk.a(trap.o)
Patch Conflicts: None
Patch Dependencies: None
Hardware Dependencies: None
Other Dependencies: None
Supersedes:
PHKL_24550 PHKL_23609
Equivalent Patches: None
Patch Package Size: 370 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_25453
5. Run swinstall to install the patch:
swinstall -x autoreboot=true -x patch_match_target=true \
-s /tmp/PHKL_25453.depot
By default swinstall will archive the original software in
/var/adm/sw/save/PHKL_25453. 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_25453.text file is
available in the product readme:
swlist -l product -a readme -d /tmp/PHKL_25453.depot
To put this patch on a magnetic tape and install from the
tape drive, use the command:
dd if=/tmp/PHKL_25453.depot of=/dev/rmt/0m bs=2k
Special Installation Instructions: None
-----End of Document ID: PHKL_25453------------------------------------------
Document ID: PHKL_25154
Date Loaded: 20011026
Title: s700_800 11.04 (VVOS) PCI cumulative patch
Patch Name: PHKL_25154
Patch Description: s700_800 11.04 (VVOS) PCI cumulative patch
Creation Date: 01/09/10
Post Date: 01/10/26
Hardware Platforms - OS Releases:
s700: 11.04
s800: 11.04
Products: N/A
Filesets:
OS-Core.CORE-KRN,fr=B.11.04,fa=HP-UX_B.11.04_32/64,v=HP
ProgSupport.C-INC,fr=B.11.04,fa=HP-UX_B.11.04_32/64,v=HP
OS-Core.CORE2-KRN,fr=B.11.04,fa=HP-UX_B.11.04_32,v=HP
OS-Core.CORE2-KRN,fr=B.11.04,fa=HP-UX_B.11.04_64,v=HP
Automatic Reboot?: Yes
Status: General Release
Critical:
Yes
PHKL_25154: PANIC
Based on HP-UX Patch PHKL_24074: PANIC
PHKL_22711: OTHER PANIC CORRUPTION
Based on HP-UX Patch PHKL_22494: OTHER
EPIC Error Handler reports wrong device and driver
Based on HP-UX Patch PHKL_22394: CORRUPTION PANIC
Based on HP-UX Patch PHKL_22230: PANIC
Based on HP-UX Patch PHKL_21886: OTHER
Without this patch the Hyperfabric driver will not
perform optimally or may not even perform at all
PHKL_21746: PANIC CORRUPTION
Based on HP-UX Patch PHKL_20994: PANIC
Based on HP-UX Patch PHKL_20835: PANIC
for JAGab78968, devices will not be recognized
and will not function. For JAGab78970,
panic will occur on multi-some devices with
a bridge on board.
Based on HP-UX Patch PHKL_20123: PANIC
Currently unsupported configurations, such as
mulitple PCI-to-PCI bridges on a single PCI bus
will cause the system to panic.
Based on HP-UX Patch PHKL_20089: CORRUPTION
Based on HP-UX Patch PHKL_19544: PANIC
For the initial N-class release, I/O Port Space
support did not make the ship requirements and
thus was not supported. However, rather than
simply not claiming cards with I/O Port Space,
they will be claimed by their drivers but they
may data page fault when their drivers attempt
to access their cards due to a bad IOPS handle.
Category Tags:
defect_repair hardware_enablement enhancement
general_release critical panic corruption
Path Name: /hp-ux_patches/s700_800/11.X/PHKL_25154
Symptoms:
PHKL_25154:
Ported HP-UX patch PHKL_24074 to VVOS
Based on HP-UX patch PHKL_24074:
(SR: 8606185627 CR: JAGad54829)
On a small percentage of A-class and L-class servers, HP-UX
will fail to boot correctly from a bootp server across the
network. Systems that fail have demonstrated one of two
symptoms. The first symptom is that the failure generates a
"6292" alert (High Priority Machine Check or HPMC)
immediately after the "alloc_pdc_pages" message during a
LAN boot. The second symptom is that the system may boot,
but some or all I/O devices will not work correctly. This
could include problems such as disks not appearing. This
problem has not been seen during HP-UX boots from local
hard disks.
PHKL_22711:
Ported HP-UX patch PHKL_22494 to VVOS
Based on HP-UX patch PHKL_22494:
( SR: 8606159641 DTS: JAGad28967 )
EPIC Error Handler reports wrong device path and driver that
caused the error. Instead of the erroring device, the
message displays an I/O path which fell victim to an error
condition that was caused by another driver. For instance,
in this example the error was caused by Fibre Channel driver
but SCSI C720 driver was mistaken as the one that caused the
error:
panic: Channel error in Driver c720,
discovered by Epic 7, Device 0
Error Config: 002bffeb:2bffebebaaabf1
Error Cause: 70000100:7000010000000000
Error Info: 80172000:8017200000000012
Based on HP-UX patch PHKL_22394:
( SR: 8606157925 DTS: JAGad27255 )
Under some circumstances the A4924A HSC Gigabit card
will not be configured at boot.
( SR: 8606152483 DTS: JAGad21813 )
Depending on the system and I/O configuration, data
corruption and resulting system failures can occur. This
defect could impact any system that boots from SCSI boot
devices.
To date, no customer configurations have experienced this
problem.
Based on HP-UX patch PHKL_22230:
( SR: 8606133584 DTS: JAGad02728 )
V-class systems panic with 'read channel context error'
messages which might be preceded or followed by 'target
abort' error messages from the Fibre Channel driver.
This problem might require heavy IO activity like disk
copying, system backup or database processing to occur.
Stack trace should look similar to this:
LEVEL FUNC
0) panic+0x14
1) fcT1_isr+0xc8
2) epic_isr+0x58
3) mp_ext_interrupt+0x34c
4) ivti_patch_to_nop3+0x0
5) idle+0x4c0
6) swidle_exit+0x0
Based on HP-UX patch PHKL_21886:
( SR: 8606102908 DTS: JAGab68966 )
HyperFabric Device unable to function optimally
PHKL_21746:
Ported HP-UX patch PHKL_21270 to VVOS
Based on HP-UX patch PHKL_21270:
( SR: 8606128261 DTS: JAGac79061 )
L-class servers are unable to support fxe graphics cards.
Based on HP-UX patch PHKL_20994:
( SR: 8606126189 DTS: JAGac56754 )
V-class panics with Channel Context Errors.
Based on HP-UX patch PHKL_20835:
( SR: 8606108530 DTS: JAGab78968 )
Some PCI multi-device cards with a bridge are ignored and
cannot function.
( SR: 8606108532 DTS: JAGab78970 )
Panic during boot with a DEBUG kernel and the stack should
look like this:
panic: assertion failed (bar->range >= free->range) at line
...
PC-Offset Stack Trace (read down, top of stack is 1st):
0x001c7504 (panic+0x54)
0x001c7f64 (assfail+0x3c)
0x000ab00c (pci_mark_free_list+0x144)
0x000ac7fc (pci_alloc_range+0x134)
0x000aca08 (pci_process_want+0x88)
0x000acac8 (pci_cdio_get_scan_state+0x28)
0x000ad3e4 (pci_cdio_scan+0x9c)
0x003c725c (gio_scan_subtree+0xdc)
0x003c7294 (gio_scan_subtree+0x114)
0x003c7294 (gio_scan_subtree+0x114)
0x003c7294 (gio_scan_subtree+0x114)
0x003c711c (io_scan+0xbc)
0x003ca8cc (io_virt_mode_config+0xa4)
0x0027ea78 (main+0x130)
0x003785a4 ($vstart+0x48)
0x0003a6cc (RDB_patch_int_trap+0xe0)
End Of Stack
Based on HP-UX patch PHKL_20123:
( SR: 8606100466 DTS: JAGab31892 )
Devices below a PCI-to-PCI bridge requesting a memory mapped
IO range with a 64 bit address, such as A5838A, are unable
to map system resources.
( SR: 8606107082 DTS: JAGab20840 )
In a configuration with multiple PCI-to-PCI bridges on a
single PCI bus, only the first PCI-to-PCI bridge is found.
Based on HP-UX patch PHKL_20089:
( SR: 8606103658 DTS: JAGab70668 )
Incorrect data in host memory buffers when using the
BN_DMA_ALIGN_BUF hint on a V-class machine.
Based on HP-UX patch PHKL_19063:
( SR: 8606101323 DTS: JAGab14263 )
Added support for the PCI-to-PCI bridge on the A5566A FCMS
Fibre Channel card.
Based on HP-UX patch PHKL_20164:
( SR: 8606107507 DTS: JAGab77743 )
B1000, C3000, J5000, and J7000 workstations do not run on
HPUX 11.00.
Based on HP-UX patch PHKL_19544:
( SR: 8606103312 DTS: JAGab16774 )
Any PCI cards needing I/O Port Space on N-class platforms
may cause a data page fault when accessed.
Defect Description:
PHKL_25154:
Ported HP-UX patch PHKL_24074 to VVOS
Based on HP-UX patch PHKL_24074:
(SR: 8606185627 CR: JAGad54829)
The defect addressed by this patch is caused by a corner
case while initializing some A-class and L-class PCI I/O
cards. If an I/O memory range assigned to a PCI card is
near the list of available I/O ranges maintained by
HP-UX, multiple PCI cards can incorrectly be assigned the
same I/O range. This problem has only been seen while
booting HP-UX across a network on a minimal number of
systems, because the conditions required for triggering
it depend on a timing interaction between system firmware
and HP-UX that seldom occurs.
Resolution:
The resolution for this defect involved fixing a compar-
ison to correctly check for the corner case that causes
this problem.
This patch is required in the install kernel that the
failing system is booting from. Patching the failing
system itself will not fix the problem. The repair must
be made to the install kernel on the bootp server. The
patch is included in the install kernel supplied on the
September 2001 Install and Core OS media.
PHKL_22711:
Ported HP-UX patch PHKL_22494 to VVOS
Based on HP-UX patch PHKL_22494:
( SR: 8606159641 DTS: JAGad28967 )
The messages being printed are related to the I/O path
which discovers the error, but the source of the problem
is in the I/O path which sent the target abort signal.
Resolution:
We look for the device that sent the target abort signal
and report this as the device that caused the error.
Based on HP-UX patch PHKL_22394:
( SR: 8606157925 DTS: JAGad27255 )
During inital boot the HSC Gigabit A4924A card was not
configured because there was insufficent time for
initialization to complete before it was polled. If another
ioscan was done by a driver or operator then the card would
be configured.
Resolution:
Delay was added after the PCI bus was reset to allow the
card to correctly initialize.
( SR: 8606152483 DTS: JAGad21813 )
The operating system did not correctly map a firmware
configured external SCSI boot device into memory and two
devices could then be assigned the same memory resulting in
data corruption and associated system failures. This is
only a problem on systems using the Symbios/NCR 53C896 chip.
Resolution:
The operating system checks for the error condition, and if
found, corrects the memory mapping for the boot device. For
systems where this chip is not present, the error condition
will never be detected; this change will have no impact on
these systems.
Based on HP-UX patch PHKL_22230:
( SR: 8606133584 DTS: JAGad02728 )
On V-class, a previously completed DMA was re-used by
the IO subsystem which subsequently led to system panic with
'read channel context error' messages.
Resolution:
Prevent the system from reusing previously completed DMA
which has been unmapped.
Based on HP-UX patch PHKL_21886:
( SR: 8606102908 DTS: JAGab68966 )
This patch provides a feature to allow the CLusterINter-
connect driver to permanently allocate contiguous large
memory, which will enhance its performance greatly.
This feature works on other Legacy machines like K-class
but not on newer N and L servers due to new HP-UX
architecture in the 11.00 release which configures PCI
devices after the System bus adapter is initialized. It
is then too late for the lowfat driver to resize the IO
Page directory using a request passed upward to the system
bus adapter.
Resolution:
During the real mode bus walk, detect the Hyper-Fabric card
and system parameter 'clicreservedmem'. If both exist then
request the system bus adapter to increment the IO Page
directory before it is initialized.
PHKL_21746:
Ported HP-UX patch PHKL_21270 to VVOS
Based on HP-UX patch PHKL_21270:
( SR: 8606128261 DTS: JAGac79061 )
Fxe graphics cards make use of a PCI expansion ROM BARs,
which were not mapped into MMIO. This caused graphics
cards on PAT based servers to remain unclaimed.
Resolution:
Modified PCI services to scan for PCI expansion ROM BAR and
map it into LMMIO.
Based on HP-UX patch PHKL_20994:
( SR: 8606126189 DTS: JAGac56754 )
In a V-class machine, each memory-request by an IO card on
the PCI bus is translated into a host-memory address by the
central IO chip. Each translation available in the central
IO chip is called a channel.
One reason that a Channel Context Error occurs is that an
IO card on the PCI bus requests a memory address which the
central IO chip is not programmed to handle. Programming
the chip for each translation is called a channel build.
Building a channel in the central IO chip of the V-class
is done by writes into the IO address space. These writes
can be delayed through the hardware before reaching the
central IO chip, thereby delaying the channel-build process.
Because the V-class is a multi-processor system,
another processor could direct a PCI card to use that
channel before the build completes -- resulting in a
Channel Context Error.
In the dump, all channels in the IO chip will look OK
(all translations will be valid) because the channel-build
process completes long before the dump is taken.
Resolution:
Read-back the channel-build register to force the completion
of the channel-build operation before releasing the
spinlock which protects the use of the channel.
Based on HP-UX patch PHKL_20835:
( SR: 8606108530 DTS: JAGab78968 )
PCI devices malfunction due to PCI-to-PCI Bus mastership,
I/O and Memory Mapped IO not enabled. This happens when
device BARs are hidden below the PCI-to-PCI bridge.
Resolution:
Enable bridge Bus Master, IO and Memory Mapped IO as
default.
( SR: 8606108532 DTS: JAGab78970 )
Panic during card initialization caused by BAR address out
of bound. Root cause is due to holes generated by PCI
address alignment.
Resolution:
Change BAR allocation, sort them from large to small, this
will eliminate holes that pushes BAR out of bound.
Based on HP-UX patch PHKL_20123:
( SR: 8606100466 DTS: JAGab31892 )
64 bit memory mapped IO space below a PCI-to-PCI bridge was
not supported.
Resolution:
Added support to map 64 bit MMIO requests into 32 bit MMIO.
( SR: 8606107082 DTS: JAGab20840 )
Error in PCI-to-PCI bridge code prevented more than the
first PCI-to-PCI bridge on a single PCI bus from being
claimed.
Resolution:
Fixed PCI-to-PCI code to properly step through each
PCI-to-PCI bridge on a PCI bus.
Based on HP-UX patch PHKL_20089:
( SR: 8606103658 DTS: JAGab70668 )
V-class PCI bus adaptor CDIO incorrectly implemented the
BN_DMA_ALIGN_BUF hint, resulting in overlapped PCI bus
mappings.
Resolution:
Modify the V-class PCI bus adaptor bus map routine to
correctly handle BN_DMA_ALIGN BUF hint
Based on HP-UX patch PHKL_19063:
( SR: 8606101323 DTS: JAGab14263 )
The A5566A FCMS card contains a PCI-to-PCI bridge. V-Class
machines do not currently support PCI-to-PCI bridges.
Resolution:
Added functionality to initialize the PCI-to-PCI bridge chip
on the A5566A FCMS card so the Fibre Channel driver can
access the Fibre Channel portion of the card.
Based on HP-UX patch PHKL_20164:
( SR: 8606107507 DTS: JAGab77743 )
Local bus adapter code in HPUX 11.00 does not support
B1000, C3000, J5000, and J7000 workstations.
Resolution:
Added LBA support for new workstations.
Based on HP-UX patch PHKL_19544:
( SR: 8606103312 DTS: JAGab16774 )
N-class did not support PCI cards needing I/O Port Space at
first release. Attempting to use an I/O Port Space card
could lead to a data page fault because the PCI bridge
manager and kernel platform services mapping routines for
I/O Port Space were not functional.
Resolution:
This patch addresses the I/O Port Space mapping defect.
Multiple fixes were made regarding I/O Port Space. This
patch depends on PHKL_19543 which ENABLES the recognition
of Postable I/O Port Space ranges.
SR:
8606100466 8606101323 8606102908 8606103312 8606103658
8606107507 8606108530 8606108532 8606126189 8606128261
8606133584 8606152483 8606157925 8606159641 8606185627
Patch Files:
OS-Core.CORE-KRN,fr=B.11.04,fa=HP-UX_B.11.04_32/64,v=HP:
/usr/conf/wsio/pci.h
ProgSupport.C-INC,fr=B.11.04,fa=HP-UX_B.11.04_32/64,v=HP:
/usr/include/sys/pci.h
OS-Core.CORE2-KRN,fr=B.11.04,fa=HP-UX_B.11.04_32,v=HP:
/usr/conf/lib/libpci.a(p2pb_cdio.o)
/usr/conf/lib/libpci.a(pci_cdio.o)
OS-Core.CORE2-KRN,fr=B.11.04,fa=HP-UX_B.11.04_64,v=HP:
/usr/conf/lib/libpci.a(elroy_cdio.o)
/usr/conf/lib/libpci.a(epic_cdio.o)
/usr/conf/lib/libpci.a(epic_chnl.o)
/usr/conf/lib/libpci.a(epic_errors.o)
/usr/conf/lib/libpci.a(p2pb_cdio.o)
/usr/conf/lib/libpci.a(pci_cdio.o)
what(1) Output:
OS-Core.CORE-KRN,fr=B.11.04,fa=HP-UX_B.11.04_32/64,v=HP:
/usr/conf/wsio/pci.h:
pci.h $Date: 2000/03/09 15:31:26 $Revision: r11ros/3
PATCH_11.00 (PHKL_21270)
ProgSupport.C-INC,fr=B.11.04,fa=HP-UX_B.11.04_32/64,v=HP:
/usr/include/sys/pci.h:
pci.h $Date: 2000/03/09 15:31:26 $Revision: r11ros/3
PATCH_11.00 (PHKL_21270)
OS-Core.CORE2-KRN,fr=B.11.04,fa=HP-UX_B.11.04_32,v=HP:
/usr/conf/lib/libpci.a(p2pb_cdio.o):
p2pb_cdio.c $Date: 2000/01/28 19:57:40 $Revision: r1
1ros/5 PATCH_11.00 (PHKL_20835)
/usr/conf/lib/libpci.a(pci_cdio.o):
pci_cdio.c $Date: 2001/06/08 11:04:38 $Revision: r11
ros/15 PATCH_11.00 (PHKL_24074)
OS-Core.CORE2-KRN,fr=B.11.04,fa=HP-UX_B.11.04_64,v=HP:
/usr/conf/lib/libpci.a(elroy_cdio.o):
elroy_cdio.c $Date: 2000/06/19 07:58:43 $Revision: r
11ros/5 PATCH_11.00 (PHKL_21886)
/usr/conf/lib/libpci.a(epic_cdio.o):
epic_cdio.c $Date: 2000/08/22 14:12:33 $Revision: r1
1ros/16 PATCH_11.00 (PHKL_22230)
/usr/conf/lib/libpci.a(epic_chnl.o):
epic_chnl.c $Date: 2000/08/22 14:12:33 $Revision: r1
1ros/7 PATCH_11.00 (PHKL_22230)
/usr/conf/lib/libpci.a(epic_errors.o):
epic_errors.c $Date: 2000/10/04 14:38:32 $Revision:
r11ros/8 PATCH_11.00 (PHKL_22494)
/usr/conf/lib/libpci.a(p2pb_cdio.o):
p2pb_cdio.c $Date: 2000/01/28 19:57:40 $Revision: r1
1ros/5 PATCH_11.00 (PHKL_20835)
/usr/conf/lib/libpci.a(pci_cdio.o):
pci_cdio.c $Date: 2001/06/08 11:04:38 $Revision: r11
ros/15 PATCH_11.00 (PHKL_24074)
cksum(1) Output:
OS-Core.CORE-KRN,fr=B.11.04,fa=HP-UX_B.11.04_32/64,v=HP:
3184135743 28335 /usr/conf/wsio/pci.h
ProgSupport.C-INC,fr=B.11.04,fa=HP-UX_B.11.04_32/64,v=HP:
3184135743 28335 /usr/include/sys/pci.h
OS-Core.CORE2-KRN,fr=B.11.04,fa=HP-UX_B.11.04_32,v=HP:
2066325377 4756 /usr/conf/lib/libpci.a(p2pb_cdio.o)
3566387097 19340 /usr/conf/lib/libpci.a(pci_cdio.o)
OS-Core.CORE2-KRN,fr=B.11.04,fa=HP-UX_B.11.04_64,v=HP:
1836187838 56864 /usr/conf/lib/libpci.a(elroy_cdio.o)
1570355386 62112 /usr/conf/lib/libpci.a(epic_cdio.o)
2038972919 9240 /usr/conf/lib/libpci.a(epic_chnl.o)
2216049711 23208 /usr/conf/lib/libpci.a(epic_errors.o)
2495747100 10176 /usr/conf/lib/libpci.a(p2pb_cdio.o)
2374514688 43904 /usr/conf/lib/libpci.a(pci_cdio.o)
Patch Conflicts: None
Patch Dependencies:
s700: 11.04: PHKL_19142 PHKL_25039
s800: 11.04: PHKL_19142 PHKL_25039
Hardware Dependencies: None
Other Dependencies: None
Supersedes:
PHKL_22711 PHKL_21746
Equivalent Patches:
PHKL_24074:
s700: 11.00
s800: 11.00
PHKL_24022:
s700: 11.11
s800: 11.11
Patch Package Size: 340 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_25154
5. Run swinstall to install the patch:
swinstall -x autoreboot=true -x patch_match_target=true \
-s /tmp/PHKL_25154.depot
By default swinstall will archive the original software in
/var/adm/sw/save/PHKL_25154. If you do not wish to retain a
copy of the original software, use the patch_save_files option:
swinstall -x autoreboot=true -x patch_match_target=true \
-x patch_save_files=false -s /tmp/PHKL_25154.depot
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_25154.text file is
available in the product readme:
swlist -l product -a readme -d /tmp/PHKL_25154.depot
To put this patch on a magnetic tape and install from the
tape drive, use the command:
dd if=/tmp/PHKL_25154.depot of=/dev/rmt/0m bs=2k
Special Installation Instructions:
The A5566A Fibre Channel Mass Storage (FCMS) card must be in
a PCI slot number greater than all non-A5566A FCMS cards on
the same bus. Multiple A5566A FCMS cards on a PCI bus can
be used.
This patch depends on base patch PHKL_19142
For successful installation please insure that PHKL_19142
is already installed, or that PHKL_19142 is included
in the same depot with this patch and PHKL_19142
is selected for installation.
-----End of Document ID: PHKL_25154------------------------------------------
Document ID: PHKL_25055
Date Loaded: 20011026
Title: s700_800 11.04 (VVOS) Cumulative gang scheduling patch
Patch Name: PHKL_25055
Patch Description: s700_800 11.04 (VVOS) Cumulative gang scheduling patch
Creation Date: 01/10/11
Post Date: 01/10/26
Hardware Platforms - OS Releases:
s700: 11.04
s800: 11.04
Products: N/A
Filesets:
OS-Core.CORE2-KRN,fr=B.11.04,fa=HP-UX_B.11.04_32,v=HP
OS-Core.CORE2-KRN,fr=B.11.04,fa=HP-UX_B.11.04_64,v=HP
Automatic Reboot?: Yes
Status: General Release
Critical:
No (superseded patches were critical)
PHKL_21685: HANG
Based on HP-UX patch PHKL_21549: HANG
PHKL_23007: HANG
Based on HP-UX patch PHKL_21549: HANG
Category Tags:
defect_repair general_release critical halts_system
Path Name: /hp-ux_patches/s700_800/11.X/PHKL_25055
Symptoms:
PHKL_25055:
Redundancy of patch filesets PHKL_21685 and
PHKL_23007. Both deliver same file without
PHKL_23007 superseding PHKL_21685.
PHKL_23007:
Ported HP-UX patch PHKL_21549 to VVOS.
Based on PHKL_21549:
( SR: 8606129909 DTS: JAGac88824 )
Gang scheduled applications appear to hang or
make minimal forward progress.
Based on PHKL_19315:
( SR: 1653280479 DTS: JAGaa42348 )
CPU usage of a mult-threaded job with gang-scheduling
on is reduced drasticly while a single-threaded job
with higher priority is running.
PHKL_21685:
Ported HP-UX patch PHKL_21549 for VVOS.
Based on HP-UX patch PHKL_21549:
( SR: 8606129909 DTS: JAGac88824 )
Gang scheduled applications appear to hang or
make minimal forward progress.
Based on HP-UX patch PHKL_19315:
( SR: 1653280479 DTS: JAGaa42348 )
CPU usage of a mult-threaded job with gang-scheduling
on is reduced drasticly while a single-threaded job
with higher priority is running.
Defect Description:
PHKL_25055:
Fixes a problem where PHKL_23007 delivered a patch
fileset containing the same file delivered in
PHKL_21685 without PHKL_23007 superseding
PHKL_21685.
PHKL_23007:
Ported HP-UX patch PHKL_21549 to VVOS.
Based on PHKL_21549:
( SR: 8606129909 DTS: JAGac88824 )
The gang scheduler did not recognize a new cpu state
that was added to the system initialization process.
This resulted in all gang scheduled processes being
bound to the monarch processor.
Resolution:
At system initialization the gang scheduler now
takes into account the new cpu state and uses all
available processors instead of just the monarch.
Based on PHKL_19315:
( SR: 1653280479 DTS: JAGaa42348 )
The GANG scheduling of multithreaded applications allows
users to improve significantly the performance of their jobs
that run on a subset of processors.
In an enviroment that uses different priorities for the
jobs, over-subscription becomes a problem: A singlethreaded
job of high priority is able to reduce the CPU usage of all
running multithreaded jobs. The expectation is that the
singlethreaded job reduces in average the CPU usage of one
gang independently from the priority of the singlethreaded
job.
Resolution:
This patch to the gang scheduler removes a previous change
that corrects the fairness algorithm of the gang scheduler
load balancer. The code is reverted back to its original
algorithm for when to initiate the gang scheduler load
balancer. Balancing is not performed is we are under or
completely subscribed. Only when the active gangs
oversubscribe the available processors will the load
balancer be initiated.
PHKL_21685:
Ported HP-UX patch PHKL_21549 for VVOS.
Based on HP-UX patch PHKL_21549:
( SR: 8606129909 DTS: JAGac88824 )
The gang scheduler did not recognize a new cpu state
that was added to the system initialization process.
This resulted in all gang scheduled processes being
bound to the monarch processor.
Resolution:
At system initialization the gang scheduler now
takes into account the new cpu state and uses all
available processors instead of just the monarch.
Based on HP-UX patch PHKL_19315:
( SR: 1653280479 DTS: JAGaa42348 )
The GANG scheduling of multithreaded applications allows
users to improve significantly the performance of their jobs
that run on a subset of processors.
In an enviroment that uses different priorities for the
jobs, over-subscription becomes a problem: A singlethreaded
job of high priority is able to reduce the CPU usage of all
running multithreaded jobs. The expectation is that the
singlethreaded job reduces in average the CPU usage of one
gang independently from the priority of the singlethreaded
job.
Resolution:
This patch to the gang scheduler removes a previous change
that corrects the fairness algorithm of the gang scheduler
load balancer. The code is reverted back to its original
algorithm for when to initiate the gang scheduler load
balancer. Balancing is not performed is we are under or
completely subscribed. Only when the active gangs
oversubscribe the available processors will the load
balancer be initiated.
SR:
1653280479 8606129909
Patch Files:
OS-Core.CORE2-KRN,fr=B.11.04,fa=HP-UX_B.11.04_32,v=HP:
/usr/conf/lib/libhp-ux.a(pm_gang.o)
OS-Core.CORE2-KRN,fr=B.11.04,fa=HP-UX_B.11.04_64,v=HP:
/usr/conf/lib/libhp-ux.a(pm_gang.o)
what(1) Output:
OS-Core.CORE2-KRN,fr=B.11.04,fa=HP-UX_B.11.04_32,v=HP:
/usr/conf/lib/libhp-ux.a(pm_gang.o):
pm_gang.c $Date: 2000/04/14 11:31:10 $Revision: r11r
os/7 PATCH_11.00 (PHKL_21549)
OS-Core.CORE2-KRN,fr=B.11.04,fa=HP-UX_B.11.04_64,v=HP:
/usr/conf/lib/libhp-ux.a(pm_gang.o):
pm_gang.c $Date: 2000/04/14 11:31:10 $Revision: r11r
os/7 PATCH_11.00 (PHKL_21549)
cksum(1) Output:
OS-Core.CORE2-KRN,fr=B.11.04,fa=HP-UX_B.11.04_32,v=HP:
3922495959 17276 /usr/conf/lib/libhp-ux.a(pm_gang.o)
OS-Core.CORE2-KRN,fr=B.11.04,fa=HP-UX_B.11.04_64,v=HP:
1077527354 43096 /usr/conf/lib/libhp-ux.a(pm_gang.o)
Patch Conflicts: None
Patch Dependencies:
s700: 11.04: PHKL_19142
s800: 11.04: PHKL_19142
Hardware Dependencies: None
Other Dependencies: None
Supersedes:
PHKL_23007 PHKL_21685
Equivalent Patches:
PHKL_21549:
s700: 11.00
s800: 11.00
Patch Package Size: 100 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_25055
5. Run swinstall to install the patch:
swinstall -x autoreboot=true -x patch_match_target=true \
-s /tmp/PHKL_25055.depot
By default swinstall will archive the original software in
/var/adm/sw/save/PHKL_25055. If you do not wish to retain a
copy of the original software, use the patch_save_files option:
swinstall -x autoreboot=true -x patch_match_target=true \
-x patch_save_files=false -s /tmp/PHKL_25055.depot
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_25055.text file is
available in the product readme:
swlist -l product -a readme -d /tmp/PHKL_25055.depot
To put this patch on a magnetic tape and install from the
tape drive, use the command:
dd if=/tmp/PHKL_25055.depot of=/dev/rmt/0m bs=2k
Special Installation Instructions:
This patch depends on base patch PHKL_19142.
For successful installation please insure that PHKL_19142
is already installed, or that PHKL_19142 is included
in the same depot with this patch and PHKL_19142
is selected for installation.
-----End of Document ID: PHKL_25055------------------------------------------
Document ID: PHKL_25054
Date Loaded: 20011026
Title: s700_800 11.04 (VVOS) VxFS 3.1 cumulative patch
Patch Name: PHKL_25054
Patch Description: s700_800 11.04 (VVOS) VxFS 3.1 cumulative patch
Creation Date: 01/10/07
Post Date: 01/10/26
Hardware Platforms - OS Releases:
s700: 11.04
s800: 11.04
Products: N/A
Filesets:
JournalFS.VXFS-PRG,fr=B.11.04,fa=HP-UX_B.11.04_32/64,v=HP
JournalFS.VXFS-BASE-KRN,fr=B.11.04,fa=HP-UX_B.11.04_32,v=HP
JournalFS.VXFS-BASE-KRN,fr=B.11.04,fa=HP-UX_B.11.04_64,v=HP
Automatic Reboot?: Yes
Status: General Release
Critical:
Yes
PHKL_25054: PANIC CORRUPTION
Based on HP-UX Patch PHKL_24027: PANIC CORRUPTION
Based on HP-UX Patch PHKL_24012: PANIC
PHKL_22561: PANIC CORRUPTION HANG
Based on HP-UX Patch PHKL_22432: PANIC CORRUPTION
Based on HP-UX Patch PHKL_21392: PANIC CORRUPTION
PHKL_20911: PANIC HANG
Based on HP-UX Patch PHKL_20674: PANIC
Based on HP-UX Patch PHKL_19800: HANG
PHKL_19441: HANG
Based on HP-UX Patch PHKL_19169: HANG
Category Tags:
defect_repair enhancement general_release critical panic
halts_system corruption
Path Name: /hp-ux_patches/s700_800/11.X/PHKL_25054
Symptoms:
PHKL_25054:
Ported HP-UX patch PHKL_24027 to VVOS
Based on HP-UX patch PHKL_24027:
( SR: 8606113817 CR: JAGac12337 )
ftruncate(2)/truncate(2) on memory mapped VxFS files may
invalidate the partial page containing eof, which
may contain some valid data causing data corruption.
( SR: 8606144927 CR: JAGad14267 )
When quota is enabled on a VxFS filesystem, chown(1m) may
fail with EINVAL for uids between 2560 and 9983 and for
uids 15104 or higher.
( SR: 8606177859 CR: JAGad47086 )
repquota(1m) command may show incorrect quota usage for
some users on a quota enabled VxFS filesystem.
( SR: 8606183708 CR: JAGad52921 )
Data Page Fault while using Hyperfabric network.
Stack of the panic thread may look like,
panic+0x14
report_trap_or_int_and_panic+0x84
interrupt+0x1d4
$ihndlr_rtn+0x0
sendfile_rele+0x304
freeb_pullupmsg+0x238
freeb+0x7b4
CLIC_SEND+0x1ecc
clicdlpi_wput+0x140
putnext+0xcc
ip_wput_ire+0x454
ip_wput+0x470
putnext+0xcc
tcp_timer+0x334
tcp_wput+0x828
puthere+0x148
mi_timeout_exec+0x294
sw_service+0xb0
mp_ext_interrupt+0x150
ivti_patch_to_nop3+0x0
idle+0x81c
Based on HP-UX patch PHKL_24012:
( SR: 8606180062 DTS: JAGad49284 )
Data Page Fault in vx_rwsleep_unlock()/vx_igunlock()
invoked from vx_iflush() or vx_fsflushi(). This happens
under heavy stress to VxFS filesystems. Stack of the
panic thread may look like:
panic+0x10
report_trap_or_int_and_panic+0xe8
trap+0xa48
thandler+0xb7c
vx_rwsleep_unlock+0xc
vx_igunlock+0x14
vx_iflush+0x1fc
vx_iflush_thread+0x70
vx_startdaemon+0xac
vx_postinit+0x74
vx_sync+0x14
update+0x6c
sync+0x20
PHKL_22561:
Ported HP-UX patch PHKL_22432 to VVOS
Based on HP-UX patch PHKL_22432:
( SR: 8606156750 DTS: JAGad26084 )
Data page fault panic in vx_rwsleep_trylock(). An example
stack trace may include the following:
vx_rwsleep_trylock
vx_irwlock_try
vx_iflush
Since the panic could occur in any VxFS ('vx_') flushing
routines, there could be other possible stack traces that
could be seen as well.
This failure occurs when there are many threads reading and
writing to the VxFS filesystem .
( SR: 8606140628 DTS: JAGad09987 )
Processes accessing files on VxFS file systems may hang, and
only be cleared if the system is rebooted.
Based on HP-UX patch PHKL_21392:
( SR: 8606105425 DTS: JAGab73477 )
Data page fault panic. Due to the nature of the fault, a
panic could occur in any VxFS ('vx_') routine. There is no
specific stack trace for reference. This failure occurs
during heavy VxFS filesystem use.
This problem was introduced by PHKL_17205.
PHKL_21225:
Ported HP-UX patch PHKL_20079 to VVOS
Based on HP-UX patch PHKL_20079:
( SR: 8606104878 DTS: JAGab72639 )
VxFS performance may be poor on large systems, due to lock
contention between processors.
Based on HP-UX patch PHKL_19942:
( SR: 8606104878 DTS: JAGab72639 )
VxFS performance may be poor on large systems, if
directories with many files in them are accessed
concurrently by several processes.
PHKL_19441:
Ported HP-UX patch PHKL_19169 to VVOS
Based on HP-UX patch PHKL_19169:
( SR: 8606101101 DTS: JAGab21116 )
Processes accessing files on VxFS file systems may hang, and
only be cleared if the system is rebooted. This problem was
introduced with patch PHKL_18534.
PHKL_20911:
Ported HP-UX patch PHKL_20674 to VVOS
Based on HP-UX patch PHKL_20674:
(SR: 8606113482 DTS : JAGac00113)
sync command may panic in vx_rwsleep_trylock/vx_fsflushi().
Stack of panic thread is given below.
panic+0x14
report_trap_or_int_and_panic+0x80
trap+0xa8c
nokgdb+0x8
vx_rwsleep_trylock+0x14
vx_irwlock_try+0x18
vx_fsflushi+0x37c
vx_sync+0x100
update+0x48
sync+0x24
syscall+0x480
$syscallrtn+0x0
Based on HP-UX patch PHKL_19800:
1. PHKL_18531 may hang a uniprocessor system while
unmounting a VxFS if an inode is locked by some
other process.
2. VxFS may hang if more than one process writes
to a memory mapped file.
PHKL_19989:
Large number of sequential writes to a regular file
takes longer on VxFS when compared with HFS.
Based on HP-UX patch PHKL_20401:
(SR: 4701415679 DTS: JAGaa93188 )
quotaon does not work. It fails with I/O error.
# quotaon -v /home
quotactl: /dev/vg02/lvol1: I/O error
Defect Description:
PHKL_25054:
Ported HP-UX patch PHKL_24027 to VVOS
Based on HP-UX patch PHKL_24027:
( SR: 8606113817 CR: JAGac12337 )
While truncating a memory mapped VxFS file, VxFS invalidates
the partial page containing eof causing data corruption.
Resolution:
Don't invalidate the partial page containing eof while
truncating a memory mapped file.
( SR: 8606144927 CR: JAGad14267 )
For uids between 2560 and 9983 and for uids 15104 or
higher, chown(1m) needs to extend the quota file which
fails since incorrect block size is used.
Resolution:
Make sure correct block size is used while extending the
quota file.
( SR: 8606177859 CR: JAGad47086 )
Under some extreme corner cases a file's link to the user
quota structure is removed and thereafter
allocation/deallocation of blocks to the file are not
accounted in the quota. This may result in incorrect
quota calculation for users and sometimes this may cause
charging the users for heavy usage of the filesystem.
Resolution:
Make sure the all files have proper links to user quota
structure always.
( SR:8606183708 CR:JAGad52921 )
VxFS may free a vnode while a buffer associated with that
vnode is in use in sendfile(2). Later when the sendfile
code accesses the vnode through the buffer, the system
panics.
Resolution:
Set up a dummy vnode which is not freed and use that vnode
for buffers passed to sendfile(2) so that sendfile(2)
code will always be accessing a valid vnode.
Based on HP-UX patch PHKL_24012:
( SR: 8606180062 DTS: JAGad49284 )
The system panics while unlocking a lock on an inode. The
lock was freed by a thread reusing the inode while another
thread had locked it for flushing the inode. Later when the
flushing thread tries to unlock the freed lock a system
panic results.
Resolution:
Keep a hold on the vnode while flushing the inode so that
the inode is not reused while being flushed.
PHKL_22561:
Ported HP-UX patch PHKL_22432 to VVOS
Based on HP-UX patch PHKL_22432:
( SR: 8606156750 DTS: JAGad26084 )
VxFS inodes were not cleaned up properly while deleting the
files. This may lead to have inodes in inconsistent
state in the inode cache, and later system may panic
while processing them. Also a flag on the inode
to indicate that the inode is in reuse, was reset
without having the proper lock, leading to races with
other functions processing the inode.
Resolution: Clean up inodes when files are
deleted. Also reset the above flag on the inode while
holding the required lock.
( SR: 8606140628 DTS: JAGad09987 )
The problem is a deadlock created between 2 VxFS threads
when accessing the same inode. One thread will have
incremented the soft hold count on the inode, and wait for
the inode lock, while the other thread will have the inode
lock waiting for the soft hold count of the inode to go to
zero.
Resolution:
The fix is for the thread that is holding the soft hold
count to give up the soft hold if it detects inode lock
is held by some other thread.
Based on HP-UX patch PHKL_21392:
( SR: 8606105425 DTS: JAGab73477 )
vx_real_iget() was holding the vnode without having the
inode lock in the "found" path, causing race conditions with
several other VxFS routines, which in turn resulted in data
page fault panics.
Resolution:
Get inode lock before holding the vnode in vx_real_iget().
PHKL_21225:
Ported HP-UX patch PHKL_20079 to VVOS
Based on HP-UX patch PHKL_20079:
( SR: 8606104878 DTS: JAGab72639 )
The number of spin locks was insufficient for systems with
several processors. VxFS performance is very poor with the
current 32 spin locks for inode operations.
Resolution:
Increase the number of spin locks to 256.
Based on HP-UX patch PHKL_19942:
( SR: 8606104878 DTS: JAGab72639 )
vx_iget always locks the ibmap exclusively and sets the
ibmap. This is not needed if the inode has the ibmap
correctly. This unnecessary locking affects performance.
Resolution:
Lock the ibmap only if necessary to set the ibmapops.
PHKL_19441:
Ported HP-UX patch PHKL_19169 to VVOS
Based on HP-UX patch PHKL_19169:
( SR: 8606101101 DTS: JAGab21116 )
The problem is a deadlock created between 2 VxFS processes
when accessing the same inode. One process will have
incremented the soft hold count on the inode, and wait for
the inode lock, while the other process will have the inode
lock waiting for the soft hold count of the inode to go to
zero.
Resolution:
The fix is for the process that is holding the inode lock to
give up the lock if it detects a non-zero soft hold count in
the inode after a limited number of retries.
PHKL_20911:
Ported HP-UX patch PHKL_20674 to VVOS
Based on HP-UX patch PHKL_20674:
(SR: 8606113482 DTS : JAGac00113)
vx_ireuse_clean() was assuming the vx_inodes on the free
lists will have i_max_lwrid = 0. So when an inode is stolen
from the free lists, fields i_fs, i_slocks... are reset,
but not i_max_lwrid. This may lead to a Data Page Fault in
vx_fsflushi(). This problem was introduced by PHKL_17205.
Resolution: vx_inactive_tran() should make sure that
i_max_lwrid = 0, before putting the vx_inode to the free
lists.
Based on HP-UX patch PHKL_19800:
1. While unmounting a VxFS, the unmount will lock all the
active inodes in the file system, in an infinite loop.
This may hang a uniprocessor, if the inode is locked
by somebody else. This is introduced by the patch
PHKL_18531.
Resolution: release the processor before retrying to lock
the inode, while unmounting the FS.
2. If more than one process write to a memory mapped file,
a deadlock may occur between inode locks and buffer
cache, because of the incorrect ordering of the locks.
To reproduce the problem, map a file to memory and
keep writing to the pages. Start two other processes
which write to this file. VxFS hangs.
Resoltion: Changed the ordering of locks, so that the
deadlock condition is avoided.
PHKL_19989:
Redundant code in routine vx_write1() is resulting in
system zeroing out privilege vectors and calling
vx_iupdat() with every write() system call.
Resolution:
Clear privilege vectors and update the inode only
if privileges exist on the file. Once the privileges
are cleared, subsequent writes to the same file
will not zero out privilege vectors and not call
vx_iupdat().
Based on HP-UX patch PHKL_20401:
(SR: 4701415679 DTS: JAGaa93188 )
Negative user IDs were not taken care of while processing
the quotas. For example the UID of nobody is -2. This
was failing a sanity check in the quotaon code path.
Resolution:
Cast UIDs to unsigned in sanity checks
in various paths to take care of negative UIDs.
SR:
4701415679 8606101101 8606103794 8606104878 8606105015
8606105425 8606113482 8606113817 8606144927 8606177859
8606183708 8606140628 8606156750 8606180062 8606105681
Patch Files:
JournalFS.VXFS-PRG,fr=B.11.04,fa=HP-UX_B.11.04_32/64,v=HP:
/usr/include/sys/fs/vx_bsdquota.h
/usr/include/sys/fs/vx_port.h
JournalFS.VXFS-BASE-KRN,fr=B.11.04,fa=HP-UX_B.11.04_32,v=HP:
/usr/conf/lib/libvxfs_base.a(vx_bsdquota.o)
/usr/conf/lib/libvxfs_base.a(vx_iflush.o)
/usr/conf/lib/libvxfs_base.a(vx_inode.o)
/usr/conf/lib/libvxfs_base.a(vx_rdwri.o)
/usr/conf/lib/libvxfs_base.a(vx_vnops.o)
JournalFS.VXFS-BASE-KRN,fr=B.11.04,fa=HP-UX_B.11.04_64,v=HP:
/usr/conf/lib/libvxfs_base.a(vx_bsdquota.o)
/usr/conf/lib/libvxfs_base.a(vx_iflush.o)
/usr/conf/lib/libvxfs_base.a(vx_inode.o)
/usr/conf/lib/libvxfs_base.a(vx_rdwri.o)
/usr/conf/lib/libvxfs_base.a(vx_vnops.o)
what(1) Output:
JournalFS.VXFS-PRG,fr=B.11.04,fa=HP-UX_B.11.04_32/64,v=HP:
/usr/include/sys/fs/vx_bsdquota.h:
vx_bsdquota.h $Date: 1999/11/04 07:20:57 $Revision:
r11ros/1 PATCH_11.00 * (PHKL_20401)
vx_bsdquota.h: $Revision: 1.5.105.3 $ $Date: 97/03/0
6 14:22:50 $
src/kernel/vxfs/vx_bsdquota.h 2.6 12 Mar 1996 03:28:
15 - */
fshp:src/kernel/vxfs/vx_bsdquota.h 2.6
/usr/include/sys/fs/vx_port.h:
vx_port.h $Date: 1999/11/04 07:18:49 $Revision: r11r
os/2 PATCH_11.00 (PHKL_20401)
vx_port.h: $Revision: 1.5.106.3 $ $Date: 97/08/25 17
:03:17 $
src/kernel/vxfs/vx_port.h 2.28.7.6 17 Jul 1997 17:42
:52 - */
fshp:src/kernel/vxfs/vx_port.h 2.28.7.6
JournalFS.VXFS-BASE-KRN,fr=B.11.04,fa=HP-UX_B.11.04_32,v=HP:
/usr/conf/lib/libvxfs_base.a(vx_bsdquota.o):
vx_bsdquota.c $Date: 2001/05/07 13:50:24 $Revision:
r11ros/3 PATCH_11.00 (PHKL_24027)
/usr/conf/lib/libvxfs_base.a(vx_iflush.o):
vx_iflush.c $Date: 2001/04/25 11:31:43 $Revision: r1
1ros/13 PATCH_11.00 (PHKL_24012)
/usr/conf/lib/libvxfs_base.a(vx_inode.o):
$Source: kern/vxfs/vx_inode.c, hpuxsysvx, vvos_rose,
rose0250 $ $Date: 01/10/05 08:20:04 $ $Revi
sion: 1.25 PATCH_11.04 (PHKL_25054) $
/usr/conf/lib/libvxfs_base.a(vx_rdwri.o):
$Source: kern/vxfs/vx_rdwri.c, hpuxsysvx, vvos_rose,
rose0250 $ $Date: 01/10/05 08:21:06 $ $Revi
sion: 1.19 PATCH_11.04 (PHKL_25054) $
/usr/conf/lib/libvxfs_base.a(vx_vnops.o):
$Source: kern/vxfs/vx_vnops.c, hpuxsysvx, vvos_rose,
rose0250 $ $Date: 01/10/05 08:21:49 $ $Revi
sion: 1.31 PATCH_11.04 (PHKL_25054) $
JournalFS.VXFS-BASE-KRN,fr=B.11.04,fa=HP-UX_B.11.04_64,v=HP:
/usr/conf/lib/libvxfs_base.a(vx_bsdquota.o):
vx_bsdquota.c $Date: 2001/05/07 13:50:24 $Revision:
r11ros/3 PATCH_11.00 (PHKL_24027)
/usr/conf/lib/libvxfs_base.a(vx_iflush.o):
vx_iflush.c $Date: 2001/04/25 11:31:43 $Revision: r1
1ros/13 PATCH_11.00 (PHKL_24012)
/usr/conf/lib/libvxfs_base.a(vx_inode.o):
$Source: kern/vxfs/vx_inode.c, hpuxsysvx, vvos_rose,
rose0250 $ $Date: 01/10/05 08:20:04 $ $Revi
sion: 1.25 PATCH_11.04 (PHKL_25054) $
/usr/conf/lib/libvxfs_base.a(vx_rdwri.o):
$Source: kern/vxfs/vx_rdwri.c, hpuxsysvx, vvos_rose,
rose0250 $ $Date: 01/10/05 08:21:06 $ $Revi
sion: 1.19 PATCH_11.04 (PHKL_25054) $
/usr/conf/lib/libvxfs_base.a(vx_vnops.o):
$Source: kern/vxfs/vx_vnops.c, hpuxsysvx, vvos_rose,
rose0250 $ $Date: 01/10/05 08:21:49 $ $Revi
sion: 1.31 PATCH_11.04 (PHKL_25054) $
cksum(1) Output:
JournalFS.VXFS-PRG,fr=B.11.04,fa=HP-UX_B.11.04_32/64,v=HP:
1597616715 9802 /usr/include/sys/fs/vx_bsdquota.h
678860475 16256 /usr/include/sys/fs/vx_port.h
JournalFS.VXFS-BASE-KRN,fr=B.11.04,fa=HP-UX_B.11.04_32,v=HP:
1583160915 31192 /usr/conf/lib/libvxfs_base.a(vx_bsdquota.o)
2791890831 32908 /usr/conf/lib/libvxfs_base.a(vx_iflush.o)
695774865 50044 /usr/conf/lib/libvxfs_base.a(vx_inode.o)
89794469 36792 /usr/conf/lib/libvxfs_base.a(vx_rdwri.o)
3182930928 31300 /usr/conf/lib/libvxfs_base.a(vx_vnops.o)
JournalFS.VXFS-BASE-KRN,fr=B.11.04,fa=HP-UX_B.11.04_64,v=HP:
870772247 66824 /usr/conf/lib/libvxfs_base.a(vx_bsdquota.o)
4147897057 77552 /usr/conf/lib/libvxfs_base.a(vx_iflush.o)
2382098994 118832 /usr/conf/lib/libvxfs_base.a(vx_inode.o)
361428793 58496 /usr/conf/lib/libvxfs_base.a(vx_rdwri.o)
2227160423 62872 /usr/conf/lib/libvxfs_base.a(vx_vnops.o)
Patch Conflicts: None
Patch Dependencies:
s700: 11.04: PHKL_19142
s800: 11.04: PHKL_19142
Hardware Dependencies: None
Other Dependencies: None
Supersedes:
PHKL_19989 PHKL_22561 PHKL_20911 PHKL_21225 PHKL_19441
Equivalent Patches:
PHKL_24027:
s700: 11.00
s800: 11.00
Patch Package Size: 640 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_25054
5. Run swinstall to install the patch:
swinstall -x autoreboot=true -x patch_match_target=true \
-s /tmp/PHKL_25054.depot
By default swinstall will archive the original software in
/var/adm/sw/save/PHKL_25054. If you do not wish to retain a
copy of the original software, use the patch_save_files option:
swinstall -x autoreboot=true -x patch_match_target=true \
-x patch_save_files=false -s /tmp/PHKL_25054.depot
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_25054.text file is
available in the product readme:
swlist -l product -a readme -d /tmp/PHKL_25054.depot
To put this patch on a magnetic tape and install from the
tape drive, use the command:
dd if=/tmp/PHKL_25054.depot of=/dev/rmt/0m bs=2k
Special Installation Instructions:
This patch depends on base patch PHKL_19142
For successful installation please insure that PHKL_19142
is already installed, or that PHKL_19142 is included
in the same depot with this patch and PHKL_19142
is selected for installation.
-----End of Document ID: PHKL_25054------------------------------------------
Document ID: PHKL_25048
Date Loaded: 20011026
Title: s700_800 11.04 (VVOS) SCSI IO Subsystem Cumulative Patch
Patch Name: PHKL_25048
Patch Description: s700_800 11.04 (VVOS) SCSI IO Subsystem Cumulative Patch
Creation Date: 01/10/08
Post Date: 01/10/26
Hardware Platforms - OS Releases:
s700: 11.04
s800: 11.04
Products: N/A
Filesets:
OS-Core.CORE-KRN,fr=B.11.04,fa=HP-UX_B.11.04_32/64,v=HP
ProgSupport.C-INC,fr=B.11.04,fa=HP-UX_B.11.04_32/64,v=HP
OS-Core.CORE2-KRN,fr=B.11.04,fa=HP-UX_B.11.04_32,v=HP
OS-Core.KERN2-RUN,fr=B.11.04,fa=HP-UX_B.11.04_32,v=HP
SCSI-Passthru.SPT2-DVR,fr=B.11.04,fa=HP-UX_B.11.04_32,v=HP
OS-Core.CORE2-KRN,fr=B.11.04,fa=HP-UX_B.11.04_64,v=HP
OS-Core.KERN2-RUN,fr=B.11.04,fa=HP-UX_B.11.04_64,v=HP
SCSI-Passthru.SPT2-DVR,fr=B.11.04,fa=HP-UX_B.11.04_64,v=HP
Automatic Reboot?: Yes
Status: General Release
Critical:
Yes
PHKL_25048: OTHER PANIC HANG
Based on HP-UX Patch PHKL_24004: PANIC OTHER
Update 11.00 to 11.11 fails.
Based on HP-UX Patch PHKL_23281: PANIC HANG
Based on HP-UX Patch PHKL_22941: HANG OTHER
See description for details on enhancements
PHKL_23077: OTHER PANIC MEMORY_LEAK HANG
Based on HP-UX Patch PHKL_22759: OTHER
Based on HP-UX Patch PHKL_22460:PANIC MEM_LEK
PHKL_21745: ABORT OTHER PANIC MEMORY_LEAK CORRUPTION HANG
Based on HP-UX Patch PHKL_21607: PANIC HANG
Based on HP-UX Patch PHKL_21504: PANIC
Based on HP-UX Patch PHKL_20688: HANG
Based on HP-UX Patch PHKL_20629: PANIC HANG
Based on HP-UX Patch PHKL_20452: PANIC HANG
ABORT CORRUPTION MEMORY_LEAK OTHER
See list of Defect Symptoms for details.
Based on HP-UX Patch PHKL_20208: PANIC
Based on HP-UX Patch PHKL_19245: PANIC
PHKL_19403: PANIC
Based on HP-UX Patch PHKL_14688: PANIC
PHKL_18750: PANIC HANG
Based on HP-UX Patch PHKL_17333: HANG
Based on HP-UX Patch PHKL_13371: PANIC
Category Tags:
defect_repair hardware_enablement enhancement
general_release critical panic halts_system corruption
memory_leak
Path Name: /hp-ux_patches/s700_800/11.X/PHKL_25048
Symptoms:
PHKL_25048:
Ported HP-UX patch PHKL_24004 to VVOS
Based on HP-UX patch PHKL_24004:
( SR: 8606179935 CR: JAGad49157 )
If an error occurs that causes LVM to switch to an
alternate link (if configured) to access the physical
volume, a subsequent attempt to deactivate the volume
group with the command:
vgchange -a n [vg_name]
hangs.
( SR: 8606158737 CR: JAGad28067 )
The following informative message on the console and in
/var/adm/syslog/syslog.log unnecessary alarmed customers:
SCSI: Attempt to access partially open
device -- dev: %x
( SR:8606189487 CR: JAGad58701 )
An operating system update from 11.00 to 11.11 fails
during the kernel rebuild. The compilation of conf.c
fails with the the following messages:
WARNING: Duplicate tunable scsi_max_qdepth found
in /usr/conf/master.d/sctl.
Ignoring the following entry from
/usr/conf/master.d/sctl.
scsi_max_qdepth SCSI_MAX_QDEPTH 8
Compiling /stand/build/conf.c...
(Bundled) cc: "/usr/conf/space.h.d/scsi_ctl_space.h",
line 54: error 1588: "SCSI_MAX_QDEPTH" undefined.
(Bundled) cc: "/usr/conf/space.h.d/scsi_ctl_space.h",
line 54: error 1521: Incorrect initialization.
(Bundled) cc: "/usr/conf/space.h.d/scsi_ctl_space.h",
line 54: error 1521: Incorrect initialization.
(Bundled) cc: "/usr/conf/space.h.d/scsi_ctl_space.h",
line 72: error 1584: Inconsistent type declaration:
"scsi_max_qdepth".
(Bundled) cc: "/usr/conf/space.h.d/scsi_ctl_space.h",
line 72: error 1521: Incorrect initialization.
*** Error exit code 1
( SR: 8606199984 CR: JAGad69170 )
With heavy stress on Fibre Channel (FC) devices, the
system panics with the following stack trace:
panic+0x14
report_trap_or_int_and_panic+0x4c
interrupt+0x1e8
$ihndlr_rtn+0x0
scsi_is_synchronous_err+0x6c
scsi_action+0xb0
sd_retry+0x5c
scsi_cbfn+0x294
fcpdev_scsi_comp+0x20c
fcpbh_scsi_comp+0x5ec
fcpbh_fcp_cbfn+0x284
fcpbh_rcv_completer+0x450
fcT1_isr+0x77c
Based on HP-UX patch PHKL_23281:
( SR: 8606173791 CR: JAGad43048 )
A system panic occurs if a specific I/O logging level is
set while the system is experiencing I/O errors using the
passthrough driver. This panic may not occur if logging is
not enabled for investigation purposes. The panic causes
the following stack trace:
panic+0x14
report_trap_or_int_and_panic+0x80
interrupt+0x1d4
$ihndlr_rtn+0x0
scsi_dmesg_log_io+0xf8
scsi_action+0x1b8
scsi_status_action+0x6c
scsi_cbfn+0x41c
scsi_fast_cbfn+0x1b0
c720_call_cbfns+0x60
c720_isr+0x5bc
epic_isr+0x58
mp_ext_interrup