Date: Sat, 30 May 2020 22:28:09 +0200 From: =?utf-8?Q?Klaus_K=C3=BCchemann?= <maciphone2@googlemail.com> To: Vincent Milum Jr <darkain@darkain.com>, freebsd-arm@freebsd.org Subject: Re: Driver for Raspberry Pi 4 PCI-express controller Message-ID: <A36F4654-4D67-44A8-9AE0-2AAC9218A289@googlemail.com> In-Reply-To: <CAOWUMWFj1FE3oiEYaKyMyg4KAfTgmFypzYJmNMPaPG0uRtDUvg@mail.gmail.com> References: <Pm_LEzoJP7MAKrZ9L-pRYQ4-qTv7TK1QARu1mwqoNFS5mzra-4zmS_0WYotf7CKSKDoZ2fjC3BSEUGIy-k95Qv1g35Zq0AsfiXwLHXpS0bE=@protonmail.com> <7F058E92-DDD3-4728-9A51-09BF1D47855C@googlemail.com> <1RBZ-1AclgkiNDwWUqrWhun8T8YSAX6g64NeSc2DKy9EF1wGsJobselP4UYGflpcmbfUx3sEEM2YplIJOXPmZ6EG_GwiMC1_3GLrqpZxisQ=@protonmail.com> <46519DEB-E96D-43DD-B739-401F9F51371E@googlemail.com> <87EE030D-5323-477B-9FF3-CB8970138729@googlemail.com> <t9qxjbkckKn-ohuWeAtdO6YomotuNUUJrldo1QJcMjWu7RcTaESt1LfG1uz3arRRVdbIbGDZcv3bfFODv0vxmdHa2r2sSQc3nQoZa3nKAGg=@protonmail.com> <37A9A3AA-F2AF-4F08-84BE-8A19E75DB5E0@googlemail.com> <CAOWUMWFj1FE3oiEYaKyMyg4KAfTgmFypzYJmNMPaPG0uRtDUvg@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi,=20 thanks, Vincent, for your extensive testing, very helpful !=20 `hope it=E2=80=99s okay for you to keep this discussion public(forward = to freebsd-arm@freebsd.org) . > Am 30.05.2020 um 20:11 schrieb Vincent M. Jr <>: >=20 > dmesg: https://dmesgd.nycbug.org/index.cgi?do=3Dview&id=3D5523 >=20 > =E2=80=A6=E2=80=A6. > It isn't perfectly stable, but at least initially working=E2=80=A6.. Yeah, initially (sometimes) works for me too... >=20 > Testing it with a USB-C (with adapter) ethernet + 3-port hub. I'm = using this for wired ethernet rather than the built in ethernet just for = testing. >=20 > On the three hub ports, I have a microsoft keyboard, microsoft mouse, = and a kingston datatraveler thumbdriv > There is also a Logitech keyboard on one of the Pi's USB 2.0 ports Did you test hot-unplugging/replugging the peripherals ? >=20 > For testing, I've created a single-drive ZFS pool with the kingston = drive. >=20 > I went to delete a test file, and got the following: >=20 > xhci_interrupt: host system error > xhci0: Resetting controller > uhub0: at usbus0, port 1, addr 1 (disconnected) > ugen0.2: <vendor 0x2109 USB2.0 Hub> at usbus0 (disconnected) > uhub1: at uhub0, port 1, addr 1 (disconnected) > ugen0.3: <Generic 4-Port USB 2.0 Hub> at usbus0 (disconnected) > uhub2: at uhub1, port 1, addr 2 (disconnected) > ugen0.4: <Kingston DataTraveler 3.0> at usbus0 (disconnected) > umass0: at uhub2, port 1, addr 3 (disconnected) > (da0:umass-sim0:0:0:0): WRITE(10). CDB: 2a 00 00 a0 21 a5 00 00 80 00 > (da0:umass-sim0:0:0:0): CAM status: CCB request completed with an = error > (da0:umass-sim0:0:0:0): Retrying command, 3 more tries remain >=20 > But every single device had to be re-detected which took ~5-10 seconds = to complete. Yeah, experienced that too ... >=20 >=20 > On another boot attempt, I'm getting this repeatedly while at the = login prompt:...usb_alloc_device: device init 2 failed (USB_ERR_TIMEOUT, = ignored)...ugen0.2: <Unknown > at usbus0 (disconnected)=E2=80=A6. This is a very interesting information : <another boot attempt> =E2=80=A6 do you mean that not every boot-attempt = does the same (for unknown reason) (That=E2=80=99s what I have experienced but I wasn=E2=80=99t sure = whether my uSD is damaged or whether it`s caused by the = pie-driver-electricity ?? Specially the <Unknown > at -thing only appears in some boot = attempts(not all) In my tests the strange thing is that one boot-attempt succeeds and = another not , while left the machine completely untouched between those = attempts.. > update: i've gotten this also while doing a lengthy transfer to USB = ZFS pool, and the error cycling never stops. I will try to make a ZFS-pool-test... >=20 > xhci0: Controller reset timeout. > uhub0 on usbus0 > uhub0: <0x1106 XHCI root HUB, class 9/0, rev 3.00/1.00, addr 1> on = usbus0 > uhub0: 5 ports with 4 removable, self powered > xhci0: Resetting controller > usb_alloc_device: device init 2 failed (USB_ERR_TIMEOUT, ignored) > ugen0.2: <Unknown > at usbus0 (disconnected) > uhub_reattach_port: could not allocate new device > uhub0: at usbus0, port 1, addr 1 (disconnected) > uhub0: detached > xhci0: Controller halt timeout. > xhci0: Controller reset timeout. > xhci0: Controller reset timeout. > uhub0 on usbus0 > uhub0: <0x1106 XHCI root HUB, class 9/0, rev 3.00/1.00, addr 1> on = usbus0 > uhub0: 5 ports with 4 removable, self powered > xhci0: Resetting controller > usb_alloc_device: device init 2 failed (USB_ERR_TIMEOUT, ignored) > ugen0.2: <Unknown > at usbus0 (disconnected) > uhub_reattach_port: could not allocate new device > uhub0: at usbus0, port 1, addr 1 (disconnected) > uhub0: detached > xhci0: Controller halt timeout. > xhci0: Controller reset timeout. > xhci0: Controller reset timeout. >=20 >=20 > =E2=80=A6=E2=80=A6.. xhci0 is this :=20 = https://svnweb.freebsd.org/base/head/sys/dev/usb/controller/generic_xhci.c= ?view=3Dmarkup (and the corresponding fdt/acpi-files)=20 uhub0 is this : https://svnweb.freebsd.org/base/head/sys/dev/usb/usb_hub.c?view=3Dmarkup Thanks again for testing, Regards=20
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?A36F4654-4D67-44A8-9AE0-2AAC9218A289>