soc(7D)

NAME | SYNOPSIS | DESCRIPTION | FILES | SEE ALSO | DIAGNOSTICS

NAME

soc– Serial Optical Controller (SOC) device driver

SYNOPSIS

soc@sbus-slot,0

DESCRIPTION

The Fibre Channel Host Bus Adapter is an SBus card which implements two full duplex Fibre Channel interfaces. Each Fibre Channel interface supports a point to point interface to another Fibre Channel device.

The soc device driver is a nexus driver. The soc driver implements portions of the FC-2 and FC-4 layers of the Fibre Channel.

Note: The SPARCstorage Array is obsolete. Support for this device will be removed in a future version of Solaris.

FILES

/kernel/drv/soc

ELF Kernel Module

SEE ALSO

sbus(4), pln(7D), ssd(7D)

Writing Device Drivers

DIAGNOSTICS

The messages described below are some that may appear on system console, as well as being logged.

On the console these messages are preceded by

---

soc%d: port %a

---

where %d is the instance number of the soc controller and %a is the port on the host adapter.

Fibre Channel is ONLINE

The Fibre Channel is now online to the device.

Fibre Channel is OFFLINE

The Fibre Channel connection is now offline.

INCORRECT WWN: Found: xxxx,xxxxxxxx Expected: yyyy,yyyyyyyy

This message means that the soc re-logged into a device after the Fibre Channel connection went offline and back online and the World Wide Name of the device is now different. This probably means the cable has been plugged into another device.

attach failed: unable to map eeprom

Driver was unable to map device memory; check for bad hardware. Driver did not attach to device, devices will be inaccessible.

attach failed: unable to map XRAM

Driver was unable to map device memory; check for bad hardware. Driver did not attach to device, devices will be inaccessible.

attach failed: unable to map registers

Driver was unable to map device registers; check for bad hardware. Driver did not attach to device, devices will be inaccessible.

attach failed: unable to access status register

Driver was unable to map device registers; check for bad hardware. Driver did not attach to device, devices will be inaccessible.

attach failed: unable to install interrupt handler

Driver was not able to add the interrupt routine to the kernel. Driver did not attach to device, devices will be inaccessible.

attach failed: could not alloc offline packet structure

Driver was unable to allocate space for the internal state structure. Driver did not attach to device, devices will be inaccessible.

NAME | SYNOPSIS | DESCRIPTION | FILES | SEE ALSO | DIAGNOSTICS