On 11. 07. 21, 21:50, Larry Finger wrote:
In the case of 5.13, the strange thing is that my
home-built kernel does
not show the problem, thus I was not aware that this calamity was
pending. I am looking at the differences between my configuration and
that of openSUSE to see if that explains the difference in behavior.
Hi, have you considered kernel-obs-qa to check vbox against Kernel:HEAD?
I don't know if the error you are writing about is a build or runtime
one. But the former can be caught by building vbox against Kernel:HEAD
(I assume you do so already.) The latter by doing an insmod in
kernel-obs-qa against Kernel:HEAD.
course, it is possible that openSUSE makes some patch to their system
that causes the breakage. If that is the case, then neither I nor Oracle
will be able to fix it!!
We can fix this. However I believe we diverge from upstream in no