Hi Paul,
On Thu, Jun 29, 2023 at 06:27:02PM +0200, Paul Leiber wrote:
> Just to state the obvious, what's bothering me is that my setup was working
> with kernel 5.10.0-21 and that it stopped working with kernel 5.10.178-3. So
> it seems that somewhere inbetween, changes have been introduced that lead to
> the non-working state. If I am not wrong, then that's called a regression,
> although one that seems to affect only a very limited number of users (who's
> the other one?). In principle, it should be possible to identify this
> change, but I lack the knowledge to do so.
You perhaps need to bisect the kernel. Can you easily reproduce the
problem on demand? If you can then this shouldn't take too long.
Here are some instructions:
https://wiki.debian.org/DebianKernel/GitBisect
If you do manage to identify the exact change that breaks things for
you, expect xen-devel would be very interested in knowing it, and
may even be able to suggest a fix.
We are getting ahead of ourselves here, but if they do come up with
a patch to fix things for you then it will likely be a patch
against some upstream kernel version. You would need to apply that
yourself (or just run an upstream kernel) until the patch makes its
way into an upstream stable kernel. Once that has happened, the
Debian kernel team will usually be open to taking it (on request)
for the next point release.
Cheers,
Andy
--
https://bitfolk.com/ -- No-nonsense VPS hosting
