Re: kvm: unable to handle kernel NULL pointer dereference

Tobias Diedrich
2008-06-05T18:29:21Z

Chris Wright wrote:
> Sorry, my math was bad. I gave you 0xffffffff8021d44f + 7 + 0x6f9cba,
> but it should have been 0xffffffff8021d44f - 17 + 0x6f9cba. Which is
> correct (as one would hope, it was a grasp at straws).
>
> Oh, wait. Is this a laptop? Do you suspend/resume? Suspend will free
> svm_data, and on resume, any launching a guest will definitely hit the
> oops you are seeing.

No, this is my desktop, but I hibernate daily and always see below
message.

> Do you ever see this in dmesg?
>
> svm_cpu_init: svm_data is NULL on 0

Yes:
[...]
PM: Creating hibernation image:
PM: Need to copy 126181 pages
PM: Normal pages needed: 126181 + 1024 + 38, available pages: 397721
x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
svm_cpu_init: svm_data is NULL on 0 …