twe — 3ware 5000/6000/7000/8000 series PATA/SATA RAID adapter driver

Authors

       The twe driver and manual page were written by Michael Smith <msmith@FreeBSD.org>.

       Extensive work done on the driver by Vinod Kashyap <vkashyap@FreeBSD.org> and Paul Saab <ps@FreeBSD.org>.

Bugs

       The controller cannot handle I/O transfers that are not aligned to a  512-byte  boundary.   In  order  to
       support  raw  device access from user-space, the driver will perform alignment fixup on non-aligned data.
       This process is inefficient, and thus  in  order  to  obtain  best  performance  user-space  applications
       accessing the device should do so with aligned buffers.

Debian                                           August 15, 2004                                          TWE(4)

Description

       The  twe  driver  provides  support  for AMCC's 3ware 5000/6000/7000/8000 series PATA/SATA RAID adapters.
       These adapters were formerly known as “3ware Escalade”.

       These devices support 2, 4, 8, or 12 ATA disk drives and provide RAID0 (striping) and  RAID1  (mirroring)
       functionality.

Diagnostics

Controllerinitialisationphasetwe%d:microcontrollernotready

The controller's onboard CPU is not reporting that it is ready; this may be due to either a board or
system failure. Initialisation has failed.

twe%d:noattentioninterrupttwe%d:can'tdrainAENqueuetwe%d:resetnotreportedtwe%d:controllererrorsdetectedtwe%d:can'tdrainresponsequeuetwe%d:reset%dfailed,tryingagain

The controller is not responding correctly to the driver's attempts to reset and initialise it. This
process is retried several times.

twe%d:can'tinitialisecontroller,givingup

Several attempts to reset and initialise the controller have failed; initialisation has failed and the
driver will not attach to this controller.

Driverinitialisation/shutdownphasetwe%d:registerwindownotavailabletwe%d:can'tallocateregisterwindowtwe%d:can'tallocateparentDMAtagtwe%d:can'tallocateinterrupttwe%d:can'tsetupinterrupttwe%d:can'testablishconfigurationhook

A resource allocation error occurred while initialising the driver; initialisation has failed and the
driver will not attach to this controller.

twe%d:can'tdetectattachedunits

Fetching the list of attached units failed; initialisation has failed.

twe%d:errorfetchingcapacityforunit%dtwe%d:errorfetchingstateforunit%dtwe%d:errorfetchingdescriptorsizeforunit%dtwe%d:errorfetchingdescriptorforunit%dtwe%d:device_add_childfailedtwe%d:bus_generic_attachreturned%d

Creation of the disk devices failed, either due to communication problems with the adapter or due to
resource shortage; attachment of one or more units may have been aborted.

Operationalphasetwe%d:commandcompleted-%s

A command was reported completed with a warning by the controller. The warning may be one of:

redundant/inconsequentialrequestignoredfailedtowritezeroestoLBA0failedtoprofileTwinStorzonestwe%d:commandfailed-%s

A command was reported as failed by the controller. The failure message may be one of:

abortedduetosystemcommandorreconfigurationabortedaccesserroraccessviolationdevicefailurecontrollererrortimedoutinvalidunitnumberunitnotavailableundefinedopcoderequestincompatiblewithunitinvalidrequestfirmwareerror,resetrequested

The command will be returned to the operating system after a fatal error.

twe%d:commandfailedsubmission-controllerwedged

A command could not be delivered to the controller because the controller is unresponsive.

twe%d:AEN:<%s>

The controller has reported a change in status using an AEN (Asynchronous Event Notification). The
following AENs may be reported:

queueemptysoftresetdegradedmirrorcontrollererrorrebuildfailrebuilddoneincompleteunitinitialisationdoneuncleanshutdowndetecteddrivetimeoutdriveerrorrebuildstartedaenqueuefull

AENs are also queued internally for use by management tools.

twe%d:errorpollingforsignalledAENs

The controller has reported that one or more status messages are ready for the driver, but attempting to
fetch one of these has returned an error.

twe%d:AENqueueoverflow,lostAEN<%s>

A status message was retrieved from the controller, but there is no more room to queue it in the driver.
The message is lost (but will be printed to the console).

twe%d:missingexpectedstatusbits%stwe%d:unexpectedstatusbits%s

A check of the controller's status bits indicates an unexpected condition.

twe%d:hostinterrupt

The controller has signalled a host interrupt. This serves an unknown purpose and is ignored.

twe%d:commandinterrupt

The controller has signalled a command interrupt. This is not used, and will be disabled.

twe%d:controllerresetinprogress...

The controller is being reset by the driver. Typically this is done when the driver has determined that
the controller is in an unrecoverable state.

twe%d:can'tresetcontroller,givingup

The driver has given up on resetting the controller. No further I/O will be handled.

controllerresetdone,%dcommandsrestarted

The controller was successfully reset, and outstanding commands were restarted.

Hardware

       The twe driver supports the following PATA/SATA RAID controllers:

       •   AMCC's 3ware 5000 series
       •   AMCC's 3ware 6000 series
       •   AMCC's 3ware 7000-2
       •   AMCC's 3ware 7006-2
       •   AMCC's 3ware 7500-4LP
       •   AMCC's 3ware 7500-8
       •   AMCC's 3ware 7500-12
       •   AMCC's 3ware 7506-4LP
       •   AMCC's 3ware 7506-8
       •   AMCC's 3ware 7506-12
       •   AMCC's 3ware 8006-2LP
       •   AMCC's 3ware 8500-4LP
       •   AMCC's 3ware 8500-8
       •   AMCC's 3ware 8500-12
       •   AMCC's 3ware 8506-4LP
       •   AMCC's 3ware 8506-8
       •   AMCC's 3ware 8506-8MI
       •   AMCC's 3ware 8506-12
       •   AMCC's 3ware 8506-12MI

Name

       twe — 3ware 5000/6000/7000/8000 series PATA/SATA RAID adapter driver

Synopsis

       To compile this driver into the kernel, place the following lines in your kernel configuration file:

             devicepcidevicetwe

       Alternatively, to load the driver as a module at boot time, place the following line in loader.conf(5):

             twe_load="YES"