Date: Sun, 14 Jan 2024 02:33:36 +0000 From: bugzilla-noreply@freebsd.org To: usb@FreeBSD.org Subject: [Bug 276307] [ure] Unable to ping RTL8153 usb 3.0 to gigabit ethernet adapter (0bda:8153) from connected Windows device after S3 sleep/wake cycling said Windows device (no quirk to set config) Message-ID: <bug-276307-19105-Yl7GsZ2jc2@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-276307-19105@https.bugs.freebsd.org/bugzilla/> References: <bug-276307-19105@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D276307 Warner Losh <imp@FreeBSD.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |imp@FreeBSD.org --- Comment #2 from Warner Losh <imp@FreeBSD.org> --- It would be useful to know if the quirk entry, once restored, fixes things. There is a way to dynamically add usb quirks. You'll need to load usb_quirk= and follow the instructions in https://man.freebsd.org/cgi/man.cgi?query=3Dusb_quirk&sektion=3D4&n=3D1 and https://man.freebsd.org/cgi/man.cgi?query=3Dusbconfig&sektion=3D8&apropos= =3D0&manpath=3DFreeBSD+14.0-RELEASE+and+Ports to add the quirk back and see if the problem persists. I'm not sure if the I/F should be pingable in S3 though. FreeBSD is basical= ly shutdown at that point (Linux might not be). If a sleep/wake cycle results = in it not being pingable, then that is definitely a bug (it was a little uncle= ar from your description). --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-276307-19105-Yl7GsZ2jc2>