Search
5 results for “kernellogger”
-
PSA: you want to report a #LinuxKernel regression you encountered when switching from a distribution's #kernel to a newer one that is vanilla or close to it?
Then you want to check if a vanilla build of the #Linux version the working distro's #kernel is based on actually works, as the latter might only work due to some modification the downstream vendor applied.
This is one reason[1] why https://docs.kernel.org/admin-guide/verify-bugs-and-bisect-regressions.html (screenshotted) tells you to do that. A recent discussion (https://lore.kernel.org/all/2026092511[email protected]/ ) shows that this is not a theoretical precaution: something worked with Ubuntu's kernel but not with a vanilla build from the same series because Canonical applied a patch that one of the upstream developers called a "horrible hack that is never going to be applied [upsteam]".
[1] The other reason: "verify if the .config localmodconfig created actually creates a working kernel, as you otherwise will only start to suspect problems in that area midway through the bisection – and by that point will have wasted a lot of time".
-
PSA: you want to report a #LinuxKernel regression you encountered when switching from a distribution's #kernel to a newer one that is vanilla or close to it?
Then you want to check if a vanilla build of the #Linux version the working distro's #kernel is based on actually works, as the latter might only work due to some modification the downstream vendor applied.
This is one reason[1] why https://docs.kernel.org/admin-guide/verify-bugs-and-bisect-regressions.html (screenshotted) tells you to do that. A recent discussion (https://lore.kernel.org/all/2026092511[email protected]/ ) shows that this is not a theoretical precaution: something worked with Ubuntu's kernel but not with a vanilla build from the same series because Canonical applied a patch that one of the upstream developers called a "horrible hack that is never going to be applied [upsteam]".
[1] The other reason: "verify if the .config localmodconfig created actually creates a working kernel, as you otherwise will only start to suspect problems in that area midway through the bisection – and by that point will have wasted a lot of time".
-
PSA: you want to report a #LinuxKernel regression you encountered when switching from a distribution's #kernel to a newer one that is vanilla or close to it?
Then you want to check if a vanilla build of the #Linux version the working distro's #kernel is based on actually works, as the latter might only work due to some modification the downstream vendor applied.
This is one reason[1] why https://docs.kernel.org/admin-guide/verify-bugs-and-bisect-regressions.html (screenshotted) tells you to do that. A recent discussion (https://lore.kernel.org/all/2026092511[email protected]/ ) shows that this is not a theoretical precaution: something worked with Ubuntu's kernel but not with a vanilla build from the same series because Canonical applied a patch that one of the upstream developers called a "horrible hack that is never going to be applied [upsteam]".
[1] The other reason: "verify if the .config localmodconfig created actually creates a working kernel, as you otherwise will only start to suspect problems in that area midway through the bisection – and by that point will have wasted a lot of time".
-
PSA: you want to report a #LinuxKernel regression you encountered when switching from a distribution's #kernel to a newer one that is vanilla or close to it?
Then you want to check if a vanilla build of the #Linux version the working distro's #kernel is based on actually works, as the latter might only work due to some modification the downstream vendor applied.
This is one reason[1] why https://docs.kernel.org/admin-guide/verify-bugs-and-bisect-regressions.html (screenshotted) tells you to do that. A recent discussion (https://lore.kernel.org/all/2026092511[email protected]/ ) shows that this is not a theoretical precaution: something worked with Ubuntu's kernel but not with a vanilla build from the same series because Canonical applied a patch that one of the upstream developers called a "horrible hack that is never going to be applied [upsteam]".
[1] The other reason: "verify if the .config localmodconfig created actually creates a working kernel, as you otherwise will only start to suspect problems in that area midway through the bisection – and by that point will have wasted a lot of time".
-
PSA: you want to report a #LinuxKernel regression you encountered when switching from a distribution's #kernel to a newer one that is vanilla or close to it?
Then you want to check if a vanilla build of the #Linux version the working distro's #kernel is based on actually works, as the latter might only work due to some modification the downstream vendor applied.
This is one reason[1] why https://docs.kernel.org/admin-guide/verify-bugs-and-bisect-regressions.html (screenshotted) tells you to do that. A recent discussion (https://lore.kernel.org/all/2026092511[email protected]/ ) shows that this is not a theoretical precaution: something worked with Ubuntu's kernel but not with a vanilla build from the same series because Canonical applied a patch that one of the upstream developers called a "horrible hack that is never going to be applied [upsteam]".
[1] The other reason: "verify if the .config localmodconfig created actually creates a working kernel, as you otherwise will only start to suspect problems in that area midway through the bisection – and by that point will have wasted a lot of time".