On 24.06.23 14:15, Bagas Sanjaya wrote: > On 6/24/23 17:21, Elmar Stellnberger wrote: >> Hi Bagas S., Hi all >> >> concerns: Bug 217544 - kernel fault on hibernation: get_zeroed_page/swsusp_write >> https://bugzilla.kernel.org/show_bug.cgi?id=217544 >> >> Bisection does not make sense here, since I can not reproduce the >> issue. Packing the kernel binaries and symbol files was meant to invoke >> gdb directly on the kcore: > > Thorsten: Should this be marked as invalid/inconclusive? Not as invalid, as there might be a real issue here; but it's hard to say, as among others it also quite possible that something else went wrong (compiler? hardware?). Someone would have to investigate. But given the fact that this happened with a stable kernel[1] and is impossible to reproduce, I suspect no developer will be motivated enough to do so. Then it's not worth tracking[2]: #regzbot inconclusive: impossible to reproduce Elmar, that's nothing bad. In case this turns out to be something you can reproduce and bisect, just let us know and we'll add it back. [1] see the sections about stable kernels https://linux-regtracking.leemhuis.info/post/frequent-reasons-why-linux-kernel-bug-reports-are-ignored/ [2] side note: due to limited resources I consider to stop tracking all non-bisected issues in general (expect those that started to happen in mainline since the last mainline release) – or put them in a special category that signals "those are collected here JFYI until they are bisected, as the regression tracker due to limited resources for now can't keep a close eye on these" Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat) -- Everything you wanna know about Linux kernel regression tracking: https://linux-regtracking.leemhuis.info/about/#tldr If I did something stupid, please tell me, as explained on that page.
