From owner-freebsd-bugs@freebsd.org Sat Oct 15 05:45:19 2016 Return-Path: Delivered-To: freebsd-bugs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 09394C12D04 for ; Sat, 15 Oct 2016 05:45:19 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id E3F25856 for ; Sat, 15 Oct 2016 05:45:18 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u9F5jIwE024083 for ; Sat, 15 Oct 2016 05:45:18 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 212718] cp(1)/mv(1)/install(1) cause vm_fault/panic on VIA boards w/USB cards/sticks. Date: Sat, 15 Oct 2016 05:45:18 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 11.0-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: nibbana@gmx.us X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: component version Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 15 Oct 2016 05:45:19 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D212718 nibbana@gmx.us changed: What |Removed |Added ---------------------------------------------------------------------------- Component|bin |kern Version|9.3-STABLE |11.0-STABLE --- Comment #6 from nibbana@gmx.us --- bug #212718 11.0-RELEASE ------------ This problem continues in 11.0-RELEASE, and generally with larger files in the MB range, less or not at all with files in the KB range. Also, there is another panic that occurs after a reboot from the cp/mv problem, which appears to be a loss of filesystem integrity (ATA). For example, after a cp(1) panic while copying from USB to ATA, after reboot, every executable in /usr/local/bin would cause a panic when run. They required deletion, and re-compiling/installing to function again without a panic. 11.0-RELEASE panic (from cp/mv/install): Fatal Trap 12: page fault while in kernel mode. cpuid =3D 0; apic id =3D 00 fault virtual address =3D 0xd3636000 fault code =3D supervisor write, page not present instruction pointer =3D 0x20:0xc132c277 stack pointer =3D 0x28:0xd90e270c frame pointer =3D 0x28:0xd90e2758 code segment =3D base 0x0, limit 0xfffff, type 0x1b =3D DPL 0, pres 1, def32 1, gran 1 processor flags =3D interrupt enable, resume, IOPC =3D 0 current process =3D 72433 (cp) trap number =3D 12 panic: page fault #0 - #17 ... kdb_backtrace+0x4f, vpanic+0x115, panic+0x1b, trap_fatal+0x30a, trap_pfault+0x10e, trap+0x68f, calltrap+0x6, vnode_pager_generic_getpages+ 0x1395, vnode_pager_local_getpages+0x42, VOP_GETPAGES_APV+0x6f, vnode_pager_getpages+0xba, vn_pager_get_pages+0x39, vn_fault_hold+0xaa0, vn_fault_quick_hold_pages+0x127 vn_io_fault1+0x2b3, vn_io_fault+0x1ff, dofilewrite+0x9b kern+writev+0x93 panic (filesystem integrity related - guessing ... sometimes part of cp/mv operations relating to USB devices, sometimes part of running an executable that was recently installed after rebooting from the previous panic): panic: unknown caching mode -268374161 cpuid=3D 0 KDB:stack backtrace #0 - #9 ... kdb_backtrace+0x4f, vpanic+0x115, panic+0x1b, pmap_qenter+0x155, g_io_check+0x304, g_io_schedule_down+0x206, g_down_procbody+0x7d, fork_exit +0x71, fork_trampoline+0x8 --=20 You are receiving this mail because: You are the assignee for the bug.=