From owner-freebsd-arm@freebsd.org Sat Jun 6 22:38:59 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 4909F34019F for ; Sat, 6 Jun 2020 22:38:59 +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 49fZDx5Zzyz44kq for ; Sat, 6 Jun 2020 22:38:57 +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 056McrfG037818 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Sat, 6 Jun 2020 15:38:53 -0700 (PDT) (envelope-from fbsd@www.zefox.net) Received: (from fbsd@localhost) by www.zefox.net (8.15.2/8.15.2/Submit) id 056Mcrvi037817; Sat, 6 Jun 2020 15:38:53 -0700 (PDT) (envelope-from fbsd) Date: Sat, 6 Jun 2020 15:38:53 -0700 From: bob prohaska To: freebsd-arm@freebsd.org Subject: Confusing USB device conflict Message-ID: <20200606223853.GA37281@www.zefox.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Rspamd-Queue-Id: 49fZDx5Zzyz44kq 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 [1.36 / 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)[]; TO_DN_SOME(0.00)[]; NEURAL_HAM_MEDIUM(-0.40)[-0.396]; NEURAL_HAM_LONG(-0.50)[-0.503]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[zefox.net]; AUTH_NA(1.00)[]; NEURAL_SPAM_SHORT(0.36)[0.357]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCPT_COUNT_TWO(0.00)[2]; R_SPF_NA(0.00)[no SPF record]; 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: Sat, 06 Jun 2020 22:38:59 -0000 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 (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. 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. Thanks for reading, and any ideas..... bob prohaska