Date: Tue, 15 Sep 2020 05:12:04 +0000 From: bugzilla-noreply@freebsd.org To: usb@FreeBSD.org Subject: [Bug 237666] repeated messages of "uhub_reattach_port: giving up port reset - device vanished" Message-ID: <bug-237666-19105-5caIWigRvF@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-237666-19105@https.bugs.freebsd.org/bugzilla/>
index | next in thread | previous in thread | raw e-mail
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237666 --- Comment #132 from Mark Millard <marklmi26-fbsd@yahoo.com> --- (In reply to Mark Millard from comment #126, #128, #131) Interesting finding? . . . I've tested putting the -mcpu=cortex-a72 based kernel on the cortext-a53 system and . . . The result boots and operates fine. (It is also a USB3 SSD based root file system.) But the xhci context (from the cortext-a53 system) is: # dmesg -a | grep -i xhci xhci0: <Synopsys Designware DWC3> mem 0xff600000-0xff6fffff irq 57 on rk_dwc30 xhci0: 64 bytes context size, 32-bit DMA usbus0 on xhci0 ugen0.1: <Synopsys XHCI root HUB> at usbus0 uhub0: <Synopsys XHCI root HUB, class 9/0, rev 3.00/1.00, addr 1> on usbus0 Instead of (from the cortext-a53 kernel on the cortext-a72 system): # dmesg -a | grep -i xhci | more xhci0: <Generic USB 3.0 controller> iomem 0x600000000-0x600000fff irq 0 on acpi0 xhci0: 32 bytes context size, 32-bit DMA usbus0 on xhci0 ugen0.1: <Generic XHCI root HUB> at usbus0 uhub0: <Generic XHCI root HUB, class 9/0, rev 3.00/1.00, addr 1> on usbus0 xhci0: Resetting controller uhub0: <Generic XHCI root HUB, class 9/0, rev 3.00/1.00, addr 1> on usbus0 So more than the cpu type and its properties provide distinctions. -- You are receiving this mail because: You are the assignee for the bug.home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-237666-19105-5caIWigRvF>