Date: Thu, 29 Jun 2017 21:46:58 +0200 From: Matthias Apitz <guru@unixarea.de> To: freebsd-usb@freebsd.org Subject: USB devices sometimes not seen at boot time Message-ID: <20170629194658.GA2488@c720-r314251>
next in thread | raw e-mail | index | archive | help
--YiEDa0DAkWCtVeE4 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hello, I have the problem that on my netbook (an Acer C720) sometimes the USB devices are not seen at boot time while the bus is probed. I filed an issue as https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D220127 which did not got any attention so far.=20 Meanwhile I was trying to find the rule for the problem and have investigated the 'dmesg' output for any "good" boot (i.e. the devices was seen) and compared with "bad" boot (when the device was not seen). There is a clear dependency of the order the USB bus is probed: This is from a good one: # egrep 'uhub|ugen' dmesg-20170628-202601-good.txt ugen0.1: <0x8086 XHCI root HUB> at usbus0 ugen1.1: <Intel EHCI root HUB> at usbus1 uhub0: <0x8086 XHCI root HUB, class 9/0, rev 3.00/1.00, addr 1> on usbus0 uhub1: <Intel EHCI root HUB, class 9/0, rev 2.00/1.00, addr 1> on usbus1 uhub0: 13 ports with 13 removable, self powered uhub1: 2 ports with 2 removable, self powered ugen0.2: <Identiv uTrust 3512 SAM slot Token> at usbus0 ugen0.3: <SunplusIT Inc HD WebCam> at usbus0 ugen0.4: <vendor 0x0489 product 0xe056> at usbus0 and this is from a bad one: # egrep 'uhub|ugen' dmesg-20170628-202351-bad.txt ugen1.1: <Intel EHCI root HUB> at usbus1 ugen0.1: <0x8086 XHCI root HUB> at usbus0 uhub0: <Intel EHCI root HUB, class 9/0, rev 2.00/1.00, addr 1> on usbus1 uhub1: <0x8086 XHCI root HUB, class 9/0, rev 3.00/1.00, addr 1> on usbus0 uhub1: 13 ports with 13 removable, self powered uhub0: 2 ports with 2 removable, self powered ugen1.2: <vendor 0x8087 product 0x8000> at usbus1 uhub2 on uhub0 uhub2: <vendor 0x8087 product 0x8000, class 9/0, rev 2.00/0.04, addr 2> on = usbus1 uhub2: 8 ports with 8 removable, self powered The device in question it the "Identiv uTrust 3512 SAM slot Token" and the rule is: When XHCI is probed as ugen0.1 and later as uhub0, all is fine; else it fails. Any ideas on this? What makes the boot differ in this order? Thanks matthias --=20 Matthias Apitz, =E2=9C=89 guru@unixarea.de, =E2=8C=82 http://www.unixarea.d= e/ Public GnuPG key: http://www.unixarea.de/key.pub --YiEDa0DAkWCtVeE4 Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCAAdFiEEXmn7rBYYViyzy/vBR8z35Hb+nREFAllVWSsACgkQR8z35Hb+ nREkng/+PCYyQavRCdMH9NFSQ1WgJ7AnJx7Rr1ATuqcwOSmWkynmyCENfpx/g1u6 K5kqO9g27wrze8tbZ27GB8/RKuHr6/Y1+XwCi0Mf3DOWH0KUHjmqhe2yNzY7GxnT F39kPc/s2vsGPdxNjR56ouCWcKE3dAUSRq5xDl/3nA45t39BTxRn9iu469ermlfX P0XUpx4F+fdpQy5nMXTLhl0/2xrl7xuMNv7sS7ml7vNwPOZUqcgx+KgedxE5atek 7o3pqm1+n9QpHu243g9YhGgADXjeafVzqlSuuyOsZVNJqR1y1OEbSfqc3Mg9NHLX DJEzR4nGm7y8uoNYv1eT/ysDb3b4W0gSqKinV1qXbEwmOidfrxfFuzOgwCxygfRa Ni69an0TmXPNeBgjuyYswO567ZVvdBQkbG+w56syPTxAEekJjNyBzAFj4WHXJ6xH 17EnyGF3sjjPdNkrmmdby7RZoRVsfaQ0yHiptP+xN5P5YGTZo8ehFHuzqgVUTwPv 66ToHBaMvjhym1qnx7F4LjrbA+QZZl7OOAYlH7Ol5p1IVuWLszjyhiYfUWii47bR 4M1QtAH+WAGQP/h9Lkydeu3rFOa0I8IdHBRIF3739kA3co/yBiNNeft73V+YV22t uZ0JrNoH3DRIL4j4aUC/Edecoj7JHwoyhMkrs3qBmWxRW1BN5Ok= =RRZn -----END PGP SIGNATURE----- --YiEDa0DAkWCtVeE4--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20170629194658.GA2488>