FS#54846 - [virtualbox] 5.1.22-5 blackscreen on boot with linux 4.12.2
Attached to Project:
Community Packages
Opened by tom (archtom) - Monday, 17 July 2017, 09:43 GMT
Last edited by Eli Schwartz (eschwartz) - Tuesday, 18 July 2017, 14:07 GMT
Opened by tom (archtom) - Monday, 17 July 2017, 09:43 GMT
Last edited by Eli Schwartz (eschwartz) - Tuesday, 18 July 2017, 14:07 GMT
|
Details
I always try updates in a virtualbox before applying them on
the server, after updating from 4.12.e-1 (which was fine) to
4.12.2.a-1 the system hangs completely and shows a black
screen. I did a complete system update.
The "regular" linux kernel boots properly in its current version 4.11.9-1. I´m sorry I don`t know how to provide more needed information. Just let me know the exact command to issue for getting further details you will probably need. Thanks in advance for fixing. |
This task depends upon
Closed by Eli Schwartz (eschwartz)
Tuesday, 18 July 2017, 14:07 GMT
Reason for closing: Fixed
Additional comments about closing: virtualbox 5.1.24-1
Tuesday, 18 July 2017, 14:07 GMT
Reason for closing: Fixed
Additional comments about closing: virtualbox 5.1.24-1
Bisect the kernel over that range to find the bad commit then report it upstream.
You can also try reverting that one commit on the latest version of linux-hardened to check your other issue.
Edit:
You could start a forum thread if you have issues with the bisection and should this thread be closed against linux-hardened
you could apply to have it reopened against linux preferably when have have located the bad commit and reported it upstream.
linux-hardened and linux-hardened-headers
which worked fine.
Then I suspected the virtualbox stuff to be responsible and tried
pacaur -Syu --ignore virtualbox-guest-dkms --ignore virtualbox-guest-utils
which worked fine, too.
So it seems virtualbox-guest-dkms 5.1.22-4 and virtualbox-guest-utils 5.1.22-4 are working with the latest hardened kernel, and versions virtualbox-guest-dkms 5.1.22-5 and virtualbox-guest-utils 5.1.22-5 are not working.
But they do work with the latest "regular" kernel (4.11 series). Could this be the case that they will work again when the latest regular kernel gets upgraded to the 4.12 series inkl. the referring guest utils? Perhaps that`s why the latest regular kernel in testing had the same issue after upgrading to 4.12 series?
EDIT: There was a virtualbox update 63 minutes ago, does 5.1.24-1 work?
Thanks to everyone for all your help, I think this one can be closed.