From nobody Sat Apr 5 07:09:43 2025 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4ZV66x4vYYz5rQMG for ; Sat, 05 Apr 2025 07:10:01 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-pg1-x536.google.com (mail-pg1-x536.google.com [IPv6:2607:f8b0:4864:20::536]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "WR4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4ZV66x34mxz400k for ; Sat, 05 Apr 2025 07:09:56 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-pg1-x536.google.com with SMTP id 41be03b00d2f7-af589091049so1839372a12.1 for ; Sat, 05 Apr 2025 00:09:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20230601.gappssmtp.com; s=20230601; t=1743836995; x=1744441795; darn=freebsd.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=wRwnyFYJBl6DmzLn6palRYhnzT37QDL84wTOTasaujQ=; b=d92jcR043gJQ9MoVZlrVVVa89TwdujbXEH/eEw2tZd4E1nLr+C1xcOqN3MV3JRP+FM OzA78BVYfA/Te+E8bBaF4egVppEzOKw8Zhx/vrHRPENlAPEP80IawArHkl5DhykOv1F3 EeRZvgCXfDgZuCtCCt1lNKPauNRUNCa0OByNwKRMUtb9/e+Br/EK4qYjPKXQvFcqyng8 I1/V3t0eO1G2ZU6Ut51z1sltq5jHwr/CNYBB10y91BrNP11qk7KKlpvDrM+BXsbMKhGi sK9qHAe7jqow3u/To/xgSBo6gpm3N3dBJguSnpuDn/bAYKkxX38tXWE1W5EZCrO1ae7X bMMw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1743836995; x=1744441795; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=wRwnyFYJBl6DmzLn6palRYhnzT37QDL84wTOTasaujQ=; b=JFsVXGrh2/6gwnTOSUJYYh4Ild6h/eBF+8SM5MldLanGQJFItPwy2ti0uiJ7bunKEH hAks+6XIWoT0ute2EB8tSMosPzi3OcokdGkPOQza2CeOAFTk0d6KlY6nPV/NoXMpA8o5 oA7Z27WeWs49ZY8IR25LiJBMkxVCgOnos5XvrOAhmIsKsvrGdGVh49UsK0a4uEW2ecat oKOJdiCLxc5kWR6O2XYTFvu4y5sq18hXdLQDu4qCqvFvfPIShfQsRrXb/1xgOR5oWiOs LxZ9sggNXOJOQ/MdAOvRBwxrFFewNqAP/VOuscbeloA9tLYHxN8sDnlYaLRmjepYI2Ns wFVA== X-Forwarded-Encrypted: i=1; AJvYcCWqqtKii28qtEEDzsm0vbeQXxB3SrbyBzLkmUEmCzxOp0rVl3dseYglND7DXiq4Mi7+qNAVcZwt4t/kmiMd0Kc=@freebsd.org X-Gm-Message-State: AOJu0YxxvanB/PKRZYa4K+Hhl4wrOgAfc+XlGCrzwUZk02gWtgQglqmf UxUry1BaodpdB0j3xqKuRISRmfE8PVjySG2qCrO99eW0/miXKX42seM+a8yEcgtMFzHso8UQsS5 fCjmkX8D0ZwWN2LuJbzcMrNLn8I9htinqH+N6Bg== X-Gm-Gg: ASbGnct6v6Q0LcnK95iuKgdbkekiLClYpsfhQkhB1DL0OSgokcjJVkdJZ+epGVFnfDw I3RLNlWM29IcuB/DGLCkhu+npjs1TLDipwiLF7w6vbCw+zYay3GOAbfGRzlHkySvVNDnHuTUTeQ lOlXlyc/eU7IbTyFk+s9rBiI/GBcs4X0heGJGM7UmwfGLEop0+rQMvPSenzohShl3e4mI= X-Google-Smtp-Source: AGHT+IHHGuu5MlnAbe9gcXjHEbbyBmZ6XoKiHzCrE+PMS8PYvypQTiZ7ZSj5to+LIQpgZ5SVKc1xu4mhL5KWh1p8RB4= X-Received: by 2002:a17:90b:1c06:b0:2ee:d371:3227 with SMTP id 98e67ed59e1d1-306a4899cddmr9744901a91.17.1743836994971; Sat, 05 Apr 2025 00:09:54 -0700 (PDT) List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@FreeBSD.org MIME-Version: 1.0 References: <39bd6092-4bd9-4086-b202-08b83b425fb5@comcast.net> <35d2361d-80e8-489a-bd9d-6c5ada5736b8@FreeBSD.org> <591a0d84-a74a-4d8e-bd40-04475eb5b457@comcast.net> <20250405125636.b078c4cdd3638a677af16494@dec.sakura.ne.jp> In-Reply-To: <20250405125636.b078c4cdd3638a677af16494@dec.sakura.ne.jp> From: Warner Losh Date: Sat, 5 Apr 2025 01:09:43 -0600 X-Gm-Features: ATxdqUGV3lBjBy5hs-zpubXoOpEgbGgvxw2fsvnAEOKzhQOoYp2_bpCctC1Zhzs Message-ID: Subject: Re: Samsung T7 external SSD support? To: Tomoaki AOKI Cc: Steve Kargl , Alexander Motin , FreeBSD Current Content-Type: multipart/alternative; boundary="000000000000a1db1a063202b005" X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US] X-Rspamd-Queue-Id: 4ZV66x34mxz400k X-Spamd-Bar: ---- --000000000000a1db1a063202b005 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Fri, Apr 4, 2025, 9:57=E2=80=AFPM Tomoaki AOKI wrote: > On Fri, 4 Apr 2025 19:44:49 -0700 > Steve Kargl wrote: > > > On 4/4/25 19:28, Alexander Motin wrote: > > > On 04.04.2025 21:45, Steve Kargl wrote: > > >> Anyone using a Samsung T7 external SSD with FreeBSD current? > > >> > > >> If I plug the drive into a USB 2.0 port, I see > > >> > > >> usb_msc_auto_quirk: UQ_MSC_NO_GETMAXLUN set for USB mass storage > > >> device Samsung PSSD T7 Shield (0x04e8:0x61fb) > > >> ugen0.2: at usbus0 > > >> umass0 on uhub1 > > >> umass0: > on > > >> usbus0 > > >> umass0: SCSI over Bulk-Only; quirks =3D 0x0100 > > >> umass0:5:0: Attached to scbus5 > > >> da0 at umass-sim0 bus 0 scbus5 target 0 lun 0 > > >> da0: Fixed Direct Access SPC-4 SCSI devic= e > > >> da0: Serial Number S6NPNS0Y201077Y > > >> da0: 40.000MB/s transfers > > >> da0: 1907729MB (3907029168 512 byte sectors) > > >> da0: quirks=3D0x2 > > >> > > >> However, the SSD is supposedly a USB 3.2 gen 2 device with a ~1000 > MBps > > >> read/write speed. > > >> > > >> When plugged into a USB 3.x port, I typically see > > >> > > >> ugen0.2: at usbus0 > > >> > > >> and the device is not listed with usbconfig. Repeatedly, unplugging > the > > >> ssd and re-plugging it into the USB 3.x port, I eventually get the > > >> above dmesg output. Do I need a quirk for this SSD to get > > >> recognized? Also, > > >> shouldn't it connect with faster transfer rate than 'da0: 40.0MB/s'? > > > > > > 40MB/s exactly means the device connected to USB2 controller or at > least > > > at USB2 speed. Considering that other times it does not connect at > all, > > > I wonder if some signal quality issue or something else prevents it > from > > > going proper USB3. IIRC USB3 uses completely different wires in the > > > connector. Also USB2 and USB3 can be handled by different controller= s > > > with different drivers, so not detecting it still might be a software > > > issue, but I can't say much about that area. > > > > Thanks for confirming my suspension. > > > > I've tried two different cables. I have few more I can test. > > Unfortunately, I have to use a short USB 3.x extension cable > > as the port is on the motherboard under a table. > > > > -- > > steve > > Another unwanted possibility would be that controller mimic'ing SCSI > (As reported being "umass0: SCSI over Bulk-Only") is reporting as if > it's U2 or UW SCSI device. > No. Reported speed doesn't matter. It's reported by the SIM and is a guess. For USB attached it doesn't change anything. Warner > https://en.wikipedia.org/wiki/SCSI > > https://en.wikipedia.org/wiki/SCSI > > > -- > Tomoaki AOKI > > --000000000000a1db1a063202b005 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


On Fri, Apr 4, 2025, 9:57=E2=80= =AFPM Tomoaki AOKI <junchoo= n@dec.sakura.ne.jp> wrote:
O= n Fri, 4 Apr 2025 19:44:49 -0700
Steve Kargl <kargls@comcast.net> wrote:

> On 4/4/25 19:28, Alexander Motin wrote:
> > On 04.04.2025 21:45, Steve Kargl wrote:
> >> Anyone using a Samsung T7 external SSD with FreeBSD current?<= br> > >>
> >> If I plug the drive into a USB 2.0 port, I see
> >>
> >> usb_msc_auto_quirk: UQ_MSC_NO_GETMAXLUN set for USB mass stor= age
> >> device Samsung PSSD T7 Shield (0x04e8:0x61fb)
> >> ugen0.2: <Samsung PSSD T7 Shield> at usbus0
> >> umass0 on uhub1
> >> umass0: <Samsung PSSD T7 Shield, class 0/0, rev 2.10/1.00,= addr 47> on
> >> usbus0
> >> umass0:=C2=A0 SCSI over Bulk-Only; quirks =3D 0x0100
> >> umass0:5:0: Attached to scbus5
> >> da0 at umass-sim0 bus 0 scbus5 target 0 lun 0
> >> da0: <Samsung PSSD T7 Shield 0> Fixed Direct Access SPC= -4 SCSI device
> >> da0: Serial Number S6NPNS0Y201077Y
> >> da0: 40.000MB/s transfers
> >> da0: 1907729MB (3907029168 512 byte sectors)
> >> da0: quirks=3D0x2<NO_6_BYTE>
> >>
> >> However, the SSD is supposedly a USB 3.2 gen 2 device with a = ~1000 MBps
> >> read/write speed.
> >>
> >> When plugged into a USB 3.x port, I typically see
> >>
> >> ugen0.2: <vendor 0x0507 product 0x0204> at usbus0
> >>
> >> and the device is not listed with usbconfig.=C2=A0 Repeatedly= , unplugging the
> >> ssd and re-plugging it into the USB 3.x port, I eventually ge= t the
> >> above dmesg output.=C2=A0 Do I need a quirk for this SSD to g= et
> >> recognized?=C2=A0 Also,
> >> shouldn't it connect with faster transfer rate than '= da0: 40.0MB/s'?
> >
> > 40MB/s exactly means the device connected to USB2 controller or a= t least
> > at USB2 speed.=C2=A0 Considering that other times it does not con= nect at all,
> > I wonder if some signal quality issue or something else prevents = it from
> > going proper USB3.=C2=A0 IIRC USB3 uses completely different wire= s in the
> > connector.=C2=A0 Also USB2 and USB3 can be handled by different c= ontrollers
> > with different drivers, so not detecting it still might be a soft= ware
> > issue, but I can't say much about that area.
>
> Thanks for confirming my suspension.
>
> I've tried two different cables.=C2=A0 I have few more I can test.=
> Unfortunately, I have to use a short USB 3.x extension cable
> as the port is on the motherboard under a table.
>
> --
> steve

Another unwanted possibility would be that controller mimic'ing SCSI (As reported being "umass0:=C2=A0 SCSI over Bulk-Only") is report= ing as if
it's U2 or UW SCSI device.


No. Reported spee= d doesn't matter. It's reported by the SIM and is a guess. For USB = attached it doesn't change anything.

<= div dir=3D"auto">Warner

--000000000000a1db1a063202b005--