Known Bugs

The following list is subject to change at any time.

Network Device Removal Fails When a Program Is Holding the Device Open (5054195)

If a process is holding open a network device, any DR operation that would involve that device fails. Daemons and processes that hold reference counts stop DR operations from completing.

Workaround: As superuser, perform the following steps:

1. Remove or rename the /rplboot directory.

2. Shut down NFS services.

   # sh /etc/init.d/nfs.server stop

3. Shut down Boot Server services.

   # sh /etc/init.d/boot.server stop

4. Perform the DR detach operation.

5. Restart NFS services.

   # sh /etc/init.d/nfs.server start

6. Restart Boot Server services.

   # sh /etc/init.d/boot.server start

Memory Interleaving Set Incorrectly After a Fatal Reset (4156075)

Memory interleaving is left in an incorrect state when a Sun Enterprise5 x500 server is rebooted after a fatal reset. Subsequent DR operations fail. The problem only occurs on systems with memory interleaving set to min.

Workaround: Choose one of the following options:

• To clear the problem, manually reset the system at the OK prompt.

• To avoid the problem, set the NVRAM memory-interleave property to max.

  The second option causes memory to be interleaved whenever the system is booted. However, this option might be unacceptable because a memory board that contains interleaved memory cannot be dynamically unconfigured. See Cannot Unconfigure a CPU/Memory Board That Has Interleaved Memory (4210234).

Cannot Unconfigure a CPU/Memory Board That Has Interleaved Memory (4210234)

To unconfigure and subsequently disconnect a CPU board with memory or a memory-only board, first unconfigure the memory. However, if the memory on the board is interleaved with memory on other boards, the memory cannot currently be unconfigured dynamically.

Memory interleaving can be displayed by using the prtdiag or the cfgadm commands.

Workaround: Shut down the system before servicing the board, then reboot afterward. To permit future DR operations on the CPU/memory board, set the NVRAM memory-interleave property to min. See also Memory Interleaving Set Incorrectly After a Fatal Reset (4156075) for a related discussion about interleaved memory.

Cannot Unconfigure a CPU/Memory Board That Has Permanent Memory (4210280)

To unconfigure and subsequently disconnect a CPU board with memory or a memory-only board, first unconfigure the memory. However, some memory cannot currently be relocated. This memory is considered permanent.

Permanent memory on a board is marked “permanent” in the cfgadm status display:

# cfgadm -s cols=ap_id:type:info
Ap_Id Type Information
ac0:bank0 memory slot3 64Mb base 0x0 permanent
ac0:bank1 memory slot3 empty
ac1:bank0 memory slot5 empty
ac1:bank1 memory slot5 64Mb base 0x40000000

In this example, the board in slot3 has permanent memory and so cannot be removed.

Workaround: Shut down the system before servicing the board, then reboot afterward.

cfgadm Disconnect Fails When Running Concurrent cfgadm Commands (4220105)

If a cfgadm process is running on one board, an attempt to simultaneously disconnect a second board fails. The following error message is displayed:

cfgadm: Hardware specific failure: 
disconnect failed: nexus error during detach:address

Workaround: Run only one cfgadm operation at a time. Allow a cfgadm operation that is running on one board to finish before you start a cfgadm disconnect operation on a second board.