I did not push strongly my patch because I recently had an hard time trusting my computer (I fear my motherboard may have an issue). Since you have exactly the same bug, yes, a debian bug report would help since the debian team could backport the patch in their kernel, waiting for it to be upstreamed.
Otherwise, well... I'm manually patching my .ko file using an hex editor. That's a weird way to work around the bug, but it's faster than recompiling :)
Just so I can have an idea what may be wrong here, what is your motherboard and what is your CPU ?
[^] # Re: Not in 4.15-RC5 yet
Posté par Pinaraf . En réponse au journal D'un kernel panic à un patch.... Évalué à 5.
Ok, now we have something :)
I did not push strongly my patch because I recently had an hard time trusting my computer (I fear my motherboard may have an issue). Since you have exactly the same bug, yes, a debian bug report would help since the debian team could backport the patch in their kernel, waiting for it to be upstreamed.
Otherwise, well... I'm manually patching my .ko file using an hex editor. That's a weird way to work around the bug, but it's faster than recompiling :)
Just so I can have an idea what may be wrong here, what is your motherboard and what is your CPU ?