Re: usb/149934: Transcend JetFlash V85 poor performance
I think this one is MFC'ed into RELENG_8 long time ago. Can we close the PR? -- Sphinx of black quartz judge my vow. ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"
Re: usb/149934: Transcend JetFlash V85 poor performance
The following reply was made to PR usb/149934; it has been noted by GNATS. From: Volodymyr Kostyrko To: bug-follo...@freebsd.org, freebsd-usb@FreeBSD.org Cc: Subject: Re: usb/149934: Transcend JetFlash V85 poor performance Date: Fri, 30 Dec 2011 15:50:06 +0200 I think this one is MFC'ed into RELENG_8 long time ago. Can we close the PR? -- Sphinx of black quartz judge my vow. ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"
Re: usb/149934: Transcend JetFlash V85 poor performance
The following reply was made to PR usb/149934; it has been noted by GNATS. From: Hans Petter Selasky To: Volodymyr Kostyrko Cc: freebsd-usb@freebsd.org, freebsd-gnats-sub...@freebsd.org Subject: Re: usb/149934: Transcend JetFlash V85 poor performance Date: Wed, 25 Aug 2010 09:22:58 +0200 On Tuesday 24 August 2010 23:43:05 Volodymyr Kostyrko wrote: > 25.08.2010 00:27, Hans Petter Selasky wrote: > > I've committed my updated patch to USB P4. See change #182862. > > > > Please verify that your drive is still working with the new patch. > > Yes, i've tested my drive exactly with this patch. > > Say, how about UQ_MSC_NO_TEST_UNIT_READY? You have omitted it on purpose > so maybe this one should be added only if without one the device would > not work at all? Sorry I overlooked that, See USB P4 change #182875. --HPS ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"
Re: usb/149934: Transcend JetFlash V85 poor performance
On Tuesday 24 August 2010 23:43:05 Volodymyr Kostyrko wrote: > 25.08.2010 00:27, Hans Petter Selasky wrote: > > I've committed my updated patch to USB P4. See change #182862. > > > > Please verify that your drive is still working with the new patch. > > Yes, i've tested my drive exactly with this patch. > > Say, how about UQ_MSC_NO_TEST_UNIT_READY? You have omitted it on purpose > so maybe this one should be added only if without one the device would > not work at all? Sorry I overlooked that, See USB P4 change #182875. --HPS ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"
Re: usb/149934: Transcend JetFlash V85 poor performance
The following reply was made to PR usb/149934; it has been noted by GNATS. From: Volodymyr Kostyrko To: Hans Petter Selasky Cc: freebsd-usb@freebsd.org, freebsd-gnats-sub...@freebsd.org Subject: Re: usb/149934: Transcend JetFlash V85 poor performance Date: Wed, 25 Aug 2010 00:17:25 +0300 24.08.2010 18:11, Hans Petter Selasky wrote: > Can you test this patch instead: > > --- sys/dev/usb/quirk/usb_quirk.c 2010-08-10 16:03:19.0 > +++ sys/dev/usb/quirk/usb_quirk.c 2010-08-10 16:03:19.0 > @@ -160,10 +160,8 @@ > USB_QUIRK(ALCOR, AU6390, 0x, 0x, UQ_MSC_NO_SYNC_CACHE), > USB_QUIRK(ALCOR, UMCR_9361, 0x, 0x, UQ_MSC_FORCE_WIRE_BBB, > UQ_MSC_FORCE_PROTO_SCSI, UQ_MSC_NO_GETMAXLUN), > - USB_QUIRK(ALCOR, TRANSCEND, 0x0142, 0x0142, UQ_MSC_FORCE_WIRE_BBB, > - UQ_MSC_FORCE_PROTO_SCSI, UQ_MSC_NO_GETMAXLUN, > UQ_MSC_NO_SYNC_CACHE), > - USB_QUIRK(ALCOR, TRANSCEND, 0x, 0x, UQ_MSC_FORCE_WIRE_BBB, > - UQ_MSC_FORCE_PROTO_SCSI, UQ_MSC_NO_GETMAXLUN), > + USB_QUIRK(ALCOR, TRANSCEND, 0x, 0x, UQ_MSC_NO_GETMAXLUN, > + UQ_MSC_NO_SYNC_CACHE), > USB_QUIRK(APACER, HT202, 0x, 0x, UQ_MSC_NO_TEST_UNIT_READY, > UQ_MSC_NO_SYNC_CACHE), > USB_QUIRK(ASAHIOPTICAL, OPTIO230, 0x, 0x, > UQ_MSC_FORCE_WIRE_BBB, > > Please also dump device and configuration descriptor using usbconfig. > > --HPS This one results in: Aug 25 00:10:17 limbo root: Unknown USB device: vendor 0x058f product 0x6387 bus uhub3 Aug 25 00:10:17 limbo kernel: ugen3.3: at usbus3 Aug 25 00:10:17 limbo kernel: umass1: on usbus3 Aug 25 00:10:17 limbo kernel: umass1: SCSI over Bulk-Only; quirks = 0x4100 Aug 25 00:10:18 limbo kernel: umass1:2:1:-1: Attached to scbus2 Aug 25 00:10:18 limbo kernel: (probe0:umass-sim1:1:0:0): TEST UNIT READY. CDB: 0 0 0 0 0 0 Aug 25 00:10:18 limbo kernel: (probe0:umass-sim1:1:0:0): CAM status: SCSI Status Error Aug 25 00:10:18 limbo kernel: (probe0:umass-sim1:1:0:0): SCSI status: Check Condition Aug 25 00:10:18 limbo kernel: (probe0:umass-sim1:1:0:0): SCSI sense: UNIT ATTENTION asc:28,0 (Not ready to ready change, medium may have changed) Aug 25 00:10:18 limbo kernel: da4 at umass-sim1 bus 1 scbus2 target 0 lun 0 Aug 25 00:10:18 limbo kernel: da4: Removable Direct Access SCSI-2 device Aug 25 00:10:18 limbo kernel: da4: 40.000MB/s transfers Aug 25 00:10:18 limbo kernel: da4: 3900MB (7987200 512 byte sectors: 255H 63S/T 497C) So how about UQ_MSC_NO_TEST_UNIT_READY? # usbconfig -d 3.3 dump_device_desc ugen3.3: at usbus3, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON bLength = 0x0012 bDescriptorType = 0x0001 bcdUSB = 0x0200 bDeviceClass = 0x bDeviceSubClass = 0x bDeviceProtocol = 0x bMaxPacketSize0 = 0x0040 idVendor = 0x058f idProduct = 0x6387 bcdDevice = 0x0100 iManufacturer = 0x0001 iProduct = 0x0002 iSerialNumber = 0x0003 bNumConfigurations = 0x0001 # usbconfig -d 3.3 dump_all_config_desc ugen3.3: at usbus3, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON Configuration index 0 bLength = 0x0009 bDescriptorType = 0x0002 wTotalLength = 0x0020 bNumInterfaces = 0x0001 bConfigurationValue = 0x0001 iConfiguration = 0x bmAttributes = 0x0080 bMaxPower = 0x0032 Interface 0 bLength = 0x0009 bDescriptorType = 0x0004 bInterfaceNumber = 0x bAlternateSetting = 0x bNumEndpoints = 0x0002 bInterfaceClass = 0x0008 bInterfaceSubClass = 0x0006 bInterfaceProtocol = 0x0050 iInterface = 0x Endpoint 0 bLength = 0x0007 bDescriptorType = 0x0005 bEndpointAddress = 0x0001 bmAttributes = 0x0002 wMaxPacketSize = 0x0200 bInterval = 0x bRefresh = 0x bSynchAddress = 0x Endpoint 1 bLength = 0x0007 bDescriptorType = 0x0005 bEndpointAddress = 0x0082 bmAttributes = 0x0002 wMaxPacketSize = 0x0200 bInterval = 0x bRefresh = 0x bSynchAddress = 0x -- Sphinx of black quartz judge my vow. ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"
Re: usb/149934: Transcend JetFlash V85 poor performance
The following reply was made to PR usb/149934; it has been noted by GNATS. From: Volodymyr Kostyrko To: Hans Petter Selasky Cc: freebsd-usb@freebsd.org, freebsd-gnats-sub...@freebsd.org Subject: Re: usb/149934: Transcend JetFlash V85 poor performance Date: Wed, 25 Aug 2010 00:43:05 +0300 25.08.2010 00:27, Hans Petter Selasky wrote: > I've committed my updated patch to USB P4. See change #182862. > > Please verify that your drive is still working with the new patch. Yes, i've tested my drive exactly with this patch. Say, how about UQ_MSC_NO_TEST_UNIT_READY? You have omitted it on purpose so maybe this one should be added only if without one the device would not work at all? -- Sphinx of black quartz judge my vow. ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"
Re: usb/149934: Transcend JetFlash V85 poor performance
25.08.2010 00:27, Hans Petter Selasky wrote: I've committed my updated patch to USB P4. See change #182862. Please verify that your drive is still working with the new patch. Yes, i've tested my drive exactly with this patch. Say, how about UQ_MSC_NO_TEST_UNIT_READY? You have omitted it on purpose so maybe this one should be added only if without one the device would not work at all? -- Sphinx of black quartz judge my vow. ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"
Re: usb/149934: Transcend JetFlash V85 poor performance
The following reply was made to PR usb/149934; it has been noted by GNATS. From: Hans Petter Selasky To: freebsd-usb@freebsd.org Cc: Volodymyr Kostyrko , freebsd-gnats-sub...@freebsd.org Subject: Re: usb/149934: Transcend JetFlash V85 poor performance Date: Tue, 24 Aug 2010 23:27:59 +0200 Hi, I've committed my updated patch to USB P4. See change #182862. Please verify that your drive is still working with the new patch. --HPS ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"
Re: usb/149934: Transcend JetFlash V85 poor performance
Hi, I've committed my updated patch to USB P4. See change #182862. Please verify that your drive is still working with the new patch. --HPS ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"
Re: usb/149934: Transcend JetFlash V85 poor performance
24.08.2010 18:11, Hans Petter Selasky wrote: Can you test this patch instead: --- sys/dev/usb/quirk/usb_quirk.c 2010-08-10 16:03:19.0 +++ sys/dev/usb/quirk/usb_quirk.c 2010-08-10 16:03:19.0 @@ -160,10 +160,8 @@ USB_QUIRK(ALCOR, AU6390, 0x, 0x, UQ_MSC_NO_SYNC_CACHE), USB_QUIRK(ALCOR, UMCR_9361, 0x, 0x, UQ_MSC_FORCE_WIRE_BBB, UQ_MSC_FORCE_PROTO_SCSI, UQ_MSC_NO_GETMAXLUN), - USB_QUIRK(ALCOR, TRANSCEND, 0x0142, 0x0142, UQ_MSC_FORCE_WIRE_BBB, - UQ_MSC_FORCE_PROTO_SCSI, UQ_MSC_NO_GETMAXLUN, UQ_MSC_NO_SYNC_CACHE), - USB_QUIRK(ALCOR, TRANSCEND, 0x, 0x, UQ_MSC_FORCE_WIRE_BBB, - UQ_MSC_FORCE_PROTO_SCSI, UQ_MSC_NO_GETMAXLUN), + USB_QUIRK(ALCOR, TRANSCEND, 0x, 0x, UQ_MSC_NO_GETMAXLUN, + UQ_MSC_NO_SYNC_CACHE), USB_QUIRK(APACER, HT202, 0x, 0x, UQ_MSC_NO_TEST_UNIT_READY, UQ_MSC_NO_SYNC_CACHE), USB_QUIRK(ASAHIOPTICAL, OPTIO230, 0x, 0x, UQ_MSC_FORCE_WIRE_BBB, Please also dump device and configuration descriptor using usbconfig. --HPS This one results in: Aug 25 00:10:17 limbo root: Unknown USB device: vendor 0x058f product 0x6387 bus uhub3 Aug 25 00:10:17 limbo kernel: ugen3.3: at usbus3 Aug 25 00:10:17 limbo kernel: umass1: class 0/0, rev 2.00/1.00, addr 3> on usbus3 Aug 25 00:10:17 limbo kernel: umass1: SCSI over Bulk-Only; quirks = 0x4100 Aug 25 00:10:18 limbo kernel: umass1:2:1:-1: Attached to scbus2 Aug 25 00:10:18 limbo kernel: (probe0:umass-sim1:1:0:0): TEST UNIT READY. CDB: 0 0 0 0 0 0 Aug 25 00:10:18 limbo kernel: (probe0:umass-sim1:1:0:0): CAM status: SCSI Status Error Aug 25 00:10:18 limbo kernel: (probe0:umass-sim1:1:0:0): SCSI status: Check Condition Aug 25 00:10:18 limbo kernel: (probe0:umass-sim1:1:0:0): SCSI sense: UNIT ATTENTION asc:28,0 (Not ready to ready change, medium may have changed) Aug 25 00:10:18 limbo kernel: da4 at umass-sim1 bus 1 scbus2 target 0 lun 0 Aug 25 00:10:18 limbo kernel: da4: Removable Direct Access SCSI-2 device Aug 25 00:10:18 limbo kernel: da4: 40.000MB/s transfers Aug 25 00:10:18 limbo kernel: da4: 3900MB (7987200 512 byte sectors: 255H 63S/T 497C) So how about UQ_MSC_NO_TEST_UNIT_READY? # usbconfig -d 3.3 dump_device_desc ugen3.3: at usbus3, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON bLength = 0x0012 bDescriptorType = 0x0001 bcdUSB = 0x0200 bDeviceClass = 0x bDeviceSubClass = 0x bDeviceProtocol = 0x bMaxPacketSize0 = 0x0040 idVendor = 0x058f idProduct = 0x6387 bcdDevice = 0x0100 iManufacturer = 0x0001 iProduct = 0x0002 iSerialNumber = 0x0003 bNumConfigurations = 0x0001 # usbconfig -d 3.3 dump_all_config_desc ugen3.3: at usbus3, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON Configuration index 0 bLength = 0x0009 bDescriptorType = 0x0002 wTotalLength = 0x0020 bNumInterfaces = 0x0001 bConfigurationValue = 0x0001 iConfiguration = 0x bmAttributes = 0x0080 bMaxPower = 0x0032 Interface 0 bLength = 0x0009 bDescriptorType = 0x0004 bInterfaceNumber = 0x bAlternateSetting = 0x bNumEndpoints = 0x0002 bInterfaceClass = 0x0008 bInterfaceSubClass = 0x0006 bInterfaceProtocol = 0x0050 iInterface = 0x Endpoint 0 bLength = 0x0007 bDescriptorType = 0x0005 bEndpointAddress = 0x0001 bmAttributes = 0x0002 wMaxPacketSize = 0x0200 bInterval = 0x bRefresh = 0x bSynchAddress = 0x Endpoint 1 bLength = 0x0007 bDescriptorType = 0x0005 bEndpointAddress = 0x0082 bmAttributes = 0x0002 wMaxPacketSize = 0x0200 bInterval = 0x bRefresh = 0x bSynchAddress = 0x -- Sphinx of black quartz judge my vow. ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"
Re: usb/149934: Transcend JetFlash V85 poor performance
The following reply was made to PR usb/149934; it has been noted by GNATS. From: Hans Petter Selasky To: freebsd-usb@freebsd.org Cc: Volodymyr Kostyrko , freebsd-gnats-sub...@freebsd.org Subject: Re: usb/149934: Transcend JetFlash V85 poor performance Date: Tue, 24 Aug 2010 17:11:59 +0200 On Tuesday 24 August 2010 13:39:30 Volodymyr Kostyrko wrote: > >Number: 149934 > >Category: usb > >Synopsis: Transcend JetFlash V85 poor performance > >Confidential: no > >Severity: non-critical > >Priority: low > >Responsible:freebsd-usb > >State: open > >Quarter: > >Keywords: > >Date-Required: > >Class: change-request > >Submitter-Id: current-users > >Arrival-Date: Tue Aug 24 11:40:02 UTC 2010 > >Closed-Date: > >Last-Modified: > >Originator: Volodymyr Kostyrko > >Release:RELENG_8 > >Organization: > > >Environment: > FreeBSD limbo.lan 8.1-STABLE FreeBSD 8.1-STABLE #0 r211717M: Tue Aug 24 > 12:56:24 EEST 2010 arc...@limbo.lan:/usr/obj/usr/src/sys/MINIMAL_8 > i386 > > >Description: > When attaching device kernel reports this: > > Aug 21 22:46:15 limbo root: Unknown USB device: vendor 0x058f product > 0x6387 bus uhub3 Aug 21 22:46:15 limbo kernel: umass1: Storage Device, class 0/0, rev 2.00/1.00, addr 3> on usbus3 Aug 21 > 22:46:15 limbo kernel: umass1: SCSI over Bulk-Only; quirks = 0x0100 Aug > 21 22:46:16 limbo kernel: umass1:2:1:-1: Attached to scbus2 > Aug 21 22:46:16 limbo kernel: (probe0:umass-sim1:1:0:0): TEST UNIT READY. > CDB: 0 0 0 0 0 0 Aug 21 22:46:16 limbo kernel: (probe0:umass-sim1:1:0:0): > CAM status: SCSI Status Error Aug 21 22:46:16 limbo kernel: > (probe0:umass-sim1:1:0:0): SCSI status: Check Condition Aug 21 22:46:16 > limbo kernel: (probe0:umass-sim1:1:0:0): SCSI sense: UNIT ATTENTION > asc:28,0 (Not ready to ready change, medium may have changed) Aug 21 > 22:46:16 limbo kernel: da4 at umass-sim1 bus 1 scbus2 target 0 lun 0 Aug > 21 22:46:16 limbo kernel: da4: Removable Direct > Access SCSI-2 device Aug 21 22:46:16 limbo kernel: da4: 40.000MB/s > transfers > Aug 21 22:46:16 limbo kernel: da4: 3900MB (7987200 512 byte sectors: 255H > 63S/T 497C) Aug 21 22:46:24 limbo kernel: (da4:umass-sim1:1:0:0): > SYNCHRONIZE CACHE(10). CDB: 35 0 0 0 0 0 0 0 0 0 Aug 21 22:46:24 limbo > kernel: (da4:umass-sim1:1:0:0): CAM status: SCSI Status Error Aug 21 > 22:46:24 limbo kernel: (da4:umass-sim1:1:0:0): SCSI status: Check > Condition Aug 21 22:46:24 limbo kernel: (da4:umass-sim1:1:0:0): SCSI > sense: ILLEGAL REQUEST asc:26,0 (Invalid field in parameter list) > > After that any time SYNCHRONIZE CACHE command is issued writing to device > stops for some time and kernel reports bad command. > > >How-To-Repeat: > Attaching the device and trying to work with it should suffice. > > >Fix: > Apply the following patch. > > Patch attached with submission follows: > > Index: sys/dev/usb/quirk/usb_quirk.c > === > --- sys/dev/usb/quirk/usb_quirk.c(revision 211717) > +++ sys/dev/usb/quirk/usb_quirk.c(working copy) > @@ -159,6 +159,9 @@ > USB_QUIRK(ALCOR, AU6390, 0x, 0x, UQ_MSC_NO_SYNC_CACHE), > USB_QUIRK(ALCOR, UMCR_9361, 0x, 0x, UQ_MSC_FORCE_WIRE_BBB, > UQ_MSC_FORCE_PROTO_SCSI, UQ_MSC_NO_GETMAXLUN), > +USB_QUIRK(ALCOR, TRANSCEND, 0x0100, 0x0100, UQ_MSC_FORCE_WIRE_BBB, > +UQ_MSC_FORCE_PROTO_SCSI, UQ_MSC_NO_GETMAXLUN, UQ_MSC_NO_SYNC_CACHE, > +UQ_MSC_NO_TEST_UNIT_READY), > USB_QUIRK(ALCOR, TRANSCEND, 0x0142, 0x0142, UQ_MSC_FORCE_WIRE_BBB, > UQ_MSC_FORCE_PROTO_SCSI, UQ_MSC_NO_GETMAXLUN, UQ_MSC_NO_SYNC_CACHE), > USB_QUIRK(ALCOR, TRANSCEND, 0x, 0x, UQ_MSC_FORCE_WIRE_BBB, > > >Release-Note: > >Audit-Trail: > > >Unformatted: Can you test this patch instead: --- sys/dev/usb/quirk/usb_quirk.c 2010-08-10 16:03:19.0 +++ sys/dev/usb/quirk/usb_quirk.c 2010-08-10 16:03:19.0 @@ -160,10 +160,8 @@ USB_QUIRK(ALCOR, AU6390, 0x, 0x, UQ_MSC_NO_SYNC_CACHE), USB_QUIRK(ALCOR, UMCR_9361, 0x, 0x, UQ_MSC_FORCE_WIRE_BBB, UQ_MSC_FORCE_PROTO_SCSI, UQ_MSC_NO_GETMAXLUN), - USB_QUIRK(ALCOR, TRANSCEND, 0x0142, 0x0142, UQ_MSC_FORCE_WIRE_BBB, - UQ_MSC_FORCE_PROTO_SCSI, UQ_MSC_NO_GETMAXLUN, UQ_MSC_NO_SYNC_CACHE), - USB_QUIRK(ALCOR, TRANSCEND, 0x, 0x, UQ_MSC_FORCE_WIRE_BBB, - UQ_MSC_FORCE_PROTO_SCSI, UQ_MSC_NO_GETMAXLUN), + USB_QUIRK(ALCOR, TRANSCEND, 0x, 0x, UQ_MSC_NO_GETM
Re: usb/149934: Transcend JetFlash V85 poor performance
On Tuesday 24 August 2010 13:39:30 Volodymyr Kostyrko wrote: > >Number: 149934 > >Category: usb > >Synopsis: Transcend JetFlash V85 poor performance > >Confidential: no > >Severity: non-critical > >Priority: low > >Responsible:freebsd-usb > >State: open > >Quarter: > >Keywords: > >Date-Required: > >Class: change-request > >Submitter-Id: current-users > >Arrival-Date: Tue Aug 24 11:40:02 UTC 2010 > >Closed-Date: > >Last-Modified: > >Originator: Volodymyr Kostyrko > >Release:RELENG_8 > >Organization: > > >Environment: > FreeBSD limbo.lan 8.1-STABLE FreeBSD 8.1-STABLE #0 r211717M: Tue Aug 24 > 12:56:24 EEST 2010 arc...@limbo.lan:/usr/obj/usr/src/sys/MINIMAL_8 > i386 > > >Description: > When attaching device kernel reports this: > > Aug 21 22:46:15 limbo root: Unknown USB device: vendor 0x058f product > 0x6387 bus uhub3 Aug 21 22:46:15 limbo kernel: umass1: Storage Device, class 0/0, rev 2.00/1.00, addr 3> on usbus3 Aug 21 > 22:46:15 limbo kernel: umass1: SCSI over Bulk-Only; quirks = 0x0100 Aug > 21 22:46:16 limbo kernel: umass1:2:1:-1: Attached to scbus2 > Aug 21 22:46:16 limbo kernel: (probe0:umass-sim1:1:0:0): TEST UNIT READY. > CDB: 0 0 0 0 0 0 Aug 21 22:46:16 limbo kernel: (probe0:umass-sim1:1:0:0): > CAM status: SCSI Status Error Aug 21 22:46:16 limbo kernel: > (probe0:umass-sim1:1:0:0): SCSI status: Check Condition Aug 21 22:46:16 > limbo kernel: (probe0:umass-sim1:1:0:0): SCSI sense: UNIT ATTENTION > asc:28,0 (Not ready to ready change, medium may have changed) Aug 21 > 22:46:16 limbo kernel: da4 at umass-sim1 bus 1 scbus2 target 0 lun 0 Aug > 21 22:46:16 limbo kernel: da4: Removable Direct > Access SCSI-2 device Aug 21 22:46:16 limbo kernel: da4: 40.000MB/s > transfers > Aug 21 22:46:16 limbo kernel: da4: 3900MB (7987200 512 byte sectors: 255H > 63S/T 497C) Aug 21 22:46:24 limbo kernel: (da4:umass-sim1:1:0:0): > SYNCHRONIZE CACHE(10). CDB: 35 0 0 0 0 0 0 0 0 0 Aug 21 22:46:24 limbo > kernel: (da4:umass-sim1:1:0:0): CAM status: SCSI Status Error Aug 21 > 22:46:24 limbo kernel: (da4:umass-sim1:1:0:0): SCSI status: Check > Condition Aug 21 22:46:24 limbo kernel: (da4:umass-sim1:1:0:0): SCSI > sense: ILLEGAL REQUEST asc:26,0 (Invalid field in parameter list) > > After that any time SYNCHRONIZE CACHE command is issued writing to device > stops for some time and kernel reports bad command. > > >How-To-Repeat: > Attaching the device and trying to work with it should suffice. > > >Fix: > Apply the following patch. > > Patch attached with submission follows: > > Index: sys/dev/usb/quirk/usb_quirk.c > === > --- sys/dev/usb/quirk/usb_quirk.c (revision 211717) > +++ sys/dev/usb/quirk/usb_quirk.c (working copy) > @@ -159,6 +159,9 @@ > USB_QUIRK(ALCOR, AU6390, 0x, 0x, UQ_MSC_NO_SYNC_CACHE), > USB_QUIRK(ALCOR, UMCR_9361, 0x, 0x, UQ_MSC_FORCE_WIRE_BBB, > UQ_MSC_FORCE_PROTO_SCSI, UQ_MSC_NO_GETMAXLUN), > + USB_QUIRK(ALCOR, TRANSCEND, 0x0100, 0x0100, UQ_MSC_FORCE_WIRE_BBB, > + UQ_MSC_FORCE_PROTO_SCSI, UQ_MSC_NO_GETMAXLUN, UQ_MSC_NO_SYNC_CACHE, > + UQ_MSC_NO_TEST_UNIT_READY), > USB_QUIRK(ALCOR, TRANSCEND, 0x0142, 0x0142, UQ_MSC_FORCE_WIRE_BBB, > UQ_MSC_FORCE_PROTO_SCSI, UQ_MSC_NO_GETMAXLUN, UQ_MSC_NO_SYNC_CACHE), > USB_QUIRK(ALCOR, TRANSCEND, 0x, 0x, UQ_MSC_FORCE_WIRE_BBB, > > >Release-Note: > >Audit-Trail: > > >Unformatted: Can you test this patch instead: --- sys/dev/usb/quirk/usb_quirk.c 2010-08-10 16:03:19.0 +++ sys/dev/usb/quirk/usb_quirk.c 2010-08-10 16:03:19.0 @@ -160,10 +160,8 @@ USB_QUIRK(ALCOR, AU6390, 0x, 0x, UQ_MSC_NO_SYNC_CACHE), USB_QUIRK(ALCOR, UMCR_9361, 0x, 0x, UQ_MSC_FORCE_WIRE_BBB, UQ_MSC_FORCE_PROTO_SCSI, UQ_MSC_NO_GETMAXLUN), - USB_QUIRK(ALCOR, TRANSCEND, 0x0142, 0x0142, UQ_MSC_FORCE_WIRE_BBB, - UQ_MSC_FORCE_PROTO_SCSI, UQ_MSC_NO_GETMAXLUN, UQ_MSC_NO_SYNC_CACHE), - USB_QUIRK(ALCOR, TRANSCEND, 0x, 0x, UQ_MSC_FORCE_WIRE_BBB, - UQ_MSC_FORCE_PROTO_SCSI, UQ_MSC_NO_GETMAXLUN), + USB_QUIRK(ALCOR, TRANSCEND, 0x, 0x, UQ_MSC_NO_GETMAXLUN, + UQ_MSC_NO_SYNC_CACHE), USB_QUIRK(APACER, HT202, 0x, 0x, UQ_MSC_NO_TEST_UNIT_READY, UQ_MSC_NO_SYNC_CACHE), USB_QUIRK(ASAHIOPTICAL, OPTIO230, 0x, 0x, UQ_MSC_FORCE_WIRE_BBB, Please also dump device and configuration descriptor using usbconfig. --HPS ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"
