kern/70931: panic: page fault at end of boot on Athlon 64 / Asus K8V
Karl L. Swartz
karl at kls2.com
Wed Aug 25 00:40:29 PDT 2004
>Number: 70931
>Category: kern
>Synopsis: panic: page fault at end of boot on Athlon 64 / Asus K8V
>Confidential: no
>Severity: critical
>Priority: high
>Responsible: freebsd-bugs
>State: open
>Quarter:
>Keywords:
>Date-Required:
>Class: sw-bug
>Submitter-Id: current-users
>Arrival-Date: Wed Aug 25 07:40:27 GMT 2004
>Closed-Date:
>Last-Modified:
>Originator: Karl L. Swartz
>Release: 4.10-RELEASE
>Organization:
>Environment:
unable
>Description:
I'm trying to install FreeBSD 4.10 in a new machine which has an Asus K8V motherboard with an AMD Athlon 64 2800+ CPU and 1GB of PC3200 ECC memory. Storage is a pair of Seagate ST-3200822A 200GB UATA-100 disks in a mirror group on a 3Ware Escalade 7006-2 RAID controller.
Booting either from the FreeBSD Mall CD or floppies I get
Mounting root from ufs:/dev/md0c
/stand/sysinstall running as init on vty0
panic: page fault
Attempts with 4.9 and 5.2.1 both fail in the same way at approximately
the same location in the boot sequence.
I then temporarily installed an older motherboard and CPU and installed
FreeBSD 4.10-RELEASE. After switching back to the K8V / Athlon 64 and
booting from the mirror set I again get a panic at approximately the
same location, albeit with more information:
Mounting root from ufs:/dev/twed0s1a
Fatal trap 12: page fault whle in kernel mode
fault virtual address = 0x4832870
fault code = supervisor write, page not present
instruction pointer = 0x8:0xc03ac086
stack pointer = 0x10:0xc043bdf0
frame pointer = 0x10:0xc043bdf8
code segment = base 0x0, limit 0xfffff, type 0x1b
= DPL 0, pres 1, def32 1, gran 1
processor eflags = interrupt enabled, resume, IOPL = 0
current process = idle
interrupt mask = net tty bio cam
trap number = 12
panic: page fault
syncing disks... 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1
giving up on 1 buffers
Uptime: 14s
twe0: Cannot delete unit, error = 16
A reset resulted in another failed boot with the only significant
difference being the fault virtual address, 0x45f27e0 the second time.
The other trace information was identical.
>How-To-Repeat:
attempt to boot
>Fix:
none known
>Release-Note:
>Audit-Trail:
>Unformatted:
More information about the freebsd-bugs
mailing list