misc/125759: Fatal Trap 12 when ICH9R RAID becomes degraded

Tamouh hakmi at rogers.com
Fri Jul 18 19:50:04 UTC 2008


>Number:         125759
>Category:       misc
>Synopsis:       Fatal Trap 12 when ICH9R RAID becomes degraded
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    freebsd-bugs
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Fri Jul 18 19:50:04 UTC 2008
>Closed-Date:
>Last-Modified:
>Originator:     Tamouh
>Release:        6.3
>Organization:
>Environment:
FreeBSD concord.smallvillages.com 6.3-RELEASE FreeBSD 6.3-RELEASE #0: Wed Jul  2 06:58:36 EDT 2008     root at host.servername.com:/usr/obj/usr/src/sys/SMP  i386

>Description:
We've seen this problem on FBSD 6.3, other online discussions show the problem is present in 6.1-R and even 7.x.

The problem occurs when using the noboard RAID function of some motherboards such as ICH9R in a mirrored RAID-1.

If you pull one of the drives out (or disconnect one), and reboot the system, the FreeBSD will fail to boot immediately after it detects one of the drives.

Attempts to boot into safe mode, single mode and anything but Prompt mode will fail. The only option is to reinstall the OS or replace the disk and rebuild in the RAID BIOS before loading FreeBSD.

The following error will be displayed on the screen during the boot process:

  Fatal trap 12: page fault while in kernel mode  fault virtual address   = 0xf4c3b8d8  fault code              = supervisor read, page not present  instruction pointer     = 0x20:0xc083fa56  stack pointer           = 0x28:0xc0c20bfc  frame pointer           = 0x28:0xc0c20c40  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         = 0 (swapper)  trap number             = 12
>How-To-Repeat:
Install FreeBSD on ICH9R RAID or similar in RAID-1. Turn off the system, unplug one of the drives, and boot the system back. The system will fail to boot.

Additional submissions about the same problem:

http://www.mavetju.org/mail/view_thread.php?list=freebsd-bugs&id=2294159&thread=yes

http://groups.google.com/group/lucky.freebsd.questions/browse_thread/thread/ec8b2dd903fba0d8
>Fix:


>Release-Note:
>Audit-Trail:
>Unformatted:


More information about the freebsd-bugs mailing list