Date: Sat, 6 Jun 2020 15:38:53 -0700 From: bob prohaska <fbsd@www.zefox.net> To: freebsd-arm@freebsd.org Subject: Confusing USB device conflict Message-ID: <20200606223853.GA37281@www.zefox.net>
next in thread | raw e-mail | index | archive | help
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: <GenesysLogic USB2.0 Hub> at usbus0 uhub2 on uhub1 uhub2: <GenesysLogic USB2.0 Hub, class 9/0, rev 2.00/92.24, addr 6> 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: <FTDI USB - Serial> at usbus0 (disconnected) uftdi0: at uhub1, port 4, addr 5 (disconnected) uftdi0: detached ugen0.6: <GenesysLogic USB2.0 Hub> at usbus0 (disconnected) uhub2: at uhub1, port 5, addr 6 (disconnected) uhub2: detached uhub1: detached ugen0.2: <Unknown > 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20200606223853.GA37281>