[Bug 237666] repeated messages of "uhub_reattach_port: giving up port reset - device vanished"

Go to: [ bottom of page ] [ top of archives ] [ this month ]
From: <bugzilla-noreply_at_freebsd.org>
Date: Thu, 29 Dec 2022 15:32:25 UTC
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237666

Graham Perrin <grahamperrin@freebsd.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
              Flags|mfc-stable12?               |mfc-stable12-
           Hardware|amd64                       |Any
            Version|12.1-STABLE                 |13.0-RELEASE
           See Also|                            |https://bugs.freebsd.org/bu
                   |                            |gzilla/show_bug.cgi?id=2356
                   |                            |25
                 CC|                            |usb@FreeBSD.org

--- Comment #219 from Graham Perrin <grahamperrin@freebsd.org> ---
Re: comment 197

Branches shown at
<https://github.com/freebsd/freebsd-src/commit/ad9d0df7c66a02db53f102e87e6f8414e8da67fc>
now include: 

    releng/13.1

Other commits that went through routine release engineering included: 

*
<https://github.com/freebsd/freebsd-src/commit/4cb98e0bea637b18e196015291441feb1c5107fe>

*
<https://github.com/freebsd/freebsd-src/commit/a29c0348f0653c25adb65e340e6f5a7edc86b8a2>

*
<https://github.com/freebsd/freebsd-src/commit/2144eb756895d97f8a09961b270f08b166a71d65>


Triage
======

Affected: 13.0-RELEASE (based partly on comments that related to 13.0-STABLE).
Please note, this is not intended to be definitive; available versions in this
menu may change through bug 262494, and so on. 

Hardware: any (based partly on comment 153).

With <https://www.freebsd.org/security/#sup> and no plan for 12.5, a
cherry-pick to stable/12 (leading to a release engineered patch for
12.4-RELEASE) seems unlikely. 

CC: usb@

Given the diversity of USB hardware – and the current length and breadth of
this bug report – here's a single question for usb@ or any other committer with
a good overview: 

* should tracking (the keyword) apply to this report, or maybe to a 
  new report that can be _solely_ for tracking? 

(A newcomer to this report will probably find it overwhelming, and I'm not the
person to summarise. I'm more double-decker than universal serial.)

That's not the only question …

<https://wiki.freebsd.org/Discord> #kernel or nearby should be ideal to kick
the ball around without adding noise to Bugzilla. Either that, or
<https://wiki.freebsd.org/IRC/Channels#Official_Channels> #freebsd-dev (not
logged). 

HTH

Graham (triage trainee without a ^ hat of officialdom)

-- 
You are receiving this mail because:
You are on the CC list for the bug.