Bug 194489 - Fatal trap 12: page fault while in kernel mode, when accessing rocketraid 1740/hptrr
Summary: Fatal trap 12: page fault while in kernel mode, when accessing rocketraid 174...
Status: New
Alias: None
Product: Base System
Classification: Unclassified
Component: kern (show other bugs)
Version: 10.0-RELEASE
Hardware: amd64 Any
: --- Affects Only Me
Assignee: freebsd-bugs mailing list
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-10-20 16:01 UTC by bc
Modified: 2014-10-21 08:49 UTC (History)
0 users

See Also:


Attachments
crash data (112.17 KB, text/plain)
2014-10-20 16:01 UTC, bc
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description bc 2014-10-20 16:01:38 UTC
Created attachment 148506 [details]
crash data

I have a rocketraid 1740, bios 1.01, raid 5, 4x1Tbps, connected to a 10.0 system and consistently when running fsck on the raid, when fsck completes, and is about to mark the filesystem as clean I get Fatal trap 12. Repeatable.
Which means I can't mount it.. It worked fine previously on a 8.4 system.

Fatal trap 12: page fault while in kernel mode
cpuid = 0; apic id = 00
fault virtual address   = 0x0
fault code              = supervisor read instruction, page not present
instruction pointer     = 0x20:0x0
stack pointer           = 0x28:0xfffffe0096aa5a40
frame pointer           = 0x28:0x0
code segment            = base rx0, limit 0xfffff, type 0x1b
                        = DPL 0, pres 1, long 1, def32 0, gran 1
processor eflags        = interrupt enabled, resume, IOPL = 0
current process         = 12 (irq20: hptrr0)
trap number             = 12
panic: page fault
cpuid = 0
KDB: stack backtrace:
#0 0xffffffff808e7e90 at kdb_backtrace+0x60
#1 0xffffffff808af975 at panic+0x155
#2 0xffffffff80c8e822 at trap_fatal+0x3a2
#3 0xffffffff80c8eaf9 at trap_pfault+0x2c9
#4 0xffffffff80c8e286 at trap+0x5e6
#5 0xffffffff80c75522 at calltrap+0x8
Uptime: 57m31s
Dumping 328 out of 2024 MB:..5%..15%..25%..35%..44%..54%..64%..74%..83%..93%
Also dump if needed.
Comment 1 bc 2014-10-21 08:49:03 UTC
The problem went away after applying revision 267368 from head to the driver.
I can now fsck/mount the raid and everything seems to be working. The probe errors are gone as well.