Bug 148002

Summary:	[boot] panic / page fault while booting from install dvd on asrock 939-dual sata
Product:	Base System	Reporter:	Mike <dura-zell>
Component:	amd64	Assignee:	freebsd-amd64 (Nobody) <amd64>
Status:	Closed FIXED
Severity:	Affects Only Me
Priority:	Normal
Version:	Unspecified
Hardware:	Any
OS:	Any

Description Mike 2010-06-20 00:50:01 UTC

I downloaded the dvd from one of the ftp mirrors, burned it and tried to boot from it. Right after harddisk detection the kernel panics like this:

fatal trap 12: page fault while in kernel mode
cpuid = 0; apic id = 00
fault = virtual address         = 0x0
fault code = supervisor read, page not present
instruction pointer             = 0x20:0x0
stack pointer                   = 0x28:0xe5b64b68
frame pointer                   = 0x28:0xe5b64b9c
code segment                    = base rx0, limit 0xfffff, type 0x1b
                                = DPL 0, pres 1, def32 1, gran 1
processor iflags                = interrupt enabled, resume, IOPL = 0
current process                 = 4 (g_down)
trap number                     = 12
panic: page fault
cpuid = 0
Uptime: 2s

Hardware: 
Mainboard: ASRock 939Dual-SATA2
CPU: AMD Athlon 64 (2GHz)
RAM: 2GBytes DDR400
Video Card: nVida Gefroce 7300GS
HDD: 2 Sata150 Disks, connected to the SATA connectors on the board. SATA2 is disabled.

Tried to deactivate ACPI, set kern.smp.disabled from loaderprompt, both didn't help. 
Tried to boot i386 dvd instead of i386-64: didn't work either with the same panic. 
Tried FreeBSD 7.2/i386: booted cleanly, was able to install.

How-To-Repeat: Get this very hardware, try to boot with FreeBSD 8.0 => crash

Comment 1 John Baldwin freebsd_committer

2010-06-21 13:06:14 UTC

Can you install 7.2, then build an 8.0 kernel with DDB enabled and get a stack 
trace of the crash?

-- 
John Baldwin

Comment 2 Mark Linimon freebsd_committer

2010-06-21 23:20:11 UTC

State Changed
From-To: open->feedback

Note that feedback was requested.

Comment 3 Jaakko Heinonen freebsd_committer

2010-09-02 16:05:01 UTC

State Changed
From-To: feedback->closed

Feedback timeout.

Comment 4 Andriy Gapon 2010-09-02 17:40:49 UTC

Just would like to add that given that the panic happens in g_down process, it is
likely that it has to do either with disk hardware or disk partitioning.
Without additional debugging info it's impossible to tell, so the PR should stay
closed.

-- 
Andriy Gapon