Bug 185734 - [zfs] [panic] panic on stable/10 when writing to ZFS disk
Summary: [zfs] [panic] panic on stable/10 when writing to ZFS disk
Status: Closed FIXED
Alias: None
Product: Base System
Classification: Unclassified
Component: kern (show other bugs)
Version: 10.0-PRERELEASE
Hardware: Any Any
: Normal Affects Only Me
Assignee: freebsd-bugs (Nobody)
URL:
Keywords: crash
Depends on:
Blocks:
 
Reported: 2014-01-13 06:50 UTC by R. Tyler Croy
Modified: 2024-12-17 08:40 UTC (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description R. Tyler Croy 2014-01-13 06:50:00 UTC
Was attempting to pull a big update from the FreeBSD git mirror, which usually downloads large-ish pack files and writes them to disk.

After fetching the object files, and attempting to write them to my encrypted ZFS-based disk, the machine panicked as you can see below.

Jan 12 22:24:43 kiwi dhclient[36674]: send_packet: Network is down
Jan 12 22:25:09 kiwi last message repeated 3 times
Jan 12 22:25:33 kiwi last message repeated 2 times
Jan 12 22:30:55 kiwi syslogd: kernel boot file is /boot/kernel/kernel
Jan 12 22:30:55 kiwi kernel: 
Jan 12 22:30:55 kiwi kernel: 
Jan 12 22:30:55 kiwi kernel: Fatal trap 12: page fault while in kernel mode
Jan 12 22:30:55 kiwi kernel: cpuid = 1; apic id = 01
Jan 12 22:30:55 kiwi kernel: fault virtual address      = 0x34f80125
Jan 12 22:30:55 kiwi kernel: fault code         = supervisor write data, page not present
Jan 12 22:30:55 kiwi kernel: instruction pointer        = 0x20:0xffffffff80685341
Jan 12 22:30:55 kiwi kernel: stack pointer              = 0x28:0xfffffe0234f888e0
Jan 12 22:30:55 kiwi kernel: frame pointer              = 0x28:0xfffffe0234f889b0
Jan 12 22:30:55 kiwi kernel: code segment               = base rx0, limit 0xfffff, type 0x1b
Jan 12 22:30:55 kiwi kernel: = DPL 0, pres 1, long 1, def32 0, gran 1
Jan 12 22:30:55 kiwi kernel: processor eflags   = interrupt enabled, resume, IOPL = 0
Jan 12 22:30:55 kiwi kernel: current process            = 22137 (git)
Jan 12 22:30:55 kiwi kernel: trap number                = 12
Jan 12 22:30:55 kiwi kernel: panic: page fault
Jan 12 22:30:55 kiwi kernel: cpuid = 1
Jan 12 22:30:55 kiwi kernel: KDB: stack backtrace:
Jan 12 22:30:55 kiwi kernel: #0 0xffffffff8066c750 at kdb_backtrace+0x60
Jan 12 22:30:55 kiwi kernel: #1 0xffffffff806341a5 at panic+0x155
Jan 12 22:30:55 kiwi kernel: #2 0xffffffff808cf752 at trap_fatal+0x3a2
Jan 12 22:30:55 kiwi kernel: #3 0xffffffff808cfa29 at trap_pfault+0x2c9
Jan 12 22:30:55 kiwi kernel: #4 0xffffffff808cf1b6 at trap+0x5e6
Jan 12 22:30:55 kiwi kernel: #5 0xffffffff808b6452 at calltrap+0x8
Jan 12 22:30:55 kiwi kernel: #6 0xffffffff8068231a at dofilewrite+0x8a
Jan 12 22:30:55 kiwi kernel: #7 0xffffffff80682045 at kern_writev+0x65
Jan 12 22:30:55 kiwi kernel: #8 0xffffffff80681fd3 at sys_write+0x63
Jan 12 22:30:55 kiwi kernel: #9 0xffffffff808d0047 at amd64_syscall+0x357
Jan 12 22:30:55 kiwi kernel: #10 0xffffffff808b673b at Xfast_syscall+0xfb
Jan 12 22:30:55 kiwi kernel: Uptime: 5d2h27m4s
Jan 12 22:30:55 kiwi kernel: Automatic reboot in 15 seconds - press a key on the console to abort
Jan 12 22:30:55 kiwi kernel: Rebooting...
Jan 12 22:30:55 kiwi kernel: cpu_reset: Restarting BSP
Jan 12 22:30:55 kiwi kernel: cpu_reset_proxy: Stopped CPU 1

How-To-Repeat: Unable to reproduce unfortunately :(
Comment 1 Mark Linimon freebsd_committer freebsd_triage 2014-04-20 02:48:45 UTC
State Changed
From-To: open->open

Over to maintainer(s). 


Comment 2 Mark Linimon freebsd_committer freebsd_triage 2014-04-20 02:48:45 UTC
Responsible Changed
From-To: freebsd-bugs->freebsd-fs
Comment 3 Eitan Adler freebsd_committer freebsd_triage 2017-12-31 08:00:21 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 4 Michael Dexter freebsd_triage 2024-12-17 08:40:31 UTC
Marked as difficult to reproduce and several encryption-related issues have been addressed. Please re-open the PR if the issue continues.