Re: HEAD memsticks broken? [USB/CAM Problems?]

On 09.02.2013 12:15, Hans Petter Selasky wrote:
> On Saturday 09 February 2013 10:26:59 Joel Dahl wrote:
>> On 09-02-2013  8:32, Joel Dahl wrote:
>>> Hi,
>>>
>>> I suspect something is broken with memsticks built from HEAD. I noticed
>>> that I couldn't boot the latest HEAD (amd64) memstick snapshot on two
>>> machines (Lenovo X220 and HP ProLiant ML350 G5). Trying snapshots from
>>> the FreeBSD.org FTP or allbsd.org makes no difference.
>>
>> I compared output from booting RELENG_9 and HEAD:
>>
>> RELENG_9:
>>
>> ugen2.3: <Kingston> at usbus2
>> umass0: <Kingston DataDtraveler G3, class 0/0, rev 2.00/1.00, addr 3> on
>> usbus2 umass0:  SCSI over Bulk-Only; quirks = 0x0100
>> umass0:4:0:-1: Attached to scbus4
>> da0 at umass-sim0 bus 0 scbus4 target 0 lun 0
>> da0: <Kingston DataTraveler G3 1.00> Removable Direct Access SCSI-2 device
>> ??????????? da0: 40.000MB/s transfers
>> da0: 1905MB (3903264 512 byte sectors: 255H 63S/T 24SC)
>> (da0-umass-sim0:0:0:0): PREVENT ALLOW MEDIUM REMOVAL. CDB: 1e 0 0 0 1 0
>> (da0-umass-sim0:0:0:0): CAM status: SCSI Status Error
>> (da0-umass-sim0:0:0:0): SCSI status: Check Condition
>> (da0-umass-sim0:0:0:0): SCSI sense: No sense data present
>> (da0-umass-sim0:0:0:0): Retrying command (per sense data)
>> <SNIP LOTS OF REDUNDANT OUTPUT>
>> <SNIP LOTS OF REDUNDANT OUTPUT>
>> <SNIP LOTS OF REDUNDANT OUTPUT>
>> Root mount waiting for: usbus2
>> ugen2.4: <Lenovo> at usbus2
>> Trying to mount root from ufs:/dev/ufs/FreeBSD_Install [ro,noatime]...
>> Starting file system checks:
>> /dev/ufs/FreeBSD_Install: FILE SYSTEM CLEAN; SKIPPING CHECKS
>> /dev/ufs/FreeBSD_Install: clean, 43155 free (507 frags, 5331 blocks, 0.1%
>> fragmentation) Mounting local file systems:.
>>
>> and it works.
>>
>> HEAD:
>>
>> ugen2.3: <Kingston> at usbus2
>> umass0: <Kingston DataDtraveler G3, class 0/0, rev 2.00/1.00, addr 3> on
>> usbus2 umass0:  SCSI over Bulk-Only; quirks = 0x0100
>> umass0:5:0:-1: Attached to scbus5
>> da0 at umass-sim0 bus 0 scbus5 target 0 lun 0
>> da0: <Kingston DataTraveler G3 1.00> Removable Direct Access SCSI-0 device
>> ?????????? da0: 40.000MB/s transfers
>> da0: 3690MB (7557704 512 byte sectors: 255H 63S/T 470SC)
>> (da0-umass-sim0:0:0:0): PREVENT ALLOW MEDIUM REMOVAL. CDB: 1e 0 0 0 1 0
>> (da0-umass-sim0:0:0:0): CAM status: SCSI Status Error
>> (da0-umass-sim0:0:0:0): SCSI status: Check Condition
>> (da0-umass-sim0:0:0:0): SCSI sense: No sense data present
>> (da0-umass-sim0:0:0:0): Retrying command (per sense data)
>> <SNIP LOTS OF REDUNDANT OUTPUT>
>> <SNIP LOTS OF REDUNDANT OUTPUT>
>> <SNIP LOTS OF REDUNDANT OUTPUT>
>> (da0-umass-sim0:0:0:0): Error 5, Retries exhausted
>> (da0-umass-sim0:0:0:0): got CAM status 0x8c
>> (da0-umass-sim0:0:0:0): fatal error, failed to attach to device
>> (da0-umass-sim0:0:0:0): lost device - 0 outstanding, 4 refs
>> (da0-umass-sim0:0:0:0): removing device entry
>> ugen2.4: <Lenovo> at usbus2
>> Trying to mount root from ufs:/dev/ufs/FreeBSD_Install [ro,noatime]...
>> mountroot: waiting for device /dev/ufs/FreeBSD_Install ...
>> Mounting from ufs:/dev/ufs/FreeBSD_Install failed with error 19.
> 
> Hi,
> 
> You can try to set the no-synchronize cache quirk in 
> sys/dev/usb/quirk/usb_quirk.c for your device. I'm not sure if it helps, but 
> else I suspect it is not an USB issue.

How long ago that HEAD was built? Could you get full dmesg? I don't
think that "PREVENT ALLOW MEDIUM REMOVAL" should cause device drop. "No
sense data present" also doesn't look right.

-- 
Alexander Motin