From owner-freebsd-stable@FreeBSD.ORG Fri Dec 12 13:09:50 2014 Return-Path: Delivered-To: stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id BA198543 for ; Fri, 12 Dec 2014 13:09:50 +0000 (UTC) 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 A279A6CE for ; Fri, 12 Dec 2014 13:09:50 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id sBCD9oN0045185 for ; Fri, 12 Dec 2014 13:09:50 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: stable@FreeBSD.org Subject: [Bug 193360] [panic] [syscons] random syscons panic Date: Fri, 12 Dec 2014 13:09:50 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: bin X-Bugzilla-Version: 9.1-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: sasamotikomi@gmail.com X-Bugzilla-Status: New X-Bugzilla-Priority: Normal X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Dec 2014 13:09:50 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193360 --- Comment #3 from sasamotikomi@gmail.com --- (In reply to John Baldwin from comment #2) > For these and the other various PRs you opened recently, you need to remove > the 'grep 0x' from the 'nm -n' output. That removes most of the useful > symbols and isn't helpful. In addition, far more useful would be to get > stack traces, especially if you have core.txt.N files, the kgdb stack trace > in that file would be the first thing needed to look at any of these. > > As I mentioned on another bug, a dmesg from this machine wouldn't hurt > either, but I doubt that either ed(4) or xl(4) is relevant. nm -n /boot/kernel9.1/kernel | grep c0e1e c0e1e170 t pmap_update_pde_user c0e1e1a0 T pmap_lazyfix_action c0e1e1f0 T pmap_copy_page c0e1e350 T pmap_release c0e1e600 T pmap_activate c0e1e6f0 T pmap_kenter_temporary c0e1e730 T pmap_map c0e1e820 T pmap_unmapdev c0e1e8c0 t pmap_unuse_pt c0e1e920 t pmap_remove_pte c0e1ea00 t pmap_remove_page c0e1ea50 t get_pv_entry -- You are receiving this mail because: You are on the CC list for the bug.