Bug 186942 - [zfs] [panic] Fatal trap 12 (seems zfs related)
Summary: [zfs] [panic] Fatal trap 12 (seems zfs related)
Status: Closed Overcome By Events
Alias: None
Product: Base System
Classification: Unclassified
Component: kern (show other bugs)
Version: 10.0-RELEASE
Hardware: Any Any
: Normal Affects Only Me
Assignee: Bugmeister
URL:
Keywords: crash
Depends on:
Blocks:
 
Reported: 2014-02-21 11:00 UTC by evan
Modified: 2025-01-19 06:54 UTC (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description evan 2014-02-21 11:00:00 UTC
Hi

I was deleting a rather large directory and had the kernel crash.

No dump file, but I am running stock binary install.  Pretty sure it's
not hardware related as this server has been in use for over a year.

Any more information required, let me know.

Feb 21 21:43:20 storage kernel: Fatal trap 12: page fault while in kernel mode
Feb 21 21:43:20 storage kernel: cpuid = 1; apic id = 01
Feb 21 21:43:20 storage kernel: fault virtual address   = 0x378
Feb 21 21:43:20 storage kernel: fault code              = supervisor read data, page not present
Feb 21 21:43:20 storage kernel: instruction pointer     = 0x20:0xffffffff808ad831
Feb 21 21:43:20 storage kernel: stack pointer           = 0x28:0xfffffe023a5b1580
Feb 21 21:43:20 storage kernel: frame pointer           = 0x28:0xfffffe023a5b1610
Feb 21 21:43:20 storage kernel: code segment            = base rx0, limit 0xfffff, type 0x1b
Feb 21 21:43:20 storage kernel: = DPL 0, pres 1, long 1, def32 0, gran 1
Feb 21 21:43:20 storage kernel: processor eflags        = interrupt enabled, resume, IOPL = 0
Feb 21 21:43:20 storage kernel: current process         = 89750 (rm)
Feb 21 21:43:20 storage kernel: trap number             = 12
Feb 21 21:43:20 storage kernel: panic: page fault
Feb 21 21:43:20 storage kernel: cpuid = 1
Feb 21 21:43:20 storage kernel: KDB: stack backtrace:
Feb 21 21:43:20 storage kernel: #0 0xffffffff808e7dd0 at kdb_backtrace+0x60
Feb 21 21:43:20 storage kernel: #1 0xffffffff808af8b5 at panic+0x155
Feb 21 21:43:20 storage kernel: #2 0xffffffff80c8e692 at trap_fatal+0x3a2
Feb 21 21:43:20 storage kernel: #3 0xffffffff80c8e969 at trap_pfault+0x2c9
Feb 21 21:43:20 storage kernel: #4 0xffffffff80c8e0f6 at trap+0x5e6
Feb 21 21:43:20 storage kernel: #5 0xffffffff80c75392 at calltrap+0x8
Feb 21 21:43:20 storage kernel: #6 0xffffffff8094883d at bufobj_invalbuf+0x4d
Feb 21 21:43:20 storage kernel: #7 0xffffffff80b18cd4 at vm_object_terminate+0xe4
Feb 21 21:43:20 storage kernel: #8 0xffffffff80b26e4f at vnode_destroy_vobject+0x8f
Feb 21 21:43:20 storage kernel: #9 0xffffffff818a7ede at zfs_freebsd_reclaim+0x1e
Feb 21 21:43:20 storage kernel: #10 0xffffffff80d99878 at VOP_RECLAIM_APV+0x98
Feb 21 21:43:20 storage kernel: #11 0xffffffff8094b17d at vgonel+0x1bd
Feb 21 21:43:20 storage kernel: #12 0xffffffff8094b609 at vrecycle+0x59
Feb 21 21:43:20 storage kernel: #13 0xffffffff818a7ead at zfs_freebsd_inactive+0xd
Feb 21 21:43:20 storage kernel: #14 0xffffffff80d99778 at VOP_INACTIVE_APV+0x98
Feb 21 21:43:20 storage kernel: #15 0xffffffff80949f81 at vinactive+0x101
Feb 21 21:43:20 storage kernel: #16 0xffffffff8094a392 at vputx+0x272

Fix: 

N/A
How-To-Repeat: N/A
Comment 1 Mark Linimon freebsd_committer freebsd_triage 2014-04-16 03:10:49 UTC
Responsible Changed
From-To: freebsd-bugs->freebsd-fs

Over to maintainer(s).
Comment 2 Eitan Adler freebsd_committer freebsd_triage 2017-12-31 08:01:00 UTC
For bugs matching the following criteria:

Status: In Progress Changed: (is less than) 2014-06-01

Reset to default assignee and clear in-progress tags.

Mail being skipped
Comment 3 Mark Linimon freebsd_committer freebsd_triage 2025-01-19 06:54:42 UTC
^Triage: I'm sorry that this PR did not get addressed in a timely fashion.

By now, the version that it was created against is long out of support.
As well, many newer versions of ZFS have been imported.

Please re-open if it is still a problem on a supported version.