Date: Thu, 31 Oct 2019 02:11:34 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 241604] NFS kernel panic after running iozone on share while idle Message-ID: <bug-241604-227@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D241604 Bug ID: 241604 Summary: NFS kernel panic after running iozone on share while idle Product: Base System Version: 12.0-RELEASE Hardware: amd64 OS: Any Status: New Severity: Affects Only Me Priority: --- Component: kern Assignee: bugs@FreeBSD.org Reporter: e.moe@rcn.com After running and completing the full suite of iozone tests on an NFS share= my client system running 12.0-RELEASE-p2 GENERIC amd64 had a GPF. The NFS ser= ver is FreeNAS 11.2-U6 exporting a basic NFS share. The client system, the sys= tem that panicked, had the share mounted. I ran the full battery of iozone 3.4= 87 tests using the following command: iozone -a -g 32G. All the tests complet= ed in about 16 hours, the system was idle for about 5 hours after the test. I= was able to view the results. I then walked away for about an hour, came back = and the system had rebooted with the following: pid 1573 (tracker-miner-fs), uid 1001: exited on signal 11 Limiting closed port RST response from 277 to 200 packets/sec Limiting closed port RST response from 206 to 200 packets/sec newnfs: server '192.168.1.65' error: fileid changed. fsid 0:0: expected fil= eid 0x4, got 0x2. (BROKEN NFS SERVER OR MIDDLEWARE) kernel trap 9 with interrupts disabled Fatal trap 9: general protection fault while in kernel mode cpuid =3D 0; apic id =3D 00 instruction pointer =3D 0x20:0xffffffff80bb524f stack pointer =3D 0x28:0xfffffe003fe92710 frame pointer =3D 0x28:0xfffffe003fe92780 code segment =3D base 0x0, limit 0xfffff, type 0x1b =3D DPL 0, pres 1, long 1, def32 0, gran 1 processor eflags =3D resume, IOPL =3D 0 current process =3D 11 (idle: cpu0) trap number =3D 9 panic: general protection fault cpuid =3D 0 time =3D 1572482669 KDB: stack backtrace: #0 0xffffffff80be7977 at kdb_backtrace+0x67 #1 0xffffffff80b9b563 at vpanic+0x1a3 #2 0xffffffff80b9b3b3 at panic+0x43 #3 0xffffffff8107496f at trap_fatal+0x35f #4 0xffffffff81073dbd at trap+0x6d #5 0xffffffff8104f315 at calltrap+0x8 #6 0xffffffff811aa358 at handleevents+0x1a8 #7 0xffffffff811aa9c9 at timercb+0xa9 #8 0xffffffff811e8af6 at lapic_handle_timer+0xb6 #9 0xffffffff81050f3e at Xtimerint+0xae #10 0xffffffff811df68f at cpu_idle_acpi+0x3f #11 0xffffffff811df747 at cpu_idle+0xa7 #12 0xffffffff80bcfb25 at sched_idletd+0x515 #13 0xffffffff80b5bf33 at fork_exit+0x83 #14 0xffffffff810502fe at fork_trampoline+0xe Uptime: 39d2h38m52s ---<<BOOT>>--- Copyright (c) 1992-2018 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 12.0-RELEASE-p2 GENERIC amd64 FreeBSD clang version 6.0.1 (tags/RELEASE_601/final 335540) (based on LLVM 6.0.1) The FreeNAS server is fine. It had been up for a day and has no issues --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-241604-227>