[Bug 212718] cp(1)/mv(1)/install(1) cause vm_fault/panic on VIA boards w/USB cards/sticks.

[bugzilla-noreply at freebsd.org]

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

nibbana at gmx.us changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
          Component|bin                         |kern
            Version|9.3-STABLE                  |11.0-STABLE

--- Comment #6 from nibbana at 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 = 0; apic id = 00
fault virtual address = 0xd3636000
fault code = supervisor write, page not present
instruction pointer = 0x20:0xc132c277
stack pointer = 0x28:0xd90e270c
frame pointer = 0x28:0xd90e2758
code segment = base 0x0, limit 0xfffff, type 0x1b
 = DPL 0, pres 1, def32 1, gran 1
processor flags = interrupt enable, resume, IOPC = 0
current process = 72433 (cp)
trap number = 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= 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

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