Opened 19 years ago
Closed 18 years ago
#171 closed bug (fixed)
[kernel] PANIC: double fault!
Reported by: | diver | Owned by: | axeld |
---|---|---|---|
Priority: | blocker | Milestone: | R1 |
Component: | System/Kernel | Version: | |
Keywords: | Cc: | umccullough@… | |
Blocked By: | Blocking: | ||
Platform: | All |
Description (last modified by )
PANIC: double fault! error code 0x0 screenshot will follow. I've got this only once under vmware with rev16392.
Attachments (3)
Change History (22)
comment:1 by , 19 years ago
op_sys: | All → Haiku |
---|
comment:2 by , 19 years ago
rep_platform: | All → X86 |
---|
comment:3 by , 19 years ago
Summary: | PANIC: double fault:! → PANIC: double fault! |
---|
comment:4 by , 19 years ago
comment:5 by , 19 years ago
Resolution: | → invalid |
---|
comment:6 by , 19 years ago
Thanks for your effort, but that doesn't help at all: it just tells me that our double fault handler is working in VMware. If you don't know how to reproduce this bug, I'll close it now.
comment:7 by , 19 years ago
Status: | new → closed |
---|
comment:8 by , 19 years ago
i'm sorry not to take screenshot in the first place. So here it is. Hope this will help you, Axel!
comment:9 by , 19 years ago
Resolution: | invalid |
---|
comment:10 by , 19 years ago
Status: | closed → reopened |
---|
comment:11 by , 19 years ago
Changing the severity to "blocker" as this problem crashes the whole system.
comment:12 by , 19 years ago
severity: | normal → blocker |
---|
comment:15 by , 19 years ago
comment:16 by , 19 years ago
I seem to get this every time I run VMWare for the first time with a haiku disk image I have created.
If I reboot it after the KDL, it works fine, and I never see it again with that image.
comment:17 by , 19 years ago
Cc: | added |
---|
by , 19 years ago
Attachment: | Haiku_r17355_VMWare_Double_Fault_KDL_on_boot.txt added |
---|
serial log from VMWare session with double fault
comment:18 by , 18 years ago
Summary: | PANIC: double fault! → [kernel] PANIC: double fault! |
---|
comment:19 by , 18 years ago
Description: | modified (diff) |
---|---|
Platform: | → All |
Resolution: | → fixed |
Status: | reopened → closed |
This one should have been fixed by geist in hrev19549.
I could reproduce it occasionally on vmware too.