Date: Mon, 27 Sep 2021 22:46:14 +0000 From: bugzilla-noreply@freebsd.org To: usb@FreeBSD.org Subject: [Bug 258057] muge(4) crashes with large tx batches Message-ID: <bug-258057-19105-ai8L0jdpre@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-258057-19105@https.bugs.freebsd.org/bugzilla/> References: <bug-258057-19105@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D258057 Mark Millard <marklmi26-fbsd@yahoo.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |marklmi26-fbsd@yahoo.com --- Comment #25 from Mark Millard <marklmi26-fbsd@yahoo.com> --- (In reply to Dan Kotowski from comment #21) >From HoneyComb that was delivered in 2021-June (same report as I made on SolidRuns's discord area, then some extra notes): # usbconfig ugen1.1: <Generic XHCI root HUB> at usbus1, cfg=3D0 md=3DHOST spd=3DSUPER (= 5.0Gbps) pwr=3DSAVE (0mA) ugen0.1: <Generic XHCI root HUB> at usbus0, cfg=3D0 md=3DHOST spd=3DSUPER (= 5.0Gbps) pwr=3DSAVE (0mA) ugen1.2: <vendor 0x04b4 product 0x6502> at usbus1, cfg=3D0 md=3DHOST spd=3D= HIGH (480Mbps) pwr=3DSAVE (0mA) ugen0.2: <Realtek USB 10/100/1000 LAN> at usbus0, cfg=3D0 md=3DHOST spd=3DS= UPER (5.0Gbps) pwr=3DON (72mA) ugen1.3: <vendor 0x0424 product 0x2514> at usbus1, cfg=3D0 md=3DHOST spd=3D= HIGH (480Mbps) pwr=3DSAVE (2mA) ugen1.4: <vendor 0x04b4 product 0x6500> at usbus1, cfg=3D0 md=3DHOST spd=3D= SUPER (5.0Gbps) pwr=3DSAVE (0mA) ugen1.5: <Samsung PSSD T7 Touch> at usbus1, cfg=3D0 md=3DHOST spd=3DSUPER (= 5.0Gbps) pwr=3DON (224mA) ugen1.6: <Samsung PSSD T7 Touch> at usbus1, cfg=3D0 md=3DHOST spd=3DSUPER (= 5.0Gbps) pwr=3DON (224mA) I've never had problems with USB3 devices that I've tried ending up without SUPER (5.0Gbps) status. (But it is only a few types of devices.) The Realtek USB 10/100/1000 LAN is plugged into the port nearest to the board. I've been running various FreeBSD versions over the time. I use bectl to bo= ot any of releng/13.0.0 , stable/13, and main [so: 14], mostly 13.0R and main. For example (root-is-ZFS): # uname -apKU FreeBSD CA72_16Gp_ZFS 14.0-CURRENT FreeBSD 14.0-CURRENT #12 main-n249019-0637070b5bca-dirty: Tue Aug 31 02:24:20 PDT 2021=20=20=20=20 root@CA72_16Gp_ZFS:/usr/obj/BUILDs/main-CA72-nodbg-clang/usr/main-src/arm64= .aarch64/sys/GENERIC-NODBG-CA72 arm64 aarch64 1400032 1400032 I usually boot an Optane in the PCIe slot but also boot an external USB3 SSD that has a slightly modified copy of the Optane (recopied & adjusted as I progre= ss). The system is built with -mcpu=3Dcortex-a72 (mentioned because it is unusua= l). The USB3 ssd can boot RPi4B's with 8 GiBytes of RAM. (I avoid ZFS when ther= e is less than 8 GiBytes.) None of those systems have had problems identifying U= SB3 SUPER as appropriate. I've used the Realtek USB3 LAN type of dongle on all = of them. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-258057-19105-ai8L0jdpre>