All Patches for PowerMAX 4.2 are:
audit-001 base-017 crypt-001 ie-001 ncr-001
base-001 base-018 crypt-002 inet-001 ncr-002
base-002 cld-001 crypt-int-001 inet-002 netboot-001
base-003 cluster-001 dec-001 inet-003 nfs-001
base-004 cluster-002 dec-002 inet-004 nfs-002
base-005 cluster-003 dec-003 inet-005 ngpib-001
base-006 cluster-004 dec-004 inet-006 nsu-001
base-007 cluster-005 dec-005 inet-007 nsu-002
base-008 cluster-006 dec-006 inet-008 pg-001
base-009 cmds-001 dec-007 librt-001 rpc-001
base-010 cmds-002 dec-008 man-001 via-001
base-011 cmds-003 dr11w-001 man-002 vp-001
base-013 crosslibs-001 fbs-001 man-003 vp-002
base-014 crosslibs-002 fd-001 man-004 vp-003
base-015 crosslibs-003 fibre-001 man-005 zld-001
base-016 crosslibs-004 ide-001 man-006 zld-002
================================================================================
Concurrent Computer Corporation Software Development
Software Patch Report
Patch Name: audit-001
Date Issued: 09/30/98 09:04:20
Software Package: audit pkg (Version 4.2)
OS Release: PowerMAX OS 4.2
Architectures: moto nh
Platforms: All PowerMAX OS 4.2 platforms
Related Patches: base-013 (Power Hawk 610/620, PowerStack, PowerStack II),
base-014 (Power Hawk 640, PowerStack II multi-processor),
base-015 (Night Hawk 6200/6800, TurboHawk, PowerMAXION)
Related SARS: none
Brief Description:
PowerMAX OS 4.2 audit package release updates
Problem Description:
1. Added audit package support for the new nvram(2) system call.
Problem Resolution:
1. Entries are added to the audit check function table and the audit
recording table any time a new system call is defined in the kernel.
Entries for the new nvram(2) system call were added to each of these
tables and were set to indicate that no auditing should be performed
by the kernel for this system call.
Object To Be Replaced:
/etc/conf/pack.d/audit/Driver.o
Special Conditions for Installation:
None.
Possible Side Effects:
None.
return to index
================================================================================
Concurrent Computer Corporation Software Development
Software Patch Report
Patch Name: audit-001
Date Issued: 09/30/98 09:04:20
Software Package: audit pkg (Version 4.2)
OS Release: PowerMAX OS 4.2
Architectures: moto nh
Platforms: All PowerMAX OS 4.2 platforms
Related Patches: base-013 (Power Hawk 610/620, PowerStack, PowerStack II),
base-014 (Power Hawk 640, PowerStack II multi-processor),
base-015 (Night Hawk 6200/6800, TurboHawk, PowerMAXION)
Related SARS: none
Brief Description:
PowerMAX OS 4.2 audit package release updates
Problem Description:
1. Added audit package support for the new nvram(2) system call.
Problem Resolution:
1. Entries are added to the audit check function table and the audit
recording table any time a new system call is defined in the kernel.
Entries for the new nvram(2) system call were added to each of these
tables and were set to indicate that no auditing should be performed
by the kernel for this system call.
Object To Be Replaced:
/etc/conf/pack.d/audit/Driver.o
Special Conditions for Installation:
None.
Possible Side Effects:
None.
return to index
================================================================================
Concurrent Computer Corporation Software Development
Software Patch Report
Patch Name: audit-001
Date Issued: 09/30/98 09:04:20
Software Package: audit pkg (Version 4.2)
OS Release: PowerMAX OS 4.2
Architectures: moto nh
Platforms: All PowerMAX OS 4.2 platforms
Related Patches: base-013 (Power Hawk 610/620, PowerStack, PowerStack II),
base-014 (Power Hawk 640, PowerStack II multi-processor),
base-015 (Night Hawk 6200/6800, TurboHawk, PowerMAXION)
Related SARS: none
Brief Description:
PowerMAX OS 4.2 audit package release updates
Problem Description:
1. Added audit package support for the new nvram(2) system call.
Problem Resolution:
1. Entries are added to the audit check function table and the audit
recording table any time a new system call is defined in the kernel.
Entries for the new nvram(2) system call were added to each of these
tables and were set to indicate that no auditing should be performed
by the kernel for this system call.
Object To Be Replaced:
/etc/conf/pack.d/audit/Driver.o
Special Conditions for Installation:
None.
Possible Side Effects:
None.
return to index
================================================================================
Concurrent Computer Corporation Software Development
Software Patch Report
Patch Name: base-001
Date Issued: 03/23/98 17:50:15
Software Package: base pkg (Version 4.2)
OS Release: PowerMAX OS 4.2
Architectures: moto
Platforms: Power Hawk 610, 620, PowerStack, PowerStack II
Related Patches: none
Related SARS: HM12323, HM12326
Brief Description:
PowerMAX OS 4.2 base package release updates.
Problem Description:
1. Write errors may occur using cp or cpio on xfs file systems
if the file system is fragmented, even though df shows
plenty of free space is available.
2. mkfs -F xfs (or newfs -F xfs) allows an extent size of 1MB
to be selected with the default fragment size (512 bytes)
using the -e 1024K option. This file system will become
corrupted due to xfs system pages being overwritten by user
files.
3. PANIC: kernel-mode address fault on user address 0x4E800048
The C91007a.X ADA test issued a server_wake1() system call
with argument 1 which is the global_lwpid_t server = 0.
server_wake1() called lwp_find() which is supposed to locate
the proc and lwp structures for the supplied global_lwpid_t.
However, a value of 0 caused lwp_find() to try to reference
p->p_lwpdir[-1]. This picked up a garbage address (0x4E800020)
for the lwp structure which resulted in a reference to an
unallocated memory location (0x4E800048).
4. Panics due to priority inheritance list corruption. This only
occurs with multi-lwp processes.
5. A race condition existed in the special file system driver
that resulted in various "Alignment Fault" kernel panics.
These faults could occur when closing a character special
device followed very closely by an open of the same device.
6. A user-level interrupts fix for SAR HM12323.
When a LWP is disconnected from an interrupt vector
(ICON_DISC), and a deallocation of that same vector (ICON_IVEC
II_DEALLOCATE) occurs at about the same point in time, then
applications are unable to re-allocate that same interrupt
vector until the system is rebooted.
7. NIS doesn't work with cpio and tar (because they are built
statically).
8. The console driver does not support modem control ioctls
(TIOCMGET/TIOCMSET).
9. The console driver fails to drop DTR on COM2 when HUPCL
has been specified and 6 or 8 bit character widths are
used.
10. Loosely-coupled multiprocessors experience random hangs or
panics during periods of heavy VME networking activity.
11. When a kernel panic occurs, the machine drops into kdb as expected.
However, once the kdb command "q" is given to exit kdb and continue
with the dump, the machine will attempt to write the dump but almost
immediately drop into the console debugger. The panicking CPU never
has a chance to complete the dump because the non-panicking CPU
enters the console debugger and interrupts the panicking CPU.
12. When the console debugger is entered, sometimes CPU 1 fails to halt.
CPU 0, upon entering the console debugger, sends an inter-processor
interrupt (IPI 3) to CPU 1 in order to force it into the console
debugger. This interrupt is not always recognized by CPU 1.
13. When CPU 1 is the first CPU to enter the console debugger, the
machine will hang up anywhere from 30 seconds to 3 minutes. Once
CPU 0 enters the console debugger, a flag is set in the console
debugger code indicating that CPU 0 halted. However, this flag is
never cleared upon exit from the console debugger. When CPU 1
subsequently enters the console debugger first, it sees that CPU 0
has been flagged as being halted when it in reality has not halted.
Because of this, CPU 1 does not send inter-processor interrupt
(IPI 3) to CPU 0 to force it into the console debugger and spins
waiting to be started by CPU 0.
14. Changes need to be made to /etc/conf/pack.d/sbc/stubs.c to allow a
kernel to be built on a machine that has the FBS package installed
but not the cluster package.
15. Temporary file handling using writes to xfs files that have
been opened then unlinked fails with EINVAL returned. For
example, this happens when using tmpfile(3S) on an xfs file system.
Problem Resolution:
1. Prior to this fix, xfs selected the size of the first file
extent based on the size of the first write to the file up
to a limit of 1MB. This limit is now set to the file
system extent size which is determined when the file system
was created (default 64KB). You can use "fstyp -v" to see
the file system extent size. See mkfs_xfs(1M) man page for
how to set a larger file system extent size if you prefer
to have xfs default to large extents.
Note this change has no effect on the behaviour of
fallocate(3X).
2. mkfs for xfs has been changed to prohibit the combination of
an extent size of 1024K with a fragment size of 512 bytes.
3. lwp_find() will now check for and return (lwp_t *)0 if
the llwpid portion of the supplied global_lwpid_t is 0.
4. The priority inheritance list was not correctly initialized when
creating new lwps within an existing process.
5. Removed the race condition.
6. Close the race in the kernel between interrupt vector
deallocations and disconnecting a LWP from an interrupt
vector, so that the interrupt vector is always properly
deallocated, thus allowing future allocations of that same
interrupt vector to succeed.
7. Build static and dynamic versions of tar and cpio. Dynamic
by default, in /usr/bin. Static versions in /sbin.
8. Added support for TIOCMGET/TIOCMSET which works on all 4
COM ports. The driver now supports setting/resetting
TIOCM_DTR and TIOCM_RTS using TIOCMSET, and will report
the current state of the following lines using TIOCMGET:
TIOCM_DTR, TIOCM_RTS, TIOCM_CTS, TIOCM_CAR, TIOCM_RNG,
and TIOCM_DSR.
9. A variable in the DTR setting logic was not properly
initialized to zero. The stale value was inherited from
bits used to select character widths. When 6 or 8 bit
character widths were specified, one of the bits inherited
forced the assertion of DTR.
10. An inappropriate interrupt level was being used for vme
message passing which was incomparable with generic
"Streams" code. Fixed the sbc/vmemsg drivers to interrupt
at IPL5 which is compatible with "Streams" modules.
11. Add code to kernel pause_self() function to allow the non-panicking
CPU to drop IPL and spin until forced into the console debugger by
the panicking CPU.
12. Add code to cpu_serv() console debugger function to temporarily
boost the priority of IPI 3 from a very low priority of 0x1 to the
highest priority of 0xf when an inter-processor interrupt is to be
sent. The priority is returned to 0x1 by CPU 0 before it enters the
console debugger command prompt loop centry().
13. a. In the console debugger kern_restart() function, if the CPU to
be restarted is CPU 0, then its halted flag is cleared before
returning to context before the console debugger was entered.
b. In the console debugger runcpu() and stepcpu() functions,
CPU 0's halted flag is cleared before restarting it.
14. Make appropriate changes to the stubs source code file.
15. Corrected a regression introduced in code for xfs writes to
non-persistent files.
Object To Be Replaced:
/etc/conf/cf.d/intr.s
/etc/conf/pack.d/bsp2600/Driver.o
/etc/conf/pack.d/cons/Driver.o
/etc/conf/pack.d/mem/Driver.o
/etc/conf/pack.d/vme/Driver.o
/etc/conf/pack.d/proc/Driver.o
/etc/conf/pack.d/sbc/stubs.c
/etc/conf/pack.d/specfs/Driver.o
/etc/conf/pack.d/svc/Driver.o
/etc/conf/pack.d/ui/Driver.o
/etc/conf/pack.d/xfs/Driver.o
/etc/fs/xfs/mkfs
/sbin/cpio.st
/sbin/tar.st
/stand/cp1
/usr/bin/cpio
/usr/lib/fs/xfs/mkfs
/usr/include/sys/vm_mdep.h
/usr/include/sys/z8536.h
/usr/sbin/tar
Special Conditions for Installation:
During installation of base-001, an updated version of /stand/cp1
will be installed and the new console overlay will be written to
partition 6 on the system disk. Following successful installation,
the system must be taken down and reset to load the new console
before rebooting. Failure to do so may result in unexpected or
unreliable behavior.
Possible Side Effects:
If the base-001 package is removed (pkgrm(1M)), the original
console will be re-written to partition 6 on the system disk. To
ensure there are no adverse side effects, the kernel should be
rebuilt (idbuild(1M)) and the system taken down and reset to load
the original console before rebooting the system.
Suggested procedure for removing base-001:
# pkgrm base-001
# /etc/conf/bin/idbuild -B
# sync
# init 0
# Reset system
Follow the normal boot procedure detailed in the PowerMAX OS Product
Release Notes to load the new console and boot the new kernel.
return to index
================================================================================
Concurrent Computer Corporation Software Development
Software Patch Report
Patch Name: base-002
Date Issued: 03/23/98 18:02:53
Software Package: base pkg (Version 4.2)
OS Release: PowerMAX OS 4.2
Architectures: moto
Platforms: Power Hawk 640, PowerStack II (multi-processor only)
Related Patches: none
Related SARS: HM12323, HM12326
Brief Description:
PowerMAX OS 4.2 base package release updates.
Problem Description:
1. Write errors may occur using cp or cpio on xfs file systems
if the file system is fragmented, even though df shows
plenty of free space is available.
2. mkfs -F xfs (or newfs -F xfs) allows an extent size of 1MB
to be selected with the default fragment size (512 bytes)
using the -e 1024K option. This file system will become
corrupted due to xfs system pages being overwritten by user
files.
3. PANIC: kernel-mode address fault on user address 0x4E800048
The C91007a.X ADA test issued a server_wake1() system call
with argument 1 which is the global_lwpid_t server = 0.
server_wake1() called lwp_find() which is supposed to locate
the proc and lwp structures for the supplied global_lwpid_t.
However, a value of 0 caused lwp_find() to try to reference
p->p_lwpdir[-1]. This picked up a garbage address (0x4E800020)
for the lwp structure which resulted in a reference to an
unallocated memory location (0x4E800048).
4. Panics due to priority inheritance list corruption. This only
occurs with multi-lwp processes.
5. A race condition existed in the special file system driver
that resulted in various "Alignment Fault" kernel panics.
These faults could occur when closing a character special
device followed very closely by an open of the same device.
6. A user-level interrupts fix for SAR HM12323.
When a LWP is disconnected from an interrupt vector
(ICON_DISC), and a deallocation of that same vector (ICON_IVEC
II_DEALLOCATE) occurs at about the same point in time, then
applications are unable to re-allocate that same interrupt
vector until the system is rebooted.
7. NIS doesn't work with cpio and tar (because they are built
statically).
8. The console driver does not support modem control ioctls
(TIOCMGET/TIOCMSET).
9. The console driver fails to drop DTR on COM2 when HUPCL
has been specified and 6 or 8 bit character widths are
used.
10. Loosely-coupled multiprocessors experience random hangs or
panics during periods of heavy VME networking activity.
11. When a kernel panic occurs, the machine drops into kdb as expected.
However, once the kdb command "q" is given to exit kdb and continue
with the dump, the machine will attempt to write the dump but almost
immediately drop into the console debugger. The panicking CPU never
has a chance to complete the dump because the non-panicking CPU
enters the console debugger and interrupts the panicking CPU.
12. When the console debugger is entered, sometimes CPU 1 fails to halt.
CPU 0, upon entering the console debugger, sends an inter-processor
interrupt (IPI 3) to CPU 1 in order to force it into the console
debugger. This interrupt is not always recognized by CPU 1.
13. When CPU 1 is the first CPU to enter the console debugger, the
machine will hang up anywhere from 30 seconds to 3 minutes. Once
CPU 0 enters the console debugger, a flag is set in the console
debugger code indicating that CPU 0 halted. However, this flag is
never cleared upon exit from the console debugger. When CPU 1
subsequently enters the console debugger first, it sees that CPU 0
has been flagged as being halted when it in reality has not halted.
Because of this, CPU 1 does not send inter-processor interrupt
(IPI 3) to CPU 0 to force it into the console debugger and spins
waiting to be started by CPU 0.
14. Changes need to be made to /etc/conf/pack.d/sbc/stubs.c to allow a
kernel to be built on a machine that has the FBS package installed
but not the cluster package.
15. Temporary file handling using writes to xfs files that have
been opened then unlinked fails with EINVAL returned. For
example, this happens when using tmpfile(3S) on an xfs file system.
Problem Resolution:
1. Prior to this fix, xfs selected the size of the first file
extent based on the size of the first write to the file up
to a limit of 1MB. This limit is now set to the file
system extent size which is determined when the file system
was created (default 64KB). You can use "fstyp -v" to see
the file system extent size. See mkfs_xfs(1M) man page for
how to set a larger file system extent size if you prefer
to have xfs default to large extents.
Note this change has no effect on the behaviour of
fallocate(3X).
2. mkfs for xfs has been changed to prohibit the combination of
an extent size of 1024K with a fragment size of 512 bytes.
3. lwp_find() will now check for and return (lwp_t *)0 if
the llwpid portion of the supplied global_lwpid_t is 0.
4. The priority inheritance list was not correctly initialized when
creating new lwps within an existing process.
5. Removed the race condition.
6. Close the race in the kernel between interrupt vector
deallocations and disconnecting a LWP from an interrupt
vector, so that the interrupt vector is always properly
deallocated, thus allowing future allocations of that same
interrupt vector to succeed.
7. Build static and dynamic versions of tar and cpio. Dynamic
by default, in /usr/bin. Static versions in /sbin.
8. Added support for TIOCMGET/TIOCMSET which works on all 4
COM ports. The driver now supports setting/resetting
TIOCM_DTR and TIOCM_RTS using TIOCMSET, and will report
the current state of the following lines using TIOCMGET:
TIOCM_DTR, TIOCM_RTS, TIOCM_CTS, TIOCM_CAR, TIOCM_RNG,
and TIOCM_DSR.
9. A variable in the DTR setting logic was not properly
initialized to zero. The stale value was inherited from
bits used to select character widths. When 6 or 8 bit
character widths were specified, one of the bits inherited
forced the assertion of DTR.
10. An inappropriate interrupt level was being used for vme
message passing which was incomparable with generic
"Streams" code. Fixed the sbc/vmemsg drivers to interrupt
at IPL5 which is compatible with "Streams" modules.
11. Add code to kernel pause_self() function to allow the non-panicking
CPU to drop IPL and spin until forced into the console debugger by
the panicking CPU.
12. Add code to cpu_serv() console debugger function to temporarily
boost the priority of IPI 3 from a very low priority of 0x1 to the
highest priority of 0xf when an inter-processor interrupt is to be
sent. The priority is returned to 0x1 by CPU 0 before it enters the
console debugger command prompt loop centry().
13. a. In the console debugger kern_restart() function, if the CPU to
be restarted is CPU 0, then its halted flag is cleared before
returning to context before the console debugger was entered.
b. In the console debugger runcpu() and stepcpu() functions,
CPU 0's halted flag is cleared before restarting it.
14. Make appropriate changes to the stubs source code file.
15. Corrected a regression introduced in code for xfs writes to
non-persistent files.
Object To Be Replaced:
/etc/conf/cf.d/intr.s
/etc/conf/pack.d/bsp4600/Driver.o
/etc/conf/pack.d/cons/Driver.o
/etc/conf/pack.d/mem/Driver.o
/etc/conf/pack.d/vme/Driver.o
/etc/conf/pack.d/proc/Driver.o
/etc/conf/pack.d/sbc/stubs.c
/etc/conf/pack.d/specfs/Driver.o
/etc/conf/pack.d/svc/Driver.o
/etc/conf/pack.d/ui/Driver.o
/etc/conf/pack.d/xfs/Driver.o
/etc/fs/xfs/mkfs
/sbin/cpio.st
/sbin/tar.st
/stand/cp1
/usr/bin/cpio
/usr/include/sys/vm_mdep.h
/usr/include/sys/z8536.h
/usr/lib/fs/xfs/mkfs
/usr/sbin/tar
Special Conditions for Installation:
During installation of base-002, an updated version of /stand/cp1
will be installed and the new console overlay will be written to
partition 6 on the system disk. Following successful installation,
the system must be taken down and reset to load the new console
before rebooting. Failure to do so may result in unexpected or
unreliable behavior.
Possible Side Effects:
If the base-002 package is removed (pkgrm(1M)), the original
console will be re-written to partition 6 on the system disk. To
ensure there are no adverse side effects, the kernel should be
rebuilt (idbuild(1M)) and the system taken down and reset to load
the original console before rebooting the system.
Suggested procedure for removing base-002:
# pkgrm base-002
# /etc/conf/bin/idbuild -B
# sync
# init 0
# Reset system
Follow the normal boot procedure detailed in the PowerMAX OS Product
Release Notes to load the new console and boot the new kernel.
return to index
================================================================================
Concurrent Computer Corporation Software Development
Software Patch Report
Patch Name: base-003
Date Issued: 03/24/98 10:19:38
Software Package: base pkg (Version 4.2)
OS Release: PowerMAX OS 4.2
Architectures: nh
Platforms: Night Hawk 6200/6800, Night Hawk 6800 Turbo, PowerMAXION
Related Patches: none
Related SARS: HM12323
Brief Description:
PowerMAX OS 4.2 base package release updates.
Problem Description:
1. Write errors may occur using cp or cpio on xfs file systems
if the file system is fragmented, even though df shows
plenty of free space is available.
2. mkfs -F xfs (or newfs -F xfs) allows an extent size of 1MB
to be selected with the default fragment size (512 bytes)
using the -e 1024K option. This file system will become
corrupted due to xfs system pages being overwritten by user
files.
3. PANIC: kernel-mode address fault on user address 0x4E800048
The C91007a.X ADA test issued a server_wake1() system call
with argument 1 which is the global_lwpid_t server = 0.
server_wake1() called lwp_find() which is supposed to locate
the proc and lwp structures for the supplied global_lwpid_t.
However, a value of 0 caused lwp_find() to try to reference
p->p_lwpdir[-1]. This picked up a garbage address (0x4E800020)
for the lwp structure which resulted in a reference to an
unallocated memory location (0x4E800048).
4. Panics due to priority inheritance list corruption. This only
occurs with multi-lwp processes.
5. A race condition existed in the special file system driver
that resulted in various "Alignment Fault" kernel panics.
These faults could occur when closing a character special
device followed very closely by an open of the same device.
6. A user-level interrupts fix for SAR HM12323.
When a LWP is disconnected from an interrupt vector
(ICON_DISC), and a deallocation of that same vector (ICON_IVEC
II_DEALLOCATE) occurs at about the same point in time, then
applications are unable to re-allocate that same interrupt
vector until the system is rebooted.
7. NIS doesn't work with cpio and tar (because they are built
statically).
8. PowerMAX OS did not support the new 256Mbyte local memory map
on the TurboHAWK system.
9. PowerMAX OS did not support the posted write feature of the Tundra
VME interface on TurboHAWK systems.
10. There was an error in the setup of the Tundra VME interface on the
two global memory cards on TurboHAWK systems. This allowed DMA
data from VME devices destined for certain local memory ranges to
also be written to the global memory boards. This Tundra setup did
not correctly reflect the address map of TurboHAWK system memory.
11. Accessing of interval timers on processor cards 6 or 7 of TurboHAWK
systems caused a system panic. This was due to an incorrect
definition of the physical addresses of the timers on these boards.
12. Temporary file handling using writes to xfs files that have
been opened then unlinked fails with EINVAL returned. For
example, this happens when using tmpfile(3S) on an xfs file system.
13. 3 and 4 position frontplanes on TurboHAWK systems with the 256Mbyte
local memory map assign the last processor board to be board 6,
but the local memory address map treats it as if it were board 3.
Problem Resolution:
1. Prior to this fix, xfs selected the size of the first file
extent based on the size of the first write to the file up
to a limit of 1MB. This limit is now set to the file
system extent size which is determined when the file system
was created (default 64KB). You can use "fstyp -v" to see
the file system extent size. See mkfs_xfs(1M) man page for
how to set a larger file system extent size if you prefer
to have xfs default to large extents.
Note this change has no effect on the behaviour of
fallocate(3X).
2. mkfs for xfs has been changed to prohibit the combination of
an extent size of 1024K with a fragment size of 512 bytes.
3. lwp_find() will now check for and return (lwp_t *)0 if
the llwpid portion of the supplied global_lwpid_t is 0.
4. The priority inheritance list was not correctly initialized when
creating new lwps within an existing process.
5. Removed the race condition.
6. Close the race in the kernel between interrupt vector
deallocations and disconnecting a LWP from an interrupt
vector, so that the interrupt vector is always properly
deallocated, thus allowing future allocations of that same
interrupt vector to succeed.
7. Build static and dynamic versions of tar and cpio. Dynamic
by default, in /usr/bin. Static versions in /sbin.
8. Modified PowerMAX OS to take full advantage of the 256Mbyte local
memory map on TurboHAWK systems.
9. Modified PowerMAX OS to take advantage of the write posting feature
of the Tundra VME interface. This feature improves data throughput
on TurboHAWK systems.
10. The setup of the Tundra VME interface on TurboHAWK global memories
was changed to correctly reflect the address map of the TurboHAWK
system memory.
11. The address definitions of the interval timers on TurboHAWK boards
6 and 7 were corrected.
12. Corrected a regression introduced in code for xfs writes to
non-persistent files.
13. Code was added to convert processor board 6's local memory address
range to that of processor board 3's address range. This address
range is programmed into the Tundra VME interface.
Object To Be Replaced:
/etc/conf/pack.d/bspall/Driver.o
/etc/conf/pack.d/bsp6800t/Driver.o
/etc/conf/pack.d/mem/Driver.o
/etc/conf/pack.d/proc/Driver.o
/etc/conf/pack.d/specfs/Driver.o
/etc/conf/pack.d/ui/Driver.o
/etc/conf/pack.d/vme/Driver.o
/etc/conf/pack.d/xfs/Driver.o
/etc/fs/xfs/mkfs
/sbin/cpio.st
/sbin/tar.st
/usr/bin/cpio
/usr/lib/fs/xfs/mkfs
/usr/include/sys/vm_mdep.h
/usr/include/vm/memory_p.h
/usr/sbin/tar
Special Conditions for Installation:
None.
Possible Side Effects:
None.
return to index
================================================================================
Concurrent Computer Corporation Software Development
Software Patch Report
Patch Name: base-004
Date Issued: 06/08/98 13:55:54
Software Package: base pkg (Version 4.2)
OS Release: PowerMAX OS 4.2
Architectures: moto
Platforms: Power Hawk 610/620, PowerStack, PowerStack II
Related Patches: vp-001
Related SARS: HM12390, HM12188, HM12359
Brief Description:
PowerMAX OS 4.2 base package release updates
Problem Description:
1. If the xfs module is to be configured, the system needs to know that
xfsth must also be configured. This is important for cluster systems
for which the default is to not configure xfs.
2. Mentat UDP performance poor with STREAMS network buffers. Use of
other drivers which set a write offset on a stream may also be
affected.
A STREAMS driver can control how the stream head allocates space for
messages sent downstream. A write offset may be set which causes the
stream head to allocate additional memory for a driver to use. This
is generally done to avoid incurring memory allocation overheads.
The stream head was copying data from user space into kernel space
whenever it had a write offset set on a stream. This was being done
on the first element of a vectored write regardless of whether
network buffers were being used or not. In cases where the first
element of a vectored write was large this was incurring a large
processing overhead copying the data.
3. STREAMS network buffers fail if a transmission is greater than the
maximum PDU size allowed by a STREAMS driver. Normal STREAMS output
is unaffected.
If a user process attempts to send greater than the maximum PDU size
allowed by a STREAMS driver, the data is segmented at the stream
head. Each segment is transmitted separately. The segmentation
mechanism breaks down if network buffers are being used.
4. According to POSIX, a process whose priority is lowered goes to the
end of its new priority run queue. Thus, if there are other
processes already in that queue, the lowered lwp must give up the
CPU immediately to them and wait its turn. This was not happening.
Instead, the running lwp would continue to run until it either
voluntarily gave up the CPU, or some other event, such as I/O
completion, caused the CPU to re-evaluate which lwp was supposed to
be running.
5. SAR HM12390: A check to free an unneeded data structure was missing
in one execution path. The data structure was only unneeded if the
calling process had already opened a semaphore prior to this
invocation to open one.
6. Improve performance for disk striping (VP). Related to patch vp-001.
* on very large transfers, a substantial amount of time is spent
locking pages in memory.
7. The setrun(1) command would not accept an engine number > 3.
8. In PowerMAX OS 4.2, xfsrestore is unable to restore a tape created
by fsdump as it had in previous releases.
This causes the following error to be reported by xfsrestore:
. is not on tape
Root directory is not on tape
abort? [yn]
9. In some situations, the thread library may create many more
multiplexing (MUX) LWPs than the amount needed by the application.
The creation of all these extra MUX LWPs tends to waste system
resources and add unnecessary system overhead.
10. When a process attempts to fork(2), the fork(2) operation never
completes due to the fact that the rendezvous operation does not ever
complete. (The rendezvous operation brings all the other LWP's
into the kernel and holds them there in a known state while the
fork(2) operation then proceeds to duplicate the process image.)
The rendezvous operation fails to complete because one or more LWPs
in the process are currently blocked in the kernel via mq_send(3)
or mq_receive(3) with their rescheduling variable locked/held.
The RV lock prevents these LWPs from honoring the pending rendezvous
request until the RV is unlocked.
11. SARs HM12188, HM12359: The IDE device driver introduced in
PowerMAX OS 4.2 utilized the ISA interrupt levels from the floppy
(irq6) and line printer (irq7) drivers. This resulted in a
non-functional floppy driver and line printer driver on all Motorola
based platforms - even those that don't support IDE.
12. Systems get into a state where preemption on a CPU no longer occurs.
This "hangs" the CPU and may lead to a hung system. It occurs on
systems using FP-class (real-time) scheduling.
13. Panics on kernel data access exceptions when mmap'ing a process using
memory-based file systems. Problem seen using "usermap".
Problem Resolution:
1. Appropriate $depend entries are added to the xfs and xfsth files in
/etc/conf/mdevice.d/.
2. The stream head has been changed to allocate an additional message
block for drivers to write to during streams output. This is done if
there is a write offset set for a stream and the first element of a
vectored write (writev() ) or a write() is in a STREAMS network
buffer. The message block is chained to the beginning of the message
sent downstream to drivers.
3. The stream head has been changed to correctly update data structures
updated during the transmission of each segment of data.
4. The cause was the failure of the priocntl system call to nudge the
CPU after changing the lwp's priority (i.e., failed to force the CPU
to re-evaluate which lwp it was supposed to run). The lwp was
actually put at the end of its new run queue as it should have been,
but without the nudge the CPU did not notice the changed
circumstances of the lwp.
The solution was to expand the `if' statement that does nudging in
priocntl(2) to nudge if the new priority run queue was not empty
prior to the insertion.
5. Restored the missing check.
6. Improve performance for disk striping (VP).
* With segdev driver (bound shared memory), eliminate page locking
checks if entire segment is already locked in memory.
7. Rather than asking the system what engines were available, setrun(1)
had this hard-wired to 0-3. This command was appropriately changed
to ask for a mask of available engines.
8. The code in xfsrestore that handles tapes created by fsdump was fixed.
9. When the kernel sees the last LWP in a process about to block
itself, the kernel sends a SIGWAITING signal to the process's
SIGWAITING signal handler. This is done to give the thread library
a chance to create another MUX LWP if the process contains
additional MUX threads that are ready to run and that need a LWP to
execute on.
The thread library's SIGWAITING signal handler was modified so that
instead of always creating a new MUX LWP when there are MUX threads
that are ready to run, a check is now first made to see if there are
idle MUX LWPs. If so, then this signal handler just unblocks one of
these idle MUX LWPs instead of creating a new MUX LWP.
10. The fix is to unlock the rescheduling variable in the thread library
before calling block(2) in the kernel and to relock the rescheduling
variable upon return from the block(2) call.
11. The ISA interrupts have been reassigned to support all 4 ISA
devices: primary IDE, secondary IDE, floppy, and line printer.
New ISA irq assignments: 6=lpt, 7=fp, 10=p-ide, 14=s-ide.
12. Fix preemption disable counter which was being incorrectly
incremented/decremented in context switcher routine.
13. memfs mmap routine was incorrectly addressing beyond end of
pseudo-vnode.
Object To Be Replaced:
/etc/conf/cf.d/intr.s
/etc/conf/mdevice.d/xfs
/etc/conf/mdevice.d/xfsth
/etc/conf/pack.d/bsp2600/Driver.o
/etc/conf/pack.d/bspall/Driver.o
/etc/conf/pack.d/bspall/space.c
/etc/conf/pack.d/bspmtx/Driver.o
/etc/conf/pack.d/bspmtx/space.c
/etc/conf/pack.d/io/Driver.o
/etc/conf/pack.d/isa/Driver.o
/etc/conf/pack.d/memfs/Driver.o
/etc/conf/pack.d/proc/Driver.o
/etc/conf/pack.d/segdev/Driver.o
/usr/bin/setrun
/usr/include/sys/ipl_masks.h
/usr/lib/fs/xfs/xfsrestore
/usr/lib/libthread.a
/usr/lib/libthread.so
Special Conditions for Installation:
The following objects are linked to some of the objects being
replaced by this patch. These objects will also be re-linked:
/usr/lib/libposix1c.a
/usr/lib/libposix1c.so
/usr/sbin/xfsrestore
Possible Side Effects:
None.
return to index
================================================================================
Concurrent Computer Corporation Software Development
Software Patch Report
Patch Name: base-005
Date Issued: 06/08/98 14:03:57
Software Package: base pkg (Version 4.2)
OS Release: PowerMAX OS 4.2
Architectures: moto
Platforms: Power Hawk 640, PowerStack II (multi-processor only)
Related Patches: vp-001
Related SARS: HM12390, HM12188, HM12359
Brief Description:
PowerMAX OS 4.2 base package release updates
Problem Description:
1. If the xfs module is to be configured, the system needs to know that
xfsth must also be configured. This is important for cluster systems
for which the default is to not configure xfs.
2. Mentat UDP performance poor with STREAMS network buffers. Use of
other drivers which set a write offset on a stream may also be
affected.
A STREAMS driver can control how the stream head allocates space for
messages sent downstream. A write offset may be set which causes the
stream head to allocate additional memory for a driver to use. This
is generally done to avoid incurring memory allocation overheads.
The stream head was copying data from user space into kernel space
whenever it had a write offset set on a stream. This was being done
on the first element of a vectored write regardless of whether
network buffers were being used or not. In cases where the first
element of a vectored write was large this was incurring a large
processing overhead copying the data.
3. STREAMS network buffers fail if a transmission is greater than the
maximum PDU size allowed by a STREAMS driver. Normal STREAMS output
is unaffected.
If a user process attempts to send greater than the maximum PDU size
allowed by a STREAMS driver, the data is segmented at the stream
head. Each segment is transmitted separately. The segmentation
mechanism breaks down if network buffers are being used.
4. According to POSIX, a process whose priority is lowered goes to the
end of its new priority run queue. Thus, if there are other
processes already in that queue, the lowered lwp must give up the
CPU immediately to them and wait its turn. This was not happening.
Instead, the running lwp would continue to run until it either
voluntarily gave up the CPU, or some other event, such as I/O
completion, caused the CPU to re-evaluate which lwp was supposed to
be running.
5. SAR HM12390: A check to free an unneeded data structure was missing
in one execution path. The data structure was only unneeded if the
calling process had already opened a semaphore prior to this
invocation to open one.
6. Improve performance for disk striping (VP). Related to patch vp-001.
* on very large transfers, a substantial amount of time is spent
locking pages in memory.
7. The setrun(1) command would not accept an engine number > 3.
8. In PowerMAX OS 4.2, xfsrestore is unable to restore a tape created
by fsdump as it had in previous releases.
This causes the following error to be reported by xfsrestore:
. is not on tape
Root directory is not on tape
abort? [yn]
9. In some situations, the thread library may create many more
multiplexing (MUX) LWPs than the amount needed by the application.
The creation of all these extra MUX LWPs tends to waste system
resources and add unnecessary system overhead.
10. When a process attempts to fork(2), the fork(2) operation never
completes due to the fact that the rendezvous operation does not ever
complete. (The rendezvous operation brings all the other LWP's
into the kernel and holds them there in a known state while the
fork(2) operation then proceeds to duplicate the process image.)
The rendezvous operation fails to complete because one or more LWPs
in the process are currently blocked in the kernel via mq_send(3)
or mq_receive(3) with their rescheduling variable locked/held.
The RV lock prevents these LWPs from honoring the pending rendezvous
request until the RV is unlocked.
11. SARs HM12188, HM12359: The IDE device driver introduced in
PowerMAX OS 4.2 utilized the ISA interrupt levels from the floppy
(irq6) and line printer (irq7) drivers. This resulted in a
non-functional floppy driver and line printer driver on all Motorola
based platforms - even those that don't support IDE.
12. The "ALLINTSONCPU0" tunable does not work correctly on Power Hawk 640
systems. It was not possible to -override- this tunable and
indicate a cpu for a specific interrupt.
13. Systems get into a state where preemption on a CPU no longer occurs.
This "hangs" the CPU and may lead to a hung system. It occurs on
systems using FP-class (real-time) scheduling.
14. Panics on kernel data access exceptions when mmap'ing a process using
memory-based file systems. Problem seen using "usermap".
Problem Resolution:
1. Appropriate $depend entries are added to the xfs and xfsth files in
/etc/conf/mdevice.d/.
2. The stream head has been changed to allocate an additional message
block for drivers to write to during streams output. This is done if
there is a write offset set for a stream and the first element of a
vectored write (writev() ) or a write() is in a STREAMS network
buffer. The message block is chained to the beginning of the message
sent downstream to drivers.
3. The stream head has been changed to correctly update data structures
updated during the transmission of each segment of data.
4. The cause was the failure of the priocntl system call to nudge the
CPU after changing the lwp's priority (i.e., failed to force the CPU
to re-evaluate which lwp it was supposed to run). The lwp was
actually put at the end of its new run queue as it should have been,
but without the nudge the CPU did not notice the changed
circumstances of the lwp.
The solution was to expand the `if' statement that does nudging in
priocntl(2) to nudge if the new priority run queue was not empty
prior to the insertion.
5. Restored the missing check.
6. Improve performance for disk striping (VP).
* With segdev driver (bound shared memory), eliminate page locking
checks if entire segment is already locked in memory.
7. Rather than asking the system what engines were available, setrun(1)
had this hard-wired to 0-3. This command was appropriately changed
to ask for a mask of available engines.
8. The code in xfsrestore that handles tapes created by fsdump was fixed.
9. When the kernel sees the last LWP in a process about to block
itself, the kernel sends a SIGWAITING signal to the process's
SIGWAITING signal handler. This is done to give the thread library
a chance to create another MUX LWP if the process contains
additional MUX threads that are ready to run and that need a LWP to
execute on.
The thread library's SIGWAITING signal handler was modified so that
instead of always creating a new MUX LWP when there are MUX threads
that are ready to run, a check is now first made to see if there are
idle MUX LWPs. If so, then this signal handler just unblocks one of
these idle MUX LWPs instead of creating a new MUX LWP.
10. The fix is to unlock the rescheduling variable in the thread library
before calling block(2) in the kernel and to relock the rescheduling
variable upon return from the block(2) call.
11. The ISA interrupts have been reassigned to support all 4 ISA
devices: primary IDE, secondary IDE, floppy, and line printer.
New ISA irq assignments: 6=lpt, 7=fp, 10=p-ide, 14=s-ide.
12. Fix so that override of "ALLINTSONCPU0" can be done for a specific
interrupt.
13. Fix preemption disable counter which was being incorrectly
incremented/decremented in context switcher routine.
14. memfs mmap routine was incorrectly addressing beyond end of
pseudo-vnode.
Object To Be Replaced:
/etc/conf/cf.d/intr.s
/etc/conf/mdevice.d/xfs
/etc/conf/mdevice.d/xfsth
/etc/conf/pack.d/bsp4600/Driver.o
/etc/conf/pack.d/bsp4600/space.c
/etc/conf/pack.d/bspmpall/Driver.o
/etc/conf/pack.d/bspmpall/space.c
/etc/conf/pack.d/bspmtx/Driver.o
/etc/conf/pack.d/bspmtx/space.c
/etc/conf/pack.d/io/Driver.o
/etc/conf/pack.d/isa/Driver.o
/etc/conf/pack.d/memfs/Driver.o
/etc/conf/pack.d/proc/Driver.o
/etc/conf/pack.d/segdev/Driver.o
/usr/bin/setrun
/usr/include/sys/ipl_masks.h
/usr/lib/fs/xfs/xfsrestore
/usr/lib/libthread.a
/usr/lib/libthread.so
Special Conditions for Installation:
I. The following objects are linked to some of the objects being
replaced by this patch. These objects will also be re-linked:
/usr/lib/libposix1c.a
/usr/lib/libposix1c.so
/usr/sbin/xfsrestore
II. Following successful installation of base-005, the system must be
shutdown and reset before booting the new kernel. Failure to do
so may result in unexpected or unreliable behavior.
Suggested procedure for installing base-005:
Install base-005 using pkgadd(1M)
# /etc/conf/bin/idbuild -B
# sync
# init 0
Reset system
Follow the normal boot procedure detailed in the PowerMAX OS
Product Release Notes to load the console and boot the new kernel.
Possible Side Effects:
none.
return to index
================================================================================
Concurrent Computer Corporation Software Development
Software Patch Report
Patch Name: base-006
Date Issued: 06/08/98 14:09:15
Software Package: base pkg (Version 4.2)
OS Release: PowerMAX OS 4.2
Architectures: nh
Platforms: Night Hawk 6200/6800, TurboHawk, PowerMAXION
Related Patches: ncr-001, dec-006, vp-001
Related SARS: HM12390, HM12351
Brief Description:
PowerMAX OS 4.2 base package release updates
Problem Description:
1. If the xfs module is to be configured, the system needs to know that
xfsth must also be configured.
2. Mentat UDP performance poor with STREAMS network buffers. Use of
other drivers which set a write offset on a stream may also be
affected.
A STREAMS driver can control how the stream head allocates space for
messages sent downstream. A write offset may be set which causes the
stream head to allocate additional memory for a driver to use. This
is generally done to avoid incurring memory allocation overheads.
The stream head was copying data from user space into kernel space
whenever it had a write offset set on a stream. This was being done
on the first element of a vectored write regardless of whether
network buffers were being used or not. In cases where the first
element of a vectored write was large this was incurring a large
processing overhead copying the data.
3. STREAMS network buffers fail if a transmission is greater than the
maximum PDU size allowed by a STREAMS driver. Normal STREAMS output
is unaffected.
If a user process attempts to send greater than the maximum PDU size
allowed by a STREAMS driver, the data is segmented at the stream
head. Each segment is transmitted separately. The segmentation
mechanism breaks down if network buffers are being used.
4. According to POSIX, a process whose priority is lowered goes to the
end of its new priority run queue. Thus, if there are other
processes already in that queue, the lowered lwp must give up the
CPU immediately to them and wait its turn. This was not happening.
Instead, the running lwp would continue to run until it either
voluntarily gave up the CPU, or some other event, such as I/O
completion, caused the CPU to re-evaluate which lwp was supposed to
be running.
5. SAR HM12390: A check to free an unneeded data structure was missing
in one execution path. The data structure was only unneeded if the
calling process had already opened a semaphore prior to this
invocation to open one.
6. Improve performance for disk striping (VP). Related to patch vp-001.
* on very large transfers, a substantial amount of time is spent
locking pages in memory.
7. The setrun(1) command would not accept an engine number > 3.
8. In PowerMAX OS 4.2, xfsrestore is unable to restore a tape created
by fsdump as it had in previous releases.
This causes the following error to be reported by xfsrestore:
. is not on tape
Root directory is not on tape
abort? [yn]
9. In some situations, the thread library may create many more
multiplexing (MUX) LWPs than the amount needed by the application.
The creation of all these extra MUX LWPs tends to waste system
resources and add unnecessary system overhead.
10. When a process attempts to fork(2), the fork(2) operation never
completes due to the fact that the rendezvous operation does not ever
complete. (The rendezvous operation brings all the other LWP's
into the kernel and holds them there in a known state while the
fork(2) operation then proceeds to duplicate the process image.)
The rendezvous operation fails to complete because one or more LWPs
in the process are currently blocked in the kernel via mq_send(3)
or mq_receive(3) with their rescheduling variable locked/held.
The RV lock prevents these LWPs from honoring the pending rendezvous
request until the RV is unlocked.
11. On PowerMAXION-8 systems, attempts to address VME devices in
secondary I/O caused a bus error.
12. On PowerMAXION-8 systems, interrupts for VME devices in secondary I/O
were not routed to the frontplane. These interrupts could not be
serviced by any processors and rendered VME devices on secondary
I/O inoperable.
13. TurboHawk system hardware was modified to increase the PCI bus
throughput. The software did not support these changes.
14. SAR HM12351: While running the PowerAT test, the console would
occasionally hang. Output would resume if the spacebar or other key
is touched.
15. Systems get into a state where preemption on a CPU no longer occurs.
This "hangs" the CPU and may lead to a hung system. It occurs on
systems using FP-class (real-time) scheduling.
16. Panics on kernel data access exceptions when mmap'ing a process using
memory-based file systems. Problem seen using "usermap".
Problem Resolution:
1. Appropriate $depend entries are added to the xfs and xfsth files in
/etc/conf/mdevice.d/.
2. The stream head has been changed to allocate an additional message
block for drivers to write to during streams output. This is done if
there is a write offset set for a stream and the first element of a
vectored write (writev() ) or a write() is in a STREAMS network
buffer. The message block is chained to the beginning of the message
sent downstream to drivers.
3. The stream head has been changed to correctly update data structures
updated during the transmission of each segment of data.
4. The cause was the failure of the priocntl system call to nudge the
CPU after changing the lwp's priority (i.e., failed to force the CPU
to re-evaluate which lwp it was supposed to run). The lwp was
actually put at the end of its new run queue as it should have been,
but without the nudge the CPU did not notice the changed
circumstances of the lwp.
The solution was to expand the `if' statement that does nudging in
priocntl(2) to nudge if the new priority run queue was not empty
prior to the insertion.
5. Restored the missing check.
6. Improve performance for disk striping (VP).
* With segdev driver (bound shared memory), eliminate page locking
checks if entire segment is already locked in memory.
7. Rather than asking the system what engines were available, setrun(1)
had this hard-wired to 0-3. This command was appropriately changed
to ask for a mask of available engines.
8. The code in xfsrestore that handles tapes created by fsdump was fixed.
9. When the kernel sees the last LWP in a process about to block
itself, the kernel sends a SIGWAITING signal to the process's
SIGWAITING signal handler. This is done to give the thread library
a chance to create another MUX LWP if the process contains
additional MUX threads that are ready to run and that need a LWP to
execute on.
The thread library's SIGWAITING signal handler was modified so that
instead of always creating a new MUX LWP when there are MUX threads
that are ready to run, a check is now first made to see if there are
idle MUX LWPs. If so, then this signal handler just unblocks one of
these idle MUX LWPs instead of creating a new MUX LWP.
10. The fix is to unlock the rescheduling variable in the thread library
before calling block(2) in the kernel and to relock the rescheduling
variable upon return from the block(2) call.
11. Corrected the initialization of the memory base and memory limit
registers on the DEC D21152 bridge on PowerMAXION-8 systems.
12. During system initialization of PowerMAXION-8 systems, all interrupts
on the Global Memory cards are routed to the frontplane.
13. Modified the initialization of the PLX Bridge, the Tundra VME
interface, embedded DEC Ethernet controller and embedded NCR SCSI
controller. This change allowed the Operating System to take
advantage of hardware changes on TurboHawk systems for increased PCI
bus throughput.
14. A change to the way the console driver handles interrupts introduced
this new problem into PowerMAX OS 4.2. Previously, the driver used
to scan both channels of a UART on interrupt from either channel.
Changes made in 4.2 accidently created a (rare) condition in which
an interrupt occasionally would not be responded to. This lack of
response was the cause of the hang.
15. Fix preemption disable counter which was being incorrectly
incremented/decremented in context switcher routine.
16. memfs mmap routine was incorrectly addressing beyond end of
pseudo-vnode.
Object To Be Replaced:
/etc/conf/mdevice.d/xfs
/etc/conf/mdevice.d/xfsth
/etc/conf/pack.d/bsp6408/Driver.o
/etc/conf/pack.d/cons/Driver.o
/etc/conf/pack.d/io/Driver.o
/etc/conf/pack.d/memfs/Driver.o
/etc/conf/pack.d/pci/Driver.o
/etc/conf/pack.d/proc/Driver.o
/etc/conf/pack.d/segdev/Driver.o
/etc/conf/pack.d/vme/Driver.o
/usr/bin/setrun
/usr/lib/fs/xfs/xfsrestore
/usr/lib/libthread.a
/usr/lib/libthread.so
Special Conditions for Installation:
The following objects are linked to some of the objects being
replaced by this patch. These objects will also be re-linked:
/usr/lib/libposix1c.a
/usr/lib/libposix1c.so
/usr/sbin/xfsrestore
Possible Side Effects:
None.
return to index
================================================================================
Concurrent Computer Corporation Software Development
Software Patch Report
Patch Name: base-007
Date Issued: 08/12/98 09:40:38
Software Package: base pkg (Version 4.2)
OS Release: PowerMAX OS 4.2
Architectures: moto
Platforms: Power Hawk 610/620, PowerStack, PowerStack II
Related Patches: nfs-002, crypt-001, inet-005, crosslibs-002, mvc (4.2.1)
Related SARS: HM12246, HM12322, HM12396, HM12413, HM12429, HM12430
Brief Description:
PowerMAX OS 4.2 base package release updates
Problem Description:
1. XFS file system loses file space that is reclaimed after remounting
The problem is associated with two kinds of temporary files:
(a) files that have been created then unlinked before being
written to;
(b) files that have been mmap'ed and subsequently removed.
Creating large temporary files of type (a) or (b) with indirect
blocks results in progressive loss of file space until the file
system becomes full. Rebooting or unmounting and remounting the
file system will reclaim all the file space lost in this way.
2. Multi-threaded applications that use user-level interrupts and
spl_request(3X) or spl_manage(3X) may hang the system.
The spl_request(3X) and spl_manage(3X) library routines lock an
internal lwp mutex lock while reading and writing the ipl value.
If this internal lock is currently locked from a thread calling
spl_request(3X)/spl_manage(3X) at program level when a user-level
interrupt routine becomes active, then a spl_request(3X) or
spl_manage(3X) call that is made from the user-level interrupt
routine will be unable to get the internal lwp mutex lock, and the
routine will spin forever at interrupt level, attempting to acquire
the lock.
3. There is currently no way for a user application to get the current
ipl level.
It is not possible to get the current ipl level without also
setting the ipl level with the spl_request(3X) or spl_manage(3X)
routines.
4. HM12322: PPC Time Base Register constants for Power Hawk 620/640 and
PowerStack II in the _hair routines of libud (also known as
TIE_FREQ_RATE) are incorrect. Because the values are incorrect for
the bus clock rating for Power Hawk 620/640 and PowerStack II
architectures, time stamps from programs that link libud could be
erroneous.
5. HM12246, HM12396: Modification of ldterm, serial, rtserial and
idmknod are required for new mvc driver.
6. HM12413: Several problems with lockd (nfs lock manager):
(a) Locks held by a client that crashes are not properly
recovered. This may result in incorrect file locks that
are never released.
(b) In some cases, when a process on a client system blocks
waiting for a lock, it would not get woken up after the
lock was released.
(c) There is a long time period between the reboot of a system
and its detection on the server.
7. HM12429: Some of the socket library routines may permanently set the
user's signal disposition of SIGPOLL to SIG_IGN (ignore the signal).
Some of the socket library routines may internally change the user's
signal disposition of SIGPOLL to SIG_IGN (ignore the signal) and
never change it back to its original disposition.
This problem will occur when these routines are called while the
SIGPOLL signal is currently being held/masked in the calling LWP's
signal mask.
8. HM12430: On XFS file systems, unlink(2) of a directory should not be
allowed if directory is not empty.
A problem in the check code of the directory unlink function did not
prevent a root user unlinking a non-empty directory. This results
in the directory content being removed from the file system but the
filespace allocated to the directory content not being released.
9. XFS file system: Stale File Handle errors on LCS targets with xfs
virtual root.
A timing window in the xfs_vget function used by NFS to attach to
file system nodes resulted in stale file handle errors when the NFS
was used over a very fast network link.
10. XFS file system: xfs_badop panic with xfs host file system and
Hummingbird NFS client and attempt to remove a file on the client
without required permissions.
A NFS protocol error in the Hummingbird client resulted in the
activation of a diagnostic panic when the client attempted an
invalid operation (VOP_LOOKUP on a file).
11. VMEbus DMA Controller (DMAC) device enhancement.
The DMA Controller (DMAC) device driver enhancement provides a user
interface to the on board Tundra Universe DMAC engine allowing high
speed block-mode transfers between user memory and a VMEbus slave
device.
12. The tunable IGNORE_STRAYS cannot be set on moto systems.
The system tunable IGNORE_STRAYS can be set so that stray interrupts
are ignored. However, on Motorola platforms this tunable has no
effect.
13. Under certain conditions, a program that modifies its scheduling
class may end up panicing the system with the message:
"XX scheduling class deferred a parameter change"
14. When either IGNORE_BUS_TIMEOUTS or IGNORE_SYSFAIL is enabled, then
the iobus_err(2) will return ENOSYS since the iobus_err(2) support
is not compatible with ignoring bus timeouts.
15. VME interrupts may be directed to the wrong CPU on a Power Hawk 640
system.
16. Motorola systems with low-level PPCBug firmware verions 3.5 and above
would appear to not boot the Power Hawk console.
Problem Resolution:
1. Fix xfs kernel code so that the indirect blocks are correctly
marked as free in the in-memory free space maps when a temporary
file is removed.
2. The lwp mutex lock is not required by the spl_request(3X) and
spl_manage(3X) routines. Therefore, this lock will no longer be
used by these two routines.
3. Add a new spl_value(3X) routine to libud that simply returns the
current ipl (architecture dependent) ipl level:
pl_t spl_value(caddr_t spl_map_address);
Where 'spl_map_address' is the address that was returned from a
previous spl_map(3X) call.
4. Modified the TIE_FREQ_RATE value returned by _hair_get_arch_info()
to be consistent with the bus clock rating for the Power Hawk
620/640 and PowerStack II architectures.
5. A new release (4.2.1) of the mvc package is replacing the 4.2
version, to provide new features (including rtserial device support)
and improved performance and reliability. Small problems in the
aforementioned I/O modules were found and corrected during
development and test of the new driver.
Additionally, idmknod(1M) did not permit a single line in a node
file to define both tty ports and printer ports, as the structure
of the new driver requires. All of the idtools have been updated
as a result of these changes.
6. lockd problems resolved as follows:
(a) Upon detecting that a client has crashed (and rebooted),
the server will clear ALL locks held by that client.
(b) Add a small delay in the kernel code that re-requests a
lock via the local lockd. This allows other messages to be
received.
(c) Shorten the initial start-up delay in statd from 15 to 5
seconds.
7. Change the appropriate libsocket routines so that they do not change
the process's signal disposition for the SIGPOLL signal.
See related patches inet-005 and crypt-001.
8. Add extra check to unlink directory code path.
9. Change xfs_vget node lookup to avoid the window.
10. Conditional compile the diagnostic panic, release code now just
returns error.
11. Added support for new DMAC driver.
12. Corrected the interrupt logic so that IGNORE_STRAYS works as
indicated.
13. Conditions for this to occur are for a parent process to change its
class and then change it back and THEN spawn a new process or lwp.
The new lwp/process would attempt to process the new scheduling class
change but there wouldn't be one present. Fixed to account for this
condition (i.e. NULL deferred scheduling class changes).
14. Change the way that the kernel handles bus timeouts so that the
iobus_err(2) processing still functions properly even when
IGNORE_BUS_TIMEOUTS and IGNORE_SYSFAIL are enabled.
15. Fix the interrupt logic to account for the CPU that a VME interrupt
is directed to when it scans the interrupt status word on the Tundra
Universe chip.
16. The console was actually booting, but very slowly. PPCBug 3.5 and
above enter user code with Instruction Cache disabled. Correction
re-enables the Instruction Cache.
Object To Be Replaced:
/etc/conf/bin/idcheck
/etc/conf/bin/idconfig
/etc/conf/bin/idinstall
/etc/conf/bin/idmknod
/etc/conf/bin/idmodload
/etc/conf/bin/idreadauto
/etc/conf/cf.d/intr.s
/etc/conf/mdevice.d/dmac
/etc/conf/mtune.d/dmac
/etc/conf/node.d/dmac
/etc/conf/pack.d/bsp1600/Driver.o
/etc/conf/pack.d/bsp2600/Driver.o
/etc/conf/pack.d/bspall/Driver.o
/etc/conf/pack.d/bspmtx/Driver.o
/etc/conf/pack.d/bsppstk/Driver.o
/etc/conf/pack.d/dmac/Driver.o
/etc/conf/pack.d/dmac/space.c
/etc/conf/pack.d/dmac/stubs.c
/etc/conf/pack.d/fs/Driver.o
/etc/conf/pack.d/iobus_err/Driver.o
/etc/conf/pack.d/ldterm/Driver.o
/etc/conf/pack.d/proc/Driver.o
/etc/conf/pack.d/rtserial/Driver.o
/etc/conf/pack.d/sbc/stubs.c
/etc/conf/pack.d/serial/Driver.o
/etc/conf/pack.d/svc/Driver.o
/etc/conf/pack.d/xfs/Driver.o
/etc/conf/sdevice.d/dmac
/stand/cp1
/usr/include/sys/dmac.h
/usr/include/sys/fcntl.h
/usr/include/sys/ipl.h
/usr/lib/libnsl_i.a
/usr/lib/libsocket.so
/usr/lib/libud.a
/usr/lib/libud.so
Special Conditions for Installation:
NOTICE #1: The changes to libud and <sys/ipl.h> for Problem #3 should
be installed on systems where multi-threaded applications
call spl_request(3X) or spl_manage(3X) from program level
threads and also from a user-level interrupt routine.
NOTICE #2: Systems which have installed the beta test (preliminary)
"dmac" package, should remove the package prior to
installation of this update. To remove the "dmac" package,
execute the following command (as root):
# /usr/sbin/pkgrm dmac
NOTICE #3: The dmac driver is not compatible with the latest release
of the cluster package software, therefore, it is installed
in the disabled state. If your system is configured with
the cluster pkg software, you must install patch cluster-004,
also on this tape, in order to use the dmac driver. If your
system is not configured with the cluster pkg software, then
you may enable the driver by editing the file 'dmac' under
the kernel configuration directory /etc/conf/sdevice.d and
substitute the 'N' for 'Y' before building a new unix kernel
using the idbuild(1M) command.
NOTICE #4: The following objects are linked to some of the objects being
replaced by this patch. These objects will also be re-linked:
/usr/lib/libnsl.a
/usr/lib/libxti.a
/usr/lib/libsocket.a
NOTICE #5: This patch modifies /etc/conf/cf.d/intr.s. If this file has
been modified locally, then those local changes will need to
be re-applied after the patch is installed.
NOTICE #6: During installation of base-007, an updated version of
/stand/cp1 will be installed and the new console overlay will
be written to partition 6 on the system disk. Following
successful installation, the system must be taken down and
reset to load the new console before rebooting. Failure to
do so may result in unexpected or unreliable behavior.
Possible Side Effects:
If the base-007 package is removed (pkgrm(1M)), the original console
will be re-written to partition 6 on the system disk. To ensure there
are no adverse side effects, the kernel should be rebuilt (idbuild(1M))
and the system taken down and reset to load the original console before
rebooting the system.
Suggested procedure for removing base-007:
# pkgrm base-007
# /etc/conf/bin/idbuild -B
# sync
# init 0
# Reset system
Follow the normal boot procedure detailed in the PowerMAX OS Product
Release Notes to load the new console and boot the new kernel.
return to index
================================================================================
Concurrent Computer Corporation Software Development
Software Patch Report
Patch Name: base-008
Date Issued: 08/12/98 10:02:08
Software Package: base pkg (Version 4.2)
OS Release: PowerMAX OS 4.2
Architectures: moto
Platforms: Power Hawk 640, PowerStack II (multi-processor only)
Related Patches: nfs-002, crypt-001, inet-005, crosslibs-002, mvc (4.2.1)
Related SARS: HM12246, HM12322, HM12396, HM12413, HM12429, HM12430
Brief Description:
PowerMAX OS 4.2 base package release updates
Problem Description:
1. XFS file system loses file space that is reclaimed after remounting
The problem is associated with two kinds of temporary files:
(a) files that have been created then unlinked before being
written to;
(b) files that have been mmap'ed and subsequently removed.
Creating large temporary files of type (a) or (b) with indirect
blocks results in progressive loss of file space until the file
system becomes full. Rebooting or unmounting and remounting the
file system will reclaim all the file space lost in this way.
2. Multi-threaded applications that use user-level interrupts and
spl_request(3X) or spl_manage(3X) may hang the system.
The spl_request(3X) and spl_manage(3X) library routines lock an
internal lwp mutex lock while reading and writing the ipl value.
If this internal lock is currently locked from a thread calling
spl_request(3X)/spl_manage(3X) at program level when a user-level
interrupt routine becomes active, then a spl_request(3X) or
spl_manage(3X) call that is made from the user-level interrupt
routine will be unable to get the internal lwp mutex lock, and the
routine will spin forever at interrupt level, attempting to acquire
the lock.
3. There is currently no way for a user application to get the current
ipl level.
It is not possible to get the current ipl level without also
setting the ipl level with the spl_request(3X) or spl_manage(3X)
routines.
4. HM12322: PPC Time Base Register constants for Power Hawk 620/640 and
PowerStack II in the _hair routines of libud (also known as
TIE_FREQ_RATE) are incorrect. Because the values are incorrect for
the bus clock rating for Power Hawk 620/640 and PowerStack II
architectures, time stamps from programs that link libud could be
erroneous.
5. HM12246, HM12396: Modification of ldterm, serial, rtserial and
idmknod are required for new mvc driver.
6. HM12413: Several problems with lockd (nfs lock manager):
(a) Locks held by a client that crashes are not properly
recovered. This may result in incorrect file locks that
are never released.
(b) In some cases, when a process on a client system blocks
waiting for a lock, it would not get woken up after the
lock was released.
(c) There is a long time period between the reboot of a system
and its detection on the server.
7. HM12429: Some of the socket library routines may permanently set the
user's signal disposition of SIGPOLL to SIG_IGN (ignore the signal).
Some of the socket library routines may internally change the user's
signal disposition of SIGPOLL to SIG_IGN (ignore the signal) and
never change it back to its original disposition.
This problem will occur when these routines are called while the
SIGPOLL signal is currently being held/masked in the calling LWP's
signal mask.
8. HM12430: On XFS file systems, unlink(2) of a directory should not be
allowed if directory is not empty.
A problem in the check code of the directory unlink function did not
prevent a root user unlinking a non-empty directory. This results
in the directory content being removed from the file system but the
filespace allocated to the directory content not being released.
9. XFS file system: Stale File Handle errors on LCS targets with xfs
virtual root.
A timing window in the xfs_vget function used by NFS to attach to
file system nodes resulted in stale file handle errors when the NFS
was used over a very fast network link.
10. XFS file system: xfs_badop panic with xfs host file system and
Hummingbird NFS client and attempt to remove a file on the client
without required permissions.
A NFS protocol error in the Hummingbird client resulted in the
activation of a diagnostic panic when the client attempted an
invalid operation (VOP_LOOKUP on a file).
11. VMEbus DMA Controller (DMAC) device enhancement.
The DMA Controller (DMAC) device driver enhancement provides a user
interface to the on board Tundra Universe DMAC engine allowing high
speed block-mode transfers between user memory and a VMEbus slave
device.
12. The tunable IGNORE_STRAYS cannot be set on moto systems.
The system tunable IGNORE_STRAYS can be set so that stray interrupts
are ignored. However, on Motorola platforms this tunable has no
effect.
13. Under certain conditions, a program that modifies its scheduling
class may end up panicing the system with the message:
"XX scheduling class deferred a parameter change"
14. When either IGNORE_BUS_TIMEOUTS or IGNORE_SYSFAIL is enabled, then
the iobus_err(2) will return ENOSYS since the iobus_err(2) support
is not compatible with ignoring bus timeouts.
15. VME interrupts may be directed to the wrong CPU on a Power Hawk 640
system.
16. Motorola systems with low-level PPCBug firmware verions 3.5 and above
would appear to not boot the Power Hawk console.
Problem Resolution:
1. Fix xfs kernel code so that the indirect blocks are correctly
marked as free in the in-memory free space maps when a temporary
file is removed.
2. The lwp mutex lock is not required by the spl_request(3X) and
spl_manage(3X) routines. Therefore, this lock will no longer be
used by these two routines.
3. Add a new spl_value(3X) routine to libud that simply returns the
current ipl (architecture dependent) ipl level:
pl_t spl_value(caddr_t spl_map_address);
Where 'spl_map_address' is the address that was returned from a
previous spl_map(3X) call.
4. Modified the TIE_FREQ_RATE value returned by _hair_get_arch_info()
to be consistent with the bus clock rating for the Power Hawk
620/640 and PowerStack II architectures.
5. A new release (4.2.1) of the mvc package is replacing the 4.2
version, to provide new features (including rtserial device support)
and improved performance and reliability. Small problems in the
aforementioned I/O modules were found and corrected during
development and test of the new driver.
Additionally, idmknod(1M) did not permit a single line in a node
file to define both tty ports and printer ports, as the structure
of the new driver requires. All of the idtools have been updated
as a result of these changes.
6. lockd problems resolved as follows:
(a) Upon detecting that a client has crashed (and rebooted),
the server will clear ALL locks held by that client.
(b) Add a small delay in the kernel code that re-requests a
lock via the local lockd. This allows other messages to be
received.
(c) Shorten the initial start-up delay in statd from 15 to 5
seconds.
7. Change the appropriate libsocket routines so that they do not change
the process's signal disposition for the SIGPOLL signal.
See related patches inet-005 and crypt-001.
8. Add extra check to unlink directory code path.
9. Change xfs_vget node lookup to avoid the window.
10. Conditional compile the diagnostic panic, release code now just
returns error.
11. Added support for new DMAC driver.
12. Corrected the interrupt logic so that IGNORE_STRAYS works as
indicated.
13. Conditions for this to occur are for a parent process to change its
class and then change it back and THEN spawn a new process or lwp.
The new lwp/process would attempt to process the new scheduling class
change but there wouldn't be one present. Fixed to account for this
condition (i.e. NULL deferred scheduling class changes).
14. Change the way that the kernel handles bus timeouts so that the
iobus_err(2) processing still functions properly even when
IGNORE_BUS_TIMEOUTS and IGNORE_SYSFAIL are enabled.
15. Fix the interrupt logic to account for the CPU that a VME interrupt
is directed to when it scans the interrupt status word on the Tundra
Universe chip.
16. The console was actually booting, but very slowly. PPCBug 3.5 and
above enter user code with Instruction Cache disabled. Correction
re-enables the Instruction Cache.
Object To Be Replaced:
/etc/conf/bin/idcheck
/etc/conf/bin/idconfig
/etc/conf/bin/idinstall
/etc/conf/bin/idmknod
/etc/conf/bin/idmodload
/etc/conf/bin/idreadauto
/etc/conf/cf.d/intr.s
/etc/conf/mdevice.d/dmac
/etc/conf/mtune.d/dmac
/etc/conf/node.d/dmac
/etc/conf/pack.d/bsp4600/Driver.o
/etc/conf/pack.d/bspmpall/Driver.o
/etc/conf/pack.d/bspmtx/Driver.o
/etc/conf/pack.d/dmac/Driver.o
/etc/conf/pack.d/dmac/space.c
/etc/conf/pack.d/dmac/stubs.c
/etc/conf/pack.d/fs/Driver.o
/etc/conf/pack.d/iobus_err/Driver.o
/etc/conf/pack.d/ldterm/Driver.o
/etc/conf/pack.d/proc/Driver.o
/etc/conf/pack.d/rtserial/Driver.o
/etc/conf/pack.d/sbc/stubs.c
/etc/conf/pack.d/serial/Driver.o
/etc/conf/pack.d/svc/Driver.o
/etc/conf/pack.d/xfs/Driver.o
/etc/conf/sdevice.d/dmac
/stand/cp1
/usr/include/sys/dmac.h
/usr/include/sys/fcntl.h
/usr/include/sys/ipl.h
/usr/lib/libnsl_i.a
/usr/lib/libsocket.so
/usr/lib/libud.a
/usr/lib/libud.so
Special Conditions for Installation:
NOTICE #1: The changes to libud and <sys/ipl.h> for Problem #3 should
be installed on systems where multi-threaded applications
call spl_request(3X) or spl_manage(3X) from program level
threads and also from a user-level interrupt routine.
NOTICE #2: Systems which have installed the beta test (preliminary)
"dmac" package, should remove the package prior to
installation of this update. To remove the "dmac" package,
execute the following command (as root):
# /usr/sbin/pkgrm dmac
NOTICE #3: The dmac driver is not compatible with the latest release
of the cluster package software, therefore, it is installed
in the disabled state. If your system is configured with
the cluster pkg software, you must install patch cluster-004,
also on this tape, in order to use the dmac driver. If your
system is not configured with the cluster pkg software, then
you may enable the driver by editing the file 'dmac' under
the kernel configuration directory /etc/conf/sdevice.d and
substitute the 'N' for 'Y' before building a new unix kernel
using the idbuild(1M) command.
NOTICE #4: The following objects are linked to some of the objects being
replaced by this patch. These objects will also be re-linked:
/usr/lib/libnsl.a
/usr/lib/libxti.a
/usr/lib/libsocket.a
NOTICE #5: This patch modifies /etc/conf/cf.d/intr.s. If this file has
been modified locally, then those local changes will need to
be re-applied after the patch is installed.
NOTICE #6: During installation of base-008, an updated version of
/stand/cp1 will be installed and the new console overlay will
be written to partition 6 on the system disk. Following
successful installation, the system must be taken down and
reset to load the new console before rebooting. Failure to
do so may result in unexpected or unreliable behavior.
Possible Side Effects:
If the base-008 package is removed (pkgrm(1M)), the original console
will be re-written to partition 6 on the system disk. To ensure there
are no adverse side effects, the kernel should be rebuilt (idbuild(1M))
and the system taken down and reset to load the original console before
rebooting the system.
Suggested procedure for removing base-008:
# pkgrm base-008
# /etc/conf/bin/idbuild -B
# sync
# init 0
# Reset system
Follow the normal boot procedure detailed in the PowerMAX OS Product
Release Notes to load the new console and boot the new kernel.
return to index
================================================================================
Concurrent Computer Corporation Software Development
Software Patch Report
Patch Name: base-009
Date Issued: 08/12/98 10:09:43
Software Package: base pkg (Version 4.2)
OS Release: PowerMAX OS 4.2
Architectures: nh
Platforms: Night Hawk 6200/6800, TurboHawk, PowerMAXION
Related Patches: nfs-002, crypt-001, inet-005, crosslibs-002, mvc (4.2.1)
Related SARS: HM12246, HM12322, HM12331, HM12396,
HM12413, HM12429, HM12430
Brief Description:
PowerMAX OS 4.2 base package release updates
Problem Description:
1. XFS file system loses file space that is reclaimed after remounting
The problem is associated with two kinds of temporary files:
(a) files that have been created then unlinked before being
written to;
(b) files that have been mmap'ed and subsequently removed.
Creating large temporary files of type (a) or (b) with indirect
blocks results in progressive loss of file space until the file
system becomes full. Rebooting or unmounting and remounting the
file system will reclaim all the file space lost in this way.
2. Multi-threaded applications that use user-level interrupts and
spl_request(3X) or spl_manage(3X) may hang the system.
The spl_request(3X) and spl_manage(3X) library routines lock an
internal lwp mutex lock while reading and writing the ipl value.
If this internal lock is currently locked from a thread calling
spl_request(3X)/spl_manage(3X) at program level when a user-level
interrupt routine becomes active, then a spl_request(3X) or
spl_manage(3X) call that is made from the user-level interrupt
routine will be unable to get the internal lwp mutex lock, and the
routine will spin forever at interrupt level, attempting to acquire
the lock.
3. There is currently no way for a user application to get the current
ipl level.
It is not possible to get the current ipl level without also
setting the ipl level with the spl_request(3X) or spl_manage(3X)
routines.
4. HM12322: PPC Time Base Register constants for Power Hawk 620/640 and
PowerStack II in the _hair routines of libud (also known as
TIE_FREQ_RATE) are incorrect. Because the values are incorrect for
the bus clock rating for Power Hawk 620/640 and PowerStack II
architectures, time stamps from programs that link libud could be
erroneous.
5. HM12246, HM12396: Modification of ldterm, serial, rtserial and
idmknod are required for new mvc driver.
6. HM12413: Several problems with lockd (nfs lock manager):
(a) Locks held by a client that crashes are not properly
recovered. This may result in incorrect file locks that
are never released.
(b) In some cases, when a process on a client system blocks
waiting for a lock, it would not get woken up after the
lock was released.
(c) There is a long time period between the reboot of a system
and its detection on the server.
7. HM12429: Some of the socket library routines may permanently set the
user's signal disposition of SIGPOLL to SIG_IGN (ignore the signal).
Some of the socket library routines may internally change the user's
signal disposition of SIGPOLL to SIG_IGN (ignore the signal) and
never change it back to its original disposition.
This problem will occur when these routines are called while the
SIGPOLL signal is currently being held/masked in the calling LWP's
signal mask.
8. HM12430: On XFS file systems, unlink(2) of a directory should not be
allowed if directory is not empty.
A problem in the check code of the directory unlink function did not
prevent a root user unlinking a non-empty directory. This results
in the directory content being removed from the file system but the
filespace allocated to the directory content not being released.
9. XFS file system: Stale File Handle errors on LCS targets with xfs
virtual root.
A timing window in the xfs_vget function used by NFS to attach to
file system nodes resulted in stale file handle errors when the NFS
was used over a very fast network link.
10. XFS file system: xfs_badop panic with xfs host file system and
Hummingbird NFS client and attempt to remove a file on the client
without required permissions.
A NFS protocol error in the Hummingbird client resulted in the
activation of a diagnostic panic when the client attempted an
invalid operation (VOP_LOOKUP on a file).
11. HM12331: User level interrupts connected to devices in TurboHawk
secondary I/O did not work.
12. On TurboHawks, mpadvise(3C) issued with the 'command' argument of
MPA_CPU_VMELEV, the 'which' argument of MPA_VMELEV_SECONDARY and the
'who' argument specifying a secondary VME level 1-7 did not correctly
define the CPU that services the interrupt.
13. On TurboHawks, in the low level interrupt handler, the VME level
acquired from the IACK of the interrupt controller WAS being written
to the stack frame at location EF_VECT*4. This prevented ktrace
from discerning between VME multiple devices interrupting on the same
VME level.
14. The generic kernel (/stand/unix.generic) originally released with
PowerMAX OS 4.2 does not boot on TurboHawk systems with three and
five position frontplanes.
15. Under certain conditions, a program that modifies its scheduling
class may end up panicing the system with the message:
"XX scheduling class deferred a parameter change"
16. When either IGNORE_BUS_TIMEOUTS or IGNORE_SYSFAIL is enabled, then
the iobus_err(2) will return ENOSYS since the iobus_err(2) support
is not compatible with ignoring bus timeouts.
17. The utility intstat reports erroneous values for the CPU IDs that
VME interrupts are assigned to. The values are bad on PowerMAXION
and TurboHawk systems.
18. On TurboHawks, Secondary VME interrupts could not be routed off of
the first processor board to the frontplane for handling by
processors on other processor boards.
Problem Resolution:
1. Fix xfs kernel code so that the indirect blocks are correctly
marked as free in the in-memory free space maps when a temporary
file is removed.
2. The lwp mutex lock is not required by the spl_request(3X) and
spl_manage(3X) routines. Therefore, this lock will no longer be
used by these two routines.
3. Add a new spl_value(3X) routine to libud that simply returns the
current ipl (architecture dependent) ipl level:
pl_t spl_value(caddr_t spl_map_address);
Where 'spl_map_address' is the address that was returned from a
previous spl_map(3X) call.
4. Modified the TIE_FREQ_RATE value returned by _hair_get_arch_info()
to be consistent with the bus clock rating for the Power Hawk
620/640 and PowerStack II architectures.
5. A new release (4.2.1) of the mvc package is replacing the 4.2
version, to provide new features (including rtserial device support)
and improved performance and reliability. Small problems in the
aforementioned I/O modules were found and corrected during
development and test of the new driver.
Additionally, idmknod(1M) did not permit a single line in a node
file to define both tty ports and printer ports, as the structure
of the new driver requires. All of the idtools have been updated
as a result of these changes.
6. lockd problems resolved as follows:
(a) Upon detecting that a client has crashed (and rebooted),
the server will clear ALL locks held by that client.
(b) Add a small delay in the kernel code that re-requests a
lock via the local lockd. This allows other messages to be
received.
(c) Shorten the initial start-up delay in statd from 15 to 5
seconds.
7. Change the appropriate libsocket routines so that they do not change
the process's signal disposition for the SIGPOLL signal.
See related patches inet-005 and crypt-001.
8. Add extra check to unlink directory code path.
9. Change xfs_vget node lookup to avoid the window.
10. Conditional compile the diagnostic panic, release code now just
returns error.
11. Modified svme_intr(), the secondary vme interrupt handler for
PowerMAXIONs and TurboHawks, so that the vector and the exception
frame pointer are passed to the handler. These items are required by
the user level interrupt handler, Xuserint.
12. A kernel routine, getbuslvl_nh6800t(), that is called by mpadvise()
was fixed to return the correct mask of CPUs that service a specified
local secondary VME level on TurboHawks.
13. On TurboHawks, the low level interrupt handler, Xintr, was modified
so that the vector presented by the VME device is written to the
exception stack frame.
14. Rebuilt unix.generic to include changes from previous PowerMAX OS 4.2
patches to add specified TurboHawk support.
15. Conditions for this to occur are for a parent process to change its
class and then change it back and THEN spawn a new process or lwp.
The new lwp/process would attempt to process the new scheduling class
change but there wouldn't be one present. Fixed to account for this
condition (i.e. NULL deferred scheduling class changes).
16. Change the way that the kernel handles bus timeouts so that the
iobus_err(2) processing still functions properly even when
IGNORE_BUS_TIMEOUTS and IGNORE_SYSFAIL are enabled.
17. The program invokes syscx(2) to return the CPU assignment for VME
interrupts. However, it incorrectly treats this as a CPU mask when
it is actually a CPU number.
18. On TurboHawks, Secondary VME interrupts can now be routed off the
first processor board using system tunables. These interrupts can
now be serviced by processors on boards other than the first
processor boards.
Object To Be Replaced:
/etc/conf/bin/idcheck
/etc/conf/bin/idconfig
/etc/conf/bin/idinstall
/etc/conf/bin/idmknod
/etc/conf/bin/idmodload
/etc/conf/bin/idreadauto
/etc/conf/cf.d/intr.s
/etc/conf/pack.d/bsp6400/Driver.o
/etc/conf/pack.d/bsp6408/Driver.o
/etc/conf/pack.d/bsp6800/Driver.o
/etc/conf/pack.d/bsp6800t/Driver.o
/etc/conf/pack.d/bspall/Driver.o
/etc/conf/pack.d/fs/Driver.o
/etc/conf/pack.d/iobus_err/Driver.o
/etc/conf/pack.d/ldterm/Driver.o
/etc/conf/pack.d/proc/Driver.o
/etc/conf/pack.d/rtserial/Driver.o
/etc/conf/pack.d/serial/Driver.o
/etc/conf/pack.d/svc/Driver.o
/etc/conf/pack.d/vme/Driver.o
/etc/conf/pack.d/xfs/Driver.o
/stand/unix.generic
/usr/bin/intstat
/usr/include/sys/fcntl.h
/usr/include/sys/ipl.h
/usr/lib/libnsl_i.a
/usr/lib/libsocket.so
/usr/lib/libud.a
/usr/lib/libud.so
Special Conditions for Installation:
NOTICE #1: The changes to libud and <sys/ipl.h> for Problem #3 should
be installed on systems where multi-threaded applications
call spl_request(3X) or spl_manage(3X) from program level
threads and also from a user-level interrupt routine.
NOTICE #2: The following objects are linked to some of the objects being
replaced by this patch. These objects will also be re-linked:
/usr/lib/libnsl.a
/usr/lib/libxti.a
/usr/lib/libsocket.a
Possible Side Effects:
None.
return to index
================================================================================
Concurrent Computer Corporation Software Development
Software Patch Report
Patch Name: base-010
Date Issued: 09/23/98 08:43:28
Software Package: base pkg (Version 4.2)
OS Release: PowerMAX OS 4.2
Architectures: moto
Platforms: Power Hawk 610/620, PowerStack, PowerStack II (uni-proc)
Related Patches: none
Related SARS: none
Brief Description:
PowerMAX OS 4.2 base package release updates
Problem Description:
1. Systems may 'hang' during boot-up. Possible symptoms include:
* The system stops after the following is printed on the
console:
PowerMAX OS Boot Loader
Boot
: /stand/unix
2675544+296695+505253 start 0x4000
symbol table loaded
other information is printed.
* The system cannot be aborted (using the 'abort' switch).
* The hang does not always occur. The system may boot once
out of ten times -or- may only fail once out of ten times.
Some systems may not see the hang at all.
* The hang is more prevalent on systems with base-007 patch
installed. The hang is more prevalent when kernel symbol
table is loaded.
Problem Resolution:
1. Correct a cache flush operation so that no memory operations are done
while the flush is in progress.
Object To Be Replaced:
/etc/conf/pack.d/bsp2600/Driver.o
/etc/conf/pack.d/bspmtx/Driver.o
/etc/conf/pack.d/bspall/Driver.o
/etc/conf/pack.d/io/Driver.o
Special Conditions for Installation:
None.
Possible Side Effects:
None.
return to index
================================================================================
Concurrent Computer Corporation Software Development
Software Patch Report
Patch Name: base-011
Date Issued: 09/23/98 08:45:21
Software Package: base pkg (Version 4.2)
OS Release: PowerMAX OS 4.2
Architectures: moto
Platforms: Power Hawk 640, PowerStack II (multi-proc)
Related Patches: none
Related SARS: none
Brief Description:
PowerMAX OS 4.2 base package release updates
Problem Description:
1. Systems may 'hang' during boot-up. Possible symptoms include:
* The system stops after the following is printed on the
console:
PowerMAX OS Boot Loader
Boot
: /stand/unix
2675544+296695+505253 start 0x4000
symbol table loaded
other information is printed.
* The system cannot be aborted (using the 'abort' switch).
* The hang does not always occur. The system may boot once
out of ten times -or- may only fail once out of ten times.
Some systems may not see the hang at all.
* The hang is more prevalent on systems with base-008 patch
installed. The hang is more prevalent when kernel symbol
table is loaded.
Problem Resolution:
1. Correct a cache flush operation so that no memory operations are done
while the flush is in progress.
Object To Be Replaced:
/etc/conf/pack.d/bsp4600/Driver.o
/etc/conf/pack.d/bspmtx/Driver.o
/etc/conf/pack.d/bspmpall/Driver.o
/etc/conf/pack.d/io/Driver.o
Special Conditions for Installation:
None.
Possible Side Effects:
None.
return to index
================================================================================
Concurrent Computer Corporation Software Development
Software Patch Report
Patch Name: base-013
Date Issued: 09/30/98 08:04:17
Software Package: base pkg (Version 4.2)
OS Release: PowerMAX OS 4.2
Architectures: moto
Platforms: Power Hawk 610/620, PowerStack, PowerStack II (uni-proc)
Related Patches: audit-001, cluster-005, cmds-002, crosslibs-003,
crypt-002, crypt-int-001, dec-007, inet-006, man-004,
ncr-002, via-001, zld-002, cld (4.2), fibre (4.2),
netboot (4.2)
Related SARS: HM12415, HM12357, HM12462
Brief Description:
PowerMAX OS 4.2 base package release updates
Problem Description:
1. iconnect(3C) ICON_IVEC II_ALLOCATE calls may always return EBUSY.
If an interrupt vector is allocated with an iconnect(3C) ICON_IVEC
II_ALLOCATE call, and a LWP makes an ienable(3C) call to connect to
that vector, and another LWP later disconnects that ienabled LWP with
a iconnect(3C) ICON_DISC call, then that allocated interrupt vector
will be improperly marked free in the kernel's interrupt vector
table, even though the kernel's user-level interrupt data structures
will properly indicate that this vector is still ICON_IVEC allocated.
All subsequent iconnect(3C) ICON_IVEC II_ALLOCATE calls without the
vector specified (where the II_VECSPEC flag is not set) will result
in EBUSY being returned, instead of having a vector successfully
allocated.
2. Rommable PowerMAX OS support added:
Added random access decompression library support (radl) to the
kernel, plus tunable and stub file to enable or disable. This
library must be enabled for all diskless configurations of
PowerMAX OS. For all other configurations, it may be enable or
disabled. By default radl is disabled for all platforms, since by
default most platforms have a true disk for root. The various
diskless build packages (netboot, cluster) automatically turn this on
for the affected targets or clients as appropriate. Hence it is
expected there will be little need to explicitly turn this
configuration tunable on or off.
Added a random access compressor which produces compressed images
suitable for use by the above random access decompression library.
This compressor is both upwards and downwards compatible with gzip.
3. Enhancements to to the memfs kernel module to support booting from
a Flash Memory Device, a new feature added to the cluster and netboot
software packages.
4. The fast boot logic does not properly detect that the file systems
are dirty during a system boot if the following condition occurs:
A) a boot and then a "clean" shutdown of a kernel that has the
FASTFS tunable SET
B) boot and then a "non-clean" shutdown of a kernel that has
the FASTFS tunable RESET
C) boot of a kernel that has the FASTFS tunable SET
The kernel in step A) would leave the dirty/clean flag set to clean.
If the kernel in step B) shutdown without going through a clean
shutdown, the dirty/clean flag would not get reset to dirty. Finally,
the kernel in step C) would see the flag as clean and would attempt
to boot without running fsck on the dirty file systems.
5. Added NVRAM Global Environment Variable (GEV) support for the
Motorola platforms. PPCBug Revisions 1.8 and later provide support
for GEVs which reside in the PowerPC Reference Platform (PRP) region
of the NVRAM on the CPU board. PPCBug allows the OS access to share
this area. GEVs can still be used by the OS with an older revision of
PPCBug, but there will be no PPCBug commands to access them, and the
GEV area may need to be initialized by the OS.
The new nvram(2) system call and the gev(1) set of commands (gevdel,
gevdump, gevget, gevgetval, gevinfo, gevinit, gevput, gevputval,
and gevshow) provide services that allow you to add, delete, replace,
initialize and get information about one or more GEV entries.
The GEV area within the NVRAM is an array of null terminated strings.
These strings have the form:
name=[value]
At the present time there is no support for GEVs on nh platforms.
The nvram system call always returns ENOSYS on nh platforms and the
gev set of commands are not present.
6. HM12415: Add Symbios 53c875/895 high performance modes enhancements
and support for removable media Magneto-Optical Drives.
* Support ncr (Symbios) 53c875/895 high performance modes.
* Need enhancements to support removable media disks and 1K
sector size.
* SCSI ULTRA requires fewer devices on shorter cabling than
FAST/WIDE.
* Optical media change not protected against change in
geometry block.
* Raw disk transfers greater than 128K not supported.
* Some SCSI devices will reconnect, then immediately
disconnect without doing anything.
7. XFS files do not have microsecond resolution update times set. XFS
fails to correctly set the tv_usec subfield of the file access,
modification or changed timeval structures. The tv_sec subfield
returned by the standard stat system call is correctly set, only the
extended stat (xstat) system call shows this problem.
8. When xdm is used to manage a host based X server process, shutdown
processing that kills all processing can lead to a race condition
wherein an X server process will be killed by shutdown, but before
xdm itself is killed, a new X server process is launched. Depending
on how far this this process gets before it is killed itself, the
video hardware may not be restored to VGA compatible mode. When this
happens, the display is corrupted, and the system appears to be hung.
9. Certain logitech serial mouse devices are not always detected and
initialized properly by the smse STREAMs module. Mouse detection
state machine in smse was easily confused because timeouts were too
short and certain early exits could be taken.
10. PCI drivers multi-function device and BIT-3 bridge support required
to correct certain deficiencies in kernel PCI drivers including:
* No support for multi-function PCI devices
* PCI bridge depth limited to 2 bridges. BIT-3 PCI expansion
chassis requires depth 3.
* Default tunable values for PCI bridges are not appropriate
for all architectures.
11. Serial keyboard STREAM module did not support Concurrent's own
serial kbd.
12. HM12357, HM12462: When the top(1) command is run on a system that
has more than six (6) processors configured, it will fail with a
segmentation violation and dump core. The problem is that the memory
allocated for memory usage display is only 80 characters in length.
This allocation is used up when more than 6 CPUs are configured.
13. According to POSIX, a process whose priority is lowered goes to the
end of its new priority run queue. Thus, if there are other
processes already in that queue, the lowered LWP must give up the
CPU immediately to them and wait its turn. This was not happening.
Instead, the running LWP would continue to run until it either
voluntarily gave up the CPU, or some other event, such as I/O
completion, caused the CPU to re-evaluate which LWP was supposed to
be running.
14. Date written to or read from Time Of Century Clock is mishandled.
If the system time is changed to certain dates in the 21st century,
the date written to the hardware Time Of Century Clock is mishandled.
On a subsequent system reboot, the system time is set wrong because
the date read from the hardware Time Of Century Clock is incorrect.
15. Support required for the Interphase 5526 PCI Fibre Channel Adapter.
16. The fast boot dirty/clean flag is in a Motorola reserved location
within the header of the NVRAM PRP area. Changes by Motorola in the
future could overwrite this flag causing the kernel to misinterpret
the dirty/clean status flag during system initialization.
17. The PCI bridge chipset (aka Raven) used on the PowerHawk 620/640 and
PowerStack II has a write posting control bit for each slave window
that allows the processor to continue before PCI writes have been
acknowledged. Prior to this change, this control bit is always off,
thereby disabling the posting of PCI writes.
Detailed problem resolution:
1. The fix is to re-implement the way that interrupt vectors are restored
in the kernel's interrupt vector table when a iconnect(3C) ICON_DISC
disconnection occurs, so that the proper vector value is placed into
the interrupt vector table entry.
2. Implemented as detailed above.
3. Modifications to the memfs kernel moduled made to support booting
from a Flash Memory Device.
4. The fast boot logic was changed to always set the dirty/clean flag to
dirty during system initialization, whether or not the FASTFS tunable
is set for the kernel. Previously, the dirty/clean flag was set to
dirty during system initialization only when the FASTFS tunable was
set. The dirty/clean flag will now be left set to dirty if the system
does not shutdown cleanly, irregardless of how FASTFS is set. This
insures that the next kernel that boots will never see the file
systems as clean when the previous kernel went down dirty.
6. Problems resolved as follows:
* Add ULTRA-2 (LVD) controller support (Symbios 53c895) to ncr
driver.
* Added special SCSI Script instructions to reset 53c875 cache
line alignment mechanism on each PCI dma block move. Added
high performance mode configuration. Added FIFO flush logic
to completion and disconnect. Added NCR_BURST_SZ tunable
to allow multiple dma cache line bursts per PCI bus tenure.
* Changed generic disk driver (gd) to support 1K sector
format, media missing at boot, media change, and disk
geometry change with media change (including new partition
layout). Added check for true block size in via driver.
* Added NCR_875_MAX_SYNC system tunable allow running more
drives on a longer cable by tuning the 53c875 to FAST/WIDE
speeds.
* Added PHYSIO_MAXTRNSFR system tunable to allow up to 512K
raw transfers for ncr (via and hsa not supported).
7. Change the xfs file time update code to set both subfields of the
access, modification or changed timeval structures.
8. xdm needs some help to know when a shutdown is occuring so that
attempts to re-launch the X server can be avoided. Once committed to
shutting down the system, the shutdown script now creates a file
/var/NOLOGIN as a signal that a shutdown is in progress. This file
is removed by rc1 and rc2 startup scripts when booting or restarting.
9. Smse timeouts have been lengthened and the state machine code made
more robust.
10. Numerous enhancements to PCI support including:
* Support added for doing configuration accesses of
multi-function PCI devices.
* PCI bridge depths up to four now supported, including last
four expansion slots of the BIT3 PCI expansion chassis.
* PCI bridge I/O and memory range tunables expanded and
architecture specific tunables (defaults) were added.
11. Replace AT2Serial converter box support in skbd STREAMS module with
support for Concurrent's own serial keyboard.
12. The top(1) command has been modified to allow a larger memory
allocation for the memory usage display. This fix also resulted in a
small change to the top(1) manpage, corrected in patch man-004.
13. The cause was the failure of the priocntl system call to nudge the
CPU after changing the LWP's priority (i.e., failed to force the CPU
to re-evaluate which LWP it was supposed to run). The LWP was
actually put at the end of its new run queue as it should have been,
but without the nudge the CPU did not notice the changed
circumstances of the LWP.
The solution was to expand the `if' statement that does nudging in
priocntl(2) to nudge if the new priority run queue was not empty
prior to the insertion.
14. The kernel now writes the correct date to the hardware Time Of
Century Clock when the system time is changed, thereby ensuring the
system time is correctly set upon system reboot.
15. This patch adds the required base system support for the Interphase
5526 PCI Fibre Channel Adapter card. The actual Fibre Channel kernel
driver and required utilities are included in the "fibre" software
package.
16. Moved the location of the fast boot dirty/clean flag from 0x0010 to
0x1200 within the NVRAM. This moves it out of the PRP header area.
The size of the flag was changed from 1 byte to 4 bytes. If the file
systems shutdown cleanly, the flag will now be set to 0x4f4b4159
(instead of 0x1). These changes will insure that the dirty/clean flag
cannot be misinterpreted by the kernel.
17. Set the write post enable bit for the slave window used for PCI
memory accesses.
Object To Be Replaced:
/etc/conf/mdevice.d/radl
/etc/conf/mtune.d/gd
/etc/conf/mtune.d/io
/etc/conf/mtune.d/memfs
/etc/conf/mtune.d/pci
/etc/conf/pack.d/bsp2600/Driver.o
/etc/conf/pack.d/bspall/Driver.o
/etc/conf/pack.d/bspmtx/Driver.o
/etc/conf/pack.d/cons/Driver.o
/etc/conf/pack.d/gd/Driver.o
/etc/conf/pack.d/gd/space.c
/etc/conf/pack.d/io/Driver.o
/etc/conf/pack.d/io/space.c
/etc/conf/pack.d/memfs/Driver.o
/etc/conf/pack.d/memfs/space.c
/etc/conf/pack.d/pci/Driver.o
/etc/conf/pack.d/pci/space.c
/etc/conf/pack.d/proc/Driver.o
/etc/conf/pack.d/radl/Driver.o
/etc/conf/pack.d/radl/stubs.c
/etc/conf/pack.d/scsi/Driver.o
/etc/conf/pack.d/skbd/Driver.o
/etc/conf/pack.d/skbd/space.c
/etc/conf/pack.d/smse/Driver.o
/etc/conf/pack.d/svc/Driver.o
/etc/conf/pack.d/ui/Driver.o
/etc/conf/pack.d/xfs/Driver.o
/etc/conf/sdevice.d/radl
/etc/conf/sdevice.d/skbd
/usr/bin/gev
/usr/bin/rac
/usr/bin/top
/usr/ccs/lib/libc.a
/usr/ccs/lib/libc.so
/usr/include/libc_synonyms.h
/usr/include/sys/adapter.h
/usr/include/sys/iconnect.h
/usr/include/sys/im.h
/usr/include/sys/in82378.h
/usr/include/sys/gd.h
/usr/include/sys/nvram.h
/usr/include/sys/pci.h
/usr/include/sys/pci_p.h
/usr/include/sys/pci_info.h
/usr/include/sys/racfile.h
/usr/include/sys/radl.h
/usr/include/sys/ravenmpic.h
/usr/include/sys/scsi.h
/usr/include/sys/skbd.h
/usr/include/sys/syscall.h
/usr/include/sys/fs/memfs_mnode.h
/usr/include/sys/fs/memfs.h
/usr/lib/libnsl_i.a
/usr/lib/libnsl_i.so
/usr/lib/libc.so.1
/usr/lib/libcmd.a
/usr/lib/libud.so
/usr/lib/libud.a
/usr/lib/locale/C/MSGFILES/core.abi.str
/usr/lib/locale/C/MSGFILES/harris.str
/sbin/rc0
/sbin/rc1
/sbin/rc2
/sbin/shutdown
/sbin/wsinit
/sbin/format
/sbin/bcheckrc
Special Conditions for Installation:
NOTICE #1: The PCI Fibre channel adapter is supported only on PowerStack
and PowerStack II (single and multi-processor) platforms.
NOTICE #2: You must insure that the configuration parameters for the
PPCBug NIOT command are not stored in NVRAM locations 0x1200
to 0x12ff on your system. The default location of the NIOT
configuration parameters is 0x1000 and they are 256 (0x100)
bytes in length. To check the location of the NIOT
configuration parameters on your system, use the PPCBug ENV
command to examine the "Network Auto Boot Configuration
Parameters Offset (NVRAM) = 00001000". If any part of the
NIOT configuration parameters area overlaps locations 0x1200
to 0x12ff, you MUST change the location of the NIOT
configuration parameters using the PPCBug ENV command.
NOTICE #3: The following links will also be created during installation
of base-013:
* Link to /usr/bin/gev
/usr/bin/gevdel
/usr/bin/gevdump
/usr/bin/gevget
/usr/bin/gevgetval
/usr/bin/gevinfo
/usr/bin/gevinit
/usr/bin/gevput
/usr/bin/gevputval
/usr/bin/gevshow
* Link to /usr/lib/libnsl_i.a
/usr/lib/libnsl.a
/usr/lib/libxti.a
/usr/lib/libsocket.a
* Link to /usr/lib/libnsl_i.a
/usr/lib/libnsl.so
/usr/lib/libxti.so
* Link to /usr/ccs/lib/libc.so
/usr/ccs/lib/libp/libc.so
Possible Side Effects:
NOTICE #1: The file systems will appear to have gone down dirty the
first time a kernel with this change is booted (even if the
previous kernel shutdown cleanly). This occurs because it
takes one boot sequence to initialize the new dirty/clean
flag location.
The fast boot logic may not accurately detect the state of
the file systems if you switch back and forth between a
kernel that does not have this change, and a kernel that has
this change.
NOTICE #2: Tunable parameters that control position and size of I/O and
memory windows on secondary PCI buses have been changed.
Sites that have locally defined any of the the old PCIx_MEM_*
or PCIx_IO_* tunable values will need to convert these to the
equivalent PCIx_MEM* or PCIx_IO* values.
DO NOT SIMPLY SUBSITITUTE THESE OLD TUNABLE VALUES FOR THE
CORRESPONDING NEW PARAMETER BECAUSE THE MEANINGS OF THESE
PARAMETERS ARE DIFFERENT. FAILURE TO DO SO MAY RESULT IN
UNEXPECTED OR UNRELIABLE BEHAVIOR.
Instead, read the descriptions of the new tunable parameters
closely, and supply a new value only if necessary for your
configuration. The default values provided should work for
most common configurations.
return to index
================================================================================
Concurrent Computer Corporation Software Development
Software Patch Report
Patch Name: base-014
Date Issued: 09/30/98 08:31:03
Software Package: base pkg (Version 4.2)
OS Release: PowerMAX OS 4.2
Architectures: moto
Platforms: Power Hawk 640, PowerStack II (multi-proc)
Related Patches: audit-001, cluster-005, cmds-002, crosslibs-003,
crypt-002, crypt-int-001, dec-007, inet-006, man-004,
ncr-002, via-001, zld-002, cld (4.2), fibre (4.2),
netboot (4.2)
Related SARS: HM12415, HM12357, HM12462, HM12322
Brief Description:
PowerMAX OS 4.2 base package release updates
Problem Description:
1. iconnect(3C) ICON_IVEC II_ALLOCATE calls may always return EBUSY.
If an interrupt vector is allocated with an iconnect(3C) ICON_IVEC
II_ALLOCATE call, and a LWP makes an ienable(3C) call to connect to
that vector, and another LWP later disconnects that ienabled LWP with
a iconnect(3C) ICON_DISC call, then that allocated interrupt vector
will be improperly marked free in the kernel's interrupt vector
table, even though the kernel's user-level interrupt data structures
will properly indicate that this vector is still ICON_IVEC allocated.
All subsequent iconnect(3C) ICON_IVEC II_ALLOCATE calls without the
vector specified (where the II_VECSPEC flag is not set) will result
in EBUSY being returned, instead of having a vector successfully
allocated.
2. Rommable PowerMAX OS support added:
Added random access decompression library support (radl) to the
kernel, plus tunable and stub file to enable or disable. This
library must be enabled for all diskless configurations of
PowerMAX OS. For all other configurations, it may be enable or
disabled. By default radl is disabled for all platforms, since by
default most platforms have a true disk for root. The various
diskless build packages (netboot, cluster) automatically turn this on
for the affected targets or clients as appropriate. Hence it is
expected there will be little need to explicitly turn this
configuration tunable on or off.
Added a random access compressor which produces compressed images
suitable for use by the above random access decompression library.
This compressor is both upwards and downwards compatible with gzip.
3. Enhancements to to the memfs kernel module to support booting from
a Flash Memory Device, a new feature added to the cluster and netboot
software packages.
4. The fast boot logic does not properly detect that the file systems
are dirty during a system boot if the following condition occurs:
A) a boot and then a "clean" shutdown of a kernel that has the
FASTFS tunable SET
B) boot and then a "non-clean" shutdown of a kernel that has
the FASTFS tunable RESET
C) boot of a kernel that has the FASTFS tunable SET
The kernel in step A) would leave the dirty/clean flag set to clean.
If the kernel in step B) shutdown without going through a clean
shutdown, the dirty/clean flag would not get reset to dirty. Finally,
the kernel in step C) would see the flag as clean and would attempt
to boot without running fsck on the dirty file systems.
5. Added NVRAM Global Environment Variable (GEV) support for the
Motorola platforms. PPCBug Revisions 1.8 and later provide support
for GEVs which reside in the PowerPC Reference Platform (PRP) region
of the NVRAM on the CPU board. PPCBug allows the OS access to share
this area. GEVs can still be used by the OS with an older revision of
PPCBug, but there will be no PPCBug commands to access them, and the
GEV area may need to be initialized by the OS.
The new nvram(2) system call and the gev(1) set of commands (gevdel,
gevdump, gevget, gevgetval, gevinfo, gevinit, gevput, gevputval,
and gevshow) provide services that allow you to add, delete, replace,
initialize and get information about one or more GEV entries.
The GEV area within the NVRAM is an array of null terminated strings.
These strings have the form:
name=[value]
At the present time there is no support for GEVs on nh platforms.
The nvram system call always returns ENOSYS on nh platforms and the
gev set of commands are not present.
6. HM12415: Add Symbios 53c875/895 high performance modes enhancements
and support for removable media Magneto-Optical Drives.
* Support ncr (Symbios) 53c875/895 high performance modes.
* Need enhancements to support removable media disks and 1K
sector size.
* SCSI ULTRA requires fewer devices on shorter cabling than
FAST/WIDE.
* Optical media change not protected against change in
geometry block.
* Raw disk transfers greater than 128K not supported.
* Some SCSI devices will reconnect, then immediately
disconnect without doing anything.
7. XFS files do not have microsecond resolution update times set. XFS
fails to correctly set the tv_usec subfield of the file access,
modification or changed timeval structures. The tv_sec subfield
returned by the standard stat system call is correctly set, only the
extended stat (xstat) system call shows this problem.
8. When xdm is used to manage a host based X server process, shutdown
processing that kills all processing can lead to a race condition
wherein an X server process will be killed by shutdown, but before
xdm itself is killed, a new X server process is launched. Depending
on how far this this process gets before it is killed itself, the
video hardware may not be restored to VGA compatible mode. When this
happens, the display is corrupted, and the system appears to be hung.
9. Certain logitech serial mouse devices are not always detected and
initialized properly by the smse STREAMs module. Mouse detection
state machine in smse was easily confused because timeouts were too
short and certain early exits could be taken.
10. PCI drivers multi-function device and BIT-3 bridge support required
to correct certain deficiencies in kernel PCI drivers including:
* No support for multi-function PCI devices
* PCI bridge depth limited to 2 bridges. BIT-3 PCI expansion
chassis requires depth 3.
* Default tunable values for PCI bridges are not appropriate
for all architectures.
11. Serial keyboard STREAM module did not support Concurrent's own
serial kbd.
12. HM12357, HM12462: When the top(1) command is run on a system that
has more than six (6) processors configured, it will fail with a
segmentation violation and dump core. The problem is that the memory
allocated for memory usage display is only 80 characters in length.
This allocation is used up when more than 6 CPUs are configured.
13. According to POSIX, a process whose priority is lowered goes to the
end of its new priority run queue. Thus, if there are other
processes already in that queue, the lowered LWP must give up the
CPU immediately to them and wait its turn. This was not happening.
Instead, the running LWP would continue to run until it either
voluntarily gave up the CPU, or some other event, such as I/O
completion, caused the CPU to re-evaluate which LWP was supposed to
be running.
14. Date written to or read from Time Of Century Clock is mishandled.
If the system time is changed to certain dates in the 21st century,
the date written to the hardware Time Of Century Clock is mishandled.
On a subsequent system reboot, the system time is set wrong because
the date read from the hardware Time Of Century Clock is incorrect.
15. Support required for the Interphase 5526 PCI Fibre Channel Adapter.
16. The fast boot dirty/clean flag is in a Motorola reserved location
within the header of the NVRAM PRP area. Changes by Motorola in the
future could overwrite this flag causing the kernel to misinterpret
the dirty/clean status flag during system initialization.
17. The PCI bridge chipset (aka Raven) used on the PowerHawk 620/640 and
PowerStack II has a write posting control bit for each slave window
that allows the processor to continue before PCI writes have been
acknowledged. Prior to this change, this control bit is always off,
thereby disabling the posting of PCI writes.
18. HM12322: Time from gettimeofday() differs with that from
clock_gettime(). When the setting up the 60 Hz interrupt the Raven
chip is mis-programmed leading to a clock drift on the 60 Hz
hardclock of approximately 11 seconds per day.
Problem Resolution:
1. The fix is to re-implement the way that interrupt vectors are restored
in the kernel's interrupt vector table when a iconnect(3C) ICON_DISC
disconnection occurs, so that the proper vector value is placed into
the interrupt vector table entry.
2. Implemented as detailed above.
3. Modifications to the memfs kernel moduled made to support booting
from a Flash Memory Device.
4. The fast boot logic was changed to always set the dirty/clean flag to
dirty during system initialization, whether or not the FASTFS tunable
is set for the kernel. Previously, the dirty/clean flag was set to
dirty during system initialization only when the FASTFS tunable was
set. The dirty/clean flag will now be left set to dirty if the system
does not shutdown cleanly, irregardless of how FASTFS is set. This
insures that the next kernel that boots will never see the file
systems as clean when the previous kernel went down dirty.
6. Problems resolved as follows:
* Add ULTRA-2 (LVD) controller support (Symbios 53c895) to ncr
driver.
* Added special SCSI Script instructions to reset 53c875 cache
line alignment mechanism on each PCI dma block move. Added
high performance mode configuration. Added FIFO flush logic
to completion and disconnect. Added NCR_BURST_SZ tunable
to allow multiple dma cache line bursts per PCI bus tenure.
* Changed generic disk driver (gd) to support 1K sector
format, media missing at boot, media change, and disk
geometry change with media change (including new partition
layout). Added check for true block size in via driver.
* Added NCR_875_MAX_SYNC system tunable allow running more
drives on a longer cable by tuning the 53c875 to FAST/WIDE
speeds.
* Added PHYSIO_MAXTRNSFR system tunable to allow up to 512K
raw transfers for ncr (via and hsa not supported).
7. Change the xfs file time update code to set both subfields of the
access, modification or changed timeval structures.
8. xdm needs some help to know when a shutdown is occuring so that
attempts to re-launch the X server can be avoided. Once committed to
shutting down the system, the shutdown script now creates a file
/var/NOLOGIN as a signal that a shutdown is in progress. This file
is removed by rc1 and rc2 startup scripts when booting or restarting.
9. Smse timeouts have been lengthened and the state machine code made
more robust.
10. Numerous enhancements to PCI support including:
* Support added for doing configuration accesses of
multi-function PCI devices.
* PCI bridge depths up to four now supported, including last
four expansion slots of the BIT3 PCI expansion chassis.
* PCI bridge I/O and memory range tunables expanded and
architecture specific tunables (defaults) were added.
11. Replace AT2Serial converter box support in skbd STREAMS module with
support for Concurrent's own serial keyboard.
12. The top(1) command has been modified to allow a larger memory
allocation for the memory usage display. This fix also resulted in a
small change to the top(1) manpage, corrected in patch man-004.
13. The cause was the failure of the priocntl system call to nudge the
CPU after changing the LWP's priority (i.e., failed to force the CPU
to re-evaluate which LWP it was supposed to run). The LWP was
actually put at the end of its new run queue as it should have been,
but without the nudge the CPU did not notice the changed
circumstances of the LWP.
The solution was to expand the `if' statement that does nudging in
priocntl(2) to nudge if the new priority run queue was not empty
prior to the insertion.
14. The kernel now writes the correct date to the hardware Time Of
Century Clock when the system time is changed, thereby ensuring the
system time is correctly set upon system reboot.
15. This patch adds the required base system support for the Interphase
5526 PCI Fibre Channel Adapter card. The actual Fibre Channel kernel
driver and required utilities are included in the "fibre" software
package.
16. Moved the location of the fast boot dirty/clean flag from 0x0010 to
0x1200 within the NVRAM. This moves it out of the PRP header area.
The size of the flag was changed from 1 byte to 4 bytes. If the file
systems shutdown cleanly, the flag will now be set to 0x4f4b4159
(instead of 0x1). These changes will insure that the dirty/clean flag
cannot be misinterpreted by the kernel.
17. Set the write post enable bit for the slave window used for PCI
memory accesses.
18. The calculation used to program the Raven chip is now set to a value
which will be more consistent with the actual Raven Timers frequency
of 8.333333 Mhz.
Object To Be Replaced:
/etc/conf/mdevice.d/radl
/etc/conf/mtune.d/gd
/etc/conf/mtune.d/io
/etc/conf/mtune.d/memfs
/etc/conf/mtune.d/pci
/etc/conf/pack.d/bsp4600/Driver.o
/etc/conf/pack.d/bspmpall/Driver.o
/etc/conf/pack.d/bspmtx/Driver.o
/etc/conf/pack.d/cons/Driver.o
/etc/conf/pack.d/gd/Driver.o
/etc/conf/pack.d/gd/space.c
/etc/conf/pack.d/io/Driver.o
/etc/conf/pack.d/io/space.c
/etc/conf/pack.d/memfs/Driver.o
/etc/conf/pack.d/memfs/space.c
/etc/conf/pack.d/pci/Driver.o
/etc/conf/pack.d/pci/space.c
/etc/conf/pack.d/proc/Driver.o
/etc/conf/pack.d/radl/Driver.o
/etc/conf/pack.d/radl/stubs.c
/etc/conf/pack.d/scsi/Driver.o
/etc/conf/pack.d/skbd/Driver.o
/etc/conf/pack.d/skbd/space.c
/etc/conf/pack.d/smse/Driver.o
/etc/conf/pack.d/svc/Driver.o
/etc/conf/pack.d/ui/Driver.o
/etc/conf/pack.d/xfs/Driver.o
/etc/conf/sdevice.d/radl
/etc/conf/sdevice.d/skbd
/usr/bin/gev
/usr/bin/rac
/usr/bin/top
/usr/ccs/lib/libc.a
/usr/ccs/lib/libc.so
/usr/include/libc_synonyms.h
/usr/include/sys/adapter.h
/usr/include/sys/iconnect.h
/usr/include/sys/im.h
/usr/include/sys/in82378.h
/usr/include/sys/gd.h
/usr/include/sys/nvram.h
/usr/include/sys/pci.h
/usr/include/sys/pci_p.h
/usr/include/sys/pci_info.h
/usr/include/sys/racfile.h
/usr/include/sys/radl.h
/usr/include/sys/ravenmpic.h
/usr/include/sys/scsi.h
/usr/include/sys/skbd.h
/usr/include/sys/syscall.h
/usr/include/sys/fs/memfs_mnode.h
/usr/include/sys/fs/memfs.h
/usr/lib/libnsl_i.a
/usr/lib/libnsl_i.so
/usr/lib/libc.so.1
/usr/lib/libcmd.a
/usr/lib/libud.so
/usr/lib/libud.a
/usr/lib/locale/C/MSGFILES/core.abi.str
/usr/lib/locale/C/MSGFILES/harris.str
/sbin/rc0
/sbin/rc1
/sbin/rc2
/sbin/shutdown
/sbin/wsinit
/sbin/format
/sbin/bcheckrc
Special Conditions for Installation:
NOTICE #1: The PCI Fibre channel adapter is supported only on PowerStack
and PowerStack II (single and multi-processor) platforms.
NOTICE #2: You must insure that the configuration parameters for the
PPCBug NIOT command are not stored in NVRAM locations 0x1200
to 0x12ff on your system. The default location of the NIOT
configuration parameters is 0x1000 and they are 256 (0x100)
bytes in length. To check the location of the NIOT
configuration parameters on your system, use the PPCBug ENV
command to examine the "Network Auto Boot Configuration
Parameters Offset (NVRAM) = 00001000". If any part of the
NIOT configuration parameters area overlaps locations 0x1200
to 0x12ff, you MUST change the location of the NIOT
configuration parameters using the PPCBug ENV command.
NOTICE #3: The following links will also be created during installation
of base-014:
* Link to /usr/bin/gev
/usr/bin/gevdel
/usr/bin/gevdump
/usr/bin/gevget
/usr/bin/gevgetval
/usr/bin/gevinfo
/usr/bin/gevinit
/usr/bin/gevput
/usr/bin/gevputval
/usr/bin/gevshow
* Link to /usr/lib/libnsl_i.a
/usr/lib/libnsl.a
/usr/lib/libxti.a
/usr/lib/libsocket.a
* Link to /usr/lib/libnsl_i.a
/usr/lib/libnsl.so
/usr/lib/libxti.so
* Link to /usr/ccs/lib/libc.so
/usr/ccs/lib/libp/libc.so
Possible Side Effects:
NOTICE #1: The file systems will appear to have gone down dirty the
first time a kernel with this change is booted (even if the
previous kernel shutdown cleanly). This occurs because it
takes one boot sequence to initialize the new dirty/clean
flag location.
The fast boot logic may not accurately detect the state of
the file systems if you switch back and forth between a
kernel that does not have this change, and a kernel that has
this change.
NOTICE #2: Tunable parameters that control position and size of I/O and
memory windows on secondary PCI buses have been changed.
Sites that have locally defined any of the the old PCIx_MEM_*
or PCIx_IO_* tunable values will need to convert these to the
equivalent PCIx_MEM* or PCIx_IO* values.
DO NOT SIMPLY SUBSITITUTE THESE OLD TUNABLE VALUES FOR THE
CORRESPONDING NEW PARAMETER BECAUSE THE MEANINGS OF THESE
PARAMETERS ARE DIFFERENT. FAILURE TO DO SO MAY RESULT IN
UNEXPECTED OR UNRELIABLE BEHAVIOR.
Instead, read the descriptions of the new tunable parameters
closely, and supply a new value only if necessary for your
configuration. The default values provided should work for
most common configurations.
return to index
================================================================================
Concurrent Computer Corporation Software Development
Software Patch Report
Patch Name: base-015
Date Issued: 09/30/98 08:48:35
Software Package: base pkg (Version 4.2)
OS Release: PowerMAX OS 4.2
Architectures: nh
Platforms: Night Hawk 6200/6800, TurboHawk, PowerMAXION
Related Patches: audit-001, cmds-002, crosslibs-003, crypt-002,
crypt-int-001, dec-007, inet-006, man-005, ncr-002,
via-001
Related SARS: HM12415, HM12357, HM12462
Brief Description:
PowerMAX OS 4.2 base package release updates
Problem Description:
1. iconnect(3C) ICON_IVEC II_ALLOCATE calls may always return EBUSY.
If an interrupt vector is allocated with an iconnect(3C) ICON_IVEC
II_ALLOCATE call, and a LWP makes an ienable(3C) call to connect to
that vector, and another LWP later disconnects that ienabled LWP with
a iconnect(3C) ICON_DISC call, then that allocated interrupt vector
will be improperly marked free in the kernel's interrupt vector
table, even though the kernel's user-level interrupt data structures
will properly indicate that this vector is still ICON_IVEC allocated.
All subsequent iconnect(3C) ICON_IVEC II_ALLOCATE calls without the
vector specified (where the II_VECSPEC flag is not set) will result
in EBUSY being returned, instead of having a vector successfully
allocated.
2. Rommable PowerMAX OS support added:
Added random access decompression library support (radl) to the
kernel, plus tunable and stub file to enable or disable. This
library must be enabled for all diskless configurations of
PowerMAX OS. For all other configurations, it may be enable or
disabled. By default radl is disabled for all platforms, since by
default most platforms have a true disk for root. The various
diskless build packages (netboot, cluster) automatically turn this on
for the affected targets or clients as appropriate. Hence it is
expected there will be little need to explicitly turn this
configuration tunable on or off.
Added a random access compressor which produces compressed images
suitable for use by the above random access decompression library.
This compressor is both upwards and downwards compatible with gzip.
3. Enhancements to to the memfs kernel module to support booting from
a Flash Memory Device, a new feature added to the cluster and netboot
software packages.
4. The fast boot logic does not properly detect that the file systems
are dirty during a system boot if the following condition occurs:
A) a boot and then a "clean" shutdown of a kernel that has the
FASTFS tunable SET
B) boot and then a "non-clean" shutdown of a kernel that has
the FASTFS tunable RESET
C) boot of a kernel that has the FASTFS tunable SET
The kernel in step A) would leave the dirty/clean flag set to clean.
If the kernel in step B) shutdown without going through a clean
shutdown, the dirty/clean flag would not get reset to dirty. Finally,
the kernel in step C) would see the flag as clean and would attempt
to boot without running fsck on the dirty file systems.
5. Added NVRAM Global Environment Variable (GEV) support for the
Motorola platforms. PPCBug Revisions 1.8 and later provide support
for GEVs which reside in the PowerPC Reference Platform (PRP) region
of the NVRAM on the CPU board. PPCBug allows the OS access to share
this area. GEVs can still be used by the OS with an older revision of
PPCBug, but there will be no PPCBug commands to access them, and the
GEV area may need to be initialized by the OS.
The new nvram(2) system call and the gev(1) set of commands (gevdel,
gevdump, gevget, gevgetval, gevinfo, gevinit, gevput, gevputval,
and gevshow) provide services that allow you to add, delete, replace,
initialize and get information about one or more GEV entries.
The GEV area within the NVRAM is an array of null terminated strings.
These strings have the form:
name=[value]
At the present time there is no support for GEVs on nh platforms.
The nvram system call always returns ENOSYS on nh platforms and the
gev set of commands are not present.
6. HM12415: Add Symbios 53c875/895 high performance modes enhancements
and support for removable media Magneto-Optical Drives.
* Support ncr (Symbios) 53c875/895 high performance modes.
* Need enhancements to support removable media disks and 1K
sector size.
* SCSI ULTRA requires fewer devices on shorter cabling than
FAST/WIDE.
* Optical media change not protected against change in
geometry block.
* Raw disk transfers greater than 128K not supported.
* Some SCSI devices will reconnect, then immediately
disconnect without doing anything.
7. XFS files do not have microsecond resolution update times set. XFS
fails to correctly set the tv_usec subfield of the file access,
modification or changed timeval structures. The tv_sec subfield
returned by the standard stat system call is correctly set, only the
extended stat (xstat) system call shows this problem.
8. When xdm is used to manage a host based X server process, shutdown
processing that kills all processing can lead to a race condition
wherein an X server process will be killed by shutdown, but before
xdm itself is killed, a new X server process is launched. Depending
on how far this this process gets before it is killed itself, the
video hardware may not be restored to VGA compatible mode. When this
happens, the display is corrupted, and the system appears to be hung.
9. Certain logitech serial mouse devices are not always detected and
initialized properly by the smse STREAMs module. Mouse detection
state machine in smse was easily confused because timeouts were too
short and certain early exits could be taken.
10. PCI drivers multi-function device and BIT-3 bridge support required
to correct certain deficiencies in kernel PCI drivers including:
* No support for multi-function PCI devices
* PCI bridge depth limited to 2 bridges. BIT-3 PCI expansion
chassis requires depth 3.
* Default tunable values for PCI bridges are not appropriate
for all architectures.
11. Serial keyboard STREAM module did not support Concurrent's own
serial kbd.
12. HM12357, HM12462: When the top(1) command is run on a system that
has more than six (6) processors configured, it will fail with a
segmentation violation and dump core. The problem is that the memory
allocated for memory usage display is only 80 characters in length.
This allocation is used up when more than 6 CPUs are configured.
13. According to POSIX, a process whose priority is lowered goes to the
end of its new priority run queue. Thus, if there are other
processes already in that queue, the lowered LWP must give up the
CPU immediately to them and wait its turn. This was not happening.
Instead, the running LWP would continue to run until it either
voluntarily gave up the CPU, or some other event, such as I/O
completion, caused the CPU to re-evaluate which LWP was supposed to
be running.
14. On TurboHawk systems, interrupts routed to the frontplane from a
processor board did not work if multiple devices shared the interrupt
level. The devices affected were:
* Embedded DEC Ethernets
* Embedded NCR SCSI
* Embedded UARTs
* PMC supported devices including secondary VME I/O
The foreign processor assigned to service the shared interrupt could
not determine the interrupting device.
NOTE: A single device on a processor board does not exhibit this
problem if its interrupt is routed to the frontplane and its
interrupt level is not shared with other devices from other boards.
15. Console write followed by baud rate change corrupts last data byte.
Baud rate changes in console driver always wait for pending data to
be flushed. Even so, the last data byte is sometimes corrupted if
the UART baud rate divisors are changed too soon after the last TBE
interrupt.
16. I/O expansion was only supported from the PMC port of the first
TurboHawk CPU board.
Problem Resolution:
1. The fix is to re-implement the way that interrupt vectors are restored
in the kernel's interrupt vector table when a iconnect(3C) ICON_DISC
disconnection occurs, so that the proper vector value is placed into
the interrupt vector table entry.
2. Implemented as detailed above.
3. Modifications to the memfs kernel moduled made to support booting
from a Flash Memory Device.
4. The fast boot logic was changed to always set the dirty/clean flag to
dirty during system initialization, whether or not the FASTFS tunable
is set for the kernel. Previously, the dirty/clean flag was set to
dirty during system initialization only when the FASTFS tunable was
set. The dirty/clean flag will now be left set to dirty if the system
does not shutdown cleanly, irregardless of how FASTFS is set. This
insures that the next kernel that boots will never see the file
systems as clean when the previous kernel went down dirty.
6. Problems resolved as follows:
* Add ULTRA-2 (LVD) controller support (Symbios 53c895) to ncr
driver.
* Added special SCSI Script instructions to reset 53c875 cache
line alignment mechanism on each PCI dma block move. Added
high performance mode configuration. Added FIFO flush logic
to completion and disconnect. Added NCR_BURST_SZ tunable
to allow multiple dma cache line bursts per PCI bus tenure.
* Changed generic disk driver (gd) to support 1K sector
format, media missing at boot, media change, and disk
geometry change with media change (including new partition
layout). Added check for true block size in via driver.
* Added NCR_875_MAX_SYNC system tunable allow running more
drives on a longer cable by tuning the 53c875 to FAST/WIDE
speeds.
* Added PHYSIO_MAXTRNSFR system tunable to allow up to 512K
raw transfers for ncr (via and hsa not supported).
7. Change the xfs file time update code to set both subfields of the
access, modification or changed timeval structures.
8. xdm needs some help to know when a shutdown is occuring so that
attempts to re-launch the X server can be avoided. Once committed to
shutting down the system, the shutdown script now creates a file
/var/NOLOGIN as a signal that a shutdown is in progress. This file
is removed by rc1 and rc2 startup scripts when booting or restarting.
9. Smse timeouts have been lengthened and the state machine code made
more robust.
10. Numerous enhancements to PCI support including:
* Support added for doing configuration accesses of
multi-function PCI devices.
* PCI bridge depths up to four now supported, including last
four expansion slots of the BIT3 PCI expansion chassis.
* PCI bridge I/O and memory range tunables expanded and
architecture specific tunables (defaults) were added.
11. Replace AT2Serial converter box support in skbd STREAMS module with
support for Concurrent's own serial keyboard.
12. The top(1) command has been modified to allow a larger memory
allocation for the memory usage display. This fix also resulted in a
small change to the top(1) manpage, corrected in patch man-005.
13. The cause was the failure of the priocntl system call to nudge the
CPU after changing the LWP's priority (i.e., failed to force the CPU
to re-evaluate which LWP it was supposed to run). The LWP was
actually put at the end of its new run queue as it should have been,
but without the nudge the CPU did not notice the changed
circumstances of the LWP.
The solution was to expand the `if' statement that does nudging in
priocntl(2) to nudge if the new priority run queue was not empty
prior to the insertion.
14. A foreign processor is now able to correctly discern between multiple
devices interrupting over the TurboHawk frontplane from multiple
processor boards.
15. Console driver now delays a short period longer to allow the UART to
finish whatever it is doing before changing line communication
parameters.
16. I/O expansion is now supported from any CPU board PMC port.
Object To Be Replaced:
/etc/conf/mdevice.d/radl
/etc/conf/mtune.d/gd
/etc/conf/mtune.d/io
/etc/conf/mtune.d/memfs
/etc/conf/mtune.d/pci
/etc/conf/pack.d/bsp6800t/Driver.o
/etc/conf/pack.d/cons/Driver.o
/etc/conf/pack.d/gd/Driver.o
/etc/conf/pack.d/gd/space.c
/etc/conf/pack.d/io/Driver.o
/etc/conf/pack.d/io/space.c
/etc/conf/pack.d/memfs/Driver.o
/etc/conf/pack.d/memfs/space.c
/etc/conf/pack.d/pci/Driver.o
/etc/conf/pack.d/pci/space.c
/etc/conf/pack.d/proc/Driver.o
/etc/conf/pack.d/radl/Driver.o
/etc/conf/pack.d/radl/stubs.c
/etc/conf/pack.d/scsi/Driver.o
/etc/conf/pack.d/skbd/Driver.o
/etc/conf/pack.d/skbd/space.c
/etc/conf/pack.d/smse/Driver.o
/etc/conf/pack.d/svc/Driver.o
/etc/conf/pack.d/ui/Driver.o
/etc/conf/pack.d/vme/Driver.o
/etc/conf/sdevice.d/radl
/etc/conf/sdevice.d/skbd
/usr/bin/rac
/usr/bin/top
/usr/ccs/lib/libc.a
/usr/ccs/lib/libc.so
/usr/include/libc_synonyms.h
/usr/include/sys/adapter.h
/usr/include/sys/iconnect.h
/usr/include/sys/im.h
/usr/include/sys/gd.h
/usr/include/sys/nvram.h
/usr/include/sys/pci.h
/usr/include/sys/pci_p.h
/usr/include/sys/pci_info.h
/usr/include/sys/racfile.h
/usr/include/sys/radl.h
/usr/include/sys/scsi.h
/usr/include/sys/skbd.h
/usr/include/sys/syscall.h
/usr/include/sys/fs/memfs_mnode.h
/usr/include/sys/fs/memfs.h
/usr/lib/libnsl_i.a
/usr/lib/libnsl_i.so
/usr/lib/libc.so.1
/usr/lib/libcmd.a
/usr/lib/libud.so
/usr/lib/libud.a
/usr/lib/locale/C/MSGFILES/core.abi.str
/usr/lib/locale/C/MSGFILES/harris.str
/sbin/rc0
/sbin/rc1
/sbin/rc2
/sbin/shutdown
/sbin/wsinit
Special Conditions for Installation:
NOTICE #1: A hardware change to TurboHawk processor boards and TurboHawk
global memory boards is required to support routing of
interrupts to the frontplane for handling by a foreign
processor. An additional hardware change to TurboHawk
processor boards is required to support I/O expansion from
CPU boards other than the first.
Revision 'N' of TurboHawk processor boards and revision 'F'
of TurboHawk global memory boards are required, along with
this software patch, to support this interrupt feature.
Revision 'R' of the TurboHawk processor boards is required
to support the secondary I/O expansion from any CPU board.
NOTICE #3: The following links will also be created during installation
of base-015:
* Link to /usr/bin/gev
/usr/bin/gevdel
/usr/bin/gevdump
/usr/bin/gevget
/usr/bin/gevgetval
/usr/bin/gevinfo
/usr/bin/gevinit
/usr/bin/gevput
/usr/bin/gevputval
/usr/bin/gevshow
* Link to /usr/lib/libnsl_i.a
/usr/lib/libnsl.a
/usr/lib/libxti.a
/usr/lib/libsocket.a
* Link to /usr/lib/libnsl_i.a
/usr/lib/libnsl.so
/usr/lib/libxti.so
* Link to /usr/ccs/lib/libc.so
/usr/ccs/lib/libp/libc.so
Possible Side Effects:
NOTICE #1: Tunable parameters that control position and size of I/O and
memory windows on secondary PCI buses have been changed.
Sites that have locally defined any of the the old PCIx_MEM_*
or PCIx_IO_* tunable values will need to convert these to the
equivalent PCIx_MEM* or PCIx_IO* values.
DO NOT SIMPLY SUBSITITUTE THESE OLD TUNABLE VALUES FOR THE
CORRESPONDING NEW PARAMETER BECAUSE THE MEANINGS OF THESE
PARAMETERS ARE DIFFERENT. FAILURE TO DO SO MAY RESULT IN
UNEXPECTED OR UNRELIABLE BEHAVIOR.
Instead, read the descriptions of the new tunable parameters
closely, and supply a new value only if necessary for your
configuration. The default values provided should work for
most common configurations.
return to index
================================================================================
Concurrent Computer Corporation Software Development
Software Patch Report
Patch Name: base-016
Date Issued: 02/09/99 08:32:36
Software Package: base pkg (Version 4.2)
OS Release: PowerMAX OS 4.2
Architectures: moto
Platforms: Power Hawk 610/620, PowerStack, PowerStack II (uni-proc)
Related Patches: cld-001, cluster-006, cmds-003, crosslibs-004, dec-008,
fibre-001, inet-007, man-006, netboot-001, nsu-002,
vp-003, rvsrv (4.2), xfsd (4.2)
Related SARS: HM12442, HM12546, HM12478
Brief Description:
PowerMAX OS 4.2 base package release updates
Problem Description:
1. All Distributed XFS (xfsd) mount-points are destroyed on the host
server in the event of a single distributed file system being
unmounted or otherwise terminated due to connection or response
timeout error.
2. The generic disk driver which generates the names for the drives used
on the mpstat command used a simple numbering system which did not
correlate to any real drive numbering.
3. Add features to support xfsd distributed xfs extension:
* Add filesystem object (.xfs_sysobj) to xfs filesystem root
directory, this is a character device supporting ioctl
commands directed to the filesystem. The supported ioctl
commands are documented in /usr/include/sys/fs/xfsps_vnop.h.
* Add XFS_SYSID to xfs Mtune file and new option "-o force" to
the xfs specific mount options to assist with inadvertent
double mount of filesystems on multi-initiator disk bus.
* Add new option "-x <xnodes>" to xfs specific mkfs options to
allow filesystems to support more than 256k xnodes. Xfs mkfs
adds new filesystem identity field to superblock.
4. PANIC: kernel-mode address fault on kernel address 0x00000008 on
unmount after disk failure forces filesystem read-only.
5. VME cards can interrupt with a few different requirements of the
host. The intr.s code previously assumed the interrupter was of the
more common case, Release-on-Acknowledge, in which the interrupt is
cleared on the VME board before intr.s is invoked. The intr.s code
could modify the host's mask of active interrupts immediately,
because the interrupt had already been cleared on the board.
However, a few VME interrupters only clear their interrupt when their
registers are accessed from the host's interrupt routine, and in
these instances, intr.s would clear the host's mask of active
interrupts before the intr.s code invoked the host's interrupt
routine. This would result in the host's mask of active interrupts
being cleared before VME interrupter actually cleared its interrupt,
and this would result in anomalous behavior.
6. Currently under PowerMAX OS, when there are pending messages that
need to be executed by a STREAMS service procedure, the STREAMS
scheduler will select the CPU(s) to execute these service procedures
based on a system-wide set of CPUs. Potentially, any CPU not in the
STRSCHED_DISABLE_MASK tunable mask may be selected to execute a
STREAMS service procedure.
For real-time systems, the above functionality does provide some
amount of shielding of STREAMS service procedures. For example,
those CPUs that are dealing with real-time critical tasks can be
placed into the STRSCHED_DISABLE_MASK, thus off-loading the task of
executing STREAMS service procedures to the non-real-time CPUs.
However, some situations may require a finer granularity of control
over STREAMS service procedure executions. This additional level of
control would be useful when it is desirable for real-time CPUs to
also execute some selectable subset of high-priority STREAMS service
procedures that are handling real-time-related STREAMS messages.
7. HM12442: memcmp() is supposed to return < = or > 0 based on the
comparison of the input data, but there are cases where it returns
wrong results. bcmp() had similar problems.
8. HM12546: Values returned by clock_gettime() on Motorola machines
would be inaccurate. This was especially true when the tunable
HIGHRESTIMING was enabled.
9. HM12478: It is possible to boot any PowerHawk/PowerStack system from
COM2 port. Since COM2 port is not fully functional to be used for
the boot terminal this causes problems in the boot process
culminating in the reassignment of /dev/syscon to /dev/COM2. This
then makes it very difficult to correct the assignment of /dev/syscon
and get the system back to properly booting on COM1.
Problem Resolution:
1. Termination signals (i.e. SIGQUIT) sent to a specific kernel sysproc
thread resulted in the signal mistakenly being sent to all sysproc
threads. This resulted in all XFSD sysproc thread terminations, not
just the thread associated with the file system being unmounted.
The kernel event signal handler now correctly identifies sysproc
threads and only wakes up the sysproc thread associated with the file
system which is being unmounted.
2. Change the generation of the internal disk metrics table to include
the controller name and number on disk drives.
3. New features added for xfsd support as follows:
* Filesystem object supports the following ioctl commands:
FSCTRL Filesystem control commands, there are six
subcommands documented in xfsps_vnop.h
XFS_FSCGETWWN display filesystem identity
XFS_FSCSETWWN set filesystem identity
XFS_FSCSETXNC set filesystem max xnode count
XFS_FSCGETEXC display filesystem export count
XFS_FSCGETEXP display filesystem export
XFS_FSCDELEXP kill filesystem export
FSEXPORT Filesystem export, used by xfsd
distributed mount.
FSUXPORT Filesystem unexport, used only by
failed mount.
FSFLUSH Filesystem flush, sync filesystem log
cache to disk. Used by xfs diagnostic
utilities.
FSDLMCALL A hook for future use to load and call
dynamic loaded filesystem extension
modules.
* Xfs filesystem mount arguments extended to allow distributed
mounts. A new option "-o force" has been added for use with
the XFS_SYSID Mtune field.
* Xfs filesystems support a default maximum number of xnodes,
this value is set at 256k. The default mkfs action is to
create a filesystem with 32 (one page) of xnodes and then
extend the list on demand in units of 32 up to the maximum.
The new -x <count> option on xfs mkfs allows the mamimum
number of supported xnodes to be raised in units of 32k up
to a limit of one xnode per Kilobyte of filesystem disk
space. A -i <count> enables up to 32k of xnodes to be
prealloacted instead of the default of 32. The maximum
xnode count can also be reset on an existing filesystem with
the FSCTRL ioctl command.
* The xfs mkfs adds a filesystem identifier to the superblock,
this identifier should be unique to each filesystem on a
multi-initiator disk bus and is used by the distributed xfs
mount to ensure that the multiple hosts of a distributed
mount are all using the same filesystem. The identifier can
be displayed and changed with the filesystem FSCTRL ioctl
command.
4. The filesystem unmount attempted to remove a structure which had
already been removed by a disk I/O failure forcing the filesystem
into read-only mode.
5. The intr.s code now has a conditional compilation flag, which allows
intr.s to properly handle Release-on-Acknowledge by enabling this
flag. By default, this flag is disabled, which provides the original
intr.s semantics. The operation of the system should not be
compromised by enabling this flag, but original semantics were felt
to be a reasonable default.
6. Provide configurable, general purpose CPU biasing control of STREAMS
service procedure executions on a per-STREAM basis. Each STREAM that
exists will have its own CPU bias mask which will define the set of
CPUs that may execute that STREAM's service procedures.
This capability gives the user a finer granularity of control over
where the STREAM's service procedures are executed.
7. Fixed to work as described in memcmp() and bcmp()'s man pages.
8. Correct kernel interval timer assist page so that update is only
done twice per second. Make corrections for handling rollover
(i.e. when lower portion of time-base-register resets to zero).
Fix computational errors so that all time-base-register ticks are
accounted for.
9. The console code has been modified to force the system to boot on
COM1 even if it is selected to boot on COM2.
Object To Be Replaced:
/etc/conf/cf.d/intr.s
/etc/conf/mtune.d/io
/etc/conf/mtune.d/xfs
/etc/conf/pack.d/gd/Driver.o
/etc/conf/pack.d/io/Driver.o
/etc/conf/pack.d/io/space.c
/etc/conf/pack.d/mod/Driver.o
/etc/conf/pack.d/proc/Driver.o
/etc/conf/pack.d/svc/Driver.o
/etc/conf/pack.d/uni/Driver.o
/etc/conf/pack.d/vp/stubs.c
/etc/conf/pack.d/xfs/Driver.o
/etc/conf/pack.d/xfs/space.c
/etc/conf/sdevice.d/vp
/etc/fs/xfs/mkfs
/etc/fs/xfs/mount
/stand/cp1
/usr/include/snmp/snmp.h
/usr/include/snmp/snmpio.h
/usr/include/snmp/snmpuser.h
/usr/include/snmp/snmp_trap.h
/usr/include/sys/assym_dbg.h
/usr/include/sys/assym_nodbg.h
/usr/include/sys/hrtiming.h
/usr/include/sys/plocal.h
/usr/include/sys/stream.h
/usr/include/sys/stropts.h
/usr/include/sys/strsubr.h
/usr/include/sys/syscx.h
/usr/include/sys/fs/xfs_dir.h
/usr/include/sys/fs/xfs_dxnode.h
/usr/include/sys/fs/xfs_filsys.h
/usr/include/sys/fs/xfs_param.h
/usr/include/sys/fs/xfs_types.h
/usr/lib/fs/xfs/mkfs
/usr/lib/fs/xfs/mount
/usr/lib/libc.so.1
/usr/lib/locale/C/MSGFILES/harris.str
/usr/ccs/lib/libc.a
/usr/ccs/lib/libc.so
Special Conditions for Installation:
NOTICE #1: With multi-initiator disk bus systems it is possible to mount
a filesystem disk on more than one host system, this is a
good way to corrupt a filesystem if both hosts are allocating
disk space and xnodes from their own cached copy of the
filesystem pages. The XFS_SYSID Mtune helps to protect
against this problem. The XFS_SYSID should be set to a value
unique on the multi-initiator disk bus, mount of an xfs
filesystem on one of the systems will then set that system's
XFS_SYSID into the superblock. Attempts to mount that
filesystem on another of the multi-initiator hosts will be
rejected unless the mount is used with the -o force option.
It is left to the user to ensure that the filesystem is not
mounted on its normal host system before using the force
option. After use of the force option the new system XFS_SYSID
is set into the superblock. If the XFS_SYSID Mtune is left at
the default value then the multi-initiator protection is not
enforced.
NOTICE #2: This patch modifies /etc/conf/cf.d/intr.s. If this file has
been modified locally, then those local changes will need to
be re-applied as necessary after the patch is installed.
NOTICE #3: During installation of base-016, an updated version of
/stand/cp1 will be installed and the new console overlay will
be written to partition 6 on the system disk. Following
successful installation, the system must be taken down and
reset to load the new console before rebooting. Failure to
do so may result in unexpected or unreliable behavior.
NOTICE #4: The following links will also be created during installation
of base-016:
* Link to /usr/ccs/lib/libc.so
/usr/ccs/lib/libp/libc.so
Possible Side Effects:
If the base-016 package is removed (pkgrm(1M)), the original console
will be re-written to partition 6 on the system disk. To ensure there
are no adverse side effects, the kernel should be rebuilt (idbuild(1M))
and the system taken down and reset to load the original console before
rebooting the system.
Suggested procedure for removing base-016:
# pkgrm base-016
# /etc/conf/bin/idbuild -B
# sync
# init 0
# Reset system
Follow the normal boot procedure detailed in the PowerMAX OS Product
Release Notes to load the new console and boot the new kernel.
return to index
================================================================================
Concurrent Computer Corporation Software Development
Software Patch Report
Patch Name: base-017
Date Issued: 02/09/99 09:26:47
Software Package: base pkg (Version 4.2)
OS Release: PowerMAX OS 4.2
Architectures: moto
Platforms: Power Hawk 640, PowerStack II (multi-proc)
Related Patches: cld-001, cluster-006, cmds-003, crosslibs-004, dec-008,
fibre-001, inet-007, man-006, netboot-001, nsu-002,
vp-003, rvsrv (4.2), xfsd (4.2)
Related SARS: HM12442, HM12546, HM12478
Brief Description:
PowerMAX OS 4.2 base package release updates
Problem Description:
1. All Distributed XFS (xfsd) mount-points are destroyed on the host
server in the event of a single distributed file system being
unmounted or otherwise terminated due to connection or response
timeout error.
2. The generic disk driver which generates the names for the drives used
on the mpstat command used a simple numbering system which did not
correlate to any real drive numbering.
3. Add features to support xfsd distributed xfs extension:
* Add filesystem object (.xfs_sysobj) to xfs filesystem root
directory, this is a character device supporting ioctl
commands directed to the filesystem. The supported ioctl
commands are documented in /usr/include/sys/fs/xfsps_vnop.h.
* Add XFS_SYSID to xfs Mtune file and new option "-o force" to
the xfs specific mount options to assist with inadvertent
double mount of filesystems on multi-initiator disk bus.
* Add new option "-x <xnodes>" to xfs specific mkfs options to
allow filesystems to support more than 256k xnodes. Xfs mkfs
adds new filesystem identity field to superblock.
4. PANIC: kernel-mode address fault on kernel address 0x00000008 on
unmount after disk failure forces filesystem read-only.
5. VME cards can interrupt with a few different requirements of the
host. The intr.s code previously assumed the interrupter was of the
more common case, Release-on-Acknowledge, in which the interrupt is
cleared on the VME board before intr.s is invoked. The intr.s code
could modify the host's mask of active interrupts immediately,
because the interrupt had already been cleared on the board.
However, a few VME interrupters only clear their interrupt when their
registers are accessed from the host's interrupt routine, and in
these instances, intr.s would clear the host's mask of active
interrupts before the intr.s code invoked the host's interrupt
routine. This would result in the host's mask of active interrupts
being cleared before VME interrupter actually cleared its interrupt,
and this would result in anomalous behavior.
6. Currently under PowerMAX OS, when there are pending messages that
need to be executed by a STREAMS service procedure, the STREAMS
scheduler will select the CPU(s) to execute these service procedures
based on a system-wide set of CPUs. Potentially, any CPU not in the
STRSCHED_DISABLE_MASK tunable mask may be selected to execute a
STREAMS service procedure.
For real-time systems, the above functionality does provide some
amount of shielding of STREAMS service procedures. For example,
those CPUs that are dealing with real-time critical tasks can be
placed into the STRSCHED_DISABLE_MASK, thus off-loading the task of
executing STREAMS service procedures to the non-real-time CPUs.
However, some situations may require a finer granularity of control
over STREAMS service procedure executions. This additional level of
control would be useful when it is desirable for real-time CPUs to
also execute some selectable subset of high-priority STREAMS service
procedures that are handling real-time-related STREAMS messages.
7. HM12442: memcmp() is supposed to return < = or > 0 based on the
comparison of the input data, but there are cases where it returns
wrong results. bcmp() had similar problems.
8. HM12546: Values returned by clock_gettime() on Motorola machines
would be inaccurate. This was especially true when the tunable
HIGHRESTIMING was enabled.
9. HM12478: It is possible to boot any PowerHawk/PowerStack system from
COM2 port. Since COM2 port is not fully functional to be used for
the boot terminal this causes problems in the boot process
culminating in the reassignment of /dev/syscon to /dev/COM2. This
then makes it very difficult to correct the assignment of /dev/syscon
and get the system back to properly booting on COM1.
Problem Resolution:
1. Termination signals (i.e. SIGQUIT) sent to a specific kernel sysproc
thread resulted in the signal mistakenly being sent to all sysproc
threads. This resulted in all XFSD sysproc thread terminations, not
just the thread associated with the file system being unmounted.
The kernel event signal handler now correctly identifies sysproc
threads and only wakes up the sysproc thread associated with the file
system which is being unmounted.
2. Change the generation of the internal disk metrics table to include
the controller name and number on disk drives.
3. New features added for xfsd support as follows:
* Filesystem object supports the following ioctl commands:
FSCTRL Filesystem control commands, there are six
subcommands documented in xfsps_vnop.h
XFS_FSCGETWWN display filesystem identity
XFS_FSCSETWWN set filesystem identity
XFS_FSCSETXNC set filesystem max xnode count
XFS_FSCGETEXC display filesystem export count
XFS_FSCGETEXP display filesystem export
XFS_FSCDELEXP kill filesystem export
FSEXPORT Filesystem export, used by xfsd
distributed mount.
FSUXPORT Filesystem unexport, used only by
failed mount.
FSFLUSH Filesystem flush, sync filesystem log
cache to disk. Used by xfs diagnostic
utilities.
FSDLMCALL A hook for future use to load and call
dynamic loaded filesystem extension
modules.
* Xfs filesystem mount arguments extended to allow distributed
mounts. A new option "-o force" has been added for use with
the XFS_SYSID Mtune field.
* Xfs filesystems support a default maximum number of xnodes,
this value is set at 256k. The default mkfs action is to
create a filesystem with 32 (one page) of xnodes and then
extend the list on demand in units of 32 up to the maximum.
The new -x <count> option on xfs mkfs allows the mamimum
number of supported xnodes to be raised in units of 32k up
to a limit of one xnode per Kilobyte of filesystem disk
space. A -i <count> enables up to 32k of xnodes to be
prealloacted instead of the default of 32. The maximum
xnode count can also be reset on an existing filesystem with
the FSCTRL ioctl command.
* The xfs mkfs adds a filesystem identifier to the superblock,
this identifier should be unique to each filesystem on a
multi-initiator disk bus and is used by the distributed xfs
mount to ensure that the multiple hosts of a distributed
mount are all using the same filesystem. The identifier can
be displayed and changed with the filesystem FSCTRL ioctl
command.
4. The filesystem unmount attempted to remove a structure which had
already been removed by a disk I/O failure forcing the filesystem
into read-only mode.
5. The intr.s code now has a conditional compilation flag, which allows
intr.s to properly handle Release-on-Acknowledge by enabling this
flag. By default, this flag is disabled, which provides the original
intr.s semantics. The operation of the system should not be
compromised by enabling this flag, but original semantics were felt
to be a reasonable default.
6. Provide configurable, general purpose CPU biasing control of STREAMS
service procedure executions on a per-STREAM basis. Each STREAM that
exists will have its own CPU bias mask which will define the set of
CPUs that may execute that STREAM's service procedures.
This capability gives the user a finer granularity of control over
where the STREAM's service procedures are executed.
7. Fixed to work as described in memcmp() and bcmp()'s man pages.
8. Correct kernel interval timer assist page so that update is only
done twice per second. Make corrections for handling rollover
(i.e. when lower portion of time-base-register resets to zero).
Fix computational errors so that all time-base-register ticks are
accounted for.
9. The console code has been modified to force the system to boot on
COM1 even if it is selected to boot on COM2.
Object To Be Replaced:
/etc/conf/cf.d/intr.s
/etc/conf/mtune.d/io
/etc/conf/mtune.d/xfs
/etc/conf/pack.d/gd/Driver.o
/etc/conf/pack.d/io/Driver.o
/etc/conf/pack.d/io/space.c
/etc/conf/pack.d/mod/Driver.o
/etc/conf/pack.d/proc/Driver.o
/etc/conf/pack.d/svc/Driver.o
/etc/conf/pack.d/uni/Driver.o
/etc/conf/pack.d/vp/stubs.c
/etc/conf/pack.d/xfs/Driver.o
/etc/conf/pack.d/xfs/space.c
/etc/conf/sdevice.d/vp
/etc/fs/xfs/mkfs
/etc/fs/xfs/mount
/stand/cp1
/usr/include/snmp/snmp.h
/usr/include/snmp/snmpio.h
/usr/include/snmp/snmpuser.h
/usr/include/snmp/snmp_trap.h
/usr/include/sys/assym_dbg.h
/usr/include/sys/assym_nodbg.h
/usr/include/sys/hrtiming.h
/usr/include/sys/plocal.h
/usr/include/sys/stream.h
/usr/include/sys/stropts.h
/usr/include/sys/strsubr.h
/usr/include/sys/syscx.h
/usr/include/sys/fs/xfs_dir.h
/usr/include/sys/fs/xfs_dxnode.h
/usr/include/sys/fs/xfs_filsys.h
/usr/include/sys/fs/xfs_param.h
/usr/include/sys/fs/xfs_types.h
/usr/lib/fs/xfs/mkfs
/usr/lib/fs/xfs/mount
/usr/lib/libc.so.1
/usr/lib/locale/C/MSGFILES/harris.str
/usr/ccs/lib/libc.a
/usr/ccs/lib/libc.so
Special Conditions for Installation:
NOTICE #1: With multi-initiator disk bus systems it is possible to mount
a filesystem disk on more than one host system, this is a
good way to corrupt a filesystem if both hosts are allocating
disk space and xnodes from their own cached copy of the
filesystem pages. The XFS_SYSID Mtune helps to protect
against this problem. The XFS_SYSID should be set to a value
unique on the multi-initiator disk bus, mount of an xfs
filesystem on one of the systems will then set that system's
XFS_SYSID into the superblock. Attempts to mount that
filesystem on another of the multi-initiator hosts will be
rejected unless the mount is used with the -o force option.
It is left to the user to ensure that the filesystem is not
mounted on its normal host system before using the force
option. After use of the force option the new system XFS_SYSID
is set into the superblock. If the XFS_SYSID Mtune is left at
the default value then the multi-initiator protection is not
enforced.
NOTICE #2: This patch modifies /etc/conf/cf.d/intr.s. If this file has
been modified locally, then those local changes will need to
be re-applied as necessary after the patch is installed.
NOTICE #3: During installation of base-017, an updated version of
/stand/cp1 will be installed and the new console overlay will
be written to partition 6 on the system disk. Following
successful installation, the system must be taken down and
reset to load the new console before rebooting. Failure to
do so may result in unexpected or unreliable behavior.
NOTICE #4: The following links will also be created during installation
of base-017:
* Link to /usr/ccs/lib/libc.so
/usr/ccs/lib/libp/libc.so
Possible Side Effects:
If the base-017 package is removed (pkgrm(1M)), the original console
will be re-written to partition 6 on the system disk. To ensure there
are no adverse side effects, the kernel should be rebuilt (idbuild(1M))
and the system taken down and reset to load the original console before
rebooting the system.
Suggested procedure for removing base-017:
# pkgrm base-017
# /etc/conf/bin/idbuild -B
# sync
# init 0
# Reset system
Follow the normal boot procedure detailed in the PowerMAX OS Product
Release Notes to load the new console and boot the new kernel.
return to index
================================================================================
Concurrent Computer Corporation Software Development
Software Patch Report
Patch Name: base-018
Date Issued: 02/09/99 09:40:04
Software Package: base pkg (Version 4.2)
OS Release: PowerMAX OS 4.2
Architectures: nh
Platforms: Night Hawk 6200/6800, TurboHawk, PowerMAXION
Related Patches: cmds-003, crosslibs-004, dec-008, fibre-001, inet-008,
man-006, nsu-002, vp-003, xfsd (4.2)
Related SARS: HM12442
Brief Description:
PowerMAX OS 4.2 base package release updates
Problem Description:
1. All Distributed XFS (xfsd) mount-points are destroyed on the host
server in the event of a single distributed file system being
unmounted or otherwise terminated due to connection or response
timeout error.
2. The generic disk driver which generates the names for the drives used
on the mpstat command used a simple numbering system which did not
correlate to any real drive numbering.
3. Add features to support xfsd distributed xfs extension:
* Add filesystem object (.xfs_sysobj) to xfs filesystem root
directory, this is a character device supporting ioctl
commands directed to the filesystem. The supported ioctl
commands are documented in /usr/include/sys/fs/xfsps_vnop.h.
* Add XFS_SYSID to xfs Mtune file and new option "-o force" to
the xfs specific mount options to assist with inadvertent
double mount of filesystems on multi-initiator disk bus.
* Add new option "-x <xnodes>" to xfs specific mkfs options to
allow filesystems to support more than 256k xnodes. Xfs mkfs
adds new filesystem identity field to superblock.
4. PANIC: kernel-mode address fault on kernel address 0x00000008 on
unmount after disk failure forces filesystem read-only.
5. VME cards can interrupt with a few different requirements of the
host. The intr.s code previously assumed the interrupter was of the
more common case, Release-on-Acknowledge, in which the interrupt is
cleared on the VME board before intr.s is invoked. The intr.s code
could modify the host's mask of active interrupts immediately,
because the interrupt had already been cleared on the board.
However, a few VME interrupters only clear their interrupt when their
registers are accessed from the host's interrupt routine, and in
these instances, intr.s would clear the host's mask of active
interrupts before the intr.s code invoked the host's interrupt
routine. This would result in the host's mask of active interrupts
being cleared before VME interrupter actually cleared its interrupt,
and this would result in anomalous behavior.
6. Currently under PowerMAX OS, when there are pending messages that
need to be executed by a STREAMS service procedure, the STREAMS
scheduler will select the CPU(s) to execute these service procedures
based on a system-wide set of CPUs. Potentially, any CPU not in the
STRSCHED_DISABLE_MASK tunable mask may be selected to execute a
STREAMS service procedure.
For real-time systems, the above functionality does provide some
amount of shielding of STREAMS service procedures. For example,
those CPUs that are dealing with real-time critical tasks can be
placed into the STRSCHED_DISABLE_MASK, thus off-loading the task of
executing STREAMS service procedures to the non-real-time CPUs.
However, some situations may require a finer granularity of control
over STREAMS service procedure executions. This additional level of
control would be useful when it is desirable for real-time CPUs to
also execute some selectable subset of high-priority STREAMS service
procedures that are handling real-time-related STREAMS messages.
7. HM12442: memcmp() is supposed to return < = or > 0 based on the
comparison of the input data, but there are cases where it returns
wrong results. bcmp() had similar problems.
Problem Resolution:
1. Termination signals (i.e. SIGQUIT) sent to a specific kernel sysproc
thread resulted in the signal mistakenly being sent to all sysproc
threads. This resulted in all XFSD sysproc thread terminations, not
just the thread associated with the file system being unmounted.
The kernel event signal handler now correctly identifies sysproc
threads and only wakes up the sysproc thread associated with the file
system which is being unmounted.
2. Change the generation of the internal disk metrics table to include
the controller name and number on disk drives.
3. New features added for xfsd support as follows:
* Filesystem object supports the following ioctl commands:
FSCTRL Filesystem control commands, there are six
subcommands documented in xfsps_vnop.h
XFS_FSCGETWWN display filesystem identity
XFS_FSCSETWWN set filesystem identity
XFS_FSCSETXNC set filesystem max xnode count
XFS_FSCGETEXC display filesystem export count
XFS_FSCGETEXP display filesystem export
XFS_FSCDELEXP kill filesystem export
FSEXPORT Filesystem export, used by xfsd
distributed mount.
FSUXPORT Filesystem unexport, used only by
failed mount.
FSFLUSH Filesystem flush, sync filesystem log
cache to disk. Used by xfs diagnostic
utilities.
FSDLMCALL A hook for future use to load and call
dynamic loaded filesystem extension
modules.
* Xfs filesystem mount arguments extended to allow distributed
mounts. A new option "-o force" has been added for use with
the XFS_SYSID Mtune field.
* Xfs filesystems support a default maximum number of xnodes,
this value is set at 256k. The default mkfs action is to
create a filesystem with 32 (one page) of xnodes and then
extend the list on demand in units of 32 up to the maximum.
The new -x <count> option on xfs mkfs allows the mamimum
number of supported xnodes to be raised in units of 32k up
to a limit of one xnode per Kilobyte of filesystem disk
space. A -i <count> enables up to 32k of xnodes to be
prealloacted instead of the default of 32. The maximum
xnode count can also be reset on an existing filesystem with
the FSCTRL ioctl command.
* The xfs mkfs adds a filesystem identifier to the superblock,
this identifier should be unique to each filesystem on a
multi-initiator disk bus and is used by the distributed xfs
mount to ensure that the multiple hosts of a distributed
mount are all using the same filesystem. The identifier can
be displayed and changed with the filesystem FSCTRL ioctl
command.
4. The filesystem unmount attempted to remove a structure which had
already been removed by a disk I/O failure forcing the filesystem
into read-only mode.
5. The intr.s code now has a conditional compilation flag, which allows
intr.s to properly handle Release-on-Acknowledge by enabling this
flag. By default, this flag is disabled, which provides the original
intr.s semantics. The operation of the system should not be
compromised by enabling this flag, but original semantics were felt
to be a reasonable default.
6. Provide configurable, general purpose CPU biasing control of STREAMS
service procedure executions on a per-STREAM basis. Each STREAM that
exists will have its own CPU bias mask which will define the set of
CPUs that may execute that STREAM's service procedures.
This capability gives the user a finer granularity of control over
where the STREAM's service procedures are executed.
7. Fixed to work as described in memcmp() and bcmp()'s man pages.
Object To Be Replaced:
/etc/conf/cf.d/intr.s
/etc/conf/mtune.d/io
/etc/conf/mtune.d/xfs
/etc/conf/pack.d/gd/Driver.o
/etc/conf/pack.d/io/Driver.o
/etc/conf/pack.d/io/space.c
/etc/conf/pack.d/mod/Driver.o
/etc/conf/pack.d/proc/Driver.o
/etc/conf/pack.d/svc/Driver.o
/etc/conf/pack.d/uni/Driver.o
/etc/conf/pack.d/vp/stubs.c
/etc/conf/pack.d/xfs/Driver.o
/etc/conf/pack.d/xfs/space.c
/etc/conf/sdevice.d/vp
/etc/fs/xfs/mkfs
/etc/fs/xfs/mount
/usr/include/snmp/snmp.h
/usr/include/snmp/snmpio.h
/usr/include/snmp/snmpuser.h
/usr/include/snmp/snmp_trap.h
/usr/include/sys/plocal.h
/usr/include/sys/stream.h
/usr/include/sys/stropts.h
/usr/include/sys/strsubr.h
/usr/include/sys/syscx.h
/usr/include/sys/fs/xfs_dir.h
/usr/include/sys/fs/xfs_dxnode.h
/usr/include/sys/fs/xfs_filsys.h
/usr/include/sys/fs/xfs_param.h
/usr/include/sys/fs/xfs_types.h
/usr/lib/fs/xfs/mkfs
/usr/lib/fs/xfs/mount
/usr/lib/libc.so.1
/usr/lib/locale/C/MSGFILES/harris.str
/usr/ccs/lib/libc.a
/usr/ccs/lib/libc.so
Special Conditions for Installation:
NOTICE #1: With multi-initiator disk bus systems it is possible to mount
a filesystem disk on more than one host system, this is a
good way to corrupt a filesystem if both hosts are allocating
disk space and xnodes from their own cached copy of the
filesystem pages. The XFS_SYSID Mtune helps to protect
against this problem. The XFS_SYSID should be set to a value
unique on the multi-initiator disk bus, mount of an xfs
filesystem on one of the systems will then set that system's
XFS_SYSID into the superblock. Attempts to mount that
filesystem on another of the multi-initiator hosts will be
rejected unless the mount is used with the -o force option.
It is left to the user to ensure that the filesystem is not
mounted on its normal host system before using the force
option. After use of the force option the new system XFS_SYSID
is set into the superblock. If the XFS_SYSID Mtune is left at
the default value then the multi-initiator protection is not
enforced.
NOTICE #2: This patch modifies /etc/conf/cf.d/intr.s. If this file has
been modified locally, then those local changes will need to
be re-applied as necessary after the patch is installed.
NOTICE #3: The following links will also be created during installation
of base-018:
* Link to /usr/ccs/lib/libc.so
/usr/ccs/lib/libp/libc.so
Possible Side Effects:
None.
return to index
================================================================================
Concurrent Computer Corporation Software Development
Software Patch Report
Patch Name: cld-001
Date Issued: 02/09/99 09:34:13
Software Package: cld pkg (Version 4.2)
OS Release: PowerMAX OS 4.2
Architectures: moto
Platforms: Power Hawk 610/620/640, PowerStack, PowerStack II
Related Patches: base-016 (Uni-processor), base-017 (Multi-processor)
Related SARS: none
Brief Description:
PowerMAX OS 4.2 cld package release updates
Problem Description:
1. The Concurrent MPEG Decoder Driver (cld) was unable to properly
handle fast-forward files. The cld driver did not implement the
DUP_FRAME ioctl() in the original release, which is required for fast
forward and reverse files.
Problem Resolution:
1. Add ioctl() support for the DUP_FRAME function.
Object To Be Replaced:
/etc/conf/pack.d/cld/Driver.o
/etc/conf/pack.d/cld/space.c
/etc/conf/mtune.d/cld
/usr/include/sys/cld.h
Special Conditions for Installation:
None.
Possible Side Effects:
None.
return to index
================================================================================
Concurrent Computer Corporation Software Development
Software Patch Report
Patch Name: cld-001
Date Issued: 02/09/99 09:34:13
Software Package: cld pkg (Version 4.2)
OS Release: PowerMAX OS 4.2
Architectures: moto
Platforms: Power Hawk 610/620/640, PowerStack, PowerStack II
Related Patches: base-016 (Uni-processor), base-017 (Multi-processor)
Related SARS: none
Brief Description:
PowerMAX OS 4.2 cld package release updates
Problem Description:
1. The Concurrent MPEG Decoder Driver (cld) was unable to properly
handle fast-forward files. The cld driver did not implement the
DUP_FRAME ioctl() in the original release, which is required for fast
forward and reverse files.
Problem Resolution:
1. Add ioctl() support for the DUP_FRAME function.
Object To Be Replaced:
/etc/conf/pack.d/cld/Driver.o
/etc/conf/pack.d/cld/space.c
/etc/conf/mtune.d/cld
/usr/include/sys/cld.h
Special Conditions for Installation:
None.
Possible Side Effects:
None.
return to index
================================================================================
Concurrent Computer Corporation Software Development
Software Patch Report
Patch Name: cluster-001
Date Issued: 03/23/98 17:55:39
Software Package: cluster pkg (Version 4.2)
OS Release: PowerMAX OS 4.2
Architectures: moto
Platforms: Power Hawk 610, 620, PowerStack, PowerStack II
Related Patches: base-001
Related SARS: none
Brief Description:
PowerMAX OS 4.2 cluster package release updates.
Problem Description:
1. An LWP waiting for a mailbox message may not be awakened depending
upon what mailbox it is waiting for a message on and upon what
notifications have been attached to other mailboxes. Within the
kernel function sbc_deliver_message(), there is a while loop which
walks the mailbox message registry list, which is kept as an ordered
list of increasing mailbox numbers, looking for an LWP that attached
notification to the mailbox number of the incoming message. Almost
at the very bottom of the loop is the condition
"new_msg->smb_mbox_num > sm_reg->mbox_num"; if the condition is
satisfied, the loop is exited. This condition does not allow for
the registry list to be walked properly for all mailbox numbers less
than or equal to that of the incoming message.
2. Random multiprocessor (PH640) deadlocks where system freezes
when heavily using "Loosely-Coupled" vme networking.
3. The wrong error message was being returned when creating a
NFS target and the "NFS Swap Size" field was invalid.
4. Removing a target configuration using clusterconfig could result
in temporary nfs access errors for targets that are up and running.
Problem Resolution:
1. The ">" sign in the sbc_deliver_message() loop exit condition is
changed to "<" to allow the registry list to be walked properly for
all mailbox numbers less than or equal to that of the incoming
message.
2. An inappropriate interrupt level was being used for vme
message passing which was incomparable with generic
"Streams" code. Fixed the sbc/vmemsg drivers to interrupt
at IPL5 which is compatible with "Streams" modules.
3. Fixed clusterconfig to return the appropriate error message.
4. Fixed clusterconfig so that removing a target configuration
does not affect nfs operations.
Object To Be Replaced:
/etc/conf/pack.d/sbc/Driver.o
/etc/conf/pack.d/vmemsg/Driver.o
/sbin/clusterconfig
Special Conditions for Installation:
None.
Possible Side Effects:
None.
return to index
================================================================================
Concurrent Computer Corporation Software Development
Software Patch Report
Patch Name: cluster-002
Date Issued: 03/24/98 10:02:22
Software Package: cluster pkg (Version 4.2)
OS Release: PowerMAX OS 4.2
Architectures: moto
Platforms: Power Hawk 640, PowerStack II (multi-processor only)
Related Patches: base-002
Related SARS: none
Brief Description:
PowerMAX OS 4.2 cluster package release updates.
Problem Description:
1. An LWP waiting for a mailbox message may not be awakened depending
upon what mailbox it is waiting for a message on and upon what
notifications have been attached to other mailboxes. Within the
kernel function sbc_deliver_message(), there is a while loop which
walks the mailbox message registry list, which is kept as an ordered
list of increasing mailbox numbers, looking for an LWP that attached
notification to the mailbox number of the incoming message. Almost
at the very bottom of the loop is the condition
"new_msg->smb_mbox_num > sm_reg->mbox_num"; if the condition is
satisfied, the loop is exited. This condition does not allow for
the registry list to be walked properly for all mailbox numbers less
than or equal to that of the incoming message.
2. Random multiprocessor (PH640) deadlocks where system freezes
when heavily using "Loosely-Coupled" vme networking.
3. The wrong error message was being returned when creating a
NFS target and the "NFS Swap Size" field was invalid.
4. Removing a target configuration using clusterconfig could result
in temporary nfs access errors for targets that are up and running.
Problem Resolution:
1. The ">" sign in the sbc_deliver_message() loop exit condition is
changed to "<" to allow the registry list to be walked properly for
all mailbox numbers less than or equal to that of the incoming
message.
2. An inappropriate interrupt level was being used for vme
message passing which was incomparable with generic
"Streams" code. Fixed the sbc/vmemsg drivers to interrupt
at IPL5 which is compatible with "Streams" modules.
3. Fixed clusterconfig to return the appropriate error message.
4. Fixed clusterconfig so that removing a target configuration
does not affect nfs operations.
Object To Be Replaced:
/etc/conf/pack.d/sbc/Driver.o
/etc/conf/pack.d/vmemsg/Driver.o
/sbin/clusterconfig
Special Conditions for Installation:
None.
Possible Side Effects:
None.
return to index
================================================================================
Concurrent Computer Corporation Software Development
Software Patch Report
Patch Name: cluster-003
Date Issued: 06/05/98 16:11:43
Software Package: cluster pkg (Version 4.2)
OS Release: PowerMAX OS 4.2
Architectures: moto
Platforms: Power Hawk 610/620/640, PowerStack, PowerStack II
Related Patches: none
Related SARS: none
Brief Description:
PowerMAX OS 4.2 cluster package release updates
Problem Description:
1. Invoking the Update Vroot function of the clusterconfig tool results
in the following error:
UX:ln: ERROR: Cannot create <vroot_dir>/etc/./.mnt.lock: File exists
Prior to PowerMAX OS 4.2 the .mnt.lock file was treated as a regular
file. In release 4.2 changes were made to allow for faster boot
times which required special handling of this file.
Problem Resolution:
1. The .mnt.lock lock file is now ignored when the Update Vroot
function is invoked.
Object To Be Replaced:
/usr/etc/clusterconf.d/bin/mkvroot
Special Conditions for Installation:
None.
Possible Side Effects:
None.
return to index
================================================================================
Concurrent Computer Corporation Software Development
Software Patch Report
Patch Name: cluster-003
Date Issued: 06/05/98 16:11:43
Software Package: cluster pkg (Version 4.2)
OS Release: PowerMAX OS 4.2
Architectures: moto
Platforms: Power Hawk 610/620/640, PowerStack, PowerStack II
Related Patches: none
Related SARS: none
Brief Description:
PowerMAX OS 4.2 cluster package release updates
Problem Description:
1. Invoking the Update Vroot function of the clusterconfig tool results
in the following error:
UX:ln: ERROR: Cannot create <vroot_dir>/etc/./.mnt.lock: File exists
Prior to PowerMAX OS 4.2 the .mnt.lock file was treated as a regular
file. In release 4.2 changes were made to allow for faster boot
times which required special handling of this file.
Problem Resolution:
1. The .mnt.lock lock file is now ignored when the Update Vroot
function is invoked.
Object To Be Replaced:
/usr/etc/clusterconf.d/bin/mkvroot
Special Conditions for Installation:
None.
Possible Side Effects:
None.
return to index
================================================================================
Concurrent Computer Corporation Software Development
Software Patch Report
Patch Name: cluster-004
Date Issued: 08/12/98 10:20:57
Software Package: cluster pkg (Version 4.2)
OS Release: PowerMAX OS 4.2
Architectures: moto
Platforms: Power Hawk 610/620/640, PowerStack, PowerStack II
Related Patches: base-007 (Uni-processor), base-008 (Multi-processor)
Related SARS: HM12338, HM12413
Brief Description:
PowerMAX OS 4.2 cluster package release updates
Problem Description:
1. HM12338: If a target (Power Hawk CPU) is in a hardware reset state
at the exact moment that another target is probing for the presence
of other boards, the board in reset is not "seen" by the probing
board resulting in loss of vmedlpi functionality as well as SBC
driver support.
2. HM12413: Networking either fails or is slow to start-up on targets
when booting after a crash. This is because NFS file locks held by
the target are not released by the server when the target crashes.
3. Crash recovery was not performed by statd(1M) because the state files
it relied on are being removed during target initialization.
4. A target system panics when a disk is configured and an entry for
the disk controller is added to the adapters table. This is because
the target would incorrectly attempt to boot from the configured disk.
5. If the IWE subsystem is added to a target's configuration, the
target's kernel fails to link.
6. When a non-serial console is used on the host, the target's console
device file is created incorrectly.
7. VMEbus DMA Controller (DMAC) device enhancement.
The DMA Controller (DMAC) device driver enhancement provides a user
interface to the on board Tundra Universe DMAC engine allowing high
speed block-mode transfers between user memory and a VMEbus slave
device.
Problem Resolution:
1. A "smart" delay loop has been introduced in the SBC driver
initialization routine that will re-probe for targets at one second
intervals up to a configurable (via tunable) maximum number of
seconds. The "smart" part is a modification to 'sbcboot', et al,
that gives a hint to the SBC driver on what targets to expect to
find during the probing sequence. If all expected targets are
probed for, and found, the probing loop is exited before the probe
timeout occurs.
A natural extension to this type of functionality allows the user to
configure (via tunable) a mask of SBCs which it should probe for.
This now allows the user to restrict the probing of boards, as
needed by their configuration. This allows netboot a target to
effectively turn off, or limit, VMEbus probing.
2. In addition to fixes to lockd and statd to properly release locks,
the scripts changed here will circumvent NFS file locking during the
boot phase by forcing all the files locked during system
initialization to be created locally in the memfs root file system
of the target.
3. The files in /etc/sm and in /etc/sm.bak are no longer removed by
disklessboot when the target boots.
4. When the target's virtual root is generated, the kernel
configuration file <vroot>/etc/conf/sassign.d/kernel is edited and
the memory, instead of the disk device, is assigned to root and swap.
5. The new kernel modules have been added to the data file used to
configure the kernel with IWE support.
6. Changed idmknod to always generate a serial console device for
targets.
7. Added support for new DMAC driver. See related patch base-007
for uni-processor systems or base-008 for multi-processor systems.
Object To Be Replaced:
/etc/conf/bin/sbcbstrap
/etc/conf/mdevice.d/vmemsg
/etc/conf/mdevice.d/sbc
/etc/conf/mtune.d/sbc
/etc/conf/pack.d/sbc/Driver.o
/etc/conf/pack.d/sbc/space.c
/etc/conf/pack.d/vmemsg/Driver.o
/etc/init.d/disklessboot
/etc/rc0.d/K14disklessboot
/etc/rc3.d/S24disklessboot
/usr/etc/clusterconf.d/bin/mkvroot
/usr/etc/clusterconf.d/data/Subsystems/IWE/modlist
/usr/etc/clusterconf.d/data/modlist.emb
/usr/etc/clusterconf.d/data/modlist.nfs
/usr/include/sys/sbc.h
/usr/lib/idtuneobj/tune_database
/usr/sbin/sbcboot
/usr/sbin/sbcextract
/usr/sbin/sbcmkimage
/usr/share/man/cat7/sbc.7.z
/usr/share/man/man7/sbc.7
Special Conditions for Installation:
The kernels on the file server and all targets must be
running the same version. To prevent a mismatch, follow
these steps before rebooting a new kernel on the server:
1. shut down all target systems.
2. for each target, build a new kernel and boot image
but do not boot the target. You can accomplish
this using the bootarget(1M) command:
/usr/sbin/bootarget -n -r unix <vroot>
3. reboot the file server.
4. reboot the targets.
Possible Side Effects:
One or more of the systems in the cluster may hang during
booting if the kernel versions do not match.
return to index
================================================================================
Concurrent Computer Corporation Software Development
Software Patch Report
Patch Name: cluster-004
Date Issued: 08/12/98 10:20:57
Software Package: cluster pkg (Version 4.2)
OS Release: PowerMAX OS 4.2
Architectures: moto
Platforms: Power Hawk 610/620/640, PowerStack, PowerStack II
Related Patches: base-007 (Uni-processor), base-008 (Multi-processor)
Related SARS: HM12338, HM12413
Brief Description:
PowerMAX OS 4.2 cluster package release updates
Problem Description:
1. HM12338: If a target (Power Hawk CPU) is in a hardware reset state
at the exact moment that another target is probing for the presence
of other boards, the board in reset is not "seen" by the probing
board resulting in loss of vmedlpi functionality as well as SBC
driver support.
2. HM12413: Networking either fails or is slow to start-up on targets
when booting after a crash. This is because NFS file locks held by
the target are not released by the server when the target crashes.
3. Crash recovery was not performed by statd(1M) because the state files
it relied on are being removed during target initialization.
4. A target system panics when a disk is configured and an entry for
the disk controller is added to the adapters table. This is because
the target would incorrectly attempt to boot from the configured disk.
5. If the IWE subsystem is added to a target's configuration, the
target's kernel fails to link.
6. When a non-serial console is used on the host, the target's console
device file is created incorrectly.
7. VMEbus DMA Controller (DMAC) device enhancement.
The DMA Controller (DMAC) device driver enhancement provides a user
interface to the on board Tundra Universe DMAC engine allowing high
speed block-mode transfers between user memory and a VMEbus slave
device.
Problem Resolution:
1. A "smart" delay loop has been introduced in the SBC driver
initialization routine that will re-probe for targets at one second
intervals up to a configurable (via tunable) maximum number of
seconds. The "smart" part is a modification to 'sbcboot', et al,
that gives a hint to the SBC driver on what targets to expect to
find during the probing sequence. If all expected targets are
probed for, and found, the probing loop is exited before the probe
timeout occurs.
A natural extension to this type of functionality allows the user to
configure (via tunable) a mask of SBCs which it should probe for.
This now allows the user to restrict the probing of boards, as
needed by their configuration. This allows netboot a target to
effectively turn off, or limit, VMEbus probing.
2. In addition to fixes to lockd and statd to properly release locks,
the scripts changed here will circumvent NFS file locking during the
boot phase by forcing all the files locked during system
initialization to be created locally in the memfs root file system
of the target.
3. The files in /etc/sm and in /etc/sm.bak are no longer removed by
disklessboot when the target boots.
4. When the target's virtual root is generated, the kernel
configuration file <vroot>/etc/conf/sassign.d/kernel is edited and
the memory, instead of the disk device, is assigned to root and swap.
5. The new kernel modules have been added to the data file used to
configure the kernel with IWE support.
6. Changed idmknod to always generate a serial console device for
targets.
7. Added support for new DMAC driver. See related patch base-007
for uni-processor systems or base-008 for multi-processor systems.
Object To Be Replaced:
/etc/conf/bin/sbcbstrap
/etc/conf/mdevice.d/vmemsg
/etc/conf/mdevice.d/sbc
/etc/conf/mtune.d/sbc
/etc/conf/pack.d/sbc/Driver.o
/etc/conf/pack.d/sbc/space.c
/etc/conf/pack.d/vmemsg/Driver.o
/etc/init.d/disklessboot
/etc/rc0.d/K14disklessboot
/etc/rc3.d/S24disklessboot
/usr/etc/clusterconf.d/bin/mkvroot
/usr/etc/clusterconf.d/data/Subsystems/IWE/modlist
/usr/etc/clusterconf.d/data/modlist.emb
/usr/etc/clusterconf.d/data/modlist.nfs
/usr/include/sys/sbc.h
/usr/lib/idtuneobj/tune_database
/usr/sbin/sbcboot
/usr/sbin/sbcextract
/usr/sbin/sbcmkimage
/usr/share/man/cat7/sbc.7.z
/usr/share/man/man7/sbc.7
Special Conditions for Installation:
The kernels on the file server and all targets must be
running the same version. To prevent a mismatch, follow
these steps before rebooting a new kernel on the server:
1. shut down all target systems.
2. for each target, build a new kernel and boot image
but do not boot the target. You can accomplish
this using the bootarget(1M) command:
/usr/sbin/bootarget -n -r unix <vroot>
3. reboot the file server.
4. reboot the targets.
Possible Side Effects:
One or more of the systems in the cluster may hang during
booting if the kernel versions do not match.
return to index
================================================================================
Concurrent Computer Corporation Software Development
Software Patch Report
Patch Name: cluster-005
Date Issued: 09/30/98 10:48:53
Software Package: cluster pkg (Version 4.2)
OS Release: PowerMAX OS 4.2
Architectures: moto
Platforms: Power Hawk 610/620/640, PowerStack, PowerStack II
Related Patches: base-013 (Uni-processor), base-014 (Multi-processor)
Related SARS:
Brief Description:
PowerMAX OS 4.2 cluster package release updates
Problem Description:
1. New enhancements for the "cluster" software package. Support for:
* compressed kernel and memfs filesystem images in boot strap
* demand-paged memfs / (root) filesystem
* flashboot capability
Problem Resolution:
1. Support added for enhancements outlined above.
Object To Be Replaced:
/etc/conf/bin/sbcbstrap
/etc/conf/bin/sbcdbstrap
/etc/init.d/clusterboot
/etc/init.d/disklessboot
/sbin/clusterconfig
/usr/sbin/sbcboot
/usr/sbin/sbcextract
/usr/sbin/sbcmkimage
/usr/share/man/cat1/clusterconfig.1m.z
/usr/share/man/cat1/sbcboot.1m.z
/usr/share/man/cat1/sbcextract.1m.z
/usr/share/man/cat1/sbcmkimage.1m.z
/usr/share/man/cat1/sbcmon.1m.z
/usr/share/man/cat1/sbczipimage.1m.z
/usr/share/man/man1/clusterconfig.1m
/usr/share/man/man1/sbcboot.1m
/usr/share/man/man1/sbcextract.1m
/usr/share/man/man1/sbcmkimage.1m
/usr/share/man/man1/sbcmon.1m
/usr/share/man/man1/sbczipimage.1m
/usr/sbin/sbczipimage
/usr/etc/clusterconf.d/bin/bootstrap.makefile
/usr/etc/clusterconf.d/bin/mkvroot
/usr/sbin/bootarget
Special Conditions for Installation:
NOTICE #1: The kernels on the file server and all targets must be
running the same version. To prevent a mismatch, follow
these steps before rebooting a new kernel on the server:
1. Shut down all target systems.
2. For each target, build a new kernel and boot image
but do not boot the target. This can be accomplished
by using the bootarget(1M) command:
/usr/sbin/bootarget -n -r all <vroot>
3. Reboot the file server.
4. Reboot the targets.
NOTICE #2: All targets configured to be netbooted must have the netboot
configuration information located in the NVRAM of each target
updated. The following update is required, in PPCBug:
PPC1-Bug> niot
...
Boot File Load Address = 00000000? 01000000
Boot File Execution Address = 00002200? 01000000
...
Save to NonVolatile RAM (N/Y)? Y
PPC1-Bug>
NOTICE #3: A documentation change is required following installation
of cluster-005. The NIOT example on page 3-16 of the manual
"PH620/PH640 Loosely-Coupled System User's Guide"
(Pubs. number 0891070-010) should be hand-modified with the
NIOT information shown above in NOTICE #2.
Possible Side Effects:
None.
return to index
================================================================================
Concurrent Computer Corporation Software Development
Software Patch Report
Patch Name: cluster-005
Date Issued: 09/30/98 10:48:53
Software Package: cluster pkg (Version 4.2)
OS Release: PowerMAX OS 4.2
Architectures: moto
Platforms: Power Hawk 610/620/640, PowerStack, PowerStack II
Related Patches: base-013 (Uni-processor), base-014 (Multi-processor)
Related SARS:
Brief Description:
PowerMAX OS 4.2 cluster package release updates
Problem Description:
1. New enhancements for the "cluster" software package. Support for:
* compressed kernel and memfs filesystem images in boot strap
* demand-paged memfs / (root) filesystem
* flashboot capability
Problem Resolution:
1. Support added for enhancements outlined above.
Object To Be Replaced:
/etc/conf/bin/sbcbstrap
/etc/conf/bin/sbcdbstrap
/etc/init.d/clusterboot
/etc/init.d/disklessboot
/sbin/clusterconfig
/usr/sbin/sbcboot
/usr/sbin/sbcextract
/usr/sbin/sbcmkimage
/usr/share/man/cat1/clusterconfig.1m.z
/usr/share/man/cat1/sbcboot.1m.z
/usr/share/man/cat1/sbcextract.1m.z
/usr/share/man/cat1/sbcmkimage.1m.z
/usr/share/man/cat1/sbcmon.1m.z
/usr/share/man/cat1/sbczipimage.1m.z
/usr/share/man/man1/clusterconfig.1m
/usr/share/man/man1/sbcboot.1m
/usr/share/man/man1/sbcextract.1m
/usr/share/man/man1/sbcmkimage.1m
/usr/share/man/man1/sbcmon.1m
/usr/share/man/man1/sbczipimage.1m
/usr/sbin/sbczipimage
/usr/etc/clusterconf.d/bin/bootstrap.makefile
/usr/etc/clusterconf.d/bin/mkvroot
/usr/sbin/bootarget
Special Conditions for Installation:
NOTICE #1: The kernels on the file server and all targets must be
running the same version. To prevent a mismatch, follow
these steps before rebooting a new kernel on the server:
1. Shut down all target systems.
2. For each target, build a new kernel and boot image
but do not boot the target. This can be accomplished
by using the bootarget(1M) command:
/usr/sbin/bootarget -n -r all <vroot>
3. Reboot the file server.
4. Reboot the targets.
NOTICE #2: All targets configured to be netbooted must have the netboot
configuration information located in the NVRAM of each target
updated. The following update is required, in PPCBug:
PPC1-Bug> niot
...
Boot File Load Address = 00000000? 01000000
Boot File Execution Address = 00002200? 01000000
...
Save to NonVolatile RAM (N/Y)? Y
PPC1-Bug>
NOTICE #3: A documentation change is required following installation
of cluster-005. The NIOT example on page 3-16 of the manual
"PH620/PH640 Loosely-Coupled System User's Guide"
(Pubs. number 0891070-010) should be hand-modified with the
NIOT information shown above in NOTICE #2.
Possible Side Effects:
None.
return to index
================================================================================
Concurrent Computer Corporation Software Development
Software Patch Report
Patch Name: cluster-006
Date Issued: 02/09/99 09:38:21
Software Package: cluster pkg (Version 4.2)
OS Release: PowerMAX OS 4.2
Architectures: moto
Platforms: Power Hawk 610/620/640, PowerStack, PowerStack II
Related Patches: base-016 (Uni-processor), base-017 (Multi-processor)
Related SARS: none
Brief Description:
PowerMAX OS 4.2 cluster package release updates
Problem Description:
1. The IWE subsystem cannot be correctly configured on an SBC target
system.
2. With the sbcboot(1m) -F option, users of the cluster package had the
ability to burn a boot image into a target's Flash, but lacked an
equivalent ability to execute a flashed boot image under programmed
control from the host.
Problem Resolution:
1. IWE subsystem corrected as follows:
* Correct IWE metadata files so that the subsystem can be
installed.
* Fix a minor problem that causes the SBC bootstrap to
(incorrectly) select /dev/tty1 as keyboard device.
2. Added a -X option to sbcboot(1m). This option resets the specified
target and forces it to start executing the boot image previously
burned into its Flash Memory.
Object To Be Replaced:
/etc/conf/bin/sbcbstrap
/usr/etc/clusterconf.d/data/Subsystems/IWE/modlist
/usr/etc/clusterconf.d/data/Subsystems/IWE/memfs
/usr/sbin/sbcboot
/usr/share/man/cat1/sbcboot.1m.z
/usr/share/man/man1/sbcboot.1m
Special Conditions for Installation:
None.
Possible Side Effects:
None.
return to index
================================================================================
Concurrent Computer Corporation Software Development
Software Patch Report
Patch Name: cluster-006
Date Issued: 02/09/99 09:38:21
Software Package: cluster pkg (Version 4.2)
OS Release: PowerMAX OS 4.2
Architectures: moto
Platforms: Power Hawk 610/620/640, PowerStack, PowerStack II
Related Patches: base-016 (Uni-processor), base-017 (Multi-processor)
Related SARS: none
Brief Description:
PowerMAX OS 4.2 cluster package release updates
Problem Description:
1. The IWE subsystem cannot be correctly configured on an SBC target
system.
2. With the sbcboot(1m) -F option, users of the cluster package had the
ability to burn a boot image into a target's Flash, but lacked an
equivalent ability to execute a flashed boot image under programmed
control from the host.
Problem Resolution:
1. IWE subsystem corrected as follows:
* Correct IWE metadata files so that the subsystem can be
installed.
* Fix a minor problem that causes the SBC bootstrap to
(incorrectly) select /dev/tty1 as keyboard device.
2. Added a -X option to sbcboot(1m). This option resets the specified
target and forces it to start executing the boot image previously
burned into its Flash Memory.
Object To Be Replaced:
/etc/conf/bin/sbcbstrap
/usr/etc/clusterconf.d/data/Subsystems/IWE/modlist
/usr/etc/clusterconf.d/data/Subsystems/IWE/memfs
/usr/sbin/sbcboot
/usr/share/man/cat1/sbcboot.1m.z
/usr/share/man/man1/sbcboot.1m
Special Conditions for Installation:
None.
Possible Side Effects:
None.
return to index
================================================================================
Concurrent Computer Corporation Software Development
Software Patch Report
Patch Name: cmds-001
Date Issued: 06/08/98 14:16:05
Software Package: cmds pkg (Version 4.2)
OS Release: PowerMAX OS 4.2
Architectures: moto nh
Platforms: All PowerMAX OS 4.2 platforms
Related Patches: none
Related SARS: none
Brief Description:
PowerMAX OS 4.2 cmds package release updates
Problem Description:
1. Enhanced the crash(1M) command to display complete contents of
certain, critical data structures. Also fixed a few minor bugs.
Problem Resolution:
1. The crash(1M) commands eng, plocal, proc, lwp, user now let the
operator specify as many `-f' options as desired. Each additional
-f increases the amount of information displayed until the maximum
is reached. No command takes more than two -f's to reach the
maximum.
Added the -e option to the `eng' and `plocal' commands. This
displays information on all engines, one line per engine.
Fixed a bug in `plocal' that prevented it from handling an
`engine number' argument (previously it could only reliably display
data on the default engine).
The command `stack -s' now displays the raw stack of a lwp in both
hexadecimal and symbolic forms.
The command `t -e' now displays the stacks of all lwp's in the
system. Previously it just displayed the stack of default lwp for
each process. Also, `t -e' no longer bombs out when encountering
an emptly proc slot. The bad slot is silently skipped.
Adjusted the builtin `help' command of crash(1M) to be completely in
sync with the crash(1M) commands it describes.
Object To Be Replaced:
/usr/sbin/crash
Special Conditions for Installation:
The following objects are linked to some of the objects being
replaced by this patch. These objects will also be re-linked:
/etc/crash
/usr/sbin/mview
Possible Side Effects:
None.
return to index
================================================================================
Concurrent Computer Corporation Software Development
Software Patch Report
Patch Name: cmds-001
Date Issued: 06/08/98 14:16:05
Software Package: cmds pkg (Version 4.2)
OS Release: PowerMAX OS 4.2
Architectures: moto nh
Platforms: All PowerMAX OS 4.2 platforms
Related Patches: none
Related SARS: none
Brief Description:
PowerMAX OS 4.2 cmds package release updates
Problem Description:
1. Enhanced the crash(1M) command to display complete contents of
certain, critical data structures. Also fixed a few minor bugs.
Problem Resolution:
1. The crash(1M) commands eng, plocal, proc, lwp, user now let the
operator specify as many `-f' options as desired. Each additional
-f increases the amount of information displayed until the maximum
is reached. No command takes more than two -f's to reach the
maximum.
Added the -e option to the `eng' and `plocal' commands. This
displays information on all engines, one line per engine.
Fixed a bug in `plocal' that prevented it from handling an
`engine number' argument (previously it could only reliably display
data on the default engine).
The command `stack -s' now displays the raw stack of a lwp in both
hexadecimal and symbolic forms.
The command `t -e' now displays the stacks of all lwp's in the
system. Previously it just displayed the stack of default lwp for
each process. Also, `t -e' no longer bombs out when encountering
an emptly proc slot. The bad slot is silently skipped.
Adjusted the builtin `help' command of crash(1M) to be completely in
sync with the crash(1M) commands it describes.
Object To Be Replaced:
/usr/sbin/crash
Special Conditions for Installation:
The following objects are linked to some of the objects being
replaced by this patch. These objects will also be re-linked:
/etc/crash
/usr/sbin/mview
Possible Side Effects:
None.
return to index
================================================================================
Concurrent Computer Corporation Software Development
Software Patch Report
Patch Name: cmds-001
Date Issued: 06/08/98 14:16:05
Software Package: cmds pkg (Version 4.2)
OS Release: PowerMAX OS 4.2
Architectures: moto nh
Platforms: All PowerMAX OS 4.2 platforms
Related Patches: none
Related SARS: none
Brief Description:
PowerMAX OS 4.2 cmds package release updates
Problem Description:
1. Enhanced the crash(1M) command to display complete contents of
certain, critical data structures. Also fixed a few minor bugs.
Problem Resolution:
1. The crash(1M) commands eng, plocal, proc, lwp, user now let the
operator specify as many `-f' options as desired. Each additional
-f increases the amount of information displayed until the maximum
is reached. No command takes more than two -f's to reach the
maximum.
Added the -e option to the `eng' and `plocal' commands. This
displays information on all engines, one line per engine.
Fixed a bug in `plocal' that prevented it from handling an
`engine number' argument (previously it could only reliably display
data on the default engine).
The command `stack -s' now displays the raw stack of a lwp in both
hexadecimal and symbolic forms.
The command `t -e' now displays the stacks of all lwp's in the
system. Previously it just displayed the stack of default lwp for
each process. Also, `t -e' no longer bombs out when encountering
an emptly proc slot. The bad slot is silently skipped.
Adjusted the builtin `help' command of crash(1M) to be completely in
sync with the crash(1M) commands it describes.
Object To Be Replaced:
/usr/sbin/crash
Special Conditions for Installation:
The following objects are linked to some of the objects being
replaced by this patch. These objects will also be re-linked:
/etc/crash
/usr/sbin/mview
Possible Side Effects:
None.
return to index
================================================================================
Concurrent Computer Corporation Software Development
Software Patch Report
Patch Name: cmds-002
Date Issued: 09/30/98 09:08:32
Software Package: cmds pkg (Version 4.2)
OS Release: PowerMAX OS 4.2
Architectures: moto nh
Platforms: All PowerMAX OS 4.2 platforms
Related Patches: none
Related SARS: none
Brief Description:
PowerMAX OS 4.2 cmds package release updates
Problem Description:
1. Added support for the new nvram(2) system call to the truss(1)
command. Added an entry to the truss command's system call table for
the new nvram(2) system call. Each entry in this table contain a
system call name, number of arguments, and flags for each argument
that specify to truss how the argument should be displayed (hex,
decimal, string, etc.).
The nvram system call has a maximum of 4 arguments. The first
argument identifies the subcommand that was requested. The type and
number of additional arguments is dependent on the subcommand that
was requested.
Problem Resolution:
1. Enhancements detailed above.
Object To Be Replaced:
/usr/bin/truss
Special Conditions for Installation:
None.
Possible Side Effects:
None.
return to index
================================================================================
Concurrent Computer Corporation Software Development
Software Patch Report
Patch Name: cmds-002
Date Issued: 09/30/98 09:08:32
Software Package: cmds pkg (Version 4.2)
OS Release: PowerMAX OS 4.2
Architectures: moto nh
Platforms: All PowerMAX OS 4.2 platforms
Related Patches: none
Related SARS: none
Brief Description:
PowerMAX OS 4.2 cmds package release updates
Problem Description:
1. Added support for the new nvram(2) system call to the truss(1)
command. Added an entry to the truss command's system call table for
the new nvram(2) system call. Each entry in this table contain a
system call name, number of arguments, and flags for each argument
that specify to truss how the argument should be displayed (hex,
decimal, string, etc.).
The nvram system call has a maximum of 4 arguments. The first
argument identifies the subcommand that was requested. The type and
number of additional arguments is dependent on the subcommand that
was requested.
Problem Resolution:
1. Enhancements detailed above.
Object To Be Replaced:
/usr/bin/truss
Special Conditions for Installation:
None.
Possible Side Effects:
None.
return to index
================================================================================
Concurrent Computer Corporation Software Development
Software Patch Report
Patch Name: cmds-002
Date Issued: 09/30/98 09:08:32
Software Package: cmds pkg (Version 4.2)
OS Release: PowerMAX OS 4.2
Architectures: moto nh
Platforms: All PowerMAX OS 4.2 platforms
Related Patches: none
Related SARS: none
Brief Description:
PowerMAX OS 4.2 cmds package release updates
Problem Description:
1. Added support for the new nvram(2) system call to the truss(1)
command. Added an entry to the truss command's system call table for
the new nvram(2) system call. Each entry in this table contain a
system call name, number of arguments, and flags for each argument
that specify to truss how the argument should be displayed (hex,
decimal, string, etc.).
The nvram system call has a maximum of 4 arguments. The first
argument identifies the subcommand that was requested. The type and
number of additional arguments is dependent on the subcommand that
was requested.
Problem Resolution:
1. Enhancements detailed above.
Object To Be Replaced:
/usr/bin/truss
Special Conditions for Installation:
None.
Possible Side Effects:
None.
return to index
================================================================================
Concurrent Computer Corporation Software Development
Software Patch Report
Patch Name: cmds-003
Date Issued: 02/09/99 09:50:06
Software Package: cmds pkg (Version 4.2)
OS Release: PowerMAX OS 4.2
Architectures: moto nh
Platforms: All PowerMAX OS 4.2 platforms
Related Patches: base-016 (Power Hawk 610/620, PowerStack, PowerStack II),
base-017 (Power Hawk 640, PowerStack II multi-processor),
base-018 (Night Hawk 6200/6800, TurboHawk, PowerMAXION),
man-006
Related SARS: none
Brief Description:
PowerMAX OS 4.2 cmds package release updates
Problem Description:
1. Currently under PowerMAX OS, when there are pending messages that
need to be executed by a STREAMS service procedure, the STREAMS
scheduler will select the CPU(s) to execute these service procedures
based on a system-wide set of CPUs. Potentially, any CPU not in the
STRSCHED_DISABLE_MASK tunable mask may be selected to execute a
STREAMS service procedure.
For real-time systems, the above functionality does provide some
amount of shielding of STREAMS service procedures. For example,
those CPUs that are dealing with real-time critical tasks can be
placed into the STRSCHED_DISABLE_MASK, thus off-loading the task of
executing STREAMS service procedures to the non-real-time CPUs.
However, some situations may require a finer granularity of control
over STREAMS service procedure executions. This additional level of
control would be useful when it is desirable for real-time CPUs to
also execute some selectable subset of high-priority STREAMS service
procedures that are handling real-time-related STREAMS messages.
Problem Resolution:
1. Provide configurable, general purpose CPU biasing control of STREAMS
service procedure executions on a per-STREAM basis. Each STREAM that
exists will have its own CPU bias mask which will define the set of
CPUs that may execute that STREAM's service procedures.
This capability gives the user a finer granularity of control over
where each STREAM's service procedures are execute.
Object To Be Replaced:
/usr/sbin/strmuxbias
/usr/sbin/crash
Special Conditions for Installation:
The following objects are linked to some of the objects being
replaced by this patch. These objects will also be re-linked:
/etc/crash
/usr/sbin/mview
Possible Side Effects:
None.
return to index
================================================================================
Concurrent Computer Corporation Software Development
Software Patch Report
Patch Name: cmds-003
Date Issued: 02/09/99 09:50:06
Software Package: cmds pkg (Version 4.2)
OS Release: PowerMAX OS 4.2
Architectures: moto nh
Platforms: All PowerMAX OS 4.2 platforms
Related Patches: base-016 (Power Hawk 610/620, PowerStack, PowerStack II),
base-017 (Power Hawk 640, PowerStack II multi-processor),
base-018 (Night Hawk 6200/6800, TurboHawk, PowerMAXION),
man-006
Related SARS: none
Brief Description:
PowerMAX OS 4.2 cmds package release updates
Problem Description:
1. Currently under PowerMAX OS, when there are pending messages that
need to be executed by a STREAMS service procedure, the STREAMS
scheduler will select the CPU(s) to execute these service procedures
based on a system-wide set of CPUs. Potentially, any CPU not in the
STRSCHED_DISABLE_MASK tunable mask may be selected to execute a
STREAMS service procedure.
For real-time systems, the above functionality does provide some
amount of shielding of STREAMS service procedures. For example,
those CPUs that are dealing with real-time critical tasks can be
placed into the STRSCHED_DISABLE_MASK, thus off-loading the task of
executing STREAMS service procedures to the non-real-time CPUs.
However, some situations may require a finer granularity of control
over STREAMS service procedure executions. This additional level of
control would be useful when it is desirable for real-time CPUs to
also execute some selectable subset of high-priority STREAMS service
procedures that are handling real-time-related STREAMS messages.
Problem Resolution:
1. Provide configurable, general purpose CPU biasing control of STREAMS
service procedure executions on a per-STREAM basis. Each STREAM that
exists will have its own CPU bias mask which will define the set of
CPUs that may execute that STREAM's service procedures.
This capability gives the user a finer granularity of control over
where each STREAM's service procedures are execute.
Object To Be Replaced:
/usr/sbin/strmuxbias
/usr/sbin/crash
Special Conditions for Installation:
The following objects are linked to some of the objects being
replaced by this patch. These objects will also be re-linked:
/etc/crash
/usr/sbin/mview
Possible Side Effects:
None.
return to index
================================================================================
Concurrent Computer Corporation Software Development
Software Patch Report
Patch Name: cmds-003
Date Issued: 02/09/99 09:50:06
Software Package: cmds pkg (Version 4.2)
OS Release: PowerMAX OS 4.2
Architectures: moto nh
Platforms: All PowerMAX OS 4.2 platforms
Related Patches: base-016 (Power Hawk 610/620, PowerStack, PowerStack II),
base-017 (Power Hawk 640, PowerStack II multi-processor),
base-018 (Night Hawk 6200/6800, TurboHawk, PowerMAXION),
man-006
Related SARS: none
Brief Description:
PowerMAX OS 4.2 cmds package release updates
Problem Description:
1. Currently under PowerMAX OS, when there are pending messages that
need to be executed by a STREAMS service procedure, the STREAMS
scheduler will select the CPU(s) to execute these service procedures
based on a system-wide set of CPUs. Potentially, any CPU not in the
STRSCHED_DISABLE_MASK tunable mask may be selected to execute a
STREAMS service procedure.
For real-time systems, the above functionality does provide some
amount of shielding of STREAMS service procedures. For example,
those CPUs that are dealing with real-time critical tasks can be
placed into the STRSCHED_DISABLE_MASK, thus off-loading the task of
executing STREAMS service procedures to the non-real-time CPUs.
However, some situations may require a finer granularity of control
over STREAMS service procedure executions. This additional level of
control would be useful when it is desirable for real-time CPUs to
also execute some selectable subset of high-priority STREAMS service
procedures that are handling real-time-related STREAMS messages.
Problem Resolution:
1. Provide configurable, general purpose CPU biasing control of STREAMS
service procedure executions on a per-STREAM basis. Each STREAM that
exists will have its own CPU bias mask which will define the set of
CPUs that may execute that STREAM's service procedures.
This capability gives the user a finer granularity of control over
where each STREAM's service procedures are execute.
Object To Be Replaced:
/usr/sbin/strmuxbias
/usr/sbin/crash
Special Conditions for Installation:
The following objects are linked to some of the objects being
replaced by this patch. These objects will also be re-linked:
/etc/crash
/usr/sbin/mview
Possible Side Effects:
None.
return to index
================================================================================
Concurrent Computer Corporation Software Development
Software Patch Report
Patch Name: crosslibs-001
Date Issued: 06/08/98 14:17:44
Software Package: crosslibs pkg (Version 4.2)
OS Release: PowerMAX OS 4.2
Architectures: moto nh
Platforms: All PowerMAX OS 4.2 platforms
Related Patches: librt-001
Related SARS: none
Brief Description:
PowerMAX OS 4.2 crosslibs package release updates
Problem Description:
1. The real-time libraries were updated in patch librt-001 to correct
the following problems:
Environment variables are not passed to programs that are scheduled
on an FBS in the following ways:
- Ada
* PGM_Schedule()
* Sched_PGM_Add()
- C
* pgmschedule()
* sched_pgmadd()
- FORTRAN
* pgmschedule()
* schedpgmadd()
- rtcp
* sp
Problem Resolution:
1. Change the librt fbs_program() and the libF77rt schedpgmadd_()
functions to pass the parent process' environment to its child
process.
Object To Be Replaced:
/usr/lib/crosslibs/libF77rt.a
/usr/lib/crosslibs/librt.a
Special Conditions for Installation:
None.
Possible Side Effects:
None.
return to index
================================================================================
Concurrent Computer Corporation Software Development
Software Patch Report
Patch Name: crosslibs-001
Date Issued: 06/08/98 14:17:44
Software Package: crosslibs pkg (Version 4.2)
OS Release: PowerMAX OS 4.2
Architectures: moto nh
Platforms: All PowerMAX OS 4.2 platforms
Related Patches: librt-001
Related SARS: none
Brief Description:
PowerMAX OS 4.2 crosslibs package release updates
Problem Description:
1. The real-time libraries were updated in patch librt-001 to correct
the following problems:
Environment variables are not passed to programs that are scheduled
on an FBS in the following ways:
- Ada
* PGM_Schedule()
* Sched_PGM_Add()
- C
* pgmschedule()
* sched_pgmadd()
- FORTRAN
* pgmschedule()
* schedpgmadd()
- rtcp
* sp
Problem Resolution:
1. Change the librt fbs_program() and the libF77rt schedpgmadd_()
functions to pass the parent process' environment to its child
process.
Object To Be Replaced:
/usr/lib/crosslibs/libF77rt.a
/usr/lib/crosslibs/librt.a
Special Conditions for Installation:
None.
Possible Side Effects:
None.
return to index
================================================================================
Concurrent Computer Corporation Software Development
Software Patch Report
Patch Name: crosslibs-001
Date Issued: 06/08/98 14:17:44
Software Package: crosslibs pkg (Version 4.2)
OS Release: PowerMAX OS 4.2
Architectures: moto nh
Platforms: All PowerMAX OS 4.2 platforms
Related Patches: librt-001
Related SARS: none
Brief Description:
PowerMAX OS 4.2 crosslibs package release updates
Problem Description:
1. The real-time libraries were updated in patch librt-001 to correct
the following problems:
Environment variables are not passed to programs that are scheduled
on an FBS in the following ways:
- Ada
* PGM_Schedule()
* Sched_PGM_Add()
- C
* pgmschedule()
* sched_pgmadd()
- FORTRAN
* pgmschedule()
* schedpgmadd()
- rtcp
* sp
Problem Resolution:
1. Change the librt fbs_program() and the libF77rt schedpgmadd_()
functions to pass the parent process' environment to its child
process.
Object To Be Replaced:
/usr/lib/crosslibs/libF77rt.a
/usr/lib/crosslibs/librt.a
Special Conditions for Installation:
None.
Possible Side Effects:
None.
return to index
================================================================================
Concurrent Computer Corporation Software Development
Software Patch Report
Patch Name: crosslibs-002
Date Issued: 08/12/98 10:36:57
Software Package: crosslibs pkg (Version 4.2)
OS Release: PowerMAX OS 4.2
Architectures: moto nh
Platforms: All PowerMAX OS 4.2 platforms
Related Patches: base-007 (Power Hawk 610/620, PowerStack, PowerStack II),
base-008 (Power Hawk 640, PowerStack II multi-processor),
base-009 (Night Hawk 6200/6800, TurboHawk, PowerMAXION)
Related SARS: HM12322
Brief Description:
PowerMAX OS 4.2 crosslibs package release updates
Problem Description:
1. There is currently no way for a user application to get the current
ipl level.
It is not possible to get the current ipl level without also
setting the ipl level with the spl_request(3X) or spl_manage(3X)
routines.
2. HM12322: PPC Time Base Register constants for Power Hawk 620/640 and
PowerStack II in the _hair routines of libud (also known as
TIE_FREQ_RATE) are incorrect. Because the values are incorrect for
the bus clock rating for Power Hawk 620/640 and PowerStack II
architectures, time stamps from programs that link libud could be
erroneous.
Problem Resolution:
1. Add a new spl_value(3X) routine to libud that simply returns the
current ipl (architecture dependent) ipl level:
pl_t spl_value(caddr_t spl_map_address);
Where 'spl_map_address' is the address that was returned from a
previous spl_map(3X) call.
2. Modified the TIE_FREQ_RATE value returned by _hair_get_arch_info()
to be consistent with the bus clock rating for the Power Hawk
620/640 and PowerStack II architectures.
Object To Be Replaced:
/usr/lib/crosslibs/libud.a
/usr/lib/crosslibs/libud.so
Special Conditions for Installation:
None.
Possible Side Effects:
None.
return to index
================================================================================
Concurrent Computer Corporation Software Development
Software Patch Report
Patch Name: crosslibs-002
Date Issued: 08/12/98 10:36:57
Software Package: crosslibs pkg (Version 4.2)
OS Release: PowerMAX OS 4.2
Architectures: moto nh
Platforms: All PowerMAX OS 4.2 platforms
Related Patches: base-007 (Power Hawk 610/620, PowerStack, PowerStack II),
base-008 (Power Hawk 640, PowerStack II multi-processor),
base-009 (Night Hawk 6200/6800, TurboHawk, PowerMAXION)
Related SARS: HM12322
Brief Description:
PowerMAX OS 4.2 crosslibs package release updates
Problem Description:
1. There is currently no way for a user application to get the current
ipl level.
It is not possible to get the current ipl level without also
setting the ipl level with the spl_request(3X) or spl_manage(3X)
routines.
2. HM12322: PPC Time Base Register constants for Power Hawk 620/640 and
PowerStack II in the _hair routines of libud (also known as
TIE_FREQ_RATE) are incorrect. Because the values are incorrect for
the bus clock rating for Power Hawk 620/640 and PowerStack II
architectures, time stamps from programs that link libud could be
erroneous.
Problem Resolution:
1. Add a new spl_value(3X) routine to libud that simply returns the
current ipl (architecture dependent) ipl level:
pl_t spl_value(caddr_t spl_map_address);
Where 'spl_map_address' is the address that was returned from a
previous spl_map(3X) call.
2. Modified the TIE_FREQ_RATE value returned by _hair_get_arch_info()
to be consistent with the bus clock rating for the Power Hawk
620/640 and PowerStack II architectures.
Object To Be Replaced:
/usr/lib/crosslibs/libud.a
/usr/lib/crosslibs/libud.so
Special Conditions for Installation:
None.
Possible Side Effects:
None.
return to index
================================================================================
Concurrent Computer Corporation Software Development
Software Patch Report
Patch Name: crosslibs-002
Date Issued: 08/12/98 10:36:57
Software Package: crosslibs pkg (Version 4.2)
OS Release: PowerMAX OS 4.2
Architectures: moto nh
Platforms: All PowerMAX OS 4.2 platforms
Related Patches: base-007 (Power Hawk 610/620, PowerStack, PowerStack II),
base-008 (Power Hawk 640, PowerStack II multi-processor),
base-009 (Night Hawk 6200/6800, TurboHawk, PowerMAXION)
Related SARS: HM12322
Brief Description:
PowerMAX OS 4.2 crosslibs package release updates
Problem Description:
1. There is currently no way for a user application to get the current
ipl level.
It is not possible to get the current ipl level without also
setting the ipl level with the spl_request(3X) or spl_manage(3X)
routines.
2. HM12322: PPC Time Base Register constants for Power Hawk 620/640 and
PowerStack II in the _hair routines of libud (also known as
TIE_FREQ_RATE) are incorrect. Because the values are incorrect for
the bus clock rating for Power Hawk 620/640 and PowerStack II
architectures, time stamps from programs that link libud could be
erroneous.
Problem Resolution:
1. Add a new spl_value(3X) routine to libud that simply returns the
current ipl (architecture dependent) ipl level:
pl_t spl_value(caddr_t spl_map_address);
Where 'spl_map_address' is the address that was returned from a
previous spl_map(3X) call.
2. Modified the TIE_FREQ_RATE value returned by _hair_get_arch_info()
to be consistent with the bus clock rating for the Power Hawk
620/640 and PowerStack II architectures.
Object To Be Replaced:
/usr/lib/crosslibs/libud.a
/usr/lib/crosslibs/libud.so
Special Conditions for Installation:
None.
Possible Side Effects:
None.
return to index
================================================================================
Concurrent Computer Corporation Software Development
Software Patch Report
Patch Name: crosslibs-003
Date Issued: 09/30/98 09:12:19
Software Package: crosslibs pkg (Version 4.2)
OS Release: PowerMAX OS 4.2
Architectures: moto nh
Platforms: base-013 (Power Hawk 610/620, PowerStack, PowerStack II),
base-014 (Power Hawk 640, PowerStack II multi-processor),
base-015 (Night Hawk 6200/6800, TurboHawk, PowerMAXION)
Related Patches:
Related SARS:
Brief Description:
PowerMAX OS 4.2 crosslibs package release updates
Problem Description:
1. Added support for new nvram(2) system call as provided for the NVRAM
Global Environment Variable (GEV) utilities for Motorola platforms.
2. Support added for doing configuration accesses of multi-function
PCI devices.
Problem Resolution:
1. Support added to cross-libraries to accompany GEV utilities.
2. Support added to cross-libraries for cross-architecture compilation.
Object To Be Replaced:
/usr/lib/crosslibs/libc.a
/usr/lib/crosslibs/libc.so
/usr/lib/crosslibs/libc.so.1
/usr/lib/crosslibs/libud.a
/usr/lib/crosslibs/libud.so
Special Conditions for Installation:
None.
Possible Side Effects:
None.
return to index
================================================================================
Concurrent Computer Corporation Software Development
Software Patch Report
Patch Name: crosslibs-003
Date Issued: 09/30/98 09:12:19
Software Package: crosslibs pkg (Version 4.2)
OS Release: PowerMAX OS 4.2
Architectures: moto nh
Platforms: base-013 (Power Hawk 610/620, PowerStack, PowerStack II),
base-014 (Power Hawk 640, PowerStack II multi-processor),
base-015 (Night Hawk 6200/6800, TurboHawk, PowerMAXION)
Related Patches:
Related SARS:
Brief Description:
PowerMAX OS 4.2 crosslibs package release updates
Problem Description:
1. Added support for new nvram(2) system call as provided for the NVRAM
Global Environment Variable (GEV) utilities for Motorola platforms.
2. Support added for doing configuration accesses of multi-function
PCI devices.
Problem Resolution:
1. Support added to cross-libraries to accompany GEV utilities.
2. Support added to cross-libraries for cross-architecture compilation.
Object To Be Replaced:
/usr/lib/crosslibs/libc.a
/usr/lib/crosslibs/libc.so
/usr/lib/crosslibs/libc.so.1
/usr/lib/crosslibs/libud.a
/usr/lib/crosslibs/libud.so
Special Conditions for Installation:
None.
Possible Side Effects:
None.
return to index
================================================================================
Concurrent Computer Corporation Software Development
Software Patch Report
Patch Name: crosslibs-003
Date Issued: 09/30/98 09:12:19
Software Package: crosslibs pkg (Version 4.2)
OS Release: PowerMAX OS 4.2
Architectures: moto nh
Platforms: base-013 (Power Hawk 610/620, PowerStack, PowerStack II),
base-014 (Power Hawk 640, PowerStack II multi-processor),
base-015 (Night Hawk 6200/6800, TurboHawk, PowerMAXION)
Related Patches:
Related SARS:
Brief Description:
PowerMAX OS 4.2 crosslibs package release updates
Problem Description:
1. Added support for new nvram(2) system call as provided for the NVRAM
Global Environment Variable (GEV) utilities for Motorola platforms.
2. Support added for doing configuration accesses of multi-function
PCI devices.
Problem Resolution:
1. Support added to cross-libraries to accompany GEV utilities.
2. Support added to cross-libraries for cross-architecture compilation.
Object To Be Replaced:
/usr/lib/crosslibs/libc.a
/usr/lib/crosslibs/libc.so
/usr/lib/crosslibs/libc.so.1
/usr/lib/crosslibs/libud.a
/usr/lib/crosslibs/libud.so
Special Conditions for Installation:
None.
Possible Side Effects:
None.
return to index
================================================================================
Concurrent Computer Corporation Software Development
Software Patch Report
Patch Name: crosslibs-004
Date Issued: 02/09/99 09:53:43
Software Package: crosslibs pkg (Version 4.2)
OS Release: PowerMAX OS 4.2
Architectures: moto nh
Platforms: All PowerMAX OS 4.2 platforms
Related Patches: base-016 (Power Hawk 610/620, PowerStack, PowerStack II),
base-017 (Power Hawk 640, PowerStack II multi-processor),
base-018 (Night Hawk 6200/6800, TurboHawk, PowerMAXION)
Related SARS: HM12546, HM12442
Brief Description:
PowerMAX OS 4.2 crosslibs package release updates
Problem Description:
1. HM12546: Values returned by clock_gettime() on Motorola machines
would be inaccurate. This was especially true when the tunable
HIGHRESTIMING was enabled.
2. HM12442: memcmp() is supposed to return < = or > 0 based on the
comparison of the input data, but there are cases where it returns
wrong results. bcmp() had similar problems.
Problem Resolution:
1. Correct kernel interval timer assist page so that update is only
done twice per second. Make corrections for handling rollover
(i.e. when lower portion of time-base-register resets to zero).
Fix computational errors so that all time-base-register ticks are
accounted for.
2. Fixed to work as described in memcmp() and bcmp()'s man pages.
Object To Be Replaced:
/usr/lib/crosslibs/libc.a
/usr/lib/crosslibs/libc.so
/usr/lib/crosslibs/libc.so.1
Special Conditions for Installation:
None.
Possible Side Effects:
None.
return to index
================================================================================
Concurrent Computer Corporation Software Development
Software Patch Report
Patch Name: crosslibs-004
Date Issued: 02/09/99 09:53:43
Software Package: crosslibs pkg (Version 4.2)
OS Release: PowerMAX OS 4.2
Architectures: moto nh
Platforms: All PowerMAX OS 4.2 platforms
Related Patches: base-016 (Power Hawk 610/620, PowerStack, PowerStack II),
base-017 (Power Hawk 640, PowerStack II multi-processor),
base-018 (Night Hawk 6200/6800, TurboHawk, PowerMAXION)
Related SARS: HM12546, HM12442
Brief Description:
PowerMAX OS 4.2 crosslibs package release updates
Problem Description:
1. HM12546: Values returned by clock_gettime() on Motorola machines
would be inaccurate. This was especially true when the tunable
HIGHRESTIMING was enabled.
2. HM12442: memcmp() is supposed to return < = or > 0 based on the
comparison of the input data, but there are cases where it returns
wrong results. bcmp() had similar problems.
Problem Resolution:
1. Correct kernel interval timer assist page so that update is only
done twice per second. Make corrections for handling rollover
(i.e. when lower portion of time-base-register resets to zero).
Fix computational errors so that all time-base-register ticks are
accounted for.
2. Fixed to work as described in memcmp() and bcmp()'s man pages.
Object To Be Replaced:
/usr/lib/crosslibs/libc.a
/usr/lib/crosslibs/libc.so
/usr/lib/crosslibs/libc.so.1
Special Conditions for Installation:
None.
Possible Side Effects:
None.
return to index
================================================================================
Concurrent Computer Corporation Software Development
Software Patch Report
Patch Name: crosslibs-004
Date Issued: 02/09/99 09:53:43
Software Package: crosslibs pkg (Version 4.2)
OS Release: PowerMAX OS 4.2
Architectures: moto nh
Platforms: All PowerMAX OS 4.2 platforms
Related Patches: base-016 (Power Hawk 610/620, PowerStack, PowerStack II),
base-017 (Power Hawk 640, PowerStack II multi-processor),
base-018 (Night Hawk 6200/6800, TurboHawk, PowerMAXION)
Related SARS: HM12546, HM12442
Brief Description:
PowerMAX OS 4.2 crosslibs package release updates
Problem Description:
1. HM12546: Values returned by clock_gettime() on Motorola machines
would be inaccurate. This was especially true when the tunable
HIGHRESTIMING was enabled.
2. HM12442: memcmp() is supposed to return < = or > 0 based on the
comparison of the input data, but there are cases where it returns
wrong results. bcmp() had similar problems.
Problem Resolution:
1. Correct kernel interval timer assist page so that update is only
done twice per second. Make corrections for handling rollover
(i.e. when lower portion of time-base-register resets to zero).
Fix computational errors so that all time-base-register ticks are
accounted for.
2. Fixed to work as described in memcmp() and bcmp()'s man pages.
Object To Be Replaced:
/usr/lib/crosslibs/libc.a
/usr/lib/crosslibs/libc.so
/usr/lib/crosslibs/libc.so.1
Special Conditions for Installation:
None.
Possible Side Effects:
None.
return to index
================================================================================
Concurrent Computer Corporation Software Development
Software Patch Report
Patch Name: crypt-001
Date Issued: 08/12/98 10:39:58
Software Package: crypt pkg (Version 4.2)
OS Release: PowerMAX OS 4.2
Architectures: moto nh
Platforms: All PowerMAX OS 4.2 platforms
Related Patches: base-007 (Power Hawk 610/620, PowerStack, PowerStack II),
base-008 (Power Hawk 640, PowerStack II multi-processor),
base-009 (Night Hawk 6200/6800, TurboHawk, PowerMAXION),
inet-005
Related SARS: HM12429
Brief Description:
PowerMAX OS 4.2 crypt package release updates
Problem Description:
1. HM12429: Some of the socket library routines may internally change
the user's signal disposition of SIGPOLL to SIG_IGN (ignore the
signal) and never change it back to its original disposition.
This problem will occur when these routines are called while the
SIGPOLL signal is currently being held/masked in the calling LWP's
signal mask.
Problem Resolution:
1. Change the appropriate libsocket routines so that they do not change
the process's signal disposition for the SIGPOLL signal.
Object To Be Replaced:
/usr/lib/libnsl_d.a
Special Conditions for Installation:
NOTICE #1: The following objects are linked to the object being replaced
by this patch. These objects will also be re-linked:
/usr/lib/libnsl.a
/usr/lib/libxti.a
/usr/lib/libsocket.a
NOTICE #2: If inet-005 has already been installed on this system, it is
recommended that it be removed (via pkgrm(1M)) and
re-installed (pkgadd(1M)) following installation of this
patch to ensure that /usr/lib/libresolv.a is linked to the
correct version of /usr/lib/libnsl.a.
Possible Side Effects:
None.
return to index
================================================================================
Concurrent Computer Corporation Software Development
Software Patch Report
Patch Name: crypt-001
Date Issued: 08/12/98 10:39:58
Software Package: crypt pkg (Version 4.2)
OS Release: PowerMAX OS 4.2
Architectures: moto nh
Platforms: All PowerMAX OS 4.2 platforms
Related Patches: base-007 (Power Hawk 610/620, PowerStack, PowerStack II),
base-008 (Power Hawk 640, PowerStack II multi-processor),
base-009 (Night Hawk 6200/6800, TurboHawk, PowerMAXION),
inet-005
Related SARS: HM12429
Brief Description:
PowerMAX OS 4.2 crypt package release updates
Problem Description:
1. HM12429: Some of the socket library routines may internally change
the user's signal disposition of SIGPOLL to SIG_IGN (ignore the
signal) and never change it back to its original disposition.
This problem will occur when these routines are called while the
SIGPOLL signal is currently being held/masked in the calling LWP's
signal mask.
Problem Resolution:
1. Change the appropriate libsocket routines so that they do not change
the process's signal disposition for the SIGPOLL signal.
Object To Be Replaced:
/usr/lib/libnsl_d.a
Special Conditions for Installation:
NOTICE #1: The following objects are linked to the object being replaced
by this patch. These objects will also be re-linked:
/usr/lib/libnsl.a
/usr/lib/libxti.a
/usr/lib/libsocket.a
NOTICE #2: If inet-005 has already been installed on this system, it is
recommended that it be removed (via pkgrm(1M)) and
re-installed (pkgadd(1M)) following installation of this
patch to ensure that /usr/lib/libresolv.a is linked to the
correct version of /usr/lib/libnsl.a.
Possible Side Effects:
None.
return to index
================================================================================
Concurrent Computer Corporation Software Development
Software Patch Report
Patch Name: crypt-001
Date Issued: 08/12/98 10:39:58
Software Package: crypt pkg (Version 4.2)
OS Release: PowerMAX OS 4.2
Architectures: moto nh
Platforms: All PowerMAX OS 4.2 platforms
Related Patches: base-007 (Power Hawk 610/620, PowerStack, PowerStack II),
base-008 (Power Hawk 640, PowerStack II multi-processor),
base-009 (Night Hawk 6200/6800, TurboHawk, PowerMAXION),
inet-005
Related SARS: HM12429
Brief Description:
PowerMAX OS 4.2 crypt package release updates
Problem Description:
1. HM12429: Some of the socket library routines may internally change
the user's signal disposition of SIGPOLL to SIG_IGN (ignore the
signal) and never change it back to its original disposition.
This problem will occur when these routines are called while the
SIGPOLL signal is currently being held/masked in the calling LWP's
signal mask.
Problem Resolution:
1. Change the appropriate libsocket routines so that they do not change
the process's signal disposition for the SIGPOLL signal.
Object To Be Replaced:
/usr/lib/libnsl_d.a
Special Conditions for Installation:
NOTICE #1: The following objects are linked to the object being replaced
by this patch. These objects will also be re-linked:
/usr/lib/libnsl.a
/usr/lib/libxti.a
/usr/lib/libsocket.a
NOTICE #2: If inet-005 has already been installed on this system, it is
recommended that it be removed (via pkgrm(1M)) and
re-installed (pkgadd(1M)) following installation of this
patch to ensure that /usr/lib/libresolv.a is linked to the
correct version of /usr/lib/libnsl.a.
Possible Side Effects:
None.
return to index
================================================================================
Concurrent Computer Corporation Software Development
Software Patch Report
Patch Name: crypt-002
Date Issued: 09/30/98 09:29:32
Software Package: crypt pkg (Version 4.2)
OS Release: PowerMAX OS 4.2
Architectures: moto nh
Platforms: All PowerMAX OS platforms
Related Patches: base-013 (Power Hawk 610/620, PowerStack, PowerStack II),
base-014 (Power Hawk 640, PowerStack II multi-processor),
base-015 (Night Hawk 6200/6800, TurboHawk, PowerMAXION),
crypt-int-001, inet-006
Related SARS: HM12429
Brief Description:
PowerMAX OS 4.2 crypt package release updates
Problem Description:
1. A clnt_create() call followed by a clnt_destroy() call leaves memory
allocated during the clnt_create() unfree'd. This problem could
eventually result in an "out of memory" condition.
Problem Resolution:
1. For the problem described memory leaks were corrected in libnsl in
_rpcb_findaddr(), clnt_tp_create(), and getclnthandle() routines.
All allocated memory that was previously unfree'd is now free'd
properly.
Object To Be Replaced:
/usr/lib/libnsl_d.a
/usr/lib/libnsl_d.so
Special Conditions for Installation:
NOTICE #1: The following objects are linked to the object being replaced
by this patch. These objects will also be re-linked:
/usr/lib/libnsl.a
/usr/lib/libxti.a
/usr/lib/libsocket.a
/usr/lib/libnsl.so
/usr/lib/libxti.so
NOTICE #2: If inet-006 has already been installed on this system, it is
recommended that it be removed (via pkgrm(1M)) and
re-installed (pkgadd(1M)) following installation of this
patch to ensure that /usr/lib/libresolv.a is linked to the
correct version of /usr/lib/libnsl.a.
Possible Side Effects:
None.
return to index
================================================================================
Concurrent Computer Corporation Software Development
Software Patch Report
Patch Name: crypt-002
Date Issued: 09/30/98 09:29:32
Software Package: crypt pkg (Version 4.2)
OS Release: PowerMAX OS 4.2
Architectures: moto nh
Platforms: All PowerMAX OS platforms
Related Patches: base-013 (Power Hawk 610/620, PowerStack, PowerStack II),
base-014 (Power Hawk 640, PowerStack II multi-processor),
base-015 (Night Hawk 6200/6800, TurboHawk, PowerMAXION),
crypt-int-001, inet-006
Related SARS: HM12429
Brief Description:
PowerMAX OS 4.2 crypt package release updates
Problem Description:
1. A clnt_create() call followed by a clnt_destroy() call leaves memory
allocated during the clnt_create() unfree'd. This problem could
eventually result in an "out of memory" condition.
Problem Resolution:
1. For the problem described memory leaks were corrected in libnsl in
_rpcb_findaddr(), clnt_tp_create(), and getclnthandle() routines.
All allocated memory that was previously unfree'd is now free'd
properly.
Object To Be Replaced:
/usr/lib/libnsl_d.a
/usr/lib/libnsl_d.so
Special Conditions for Installation:
NOTICE #1: The following objects are linked to the object being replaced
by this patch. These objects will also be re-linked:
/usr/lib/libnsl.a
/usr/lib/libxti.a
/usr/lib/libsocket.a
/usr/lib/libnsl.so
/usr/lib/libxti.so
NOTICE #2: If inet-006 has already been installed on this system, it is
recommended that it be removed (via pkgrm(1M)) and
re-installed (pkgadd(1M)) following installation of this
patch to ensure that /usr/lib/libresolv.a is linked to the
correct version of /usr/lib/libnsl.a.
Possible Side Effects:
None.
return to index
================================================================================
Concurrent Computer Corporation Software Development
Software Patch Report
Patch Name: crypt-002
Date Issued: 09/30/98 09:29:32
Software Package: crypt pkg (Version 4.2)
OS Release: PowerMAX OS 4.2
Architectures: moto nh
Platforms: All PowerMAX OS platforms
Related Patches: base-013 (Power Hawk 610/620, PowerStack, PowerStack II),
base-014 (Power Hawk 640, PowerStack II multi-processor),
base-015 (Night Hawk 6200/6800, TurboHawk, PowerMAXION),
crypt-int-001, inet-006
Related SARS: HM12429
Brief Description:
PowerMAX OS 4.2 crypt package release updates
Problem Description:
1. A clnt_create() call followed by a clnt_destroy() call leaves memory
allocated during the clnt_create() unfree'd. This problem could
eventually result in an "out of memory" condition.
Problem Resolution:
1. For the problem described memory leaks were corrected in libnsl in
_rpcb_findaddr(), clnt_tp_create(), and getclnthandle() routines.
All allocated memory that was previously unfree'd is now free'd
properly.
Object To Be Replaced:
/usr/lib/libnsl_d.a
/usr/lib/libnsl_d.so
Special Conditions for Installation:
NOTICE #1: The following objects are linked to the object being replaced
by this patch. These objects will also be re-linked:
/usr/lib/libnsl.a
/usr/lib/libxti.a
/usr/lib/libsocket.a
/usr/lib/libnsl.so
/usr/lib/libxti.so
NOTICE #2: If inet-006 has already been installed on this system, it is
recommended that it be removed (via pkgrm(1M)) and
re-installed (pkgadd(1M)) following installation of this
patch to ensure that /usr/lib/libresolv.a is linked to the
correct version of /usr/lib/libnsl.a.
Possible Side Effects:
None.
return to index
================================================================================
Concurrent Computer Corporation Software Development
Software Patch Report
Patch Name: crypt-int-001
Date Issued: 09/30/98 09:38:46
Software Package: crypt-int pkg (Version 4.2)
OS Release: PowerMAX OS 4.2
Architectures: moto nh
Platforms: All PowerMAX OS platforms
Related Patches: base-013 (Power Hawk 610/620, PowerStack, PowerStack II),
base-014 (Power Hawk 640, PowerStack II multi-processor),
base-015 (Night Hawk 6200/6800, TurboHawk, PowerMAXION),
crypt-002, inet-006
Related SARS:
Brief Description:
PowerMAX OS 4.2 crypt-int package release updates
Problem Description:
1. A clnt_create() call followed by a clnt_destroy() call leaves memory
allocated during the clnt_create() unfree'd. This problem could
eventually result in an "out of memory" condition.
Problem Resolution:
1. For the problem described memory leaks were corrected in libnsl in
_rpcb_findaddr(), clnt_tp_create(), and getclnthandle() routines.
All allocated memory that was previously unfree'd is now free'd
properly.
Object To Be Replaced:
/usr/lib/libnsl_i.so
Special Conditions for Installation:
NOTICE #1: The following object is linked to the object being replaced
by this patch. This object will also be re-linked:
/usr/lib/libnsl.so
NOTICE #2: If inet-006 has already been installed on this system, it is
recommended that it be removed (via pkgrm(1M)) and
re-installed (pkgadd(1M)) following installation of this
patch to ensure that /usr/lib/libresolv.a is linked to the
correct version of /usr/lib/libnsl.a.
Possible Side Effects:
None.
return to index
================================================================================
Concurrent Computer Corporation Software Development
Software Patch Report
Patch Name: crypt-int-001
Date Issued: 09/30/98 09:38:46
Software Package: crypt-int pkg (Version 4.2)
OS Release: PowerMAX OS 4.2
Architectures: moto nh
Platforms: All PowerMAX OS platforms
Related Patches: base-013 (Power Hawk 610/620, PowerStack, PowerStack II),
base-014 (Power Hawk 640, PowerStack II multi-processor),
base-015 (Night Hawk 6200/6800, TurboHawk, PowerMAXION),
crypt-002, inet-006
Related SARS:
Brief Description:
PowerMAX OS 4.2 crypt-int package release updates
Problem Description:
1. A clnt_create() call followed by a clnt_destroy() call leaves memory
allocated during the clnt_create() unfree'd. This problem could
eventually result in an "out of memory" condition.
Problem Resolution:
1. For the problem described memory leaks were corrected in libnsl in
_rpcb_findaddr(), clnt_tp_create(), and getclnthandle() routines.
All allocated memory that was previously unfree'd is now free'd
properly.
Object To Be Replaced:
/usr/lib/libnsl_i.so
Special Conditions for Installation:
NOTICE #1: The following object is linked to the object being replaced
by this patch. This object will also be re-linked:
/usr/lib/libnsl.so
NOTICE #2: If inet-006 has already been installed on this system, it is
recommended that it be removed (via pkgrm(1M)) and
re-installed (pkgadd(1M)) following installation of this
patch to ensure that /usr/lib/libresolv.a is linked to the
correct version of /usr/lib/libnsl.a.
Possible Side Effects:
None.
return to index
================================================================================
Concurrent Computer Corporation Software Development
Software Patch Report
Patch Name: crypt-int-001
Date Issued: 09/30/98 09:38:46
Software Package: crypt-int pkg (Version 4.2)
OS Release: PowerMAX OS 4.2
Architectures: moto nh
Platforms: All PowerMAX OS platforms
Related Patches: base-013 (Power Hawk 610/620, PowerStack, PowerStack II),
base-014 (Power Hawk 640, PowerStack II multi-processor),
base-015 (Night Hawk 6200/6800, TurboHawk, PowerMAXION),
crypt-002, inet-006
Related SARS:
Brief Description:
PowerMAX OS 4.2 crypt-int package release updates
Problem Description:
1. A clnt_create() call followed by a clnt_destroy() call leaves memory
allocated during the clnt_create() unfree'd. This problem could
eventually result in an "out of memory" condition.
Problem Resolution:
1. For the problem described memory leaks were corrected in libnsl in
_rpcb_findaddr(), clnt_tp_create(), and getclnthandle() routines.
All allocated memory that was previously unfree'd is now free'd
properly.
Object To Be Replaced:
/usr/lib/libnsl_i.so
Special Conditions for Installation:
NOTICE #1: The following object is linked to the object being replaced
by this patch. This object will also be re-linked:
/usr/lib/libnsl.so
NOTICE #2: If inet-006 has already been installed on this system, it is
recommended that it be removed (via pkgrm(1M)) and
re-installed (pkgadd(1M)) following installation of this
patch to ensure that /usr/lib/libresolv.a is linked to the
correct version of /usr/lib/libnsl.a.
Possible Side Effects:
None.
return to index
================================================================================
Concurrent Computer Corporation Software Development
Software Patch Report
Patch Name: dec-001
Date Issued: 03/23/98 17:54:45
Software Package: dec pkg (Version 4.2)
OS Release: PowerMAX OS 4.2
Architectures: moto
Platforms: Power Hawk 610, 620, PowerStack, PowerStack II
Related Patches: none
Related SARS: none
Brief Description:
PowerMAX OS 4.2 dec package release updates.
Problem Description:
1. Embedded PCI DEC Ethernet controllers models DC21140A (Power Hawks)
and DC21143 (TurboHAWKs) experienced excessive number of network
collisions when running in 10baseT mode. This affected the
throughput of data on these controllers.
Problem Resolution:
1. DEC controller CSR registers 6 and 15 were modified to reduce
the excessive collision problem seen when running 10baseT.
Bits 17 and 13, capture effect enable and special capture effect
enable, were set in CSR6. Bit 2, jabber clock, was set in CSR15.
Object To Be Replaced:
/etc/conf/pack.d/dec/Driver.o
/usr/include/sys/dec.h
Special Conditions for Installation:
None.
Possible Side Effects:
None.
return to index
================================================================================
Concurrent Computer Corporation Software Development
Software Patch Report
Patch Name: dec-002
Date Issued: 03/24/98 10:00:30
Software Package: dec pkg (Version 4.2)
OS Release: PowerMAX OS 4.2
Architectures: moto
Platforms: Power Hawk 640, PowerStack II (multi-processor only)
Related Patches: none
Related SARS: none
Brief Description:
PowerMAX OS 4.2 dec package release updates.
Problem Description:
1. Embedded PCI DEC Ethernet controllers models DC21140A (Power Hawks)
and DC21143 (TurboHAWKs) experienced excessive number of network
collisions when running in 10baseT mode. This affected the
throughput of data on these controllers.
Problem Resolution:
1. DEC controller CSR registers 6 and 15 were modified to reduce
the excessive collision problem seen when running 10baseT.
Bits 17 and 13, capture effect enable and special capture effect
enable, were set in CSR6. Bit 2, jabber clock, was set in CSR15.
Object To Be Replaced:
/etc/conf/pack.d/dec/Driver.o
/usr/include/sys/dec.h
Special Conditions for Installation:
None.
Possible Side Effects:
None.
return to index
================================================================================
Concurrent Computer Corporation Software Development
Software Patch Report
Patch Name: dec-003
Date Issued: 03/24/98 10:23:06
Software Package: dec pkg (Version 4.2)
OS Release: PowerMAX OS 4.2
Architectures: nh
Platforms: Night Hawk 6200/6800, Night Hawk 6800 Turbo, PowerMAXION
Related Patches: none
Related SARS: none
Brief Description:
PowerMAX OS 4.2 dec package release updates.
Problem Description:
1. Embedded PCI DEC Ethernet controllers models DC21140A (Power Hawks)
and DC21143 (TurboHAWKs) experienced excessive number of network
collisions when running in 10baseT mode. This affected the
throughput of data on these controllers.
Problem Resolution:
1. DEC controller CSR registers 6 and 15 were modified to reduce
the excessive collision problem seen when running 10baseT.
Bits 17 and 13, capture effect enable and special capture effect
enable, were set in CSR6. Bit 2, jabber clock, was set in CSR15.
Object To Be Replaced:
/etc/conf/pack.d/dec/Driver.o
/usr/include/sys/dec.h
Special Conditions for Installation:
None.
Possible Side Effects:
None.
return to index
================================================================================
Concurrent Computer Corporation Software Development
Software Patch Report
Patch Name: dec-004
Date Issued: 06/05/98 15:04:54
Software Package: dec pkg (Version 4.2)
OS Release: PowerMAX OS 4.2
Architectures: moto
Platforms: Power Hawk 610/620/640, PowerStack, PowerStack II
Related Patches: none
Related SARS: HM12405
Brief Description:
PowerMAX OS 4.2 dec package release updates
Problem Description:
1. SAR HM12405: DEC Ethernet controllers were not configuring reliably
on 100bT networks.
Problem Resolution:
1. The initialization of the DEC Ethernet command moded register was
corrected.
Object To Be Replaced:
/etc/conf/pack.d/dec/Driver.o
Special Conditions for Installation:
None.
Possible Side Effects:
None.
return to index
================================================================================
Concurrent Computer Corporation Software Development
Software Patch Report
Patch Name: dec-004
Date Issued: 06/05/98 15:04:54
Software Package: dec pkg (Version 4.2)
OS Release: PowerMAX OS 4.2
Architectures: moto
Platforms: Power Hawk 610/620/640, PowerStack, PowerStack II
Related Patches: none
Related SARS: HM12405
Brief Description:
PowerMAX OS 4.2 dec package release updates
Problem Description:
1. SAR HM12405: DEC Ethernet controllers were not configuring reliably
on 100bT networks.
Problem Resolution:
1. The initialization of the DEC Ethernet command moded register was
corrected.
Object To Be Replaced:
/etc/conf/pack.d/dec/Driver.o
Special Conditions for Installation:
None.
Possible Side Effects:
None.
return to index
================================================================================
Concurrent Computer Corporation Software Development
Software Patch Report
Patch Name: dec-005
Date Issued: 06/05/98 15:06:41
Software Package: dec pkg (Version 4.2)
OS Release: PowerMAX OS 4.2
Architectures: nh
Platforms: Night Hawk 6200/6800, TurboHawk, PowerMAXION
Related Patches: ncr-001, base-006
Related SARS: HM12405
Brief Description:
PowerMAX OS 4.2 dec package release updates
Problem Description:
1. SAR HM12405: DEC Ethernet controllers were not configuring reliably
on 100bT networks.
2. TurboHawk system hardware was modified to increase the PCI bus
throughput. The software did not support these changes.
Problem Resolution:
1. The initialization of the DEC Ethernet command moded register was
corrected.
2. Modified the initialization of the PLX Bridge, the Tundra VME
interface, embedded DEC Ethernet controller and embedded NCR SCSI
controller. This change allowed the Operating System to take
advantage of hardware changes on TurboHawk systems for increased PCI
bus throughput.
Object To Be Replaced:
/etc/conf/pack.d/dec/Driver.o
Special Conditions for Installation:
None.
Possible Side Effects:
None.
return to index
================================================================================
Concurrent Computer Corporation Software Development
Software Patch Report
Patch Name: dec-006
Date Issued: 08/27/98 16:51:50
Software Package: dec pkg (Version 4.2)
OS Release: PowerMAX OS 4.2
Architectures: moto nh
Platforms: All PowerMAX OS 4.2 platforms
Related Patches: none
Related SARS: none
Brief Description:
PowerMAX OS 4.2 dec package release updates
Problem Description:
1. External pci LAN cards that provide 10BaseT/100BaseT service can
offer additional network connectivity. Many such cards use DEC
controller chips, but do not fully adhere to the standards set forth
by DEC for their use (also required by Concurrent's dec LAN device
driver). The driver was enhanced to support one such pci card, the
Interphase 5524.
Problem Resolution:
1. The Interphase 5524 does not provide SROM data specific to
initialization of certain board features. The driver was enhanced to
provide this missing information based on the capabilities advertised
by the physical layer entity on the board.
Object To Be Replaced:
/etc/conf/pack.d/dec/Driver.o
Special Conditions for Installation:
None.
Possible Side Effects:
None.
return to index
================================================================================
Concurrent Computer Corporation Software Development
Software Patch Report
Patch Name: dec-006
Date Issued: 08/27/98 16:51:50
Software Package: dec pkg (Version 4.2)
OS Release: PowerMAX OS 4.2
Architectures: moto nh
Platforms: All PowerMAX OS 4.2 platforms
Related Patches: none
Related SARS: none
Brief Description:
PowerMAX OS 4.2 dec package release updates
Problem Description:
1. External pci LAN cards that provide 10BaseT/100BaseT service can
offer additional network connectivity. Many such cards use DEC
controller chips, but do not fully adhere to the standards set forth
by DEC for their use (also required by Concurrent's dec LAN device
driver). The driver was enhanced to support one such pci card, the
Interphase 5524.
Problem Resolution:
1. The Interphase 5524 does not provide SROM data specific to
initialization of certain board features. The driver was enhanced to
provide this missing information based on the capabilities advertised
by the physical layer entity on the board.
Object To Be Replaced:
/etc/conf/pack.d/dec/Driver.o
Special Conditions for Installation:
None.
Possible Side Effects:
None.
return to index
================================================================================
Concurrent Computer Corporation Software Development
Software Patch Report
Patch Name: dec-006
Date Issued: 08/27/98 16:51:50
Software Package: dec pkg (Version 4.2)
OS Release: PowerMAX OS 4.2
Architectures: moto nh
Platforms: All PowerMAX OS 4.2 platforms
Related Patches: none
Related SARS: none
Brief Description:
PowerMAX OS 4.2 dec package release updates
Problem Description:
1. External pci LAN cards that provide 10BaseT/100BaseT service can
offer additional network connectivity. Many such cards use DEC
controller chips, but do not fully adhere to the standards set forth
by DEC for their use (also required by Concurrent's dec LAN device
driver). The driver was enhanced to support one such pci card, the
Interphase 5524.
Problem Resolution:
1. The Interphase 5524 does not provide SROM data specific to
initialization of certain board features. The driver was enhanced to
provide this missing information based on the capabilities advertised
by the physical layer entity on the board.
Object To Be Replaced:
/etc/conf/pack.d/dec/Driver.o
Special Conditions for Installation:
None.
Possible Side Effects:
None.
return to index
================================================================================
Concurrent Computer Corporation Software Development
Software Patch Report
Patch Name: dec-007
Date Issued: 09/30/98 09:40:41
Software Package: dec pkg (Version 4.2)
OS Release: PowerMAX OS 4.2
Architectures: moto nh
Platforms: All PowerMAX OS 4.2 platforms
Related Patches: none
Related SARS: none
Brief Description:
PowerMAX OS 4.2 dec package release updates
Problem Description:
1. The DEC Ethernet driver did not properly decode DEC Ethernet adapter
SROM block types of 1, 3 or 5. This would prevent certain DEC
Ethernet adapters that adhere to the DEC SROM format from configuring
properly.
Problem Resolution:
1. The DEC Ethernet driver was corrected to properly interpret contents
of block types 1, 3, and 5 in the adapter's SROM.
Object To Be Replaced:
/etc/conf/pack.d/dec/Driver.o
Special Conditions for Installation:
None.
Possible Side Effects:
None.
return to index
================================================================================
Concurrent Computer Corporation Software Development
Software Patch Report
Patch Name: dec-007
Date Issued: 09/30/98 09:40:41
Software Package: dec pkg (Version 4.2)
OS Release: PowerMAX OS 4.2
Architectures: moto nh
Platforms: All PowerMAX OS 4.2 platforms
Related Patches: none
Related SARS: none
Brief Description:
PowerMAX OS 4.2 dec package release updates
Problem Description:
1. The DEC Ethernet driver did not properly decode DEC Ethernet adapter
SROM block types of 1, 3 or 5. This would prevent certain DEC
Ethernet adapters that adhere to the DEC SROM format from configuring
properly.
Problem Resolution:
1. The DEC Ethernet driver was corrected to properly interpret contents
of block types 1, 3, and 5 in the adapter's SROM.
Object To Be Replaced:
/etc/conf/pack.d/dec/Driver.o
Special Conditions for Installation:
None.
Possible Side Effects:
None.
return to index
================================================================================
Concurrent Computer Corporation Software Development
Software Patch Report
Patch Name: dec-007
Date Issued: 09/30/98 09:40:41
Software Package: dec pkg (Version 4.2)
OS Release: PowerMAX OS 4.2
Architectures: moto nh
Platforms: All PowerMAX OS 4.2 platforms
Related Patches: none
Related SARS: none
Brief Description:
PowerMAX OS 4.2 dec package release updates
Problem Description:
1. The DEC Ethernet driver did not properly decode DEC Ethernet adapter
SROM block types of 1, 3 or 5. This would prevent certain DEC
Ethernet adapters that adhere to the DEC SROM format from configuring
properly.
Problem Resolution:
1. The DEC Ethernet driver was corrected to properly interpret contents
of block types 1, 3, and 5 in the adapter's SROM.
Object To Be Replaced:
/etc/conf/pack.d/dec/Driver.o
Special Conditions for Installation:
None.
Possible Side Effects:
None.
return to index
================================================================================
Concurrent Computer Corporation Software Development
Software Patch Report
Patch Name: dec-008
Date Issued: 02/09/99 09:55:58
Software Package: dec pkg (Version 4.2)
OS Release: PowerMAX OS 4.2
Architectures: moto nh
Platforms: All PowerMAX OS 4.2 platforms
Related Patches: base-016 (Power Hawk 610/620, PowerStack, PowerStack II),
base-017 (Power Hawk 640, PowerStack II multi-processor),
base-018 (Night Hawk 6200/6800, TurboHawk, PowerMAXION)
Related SARS: none
Brief Description:
PowerMAX OS 4.2 dec package release updates
Problem Description:
1. On certain DEC Ethernet configurations with MII interfaces, such as
the Motorola PowerStack II systems with 10 or 100 Base T connections,
the driver setup logic would reduce the buffering for transmits.
This would cause occasional transmit failures, reported as Output
Errors, which were actually transmit underrun errors.
Problem Resolution:
1. Preserve previously set up buffering values when performing MII
interface setup.
Object To Be Replaced:
/etc/conf/pack.d/dec/Driver.o
Special Conditions for Installation:
None.
Possible Side Effects:
None.
return to index
================================================================================
Concurrent Computer Corporation Software Development
Software Patch Report
Patch Name: dec-008
Date Issued: 02/09/99 09:55:58
Software Package: dec pkg (Version 4.2)
OS Release: PowerMAX OS 4.2
Architectures: moto nh
Platforms: All PowerMAX OS 4.2 platforms
Related Patches: base-016 (Power Hawk 610/620, PowerStack, PowerStack II),
base-017 (Power Hawk 640, PowerStack II multi-processor),
base-018 (Night Hawk 6200/6800, TurboHawk, PowerMAXION)
Related SARS: none
Brief Description:
PowerMAX OS 4.2 dec package release updates
Problem Description:
1. On certain DEC Ethernet configurations with MII interfaces, such as
the Motorola PowerStack II systems with 10 or 100 Base T connections,
the driver setup logic would reduce the buffering for transmits.
This would cause occasional transmit failures, reported as Output
Errors, which were actually transmit underrun errors.
Problem Resolution:
1. Preserve previously set up buffering values when performing MII
interface setup.
Object To Be Replaced:
/etc/conf/pack.d/dec/Driver.o
Special Conditions for Installation:
None.
Possible Side Effects:
None.
return to index
================================================================================
Concurrent Computer Corporation Software Development
Software Patch Report
Patch Name: dec-008
Date Issued: 02/09/99 09:55:58
Software Package: dec pkg (Version 4.2)
OS Release: PowerMAX OS 4.2
Architectures: moto nh
Platforms: All PowerMAX OS 4.2 platforms
Related Patches: base-016 (Power Hawk 610/620, PowerStack, PowerStack II),
base-017 (Power Hawk 640, PowerStack II multi-processor),
base-018 (Night Hawk 6200/6800, TurboHawk, PowerMAXION)
Related SARS: none
Brief Description:
PowerMAX OS 4.2 dec package release updates
Problem Description:
1. On certain DEC Ethernet configurations with MII interfaces, such as
the Motorola PowerStack II systems with 10 or 100 Base T connections,
the driver setup logic would reduce the buffering for transmits.
This would cause occasional transmit failures, reported as Output
Errors, which were actually transmit underrun errors.
Problem Resolution:
1. Preserve previously set up buffering values when performing MII
interface setup.
Object To Be Replaced:
/etc/conf/pack.d/dec/Driver.o
Special Conditions for Installation:
None.
Possible Side Effects:
None.
return to index
================================================================================
Concurrent Computer Corporation Software Development
Software Patch Report
Patch Name: dr11w-001
Date Issued: 03/24/98 10:25:34
Software Package: dr11w pkg (Version 4.2)
OS Release: PowerMAX OS 4.2
Architectures: nh
Platforms: Night Hawk 6200/6800, Night Hawk 6800 Turbo, PowerMAXION
Related Patches: none
Related SARS: none
Brief Description:
PowerMAX OS 4.2 dr11w package release updates.
Problem Description:
1. The DR11W user level driver did not run on TurboHAWK systems.
Problem Resolution:
1. The DR11W user level driver was ported to the TurboHAWK platform.
Object To Be Replaced:
/usr/include/ud/dr11w.h
/usr/lib/libdr11w.a
/usr/sbin/drivers/dr11w/dr11wconfig
Special Conditions for Installation:
None.
Possible Side Effects:
None.
return to index
================================================================================
Concurrent Computer Corporation Software Development
Software Patch Report
Patch Name: fbs-001
Date Issued: 06/08/98 14:19:52
Software Package: fbs pkg (Version 4.2)
OS Release: PowerMAX OS 4.2
Architectures: moto nh
Platforms: All PowerMAX OS 4.2 platforms
Related Patches: librt-001, crosslibs-001
Related SARS: none
Brief Description:
PowerMAX OS 4.2 fbs package release updates
Problem Description:
1. The real time libraries were changed to pass the process' environment
when scheduling a new process on an FBS. Since rtcp is statically
linked, it needs to be linked with the new libraries in order to
allow programs scheduled with rtcp to have access to the environment.
Problem Resolution:
1. Relink rtcp with the new C real time library.
Object To Be Replaced:
/usr/bin/rtcp
Special Conditions for Installation:
None.
Possible Side Effects:
None.
return to index
================================================================================
Concurrent Computer Corporation Software Development
Software Patch Report
Patch Name: fbs-001
Date Issued: 06/08/98 14:19:52
Software Package: fbs pkg (Version 4.2)
OS Release: PowerMAX OS 4.2
Architectures: moto nh
Platforms: All PowerMAX OS 4.2 platforms
Related Patches: librt-001, crosslibs-001
Related SARS: none
Brief Description:
PowerMAX OS 4.2 fbs package release updates
Problem Description:
1. The real time libraries were changed to pass the process' environment
when scheduling a new process on an FBS. Since rtcp is statically
linked, it needs to be linked with the new libraries in order to
allow programs scheduled with rtcp to have access to the environment.
Problem Resolution:
1. Relink rtcp with the new C real time library.
Object To Be Replaced:
/usr/bin/rtcp
Special Conditions for Installation:
None.
Possible Side Effects:
None.
return to index
================================================================================
Concurrent Computer Corporation Software Development
Software Patch Report
Patch Name: fbs-001
Date Issued: 06/08/98 14:19:52
Software Package: fbs pkg (Version 4.2)
OS Release: PowerMAX OS 4.2
Architectures: moto nh
Platforms: All PowerMAX OS 4.2 platforms
Related Patches: librt-001, crosslibs-001
Related SARS: none
Brief Description:
PowerMAX OS 4.2 fbs package release updates
Problem Description:
1. The real time libraries were changed to pass the process' environment
when scheduling a new process on an FBS. Since rtcp is statically
linked, it needs to be linked with the new libraries in order to
allow programs scheduled with rtcp to have access to the environment.
Problem Resolution:
1. Relink rtcp with the new C real time library.
Object To Be Replaced:
/usr/bin/rtcp
Special Conditions for Installation:
None.
Possible Side Effects:
None.
return to index
================================================================================
Concurrent Computer Corporation Software Development
Software Patch Report
Patch Name: fd-001
Date Issued: 06/05/98 16:15:08
Software Package: fd pkg (Version 4.2)
OS Release: PowerMAX OS 4.2
Architectures: moto
Platforms: Power Hawk 610/620/640, PowerStack, PowerStack II
Related Patches: base-004/base-005, ide-001
Related SARS: HM12188
Brief Description:
PowerMAX OS 4.2 fd package release updates
Problem Description:
1. SAR HM12188: The IDE device driver introduced in PowerMAX OS 4.2
utilized the ISA interrupt levels from the floppy (irq6) and line
printer (irq7) drivers. This resulted in a non-functional floppy
driver and line printer driver on all Motorola based
platforms - even those that don't support IDE.
Problem Resolution:
1. The ISA interrupts have been reassigned to support all 4 ISA
devices: primary IDE, secondary IDE, floppy, and line printer.
New ISA irq assignments: 6=lpt, 7=fp, 10=p-ide, 14=s-ide.
Object To Be Replaced:
/usr/include/sys/fd.h
Special Conditions for Installation:
None.
Possible Side Effects:
None.
return to index
================================================================================
Concurrent Computer Corporation Software Development
Software Patch Report
Patch Name: fd-001
Date Issued: 06/05/98 16:15:08
Software Package: fd pkg (Version 4.2)
OS Release: PowerMAX OS 4.2
Architectures: moto
Platforms: Power Hawk 610/620/640, PowerStack, PowerStack II
Related Patches: base-004/base-005, ide-001
Related SARS: HM12188
Brief Description:
PowerMAX OS 4.2 fd package release updates
Problem Description:
1. SAR HM12188: The IDE device driver introduced in PowerMAX OS 4.2
utilized the ISA interrupt levels from the floppy (irq6) and line
printer (irq7) drivers. This resulted in a non-functional floppy
driver and line printer driver on all Motorola based
platforms - even those that don't support IDE.
Problem Resolution:
1. The ISA interrupts have been reassigned to support all 4 ISA
devices: primary IDE, secondary IDE, floppy, and line printer.
New ISA irq assignments: 6=lpt, 7=fp, 10=p-ide, 14=s-ide.
Object To Be Replaced:
/usr/include/sys/fd.h
Special Conditions for Installation:
None.
Possible Side Effects:
None.
return to index
================================================================================
Concurrent Computer Corporation Software Development
Software Patch Report
Patch Name: fibre-001
Date Issued: 02/09/99 09:57:10
Software Package: fibre pkg (Version 4.2)
OS Release: PowerMAX OS 4.2
Architectures: moto
Platforms: All PowerMAX OS 4.2 platforms
Related Patches: base-016 (Power Hawk 610/620, PowerStack, PowerStack II),
base-017 (Power Hawk 640, PowerStack II multi-processor)
Related SARS: none
Brief Description:
PowerMAX OS 4.2 fibre package release updates
Problem Description:
1. The fibre channel disk controller driver would panic or fail to
properly initialize the disks on the first boot following a power-up.
Subsequent boots would work fine.
Problem Resolution:
1. Add support to handle SCSI requests which take a long time (start
unit commands) and appear to timeout before actually completing.
Object To Be Replaced:
/etc/conf/pack.d/fibre/Driver.o
/etc/conf/pack.d/fibre/space.c
/etc/conf/mtune.d/fibre
/usr/include/sys/tachyon.h
/usr/include/sys/fibre.h
/sbin/fibconfig
Special Conditions for Installation:
None.
Possible Side Effects:
None.
return to index
================================================================================
Concurrent Computer Corporation Software Development
Software Patch Report
Patch Name: ide-001
Date Issued: 06/05/98 16:16:24
Software Package: ide pkg (Version 4.2)
OS Release: PowerMAX OS 4.2
Architectures: moto
Platforms: Power Hawk 610/620/640, PowerStack, PowerStack II
Related Patches: base-004/base-005, fd-001
Related SARS: none
Brief Description:
PowerMAX OS 4.2 ide package release updates
Problem Description:
1. The IDE device driver introduced in PowerMAX OS 4.2 utilized the
ISA interrupt levels from the floppy (irq6) and line printer (irq7)
drivers. This resulted in a non-functional floppy driver and line
printer driver on all Motorola based platforms - even those that
don't support IDE.
Problem Resolution:
1. The ISA interrupts have been reassigned to support all 4 ISA
devices: primary IDE, secondary IDE, floppy, and line printer.
New ISA irq assignments: 6=lpt, 7=fp, 10=p-ide, 14=s-ide.
Object To Be Replaced:
/etc/conf/pack.d/ide/Driver.o
Special Conditions for Installation:
None.
Possible Side Effects:
None.
return to index
================================================================================
Concurrent Computer Corporation Software Development
Software Patch Report
Patch Name: ide-001
Date Issued: 06/05/98 16:16:24
Software Package: ide pkg (Version 4.2)
OS Release: PowerMAX OS 4.2
Architectures: moto
Platforms: Power Hawk 610/620/640, PowerStack, PowerStack II
Related Patches: base-004/base-005, fd-001
Related SARS: none
Brief Description:
PowerMAX OS 4.2 ide package release updates
Problem Description:
1. The IDE device driver introduced in PowerMAX OS 4.2 utilized the
ISA interrupt levels from the floppy (irq6) and line printer (irq7)
drivers. This resulted in a non-functional floppy driver and line
printer driver on all Motorola based platforms - even those that
don't support IDE.
Problem Resolution:
1. The ISA interrupts have been reassigned to support all 4 ISA
devices: primary IDE, secondary IDE, floppy, and line printer.
New ISA irq assignments: 6=lpt, 7=fp, 10=p-ide, 14=s-ide.
Object To Be Replaced:
/etc/conf/pack.d/ide/Driver.o
Special Conditions for Installation:
None.
Possible Side Effects:
None.
return to index
================================================================================
Concurrent Computer Corporation Software Development
Software Patch Report
Patch Name: ie-001
Date Issued: 03/24/98 10:24:51
Software Package: ie pkg (Version 4.2)
OS Release: PowerMAX OS 4.2
Architectures: nh
Platforms: Night Hawk 6200/6800, Night Hawk 6800 Turbo, PowerMAXION
Related Patches: none
Related SARS: none
Brief Description:
PowerMAX OS 4.2 ie package release updates.
Problem Description:
1. Using the ie driver can cause memory leaks.
Problem Resolution:
1. If a message is unaligned or too fragmented, ie_transmit() uses
msgpullup() to duplicate the message and resolve these problems in the
new message. If all is well (TBDs/CBs can be allocated, the message is
successfully placed on xmit queue, etc...) the old copy of the message
is freed and the new one will be freed by the ie interrupt service
routine. However, if there are errors along the way, the new message
must be freed before returning an error code to the caller indicating
the necessity for a retransmit. This was not being done. The necessary
calls to freemsg have been added along these error paths.
Object To Be Replaced:
/etc/conf/pack.d/ie/Driver.o
Special Conditions for Installation:
None.
Possible Side Effects:
None.
return to index
================================================================================
Concurrent Computer Corporation Software Development
Software Patch Report
Patch Name: inet-001
Date Issued: 03/23/98 17:56:38
Software Package: inet pkg (Version 4.2)
OS Release: PowerMAX OS 4.2
Architectures: moto
Platforms: Power Hawk 610, 620, PowerStack, PowerStack II
Related Patches: none
Related SARS: none
Brief Description:
PowerMAX OS 4.2 inet package release updates.
Problem Description:
1. The problem is that NIS did not work; NIS sends UDP packets with
destination address 0.0.0.0, and these packets are not being sent
out on the network.
Problem Resolution:
1. The problem is resolved by removing code which discards
outgoing packets with destination address 0.0.0.0,
allowing such packets to be transmitted.
The above code was introduced to fix an earlier problem,
whereby the DNS name resolver did not respond if there was
no /etc/resolv.conf file on the system. This caused commands
using the resolver to hang for a long period of time. This
task also provides a fix for this original problem, by causing ICMP
messages in response to packets with destination address
0.0.0.0 to be returned to the sending process, instead of
being dropped.
Object To Be Replaced:
/etc/conf/pack.d/ipm/Driver.o
/etc/conf/pack.d/udpm/Driver.o
Special Conditions for Installation:
None.
Possible Side Effects:
None.
return to index
================================================================================
Concurrent Computer Corporation Software Development
Software Patch Report
Patch Name: inet-002
Date Issued: 03/24/98 10:03:30
Software Package: inet pkg (Version 4.2)
OS Release: PowerMAX OS 4.2
Architectures: moto
Platforms: Power Hawk 640, PowerStack II (multi-processor only)
Related Patches: none
Related SARS: none
Brief Description:
PowerMAX OS 4.2 inet package release updates.
Problem Description:
1. The problem is that NIS did not work; NIS sends UDP packets with
destination address 0.0.0.0, and these packets are not being sent
out on the network.
Problem Resolution:
1. The problem is resolved by removing code which discards
outgoing packets with destination address 0.0.0.0,
allowing such packets to be transmitted.
The above code was introduced to fix an earlier problem,
whereby the DNS name resolver did not respond if there was
no /etc/resolv.conf file on the system. This caused commands
using the resolver to hang for a long period of time. This
task also provides a fix for this original problem, by causing ICMP
messages in response to packets with destination address
0.0.0.0 to be returned to the sending process, instead of
being dropped.
Object To Be Replaced:
/etc/conf/pack.d/ipm/Driver.o
/etc/conf/pack.d/udpm/Driver.o
Special Conditions for Installation:
None.
Possible Side Effects:
None.
return to index
================================================================================
Concurrent Computer Corporation Software Development
Software Patch Report
Patch Name: inet-003
Date Issued: 03/24/98 10:23:58
Software Package: inet pkg (Version 4.2)
OS Release: PowerMAX OS 4.2
Architectures: nh
Platforms: Night Hawk 6200/6800, Night Hawk 6800 Turbo, PowerMAXION
Related Patches: none
Related SARS: none
Brief Description:
PowerMAX OS 4.2 inet package release updates.
Problem Description:
1. The problem is that NIS did not work; NIS sends UDP packets with
destination address 0.0.0.0, and these packets are not being sent
out on the network.
Problem Resolution:
1. The problem is resolved by removing code which discards
outgoing packets with destination address 0.0.0.0,
allowing such packets to be transmitted.
The above code was introduced to fix an earlier problem,
whereby the DNS name resolver did not respond if there was
no /etc/resolv.conf file on the system. This caused commands
using the resolver to hang for a long period of time. This
task also provides a fix for this original problem, by causing ICMP
messages in response to packets with destination address
0.0.0.0 to be returned to the sending process, instead of
being dropped.
Object To Be Replaced:
/etc/conf/pack.d/ipm/Driver.o
/etc/conf/pack.d/udpm/Driver.o
Special Conditions for Installation:
None.
Possible Side Effects:
None.
return to index
================================================================================
Concurrent Computer Corporation Software Development
Software Patch Report
Patch Name: inet-004
Date Issued: 06/05/98 15:21:07
Software Package: inet pkg (Version 4.2)
OS Release: PowerMAX OS 4.2
Architectures: moto nh
Platforms: All PowerMAX OS 4.2 platforms
Related Patches: man-001
Related SARS: HM12392
Brief Description:
PowerMAX OS 4.2 inet package release updates
Problem Description:
1. The httpd daemon was previously not available on PowerMAX OS.
2. New release of TCP/IP from Mentat fixing various problems.
(See descriptions of problems in "Problem Resolution" section below.)
3. SAR HM12392: It was not possible to use SLIP over /dev/remote. The
slattach command failed when sending a SIOCSIFFLAGS ioctl to the IP
module.
Problem Resolution:
1. The httpd daemon, configuration files, and initialization scripts
were ported to PowerMAX OS from source provided by CERN. Online
manual pages are included in the related patch, man-001.
2. The following problems are corrected with this latest release of
Mentat TCP/IP:
* Loopback multicast crash: If the loopback interface (127.0.0.1)
is selected as the interface to use for outgoing IP multicast
packets, and then the 224.0.0.1 multicast address is pinged,
the machine would crash.
* Vulnerability to the "Land Attack" security threat has been
removed. The Land Attack sends SYN packets with the same source
and destination IP addresses and the same source and destination
ports to the target system; this causes performance degradation.
* Reassembly bug: Bug in IP reassembly code handling fragments
which crossed multiple streams mblks. A crash would occur in
the reassembly timeout code because it was believed that a
complete IP header was available to use for the ICMP time
exceeded message when in fact it was not. The IP header had
mistakenly been discarded.
* Bug in IP multicast with interfaces which don't support
multicasting at the DLPI driver level (These interfaces are
identified by having the MULTI_BCAST flag set in the ifconfig
display). This applies to Ethernet and FDDI interfaces in
PowerMAX OS 4.2. It was necessary to bring an interface down
and up using ifconfig in order to enable IP multicast on that
interface. This is no longer the case.
3. The IP code was modified to recognize /dev/remote as a valid
SLIP device.
Object To Be Replaced:
/etc/httpd
/etc/httpd.conf
/etc/conf/pack.d/arpm/Driver.o
/etc/conf/pack.d/ipm/Driver.o
/etc/conf/pack.d/rawipm/Driver.o
/etc/conf/pack.d/tcpm/Driver.o
/etc/conf/pack.d/udpm/Driver.o
/etc/init.d/httpd
/etc/rc0.d/K83http
/etc/rc1.d/K83http
/etc/rc2.d/S83http
Special Conditions for Installation:
None.
Possible Side Effects:
None.
return to index
================================================================================
Concurrent Computer Corporation Software Development
Software Patch Report
Patch Name: inet-004
Date Issued: 06/05/98 15:21:07
Software Package: inet pkg (Version 4.2)
OS Release: PowerMAX OS 4.2
Architectures: moto nh
Platforms: All PowerMAX OS 4.2 platforms
Related Patches: man-001
Related SARS: HM12392
Brief Description:
PowerMAX OS 4.2 inet package release updates
Problem Description:
1. The httpd daemon was previously not available on PowerMAX OS.
2. New release of TCP/IP from Mentat fixing various problems.
(See descriptions of problems in "Problem Resolution" section below.)
3. SAR HM12392: It was not possible to use SLIP over /dev/remote. The
slattach command failed when sending a SIOCSIFFLAGS ioctl to the IP
module.
Problem Resolution:
1. The httpd daemon, configuration files, and initialization scripts
were ported to PowerMAX OS from source provided by CERN. Online
manual pages are included in the related patch, man-001.
2. The following problems are corrected with this latest release of
Mentat TCP/IP:
* Loopback multicast crash: If the loopback interface (127.0.0.1)
is selected as the interface to use for outgoing IP multicast
packets, and then the 224.0.0.1 multicast address is pinged,
the machine would crash.
* Vulnerability to the "Land Attack" security threat has been
removed. The Land Attack sends SYN packets with the same source
and destination IP addresses and the same source and destination
ports to the target system; this causes performance degradation.
* Reassembly bug: Bug in IP reassembly code handling fragments
which crossed multiple streams mblks. A crash would occur in
the reassembly timeout code because it was believed that a
complete IP header was available to use for the ICMP time
exceeded message when in fact it was not. The IP header had
mistakenly been discarded.
* Bug in IP multicast with interfaces which don't support
multicasting at the DLPI driver level (These interfaces are
identified by having the MULTI_BCAST flag set in the ifconfig
display). This applies to Ethernet and FDDI interfaces in
PowerMAX OS 4.2. It was necessary to bring an interface down
and up using ifconfig in order to enable IP multicast on that
interface. This is no longer the case.
3. The IP code was modified to recognize /dev/remote as a valid
SLIP device.
Object To Be Replaced:
/etc/httpd
/etc/httpd.conf
/etc/conf/pack.d/arpm/Driver.o
/etc/conf/pack.d/ipm/Driver.o
/etc/conf/pack.d/rawipm/Driver.o
/etc/conf/pack.d/tcpm/Driver.o
/etc/conf/pack.d/udpm/Driver.o
/etc/init.d/httpd
/etc/rc0.d/K83http
/etc/rc1.d/K83http
/etc/rc2.d/S83http
Special Conditions for Installation:
None.
Possible Side Effects:
None.
return to index
================================================================================
Concurrent Computer Corporation Software Development
Software Patch Report
Patch Name: inet-004
Date Issued: 06/05/98 15:21:07
Software Package: inet pkg (Version 4.2)
OS Release: PowerMAX OS 4.2
Architectures: moto nh
Platforms: All PowerMAX OS 4.2 platforms
Related Patches: man-001
Related SARS: HM12392
Brief Description:
PowerMAX OS 4.2 inet package release updates
Problem Description:
1. The httpd daemon was previously not available on PowerMAX OS.
2. New release of TCP/IP from Mentat fixing various problems.
(See descriptions of problems in "Problem Resolution" section below.)
3. SAR HM12392: It was not possible to use SLIP over /dev/remote. The
slattach command failed when sending a SIOCSIFFLAGS ioctl to the IP
module.
Problem Resolution:
1. The httpd daemon, configuration files, and initialization scripts
were ported to PowerMAX OS from source provided by CERN. Online
manual pages are included in the related patch, man-001.
2. The following problems are corrected with this latest release of
Mentat TCP/IP:
* Loopback multicast crash: If the loopback interface (127.0.0.1)
is selected as the interface to use for outgoing IP multicast
packets, and then the 224.0.0.1 multicast address is pinged,
the machine would crash.
* Vulnerability to the "Land Attack" security threat has been
removed. The Land Attack sends SYN packets with the same source
and destination IP addresses and the same source and destination
ports to the target system; this causes performance degradation.
* Reassembly bug: Bug in IP reassembly code handling fragments
which crossed multiple streams mblks. A crash would occur in
the reassembly timeout code because it was believed that a
complete IP header was available to use for the ICMP time
exceeded message when in fact it was not. The IP header had
mistakenly been discarded.
* Bug in IP multicast with interfaces which don't support
multicasting at the DLPI driver level (These interfaces are
identified by having the MULTI_BCAST flag set in the ifconfig
display). This applies to Ethernet and FDDI interfaces in
PowerMAX OS 4.2. It was necessary to bring an interface down
and up using ifconfig in order to enable IP multicast on that
interface. This is no longer the case.
3. The IP code was modified to recognize /dev/remote as a valid
SLIP device.
Object To Be Replaced:
/etc/httpd
/etc/httpd.conf
/etc/conf/pack.d/arpm/Driver.o
/etc/conf/pack.d/ipm/Driver.o
/etc/conf/pack.d/rawipm/Driver.o
/etc/conf/pack.d/tcpm/Driver.o
/etc/conf/pack.d/udpm/Driver.o
/etc/init.d/httpd
/etc/rc0.d/K83http
/etc/rc1.d/K83http
/etc/rc2.d/S83http
Special Conditions for Installation:
None.
Possible Side Effects:
None.
return to index
================================================================================
Concurrent Computer Corporation Software Development
Software Patch Report
Patch Name: inet-005
Date Issued: 08/12/98 11:02:02
Software Package: inet pkg (Version 4.2)
OS Release: PowerMAX OS 4.2
Architectures: moto nh
Platforms: All PowerMAX OS 4.2 platforms
Related Patches: base-007 (Power Hawk 610/620, PowerStack, PowerStack II),
base-008 (Power Hawk 640, PowerStack II multi-processor),
base-009 (Night Hawk 6200/6800, TurboHawk, PowerMAXION),
crypt-001
Related SARS: HM12406, HM12429
Brief Description:
PowerMAX OS 4.2 inet package release updates
Problem Description:
1. HM12406: Some of the ntp utilities do not work correctly:
A. The ntpdate(1M) command terminates with the error message "Pollable Event".
B. When the ntp daemon (in.xntpd) receives an incoming
message, it is killed.
These problems are caused by the fact that these utilities expect
incoming data from the network to generate a SIGIO signal. In fact,
when data is received, a SIGPOLL signal is received. So, the
correct action for incoming data is not carried out.
2. The system can hang when TCP connections are being closed. If there
are a lot of TCP connections active, and the system is busy, it is
possible for the system to go into a loop when closing a TCP
connection. The system cannot be interrupted in this loop, so the
system hangs.
3. HM12429: Due to changes to libsocket in related patches base-007,
base-008, base-009, and crypt-001, static library
/usr/lib/libresolv.a must be relinked to /usr/lib/libnsl.a.
Problem Resolution:
1. The signal handler required for incoming data is defined for the
SIGPOLL signal.
2. The code has been changed so that the system is interruptible while
it is performing the loop during connection close.
3. Hard link /usr/lib/libresolv.a to /usr/lib/libnsl.a.
Object To Be Replaced:
/etc/conf/pack.d/tcpm/Driver.o
/usr/sbin/in.xntpd
/usr/sbin/ntpdate
/usr/lib/libresolv.a
Special Conditions for Installation:
NOTICE: If crypt-001 will be installed on this system, it MUST be
installed BEFORE this patch (inet-005) to ensure that
/usr/lib/libresolv.a is linked to the correct version of
/usr/lib/libnsl.a.
Possible Side Effects:
None.
return to index
================================================================================
Concurrent Computer Corporation Software Development
Software Patch Report
Patch Name: inet-005
Date Issued: 08/12/98 11:02:02
Software Package: inet pkg (Version 4.2)
OS Release: PowerMAX OS 4.2
Architectures: moto nh
Platforms: All PowerMAX OS 4.2 platforms
Related Patches: base-007 (Power Hawk 610/620, PowerStack, PowerStack II),
base-008 (Power Hawk 640, PowerStack II multi-processor),
base-009 (Night Hawk 6200/6800, TurboHawk, PowerMAXION),
crypt-001
Related SARS: HM12406, HM12429
Brief Description:
PowerMAX OS 4.2 inet package release updates
Problem Description:
1. HM12406: Some of the ntp utilities do not work correctly:
A. The ntpdate(1M) command terminates with the error message "Pollable Event".
B. When the ntp daemon (in.xntpd) receives an incoming
message, it is killed.
These problems are caused by the fact that these utilities expect
incoming data from the network to generate a SIGIO signal. In fact,
when data is received, a SIGPOLL signal is received. So, the
correct action for incoming data is not carried out.
2. The system can hang when TCP connections are being closed. If there
are a lot of TCP connections active, and the system is busy, it is
possible for the system to go into a loop when closing a TCP
connection. The system cannot be interrupted in this loop, so the
system hangs.
3. HM12429: Due to changes to libsocket in related patches base-007,
base-008, base-009, and crypt-001, static library
/usr/lib/libresolv.a must be relinked to /usr/lib/libnsl.a.
Problem Resolution:
1. The signal handler required for incoming data is defined for the
SIGPOLL signal.
2. The code has been changed so that the system is interruptible while
it is performing the loop during connection close.
3. Hard link /usr/lib/libresolv.a to /usr/lib/libnsl.a.
Object To Be Replaced:
/etc/conf/pack.d/tcpm/Driver.o
/usr/sbin/in.xntpd
/usr/sbin/ntpdate
/usr/lib/libresolv.a
Special Conditions for Installation:
NOTICE: If crypt-001 will be installed on this system, it MUST be
installed BEFORE this patch (inet-005) to ensure that
/usr/lib/libresolv.a is linked to the correct version of
/usr/lib/libnsl.a.
Possible Side Effects:
None.
return to index
================================================================================
Concurrent Computer Corporation Software Development
Software Patch Report
Patch Name: inet-005
Date Issued: 08/12/98 11:02:02
Software Package: inet pkg (Version 4.2)
OS Release: PowerMAX OS 4.2
Architectures: moto nh
Platforms: All PowerMAX OS 4.2 platforms
Related Patches: base-007 (Power Hawk 610/620, PowerStack, PowerStack II),
base-008 (Power Hawk 640, PowerStack II multi-processor),
base-009 (Night Hawk 6200/6800, TurboHawk, PowerMAXION),
crypt-001
Related SARS: HM12406, HM12429
Brief Description:
PowerMAX OS 4.2 inet package release updates
Problem Description:
1. HM12406: Some of the ntp utilities do not work correctly:
A. The ntpdate(1M) command terminates with the error message "Pollable Event".
B. When the ntp daemon (in.xntpd) receives an incoming
message, it is killed.
These problems are caused by the fact that these utilities expect
incoming data from the network to generate a SIGIO signal. In fact,
when data is received, a SIGPOLL signal is received. So, the
correct action for incoming data is not carried out.
2. The system can hang when TCP connections are being closed. If there
are a lot of TCP connections active, and the system is busy, it is
possible for the system to go into a loop when closing a TCP
connection. The system cannot be interrupted in this loop, so the
system hangs.
3. HM12429: Due to changes to libsocket in related patches base-007,
base-008, base-009, and crypt-001, static library
/usr/lib/libresolv.a must be relinked to /usr/lib/libnsl.a.
Problem Resolution:
1. The signal handler required for incoming data is defined for the
SIGPOLL signal.
2. The code has been changed so that the system is interruptible while
it is performing the loop during connection close.
3. Hard link /usr/lib/libresolv.a to /usr/lib/libnsl.a.
Object To Be Replaced:
/etc/conf/pack.d/tcpm/Driver.o
/usr/sbin/in.xntpd
/usr/sbin/ntpdate
/usr/lib/libresolv.a
Special Conditions for Installation:
NOTICE: If crypt-001 will be installed on this system, it MUST be
installed BEFORE this patch (inet-005) to ensure that
/usr/lib/libresolv.a is linked to the correct version of
/usr/lib/libnsl.a.
Possible Side Effects:
None.
return to index
================================================================================
Concurrent Computer Corporation Software Development
Software Patch Report
Patch Name: inet-006
Date Issued: 09/30/98 09:43:07
Software Package: inet pkg (Version 4.2)
OS Release: PowerMAX OS 4.2
Architectures: moto nh
Platforms: All PowerMAX OS platforms
Related Patches: base-013 (Power Hawk 610/620, PowerStack, PowerStack II),
base-014 (Power Hawk 640, PowerStack II multi-processor),
base-015 (Night Hawk 6200/6800, TurboHawk, PowerMAXION),
crypt-002, crypt-int-001
Related SARS:
Brief Description:
PowerMAX OS 4.2 inet package release updates
Problem Description:
1. A clnt_create() call followed by a clnt_destroy() call leaves memory
allocated during the clnt_create() unfree'd. This problem could
eventually result in an "out of memory" condition.
Problem Resolution:
1. For the problem described memory leaks were corrected in libnsl in
_rpcb_findaddr(), clnt_tp_create(), and getclnthandle() routines.
All allocated memory that was previously unfree'd is now free'd
properly.
Object To Be Replaced:
/usr/lib/libresolv.a
Special Conditions for Installation:
NOTICE: If crypt-002 or crypt-int-001 will be installed on this system,
it MUST be installed BEFORE this patch (inet-006) to ensure that
/usr/lib/libresolv.a is linked to the correct version of
/usr/lib/libnsl.a.
Possible Side Effects:
None.
return to index
================================================================================
Concurrent Computer Corporation Software Development
Software Patch Report
Patch Name: inet-006
Date Issued: 09/30/98 09:43:07
Software Package: inet pkg (Version 4.2)
OS Release: PowerMAX OS 4.2
Architectures: moto nh
Platforms: All PowerMAX OS platforms
Related Patches: base-013 (Power Hawk 610/620, PowerStack, PowerStack II),
base-014 (Power Hawk 640, PowerStack II multi-processor),
base-015 (Night Hawk 6200/6800, TurboHawk, PowerMAXION),
crypt-002, crypt-int-001
Related SARS:
Brief Description:
PowerMAX OS 4.2 inet package release updates
Problem Description:
1. A clnt_create() call followed by a clnt_destroy() call leaves memory
allocated during the clnt_create() unfree'd. This problem could
eventually result in an "out of memory" condition.
Problem Resolution:
1. For the problem described memory leaks were corrected in libnsl in
_rpcb_findaddr(), clnt_tp_create(), and getclnthandle() routines.
All allocated memory that was previously unfree'd is now free'd
properly.
Object To Be Replaced:
/usr/lib/libresolv.a
Special Conditions for Installation:
NOTICE: If crypt-002 or crypt-int-001 will be installed on this system,
it MUST be installed BEFORE this patch (inet-006) to ensure that
/usr/lib/libresolv.a is linked to the correct version of
/usr/lib/libnsl.a.
Possible Side Effects:
None.
return to index
================================================================================
Concurrent Computer Corporation Software Development
Software Patch Report
Patch Name: inet-006
Date Issued: 09/30/98 09:43:07
Software Package: inet pkg (Version 4.2)
OS Release: PowerMAX OS 4.2
Architectures: moto nh
Platforms: All PowerMAX OS platforms
Related Patches: base-013 (Power Hawk 610/620, PowerStack, PowerStack II),
base-014 (Power Hawk 640, PowerStack II multi-processor),
base-015 (Night Hawk 6200/6800, TurboHawk, PowerMAXION),
crypt-002, crypt-int-001
Related SARS:
Brief Description:
PowerMAX OS 4.2 inet package release updates
Problem Description:
1. A clnt_create() call followed by a clnt_destroy() call leaves memory
allocated during the clnt_create() unfree'd. This problem could
eventually result in an "out of memory" condition.
Problem Resolution:
1. For the problem described memory leaks were corrected in libnsl in
_rpcb_findaddr(), clnt_tp_create(), and getclnthandle() routines.
All allocated memory that was previously unfree'd is now free'd
properly.
Object To Be Replaced:
/usr/lib/libresolv.a
Special Conditions for Installation:
NOTICE: If crypt-002 or crypt-int-001 will be installed on this system,
it MUST be installed BEFORE this patch (inet-006) to ensure that
/usr/lib/libresolv.a is linked to the correct version of
/usr/lib/libnsl.a.
Possible Side Effects:
None.
return to index
================================================================================
Concurrent Computer Corporation Software Development
Software Patch Report
Patch Name: inet-007
Date Issued: 02/09/99 10:00:15
Software Package: inet pkg (Version 4.2)
OS Release: PowerMAX OS 4.2
Architectures: moto
Platforms: Power Hawk 610/620/640, PowerStack, PowerStack II
Related Patches: base-016 (Power Hawk 610/620, PowerStack, PowerStack II),
base-017 (Power Hawk 640, PowerStack II multi-processor),
xfsd (4.2)
Related SARS: none
Brief Description:
PowerMAX OS 4.2 inet package release updates
Problem Description:
1. The standard SNMP libraries did not allow user processes to handle
SNMP requests from other systems. The SNMP daemons provide the
ability to have individual user processes handle specific SNMP
information requests. This is done by registering with the SNMP
daemon and passing information back and forth to it. Some of the
library routines necessary to utilize this capability had never been
included as a standard part of PowerMAX OS before.
2. Enhancements required to support new xfsd software package.
Problem Resolution:
1. Add the library routines and corrections to enable user handling of
SNMP calls.
2. Added required support for xfsd package.
Object To Be Replaced:
/usr/lib/libsnmp.so
/usr/lib/libsnmpio.so
/usr/lib/libsmux.so
/usr/sbin/in.snmpd
/etc/inet/services
Special Conditions for Installation:
None.
Possible Side Effects:
None.
return to index
================================================================================
Concurrent Computer Corporation Software Development
Software Patch Report
Patch Name: inet-007
Date Issued: 02/09/99 10:00:15
Software Package: inet pkg (Version 4.2)
OS Release: PowerMAX OS 4.2
Architectures: moto
Platforms: Power Hawk 610/620/640, PowerStack, PowerStack II
Related Patches: base-016 (Power Hawk 610/620, PowerStack, PowerStack II),
base-017 (Power Hawk 640, PowerStack II multi-processor),
xfsd (4.2)
Related SARS: none
Brief Description:
PowerMAX OS 4.2 inet package release updates
Problem Description:
1. The standard SNMP libraries did not allow user processes to handle
SNMP requests from other systems. The SNMP daemons provide the
ability to have individual user processes handle specific SNMP
information requests. This is done by registering with the SNMP
daemon and passing information back and forth to it. Some of the
library routines necessary to utilize this capability had never been
included as a standard part of PowerMAX OS before.
2. Enhancements required to support new xfsd software package.
Problem Resolution:
1. Add the library routines and corrections to enable user handling of
SNMP calls.
2. Added required support for xfsd package.
Object To Be Replaced:
/usr/lib/libsnmp.so
/usr/lib/libsnmpio.so
/usr/lib/libsmux.so
/usr/sbin/in.snmpd
/etc/inet/services
Special Conditions for Installation:
None.
Possible Side Effects:
None.
return to index
================================================================================
Concurrent Computer Corporation Software Development
Software Patch Report
Patch Name: inet-008
Date Issued: 02/09/99 10:02:02
Software Package: inet pkg (Version 4.2)
OS Release: PowerMAX OS 4.2
Architectures: nh
Platforms: Night Hawk 6200/6800, Night Hawk 6800 Turbo, PowerMAXION
Related Patches: base-018, xfs (4.2)
Related SARS: none
Brief Description:
PowerMAX OS 4.2 inet package release updates
Problem Description:
1. The standard SNMP libraries did not allow user processes to handle
SNMP requests from other systems. The SNMP daemons provide the
ability to have individual user processes handle specific SNMP
information requests. This is done by registering with the SNMP
daemon and passing information back and forth to it. Some of the
library routines necessary to utilize this capability had never been
included as a standard part of PowerMAX OS before.
2. Enhancements required to support new xfsd software package.
Problem Resolution:
1. Add the library routines and corrections to enable user handling of
SNMP calls.
2. Added required support for xfsd package.
Object To Be Replaced:
/usr/sbin/in.snmpd
/etc/inet/services
Special Conditions for Installation:
None.
Possible Side Effects:
None.
return to index
================================================================================
Concurrent Computer Corporation Software Development
Software Patch Report
Patch Name: librt-001
Date Issued: 06/05/98 15:45:00
Software Package: librt pkg (Version 4.2)
OS Release: PowerMAX OS 4.2
Architectures: moto nh
Platforms: All PowerMAX OS 4.2 platforms
Related Patches: fbs-001, crosslibs-001
Related SARS: none
Brief Description:
PowerMAX OS 4.2 librt package release updates
Problem Description:
1. Environment variables are not passed to programs that are scheduled
on an FBS in the following ways:
- Ada
* PGM_Schedule()
* Sched_PGM_Add()
- C
* pgmschedule()
* sched_pgmadd()
- FORTRAN
* pgmschedule()
* schedpgmadd()
- rtcp
* sp
Problem Resolution:
1. Change the librt fbs_program() and the libF77rt schedpgmadd_()
functions to pass the parent process' environment to its child
process.
Object To Be Replaced:
/usr/lib/libF77rt.a
/usr/lib/librt.a
Special Conditions for Installation:
None.
Possible Side Effects:
None.
return to index
================================================================================
Concurrent Computer Corporation Software Development
Software Patch Report
Patch Name: librt-001
Date Issued: 06/05/98 15:45:00
Software Package: librt pkg (Version 4.2)
OS Release: PowerMAX OS 4.2
Architectures: moto nh
Platforms: All PowerMAX OS 4.2 platforms
Related Patches: fbs-001, crosslibs-001
Related SARS: none
Brief Description:
PowerMAX OS 4.2 librt package release updates
Problem Description:
1. Environment variables are not passed to programs that are scheduled
on an FBS in the following ways:
- Ada
* PGM_Schedule()
* Sched_PGM_Add()
- C
* pgmschedule()
* sched_pgmadd()
- FORTRAN
* pgmschedule()
* schedpgmadd()
- rtcp
* sp
Problem Resolution:
1. Change the librt fbs_program() and the libF77rt schedpgmadd_()
functions to pass the parent process' environment to its child
process.
Object To Be Replaced:
/usr/lib/libF77rt.a
/usr/lib/librt.a
Special Conditions for Installation:
None.
Possible Side Effects:
None.
return to index
================================================================================
Concurrent Computer Corporation Software Development
Software Patch Report
Patch Name: librt-001
Date Issued: 06/05/98 15:45:00
Software Package: librt pkg (Version 4.2)
OS Release: PowerMAX OS 4.2
Architectures: moto nh
Platforms: All PowerMAX OS 4.2 platforms
Related Patches: fbs-001, crosslibs-001
Related SARS: none
Brief Description:
PowerMAX OS 4.2 librt package release updates
Problem Description:
1. Environment variables are not passed to programs that are scheduled
on an FBS in the following ways:
- Ada
* PGM_Schedule()
* Sched_PGM_Add()
- C
* pgmschedule()
* sched_pgmadd()
- FORTRAN
* pgmschedule()
* schedpgmadd()
- rtcp
* sp
Problem Resolution:
1. Change the librt fbs_program() and the libF77rt schedpgmadd_()
functions to pass the parent process' environment to its child
process.
Object To Be Replaced:
/usr/lib/libF77rt.a
/usr/lib/librt.a
Special Conditions for Installation:
None.
Possible Side Effects:
None.
return to index
================================================================================
Concurrent Computer Corporation Software Development
Software Patch Report
Patch Name: man-001
Date Issued: 06/05/98 15:46:51
Software Package: man pkg (Version 4.2)
OS Release: PowerMAX OS 4.2
Architectures: moto nh
Platforms: All PowerMAX OS 4.2 platforms
Related Patches: inet-004
Related SARS: none
Brief Description:
PowerMAX OS 4.2 man package release updates
Problem Description:
1. The httpd daemon was added to PowerMAX OS 4.2 as part of the patch:
inet-004
The httpd (1m) man page is also required as part of this patch.
2. The manual (9) man page was released with an incorrect Pubs Number
for the Network Administration manual.
Problem Resolution:
1. The httpd (1m) man page is included in this patch.
2. The Pubs Number for the Network Administration manual has been
corrected as "0890432-020".
Object To Be Replaced:
/usr/share/man/cat1/httpd.1m.z
/usr/share/man/man1/httpd.1m
/usr/share/man/cat9/manual.9.z
/usr/share/man/man9/manual.9
Special Conditions for Installation:
None.
Possible Side Effects:
None.
return to index
================================================================================
Concurrent Computer Corporation Software Development
Software Patch Report
Patch Name: man-001
Date Issued: 06/05/98 15:46:51
Software Package: man pkg (Version 4.2)
OS Release: PowerMAX OS 4.2
Architectures: moto nh
Platforms: All PowerMAX OS 4.2 platforms
Related Patches: inet-004
Related SARS: none
Brief Description:
PowerMAX OS 4.2 man package release updates
Problem Description:
1. The httpd daemon was added to PowerMAX OS 4.2 as part of the patch:
inet-004
The httpd (1m) man page is also required as part of this patch.
2. The manual (9) man page was released with an incorrect Pubs Number
for the Network Administration manual.
Problem Resolution:
1. The httpd (1m) man page is included in this patch.
2. The Pubs Number for the Network Administration manual has been
corrected as "0890432-020".
Object To Be Replaced:
/usr/share/man/cat1/httpd.1m.z
/usr/share/man/man1/httpd.1m
/usr/share/man/cat9/manual.9.z
/usr/share/man/man9/manual.9
Special Conditions for Installation:
None.
Possible Side Effects:
None.
return to index
================================================================================
Concurrent Computer Corporation Software Development
Software Patch Report
Patch Name: man-001
Date Issued: 06/05/98 15:46:51
Software Package: man pkg (Version 4.2)
OS Release: PowerMAX OS 4.2
Architectures: moto nh
Platforms: All PowerMAX OS 4.2 platforms
Related Patches: inet-004
Related SARS: none
Brief Description:
PowerMAX OS 4.2 man package release updates
Problem Description:
1. The httpd daemon was added to PowerMAX OS 4.2 as part of the patch:
inet-004
The httpd (1m) man page is also required as part of this patch.
2. The manual (9) man page was released with an incorrect Pubs Number
for the Network Administration manual.
Problem Resolution:
1. The httpd (1m) man page is included in this patch.
2. The Pubs Number for the Network Administration manual has been
corrected as "0890432-020".
Object To Be Replaced:
/usr/share/man/cat1/httpd.1m.z
/usr/share/man/man1/httpd.1m
/usr/share/man/cat9/manual.9.z
/usr/share/man/man9/manual.9
Special Conditions for Installation:
None.
Possible Side Effects:
None.
return to index
================================================================================
Concurrent Computer Corporation Software Development
Software Patch Report
Patch Name: man-002
Date Issued: 08/12/98 11:20:45
Software Package: man pkg (Version 4.2)
OS Release: PowerMAX OS 4.2
Architectures: moto
Platforms: Power Hawk 610/620/640, PowerStack, PowerStack II
Related Patches: base-007 (Power Hawk 610/620, PowerStack, PowerStack II),
base-008 (Power Hawk 640, PowerStack II multi-processor),
cluster-004, mvc (4.2.1)
Related SARS: HM12246, HM12396
Brief Description:
PowerMAX OS 4.2 man package release updates
Problem Description:
1. HM12246, HM12396: Updates to ldterm(7) and rtserial(7) man pages
required to match driver changes for new mvc 4.2.1 package release.
2. Man pages required for new DMAC driver.
Problem Resolution:
1. Man pages updated.
2. Added man page for DMAC driver.
Object To Be Replaced:
/usr/share/man/cat7/dmac.7.z
/usr/share/man/cat7/ldterm.7.z
/usr/share/man/cat7/rtserial.7.z
/usr/share/man/man7/dmac.7
/usr/share/man/man7/ldterm.7
/usr/share/man/man7/rtserial.7
Special Conditions for Installation:
None.
Possible Side Effects:
None.
return to index
================================================================================
Concurrent Computer Corporation Software Development
Software Patch Report
Patch Name: man-002
Date Issued: 08/12/98 11:20:45
Software Package: man pkg (Version 4.2)
OS Release: PowerMAX OS 4.2
Architectures: moto
Platforms: Power Hawk 610/620/640, PowerStack, PowerStack II
Related Patches: base-007 (Power Hawk 610/620, PowerStack, PowerStack II),
base-008 (Power Hawk 640, PowerStack II multi-processor),
cluster-004, mvc (4.2.1)
Related SARS: HM12246, HM12396
Brief Description:
PowerMAX OS 4.2 man package release updates
Problem Description:
1. HM12246, HM12396: Updates to ldterm(7) and rtserial(7) man pages
required to match driver changes for new mvc 4.2.1 package release.
2. Man pages required for new DMAC driver.
Problem Resolution:
1. Man pages updated.
2. Added man page for DMAC driver.
Object To Be Replaced:
/usr/share/man/cat7/dmac.7.z
/usr/share/man/cat7/ldterm.7.z
/usr/share/man/cat7/rtserial.7.z
/usr/share/man/man7/dmac.7
/usr/share/man/man7/ldterm.7
/usr/share/man/man7/rtserial.7
Special Conditions for Installation:
None.
Possible Side Effects:
None.
return to index
================================================================================
Concurrent Computer Corporation Software Development
Software Patch Report
Patch Name: man-003
Date Issued: 08/12/98 11:28:29
Software Package: man pkg (Version 4.2)
OS Release: PowerMAX OS 4.2
Architectures: nh
Platforms: Night Hawk 6200/6800, TurboHawk, PowerMAXION
Related Patches: base-009, mvc (4.2.1)
Related SARS: HM12246, HM12396
Brief Description:
PowerMAX OS 4.2 man package release updates
Problem Description:
1. HM12246, HM12396: Updates to ldterm(7) and rtserial(7) man pages
required to match driver changes for new mvc 4.2.1 package release.
Problem Resolution:
1. Man pages updated.
Object To Be Replaced:
/usr/share/man/cat7/ldterm.7.z
/usr/share/man/cat7/rtserial.7.z
/usr/share/man/man7/ldterm.7
/usr/share/man/man7/rtserial.7
Special Conditions for Installation:
None.
Possible Side Effects:
None.
return to index
================================================================================
Concurrent Computer Corporation Software Development
Software Patch Report
Patch Name: man-004
Date Issued: 09/30/98 10:02:43
Software Package: man pkg (Version 4.2)
OS Release: PowerMAX OS 4.2
Architectures: moto
Platforms: Power Hawk 610/620/640, PowerStack, PowerStack II
Related Patches: base-013 (Power Hawk 610/620, PowerStack, PowerStack II),
base-014 (Power Hawk 640, PowerStack II multi-processor)
Related SARS: HM12357, HM12462
Brief Description:
PowerMAX OS 4.2 man package release updates
Problem Description:
1. Man page required for rac(1), a random access compressor which
produces compressed images suitable for use by the "radl" random
access decompression library included in base-013/base-014.
2. HM12357, HM12462: Man page update required for top(1) to reflect
changes made in base-013/base-014.
3. Man pages required for new GEV utilities.
Problem Resolution:
1. rac(1) man page added.
2. top(1) man page updated.
3. Added man page for GEV utilities.
Object To Be Replaced:
/usr/share/man/cat1/gev.1.z
/usr/share/man/cat2/nvram.2.z
/usr/share/man/cat1/rac.1.z
/usr/share/man/cat1/top.1.z
/usr/share/man/man1/gev.1
/usr/share/man/man2/nvram.2
/usr/share/man/man1/rac.1
/usr/share/man/man1/top.1
Special Conditions for Installation:
None.
Possible Side Effects:
None.
return to index
================================================================================
Concurrent Computer Corporation Software Development
Software Patch Report
Patch Name: man-004
Date Issued: 09/30/98 10:02:43
Software Package: man pkg (Version 4.2)
OS Release: PowerMAX OS 4.2
Architectures: moto
Platforms: Power Hawk 610/620/640, PowerStack, PowerStack II
Related Patches: base-013 (Power Hawk 610/620, PowerStack, PowerStack II),
base-014 (Power Hawk 640, PowerStack II multi-processor)
Related SARS: HM12357, HM12462
Brief Description:
PowerMAX OS 4.2 man package release updates
Problem Description:
1. Man page required for rac(1), a random access compressor which
produces compressed images suitable for use by the "radl" random
access decompression library included in base-013/base-014.
2. HM12357, HM12462: Man page update required for top(1) to reflect
changes made in base-013/base-014.
3. Man pages required for new GEV utilities.
Problem Resolution:
1. rac(1) man page added.
2. top(1) man page updated.
3. Added man page for GEV utilities.
Object To Be Replaced:
/usr/share/man/cat1/gev.1.z
/usr/share/man/cat2/nvram.2.z
/usr/share/man/cat1/rac.1.z
/usr/share/man/cat1/top.1.z
/usr/share/man/man1/gev.1
/usr/share/man/man2/nvram.2
/usr/share/man/man1/rac.1
/usr/share/man/man1/top.1
Special Conditions for Installation:
None.
Possible Side Effects:
None.
return to index
================================================================================
Concurrent Computer Corporation Software Development
Software Patch Report
Patch Name: man-005
Date Issued: 09/30/98 10:17:46
Software Package: man pkg (Version 4.2)
OS Release: PowerMAX OS 4.2
Architectures: nh
Platforms: Night Hawk 6200/6800, TurboHawk, PowerMAXION
Related Patches: base-015
Related SARS: HM12357, HM12462
Brief Description:
PowerMAX OS 4.2 man package release updates
Problem Description:
1. Man page required for rac(1), a random access compressor which
produces compressed images suitable for use by the "radl" random
access decompression library included in base-015.
2. HM12357, HM12462: Man page update required for top(1) to reflect
changes made in base-015.
Problem Resolution:
1. rac(1) man page added.
2. top(1) man page updated.
Object To Be Replaced:
/usr/share/man/cat1/rac.1.z
/usr/share/man/cat1/top.1.z
/usr/share/man/man1/rac.1
/usr/share/man/man1/top.1
Special Conditions for Installation:
None.
Possible Side Effects:
None.
return to index
================================================================================
Concurrent Computer Corporation Software Development
Software Patch Report
Patch Name: man-006
Date Issued: 02/09/99 10:02:46
Software Package: man pkg (Version 4.2)
OS Release: PowerMAX OS 4.2
Architectures: moto nh
Platforms: All PowerMAX OS 4.2 platforms
Related Patches: base-016 (Power Hawk 610/620, PowerStack, PowerStack II),
base-017 (Power Hawk 640, PowerStack II multi-processor),
base-018 (Night Hawk 6200/6800, TurboHawk, PowerMAXION),
vp-003, xfsd (4.2)
Related SARS: none
Brief Description:
PowerMAX OS 4.2 man package release updates
Problem Description:
1. Man page updates required for virtual partition enhancements.
2. Man page changes necessary to include documentation for new
enhancements to the xfs driver in base-016|base-017|base-018 and the
new PowerMAX OS 4.2 'xfsd' package.
3. Man page updates needed for enhancements to STREAMS service
procedures.
Problem Resolution:
1. Updated man pages.
2. Updated man pages.
3. Updated man pages.
Object To Be Replaced:
/usr/share/man/man1/mount_xfs.1m
/usr/share/man/man1/mkfs_xfs.1m
/usr/share/man/man1/strmuxbias.1m
/usr/share/man/man1/vpinit.1m
/usr/share/man/man1/vpstat.1m
/usr/share/man/man2/cpu_bias.2
/usr/share/man/man7/streamio.7
/usr/share/man/man7/vp.7
/usr/share/man/cat1/mount_xfs.1m.z
/usr/share/man/cat1/mkfs_xfs.1m.z
/usr/share/man/cat1/strmuxbias.1m.z
/usr/share/man/cat1/vpstat.1m.z
/usr/share/man/cat1/vpinit.1m.z
/usr/share/man/cat2/cpu_bias.2.z
/usr/share/man/cat7/streamio.7.z
/usr/share/man/cat7/vp.7.z
Special Conditions for Installation:
None.
Possible Side Effects:
None.
return to index
================================================================================
Concurrent Computer Corporation Software Development
Software Patch Report
Patch Name: man-006
Date Issued: 02/09/99 10:02:46
Software Package: man pkg (Version 4.2)
OS Release: PowerMAX OS 4.2
Architectures: moto nh
Platforms: All PowerMAX OS 4.2 platforms
Related Patches: base-016 (Power Hawk 610/620, PowerStack, PowerStack II),
base-017 (Power Hawk 640, PowerStack II multi-processor),
base-018 (Night Hawk 6200/6800, TurboHawk, PowerMAXION),
vp-003, xfsd (4.2)
Related SARS: none
Brief Description:
PowerMAX OS 4.2 man package release updates
Problem Description:
1. Man page updates required for virtual partition enhancements.
2. Man page changes necessary to include documentation for new
enhancements to the xfs driver in base-016|base-017|base-018 and the
new PowerMAX OS 4.2 'xfsd' package.
3. Man page updates needed for enhancements to STREAMS service
procedures.
Problem Resolution:
1. Updated man pages.
2. Updated man pages.
3. Updated man pages.
Object To Be Replaced:
/usr/share/man/man1/mount_xfs.1m
/usr/share/man/man1/mkfs_xfs.1m
/usr/share/man/man1/strmuxbias.1m
/usr/share/man/man1/vpinit.1m
/usr/share/man/man1/vpstat.1m
/usr/share/man/man2/cpu_bias.2
/usr/share/man/man7/streamio.7
/usr/share/man/man7/vp.7
/usr/share/man/cat1/mount_xfs.1m.z
/usr/share/man/cat1/mkfs_xfs.1m.z
/usr/share/man/cat1/strmuxbias.1m.z
/usr/share/man/cat1/vpstat.1m.z
/usr/share/man/cat1/vpinit.1m.z
/usr/share/man/cat2/cpu_bias.2.z
/usr/share/man/cat7/streamio.7.z
/usr/share/man/cat7/vp.7.z
Special Conditions for Installation:
None.
Possible Side Effects:
None.
return to index
================================================================================
Concurrent Computer Corporation Software Development
Software Patch Report
Patch Name: man-006
Date Issued: 02/09/99 10:02:46
Software Package: man pkg (Version 4.2)
OS Release: PowerMAX OS 4.2
Architectures: moto nh
Platforms: All PowerMAX OS 4.2 platforms
Related Patches: base-016 (Power Hawk 610/620, PowerStack, PowerStack II),
base-017 (Power Hawk 640, PowerStack II multi-processor),
base-018 (Night Hawk 6200/6800, TurboHawk, PowerMAXION),
vp-003, xfsd (4.2)
Related SARS: none
Brief Description:
PowerMAX OS 4.2 man package release updates
Problem Description:
1. Man page updates required for virtual partition enhancements.
2. Man page changes necessary to include documentation for new
enhancements to the xfs driver in base-016|base-017|base-018 and the
new PowerMAX OS 4.2 'xfsd' package.
3. Man page updates needed for enhancements to STREAMS service
procedures.
Problem Resolution:
1. Updated man pages.
2. Updated man pages.
3. Updated man pages.
Object To Be Replaced:
/usr/share/man/man1/mount_xfs.1m
/usr/share/man/man1/mkfs_xfs.1m
/usr/share/man/man1/strmuxbias.1m
/usr/share/man/man1/vpinit.1m
/usr/share/man/man1/vpstat.1m
/usr/share/man/man2/cpu_bias.2
/usr/share/man/man7/streamio.7
/usr/share/man/man7/vp.7
/usr/share/man/cat1/mount_xfs.1m.z
/usr/share/man/cat1/mkfs_xfs.1m.z
/usr/share/man/cat1/strmuxbias.1m.z
/usr/share/man/cat1/vpstat.1m.z
/usr/share/man/cat1/vpinit.1m.z
/usr/share/man/cat2/cpu_bias.2.z
/usr/share/man/cat7/streamio.7.z
/usr/share/man/cat7/vp.7.z
Special Conditions for Installation:
None.
Possible Side Effects:
None.
return to index
================================================================================
Concurrent Computer Corporation Software Development
Software Patch Report
Patch Name: ncr-001
Date Issued: 06/05/98 16:08:57
Software Package: ncr pkg (Version 4.2)
OS Release: PowerMAX OS 4.2
Architectures: nh
Platforms: TurboHawk, PowerMAXION
Related Patches: dec-006, base-006
Related SARS: none
Brief Description:
PowerMAX OS 4.2 ncr package release updates
Problem Description:
1. TurboHawk system hardware was modified to increase the PCI bus
throughput. The software did not support these changes.
Problem Resolution:
1. Modified the initialization of the PLX Bridge, the Tundra VME
interface, embedded DEC Ethernet controller and embedded NCR SCSI
controller. This change allowed the Operating System to take
advantage of hardware changes on TurboHawk systems for increased PCI
bus throughput.
Object To Be Replaced:
/etc/conf/pack.d/ncr/Driver.o
Special Conditions for Installation:
None.
Possible Side Effects:
None.
return to index
================================================================================
Concurrent Computer Corporation Software Development
Software Patch Report
Patch Name: ncr-002
Date Issued: 09/30/98 10:20:10
Software Package: ncr pkg (Version 4.2)
OS Release: PowerMAX OS 4.2
Architectures: moto nh
Platforms: All PowerMAX OS 4.2 platforms
Related Patches: base-013 (Power Hawk 610/620, PowerStack, PowerStack II),
base-014 (Power Hawk 640, PowerStack II multi-processor),
base-015 (Night Hawk 6200/6800, TurboHawk, PowerMAXION),
via-001
Related SARS: HM12415
Brief Description:
PowerMAX OS 4.2 ncr package release updates
Problem Description:
1. HM12415: Add ncr (Symbios) 53c875/895 SCSI controller chip high
performance mode enhancements and support for removable media
Magneto-Optical drives.
* Add SCSI ULTRA-2 (LVD) controller support (Symbios 53c895).
* SCSI ULTRA controller (Symbios 53c875) corrupted data when
full performance cababilities of chip were enabled.
* Need enhancements to support removable media disks and 1K
sector size.
* SCSI ULTRA requires fewer devices on shorter cabling than
FAST/WIDE.
* Raw disk transfers greater than 128K not supported.
* Some SCSI devices will do a SCSI reconnect, then immediately
disconnect without doing anything.
Problem Resolution:
1. Problems resolved as follows:
* Add ULTRA-2 (LVD) controller support (Symbios 53c895) to ncr
driver.
* Added special SCSI Script instructions to reset 53c875 cache
line alignment mechanism on each PCI dma block move. Added
high performance mode configuration. Added FIFO flush logic
to completion and disconnect. Added NCR_BURST_SZ tunable to
/etc/conf/mtune.d/ncr to allow multiple dma cache line
bursts per PCI bus tenure.
* Changed generic disk driver (gd) to support 1K sector
format, media missing at boot, media change, and disk
geometry change with media change (including new partition
layout). Added check for true block size in via driver.
* Added NCR_875_MAX_SYNC system tunable allow running more
drives on a longer cable by tuning the 53c875 to FAST/WIDE
speeds.
* Added PHYSIO_MAXTRNSFR system tunable to allow up to 512K
raw transfers for ncr (via and hsa not supported).
* Added workaround to ncr driver via ncr scripts.
Object To Be Replaced:
/etc/conf/mtune.d/ncr
/etc/conf/pack.d/ncr/Driver.o
/etc/conf/pack.d/ncr/space.c
/usr/include/sys/ncr.h
/usr/include/sys/ncr53c8xx.h
Special Conditions for Installation:
None.
Possible Side Effects:
The SCSISCAN tunable MUST be enabled (set to '1') following installation
of ncr-002. Disabling this tunable may cause unexpected or unreliable
behavior. NOTE: By default this tunable is enabled.
return to index
================================================================================
Concurrent Computer Corporation Software Development
Software Patch Report
Patch Name: ncr-002
Date Issued: 09/30/98 10:20:10
Software Package: ncr pkg (Version 4.2)
OS Release: PowerMAX OS 4.2
Architectures: moto nh
Platforms: All PowerMAX OS 4.2 platforms
Related Patches: base-013 (Power Hawk 610/620, PowerStack, PowerStack II),
base-014 (Power Hawk 640, PowerStack II multi-processor),
base-015 (Night Hawk 6200/6800, TurboHawk, PowerMAXION),
via-001
Related SARS: HM12415
Brief Description:
PowerMAX OS 4.2 ncr package release updates
Problem Description:
1. HM12415: Add ncr (Symbios) 53c875/895 SCSI controller chip high
performance mode enhancements and support for removable media
Magneto-Optical drives.
* Add SCSI ULTRA-2 (LVD) controller support (Symbios 53c895).
* SCSI ULTRA controller (Symbios 53c875) corrupted data when
full performance cababilities of chip were enabled.
* Need enhancements to support removable media disks and 1K
sector size.
* SCSI ULTRA requires fewer devices on shorter cabling than
FAST/WIDE.
* Raw disk transfers greater than 128K not supported.
* Some SCSI devices will do a SCSI reconnect, then immediately
disconnect without doing anything.
Problem Resolution:
1. Problems resolved as follows:
* Add ULTRA-2 (LVD) controller support (Symbios 53c895) to ncr
driver.
* Added special SCSI Script instructions to reset 53c875 cache
line alignment mechanism on each PCI dma block move. Added
high performance mode configuration. Added FIFO flush logic
to completion and disconnect. Added NCR_BURST_SZ tunable to
/etc/conf/mtune.d/ncr to allow multiple dma cache line
bursts per PCI bus tenure.
* Changed generic disk driver (gd) to support 1K sector
format, media missing at boot, media change, and disk
geometry change with media change (including new partition
layout). Added check for true block size in via driver.
* Added NCR_875_MAX_SYNC system tunable allow running more
drives on a longer cable by tuning the 53c875 to FAST/WIDE
speeds.
* Added PHYSIO_MAXTRNSFR system tunable to allow up to 512K
raw transfers for ncr (via and hsa not supported).
* Added workaround to ncr driver via ncr scripts.
Object To Be Replaced:
/etc/conf/mtune.d/ncr
/etc/conf/pack.d/ncr/Driver.o
/etc/conf/pack.d/ncr/space.c
/usr/include/sys/ncr.h
/usr/include/sys/ncr53c8xx.h
Special Conditions for Installation:
None.
Possible Side Effects:
The SCSISCAN tunable MUST be enabled (set to '1') following installation
of ncr-002. Disabling this tunable may cause unexpected or unreliable
behavior. NOTE: By default this tunable is enabled.
return to index
================================================================================
Concurrent Computer Corporation Software Development
Software Patch Report
Patch Name: ncr-002
Date Issued: 09/30/98 10:20:10
Software Package: ncr pkg (Version 4.2)
OS Release: PowerMAX OS 4.2
Architectures: moto nh
Platforms: All PowerMAX OS 4.2 platforms
Related Patches: base-013 (Power Hawk 610/620, PowerStack, PowerStack II),
base-014 (Power Hawk 640, PowerStack II multi-processor),
base-015 (Night Hawk 6200/6800, TurboHawk, PowerMAXION),
via-001
Related SARS: HM12415
Brief Description:
PowerMAX OS 4.2 ncr package release updates
Problem Description:
1. HM12415: Add ncr (Symbios) 53c875/895 SCSI controller chip high
performance mode enhancements and support for removable media
Magneto-Optical drives.
* Add SCSI ULTRA-2 (LVD) controller support (Symbios 53c895).
* SCSI ULTRA controller (Symbios 53c875) corrupted data when
full performance cababilities of chip were enabled.
* Need enhancements to support removable media disks and 1K
sector size.
* SCSI ULTRA requires fewer devices on shorter cabling than
FAST/WIDE.
* Raw disk transfers greater than 128K not supported.
* Some SCSI devices will do a SCSI reconnect, then immediately
disconnect without doing anything.
Problem Resolution:
1. Problems resolved as follows:
* Add ULTRA-2 (LVD) controller support (Symbios 53c895) to ncr
driver.
* Added special SCSI Script instructions to reset 53c875 cache
line alignment mechanism on each PCI dma block move. Added
high performance mode configuration. Added FIFO flush logic
to completion and disconnect. Added NCR_BURST_SZ tunable to
/etc/conf/mtune.d/ncr to allow multiple dma cache line
bursts per PCI bus tenure.
* Changed generic disk driver (gd) to support 1K sector
format, media missing at boot, media change, and disk
geometry change with media change (including new partition
layout). Added check for true block size in via driver.
* Added NCR_875_MAX_SYNC system tunable allow running more
drives on a longer cable by tuning the 53c875 to FAST/WIDE
speeds.
* Added PHYSIO_MAXTRNSFR system tunable to allow up to 512K
raw transfers for ncr (via and hsa not supported).
* Added workaround to ncr driver via ncr scripts.
Object To Be Replaced:
/etc/conf/mtune.d/ncr
/etc/conf/pack.d/ncr/Driver.o
/etc/conf/pack.d/ncr/space.c
/usr/include/sys/ncr.h
/usr/include/sys/ncr53c8xx.h
Special Conditions for Installation:
None.
Possible Side Effects:
The SCSISCAN tunable MUST be enabled (set to '1') following installation
of ncr-002. Disabling this tunable may cause unexpected or unreliable
behavior. NOTE: By default this tunable is enabled.
return to index
================================================================================
Concurrent Computer Corporation Software Development
Software Patch Report
Patch Name: netboot-001
Date Issued: 02/09/99 10:09:21
Software Package: netboot pkg (Version 4.2)
OS Release: PowerMAX OS 4.2
Architectures: moto
Platforms: Power Hawk 610/620/640, PowerStack, PowerStack II
Related Patches: base-016 (Power Hawk 610/620, PowerStack, PowerStack II),
base-017 (Power Hawk 640, PowerStack II multi-processor)
Related SARS: none
Brief Description:
PowerMAX OS 4.2 netboot package release updates
Problem Description:
1. netbootconfig does not correctly parse /etc/hosts entries of the
type: ($ is used below to indicate end-of-line)
ipaddr hostname$
ipaddr hostname#comment$
netbootconfig will fail printing the following error message:
ERROR: no such client in /etc/inet/hosts: <client>
2. During the booting of a netboot client, the Internet Services Daemon
(inetd) may fail to start up resulting in certain network services
(such as telnet) being rejected by the client.
Problem Resolution:
1. netbootconfig has been modified to parse the hosts file correctly.
2. A file which inetd accesses was being removed during client system
inititalization. Fix is to not remove the file.
Object To Be Replaced:
/usr/etc/netbootconf.d/bin/netbootconfig
/etc/init.d/netboot
/etc/conf/bin/sbcbstrap
Special Conditions for Installation:
NOTICE #3: The following links will also be created during installation
of netboot-001:
* Link to /usr/etc/netbootconf.d/bin/netbootconfig
/sbin/netbootconfig
* Link to /etc/init.d/netboot
/etc/rc3.d/S24netboot
Possible Side Effects:
None.
return to index
================================================================================
Concurrent Computer Corporation Software Development
Software Patch Report
Patch Name: netboot-001
Date Issued: 02/09/99 10:09:21
Software Package: netboot pkg (Version 4.2)
OS Release: PowerMAX OS 4.2
Architectures: moto
Platforms: Power Hawk 610/620/640, PowerStack, PowerStack II
Related Patches: base-016 (Power Hawk 610/620, PowerStack, PowerStack II),
base-017 (Power Hawk 640, PowerStack II multi-processor)
Related SARS: none
Brief Description:
PowerMAX OS 4.2 netboot package release updates
Problem Description:
1. netbootconfig does not correctly parse /etc/hosts entries of the
type: ($ is used below to indicate end-of-line)
ipaddr hostname$
ipaddr hostname#comment$
netbootconfig will fail printing the following error message:
ERROR: no such client in /etc/inet/hosts: <client>
2. During the booting of a netboot client, the Internet Services Daemon
(inetd) may fail to start up resulting in certain network services
(such as telnet) being rejected by the client.
Problem Resolution:
1. netbootconfig has been modified to parse the hosts file correctly.
2. A file which inetd accesses was being removed during client system
inititalization. Fix is to not remove the file.
Object To Be Replaced:
/usr/etc/netbootconf.d/bin/netbootconfig
/etc/init.d/netboot
/etc/conf/bin/sbcbstrap
Special Conditions for Installation:
NOTICE #3: The following links will also be created during installation
of netboot-001:
* Link to /usr/etc/netbootconf.d/bin/netbootconfig
/sbin/netbootconfig
* Link to /etc/init.d/netboot
/etc/rc3.d/S24netboot
Possible Side Effects:
None.
return to index
================================================================================
Concurrent Computer Corporation Software Development
Software Patch Report
Patch Name: nfs-001
Date Issued: 06/05/98 15:49:34
Software Package: nfs pkg (Version 4.2)
OS Release: PowerMAX OS 4.2
Architectures: moto nh
Platforms: All PowerMAX OS 4.2 platforms
Related Patches: none
Related SARS: HM12342
Brief Description:
PowerMAX OS 4.2 nfs package release updates
Problem Description:
1. A file system is NFS mounted from an SGI Octane system. When doing
`ls` or `find` not all files are visible. A 4.1 system with the same
filesystem crossmounted from the SGI does not exhibit this problem.
If a non-visible file is mentioned by name i.e. `ls file` it can be
seen.
Problem Resolution:
1. Removed inappropriate check for overflow in the offset passed to
getdents(2) during a directory read operation, introduced as part
of large file support. When this problem shows, the value of the
directory offset returned by the NFS server in a previous getdents(2)
call will have the high-order bit set. This is normal on some NFS
servers.
Object To Be Replaced:
/etc/conf/pack.d/nfs/Driver.o
Special Conditions for Installation:
None.
Possible Side Effects:
None.
return to index
================================================================================
Concurrent Computer Corporation Software Development
Software Patch Report
Patch Name: nfs-001
Date Issued: 06/05/98 15:49:34
Software Package: nfs pkg (Version 4.2)
OS Release: PowerMAX OS 4.2
Architectures: moto nh
Platforms: All PowerMAX OS 4.2 platforms
Related Patches: none
Related SARS: HM12342
Brief Description:
PowerMAX OS 4.2 nfs package release updates
Problem Description:
1. A file system is NFS mounted from an SGI Octane system. When doing
`ls` or `find` not all files are visible. A 4.1 system with the same
filesystem crossmounted from the SGI does not exhibit this problem.
If a non-visible file is mentioned by name i.e. `ls file` it can be
seen.
Problem Resolution:
1. Removed inappropriate check for overflow in the offset passed to
getdents(2) during a directory read operation, introduced as part
of large file support. When this problem shows, the value of the
directory offset returned by the NFS server in a previous getdents(2)
call will have the high-order bit set. This is normal on some NFS
servers.
Object To Be Replaced:
/etc/conf/pack.d/nfs/Driver.o
Special Conditions for Installation:
None.
Possible Side Effects:
None.
return to index
================================================================================
Concurrent Computer Corporation Software Development
Software Patch Report
Patch Name: nfs-001
Date Issued: 06/05/98 15:49:34
Software Package: nfs pkg (Version 4.2)
OS Release: PowerMAX OS 4.2
Architectures: moto nh
Platforms: All PowerMAX OS 4.2 platforms
Related Patches: none
Related SARS: HM12342
Brief Description:
PowerMAX OS 4.2 nfs package release updates
Problem Description:
1. A file system is NFS mounted from an SGI Octane system. When doing
`ls` or `find` not all files are visible. A 4.1 system with the same
filesystem crossmounted from the SGI does not exhibit this problem.
If a non-visible file is mentioned by name i.e. `ls file` it can be
seen.
Problem Resolution:
1. Removed inappropriate check for overflow in the offset passed to
getdents(2) during a directory read operation, introduced as part
of large file support. When this problem shows, the value of the
directory offset returned by the NFS server in a previous getdents(2)
call will have the high-order bit set. This is normal on some NFS
servers.
Object To Be Replaced:
/etc/conf/pack.d/nfs/Driver.o
Special Conditions for Installation:
None.
Possible Side Effects:
None.
return to index
================================================================================
Concurrent Computer Corporation Software Development
Software Patch Report
Patch Name: nfs-002
Date Issued: 08/12/98 11:32:13
Software Package: nfs pkg (Version 4.2)
OS Release: PowerMAX OS 4.2
Architectures: moto nh
Platforms: All PowerMAX OS 4.2 platforms
Related Patches: none
Related SARS: HM12413
Brief Description:
PowerMAX OS 4.2 nfs package release updates
Problem Description:
1. Problems with PC file systems NFS mounted using Hummingbird NFS
server:
A. 'ls -l' sometimes erroneously shows PC directories as having
a size of 4278190079.
B. The moxfm(1) file manager invoked from npanel(1) does not
show the contents of PC directories that can be seen from
the shell. At this point moxfm may core dump.
C. When a new directory is created on the server, the creation
date is wrong (as shown by ls -l). It typically appears as
Jan 1 1970.
2. HM12413: Several problems with lockd(1M) (nfs lock manager):
(a) Locks held by a client that crashes are not properly
recovered. This may result in incorrect file locks that
are never released.
(b) In some cases, when a process on a client system blocks
waiting for a lock, it would not get woken up after the
lock was released.
(c) There is a long time period between the reboot of a system
and its detection on the server.
Problem Resolution:
1. Correct NFS client code in kernel to conform more strictly to the
NFS protocol in directory read and make directory operations.
2. lockd problems resolved as follows:
(a) Upon detecting that a client has crashed (and rebooted),
the server will clear ALL locks held by that client.
(b) Add a small delay in the kernel code that re-requests a
lock via the local lockd. This allows other messages to be
received.
(c) Shorten the initial start-up delay in statd from 15 to 5
seconds.
Object To Be Replaced:
/etc/conf/pack.d/klm/Driver.o
/etc/conf/pack.d/nfs/Driver.o
/usr/lib/nfs/lockd
/usr/lib/nfs/statd
Special Conditions for Installation:
None.
Possible Side Effects:
None.
return to index
================================================================================
Concurrent Computer Corporation Software Development
Software Patch Report
Patch Name: nfs-002
Date Issued: 08/12/98 11:32:13
Software Package: nfs pkg (Version 4.2)
OS Release: PowerMAX OS 4.2
Architectures: moto nh
Platforms: All PowerMAX OS 4.2 platforms
Related Patches: none
Related SARS: HM12413
Brief Description:
PowerMAX OS 4.2 nfs package release updates
Problem Description:
1. Problems with PC file systems NFS mounted using Hummingbird NFS
server:
A. 'ls -l' sometimes erroneously shows PC directories as having
a size of 4278190079.
B. The moxfm(1) file manager invoked from npanel(1) does not
show the contents of PC directories that can be seen from
the shell. At this point moxfm may core dump.
C. When a new directory is created on the server, the creation
date is wrong (as shown by ls -l). It typically appears as
Jan 1 1970.
2. HM12413: Several problems with lockd(1M) (nfs lock manager):
(a) Locks held by a client that crashes are not properly
recovered. This may result in incorrect file locks that
are never released.
(b) In some cases, when a process on a client system blocks
waiting for a lock, it would not get woken up after the
lock was released.
(c) There is a long time period between the reboot of a system
and its detection on the server.
Problem Resolution:
1. Correct NFS client code in kernel to conform more strictly to the
NFS protocol in directory read and make directory operations.
2. lockd problems resolved as follows:
(a) Upon detecting that a client has crashed (and rebooted),
the server will clear ALL locks held by that client.
(b) Add a small delay in the kernel code that re-requests a
lock via the local lockd. This allows other messages to be
received.
(c) Shorten the initial start-up delay in statd from 15 to 5
seconds.
Object To Be Replaced:
/etc/conf/pack.d/klm/Driver.o
/etc/conf/pack.d/nfs/Driver.o
/usr/lib/nfs/lockd
/usr/lib/nfs/statd
Special Conditions for Installation:
None.
Possible Side Effects:
None.
return to index
================================================================================
Concurrent Computer Corporation Software Development
Software Patch Report
Patch Name: nfs-002
Date Issued: 08/12/98 11:32:13
Software Package: nfs pkg (Version 4.2)
OS Release: PowerMAX OS 4.2
Architectures: moto nh
Platforms: All PowerMAX OS 4.2 platforms
Related Patches: none
Related SARS: HM12413
Brief Description:
PowerMAX OS 4.2 nfs package release updates
Problem Description:
1. Problems with PC file systems NFS mounted using Hummingbird NFS
server:
A. 'ls -l' sometimes erroneously shows PC directories as having
a size of 4278190079.
B. The moxfm(1) file manager invoked from npanel(1) does not
show the contents of PC directories that can be seen from
the shell. At this point moxfm may core dump.
C. When a new directory is created on the server, the creation
date is wrong (as shown by ls -l). It typically appears as
Jan 1 1970.
2. HM12413: Several problems with lockd(1M) (nfs lock manager):
(a) Locks held by a client that crashes are not properly
recovered. This may result in incorrect file locks that
are never released.
(b) In some cases, when a process on a client system blocks
waiting for a lock, it would not get woken up after the
lock was released.
(c) There is a long time period between the reboot of a system
and its detection on the server.
Problem Resolution:
1. Correct NFS client code in kernel to conform more strictly to the
NFS protocol in directory read and make directory operations.
2. lockd problems resolved as follows:
(a) Upon detecting that a client has crashed (and rebooted),
the server will clear ALL locks held by that client.
(b) Add a small delay in the kernel code that re-requests a
lock via the local lockd. This allows other messages to be
received.
(c) Shorten the initial start-up delay in statd from 15 to 5
seconds.
Object To Be Replaced:
/etc/conf/pack.d/klm/Driver.o
/etc/conf/pack.d/nfs/Driver.o
/usr/lib/nfs/lockd
/usr/lib/nfs/statd
Special Conditions for Installation:
None.
Possible Side Effects:
None.
return to index
================================================================================
Concurrent Computer Corporation Software Development
Software Patch Report
Patch Name: ngpib-001
Date Issued: 06/08/98 14:21:33
Software Package: ngpib pkg (Version 4.2)
OS Release: PowerMAX OS 4.2
Architectures: moto nh
Platforms: All PowerMAX OS 4.2 platforms (w/ VME)
Related Patches: none
Related SARS: HM12398
Brief Description:
PowerMAX OS 4.2 ngpib package release updates
Problem Description:
1. HM12398: NGPIB User-Level Driver does not support the Power Hawk or
TurboHawk platforms.
The NGPIB User-Level Driver is a single set of source modules,
designed to support various architectures. The driver interrogates
the architecture type during the "config" configuration phase.
A switch statement is executed for each architecture type, and
any special processing unique to that archictecuture is provided.
Problem Resolution:
1. New case statements needed to be added for the Power Hawk and
TurboHawk architectures, and the architecture-unique processing
had to be added, i.e., setting up different VMEbus memory maps,
handling VMEbus interrupts, etc.
Object To Be Replaced:
/usr/etc/ngpibconfig
/usr/include/ud/ngpib.h
/usr/lib/libngpib.a
/usr/src/drivers/ngpib/ngpib_masterloop.c
/usr/src/drivers/ngpib/ngpib_slaveloop.c
Special Conditions for Installation:
None.
Possible Side Effects:
None.
return to index
================================================================================
Concurrent Computer Corporation Software Development
Software Patch Report
Patch Name: ngpib-001
Date Issued: 06/08/98 14:21:33
Software Package: ngpib pkg (Version 4.2)
OS Release: PowerMAX OS 4.2
Architectures: moto nh
Platforms: All PowerMAX OS 4.2 platforms (w/ VME)
Related Patches: none
Related SARS: HM12398
Brief Description:
PowerMAX OS 4.2 ngpib package release updates
Problem Description:
1. HM12398: NGPIB User-Level Driver does not support the Power Hawk or
TurboHawk platforms.
The NGPIB User-Level Driver is a single set of source modules,
designed to support various architectures. The driver interrogates
the architecture type during the "config" configuration phase.
A switch statement is executed for each architecture type, and
any special processing unique to that archictecuture is provided.
Problem Resolution:
1. New case statements needed to be added for the Power Hawk and
TurboHawk architectures, and the architecture-unique processing
had to be added, i.e., setting up different VMEbus memory maps,
handling VMEbus interrupts, etc.
Object To Be Replaced:
/usr/etc/ngpibconfig
/usr/include/ud/ngpib.h
/usr/lib/libngpib.a
/usr/src/drivers/ngpib/ngpib_masterloop.c
/usr/src/drivers/ngpib/ngpib_slaveloop.c
Special Conditions for Installation:
None.
Possible Side Effects:
None.
return to index
================================================================================
Concurrent Computer Corporation Software Development
Software Patch Report
Patch Name: ngpib-001
Date Issued: 06/08/98 14:21:33
Software Package: ngpib pkg (Version 4.2)
OS Release: PowerMAX OS 4.2
Architectures: moto nh
Platforms: All PowerMAX OS 4.2 platforms (w/ VME)
Related Patches: none
Related SARS: HM12398
Brief Description:
PowerMAX OS 4.2 ngpib package release updates
Problem Description:
1. HM12398: NGPIB User-Level Driver does not support the Power Hawk or
TurboHawk platforms.
The NGPIB User-Level Driver is a single set of source modules,
designed to support various architectures. The driver interrogates
the architecture type during the "config" configuration phase.
A switch statement is executed for each architecture type, and
any special processing unique to that archictecuture is provided.
Problem Resolution:
1. New case statements needed to be added for the Power Hawk and
TurboHawk architectures, and the architecture-unique processing
had to be added, i.e., setting up different VMEbus memory maps,
handling VMEbus interrupts, etc.
Object To Be Replaced:
/usr/etc/ngpibconfig
/usr/include/ud/ngpib.h
/usr/lib/libngpib.a
/usr/src/drivers/ngpib/ngpib_masterloop.c
/usr/src/drivers/ngpib/ngpib_slaveloop.c
Special Conditions for Installation:
None.
Possible Side Effects:
None.
return to index
================================================================================
Concurrent Computer Corporation Software Development
Software Patch Report
Patch Name: nsu-001
Date Issued: 06/05/98 15:55:58
Software Package: nsu pkg (Version 4.2)
OS Release: PowerMAX_OS 4.2
Architectures: moto nh
Platforms: All PowerMAX OS 4.2 platforms
Related Patches: none
Related SARS: none
Brief Description:
PowerMAX OS 4.2 nsu package release updates
Problem Description:
1. When issuing a send() socket call for more than 536 bytes of data,
only the first 536 bytes of data were sent. This corresponds to the
default value of the maximum segment size.
Problem Resolution:
1. The sockmod module is modified to allow 16K of data to be sent in a
send() call, as in previous releases of PowerMAX OS.
Object To Be Replaced:
/etc/conf/pack.d/sockmod/Driver.o
Special Conditions for Installation:
None.
Possible Side Effects:
None.
return to index
================================================================================
Concurrent Computer Corporation Software Development
Software Patch Report
Patch Name: nsu-001
Date Issued: 06/05/98 15:55:58
Software Package: nsu pkg (Version 4.2)
OS Release: PowerMAX_OS 4.2
Architectures: moto nh
Platforms: All PowerMAX OS 4.2 platforms
Related Patches: none
Related SARS: none
Brief Description:
PowerMAX OS 4.2 nsu package release updates
Problem Description:
1. When issuing a send() socket call for more than 536 bytes of data,
only the first 536 bytes of data were sent. This corresponds to the
default value of the maximum segment size.
Problem Resolution:
1. The sockmod module is modified to allow 16K of data to be sent in a
send() call, as in previous releases of PowerMAX OS.
Object To Be Replaced:
/etc/conf/pack.d/sockmod/Driver.o
Special Conditions for Installation:
None.
Possible Side Effects:
None.
return to index
================================================================================
Concurrent Computer Corporation Software Development
Software Patch Report
Patch Name: nsu-001
Date Issued: 06/05/98 15:55:58
Software Package: nsu pkg (Version 4.2)
OS Release: PowerMAX_OS 4.2
Architectures: moto nh
Platforms: All PowerMAX OS 4.2 platforms
Related Patches: none
Related SARS: none
Brief Description:
PowerMAX OS 4.2 nsu package release updates
Problem Description:
1. When issuing a send() socket call for more than 536 bytes of data,
only the first 536 bytes of data were sent. This corresponds to the
default value of the maximum segment size.
Problem Resolution:
1. The sockmod module is modified to allow 16K of data to be sent in a
send() call, as in previous releases of PowerMAX OS.
Object To Be Replaced:
/etc/conf/pack.d/sockmod/Driver.o
Special Conditions for Installation:
None.
Possible Side Effects:
None.
return to index
================================================================================
Concurrent Computer Corporation Software Development
Software Patch Report
Patch Name: nsu-002
Date Issued: 02/09/99 10:11:08
Software Package: nsu pkg (Version 4.2)
OS Release: PowerMAX OS 4.2
Architectures: moto nh
Platforms: All PowerMAX OS 4.2 platforms
Related Patches: base-016 (Power Hawk 610/620, PowerStack, PowerStack II),
base-017 (Power Hawk 640, PowerStack II multi-processor),
base-018 (Night Hawk 6200/6800, TurboHawk, PowerMAXION)
Related SARS: HM12428
Brief Description:
PowerMAX OS 4.2 nsu package release updates
Problem Description:
1. HM12428: The header files used in building the ticlts, ticots, and
ticotsor drivers define the number of loopback endpoints to be
O_MAXMIN (255) in TCL__NENDPT, TCO_NENDPT, and TCOO_NENDPT
respectively. The drivers need to be rebuilt with the new L_MAXMIN
value.
Problem Resolution:
1. The value of the number of endpoints has been changed to L_MAXMIN
(32768).
Object To Be Replaced:
/usr/include/sys/ticots.h
/usr/include/sys/ticotsord.h
/usr/include/sys/ticlts.h
/etc/conf/pack.d/ticlts/Driver.o
/etc/conf/pack.d/ticots/Driver.o
/etc/conf/pack.d/ticotsor/Driver.o
Special Conditions for Installation:
None.
Possible Side Effects:
None.
return to index
================================================================================
Concurrent Computer Corporation Software Development
Software Patch Report
Patch Name: nsu-002
Date Issued: 02/09/99 10:11:08
Software Package: nsu pkg (Version 4.2)
OS Release: PowerMAX OS 4.2
Architectures: moto nh
Platforms: All PowerMAX OS 4.2 platforms
Related Patches: base-016 (Power Hawk 610/620, PowerStack, PowerStack II),
base-017 (Power Hawk 640, PowerStack II multi-processor),
base-018 (Night Hawk 6200/6800, TurboHawk, PowerMAXION)
Related SARS: HM12428
Brief Description:
PowerMAX OS 4.2 nsu package release updates
Problem Description:
1. HM12428: The header files used in building the ticlts, ticots, and
ticotsor drivers define the number of loopback endpoints to be
O_MAXMIN (255) in TCL__NENDPT, TCO_NENDPT, and TCOO_NENDPT
respectively. The drivers need to be rebuilt with the new L_MAXMIN
value.
Problem Resolution:
1. The value of the number of endpoints has been changed to L_MAXMIN
(32768).
Object To Be Replaced:
/usr/include/sys/ticots.h
/usr/include/sys/ticotsord.h
/usr/include/sys/ticlts.h
/etc/conf/pack.d/ticlts/Driver.o
/etc/conf/pack.d/ticots/Driver.o
/etc/conf/pack.d/ticotsor/Driver.o
Special Conditions for Installation:
None.
Possible Side Effects:
None.
return to index
================================================================================
Concurrent Computer Corporation Software Development
Software Patch Report
Patch Name: nsu-002
Date Issued: 02/09/99 10:11:08
Software Package: nsu pkg (Version 4.2)
OS Release: PowerMAX OS 4.2
Architectures: moto nh
Platforms: All PowerMAX OS 4.2 platforms
Related Patches: base-016 (Power Hawk 610/620, PowerStack, PowerStack II),
base-017 (Power Hawk 640, PowerStack II multi-processor),
base-018 (Night Hawk 6200/6800, TurboHawk, PowerMAXION)
Related SARS: HM12428
Brief Description:
PowerMAX OS 4.2 nsu package release updates
Problem Description:
1. HM12428: The header files used in building the ticlts, ticots, and
ticotsor drivers define the number of loopback endpoints to be
O_MAXMIN (255) in TCL__NENDPT, TCO_NENDPT, and TCOO_NENDPT
respectively. The drivers need to be rebuilt with the new L_MAXMIN
value.
Problem Resolution:
1. The value of the number of endpoints has been changed to L_MAXMIN
(32768).
Object To Be Replaced:
/usr/include/sys/ticots.h
/usr/include/sys/ticotsord.h
/usr/include/sys/ticlts.h
/etc/conf/pack.d/ticlts/Driver.o
/etc/conf/pack.d/ticots/Driver.o
/etc/conf/pack.d/ticotsor/Driver.o
Special Conditions for Installation:
None.
Possible Side Effects:
None.
return to index
================================================================================
Concurrent Computer Corporation Software Development
Software Patch Report
Patch Name: pg-001
Date Issued: 06/05/98 15:57:35
Software Package: pg pkg (Version 4.2)
OS Release: PowerMAX OS 4.2
Architectures: moto nh
Platforms: All PowerMAX OS 4.2 platforms (w/ VME)
Related Patches: none
Related SARS: none
Brief Description:
PowerMAX OS 4.2 pg package release updates
Problem Description:
1. Kernel panics with "kernel-mode address fault on kernel address
0x00000000" from within pg_unload().
The pg module is by default a dynamically loadable module (DLM). If
the module is not used for 600 seconds (10 minutes), the module will
be unloaded. A panic occurrs if the pg module is loaded, no
successful opens occur, and the pg module is unloaded. pg_unload
causes the panic because it is trying to free a structure that was
never allocated, and it is attempting to lock the never allocated
structure.
The panic occurs in one of the following situations:
A. Configure the pg package and the appropriate
/etc/confnet.d/inet/interface file entry, but do not install
the physical board. Networking will not startup properly, and
then 10 minutes later the system will panic.
B. A load/unload sequence is forced using the modadmin (1M) command.
Problem Resolution:
1. pg_unload() now checks to make sure the ADAPTER_PROBED flag is set
in the adapter_t structure for the board before calling the
pgnull_sap_close() routine and deallocating the dynamically allocated
data structures allocated to it. If ADAPTER_PROBED is not set, there
were no dynamically allocated data structures ever created for the
board, and the routine continues on to do cleanup for the next board.
Object To Be Replaced:
/etc/conf/pack.d/pg/Driver.o
Special Conditions for Installation:
None.
Possible Side Effects:
None.
return to index
================================================================================
Concurrent Computer Corporation Software Development
Software Patch Report
Patch Name: pg-001
Date Issued: 06/05/98 15:57:35
Software Package: pg pkg (Version 4.2)
OS Release: PowerMAX OS 4.2
Architectures: moto nh
Platforms: All PowerMAX OS 4.2 platforms (w/ VME)
Related Patches: none
Related SARS: none
Brief Description:
PowerMAX OS 4.2 pg package release updates
Problem Description:
1. Kernel panics with "kernel-mode address fault on kernel address
0x00000000" from within pg_unload().
The pg module is by default a dynamically loadable module (DLM). If
the module is not used for 600 seconds (10 minutes), the module will
be unloaded. A panic occurrs if the pg module is loaded, no
successful opens occur, and the pg module is unloaded. pg_unload
causes the panic because it is trying to free a structure that was
never allocated, and it is attempting to lock the never allocated
structure.
The panic occurs in one of the following situations:
A. Configure the pg package and the appropriate
/etc/confnet.d/inet/interface file entry, but do not install
the physical board. Networking will not startup properly, and
then 10 minutes later the system will panic.
B. A load/unload sequence is forced using the modadmin (1M) command.
Problem Resolution:
1. pg_unload() now checks to make sure the ADAPTER_PROBED flag is set
in the adapter_t structure for the board before calling the
pgnull_sap_close() routine and deallocating the dynamically allocated
data structures allocated to it. If ADAPTER_PROBED is not set, there
were no dynamically allocated data structures ever created for the
board, and the routine continues on to do cleanup for the next board.
Object To Be Replaced:
/etc/conf/pack.d/pg/Driver.o
Special Conditions for Installation:
None.
Possible Side Effects:
None.
return to index
================================================================================
Concurrent Computer Corporation Software Development
Software Patch Report
Patch Name: pg-001
Date Issued: 06/05/98 15:57:35
Software Package: pg pkg (Version 4.2)
OS Release: PowerMAX OS 4.2
Architectures: moto nh
Platforms: All PowerMAX OS 4.2 platforms (w/ VME)
Related Patches: none
Related SARS: none
Brief Description:
PowerMAX OS 4.2 pg package release updates
Problem Description:
1. Kernel panics with "kernel-mode address fault on kernel address
0x00000000" from within pg_unload().
The pg module is by default a dynamically loadable module (DLM). If
the module is not used for 600 seconds (10 minutes), the module will
be unloaded. A panic occurrs if the pg module is loaded, no
successful opens occur, and the pg module is unloaded. pg_unload
causes the panic because it is trying to free a structure that was
never allocated, and it is attempting to lock the never allocated
structure.
The panic occurs in one of the following situations:
A. Configure the pg package and the appropriate
/etc/confnet.d/inet/interface file entry, but do not install
the physical board. Networking will not startup properly, and
then 10 minutes later the system will panic.
B. A load/unload sequence is forced using the modadmin (1M) command.
Problem Resolution:
1. pg_unload() now checks to make sure the ADAPTER_PROBED flag is set
in the adapter_t structure for the board before calling the
pgnull_sap_close() routine and deallocating the dynamically allocated
data structures allocated to it. If ADAPTER_PROBED is not set, there
were no dynamically allocated data structures ever created for the
board, and the routine continues on to do cleanup for the next board.
Object To Be Replaced:
/etc/conf/pack.d/pg/Driver.o
Special Conditions for Installation:
None.
Possible Side Effects:
None.
return to index
================================================================================
Concurrent Computer Corporation Software Development
Software Patch Report
Patch Name: rpc-001
Date Issued: 02/09/99 10:15:10
Software Package: rpc pkg (Version 4.2)
OS Release: PowerMAX OS 4.2
Architectures: moto nh
Platforms: All PowerMAX OS 4.2 platforms
Related Patches: base-016 (Power Hawk 610/620, PowerStack, PowerStack II),
base-017 (Power Hawk 640, PowerStack II multi-processor),
base-018 (Night Hawk 6200/6800, TurboHawk, PowerMAXION),
xfsd (4.2)
Related SARS: none
Brief Description:
PowerMAX OS 4.2 rpc package release updates
Problem Description:
1. Enhancements required to support new PowerMAX OS 4.2 xfsd software
package.
Problem Resolution:
1. Added required support for xfsd package.
Object To Be Replaced:
/etc/rpc
Special Conditions for Installation:
None.
Possible Side Effects:
None.
return to index
================================================================================
Concurrent Computer Corporation Software Development
Software Patch Report
Patch Name: rpc-001
Date Issued: 02/09/99 10:15:10
Software Package: rpc pkg (Version 4.2)
OS Release: PowerMAX OS 4.2
Architectures: moto nh
Platforms: All PowerMAX OS 4.2 platforms
Related Patches: base-016 (Power Hawk 610/620, PowerStack, PowerStack II),
base-017 (Power Hawk 640, PowerStack II multi-processor),
base-018 (Night Hawk 6200/6800, TurboHawk, PowerMAXION),
xfsd (4.2)
Related SARS: none
Brief Description:
PowerMAX OS 4.2 rpc package release updates
Problem Description:
1. Enhancements required to support new PowerMAX OS 4.2 xfsd software
package.
Problem Resolution:
1. Added required support for xfsd package.
Object To Be Replaced:
/etc/rpc
Special Conditions for Installation:
None.
Possible Side Effects:
None.
return to index
================================================================================
Concurrent Computer Corporation Software Development
Software Patch Report
Patch Name: rpc-001
Date Issued: 02/09/99 10:15:10
Software Package: rpc pkg (Version 4.2)
OS Release: PowerMAX OS 4.2
Architectures: moto nh
Platforms: All PowerMAX OS 4.2 platforms
Related Patches: base-016 (Power Hawk 610/620, PowerStack, PowerStack II),
base-017 (Power Hawk 640, PowerStack II multi-processor),
base-018 (Night Hawk 6200/6800, TurboHawk, PowerMAXION),
xfsd (4.2)
Related SARS: none
Brief Description:
PowerMAX OS 4.2 rpc package release updates
Problem Description:
1. Enhancements required to support new PowerMAX OS 4.2 xfsd software
package.
Problem Resolution:
1. Added required support for xfsd package.
Object To Be Replaced:
/etc/rpc
Special Conditions for Installation:
None.
Possible Side Effects:
None.
return to index
================================================================================
Concurrent Computer Corporation Software Development
Software Patch Report
Patch Name: via-001
Date Issued: 09/30/98 10:30:08
Software Package: via pkg (Version 4.2)
OS Release: PowerMAX OS 4.2
Architectures: moto nh
Platforms: All PowerMAX OS 4.2 platforms
Related Patches: base-013 (Power Hawk 610/620, PowerStack, PowerStack II),
base-014 (Power Hawk 640, PowerStack II multi-processor),
base-015 (Night Hawk 6200/6800, TurboHawk, PowerMAXION),
ncr-002
Related SARS: HM12415
Brief Description:
PowerMAX OS 4.2 via package release updates
Problem Description:
1. HM12415: Add ncr (Symbios) 53c875/895 SCSI controller chip high
performance mode enhancements and support for removable media
Magneto-Optical drives.
* Add SCSI ULTRA-2 (LVD) controller support (Symbios 53c895).
* SCSI ULTRA controller (Symbios 53c875) corrupted data when
full performance cababilities of chip were enabled.
* Need enhancements to support removable media disks and 1K
sector size.
* SCSI ULTRA requires fewer devices on shorter cabling than
FAST/WIDE.
* Raw disk transfers greater than 128K not supported.
* Some SCSI devices will do a SCSI reconnect, then immediately
disconnect without doing anything.
Problem Resolution:
1. Problems resolved as follows:
* Add ULTRA-2 (LVD) controller support (Symbios 53c895) to ncr
driver.
* Added special SCSI Script instructions to reset 53c875 cache
line alignment mechanism on each PCI dma block move. Added
high performance mode configuration. Added FIFO flush logic
to completion and disconnect. Added NCR_BURST_SZ tunable to
/etc/conf/mtune.d/ncr to allow multiple dma cache line
bursts per PCI bus tenure.
* Changed generic disk driver (gd) to support 1K sector
format, media missing at boot, media change, and disk
geometry change with media change (including new partition
layout). Added check for true block size in via driver.
* Added NCR_875_MAX_SYNC system tunable allow running more
drives on a longer cable by tuning the 53c875 to FAST/WIDE
speeds.
* Added PHYSIO_MAXTRNSFR system tunable to allow up to 512K
raw transfers for ncr (via and hsa not supported).
* Added workaround to ncr driver via ncr scripts.
Object To Be Replaced:
/etc/conf/pack.d/via/Driver.o
Special Conditions for Installation:
None.
Possible Side Effects:
None.
return to index
================================================================================
Concurrent Computer Corporation Software Development
Software Patch Report
Patch Name: via-001
Date Issued: 09/30/98 10:30:08
Software Package: via pkg (Version 4.2)
OS Release: PowerMAX OS 4.2
Architectures: moto nh
Platforms: All PowerMAX OS 4.2 platforms
Related Patches: base-013 (Power Hawk 610/620, PowerStack, PowerStack II),
base-014 (Power Hawk 640, PowerStack II multi-processor),
base-015 (Night Hawk 6200/6800, TurboHawk, PowerMAXION),
ncr-002
Related SARS: HM12415
Brief Description:
PowerMAX OS 4.2 via package release updates
Problem Description:
1. HM12415: Add ncr (Symbios) 53c875/895 SCSI controller chip high
performance mode enhancements and support for removable media
Magneto-Optical drives.
* Add SCSI ULTRA-2 (LVD) controller support (Symbios 53c895).
* SCSI ULTRA controller (Symbios 53c875) corrupted data when
full performance cababilities of chip were enabled.
* Need enhancements to support removable media disks and 1K
sector size.
* SCSI ULTRA requires fewer devices on shorter cabling than
FAST/WIDE.
* Raw disk transfers greater than 128K not supported.
* Some SCSI devices will do a SCSI reconnect, then immediately
disconnect without doing anything.
Problem Resolution:
1. Problems resolved as follows:
* Add ULTRA-2 (LVD) controller support (Symbios 53c895) to ncr
driver.
* Added special SCSI Script instructions to reset 53c875 cache
line alignment mechanism on each PCI dma block move. Added
high performance mode configuration. Added FIFO flush logic
to completion and disconnect. Added NCR_BURST_SZ tunable to
/etc/conf/mtune.d/ncr to allow multiple dma cache line
bursts per PCI bus tenure.
* Changed generic disk driver (gd) to support 1K sector
format, media missing at boot, media change, and disk
geometry change with media change (including new partition
layout). Added check for true block size in via driver.
* Added NCR_875_MAX_SYNC system tunable allow running more
drives on a longer cable by tuning the 53c875 to FAST/WIDE
speeds.
* Added PHYSIO_MAXTRNSFR system tunable to allow up to 512K
raw transfers for ncr (via and hsa not supported).
* Added workaround to ncr driver via ncr scripts.
Object To Be Replaced:
/etc/conf/pack.d/via/Driver.o
Special Conditions for Installation:
None.
Possible Side Effects:
None.
return to index
================================================================================
Concurrent Computer Corporation Software Development
Software Patch Report
Patch Name: via-001
Date Issued: 09/30/98 10:30:08
Software Package: via pkg (Version 4.2)
OS Release: PowerMAX OS 4.2
Architectures: moto nh
Platforms: All PowerMAX OS 4.2 platforms
Related Patches: base-013 (Power Hawk 610/620, PowerStack, PowerStack II),
base-014 (Power Hawk 640, PowerStack II multi-processor),
base-015 (Night Hawk 6200/6800, TurboHawk, PowerMAXION),
ncr-002
Related SARS: HM12415
Brief Description:
PowerMAX OS 4.2 via package release updates
Problem Description:
1. HM12415: Add ncr (Symbios) 53c875/895 SCSI controller chip high
performance mode enhancements and support for removable media
Magneto-Optical drives.
* Add SCSI ULTRA-2 (LVD) controller support (Symbios 53c895).
* SCSI ULTRA controller (Symbios 53c875) corrupted data when
full performance cababilities of chip were enabled.
* Need enhancements to support removable media disks and 1K
sector size.
* SCSI ULTRA requires fewer devices on shorter cabling than
FAST/WIDE.
* Raw disk transfers greater than 128K not supported.
* Some SCSI devices will do a SCSI reconnect, then immediately
disconnect without doing anything.
Problem Resolution:
1. Problems resolved as follows:
* Add ULTRA-2 (LVD) controller support (Symbios 53c895) to ncr
driver.
* Added special SCSI Script instructions to reset 53c875 cache
line alignment mechanism on each PCI dma block move. Added
high performance mode configuration. Added FIFO flush logic
to completion and disconnect. Added NCR_BURST_SZ tunable to
/etc/conf/mtune.d/ncr to allow multiple dma cache line
bursts per PCI bus tenure.
* Changed generic disk driver (gd) to support 1K sector
format, media missing at boot, media change, and disk
geometry change with media change (including new partition
layout). Added check for true block size in via driver.
* Added NCR_875_MAX_SYNC system tunable allow running more
drives on a longer cable by tuning the 53c875 to FAST/WIDE
speeds.
* Added PHYSIO_MAXTRNSFR system tunable to allow up to 512K
raw transfers for ncr (via and hsa not supported).
* Added workaround to ncr driver via ncr scripts.
Object To Be Replaced:
/etc/conf/pack.d/via/Driver.o
Special Conditions for Installation:
None.
Possible Side Effects:
None.
return to index
================================================================================
Concurrent Computer Corporation Software Development
Software Patch Report
Patch Name: vp-001
Date Issued: 06/08/98 14:29:33
Software Package: vp pkg (Version 4.2)
OS Release: PowerMAX OS 4.2
Architectures: moto nh
Platforms: All PowerMAX OS 4.2 platforms
Related Patches: base-004|base-005|base-006
Related SARS: none
Brief Description:
PowerMAX OS 4.2 vp package release updates
Problem Description:
1. Improve performance for disk striping (VP). Related to patches
base-004|base-005|base-006.
* Memory allocator overhead in vp driver.
2. After a system crash, a mirrored disk (MP) is automatically no
longer synchronized and the secondary partition is silently marked
down.
Problem Resolution:
1. Improved performance for disk striping (VP).
* Add private free lists, buffering to vp driver.
2. Modified vpinit:
* Add vpinit option when initializing an MP, so that an
automatic restoration is done after a system crash.
* If this new option is not used, be verbose about indicating
that the secondary partition is marked down.
Object To Be Replaced:
/etc/vptab
/etc/conf/pack.d/vp/Driver.o
/sbin/vpinit
/usr/sbin/vpstat
Special Conditions for Installation:
None.
Possible Side Effects:
None.
return to index
================================================================================
Concurrent Computer Corporation Software Development
Software Patch Report
Patch Name: vp-001
Date Issued: 06/08/98 14:29:33
Software Package: vp pkg (Version 4.2)
OS Release: PowerMAX OS 4.2
Architectures: moto nh
Platforms: All PowerMAX OS 4.2 platforms
Related Patches: base-004|base-005|base-006
Related SARS: none
Brief Description:
PowerMAX OS 4.2 vp package release updates
Problem Description:
1. Improve performance for disk striping (VP). Related to patches
base-004|base-005|base-006.
* Memory allocator overhead in vp driver.
2. After a system crash, a mirrored disk (MP) is automatically no
longer synchronized and the secondary partition is silently marked
down.
Problem Resolution:
1. Improved performance for disk striping (VP).
* Add private free lists, buffering to vp driver.
2. Modified vpinit:
* Add vpinit option when initializing an MP, so that an
automatic restoration is done after a system crash.
* If this new option is not used, be verbose about indicating
that the secondary partition is marked down.
Object To Be Replaced:
/etc/vptab
/etc/conf/pack.d/vp/Driver.o
/sbin/vpinit
/usr/sbin/vpstat
Special Conditions for Installation:
None.
Possible Side Effects:
None.
return to index
================================================================================
Concurrent Computer Corporation Software Development
Software Patch Report
Patch Name: vp-001
Date Issued: 06/08/98 14:29:33
Software Package: vp pkg (Version 4.2)
OS Release: PowerMAX OS 4.2
Architectures: moto nh
Platforms: All PowerMAX OS 4.2 platforms
Related Patches: base-004|base-005|base-006
Related SARS: none
Brief Description:
PowerMAX OS 4.2 vp package release updates
Problem Description:
1. Improve performance for disk striping (VP). Related to patches
base-004|base-005|base-006.
* Memory allocator overhead in vp driver.
2. After a system crash, a mirrored disk (MP) is automatically no
longer synchronized and the secondary partition is silently marked
down.
Problem Resolution:
1. Improved performance for disk striping (VP).
* Add private free lists, buffering to vp driver.
2. Modified vpinit:
* Add vpinit option when initializing an MP, so that an
automatic restoration is done after a system crash.
* If this new option is not used, be verbose about indicating
that the secondary partition is marked down.
Object To Be Replaced:
/etc/vptab
/etc/conf/pack.d/vp/Driver.o
/sbin/vpinit
/usr/sbin/vpstat
Special Conditions for Installation:
None.
Possible Side Effects:
None.
return to index
================================================================================
Concurrent Computer Corporation Software Development
Software Patch Report
Patch Name: vp-002
Date Issued: 08/12/98 11:40:11
Software Package: vp pkg (Version 4.2)
OS Release: PowerMAX OS 4.2
Architectures: moto nh
Platforms: All PowerMAX OS 4.2 platforms
Related Patches: none
Related SARS: none
Brief Description:
PowerMAX OS 4.2 vp package release updates
Problem Description:
1. With 4.2 patch vp-001, I/O to vp (striped) disks would sometimes
result in files with lost or corrupted data.
Problem Resolution:
1. The vp code would sometimes compute an incorrect block number
within a file. This was corrected.
Object To Be Replaced:
/etc/conf/pack.d/vp/Driver.o
Special Conditions for Installation:
None.
Possible Side Effects:
None.
return to index
================================================================================
Concurrent Computer Corporation Software Development
Software Patch Report
Patch Name: vp-002
Date Issued: 08/12/98 11:40:11
Software Package: vp pkg (Version 4.2)
OS Release: PowerMAX OS 4.2
Architectures: moto nh
Platforms: All PowerMAX OS 4.2 platforms
Related Patches: none
Related SARS: none
Brief Description:
PowerMAX OS 4.2 vp package release updates
Problem Description:
1. With 4.2 patch vp-001, I/O to vp (striped) disks would sometimes
result in files with lost or corrupted data.
Problem Resolution:
1. The vp code would sometimes compute an incorrect block number
within a file. This was corrected.
Object To Be Replaced:
/etc/conf/pack.d/vp/Driver.o
Special Conditions for Installation:
None.
Possible Side Effects:
None.
return to index
================================================================================
Concurrent Computer Corporation Software Development
Software Patch Report
Patch Name: vp-002
Date Issued: 08/12/98 11:40:11
Software Package: vp pkg (Version 4.2)
OS Release: PowerMAX OS 4.2
Architectures: moto nh
Platforms: All PowerMAX OS 4.2 platforms
Related Patches: none
Related SARS: none
Brief Description:
PowerMAX OS 4.2 vp package release updates
Problem Description:
1. With 4.2 patch vp-001, I/O to vp (striped) disks would sometimes
result in files with lost or corrupted data.
Problem Resolution:
1. The vp code would sometimes compute an incorrect block number
within a file. This was corrected.
Object To Be Replaced:
/etc/conf/pack.d/vp/Driver.o
Special Conditions for Installation:
None.
Possible Side Effects:
None.
return to index
================================================================================
Concurrent Computer Corporation Software Development
Software Patch Report
Patch Name: vp-003
Date Issued: 02/09/99 10:16:09
Software Package: vp pkg (Version 4.2)
OS Release: PowerMAX OS 4.2
Architectures: moto nh
Platforms: All PowerMAX OS 4.2 platforms
Related Patches: base-016 (Power Hawk 610/620, PowerStack, PowerStack II),
base-017 (Power Hawk 640, PowerStack II multi-processor),
base-018 (Night Hawk 6200/6800, TurboHawk, PowerMAXION)
Related SARS: none
Brief Description:
PowerMAX OS 4.2 vp package release updates
Problem Description:
1. Various enhancements to the Virtual Partition (VP) software:
* The Virtual Partition (VP) software did not support the
mirroring of the System Disk partitions.
* VP device 0 (/dev/[r]dsk/vp0) is no longer reserved for
system use.
* Change ioctl: VP_STATUS.
* New ioctls: IOCTYPE, VP_GET_VPB, VP_DESTROY, VP_VERIFY,
VP_CANCEL, VP_READER_MODE, VP_THROTTLE, VP_REPAIR, VP_MAXVP,
VP_UPDATE.
* Enhanced /sbin/vpinit.
* Enhanced /usr/sbin/vpstat.
Problem Resolution:
1. Enhancements resolved as follows:
* The Virtual Partition (VP) software has been enhanced to
support mirroring of the System Disk partitions.
The system disk partitions are defined as follows:
/dev/[r]root root partition (/)
/dev/[r]swap swap partition
/dev/[r]usr usr partition (/usr)
/dev/[r]var usr partition (/var)
* A new device, /dev/mpdemon, now replaces the functionality
provided by /dev/[r]dsk/vp0 in previous releases of the vp
package.
* The VP_STATUS ioctl use to return a kernel data structure
(struct vpblock) in the ioctl argument. This has been
changed to return a NEW data structure (struct vpstatus) in
order to break kernel data structure dependencies on public
(user accessible) ioctl returns.
* New VP ioctls added:
IOCTYPE Returns VP_IOC to the caller. Used to verify
that caller is talking to the VP device driver.
VP_GET_VPB Returns the kernel data structure (struct
vpblock) that use to be returned by VP_STATUS.
VP_DESTROY Performs an identical function as VP_UNCONFIG
but also zeros out the on-disk data structures.
This will force the user to create (VP_CREATE)
a new VP. The older VP_UNCONFIG ioctl should
be reserved for "guru" users.
VP_VERIFY Allows the caller to verify the integrity of a
synchronized mirror by reading equivalent blocks
on the two partitions and performing a buffer
compare.
VP_CANCEL Allows the caller to cancel an ongoing restore
or verify operation.
VP_READER_MODE By default, reads to a synchronized mirror
are generally distributed between the two
mirrored partitions, providing better
overall throughput. This option allows the
user to force synchronized reads to occur
ONLY on either the primary or secondary
partition.
VP_THROTTLE By default, a mirror restore (or verify)
operation is performed in a tight read/write
loop (or read/read-verify) resulting in a faster
restore/verify at the cost of disk subsystem
bandwidth. The restore throttle allows the user
to request an delay (in microseconds) between
loops to allow a fairer distribution of I/O's
on the disk subsystem.
VP_REPAIR When a mirrored disk fails and needs to be
replaced, the on disk VP data structures are
lost. This ioctl rebuilds the on-disk data
structures which results in a mirror suitable
for re-synchronization.
VP_MAXVP Simply returns the number of VP's that may be
configured in the system (as specified by the
unit field in the System configuration file).
VP_UPDATE Originally, the on-disk data structure
associated with a synchronized mirrored
partition was marked "dirty" on the first open,
and "clean" on the last close. This was done to
provide crash integrity on the mirror. This
enhancement changes this behavior two-fold:
A synchronized partition is only marked "dirty"
preceding the first write to the partition (not
at open). If the update timeout is set to zero
(the default), the partition remains "dirty"
until the last close. If the update timeout is
non-zero, then the on-disk state will be
automatically marked "clean" after the specified
timeout (in seconds) elapses without any more
write activity.
* Enhanced /sbin/vpinit as follows:
- Extended vpinit's ability to interpret device names
by allowing for basename entries instead of full
pathnames. For example, the following is now legal:
/sbin/vpinit vp1 1s0 2s0 3s0 4s0 5s0 6s0
and results in a 6 partition stripe.
- 9 new mirror options added:
-t Verify mirror.
-p {Report interval in seconds}
Display the progress of a restore or
verify operation.
-x Destroy a mirror. Like -u with on-disk
VP data structures invalidated also.
-o reader={primary|secondary|distributed}
-o throttle={# of usecs}
-o update={# of seconds}
-q Quiet mode. Suppress advisory messages
such as "Vp is already synchronized" as
well as other non-error messages.
-R Repair a mirror. Used when replacing a
failed disk.
-Z Determine if the specified VP is a root
device mirror. The vpinit exit code
returns the results.
- Updated to allow a mirror restore or verify operation
to be canceled via signal (SIGINT, etc). Previously,
once started, the restore operation could not be
canceled.
* Enhanced /usr/sbin/vpstat as follows:
- Extended vpstat's ability to interpret device names
as described above in /sbin/vpinit.
- Added "default display" mode. In the event of no VP
device being entered on the command line, all status
of devices of the selected type are displayed.
- Added command options to augment the "default
display" mode by specifying any combination of
unconfigured (-u), mirrored (-m), or striped (-s)
VPs. By default, only mirrored and striped VPs are
displayed.
- For verbose displays on mirrored VPs, display info
on new mirror options: update timeout, restore
throttle, and reader mode.
Object To Be Replaced:
/etc/conf/node.d/vp
/etc/conf/pack.d/vp/Driver.o
/etc/conf/pack.d/vp/space.c
/etc/conf/sdevice.d/vp
/sbin/vpinit
/usr/include/sys/vp.h
/usr/sbin/vpstat
Special Conditions for Installation:
The VP ioctl definitions found in /usr/include/sys/vp.h have changed
requiring end-users to recompile code that may access them.
Possible Side Effects:
None.
return to index
================================================================================
Concurrent Computer Corporation Software Development
Software Patch Report
Patch Name: vp-003
Date Issued: 02/09/99 10:16:09
Software Package: vp pkg (Version 4.2)
OS Release: PowerMAX OS 4.2
Architectures: moto nh
Platforms: All PowerMAX OS 4.2 platforms
Related Patches: base-016 (Power Hawk 610/620, PowerStack, PowerStack II),
base-017 (Power Hawk 640, PowerStack II multi-processor),
base-018 (Night Hawk 6200/6800, TurboHawk, PowerMAXION)
Related SARS: none
Brief Description:
PowerMAX OS 4.2 vp package release updates
Problem Description:
1. Various enhancements to the Virtual Partition (VP) software:
* The Virtual Partition (VP) software did not support the
mirroring of the System Disk partitions.
* VP device 0 (/dev/[r]dsk/vp0) is no longer reserved for
system use.
* Change ioctl: VP_STATUS.
* New ioctls: IOCTYPE, VP_GET_VPB, VP_DESTROY, VP_VERIFY,
VP_CANCEL, VP_READER_MODE, VP_THROTTLE, VP_REPAIR, VP_MAXVP,
VP_UPDATE.
* Enhanced /sbin/vpinit.
* Enhanced /usr/sbin/vpstat.
Problem Resolution:
1. Enhancements resolved as follows:
* The Virtual Partition (VP) software has been enhanced to
support mirroring of the System Disk partitions.
The system disk partitions are defined as follows:
/dev/[r]root root partition (/)
/dev/[r]swap swap partition
/dev/[r]usr usr partition (/usr)
/dev/[r]var usr partition (/var)
* A new device, /dev/mpdemon, now replaces the functionality
provided by /dev/[r]dsk/vp0 in previous releases of the vp
package.
* The VP_STATUS ioctl use to return a kernel data structure
(struct vpblock) in the ioctl argument. This has been
changed to return a NEW data structure (struct vpstatus) in
order to break kernel data structure dependencies on public
(user accessible) ioctl returns.
* New VP ioctls added:
IOCTYPE Returns VP_IOC to the caller. Used to verify
that caller is talking to the VP device driver.
VP_GET_VPB Returns the kernel data structure (struct
vpblock) that use to be returned by VP_STATUS.
VP_DESTROY Performs an identical function as VP_UNCONFIG
but also zeros out the on-disk data structures.
This will force the user to create (VP_CREATE)
a new VP. The older VP_UNCONFIG ioctl should
be reserved for "guru" users.
VP_VERIFY Allows the caller to verify the integrity of a
synchronized mirror by reading equivalent blocks
on the two partitions and performing a buffer
compare.
VP_CANCEL Allows the caller to cancel an ongoing restore
or verify operation.
VP_READER_MODE By default, reads to a synchronized mirror
are generally distributed between the two
mirrored partitions, providing better
overall throughput. This option allows the
user to force synchronized reads to occur
ONLY on either the primary or secondary
partition.
VP_THROTTLE By default, a mirror restore (or verify)
operation is performed in a tight read/write
loop (or read/read-verify) resulting in a faster
restore/verify at the cost of disk subsystem
bandwidth. The restore throttle allows the user
to request an delay (in microseconds) between
loops to allow a fairer distribution of I/O's
on the disk subsystem.
VP_REPAIR When a mirrored disk fails and needs to be
replaced, the on disk VP data structures are
lost. This ioctl rebuilds the on-disk data
structures which results in a mirror suitable
for re-synchronization.
VP_MAXVP Simply returns the number of VP's that may be
configured in the system (as specified by the
unit field in the System configuration file).
VP_UPDATE Originally, the on-disk data structure
associated with a synchronized mirrored
partition was marked "dirty" on the first open,
and "clean" on the last close. This was done to
provide crash integrity on the mirror. This
enhancement changes this behavior two-fold:
A synchronized partition is only marked "dirty"
preceding the first write to the partition (not
at open). If the update timeout is set to zero
(the default), the partition remains "dirty"
until the last close. If the update timeout is
non-zero, then the on-disk state will be
automatically marked "clean" after the specified
timeout (in seconds) elapses without any more
write activity.
* Enhanced /sbin/vpinit as follows:
- Extended vpinit's ability to interpret device names
by allowing for basename entries instead of full
pathnames. For example, the following is now legal:
/sbin/vpinit vp1 1s0 2s0 3s0 4s0 5s0 6s0
and results in a 6 partition stripe.
- 9 new mirror options added:
-t Verify mirror.
-p {Report interval in seconds}
Display the progress of a restore or
verify operation.
-x Destroy a mirror. Like -u with on-disk
VP data structures invalidated also.
-o reader={primary|secondary|distributed}
-o throttle={# of usecs}
-o update={# of seconds}
-q Quiet mode. Suppress advisory messages
such as "Vp is already synchronized" as
well as other non-error messages.
-R Repair a mirror. Used when replacing a
failed disk.
-Z Determine if the specified VP is a root
device mirror. The vpinit exit code
returns the results.
- Updated to allow a mirror restore or verify operation
to be canceled via signal (SIGINT, etc). Previously,
once started, the restore operation could not be
canceled.
* Enhanced /usr/sbin/vpstat as follows:
- Extended vpstat's ability to interpret device names
as described above in /sbin/vpinit.
- Added "default display" mode. In the event of no VP
device being entered on the command line, all status
of devices of the selected type are displayed.
- Added command options to augment the "default
display" mode by specifying any combination of
unconfigured (-u), mirrored (-m), or striped (-s)
VPs. By default, only mirrored and striped VPs are
displayed.
- For verbose displays on mirrored VPs, display info
on new mirror options: update timeout, restore
throttle, and reader mode.
Object To Be Replaced:
/etc/conf/node.d/vp
/etc/conf/pack.d/vp/Driver.o
/etc/conf/pack.d/vp/space.c
/etc/conf/sdevice.d/vp
/sbin/vpinit
/usr/include/sys/vp.h
/usr/sbin/vpstat
Special Conditions for Installation:
The VP ioctl definitions found in /usr/include/sys/vp.h have changed
requiring end-users to recompile code that may access them.
Possible Side Effects:
None.
return to index
================================================================================
Concurrent Computer Corporation Software Development
Software Patch Report
Patch Name: vp-003
Date Issued: 02/09/99 10:16:09
Software Package: vp pkg (Version 4.2)
OS Release: PowerMAX OS 4.2
Architectures: moto nh
Platforms: All PowerMAX OS 4.2 platforms
Related Patches: base-016 (Power Hawk 610/620, PowerStack, PowerStack II),
base-017 (Power Hawk 640, PowerStack II multi-processor),
base-018 (Night Hawk 6200/6800, TurboHawk, PowerMAXION)
Related SARS: none
Brief Description:
PowerMAX OS 4.2 vp package release updates
Problem Description:
1. Various enhancements to the Virtual Partition (VP) software:
* The Virtual Partition (VP) software did not support the
mirroring of the System Disk partitions.
* VP device 0 (/dev/[r]dsk/vp0) is no longer reserved for
system use.
* Change ioctl: VP_STATUS.
* New ioctls: IOCTYPE, VP_GET_VPB, VP_DESTROY, VP_VERIFY,
VP_CANCEL, VP_READER_MODE, VP_THROTTLE, VP_REPAIR, VP_MAXVP,
VP_UPDATE.
* Enhanced /sbin/vpinit.
* Enhanced /usr/sbin/vpstat.
Problem Resolution:
1. Enhancements resolved as follows:
* The Virtual Partition (VP) software has been enhanced to
support mirroring of the System Disk partitions.
The system disk partitions are defined as follows:
/dev/[r]root root partition (/)
/dev/[r]swap swap partition
/dev/[r]usr usr partition (/usr)
/dev/[r]var usr partition (/var)
* A new device, /dev/mpdemon, now replaces the functionality
provided by /dev/[r]dsk/vp0 in previous releases of the vp
package.
* The VP_STATUS ioctl use to return a kernel data structure
(struct vpblock) in the ioctl argument. This has been
changed to return a NEW data structure (struct vpstatus) in
order to break kernel data structure dependencies on public
(user accessible) ioctl returns.
* New VP ioctls added:
IOCTYPE Returns VP_IOC to the caller. Used to verify
that caller is talking to the VP device driver.
VP_GET_VPB Returns the kernel data structure (struct
vpblock) that use to be returned by VP_STATUS.
VP_DESTROY Performs an identical function as VP_UNCONFIG
but also zeros out the on-disk data structures.
This will force the user to create (VP_CREATE)
a new VP. The older VP_UNCONFIG ioctl should
be reserved for "guru" users.
VP_VERIFY Allows the caller to verify the integrity of a
synchronized mirror by reading equivalent blocks
on the two partitions and performing a buffer
compare.
VP_CANCEL Allows the caller to cancel an ongoing restore
or verify operation.
VP_READER_MODE By default, reads to a synchronized mirror
are generally distributed between the two
mirrored partitions, providing better
overall throughput. This option allows the
user to force synchronized reads to occur
ONLY on either the primary or secondary
partition.
VP_THROTTLE By default, a mirror restore (or verify)
operation is performed in a tight read/write
loop (or read/read-verify) resulting in a faster
restore/verify at the cost of disk subsystem
bandwidth. The restore throttle allows the user
to request an delay (in microseconds) between
loops to allow a fairer distribution of I/O's
on the disk subsystem.
VP_REPAIR When a mirrored disk fails and needs to be
replaced, the on disk VP data structures are
lost. This ioctl rebuilds the on-disk data
structures which results in a mirror suitable
for re-synchronization.
VP_MAXVP Simply returns the number of VP's that may be
configured in the system (as specified by the
unit field in the System configuration file).
VP_UPDATE Originally, the on-disk data structure
associated with a synchronized mirrored
partition was marked "dirty" on the first open,
and "clean" on the last close. This was done to
provide crash integrity on the mirror. This
enhancement changes this behavior two-fold:
A synchronized partition is only marked "dirty"
preceding the first write to the partition (not
at open). If the update timeout is set to zero
(the default), the partition remains "dirty"
until the last close. If the update timeout is
non-zero, then the on-disk state will be
automatically marked "clean" after the specified
timeout (in seconds) elapses without any more
write activity.
* Enhanced /sbin/vpinit as follows:
- Extended vpinit's ability to interpret device names
by allowing for basename entries instead of full
pathnames. For example, the following is now legal:
/sbin/vpinit vp1 1s0 2s0 3s0 4s0 5s0 6s0
and results in a 6 partition stripe.
- 9 new mirror options added:
-t Verify mirror.
-p {Report interval in seconds}
Display the progress of a restore or
verify operation.
-x Destroy a mirror. Like -u with on-disk
VP data structures invalidated also.
-o reader={primary|secondary|distributed}
-o throttle={# of usecs}
-o update={# of seconds}
-q Quiet mode. Suppress advisory messages
such as "Vp is already synchronized" as
well as other non-error messages.
-R Repair a mirror. Used when replacing a
failed disk.
-Z Determine if the specified VP is a root
device mirror. The vpinit exit code
returns the results.
- Updated to allow a mirror restore or verify operation
to be canceled via signal (SIGINT, etc). Previously,
once started, the restore operation could not be
canceled.
* Enhanced /usr/sbin/vpstat as follows:
- Extended vpstat's ability to interpret device names
as described above in /sbin/vpinit.
- Added "default display" mode. In the event of no VP
device being entered on the command line, all status
of devices of the selected type are displayed.
- Added command options to augment the "default
display" mode by specifying any combination of
unconfigured (-u), mirrored (-m), or striped (-s)
VPs. By default, only mirrored and striped VPs are
displayed.
- For verbose displays on mirrored VPs, display info
on new mirror options: update timeout, restore
throttle, and reader mode.
Object To Be Replaced:
/etc/conf/node.d/vp
/etc/conf/pack.d/vp/Driver.o
/etc/conf/pack.d/vp/space.c
/etc/conf/sdevice.d/vp
/sbin/vpinit
/usr/include/sys/vp.h
/usr/sbin/vpstat
Special Conditions for Installation:
The VP ioctl definitions found in /usr/include/sys/vp.h have changed
requiring end-users to recompile code that may access them.
Possible Side Effects:
None.
return to index
================================================================================
Concurrent Computer Corporation Software Development
Software Patch Report
Patch Name: zld-001
Date Issued: 06/05/98 16:17:42
Software Package: zld pkg (Version 4.2)
OS Release: PowerMAX OS 4.2
Architectures: moto
Platforms: Power Hawk 610/620/640, PowerStack, PowerStack II
Related Patches: none
Related SARS: none
Brief Description:
PowerMAX OS 4.2 zld package release updates
Problem Description:
1. Various minor bugs in the ZLD MPEG Decoder Driver were causing
occasional hangs on one or more ports and audio/video
synchronization problems.
* Entering fast foward took too long.
* Use of fast foward and/or rewind would frequently hang
the port.
Problem Resolution:
1. Various corrections and enhancements were made to the driver to
correct the performance and hang problems.
Object To Be Replaced:
/etc/conf/pack.d/zld/Driver.o
/usr/include/sys/zld.h
Special Conditions for Installation:
None.
Possible Side Effects:
None.
return to index
================================================================================
Concurrent Computer Corporation Software Development
Software Patch Report
Patch Name: zld-001
Date Issued: 06/05/98 16:17:42
Software Package: zld pkg (Version 4.2)
OS Release: PowerMAX OS 4.2
Architectures: moto
Platforms: Power Hawk 610/620/640, PowerStack, PowerStack II
Related Patches: none
Related SARS: none
Brief Description:
PowerMAX OS 4.2 zld package release updates
Problem Description:
1. Various minor bugs in the ZLD MPEG Decoder Driver were causing
occasional hangs on one or more ports and audio/video
synchronization problems.
* Entering fast foward took too long.
* Use of fast foward and/or rewind would frequently hang
the port.
Problem Resolution:
1. Various corrections and enhancements were made to the driver to
correct the performance and hang problems.
Object To Be Replaced:
/etc/conf/pack.d/zld/Driver.o
/usr/include/sys/zld.h
Special Conditions for Installation:
None.
Possible Side Effects:
None.
return to index
================================================================================
Concurrent Computer Corporation Software Development
Software Patch Report
Patch Name: zld-002
Date Issued: 10/02/98 15:25:30
Software Package: zld pkg (Version 4.2)
OS Release: PowerMAX OS 4.2
Architectures: moto
Platforms: Power Hawk 610/620/640, PowerStack, PowerStack II
Related Patches: none
Related SARS: none
Brief Description:
PowerMAX OS 4.2 zld package release updates
Problem Description:
1. Audio/Video synchronization (lip sync) is not maintained on certain
PAL format MPEG-2 videos. These videos have longer MPEG-2 header
blocks than other videos which have been working in the past. The
time stamp information is located in a different portion of the
header and is thus misread.
Problem Resolution:
1. The logic which reads the time stamps from the MPEG-2 videos has been
enhanced to read the header length and read the correct time stamp
value for all MPEG-2 headers.
Object To Be Replaced:
/etc/conf/pack.d/zld/Driver.o
Special Conditions for Installation:
None.
Possible Side Effects:
None.
return to index
================================================================================
Concurrent Computer Corporation Software Development
Software Patch Report
Patch Name: zld-002
Date Issued: 10/02/98 15:25:30
Software Package: zld pkg (Version 4.2)
OS Release: PowerMAX OS 4.2
Architectures: moto
Platforms: Power Hawk 610/620/640, PowerStack, PowerStack II
Related Patches: none
Related SARS: none
Brief Description:
PowerMAX OS 4.2 zld package release updates
Problem Description:
1. Audio/Video synchronization (lip sync) is not maintained on certain
PAL format MPEG-2 videos. These videos have longer MPEG-2 header
blocks than other videos which have been working in the past. The
time stamp information is located in a different portion of the
header and is thus misread.
Problem Resolution:
1. The logic which reads the time stamps from the MPEG-2 videos has been
enhanced to read the header length and read the correct time stamp
value for all MPEG-2 headers.
Object To Be Replaced:
/etc/conf/pack.d/zld/Driver.o
Special Conditions for Installation:
None.
Possible Side Effects:
None.
return to index
================================================================================