Bug 40948 - [umass] [request] USB HP CDW8200 does not work
Summary: [umass] [request] USB HP CDW8200 does not work
Status: Closed Not Enough Information
Alias: None
Product: Base System
Classification: Unclassified
Component: usb (show other bugs)
Version: 5.0-CURRENT
Hardware: Any Any
: Normal Affects Only Me
Assignee: freebsd-usb (Nobody)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-07-24 11:40 UTC by gavin
Modified: 2019-01-09 05:51 UTC (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description gavin 2002-07-24 11:40:02 UTC
	Plugging this drive into my laptop fails to attach with the
following errors: (UMASS_DEBUG on)

umass0: Hewlett Packard HP USB CD-Writer Plus, rev 1.00/0.01, addr 2
umass0: 8070i (ATAPI) over CBI with CCI (using CBI); quirks = 0x0005
umass-sim:0:-1:-1:XPT_PATH_INQ:.
umass0:0:0:-1: Attached to scbus0 as device 0
umass0: Attach finished
scbus0: scanning for umass0:0:0:-1
umass-sim:0:-1:-1:XPT_PATH_INQ:.
umass0:0:0:0:XPT_PATH_INQ:.
umass0:0:0:0:XPT_PATH_INQ:.
umass0:0:0:0:XPT_SCSI_IO: cmd: 0x12, flags: 0x40, 6b cmd/36b data/18b sense
umass0: cmd = 12b (0x120000002400...), data = 36b, dir = in
umass-sim:0:1:0:func_code 0x0004: Invalid target (no wildcard)
umass-sim:0:2:0:func_code 0x0004: Invalid target (no wildcard)
umass0: Handling CBI state 11 (CBI Command), xfer=0xc1878000, TIMEOUT
umass0: failed to send ADSC
umass0: CBI Reset
umass0: Handling CBI state 16 (CBI Reset), xfer=0xc1c31000, TIMEOUT
umass0: CBI reset failed, TIMEOUT
umass0: Clear endpoint 0x82 stall
umass0: Handling CBI state 17 (CBI bulk-in clear stall), xfer=0xc1be7700, NORMAL_COMPLETION
umass0: Clear endpoint 0x03 stall
umass0: Handling CBI state 18 (CBI bulk-out clear stall), xfer=0xc1bd1a00, NORMAL_COMPLETION
umass0:0:0:0:XPT_SCSI_IO: cmd: 0x12, flags: 0x40, 6b cmd/36b data/18b sense
umass0: cmd = 12b (0x120000002400...), data = 36b, dir = in
umass0: Handling CBI state 11 (CBI Command), xfer=0xc1878000, TIMEOUT
umass0: failed to send ADSC
umass0: CBI Reset
umass0: Handling CBI state 16 (CBI Reset), xfer=0xc1c31000, TIMEOUT
umass0: CBI reset failed, TIMEOUT
umass0: Clear endpoint 0x82 stall
umass0: Handling CBI state 17 (CBI bulk-in clear stall), xfer=0xc1be7700, NORMAL_COMPLETION
umass0: Clear endpoint 0x03 stall
umass0: Handling CBI state 18 (CBI bulk-out clear stall), xfer=0xc1bd1a00, NORMAL_COMPLETION
umass0:0:0:0:XPT_SCSI_IO: cmd: 0x12, flags: 0x40, 6b cmd/36b data/18b sense
umass0: cmd = 12b (0x120000002400...), data = 36b, dir = in
umass0: Handling CBI state 11 (CBI Command), xfer=0xc1878000, TIMEOUT
umass0: failed to send ADSC
umass0: CBI Reset
umass0: Handling CBI state 16 (CBI Reset), xfer=0xc1c31000, TIMEOUT
umass0: CBI reset failed, TIMEOUT
umass0: Clear endpoint 0x82 stall
umass0: Handling CBI state 17 (CBI bulk-in clear stall), xfer=0xc1be7700, NORMAL_COMPLETION
umass0: Clear endpoint 0x03 stall
umass0: Handling CBI state 18 (CBI bulk-out clear stall), xfer=0xc1bd1a00, NORMAL_COMPLETION
umass0:0:0:0:XPT_SCSI_IO: cmd: 0x12, flags: 0x40, 6b cmd/36b data/18b sense
umass0: cmd = 12b (0x120000002400...), data = 36b, dir = in
umass0: Handling CBI state 11 (CBI Command), xfer=0xc1878000, TIMEOUT
umass0: failed to send ADSC
umass0: CBI Reset
umass0: Handling CBI state 16 (CBI Reset), xfer=0xc1c31000, TIMEOUT
umass0: CBI reset failed, TIMEOUT
umass0: Clear endpoint 0x82 stall
umass0: Handling CBI state 17 (CBI bulk-in clear stall), xfer=0xc1be7700, NORMAL_COMPLETION
umass0: Clear endpoint 0x03 stall
umass0: Handling CBI state 18 (CBI bulk-out clear stall), xfer=0xc1bd1a00, NORMAL_COMPLETION
umass0:0:0:0:XPT_SCSI_IO: cmd: 0x12, flags: 0x40, 6b cmd/36b data/18b sense
umass0: cmd = 12b (0x120000002400...), data = 36b, dir = in
umass0: Handling CBI state 11 (CBI Command), xfer=0xc1878000, TIMEOUT
umass0: failed to send ADSC
umass0: CBI Reset
umass0: Handling CBI state 16 (CBI Reset), xfer=0xc1c31000, TIMEOUT
umass0: CBI reset failed, TIMEOUT
umass0: Clear endpoint 0x82 stall
umass0: Handling CBI state 17 (CBI bulk-in clear stall), xfer=0xc1be7700, NORMAL_COMPLETION
umass0: Clear endpoint 0x03 stall
umass0: Handling CBI state 18 (CBI bulk-out clear stall), xfer=0xc1bd1a00, NORMAL_COMPLETION
scbus0: Rescan succeeded

Fix: 

unknown

There is already a quirks entry for this drive in umass.c, however my drive
still does not work. Adding other quirks to the list makes no difference,
similarly enabling CBI_I does not help.

The drive itself consists of an IDE drive and a USB-IDE converter card. The
chip on the converter card is a Shuttle Technology USBAT-02 chip. The quirk
for Shuttle chips does not help.
How-To-Repeat: 	Plug a HP CDW-8200 into my laptop
Comment 1 Kris Kennaway freebsd_committer freebsd_triage 2003-07-18 01:35:42 UTC
Responsible Changed
From-To: freebsd-bugs->joe

Assign to USB maintainer
Comment 2 joe freebsd_committer freebsd_triage 2004-11-10 11:04:33 UTC
Responsible Changed
From-To: joe->freebsd-usb

Hand this over to the usb mailling list.
Comment 3 iedowse freebsd_committer freebsd_triage 2005-03-23 01:57:09 UTC
State Changed
From-To: open->feedback


Does this problem still occur with more recent releases?
Comment 4 Mark Linimon freebsd_committer freebsd_triage 2005-07-23 03:46:31 UTC
State Changed
From-To: feedback->closed

Feedback timeout (> 3 months).
Comment 5 Gavin Atkinson 2005-07-23 13:52:55 UTC
Feedback was provided, see 
http://lists.freebsd.org/pipermail/freebsd-usb/2005-April/000986.html

As I simply did a reply-all, it never made it to the PR database.  I've 
manually added bug-folowup to this email.

In short, yes, this is still an issue.

Gavin
Comment 6 Mark Linimon freebsd_committer freebsd_triage 2005-07-23 17:41:35 UTC
State Changed
From-To: closed->open

Closed by mistake (feedback was sent but didn't make it into the 
Audit-Trail).
Comment 7 Eitan Adler freebsd_committer freebsd_triage 2017-12-31 07:58:53 UTC
For bugs matching the following criteria:

Status: In Progress Changed: (is less than) 2014-06-01

Reset to default assignee and clear in-progress tags.

Mail being skipped
Comment 8 Warner Losh freebsd_committer freebsd_triage 2019-01-09 05:51:45 UTC
This bug doesn't really have enough information to be actionable.
There's been a lot of churn in the umass driver since FreeBSD 5.4
I'm closing this bug because it is against a code base that's radically different today. If the problem still somehow persists in FreeBSD 11 or 12, please open a new bug and cc me so we can work through it.