On Wednesday, 11 January 2023 19:28:25 CET Julian Groß wrote: > On Mon, 09 Jan 2023 14:09:30 +0100 Diederik de Haas > <didi.deb...@cknow.org> wrote: > > https://wiki.debian.org/DebianKernel/GitBisect describes a procedure > > to find the exact commit which introduced the issue you reported, but it's > > often faster to first narrow down the range using snapshot.d.o. > > The way I understand the `git bisect`, and with the issue taking > sometimes days to happen, I will be sitting on this for months by the way.
Yep, that would/could be the consequence, which I can fully understand is not desirable or very useful. Having the exact offending commit is ideal, but not a '100%' requirement. As you've determined that it already happened with 6.0~rc7 and not with 5.19.x, that's already a reasonably small range (likely introduced in the 6.0 merge window). So the next thing to do, is present the issue to the relevant upstream maintainers. Searching for "nvme controller is down" brought up another bug (but that happened pretty instantly) and in there the request was made to report the issue (via email) to the linux-...@vger.kernel.org and linux-n...@lists.infradead.org lists. And that seems like the next best step for you too. Use the information you provided in your initial bug report and add the extra findings (ie 6.1-rc7) to that too. When you've done that, please inform this bug report where you did that so that we can track it's progress too. Cheers, Diederik
signature.asc
Description: This is a digitally signed message part.
