Date: Mon, 26 Sep 2016 23:53:30 -0600 From: Warner Losh <imp@bsdimp.com> To: "O. Hartmann" <ohartman@zedat.fu-berlin.de> Cc: "freebsd-embedded@freebsd.org" <embedded@freebsd.org> Subject: Re: CURRENT: PCengines APU2C4 SanDisk UltraFit USB 3.0 32G failure: error 19 Message-ID: <CANCZdfrRBrzSkW35Vgvq_%2B-FyOFNxUWY34%2BHfOCGtBH1vbLoFQ@mail.gmail.com> In-Reply-To: <20160926221506.21a6c247.ohartman@zedat.fu-berlin.de> References: <20160917012949.64df9887.ohartman@zedat.fu-berlin.de> <20160926221506.21a6c247.ohartman@zedat.fu-berlin.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Sep 26, 2016 at 2:15 PM, O. Hartmann <ohartman@zedat.fu-berlin.de> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA256 > > Am Sat, 17 Sep 2016 01:29:49 +0200 > "O. Hartmann" <ohartman@zedat.fu-berlin.de> schrieb: > >> Trying to use a SanDisk 32GB UltraFit USB 3.0 Flash drive as boot device with a PCengine >> APU2C4, booting recent CURRENT (r305893) fails with error 19: >> >> [...] >> ugen1.2: <vendor 0x0438> at usbus1 >> uhub2 on uhub1 >> uhub2: <vendor 0x0438 product 0x7900, class 9/0, rev 2.00/0.18, addr 2> on usbus1 >> ugen0.2: <SanDisk> at usbus0 >> umass0 on uhub0 >> umass0: <SanDisk Ultra Fit, class 0/0, rev 2.10/1.00, addr 1> on usbus0 >> umass0: SCSI over Bulk-Only; quirks = 0xc100 >> umass0:2:0: Attached to scbus2 >> uhub2: 4 ports with 4 removable, self powered >> mountroot: waiting for device /dev/ufs/Rs1a... >> Mounting from ufs:/dev/ufs/Rs1a failed with error 19. >> >> The very same NanoBSD image put to SD or USB 2.0 flash drive does boot! >> >> I tried tinyLinux with the same flash drive and it worked. >> >> Are there any hints how to make this flash drive work? >> >> Kind regards, >> >> oh > > Plugging in the USB 3 flash drive, I get this message on the console, maybe it tells > somebody enlightened more than me ...: > > [...] > umass0 on uhub0 > umass0: <SanDisk Ultra Fit, class 0/0, rev 3.00/1.00, addr 1> on usbus0 > umass0: SCSI over Bulk-Only; quirks = 0xc100 > umass0:2:0: Attached to scbus2 > (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 > (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 > da0 at umass-sim0 bus 0 scbus2 target 0 lun 0 > da0: <SanDisk Ultra Fit 1.00> Removable Direct Access SPC-4 SCSI device > da0: Serial Number 4C530001010504121064 > da0: 400.000MB/s transfers > da0: 29327MB (60062500 512 byte sectors) > da0: quirks=0x2<NO_6_BYTE> Wonder what the error is to the INQURY? Is 36 bytes not enough to hold the return? Or is it just becoming ready (though even then it should return some non-error)... Maybe there's a new non-error error return code to test for to eliminate this message :) Warner
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CANCZdfrRBrzSkW35Vgvq_%2B-FyOFNxUWY34%2BHfOCGtBH1vbLoFQ>