Compaq Smart Array 4200 controller question
Andrew Heyn
aheyn at jmsent.com
Wed Feb 2 16:32:52 PST 2005
Hi,
I got a 6-CURRENT kernel so I could show you the messages it creates when it
times out.
Unfortunately, it doesn't seem very useful, but here it is:
ida0: ida_timeout() qactive 1
ida0: IDA_INTERRUPTS
ida0: R_CMD_FIFO: 00000000
R_DONE_FIFO:00000000
R_INT_MASK: 00000000
R_STATUS: 00000000
R_INT_PENDING
Sometimes I get "soft read error" before the
messages above.
ida0: <Compaq Integrated Array controller> port 0x2400-0x24ff mem
0xf5000000-0xf5ffffff,0xf6000000-0xf6ffffff irq 24 at device 14.0 on pci0
ida0: [GIANT-LOCKED]
ida0: drives=1 firm_rev=1.50
idad0: <Compaq Logical Drive> on ida0
idad0: 17268MB (35365440 sectors), blocksize=512
isab0: <PCI-ISA bridge> at device 15.0 on pci0
compaq# ./idacontrol show
cmd_show_all()
[Compaq Integrated Array controller]
Controller uptime: 00 hours 59 minutes 39 seconds
Firmware Version: 1.50 (running) 1.50 (ROM)
Revision -
Hardware: 1
Marketing: A
SCSI bus count: 2
Max drives per bus: 16
Maximum request: 65535 blocks
Logical drive 0: 17268MB (35365440 sectors), blocksize=512
Status: Logical drive ok
Mode: Mirroring (RAID1)
Drive ID: 00000000
Drive Label:
bus 1 target 1 lun 0:
enclosure 0, bay 1, connector 2J
<FUJITSU MAG3182L SUN18G 02578099 1111> direct-access
17270MB (35370341 512 byte sectors, 1088 reserved)
Async, Wide - Configured in a logical volume.
bus 1 target 3 lun 0:
enclosure 0, bay 3, connector 2J
<FUJITSU MAJ3182MC 50029712 5508> direct-access
17362MB (35558286 512 byte sectors, 1088 reserved)
Async, Wide - Configured in a logical volume.
bus 1 target 7 lun 0:
enclosure 0, bay 7, connector 2J
<COMPAQ PROLIANT 4L4I JB21> non-disk
Async
Hope this sheds some light,
Andrew
(don't forget to cc me)
-----Original Message-----
From: Matthew N. Dodd [mailto:mdodd at FreeBSD.ORG]
Sent: Wednesday, February 02, 2005 8:06 AM
To: Andrew Heyn
Cc: freebsd-hardware at FreeBSD.ORG
Subject: RE: Compaq Smart Array 4200 controller question
On Wed, 2 Feb 2005, Andrew Heyn wrote:
> I was going to use that program given to me, but untarring the kernel
> source tree would cause programs to hang indefinitely on biord...and
> then I wouldnt be able to get it done.
The change to report the error was added recently but I don't see how
reporting errors could cause your problem.
I suspect the firmware on the controller is locking up. Code in -CURRENT
will perform a register dump on command timeout, which is the usual
indicator of a lockup.
I'd go looking for the latest firmware for your controller.
--
10 40 80 C0 00 FF FF FF FF C0 00 00 00 00 10 AA AA 03 00 00 00 08 00
More information about the freebsd-hardware
mailing list