Date: Sun, 22 Feb 2015 22:00:38 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 197934] Kernel panic when creating backup with tar Message-ID: <bug-197934-8@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=197934 Bug ID: 197934 Summary: Kernel panic when creating backup with tar Product: Base System Version: 10.1-RELEASE Hardware: amd64 OS: Any Status: New Severity: Affects Only Me Priority: --- Component: kern Assignee: freebsd-bugs@FreeBSD.org Reporter: pvoigt@uos.de A few days ago I had a kernel panic when doing a backup of my home partition. The resulting tar file is about 16 GiB. The following lines are the corresponding lines from my rsyslog: Feb 18 23:23:15 spock kernel: kernel trap 12 with interrupts disabled Feb 18 23:23:15 spock kernel: Feb 18 23:23:15 spock kernel: Feb 18 23:23:15 spock kernel: Fatal trap 12: page fault while in kernel mode Feb 18 23:23:15 spock kernel: cpuid = 2; apic id = 02 Feb 18 23:23:15 spock kernel: fault virtual address = 0x20 Feb 18 23:23:15 spock kernel: fault code = supervisor read data, page not present Feb 18 23:23:15 spock kernel: instruction pointer = 0x20:0xffffffff80974c3c Feb 18 23:23:15 spock kernel: stack pointer = 0x28:0xfffffe045c8cc920 Feb 18 23:23:15 spock kernel: frame pointer = 0x28:0xfffffe045c8cc950 Feb 18 23:23:15 spock kernel: code segment = base 0x0, limit 0xfffff, type 0x1b Feb 18 23:23:15 spock kernel: = DPL 0, pres 1, long 1, def32 0, gran 1 Feb 18 23:23:15 spock kernel: processor eflags = resume, IOPL = 0 Feb 18 23:23:15 spock kernel: current process = 72239 (smbiod21) Feb 18 23:23:15 spock kernel: trap number = 12 Feb 18 23:23:15 spock kernel: panic: page fault Feb 18 23:23:15 spock kernel: cpuid = 2 Feb 18 23:23:15 spock kernel: KDB: stack backtrace: Feb 18 23:23:15 spock kernel: #0 0xffffffff80963000 at kdb_backtrace+0x60 Feb 18 23:23:15 spock kernel: #1 0xffffffff80928125 at panic+0x155 Feb 18 23:23:15 spock kernel: #2 0xffffffff80d24f1f at trap_fatal+0x38f Feb 18 23:23:15 spock kernel: #3 0xffffffff80d25238 at trap_pfault+0x308 Feb 18 23:23:15 spock kernel: #4 0xffffffff80d2489a at trap+0x47a Feb 18 23:23:15 spock kernel: #5 0xffffffff80d0a782 at calltrap+0x8 Feb 18 23:23:15 spock kernel: #6 0xffffffff80914c20 at __mtx_unlock_sleep+0x60 Feb 18 23:23:15 spock kernel: #7 0xffffffff80914ba9 at __mtx_unlock_flags+0x69 Feb 18 23:23:15 spock kernel: #8 0xffffffff81a21054 at smb_iod_sendall+0x264 Feb 18 23:23:15 spock kernel: #9 0xffffffff81a21760 at smb_iod_thread+0xf0 Feb 18 23:23:15 spock kernel: #10 0xffffffff808f8b6a at fork_exit+0x9a Feb 18 23:23:15 spock kernel: #11 0xffffffff80d0acbe at fork_trampoline+0xe Feb 18 23:23:15 spock kernel: Uptime: 21d12h47m48s -- 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-197934-8>