#887 closed defect (invalid)

Install crash of FN 8.0.1 RELEASE i386

Reported by: Blotter Owned by:
Priority: critical Milestone: 8.2.0-RELEASE
Component: FreeBSD Version: 8.0.1-RELEASE
Keywords: Trap 12 install kernel panic Cc:

Description

I am attempting to install a new FreeNAS server and the kernel panics immediately after the FreenNAS menu page. (The screen that gives the options of default, boot with apci disabled, Safe Mode, Single user mode, etc.

After you select an option you see the BSD kernel start up. I have tried each one and they all throw a Fatal trap 12: page fault while in kernel mode, except for the option to drop to the command line.

The versions I have tried are 8.0RC5, 8.0.1 RC1 and RC2 and 8.0.1-RELEASE.

The hardware is as follows.
motherboard: ZOTAC H55-ITX-CE
CPU: Core i3-550
RAM: 4GB Crucial DDRIII 1333
Hard disks: 6x Western Digital 400GB SATA
image files I have used to try and build:
FreeNAS-8.0-RC5-i386.iso
FreeNAS-8.0.1-RC1-i386.iso
FreeNAS-8.0.1-RC2-i386.iso
FreeNAS-8.0.1-RELEASE-i386.iso

Attached is a screen dump of the panic.

Please advise on what is causing this and how I can correct it. I have tried numerous BIOS settings etc, but I always get the panic immediately after BSD starts loading after the 'Welcome to FreeNAS!" screen during initial install.

This is not an upgrade, it is a new install.

Attachments (4)

Kernel Panic FreeNAS.jpg (147.5 KB) - added by Blotter 20 months ago.
screen shot of installer panic
IMG_0043.jpg (161.8 KB) - added by Blotter 20 months ago.
screen capture
IMG_0045.jpg (163.8 KB) - added by Blotter 20 months ago.
screen capture
IMG_0046.jpg (194.1 KB) - added by Blotter 20 months ago.
screen capture

Download all attachments as: .zip

Change History (11)

Changed 20 months ago by Blotter

screen shot of installer panic

comment:1 Changed 20 months ago by dwhite

Wow, haven't seen a crash like that there since the 386.

First blush is that your problem is probably a BIOS bug. About then is where the memory map scan & walk happens and crashes there are unheard of unless SMAP data is wrong, short of a serious hardware problem.

Try updating BIOS to latest and boot the system again. If that doesn't work, we'd like to get the output of a verbose boot to try and figure out what precisely the BIOS is doing wrong or if there is rampant memory corruption going on.

comment:2 Changed 20 months ago by protosd

If you're using a Core i3-550, why are you using the i386 installation files? I know this is confusing for a lot of people, but have you tried the AMD64 installation files?

comment:3 Changed 20 months ago by Blotter

I didn't use the AMD install since its not an AMD chip. Its a Intel Core i3-550 (3.2GHz dual core)

comment:4 Changed 20 months ago by protosd

Yes, I understand that is confusing, I had the same thought when I first started using FreeNAS. There's an explaination in the FAQ in the forums. Question #11, http://forums.freenas.org/showthread.php?1351-FAQ-Those-same-questions-that-keep-getting-asked-and-answered-about-FreeNAS&p=5631&viewfull=1#post5631

The AMD64 description stems from the fact that AMD was first to introduce 64bit extensions to the 'old' x86 architecture.

I think it should be changed from AMD64 to x64 to reduce confusion for people.

comment:5 Changed 20 months ago by Blotter

Thanks Protosd. I never realized that. I did try and and with the amd image instad of a kernel panic trap 12, the screen just starts spewing text down the screen as fast as it can. it looks like traceback info or something but hard to tell since it goes by in a blur. It doesnt actually hang, it just sits there vomiting text. :/

@dwhite,

I am attaching a couple more screen shots. one is the same trap but at a different virtual address (but 90+% of them match the first one I sent) as well a a look at smap from the loader console. Hope these are able to help diagnose whats going on.

Thanks

Changed 20 months ago by Blotter

screen capture

Changed 20 months ago by Blotter

screen capture

Changed 20 months ago by Blotter

screen capture

comment:6 Changed 17 months ago by gcooper

Is this still reproducible with 8.0.3-RELEASE ?

comment:7 Changed 14 months ago by william

  • Resolution set to invalid
  • Status changed from new to closed

Closing for lack of feedback

Note: See TracTickets for help on using tickets.