mpt driver problem?

Bruno Afonso brunomiguel at dequim.ist.utl.pt
Tue Dec 6 07:21:44 GMT 2005


Hi,

I have a box that's running a scsi card that uses the mpt driver. This 
is now running 6.0:

Dec  6 07:14:04 ribossoma kernel: mpt0: <LSILogic 1030 Ultra4 Adapter> 
port 0xc400-0xc4ff mem 0xfea90000-0xfea9ffff,0xfea80000-0xfea8ffff irq 
19 at device 3.0 on
Dec  6 07:14:04 ribossoma kernel: mpt0: [GIANT-LOCKED]
Dec  6 07:14:04 ribossoma kernel: mpt0: MPI Version=1.2.6.0
Dec  6 07:14:04 ribossoma kernel: mpt0: Unhandled Event Notify Frame. 
Event 0xa.
Dec  6 07:14:04 ribossoma kernel: mpt0: Capabilities: ( RAID-1 SAFTE )
Dec  6 07:14:04 ribossoma kernel: mpt0: 0 Active Volumes (1 Max)
Dec  6 07:14:04 ribossoma kernel: mpt0: 0 Hidden Drive Members (3 Max)
Dec  6 07:14:04 ribossoma kernel: mpt1: <LSILogic 1030 Ultra4 Adapter> 
port 0xc800-0xc8ff mem 0xfeaf0000-0xfeafffff,0xfeae0000-0xfeaeffff irq 
18 at device 3.1 on
Dec  6 07:14:04 ribossoma kernel: mpt1: [GIANT-LOCKED]
Dec  6 07:14:04 ribossoma kernel: mpt1: MPI Version=1.2.6.0
Dec  6 07:14:04 ribossoma kernel: mpt1: Unhandled Event Notify Frame. 
Event 0xa.
Dec  6 07:14:04 ribossoma kernel: mpt1: Capabilities: ( RAID-1 SAFTE )
Dec  6 07:14:04 ribossoma kernel: mpt1: 0 Active Volumes (1 Max)
Dec  6 07:14:04 ribossoma kernel: mpt1: 0 Hidden Drive Members (3 Max)

Dec  6 07:14:04 ribossoma kernel: da0 at mpt0 bus 0 target 0 lun 0
Dec  6 07:14:04 ribossoma kernel: da0: <SEAGATE ST336607LW 0007> Fixed 
Direct Access SCSI-3 device
Dec  6 07:14:04 ribossoma kernel: da0: 320.000MB/s transfers 
(160.000MHz, offset 63, 16bit), Tagged Queueing Enabled
Dec  6 07:14:04 ribossoma kernel: da0: 35003MB (71687372 512 byte 
sectors: 255H 63S/T 4462C)


The problem appears randomly on boots, meaning that it does not show 
indeed on EVERY boot, but afterwards, every so often. This is what 
typically appears:

Dec  6 07:14:27 ribossoma kernel: mpt0: Request 0xc24755a8 Timed out.
Dec  6 07:14:27 ribossoma kernel: mpt0: Attempting to Abort Req 0xc24755a8
Dec  6 07:14:28 ribossoma kernel: (da0:mpt0:0:0:0): READ(10). CDB: 28 0 
0 f0 88 87 0 0 48 0
Dec  6 07:14:28 ribossoma kernel: (da0:mpt0:0:0:0): CAM Status: SCSI 
Status Error
Dec  6 07:14:28 ribossoma kernel: (da0:mpt0:0:0:0): SCSI Status: Check 
Condition
Dec  6 07:14:28 ribossoma kernel: (da0:mpt0:0:0:0): UNIT ATTENTION asc:29,2
Dec  6 07:14:28 ribossoma kernel: (da0:mpt0:0:0:0): Scsi bus reset 
occurred field replaceable unit: 2
Dec  6 07:14:28 ribossoma kernel: (da0:mpt0:0:0:0): Retrying Command 
(per Sense Data)
Dec  6 07:14:28 ribossoma kernel: mpt0: Request 0xc2475508 Timed out.
Dec  6 07:14:28 ribossoma kernel: mpt0: Attempting to Abort Req 0xc2475508
Dec  6 07:14:29 ribossoma kernel: (da0:mpt0:0:0:0): READ(10). CDB: 28 0 
0 f0 84 a7 0 0 28 0
Dec  6 07:14:29 ribossoma kernel: (da0:mpt0:0:0:0): CAM Status: SCSI 
Status Error
Dec  6 07:14:29 ribossoma kernel: (da0:mpt0:0:0:0): SCSI Status: Check 
Condition
Dec  6 07:14:29 ribossoma kernel: (da0:mpt0:0:0:0): UNIT ATTENTION asc:29,2
Dec  6 07:14:29 ribossoma kernel: (da0:mpt0:0:0:0): Scsi bus reset 
occurred field replaceable unit: 2
Dec  6 07:14:29 ribossoma kernel: (da0:mpt0:0:0:0): Retrying Command 
(per Sense Data)
Dec  6 07:14:30 ribossoma kernel: mpt0: Request 0xc24756c0 Timed out.
Dec  6 07:14:30 ribossoma kernel: mpt0: Attempting to Abort Req 0xc24756c0
Dec  6 07:14:30 ribossoma kernel: (da0:mpt0:0:0:0): READ(10). CDB: 28 0 
0 ec cb af 0 0 40 0
Dec  6 07:14:30 ribossoma kernel: (da0:mpt0:0:0:0): CAM Status: SCSI 
Status Error
Dec  6 07:14:30 ribossoma kernel: (da0:mpt0:0:0:0): SCSI Status: Check 
Condition
Dec  6 07:14:30 ribossoma kernel: (da0:mpt0:0:0:0): UNIT ATTENTION asc:29,2
Dec  6 07:14:30 ribossoma kernel: (da0:mpt0:0:0:0): Scsi bus reset 
occurred field replaceable unit: 2
Dec  6 07:14:30 ribossoma kernel: (da0:mpt0:0:0:0): Retrying Command 
(per Sense Data)


I'd like to know if this is a serious problem with hardware or the 
driver itself. Should I worry? I know that some work is being done on 
mpt but I cannot use -current as this is a production box. I have used a 
-stable and it didn't improve so now I'm back to 6.0. I'll provide more 
information if needed.


Thanks
Bruno Afonso



More information about the freebsd-scsi mailing list