Bug 20384

Summary: Phase errors with Zip650 CD on USB
Product: Base System Reporter: boopboopboop <boopboopboop>
Component: kernAssignee: freebsd-bugs (Nobody) <bugs>
Status: Closed FIXED    
Severity: Affects Only Me    
Priority: Normal    
Version: Unspecified   
Hardware: Any   
OS: Any   

Description boopboopboop 2000-08-03 18:20:01 UTC 
With the 3 listed kernels and an Iomega ZipCD 650 USB drive, i get repeated Phase errors. I recompiled with all the debugging for umass and usb turned on, and tracked it to a bogus cmd being sent to the device. it was sending an inquiry (12h) with the correct allocation length (36 bytes) which was succeeding, then sending an inquiry with a bogus allocation length (55 bytes) which caused the phase error. I put a quick hack in umass.c to take all inquiry cmds to the device and remap the allocation length to 36 bytes, which seems to have fixed it. sorry i do not have the time to track down the real source and provide a patch.

Fix: 

I didn't take the time to track down the source of the bogus cmd, i just put a filter in the umass layer before the cmd was sent out so it would be structured properly. FYI the drive seems to behave properly now. I might have backlogs of the debug output, if that would be helpful mail me and i can search for them.
How-To-Repeat: Purchase Zip650 CD drive.
Apply to USB port.
Configure kernel for umass support.
Achieve Nirvana.
Comment 1 Sheldon Hearn freebsd_committer freebsd_triage 2000-08-03 21:01:07 UTC 
Responsible Changed
From-To: freebsd-bugs->n_hibma

Nick's Mr USB.
Comment 2 n_hibma 2000-08-09 21:33:29 UTC 
> I didn't take the time to track down the source of the bogus cmd, i
> just put a filter in the umass layer before the cmd was sent out so
> it would be structured properly. FYI the drive seems to behave
> properly now. I might have backlogs of the debug output, if that
> would be helpful mail me and i can search for them.

Please do. That would be very helpful. Please send them to

	n_hibma@freebsd.org

You stated Inquiry command with data length (36) and (55). Was that last
one supposed to by (255)? It might be that the device does not
understand the long command (something fishy is being done to get the
length that long, I think it is set to 0, so I would appreciate some
help on that one).

Thanks in advance.

Nick
--
Qube Software, Ltd.                                             Private:
n_hibma@qubesoft.com                              n_hibma@webweaving.org
                                                     n_hibma@freebsd.org
http://www.qubesoft.com/                   http://www.etla.net/~n_hibma/
Comment 3 Mark Linimon freebsd_committer freebsd_triage 2004-08-27 23:27:35 UTC 
State Changed
From-To: open->feedback

Is this still a problem with modern versions of FreeBSD?
Comment 4 Mark Linimon freebsd_committer freebsd_triage 2004-08-27 23:27:35 UTC 
Responsible Changed
From-To: n_hibma->freebsd-bugs

With permission of assignee, reset assignment.
Comment 5 Mark Linimon freebsd_committer freebsd_triage 2004-08-27 23:45:25 UTC 
State Changed
From-To: feedback->closed

Submitter's email address bounces.