Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

ips(4) [freebsd man page]

IPS(4)							   BSD Kernel Interfaces Manual 						    IPS(4)

NAME
ips -- IBM/Adaptec ServeRAID controller driver SYNOPSIS
To compile this driver into the kernel, place the following lines in your kernel configuration file: device pci device scbus device ips Alternatively, to load the driver as a module at boot time, place the following line in loader.conf(5): ips_load="YES" DESCRIPTION
The ips driver claims to support the IBM (now Adaptec) ServeRAID series SCSI controller cards. These cards come with a built in configuration utility stored in the firmware known as the ISPR. This utility is accessed with the <Ctrl+I> key combination during the initial card POST. It is highly recommended that this utility be used to configure the card before attempting to diagnose the below error messages. In some cases, the ips driver can have difficulties attaching during the system initialization period. To avoid these difficulties, set the hw.ips.0.disable tunable to 1. It will prevent the driver from attaching. HARDWARE
Controllers supported by the ips driver include: o IBM ServeRAID 3H o ServeRAID 4L/4M/4H o ServeRAID Series 5 o ServeRAID 6i/6M o ServeRAID 7t/7k/7M Newer ServeRAID controllers are supported by the aac(4) or mfi(4) driver. DIAGNOSTICS
Several error codes may be shown when the card initializes the IBM ISPR utility and are independent of FreeBSD. ips%d: failed to get adapter configuration data from device ips%d: failed to get drive configuration data from device Unable to obtain adapter or drive configuration. ips%d iobuf error A buffer input/output error has occurred. [ENXIO] General adapter errors: Attaching bus failed This message is undocumented. WARNING: command timeout. Adapter is in toaster mode, resetting A command timeout has caused the adapter to be reset. AIEE! adapter reset failed, giving up and going home! Have a nice day An error occurred while attempting to reset the adapter. unable to get adapter configuration unable to get drive configuration There was an error when attempting to get configuration information. Adapter error during initialization. adapter initialization failed There was an error while attempting to initialize the adapter. adapter failed config check adapter clear failed There was an error while checking the adapter. device is disabled The adapter is disabled. resource allocation failed irq allocation failed irq setup failed The driver was unable to allocate resources for the device. Error messages due to DMA: can't alloc command dma tag can't alloc SG dma tag can't alloc dma tag for statue queue dmamap failed Failure to map or allocate DMA resources. Cache, buffer, and command errors: failed to initialize command buffers no mem for command slots! The ips driver will return [ENOMEM] in such cases. ERROR: unable to get a command! can't flush cache! ERROR: cache flush command failed! ERROR: unable to get a command! can't update nvram ERROR: nvram update command failed! ERROR: unable to get a command! can't sync cache! ERROR: cache sync command failed! ERROR: unable to get a command! can't sync cache! ERROR: etable command failed! COMPATIBILITY
Unlike many of the other SCSI devices in FreeBSD, the ips driver does not use the cam(4) SCSI subsystem. SEE ALSO
aac(4), ch(4), da(4), mfi(4), sysctl(8) AUTHORS
The ips driver was written by David Jefferys and Scott Long <scottl@FreeBSD.org>. This manual page was written by Tom Rhodes <trhodes@FreeBSD.org>. BSD
August 7, 2009 BSD

Check Out this Related Man Page

socal(7D)							      Devices								 socal(7D)

NAME
socal - Serial Optical Controller for Fibre Channel Arbitrated Loop (SOC+) device driver SYNOPSIS
socal@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 can connect to a Fibre Channel Arbitrated Loop (FC-AL). The socal device driver is a nexus driver and implements portions of the FC-2 and FC-4 layers of FC-AL. FILES
/kernel/drv/socal ELF Kernel Module ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Architecture |SPARC | +-----------------------------+-----------------------------+ SEE ALSO
sbus(4), sf(7D), ssd(7D) Writing Device Drivers ANSI X3.230-1994, Fibre Channel Physical and Signalling Interface (FC-PH) ANSI X3.272-1996, Fibre Channel Arbitrated Loop (FC-AL) Fibre Channel Private Loop SCSI Direct Attach (FC-PLDA) DIAGNOSTICS
The messages described below may appear on system console in addition to being logged. On the console, these messages are preceded by: socal%d: port %a where %d is the instance number of the socal controller and %a is the port on the host adapter. Fibre Channel Loop is ONLINE The Fibre Channel loop is now online. Fibre Channel Loop is OFFLINE The Fibre Channel loop is now offline. attach failed: device in slave-only slot. Move soc+ card to another slot. attach failed: bad soft state. Driver did not attach, devices will be inaccessible. attach failed: unable to alloc xport struct. Driver did not attach, devices will be inaccessible. 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: unable to access host adapter XRAM Driver was unable to access device RAM; check for bad hardware. Driver did not attach to device, devices will be inaccessible. attach failed: unable to write host adapter XRAM Driver was unable to write device RAM; check for bad hardware. Driver did not attach to device, devices will be inaccessible. attach failed: read/write mismatch in XRAM Driver was unable to verify device RAM; check for bad hardware. Driver did not attach to device, devices will be inaccessible. SunOS 5.10 9 May 1997 socal(7D)
Man Page