6.5.0-25-generic kernel broke due to VirtualBox; don't install

[Jeffrey Walton]

On Fri, Mar 8, 2024 at 5:07 PM Jeffrey Walton <noloader at gmail.com> wrote:
>
> On Fri, Mar 8, 2024 at 4:56 PM Aaron Rainbolt <arraybolt3 at gmail.com> wrote:
> >
> > On 3/8/24 15:18, Jeffrey Walton wrote:
> >
> > On Fri, Mar 8, 2024 at 3:44 PM Aaron Rainbolt <arraybolt3 at gmail.com> wrote:
> >
> > On 3/8/24 13:09, Aaron Rainbolt wrote:
> >
> > On 3/8/24 09:56, Jeffrey Walton wrote:
> >
> > A heads up... Installing the latest HWE kernel, 6.5.0-25-generic,
> > broke due to VirtualBox. Boot hung with the message "Failed to start
> > LSB: VirtualBox Linux kernel module."
> >
> > If you have VirtualBox installed, you should boot to an old kernel,
> > remove the 6.5.0-25 kernel, and block the kernel package with
> > something like `sudo apt-mark hold '*6.5.0-25-generic*'`.
> >
> > Could you report this on Launchpad against the virtualbox package?
> > That way it can get greater visibility. If not, no problem, I'll try
> > to verify the issue and report it when I can.
> >
> > OK, so I did some testing, and I cannot reproduce this issue. I'm able
> > to have Virtualbox and the 6.5.0-25-generic kernel installed at the same
> > time - my physical system boots up just fine, and a Tiny Core Linux VM
> > runs pretty well.
> >
> > Uh oh, one of those.
> >
> > I also have the USB extension pack installed, in case it makes a
> > difference. I_think_ it may be the USB 3.0 one nowadays.
> >
> > Just tried installing that too, no change. System boots fine, Tiny Core Linux VM boots fine (it did freeze during boot once but a reset of the VM fixed that). I guess this is one of those lovely hardware-dependent Heisenbugs...
>
> Ok, thanks.
>
> This weekend I will unblock the the 6.5.0-25 kernel, and add
> initcall_debug to the kernel command line, and try to get some more
> info.

Good news/bad news. The good news is, I can't duplicate the issue
after unholding and installing the 6.5.0-25 kernel.

The bad news is, I can't duplicate the issue so I can't provide any data.

I will report it on the bug so the issue can be closed.

Jeff