Fatal trap 12 page fault while in vm86 mode

[ThePowerTool]

I've been running FreeNAS for a fairly long time. Recently I came across some new hardware (new drives, new controller) which made me undertake the task of upgrading my FreeNAS server. I was on .68b--I know this because I still have the FreeNAS-0.68.iso image.

I'm running an IBM IntelliStation M-Pro Model 6850-66u with a Xeon 2.4 (32b) and 3.5G RAM I can provide more details on specifications, if necessary. It is running the latest BIOS available for the system.

I jumped feet-first into FreeNAS 8, got it installed and then discovered 1) my system isn't quite "beefy" enough for 8 and 2) a complete lack of support for RAID5. After reading through the documentation I determined that while I could "get by" on 8 with UFS the better route for my system would be NAS4Free. Please keep in mind that I have 8 running on my server and everything was working fine except it wouldn't see my RAID5 array--which is an entirely separate question because it still seems to build on boot.

I downloaded the correct ISO to install 9.1.0.1.690 (specifically NAS4Free-x86-LiveCD-9.1.0.1.690.iso) and burned it to a CD. When I boot the CD it goes through a significant portion of the boot and I get the text menu (about starting in "Normal" mode or "Safe") and then shortly after that menu I see the error:

Code: Select all

Fatal trap 12: page fault while in vm86 mode
cpuid=0; apic id=00
fault virtual address = 0x7c00
fault code            = user read, page not presnt
instruction pointer   = 0xc000:0x69d
stack pointer         = 0x0:0xff4
frame pointer         = 0x0:0x0
code segment          = base 0x0, limit 0x0, type....

processor eflags      = interrupt enabled, resume, ....
current process       = 0 (swapper)
trap number           = 12
panic: page fault
cpuid = 0
KDB: stack backtrace:
#0 0x80bc974f at kdb_backtrace+0x4f
#1 0x80b9617f at panic+0x16f
#2 0x80f2c323 at trap_fatal+0x323
#3 0x80f2c397 at trap_pfault+0x67
#4 0x80f2d38a at trap+0x44a
#5 0x80f1697c at calltrap+0x6
uptime: 1s

I am still running my server on 8 (specifically 8.3.1 rP2_x386) but would like to know if I can run on NAS4Free since it seems to be the better option for my HW.

One additional concern--I have been researching my new controller. I/O Flex Silicon Image SIL3124-2. It seems 3124-2 is the chipset (I'm no expert I'm just stating what I believe based upon my research) and it says this controller supports RAID. My reading indicates that this controller (chipset) is supported in FreeNAS starting with 8 (both with generic drivers and specific drivers) but it seems there's some question as to whether or not it is fully supported in NAS4Free--I'd be grateful for some clarification on this, as well.

I would greatly appreciate troubleshooting assistance. Thanks, in-advance!

[raulfg3]

not sure, I find at least 3 pages with about 3 faults:

memory: http://forums.freebsd.org/showthread.php?t=9608
nfe=NIC: http://forums.freebsd.org/showthread.php?t=34150
Bad motherboard: http://forums.freebsd.org/showthread.php?t=26710


You need to pass some test to identify correct answer.

[ThePowerTool]

not sure, I find at least 3 pages with about 3 faults:

I'm not expert but these are trap 12 while in kernel mode rather than vm86 mode which is an 8086 emulation mode specific to 32b processors.

memory: http://forums.freebsd.org/showthread.php?t=9608
nfe=NIC: http://forums.freebsd.org/showthread.php?t=34150
Bad motherboard: http://forums.freebsd.org/showthread.php?t=26710


You need to pass some test to identify correct answer.

These three issues identified here would prevent me from successfully running in FreeNAS--which I am doing right now. I have the system up and running under 8 but the failure I'm seeing is during the inital boot to CD for installation of NAS4Free. I know that I've got a good NIC and mb because I'm using 8. I also know troubleshooting memory issues can be tricky so I will run a memory check to confirm I have good memory. I'm fully expecting the memory to pass but I'll be watching closesly in case this test identifies an easy HW fix.

Thank you very much for your response!