grsecurity forums

Hello,

Using the above patch, I get a general protection fault when booting a VirtualBox 4.3.4 Slackware
Linux system. grsecurity-3.0-3.12.1-201311261522.patch also gets a GFP during boot. Both of
these patches boots successfully outside VirtualBox.

The last patch that boots successfully within VirtualBox is grsecurity-3.0-3.11.9-201311242034.patch.

My config, kernel, and a png screenshot of grsecurity-3.0-3.12.2-201312032145.patch are available here:

https://home.comcast.net/~x14sg1/config
https://home.comcast.net/~x14sg1/vmlinuz
https://home.comcast.net/~x14sg1/GPF.png

Thanks,

Tim

did you have CONFIG_X86_INTEL_PSTATE enabled in 3.11 as well? can you try vanilla 3.12 with that enabled?

Thanks for the reply

CONFIG_X86_INTEL_PSTATE is in the config for grsecurity-3.0-3.11.9-201311242034.patch and it
does boot.

Vanilla 3.12.3 gets a slightly different GFP so it looks like it is a kernel issue and I put a screenshot
of it here:

https://home.comcast.net/~x14sg1/GPF2.png

I apologize for not trying a Vanilla kernel before sending in this report.

Thanks for looking at it.

Tim

it's the same rdmsrl(MSR_NHM_TURBO_RATIO_LIMIT, value) in intel_pstate_turbo_pstate in both cases that fails. my guess is that since this code is the same in 3.11, it probably didn't at all get called there. in any case, please let upstream know and figure this out.

Thanks - will do

BTW: Disabling CONFIG_X86_INTEL_PSTATE allows me to boot grsec and vanilla 3.12.2

Update:

CONFIG_X86_INTEL_PSTATE=y now works with linux kernel 3.12.6 and VirtualBox 4.3.6.

I do not know in which kernel version it was fixed.