Re: svn commit: r237318 - in stable/8: share/man/man4 sys/cam sys/cam/scsi sys/conf
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 ? 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
Re: svn commit: r237318 - in stable/8: share/man/man4 sys/cam sys/cam/scsi sys/conf
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):
Re: svn commit: r237318 - in stable/8: share/man/man4 sys/cam sys/cam/scsi sys/conf
On Friday, June 22, 2012 2:41:35 pm Mike Tancsa wrote: Using jhb's handy pciconf from HEAD, I see (pciconf -lvcbe) twa0@pci0:2:0:0:class=0x010400 card=0x100413c1 chip=0x100413c1 rev=0x01 hdr=0x00 vendor = '3ware Inc' device = '9650SE SATA-II RAID PCIe' class = mass storage subclass = RAID bar [10] = type Prefetchable Memory, range 64, base 0x81c00, size 33554432, enabled bar [18] = type Memory, range 64, base 0xe242, size 4096, enabled bar [20] = type I/O Port, range 32, base 0x4000, size 256, enabled cap 01[40] = powerspec 2 supports D0 D1 D2 D3 current D0 cap 05[50] = MSI supports 32 messages, 64 bit cap 10[70] = PCI-Express 1 legacy endpoint max data 128(512) link x1(x8) ecap 0001[100] = AER 1 1 fatal 0 non-fatal 0 corrected PCI-e errors = Fatal Error Detected Unsupported Request Detected Fatal = Unsupported Request Looking at the pciconf output from the older kernel, the unsupported request is there too twa0@pci0:2:0:0:class=0x010400 card=0x100413c1 chip=0x100413c1 rev=0x01 hdr=0x00 vendor = '3ware Inc' device = '9650SE SATA-II RAID PCIe' class = mass storage subclass = RAID bar [10] = type Prefetchable Memory, range 64, base 0x81c00, size 33554432, enabled bar [18] = type Memory, range 64, base 0xe242, size 4096, enabled bar [20] = type I/O Port, range 32, base 0x4000, size 256, enabled cap 01[40] = powerspec 2 supports D0 D1 D2 D3 current D0 cap 05[50] = MSI supports 32 messages, 64 bit cap 10[70] = PCI-Express 1 legacy endpoint max data 128(512) link x1(x8) ecap 0001[100] = AER 1 1 fatal 0 non-fatal 0 corrected PCI-e errors = Fatal Error Detected Unsupported Request Detected Fatal = Unsupported Request I think you can ignore these. I think they happen during POST. -- John Baldwin ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: svn commit: r237318 - in stable/8: share/man/man4 sys/cam sys/cam/scsi sys/conf
On 6/22/2012 3:06 PM, John Baldwin wrote: PCI-e errors = Fatal Error Detected Unsupported Request Detected Fatal = Unsupported Request I think you can ignore these. I think they happen during POST. Thanks! A handy diagnostic tool to have BTW. ---Mike -- --- Mike Tancsa, tel +1 519 651 3400 Sentex Communications, m...@sentex.net Providing Internet services since 1994 www.sentex.net Cambridge, Ontario Canada http://www.tancsa.com/ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
