Aurelien Jarno wrote:
> Hi,
>
> I have just updated my system from kvm 28 to kvm 29, and a GNU/kFreeBSD
> amd64 system fails to boot with the following error:
>
>   Fatal trap 12 with interrupts disabled
>
>
>   Fatal trap 12: page fault while in kernel mode
>   fault virtual address   = 0x7aa93e0
>   fault code              = supervisor read, page not present
>   instruction pointer     = 0x8:0xffffffff80598b36
>   stack pointer           = 0x10:0xffffffff87c556b0
>   frame pointer           = 0x10:0xffffff0007aa9260
>   code segment            = base 0x00, lmit 0xfffff, type 0x1b
>                           = DPL 0, pres 1, long 1, def32 0, gran 1
>   processor eflags        = resume, IOPL = 0
>   current process         = 1 (init)
>   trap number             = 12
>   panic: page fault
>
>
> This is on an machine with an Athlon64 X2 CPU.
>
> As it was running fine with kvm 28, I tried to mix kvm 28 and kvm 29. It
> fails when using modules from kvm 29, whatever the version of the
> userland part. This looks like a problem in the kernel modules.
>
> Please also note that GNU/kFreeBSD i386 is working fine with kvm 29 on
> the same machine.
>
> Please tell me what I can do to help debugging this problem. 
> Alternatively I have uploaded an image to reproduce the problem here:
> http://temp.aurel32.net/kfreebsd-amd64.img.g

I've downloaded the image and booted it three times using kvm HEAD. 
Each time I got to the login prompt.

Is this always reproducible?  Can you check with kvm HEAD (not that I
think of anything that could have fixed this).


-- 
Do not meddle in the internals of kernels, for they are subtle and quick to 
panic.


-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
kvm-devel mailing list
kvm-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/kvm-devel

Reply via email to