Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 22 Jun 2012 21:58:47 +0300
From:      Alexander Motin <mav@FreeBSD.org>
To:        Mike Tancsa <mike@sentex.net>
Cc:        FreeBSD-STABLE Mailing List <freebsd-stable@freebsd.org>
Subject:   Re: svn commit: r237318 - in stable/8: share/man/man4 sys/cam sys/cam/scsi sys/conf
Message-ID:  <4FE4C067.1010705@FreeBSD.org>
In-Reply-To: <4FE4BC5F.30002@sentex.net>
References:  <201206201439.q5KEdaF9048424@svn.freebsd.org> <4FE4BC5F.30002@sentex.net>

next in thread | previous in thread | raw e-mail | index | archive | help
On 06/22/12 21:41, Mike Tancsa wrote:
> On 6/20/2012 10:39 AM, Alexander Motin wrote:
>> Author: mav
>> Date: Wed Jun 20 14:39:35 2012
>> New Revision: 237318
>> URL: http://svn.freebsd.org/changeset/base/237318
>>
>> Log:
>>    MFC r236712:
>>    To make CAM debugging easier, compile in some debug flags (CAM_DEBUG_INFO,
>>    CAM_DEBUG_CDB, CAM_DEBUG_PERIPH and CAM_DEBUG_PROBE) by default.
>>    List of these flags can be modified with CAM_DEBUG_COMPILE kernel option.
>>    CAMDEBUG kernel option still enables all possible debug, if not overriden.
>>
>>    Additional 50KB of kernel size is a good price for the ability to debug
>>    problems without rebuilding the kernel. In case where size is important,
>>    debugging can be compiled out by setting CAM_DEBUG_COMPILE option to 0.
>
> Hi,
> 	Not sure if this is the commit or not, but a kernel from the 18th seems to function normally, and a kernel from today has a great deal of messages like the ones below. I also dont know if this is just exposing an existing bug in the driver that was upto now hidden ?

That's not. That's a bit later.

> Boot time, I see the following
>
> (probe1:twa0:0:1:0): INQUIRY. CDB: 12 0 0 0 24 0
> (probe1:twa0:0:1:0): CAM status: Invalid Target ID
> (probe1:twa0:0:1:0): Error 22, Unretryable error
> (probe2:twa0:0:2:0): INQUIRY. CDB: 12 0 0 0 24 0
> (probe2:twa0:0:2:0): CAM status: Invalid Target ID
> (probe2:twa0:0:2:0): Error 22, Unretryable error
> (probe3:twa0:0:3:0): INQUIRY. CDB: 12 0 0 0 24 0
> (probe3:twa0:0:3:0): CAM status: Invalid Target ID
> (probe3:twa0:0:3:0): Error 22, Unretryable error
> (probe4:twa0:0:4:0): INQUIRY. CDB: 12 0 0 0 24 0
> (probe4:twa0:0:4:0): CAM status: Invalid Target ID
> (probe4:twa0:0:4:0): Error 22, Unretryable error
> (probe15:twa0:0:15:0): INQUIRY. CDB: 12 0 0 0 24 0
> (probe15:twa0:0:15:0): CAM status: Invalid Target ID
> (probe15:twa0:0:15:0): Error 22, Unretryable error
> (probe16:twa0:0:16:0): INQUIRY. CDB: 12 0 0 0 24 0
> (probe16:twa0:0:16:0): CAM status: Invalid Target ID
> (probe16:twa0:0:16:0): Error 22, Unretryable error
> (probe17:twa0:0:17:0): INQUIRY. CDB: 12 0 0 0 24 0
> (probe17:twa0:0:17:0): CAM status: Invalid Target ID
> (probe17:twa0:0:17:0): Error 22, Unretryable error
> (probe18:twa0:0:18:0): INQUIRY. CDB: 12 0 0 0 24 0
> (probe18:twa0:0:18:0): CAM status: Invalid Target ID
> (probe18:twa0:0:18:0): Error 22, Unretryable error
> (probe19:twa0:0:19:0): INQUIRY. CDB: 12 0 0 0 24 0
> (probe19:twa0:0:19:0): CAM status: Invalid Target ID
> (probe19:twa0:0:19:0): Error 22, Unretryable error
> (probe20:twa0:0:20:0): INQUIRY. CDB: 12 0 0 0 24 0
> (probe20:twa0:0:20:0): CAM status: Invalid Target ID
> (probe20:twa0:0:20:0): Error 22, Unretryable error
> (probe21:twa0:0:21:0): INQUIRY. CDB: 12 0 0 0 24 0
> (probe21:twa0:0:21:0): CAM status: Invalid Target ID
> (probe21:twa0:0:21:0): Error 22, Unretryable error
> (probe22:twa0:0:22:0): INQUIRY. CDB: 12 0 0 0 24 0
> (probe22:twa0:0:22:0): CAM status: Invalid Target ID
> (probe22:twa0:0:22:0): Error 22, Unretryable error
> (probe23:twa0:0:23:0): INQUIRY. CDB: 12 0 0 0 24 0
> (probe23:twa0:0:23:0): CAM status: Invalid Target ID
> (probe23:twa0:0:23:0): Error 22, Unretryable error
> (probe24:twa0:0:24:0): INQUIRY. CDB: 12 0 0 0 24 0
> (probe24:twa0:0:24:0): CAM status: Invalid Target ID
> (probe24:twa0:0:24:0): Error 22, Unretryable error
> (probe25:twa0:0:25:0): INQUIRY. CDB: 12 0 0 0 24 0
> (probe25:twa0:0:25:0): CAM status: Invalid Target ID
> (probe25:twa0:0:25:0): Error 22, Unretryable error
> (probe26:twa0:0:26:0): INQUIRY. CDB: 12 0 0 0 24 0
> (probe26:twa0:0:26:0): CAM status: Invalid Target ID
> (probe26:twa0:0:26:0): Error 22, Unretryable error
> (probe5:twa0:0:5:0): INQUIRY. CDB: 12 0 0 0 24 0
> (probe5:twa0:0:5:0): CAM status: Invalid Target ID
> (probe5:twa0:0:5:0): Error 22, Unretryable error
> (probe6:twa0:0:6:0): INQUIRY. CDB: 12 0 0 0 24 0
> (probe6:twa0:0:6:0): CAM status: Invalid Target ID
> (probe6:twa0:0:6:0): Error 22, Unretryable error
> (probe7:twa0:0:7:0): INQUIRY. CDB: 12 0 0 0 24 0
> (probe7:twa0:0:7:0): CAM status: Invalid Target ID
> (probe7:twa0:0:7:0): Error 22, Unretryable error
> (probe8:twa0:0:8:0): INQUIRY. CDB: 12 0 0 0 24 0
> (probe8:twa0:0:8:0): CAM status: Invalid Target ID
> (probe8:twa0:0:8:0): Error 22, Unretryable error
> (probe9:twa0:0:9:0): INQUIRY. CDB: 12 0 0 0 24 0
> (probe9:twa0:0:9:0): CAM status: Invalid Target ID
> (probe9:twa0:0:9:0): Error 22, Unretryable error
> (probe10:twa0:0:10:0): INQUIRY. CDB: 12 0 0 0 24 0
> (probe10:twa0:0:10:0): CAM status: Invalid Target ID
> (probe10:twa0:0:10:0): Error 22, Unretryable error
> (probe11:twa0:0:11:0): INQUIRY. CDB: 12 0 0 0 24 0
> (probe11:twa0:0:11:0): CAM status: Invalid Target ID
> (probe11:twa0:0:11:0): Error 22, Unretryable error
> (probe12:twa0:0:12:0): INQUIRY. CDB: 12 0 0 0 24 0
> (probe12:twa0:0:12:0): CAM status: Invalid Target ID
> (probe12:twa0:0:12:0): Error 22, Unretryable error
> (probe13:twa0:0:13:0): INQUIRY. CDB: 12 0 0 0 24 0
> (probe13:twa0:0:13:0): CAM status: Invalid Target ID
> (probe13:twa0:0:13:0): Error 22, Unretryable error
> (probe14:twa0:0:14:0): INQUIRY. CDB: 12 0 0 0 24 0
> (probe14:twa0:0:14:0): CAM status: Invalid Target ID
> (probe14:twa0:0:14:0): Error 22, Unretryable error
> (probe27:twa0:0:27:0): INQUIRY. CDB: 12 0 0 0 24 0
> (probe27:twa0:0:27:0): CAM status: Invalid Target ID
> (probe27:twa0:0:27:0): Error 22, Unretryable error
> (probe28:twa0:0:28:0): INQUIRY. CDB: 12 0 0 0 24 0
> (probe28:twa0:0:28:0): CAM status: Invalid Target ID
> (probe28:twa0:0:28:0): Error 22, Unretryable error
> (probe29:twa0:0:29:0): INQUIRY. CDB: 12 0 0 0 24 0
> (probe29:twa0:0:29:0): CAM status: Invalid Target ID
> (probe29:twa0:0:29:0): Error 22, Unretryable error
> (probe30:twa0:0:30:0): INQUIRY. CDB: 12 0 0 0 24 0
> (probe30:twa0:0:30:0): CAM status: Invalid Target ID
> (probe30:twa0:0:30:0): Error 22, Unretryable error
> (probe31:twa0:0:31:0): INQUIRY. CDB: 12 0 0 0 24 0
> (probe31:twa0:0:31:0): CAM status: Invalid Target ID
> (probe31:twa0:0:31:0): Error 22, Unretryable error

That is probably bug in a driver. It should return CAM_SEL_TIMEOUT 
instead of CAM_TID_INVALID for missing devices. You should seen some of 
these errors even before if booted with verbose messages enabled.

> And then with moderate disk activity,
>
> Jun 22 14:22:57 offsite2 kernel: (da0:twa0:0:0:0): WRITE(10). CDB: 2a 0 18 af 19 e2 0 0 40 0
> Jun 22 14:22:57 offsite2 kernel: (da0:twa0:0:0:0): CAM status: Unconditionally Re-queue Request
> Jun 22 14:22:57 offsite2 kernel: (da0:twa0:0:0:0): Retrying command
> Jun 22 14:22:57 offsite2 kernel: (da0:twa0:0:0:0): WRITE(10). CDB: 2a 0 18 ad 78 92 0 0 10 0
> Jun 22 14:22:57 offsite2 kernel: (da0:twa0:0:0:0): CAM status: Unconditionally Re-queue Request
> Jun 22 14:22:57 offsite2 kernel: (da0:twa0:0:0:0): Retrying command
> Jun 22 14:22:58 offsite2 kernel: (da0:twa0:0:0:0): WRITE(10). CDB: 2a 0 18 95 20 ba 0 0 8 0
> Jun 22 14:22:58 offsite2 kernel: (da0:twa0:0:0:0): CAM status: Unconditionally Re-queue Request
> Jun 22 14:22:58 offsite2 kernel: (da0:twa0:0:0:0): Retrying command
> Jun 22 14:22:59 offsite2 kernel: (da0:twa0:0:0:0): WRITE(10). CDB: 2a 0 18 af 2f e2 0 0 40 0
> Jun 22 14:22:59 offsite2 kernel: (da0:twa0:0:0:0): CAM status: Unconditionally Re-queue Request
> Jun 22 14:22:59 offsite2 kernel: (da0:twa0:0:0:0): Retrying command
> Jun 22 14:22:59 offsite2 kernel: (da0:twa0:0:0:0): WRITE(10). CDB: 2a 0 18 af 30 62 0 0 40 0
> Jun 22 14:22:59 offsite2 kernel: (da0:twa0:0:0:0): CAM status: Unconditionally Re-queue Request
> Jun 22 14:22:59 offsite2 kernel: (da0:twa0:0:0:0): Retrying command

That is my fault and it is already fixed at HEAD at r237446. I'll merge 
it soon. It should be harmless. Sorry.

-- 
Alexander Motin



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4FE4C067.1010705>