Kenneth D. Merry wrote: > > Did you also backport rev 1.35 and 1.36 of scsi_all.c? > You may need that as well.
Good catch, I missed that file. After applying that patch, they now seem to be detected correctly: da0 at mpt1 bus 0 target 0 lun 0 da0: <SEAGATE ST336732LW 2223> Fixed Direct Access SCSI-3 device da0: 320.000MB/s transfers (160.000MHz, offset 31, 16bit), Tagged Queueing Enabled da0: 34732MB (71132959 512 byte sectors: 255H 63S/T 4427C) da1 at mpt1 bus 0 target 1 lun 0 da1: <SEAGATE ST336732LW 2223> Fixed Direct Access SCSI-3 device da1: 320.000MB/s transfers (160.000MHz, offset 31, 16bit), Tagged Queueing Enabled da1: 34732MB (71132959 512 byte sectors: 255H 63S/T 4427C) The bad news is that any kind of extended disk activity (e.g. kernel building), results in a ton of unhealthy messages like this: mpt1: time out on request index = 0xe4 sequence = 0x00000cad mpt1: Status 00000001; Mask 00000001; Doorbell 24000000 request state On Chip SCSI IO Request @ 0xff807f34 Chain Offset 0x00 MsgFlags 0x00 MsgContext 0x000000e4 Bus: 0 TargetID 1 SenseBufferLength 32 LUN: 0x0 Control 0x01000000 WRITE SIMPLEQ DataLength 0x00004000 SenseBufAddr 0x0005d9e0 CDB[0:10] 2a 00 01 3f e1 9f 00 00 20 00 SE32 0xdc3c2830: Addr=0xd0f3000 FlagsLength=0x14001000 HOST_TO_IOC SE32 0xdc3c2838: Addr=0xd034000 FlagsLength=0x14002000 HOST_TO_IOC SE32 0xdc3c2840: Addr=0xd136000 FlagsLength=0xd5001000 HOST_TO_IOC LAST_ELEMENT END_OF_BUFFER END_OF_LIST mpt1: mpt_done: corrupted ccb, index = 0xe4 seq = 0x00000cad request state Timeout mpt_request: SCSI IO Request @ 0xff807e88 Chain Offset 0x00 MsgFlags 0x00 MsgContext 0x000000e4 Bus: 0 TargetID 1 SenseBufferLength 32 LUN: 0x0 Control 0x01000000 WRITE SIMPLEQ DataLength 0x00004000 SenseBufAddr 0x0005d9e0 CDB[0:10] 2a 00 01 3f e1 9f 00 00 20 00 SE32 0xdc3c2830: Addr=0xd0f3000 FlagsLength=0x14001000 HOST_TO_IOC SE32 0xdc3c2838: Addr=0xd034000 FlagsLength=0x14002000 HOST_TO_IOC SE32 0xdc3c2840: Addr=0xd136000 FlagsLength=0xd5001000 HOST_TO_IOC LAST_ELEMENT END_OF_BUFFER END_OF_LIST mpt_done: context reply: 0x000000e4 Did I miss any more pieces? Nothing under sys/cam seemed recent enough. Thanks, Lars -- Lars Eggert <[EMAIL PROTECTED]> USC Information Sciences Institute
smime.p7s
Description: S/MIME Cryptographic Signature
