Date: Sun, 28 Sep 2014 19:49:02 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 193622] regular kernel panic in the graphics subsystem (possible nvidia.ko issue), FreeBSD 10-BETA1 Message-ID: <bug-193622-8-lsYO5RwtxW@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-193622-8@https.bugs.freebsd.org/bugzilla/> References: <bug-193622-8@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193622 Jan Beich <jbeich@vfemail.net> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jbeich@vfemail.net --- Comment #1 from Jan Beich <jbeich@vfemail.net> --- What type of card? Do you use vt(4) console? nvidia-driver-343.22 with GeForce GT 640 (GK107 or 0x0fc1) on 11.0-CURRENT amd64 here. The panic often happens during high ZFS I/O load when either VT is switched or an OpenGL app closed/opened. vt(4) because syscons(4) fails to gracefully dump a core in X11. panic: vm_fault: fault on nofault entry, addr: fffffe0005ec1000 cpuid = 0 KDB: stack backtrace: db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xfffffe01250cbd60 kdb_backtrace() at kdb_backtrace+0x39/frame 0xfffffe01250cbe10 vpanic() at vpanic+0x189/frame 0xfffffe01250cbe90 panic() at panic+0x43/frame 0xfffffe01250cbef0 vm_fault_hold() at vm_fault_hold+0x1c19/frame 0xfffffe01250cc140 vm_fault() at vm_fault+0x77/frame 0xfffffe01250cc180 trap_pfault() at trap_pfault+0x1e1/frame 0xfffffe01250cc220 trap() at trap+0x6f1/frame 0xfffffe01250cc570 calltrap() at calltrap+0x8/frame 0xfffffe01250cc570 --- trap 0xc, rip = 0xffffffff818a23aa, rsp = 0xfffffe01250cc630, rbp = 0xfffffe002db39f98 --- _nv000224rm() at _nv000224rm+0x3a/frame 0xfffffe002db39f98 I couldn't gather |show locks| or |show alllocks|, only unrelated warnings from INVARIANTS and WITNESS. panic: mutex os.lock_mtx not owned at nvidia_os.c:772 cpuid = 0 KDB: stack backtrace: db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xfffffe0124fef630 kdb_backtrace() at kdb_backtrace+0x39/frame 0xfffffe0124fef6e0 vpanic() at vpanic+0x189/frame 0xfffffe0124fef760 panic() at panic+0x43/frame 0xfffffe0124fef7c0 __mtx_assert() at __mtx_assert+0xc2/frame 0xfffffe0124fef7d0 os_free_spinlock() at os_free_spinlock+0x2c/frame 0xfffffe0124fef7f0 _nv014282rm() at _nv014282rm+0x9/frame 0xfffffe000e619fe8 dmapbase() at 0xfffff8001a0da000/frame 0xfffffe0005e0e000 dmapbase() at 0xfffff8001a0cc800 acquiring duplicate lock of same type: "os.lock_sx" 1st os.lock_sx @ nvidia_os.c:608 2nd os.lock_sx @ nvidia_os.c:608 KDB: stack backtrace: db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xfffffe01251cf600 kdb_backtrace() at kdb_backtrace+0x39/frame 0xfffffe01251cf6b0 witness_checkorder() at witness_checkorder+0xc4a/frame 0xfffffe01251cf740 _sx_xlock() at _sx_xlock+0x47/frame 0xfffffe01251cf780 os_acquire_mutex() at os_acquire_mutex+0x32/frame 0xfffffe01251cf7a0 _nv014147rm() at _nv014147rm+0x18/frame 0xfffffe003d63fe90 dmapbase() at 0xfffff800445b3c80 acquiring duplicate lock of same type: "os.lock_mtx" 1st os.lock_mtx @ nvidia_os.c:782 2nd os.lock_mtx @ nvidia_os.c:782 KDB: stack backtrace: db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xfffffe01251cf1e0 kdb_backtrace() at kdb_backtrace+0x39/frame 0xfffffe01251cf290 witness_checkorder() at witness_checkorder+0xc4a/frame 0xfffffe01251cf320 __mtx_lock_flags() at __mtx_lock_flags+0x48/frame 0xfffffe01251cf360 os_acquire_spinlock() at os_acquire_spinlock+0x1b/frame 0xfffffe01251cf370 _nv017635rm() at _nv017635rm+0x185/frame 0xfffffe003d6a2ef8 -- 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-193622-8-lsYO5RwtxW>