From owner-freebsd-arm@freebsd.org Sun Jun 7 02:56:17 2020 Return-Path: Delivered-To: freebsd-arm@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 5AE04347386 for ; Sun, 7 Jun 2020 02:56:17 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (www.zefox.net [50.1.20.27]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "www.zefox.com", Issuer "www.zefox.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 49fgxq452dz4ZJt for ; Sun, 7 Jun 2020 02:56:15 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (localhost [127.0.0.1]) by www.zefox.net (8.15.2/8.15.2) with ESMTPS id 0572uGYs038339 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Sat, 6 Jun 2020 19:56:17 -0700 (PDT) (envelope-from fbsd@www.zefox.net) Received: (from fbsd@localhost) by www.zefox.net (8.15.2/8.15.2/Submit) id 0572uGGu038338; Sat, 6 Jun 2020 19:56:16 -0700 (PDT) (envelope-from fbsd) Date: Sat, 6 Jun 2020 19:56:16 -0700 From: bob prohaska To: Mark Millard Cc: freebsd-arm@freebsd.org, bob prohaska Subject: Re: Confusing USB device conflict Message-ID: <20200607025616.GA38272@www.zefox.net> References: <20200606223853.GA37281@www.zefox.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Rspamd-Queue-Id: 49fgxq452dz4ZJt X-Spamd-Bar: ++ Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=none (mx1.freebsd.org: domain of fbsd@www.zefox.net has no SPF policy when checking 50.1.20.27) smtp.mailfrom=fbsd@www.zefox.net X-Spamd-Result: default: False [2.60 / 15.00]; RCVD_TLS_ALL(0.00)[]; ARC_NA(0.00)[]; WWW_DOT_DOMAIN(0.50)[]; MID_RHS_MATCH_FROM(0.00)[]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; TO_DN_SOME(0.00)[]; NEURAL_SPAM_SHORT(0.30)[0.303]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[zefox.net]; AUTH_NA(1.00)[]; NEURAL_SPAM_MEDIUM(0.37)[0.369]; TO_MATCH_ENVRCPT_SOME(0.00)[]; NEURAL_SPAM_LONG(0.03)[0.027]; R_SPF_NA(0.00)[no SPF record]; FREEMAIL_TO(0.00)[yahoo.com]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:7065, ipnet:50.1.16.0/20, country:US]; RCVD_COUNT_TWO(0.00)[2]; MID_RHS_WWW(0.50)[] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.33 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Jun 2020 02:56:17 -0000 On Sat, Jun 06, 2020 at 06:22:03PM -0700, Mark Millard wrote: > > > > On 2020-Jun-6, at 15:38, bob prohaska wrote: > > > > Just got a disk, adapter and usb3 hub for use with > > freebsd-arm. When it's connected to a Pi2 running 12-stable, > > the console reports > > > > login: ugen0.6: at usbus0 > > uhub2 on uhub1 > > uhub2: on usbus0 > > uhub2: MTT enabled > > uhub2: 4 ports with 4 removable, self powered > > smsc0: warning: Failed to read register 0x114 > > smsc0: warning: MII is busy > > smsc0: warning: Failed to read register 0x114 > > smsc0: warning: MII is busy > > smsc0: warning: Failed to read register 0x114 > > smsc0: warning: MII is busy > > smsc0: warning: Failed to read register 0x114 > > smsc0: warning: MII is busy > > (da0:umass-sim0:0:0:0): READ(10). CDB: 28 00 02 06 20 50 00 00 30 00 > > > > Things then go from bad to worse, ending with > > Does this happen with FreeBSD head? It looked like there > was a late 2019 check-in that was related to a context > that involved the above types of messages on a RPi*. If > you are lucky, may be there is something someone could > MFC back into 12 that would help. (I do not know the > details or if what I saw really would help if head > works okay.) I'll find out shortly. 13-current is building on a Pi3 presently. If head works, there's hope for tail on 12! > > (da0:umass-sim0:0:0:0): Periph destroyed > > umass0: detached > > ugen0.5: at usbus0 (disconnected) > > uftdi0: at uhub1, port 4, addr 5 (disconnected) > > uftdi0: detached > > ugen0.6: at usbus0 (disconnected) > > uhub2: at uhub1, port 5, addr 6 (disconnected) > > uhub2: detached > > uhub1: detached > > ugen0.2: at usbus0 (disconnected) > > Jun 6 15:20:00 www syslogd: /var/log/cron: Device not configured > > vm_fault: pager read error, pid 924 (sendmail) > > vm_fault: pager read error, pid 927 (sendmail) > > vm_fault: pager read error, pid 930 (sendmail) > > vm_fault: pager read error, pid 933 (sendmail) > > vm_fault: pager read error, pid 936 (sendmail) > > > > AFAIK, smsc is a (not-present) network device. Perhaps a case of > > mistaken identity? I've seen complaints from smsc0 before, but > > not lately. > > On a RPi3 here (omitted text indicated with ". . ."): > > # devinfo > nexus0 > ofwbus0 > psci0 > simplebus0 > . . . > bcm283x_dwcotg0 > usbus0 > uhub0 > uhub1 > smsc0 > miibus0 > smscphy0 > uhub3 > umass0 > uhub2 > ukbd0 > uhid0 > ums0 > . . . > ofw_clkbus0 > . . . > cryptosoft0 > > (Context: head -r360311 based) > > In the above, uhub3 is my external, powered, USB3 > capable hub that the USB3 SSD is on that holds > FreeBSD. (USB2 compatible devices.) > > # usbconfig show_ifdrv > . . . > ugen0.2: at usbus0, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE (2mA) > ugen0.2.0: uhub1: > ugen0.3: at usbus0, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON (2mA) > ugen0.3.0: smsc0: > ugen0.7: at usbus0, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE (100mA) > ugen0.7.0: uhub3: > ugen0.8: at usbus0, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON (0mA) > ugen0.8.0: umass0: > . . . > > uhub1 and smsc0 are internal the the RPi3, > smsc being for the Ethernet interface (based on > looking around that is what it appeared to be > anyway). > > An interesting implication is that the Ethernet and the > external USB ports on the RPi3* share bandwidth via > uhub1 and uhub0. Yes, that's my understanding also. > > > FWIW, when connected to a Pi3B+ running Raspberry Pi Buster, the hub, > > adapter and disk are recognized correctly, but dmesg reports: > > The driver for the USB controller dwc_otg_hcd does not support scatter-gather which is > > required by the UAS driver. Please try an other USB controller if you wish to use UAS. > > There's no crash, and it looks like the device file is created, though I haven't > > tried to talk with it yet. > > https://www.raspberrypi.org/forums/viewtopic.php?f=28&t=245931 documents: > > QUOTE > Prior to Pi 4, the USB host controller software did not support DMA > scatter-gather operations. As a result of this limitation, the USB > Attached SCSI (UAS) driver was not enabled. . . . > All UAS drives must support mass-storage as a fallback option. . . . > END QUOTE > > So the lack of UAS support for the context should not mean > lack of mass-storage support. > Thanks for a little good news! 8-) bob prohaska > === > Mark Millard > marklmi at yahoo.com > ( dsl-only.net went > away in early 2018-Mar) > >