[Bug 227784] zfs: Fatal trap 9: general protection fault while in kernel mode on shutdown

[bugzilla-noreply at freebsd.org]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227784

Conor <inextricable.nadir at gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |inextricable.nadir at gmail.co
                   |                            |m

--- Comment #11 from Conor <inextricable.nadir at gmail.com> ---
I've also seen this issue on FreeBSD 11.2-RELEASE-p2, not CURRENT in somewhat
reproducible fashion; the panic seems to happen under heavy ZFS load reading
and writing via NFS _eventually_ without fail. The manner which I trigger it
each time is running a bittorrent client which is writing to the NFS share from
another machine. The stack trace is always the same.

Problem Machine:

FreeBSD nas 11.2-RELEASE-p2 FreeBSD 11.2-RELEASE-p2 #0: Tue Aug 14 21:45:40 UTC
2018     root at amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC  amd64


Entry in /var/log/messages on reboot:

Sep  4 23:08:35 nas kernel: Fatal trap 9: general protection fault while in
kernel mode
Sep  4 23:08:35 nas kernel: cpuid = 0; apic id = 00
Sep  4 23:08:35 nas kernel: instruction pointer = 0x20:0xffffffff80f7572e
Sep  4 23:08:35 nas kernel: stack pointer               =
0x28:0xfffffe023273a9b0
Sep  4 23:08:35 nas kernel: frame pointer               =
0x28:0xfffffe023273a9b0
Sep  4 23:08:35 nas kernel: code segment                = base 0x0, limit
0xfffff, type 0x
1b
Sep  4 23:08:35 nas kernel: = DPL 0, pres 1, long 1, def32 0, gran 1
Sep  4 23:08:35 nas kernel: processor eflags    = interrupt enabled, resume,
IOPL = 0
Sep  4 23:08:35 nas kernel: current process             = 0 (zio_read_intr_0_4)
Sep  4 23:08:35 nas kernel: trap number         = 9
Sep  4 23:08:35 nas kernel: panic: general protection fault
Sep  4 23:08:35 nas kernel: cpuid = 0
Sep  4 23:08:35 nas kernel: KDB: stack backtrace:
Sep  4 23:08:35 nas kernel: #0 0xffffffff80b3d567 at kdb_backtrace+0x67
Sep  4 23:08:35 nas kernel: #1 0xffffffff80af6b07 at vpanic+0x177
Sep  4 23:08:35 nas kernel: #2 0xffffffff80af6983 at panic+0x43
Sep  4 23:08:35 nas kernel: #3 0xffffffff80f77fcf at trap_fatal+0x35f
Sep  4 23:08:35 nas kernel: #4 0xffffffff80f7758e at trap+0x5e
Sep  4 23:08:35 nas kernel: #5 0xffffffff80f57dac at calltrap+0x8
Sep  4 23:08:35 nas kernel: #6 0xffffffff8228a6b6 at abd_copy_off+0x156
Sep  4 23:08:35 nas kernel: #7 0xffffffff82307ffa at
vdev_queue_agg_io_done+0x6a
Sep  4 23:08:35 nas kernel: #8 0xffffffff8232ecfe at zio_done+0x90e
Sep  4 23:08:35 nas kernel: #9 0xffffffff8232a74c at zio_execute+0xac
Sep  4 23:08:35 nas kernel: #10 0xffffffff80b4ed74 at
taskqueue_run_locked+0x154
Sep  4 23:08:35 nas kernel: #11 0xffffffff80b4fed8 at
taskqueue_thread_loop+0x98
Sep  4 23:08:35 nas kernel: #12 0xffffffff80aba083 at fork_exit+0x83

zpool status:
root at nas:/var/log # zpool status
  pool: zroot
 state: ONLINE
  scan: scrub repaired 24K in 0h7m with 0 errors on Tue Sep  4 23:21:17 2018
config:

        NAME        STATE     READ WRITE CKSUM
        zroot       ONLINE       0     0     0
          raidz3-0  ONLINE       0     0     0
            ada0p3  ONLINE       0     0     0
            ada1p3  ONLINE       0     0     0
            ada2p3  ONLINE       0     0     0
            ada3p3  ONLINE       0     0     0
            ada4p3  ONLINE       0     0     0
            ada5p3  ONLINE       0     0     0
            ada6p3  ONLINE       0     0     0
            ada7p3  ONLINE       0     0     0

errors: No known data errors

I can collect a crash dump if it will be useful.

-- 
You are receiving this mail because:
You are the assignee for the bug.