int_die_halt!
Submitted by Trickkiste on Tue, 06/08/2004 - 12:22.
Hi,
I am no longer able to boot JNode from iso in vmware, I got the following Error :
loadFromBootClassArrayStarting JNode
VmSystem.initialize
00000000 1DC50000
int : 00000005 Error: 00000000 CR2 : 00000000 CR3 : 00001000
EIP : 0036F493 CS : 0000001B FLAGS: 00203217
EAX : FFFFFFFF EBX : 0000FFFF ECX : 023970B8 EDX : FFFFFFFF
EBP : 00118EE4 ESP : 00118EBC EDI : 01BAFB88 ESI : FFFFFFFF
DS : 00000023 ES : 00000023 FS : 00000033 GS : 000000023
Stack: 00000000 00000000 00000000 00000000 00000000 FFFFFFFF
Code : 8A 44 11 04 0F BE C0 89 45 E8 8B 45 10 89 C1 8B Real panic: int_die_halt!
I have tried a clean build and a new checkout. Has anyone an Idea?
Trickkiste
- Login to post comments
See function at EIP address
Have a look at the buildlogs (jnode\all\build\x86\bootimage\bootimage.lst) to find out which function causes this problem. (Conmpare the EIP address)
Also please provide info on the version you're using and the system you're testing it on.
Ewout
the corresponding line
is :
$000000000036f493 Q53org5jnode2vm3x8613MPConfigTable23parse2e2829Ljava2futil2fList3b__bci_52$$cbok (org.jnode.assembler.Label)
so I guess it is in
org.jnode.vm.x86.MPConfigTable.java
and it deals with
private final List parse()
which is called by the constructor :
MPConfigTable(MemoryResource mem) {
this.mem = mem;
this.entries = parse();
}
I use Microsoft Windows XP Professional 5.1.2600, Service Pack 1 on an AMD Athlon XP 1800+ with 1GB RAM and VMware version is 4.0.5 build-6030.
Trickkiste
Humm...
That line indeed corresponds to the indicated class. I'll try to make the multiprocessor detection optional for now. I hope to do that tonight, but I'm not sure i'll make it.
Ewout
it still does not work
Hi,
it still doesn't work under vmware for me.
Is someone able to boot the current dev version of JNode in vmware?
thx,
Trickkiste
Re : not work
Apparently ewout made a fix in the CVS but it not work for me, i have always same error.
windows : XP pro
VMWARE : 4.0.5 - build 6030
Fabien.
hi
here is what ewout mailed me :
Try adding "mp=no" (without the quotes) to the kernel commandline in grub.
This will prevent the MP detection.
Ewout
I use vmware 4.5.1 and it works .
Trickkiste
It works
It works. If it is a definitive fix, perhaps we can add it to the documentation...
Fabien.
what I did..
in addition I tried to change the BIOS settings of the virtual PC concerning multiprozessor things.
I was able to change the Multiprozessor Specification, the choice was between 1.1 and 1.4, but neither nor worked.
Trickkiste