The following reply was made to PR usb/144915; it has been noted by GNATS.

From: Hans Petter Selasky <hsela...@c2i.net>
To: freebsd-usb@freebsd.org
Cc: Monty Hall <kungfu_disci...@sbcglobal.net>,
 freebsd-gnats-sub...@freebsd.org
Subject: Re: usb/144915: Prolific USB-IDE Bridge for Seagate ST350083
Date: Sun, 21 Mar 2010 11:27:48 +0100

 On Saturday 20 March 2010 19:56:35 Monty Hall wrote:
 > >Number:         144915
 > >Category:       usb
 > >Synopsis:       Prolific USB-IDE Bridge for Seagate ST350083
 > >Confidential:   no
 > >Severity:       non-critical
 > >Priority:       low
 > >Responsible:    freebsd-usb
 > >State:          open
 > >Quarter:
 > >Keywords:
 > >Date-Required:
 > >Class:          sw-bug
 > >Submitter-Id:   current-users
 > >Arrival-Date:   Sat Mar 20 19:00:16 UTC 2010
 > >Closed-Date:
 > >Last-Modified:
 > >Originator:     Monty Hall
 > >Release:        8.0
 > >Organization:
 > >Environment:
 > 
 > FreeBSD XXXXX 8.0-STABLE FreeBSD 8.0-STABLE #8 r205349M: Sat Mar 20
 >  00:02:49 EDT 2010     r...@xxxx:/usr/obj/usr/src/sys/INSPIRON  i386
 > 
 > >Description:
 > 
 > I started getting zpool corruption errors, and the console was displaying
 >  error messages concerning CACHE problems and SCSI error (20,0). 
 >  Unfortunately I recompiled for this quirk and no longer have the actual
 >  error message:
 > 
 > camcontrol devlist:
 > <ST350083 0A 3.AA>                 at scbus2 target 0 lun 0 (da0,pass1)
 > 
 > usbcontrol list:
 > ---------------
 > ugen4.5: <Mass Storage Device Prolific Technology Inc.> at usbus4, cfg=0
 >  md=HOST spd=HIGH (480Mbps) pwr=ON
 > 
 > >How-To-Repeat:
 > 
 > I never had this problem as a UFS drive.  Only started getting this message
 >  after adding to a zpool.
 > 
 > >Fix:
 > 
 > Recompile w/ the following changes:
 > 
 > /usr/src/sys/dev/usb/quirk/usb_quirk.c
 > Index: usb_quirk.c
 > ===================================================================
 > --- usb_quirk.c (revision 205388)
 > +++ usb_quirk.c (working copy)
 > @@ -80,6 +80,10 @@
 >    USB_QUIRK_VP(USB_VENDOR_##v, USB_PRODUCT_##v##_##p, l, h, __VA_ARGS__)
 > 
 >  static struct usb_quirk_entry usb_quirks[USB_DEV_QUIRKS_MAX] = {
 > +       USB_QUIRK(PROLIFIC, PL2506, 0x0000, 0xffff,
 > +               UQ_MSC_FORCE_PROTO_SCSI,
 > +               UQ_MSC_FORCE_WIRE_BBB,
 > +               UQ_MSC_NO_SYNC_CACHE),
 >         USB_QUIRK(ASUS, LCM, 0x0000, 0xffff, UQ_HID_IGNORE),
 >         USB_QUIRK(INSIDEOUT, EDGEPORT4, 0x094, 0x094, UQ_SWAP_UNICODE),
 >         USB_QUIRK(DALLAS, J6502, 0x0a2, 0x0a2, UQ_BAD_ADC),
 > 
 > --------------------------------------------
 > 
 
 Hi,
 
 Thanks for your patch!
 
 Can you try the patch without the UQ_MSC_FORCE options, only the 
 UQ_MSC_NO_SYNC_CACHE? We try to avoid the UQ_MSC_FORCE options when the USB 
 descriptors already have the correct values for these fields.
 
 Does the patch still work?
 
 --HPS
 
 > /usr/src/sys/dev/usb/usbdevs
 > Index: usbdevs
 > ===================================================================
 > --- usbdevs     (revision 205388)
 > +++ usbdevs     (working copy)
 > @@ -2223,6 +2223,7 @@
 >  product PROLIFIC PL2305                0x2305  Parallel printer
 >  product PROLIFIC ATAPI4                0x2307  ATAPI-4 Controller
 >  product PROLIFIC PL2501                0x2501  PL2501 Host-Host interface
 > +product PROLIFIC PL2506                0x2506  PL2506 USB to IDE Bridge
 >  product PROLIFIC PHAROS                0xaaa0  Prolific Pharos
 >  product PROLIFIC RSAQ3         0xaaa2  PL2303 Serial Adapter (IODATA
 >  USB-RSAQ3) product PROLIFIC2 WSIM         0x2001  Willcom WSIM
 > 
 > >Release-Note:
 > >Audit-Trail:
 > >Unformatted:
 > 
 > _______________________________________________
 > 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"
 > 
_______________________________________________
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"

Reply via email to