From mboxrd@z Thu Jan 1 00:00:00 1970 Date: Fri, 27 Jan 2017 07:21:04 -0800 (PST) From: Ricardo Da Silva To: voidlinux Message-Id: Subject: Issues with kernel hardening updates in Virtualbox MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_Part_740_2074021854.1485530464887" ------=_Part_740_2074021854.1485530464887 Content-Type: multipart/alternative; boundary="----=_Part_741_824728019.1485530464887" ------=_Part_741_824728019.1485530464887 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Hi all When "slub_debug" is enabled in /etc/default/grub (as of https://github.com/voidlinux/void-packages/commit/2686d88dd4e2f793c9351f9e7ccc81099013e60e), a fresh install of Void fails to boot in Virtualbox. It hangs after printing "write protecting the kernel read-only data ...". I don't know enough about what slub_debug does to figure out what's going on, but for now I'm happy to just revert that line in my grub config to get my system working. Any ideas of what's going on? Ricardo ------=_Part_741_824728019.1485530464887 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable
Hi all

When "slub_debug" is e= nabled in /etc/default/grub (as of=C2=A0https://github.com/voidlinux/void-p= ackages/commit/2686d88dd4e2f793c9351f9e7ccc81099013e60e), a fresh install o= f Void fails to boot in Virtualbox.

It hangs after= printing "write protecting the kernel read-only data ...".
=

I don't know enough about what slub_debug does to f= igure out what's going on, but for now I'm happy to just revert tha= t line in my grub config to get my system working.

Any ideas of what's going on?

Ricardo
------=_Part_741_824728019.1485530464887-- ------=_Part_740_2074021854.1485530464887--