Bug #2089
closedFatal trap 9: GPF in kernel mode
0%
Description
dfly-x86_64-2.10.1_REL.iso:
Running on proxmox 1.8 (linux kvm style VM)
tryroot cd0
cd9660: RockRidge Extension
Fatal trap 9: general protection fault while in kernel mode
instruction pointer = 0x8:0xfff...80701772
stack pointer = 0x10:0xfff...e001716bf0
frame pointer = 0x10:0xfff...e00c39eaf0
...
Stopped at cpu_heavy_restore+0x32: movq 0x320(%rdx),%rdi
Trace shows:
cpu_heavy_restore()
tsleep()
vm_pageout_thread() at vm_pageout_thread+0x221
Registers show:
can't get rdx... scrolls off screen, and cant seem to get backscroll
working.
Updated by weingart over 13 years ago
dfly x86_64 LATEST on 20110613 simply hangs during IDE/ATA detection:
atapci0: Reserved 0x8 bytes for rid 0x10 type 4 at 0x1f0
atapci0: Reserved 0x1 bytes for rid 0x14 type 4 at 0x3f6
ata0: reset tp1 mask=03 ostat0=50 ostat1=00
ata0: stat0=0x50 err=0x01 lsb=0x00 msb=0x00
ata0: stat1=0x00 err=0x00 lsb=0xff msg=0xff
ata0: reset tp2 stat0=50 stat1=00 devices=0x1<ATA_MASTER>
<HANG HERE>
Updated by tuxillo over 12 years ago
- Assignee deleted (
0)
Tobias,
Is your KVM host an Intel Processor? Which one?
I'm unable to boot DFly x64 using KVM on Intel CPUs.
DMA space used: 144k, remaining available: 16384k
Fatal trap 9: general protection fault while in kernel mode
cpuid = 0; lapic->id = 00000000
instruction pointer = 0x8:0xffffffff80797aa2
stack pointer = 0x10:0xffffffe00e4bbc00
frame pointer = 0x10:0xffffffe021c6fbd0
code segment = base 0x0, limit 0xfffff, type 0x1b
= DPL 0, pres 1, long 0, def32 0, gran 1
processor eflags = interrupt enabled, IOPL = 0
current process = 1
current thread = pri 10 (CRIT)
kernel: type 9 trap, code=0
CPU0 stopping CPUs: 0x00000000
stopped
Stopped at cpu_heavy_restore+0x72: movl %ecx,%cr3
db> trace
cpu_heavy_restore() at cpu_heavy_restore+0x72 0xffffffff80797aa2
tsleep() at tsleep+0x54e 0xffffffff804f2f2b
constty_daemon() at constty_daemon+0xb5 0xffffffff80505978
Cheers,
Antonio Huete
Updated by swildner over 11 years ago
- Status changed from New to Closed
Closing, it was fixed recently.