JNode fails to boot on an AL440LX mobo wit
Project: | JNode Core |
Component: | Code |
Category: | bug report |
Priority: | normal |
Assigned: | Unassigned |
Status: | closed |
Jump to:
JNode fails to boot on an AL440LX mobo with a Celeron 2 processor upgrade.
Processor upgrade: PowerLeap PL-iP3
CPU: Celeron II 766MHz
Package: Socket 370 FC-PGA
Features: MMX, SSE
Core stepping: cC0
Family/Model/Stepping: 06/08/06
RAM: 256MB
Installed operating system: Windows 98
Notes: BIOS incorrectly reports processor as a Pentium Pro
Visible screen dump as follows:
. org.jnode.vm.compiler.NativeCodeCompiler::compileRuntime
. org.jnode.vm.VmSystemClassLoader::compileRuntime
. org.jnode.vm.classmgr.VmMethod::doCompile
...Suspend with invalid tsi: 00000001 Debug stacktrace: org.jnode.vm.VmStackReader::debugStackTrace
. org.jnode.vm.VmProcessor::suspend
. org.jnode.vm.Monitor::wait
. org.jnode.vm.memmgr.def.GCThread::trigger
. org.jnode.vm.memmgr.def.DefaultHeapManager::allocObject
. org.jnode.vm.memmgr.VmHeapManager::newArray0
. org.jnode.vm.memmgr.VmHeapManager::newArray
. org.jnode.vm.SoftByteCodes::allocPrimitiveArray
. java.lang.StringBuilder::ensureCapacity
. java.lang.StringBuilder::append
. org.jnode.vm.x86.compiler.X86CompilerHelper::getInstrLabel
. org.jnode.vm.x86.compiler.l1a.X86BytecodeVisitor::startInstruction
. org.jnode.vm.compiler.DelegatingCompilerBytecodeVisitor::startInstruction
. org.jnode.vm.bytecode.BytecodeParser::fireStartInstruction
. org.jnode.vm.compiler.CompilerBytecodeParser::fireStartInstruction
. org.jnode.vm.bytecode.BytecodeParser::parse
. org.jnode.vm.compiler.NativeCodeCompiler::doCompile
. org.jnode.vm.compiler.NativeCodeCompiler::compileRuntime
. org.jnode.vm.VmSystemClassLoader::compileRuntime
. org.jnode.vm.classmgr.VmMethod::doCompile
...Real panic: reschedule
Last thing that flashed on the screen before that was:
VmSystem.initialize
then something that looked like <gc>
- Login to post comments
#1
From what I can see this seems to be a memory/gc related issue. This might be fixed. Also remember that 256MB is not much memory, one should use definitly more than 256MB. Closing this, reopen if problem remains.
#2
Automatically closed -- issue fixed for two weeks with no activity.