Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 22 Jan 2014 13:57:35 +0100
From:      Hans Petter Selasky <hps@bitfrost.no>
To:        =?ISO-8859-1?Q?Gerrit_K=FChn?= <gerrit.kuehn@aei.mpg.de>,  freebsd-usb@FreeBSD.org
Subject:   Re: ATP USB flash failure (regression?)
Message-ID:  <52DFC03F.6090002@bitfrost.no>
In-Reply-To: <20140122134116.1c589702.gerrit.kuehn@aei.mpg.de>
References:  <20140122134116.1c589702.gerrit.kuehn@aei.mpg.de>

next in thread | previous in thread | raw e-mail | index | archive | help
On 01/22/14 13:41, Gerrit Kühn wrote:
> Hi all,
>
> I have USB-attached flash media by ATP that worked on my FreeBSD 9.2 System not too long ago:
>
> ---
> ugen1.4: <ATP Electronics> at usbus1
> umass0: <ATP Electronics ATP IG eUSB SSD, class 0/0, rev 2.00/11.00, addr 4> on usbus1
> umass0:  SCSI over Bulk-Only; quirks = 0x0100
> umass0:8:0:-1: Attached to scbus8
> da8 at umass-sim0 bus 0 scbus8 target 0 lun 0
> da8: <ATP ATP IG eUSB SSD 1100> Fixed Direct Access SCSI-0 device
> da8: 40.000MB/s transfers
> da8: 1960MB (4014080 512 byte sectors: 255H 63S/T 249C)
> da8: quirks=0x2<NO_6_BYTE>
> ---
>
>
> After pulling in the most recent updates from the 9.2-stable branch, it looks like this does not work anymore:
>
> ---
> ugen1.4: <ATP Electronics> at usbus1
> umass0: <ATP Electronics ATP IG eUSB SSD, class 0/0, rev 2.00/11.00, addr 4> on usbus1
> umass0:  SCSI over Bulk-Only; quirks = 0x4101
> umass0:8:0:-1: Attached to scbus8
> (probe0:umass-sim0:0:0:0): INQUIRY. CDB: 12 00 00 00 24 00
> (probe0:umass-sim0:0:0:0): CAM status: CCB request completed with an error
> (probe0:umass-sim0:0:0:0): Retrying command
> Trying to mount root from ufs:/dev/mirror/root [rw]...
> (probe0:umass-sim0:0:0:0): INQUIRY. CDB: 12 00 00 00 24 00
> (probe0:umass-sim0:0:0:0): CAM status: CCB request completed with an error
> (probe0:umass-sim0:0:0:0): Retrying command
> ZFS filesystem version: 5
> ZFS storage pool version: features support (5000)
> (probe0:umass-sim0:0:0:0): INQUIRY. CDB: 12 00 00 00 24 00
> (probe0:umass-sim0:0:0:0): CAM status: CCB request completed with an error
> (probe0:umass-sim0:0:0:0): Retrying command
> igb0: link state changed to UP
> (probe0:umass-sim0:0:0:0): INQUIRY. CDB: 12 00 00 00 24 00
> (probe0:umass-sim0:0:0:0): CAM status: CCB request completed with an error
> (probe0:umass-sim0:0:0:0): Retrying command
> arp: 10.117.0.1 moved from 00:1a:8c:f0:14:e1 to 00:1a:8c:f0:14:e0 on igb0
> (probe0:umass-sim0:0:0:0): INQUIRY. CDB: 12 00 00 00 24 00
> (probe0:umass-sim0:0:0:0): CAM status: CCB request completed with an error
> (probe0:umass-sim0:0:0:0): Error 5, Retries exhausted
> ---
>
>
> It looks like the quieks have changed and do not work anymore now... Does anybody have an idea how to fix this?

Hi,

It looks like the auto-quirk code for USB mass storage, which was 
activated recently is changing the quirks for your device. The INQUIRY 
command is expected to fail. Does the device work, or are you just 
worried about the warnings in dmesg?

You can get more information by setting:

sysctl hw.usb.usb.debug=15

while plugging your device. Search for "msctest" keyword.

QUIRKS 0x4101 are:

#define NO_SYNCHRONIZE_CACHE    0x4000
#define NO_GETMAXLUN            0x0100
#define NO_TEST_UNIT_READY      0x0001

If you add this quirk, the msctest logic will be disabled:

usbconfig -d X.Y add_quirk NO_SYNCHRONIZE_CACHE

You need to replug the device after adding the quirk.

See also:

sys/dev/usb/quirk/usb_quirk.c

For permanent quirks.

--HPS



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?52DFC03F.6090002>