vboxdrv unable to handle kernel paging request when AMD Cool N Quiet disabled

[John]

I cannot attach a VBox.log because this is happening via the vboxdrv kernel module.

If I have AMD Cool N Quiet enabled in the bios, vboxdrv is able to load and I can run VMs. The second I disable it, I get the following:

[  406.309786] vboxdrv: Found 8 processor cores.
[  406.309956] BUG: unable to handle kernel paging request at ffffffffa02702d0
[  406.309960] IP: [<ffffffff81080968>] raw_notifier_chain_register+0x18/0x40
[  406.309965] PGD 1a05067 PUD 1a09063 PMD 22e7d6067 PTE 0
[  406.309969] Oops: 0000 [#1] PREEMPT SMP 
[  406.309971] last sysfs file: /sys/devices/virtual/misc/vboxdrv/uevent
[  406.309974] CPU 4 
[  406.309974] Modules linked in: vboxdrv(+) snd_pcm_oss snd_mixer_oss snd_seq edd fuse md5 nls_utf8 cifs af_packet uinput mperf it87 hwmon_vid dm_crypt loop nvidia(P) hdj_mod uvcvideo videodev v4l1_compat v4l2_compat_ioctl32 snd_usb_audio snd_usbmidi_lib snd_rawmidi joydev snd_hda_codec_realtek snd_seq_device snd_hda_intel snd_hda_codec snd_hwdep snd_pcm snd_timer sr_mod cdrom snd firewire_ohci firewire_core soundcore r8169 crc_itu_t sg xhci_hcd snd_page_alloc pcspkr i2c_piix4 shpchp pci_hotplug eeepc_wmi serio_raw sparse_keymap wmi button ext4 jbd2 crc16 dm_snapshot dm_mod fan processor thermal thermal_sys ata_generic pata_atiixp [last unloaded: preloadtrace]
[  406.310018] 
[  406.310021] Pid: 11487, comm: modprobe Tainted: P            2.6.37.6-0.9-desktop #1 To be filled by O.E.M. To be filled by O.E.M./M5A99X EVO
[  406.310029] RIP: 0010:[<ffffffff81080968>]  [<ffffffff81080968>] raw_notifier_chain_register+0x18/0x40
[  406.310037] RSP: 0018:ffff880229931ed0  EFLAGS: 00010286
[  406.310040] RAX: ffffffffa02702c0 RBX: ffffffffa0583e60 RCX: ffff8801e258fc10
[  406.310044] RDX: 0000000000000000 RSI: ffffffffa0583e60 RDI: ffffffffa0029198
[  406.310048] RBP: 0000000000000000 R08: 0000000000000000 R09: 0000000000000001
[  406.310051] R10: 0000000000012640 R11: 0000000000000000 R12: ffffffffa059e000
[  406.310055] R13: 0000000000612d70 R14: 0000000000000000 R15: 0000000000406750
[  406.310059] FS:  00007fe860272700(0000) GS:ffff8800bcf00000(0000) knlGS:00000000f679c760
[  406.310063] CS:  0010 DS: 0000 ES: 0000 CR0: 000000008005003b
[  406.310066] CR2: ffffffffa02702d0 CR3: 00000001d9341000 CR4: 00000000000406e0
[  406.310070] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
[  406.310074] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
[  406.310078] Process modprobe (pid: 11487, threadinfo ffff880229930000, task ffff88022d280400)
[  406.310081] Stack:
[  406.310084]  ffffffff8150f9f8 0000000000000000 ffffffffa03e01ac 0000000000000000
[  406.310090]  ffffffffa03dda98 0000000000000000 ffffffffa03dc3e7 0000000000000008
[  406.310094]  ffffffffa0584540 0000000000000000 ffffffffa059e044 ffffffffa0584540
[  406.310098] Call Trace:
[  406.310107]  [<ffffffff8150f9f8>] register_cpu_notifier+0x18/0x30
[  406.310121]  [<ffffffffa03e01ac>] rtR0MpNotificationNativeInit+0x3c/0x60 [vboxdrv]
[  406.310148]  [<ffffffffa03dda98>] rtR0MpNotificationInit+0x18/0x40 [vboxdrv]
[  406.310167]  [<ffffffffa03dc3e7>] VBoxHost_RTR0Init+0x37/0x80 [vboxdrv]
[  406.310185]  [<ffffffffa059e044>] VBoxDrvLinuxInit+0x44/0x110 [vboxdrv]
[  406.310191]  [<ffffffff810002da>] do_one_initcall+0x3a/0x170
[  406.310197]  [<ffffffff810976ca>] sys_init_module+0xba/0x210
[  406.310204]  [<ffffffff81002f8b>] system_call_fastpath+0x16/0x1b
[  406.310210]  [<00007fe85fbd7d1a>] 0x7fe85fbd7d1a
[  406.310212] Code: 00 48 8b 74 24 08 89 c5 eb d1 90 90 90 90 90 90 90 90 90 48 8b 07 48 85 c0 74 22 8b 56 10 3b 50 10 7e 0d eb 18 66 0f 1f 44 00 00 <39> 50 10 7c 0d 48 8d 78 08 48 8b 40 08 48 85 c0 75 ee 48 89 46 
[  406.310231] RIP  [<ffffffff81080968>] raw_notifier_chain_register+0x18/0x40
[  406.310235]  RSP <ffff880229931ed0>
[  406.310236] CR2: ffffffffa02702d0
[  406.310239] ---[ end trace e8a8ff27b7232109 ]---

To make a long story short, I've tried both the version that ships with OpenSuSE, 4.0.14, the latest from Oracle, 4.1.6, and both plain OSE and PUEL. I've also tried using the prepackaged kernel modules for 4.0.14, and building my own with 4.1.6. No matter what I do, I cannot get vboxdrv to load without enabling the cool n quiet feature. I always get a general protection fault of type preempt smp from vboxdrv.

I've scoured the internet and these forums for the past few days and it looks like I am doing everything correctly to build the modules. I did come across this however: ​https://forums.virtualbox.org/viewtopic.php?f=7&t=45948&p=207341#p207341 So it seems that I am not the only one with this issue. I can literally leave everything in the bios the same and just change the cool n quiet option, and that makes the difference between vboxdrv giving me a gpf and running fine.

Please let me know if you need more information. I will be happy to provide it.