From nobody@FreeBSD.org Tue Aug 24 22:40:19 2010 Return-Path: Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C46E910656A3 for ; Tue, 24 Aug 2010 22:40:19 +0000 (UTC) (envelope-from nobody@FreeBSD.org) Received: from www.freebsd.org (www.freebsd.org [IPv6:2001:4f8:fff6::21]) by mx1.freebsd.org (Postfix) with ESMTP id B41B38FC12 for ; Tue, 24 Aug 2010 22:40:19 +0000 (UTC) Received: from www.freebsd.org (localhost [127.0.0.1]) by www.freebsd.org (8.14.3/8.14.3) with ESMTP id o7OMeJ74050353 for ; Tue, 24 Aug 2010 22:40:19 GMT (envelope-from nobody@www.freebsd.org) Received: (from nobody@localhost) by www.freebsd.org (8.14.3/8.14.3/Submit) id o7OMeJ5P050348; Tue, 24 Aug 2010 22:40:19 GMT (envelope-from nobody) Message-Id: <201008242240.o7OMeJ5P050348@www.freebsd.org> Date: Tue, 24 Aug 2010 22:40:19 GMT From: "Vladislav V. Prodan" To: freebsd-gnats-submit@FreeBSD.org Subject: Panic when starting ladvd X-Send-Pr-Version: www-3.1 X-GNATS-Notify: >Number: 149948 >Category: kern >Synopsis: [panic] when starting net/ladvd >Confidential: no >Severity: serious >Priority: low >Responsible: freebsd-bugs >State: closed >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Tue Aug 24 22:50:03 UTC 2010 >Closed-Date: Thu Apr 14 20:16:24 UTC 2011 >Last-Modified: Thu Apr 14 20:16:24 UTC 2011 >Originator: Vladislav V. Prodan >Release: 9.0-CURRENT amd64 >Organization: >Environment: FreeBSD solo.XXX.biz 9.0-CURRENT FreeBSD 9.0-CURRENT #0: Tue Aug 24 15:52:21 EEST 2010 root@solo.XXX.biz:/usr/obj/usr/src/sys/solo.2 amd64 >Description: Sorry, using ZFS, so there is no crash dump ... # pkg_info | grep ladvd ladvd-0.9.0_2 A minimal CDP/LLDP daemon I am sending a screenshot: http://img714.imageshack.us/img714/286/capture08252010012658.png I can send the system variables for a few minutes to panic ... >How-To-Repeat: cd /usr/ports/net/ladvd make install clean service ladvd onestart >Fix: >Release-Note: >Audit-Trail: State-Changed-From-To: open->feedback State-Changed-By: vwe State-Changed-When: Sun Aug 29 13:26:03 UTC 2010 State-Changed-Why: Vladislav, w/o a backtrace or any other information, it's quite hard to tell where the problem might come from. Your screenshot suggests, there's a NULL pointer causing the trouble. Can you please try at first the following command and post us it's output: addr2line -e /boot/kernel/kernel.symbols 0xffffffff806aa114 If your kernel config is near GENERIC, the problem might be in sys/net80211/ieee80211_node.c:2328 Having a backtrace would make things simpler. If you're brave enough, you may try to get the kernel dump onto a usb thumb drive (I'm using this for embedded machines, where I don't have the space to store dumps). It works find, just take a look at dumpon(8). If you got a dump, please use the kernel debugger to get the backtrace. http://www.freebsd.org/cgi/query-pr.cgi?pr=149948 From: Maxim Konovalov To: universite@ukr.net Cc: bug-followup@freebsd.org Subject: Re: kern/149948: [panic] when starting net/ladvd Date: Mon, 30 Aug 2010 09:29:08 +0400 (MSD) Hello, please try a patch in kern/149807: http://www.freebsd.org/cgi/query-pr.cgi?pr=149807&cat= and report me back the results. Thanks! -- Maxim Konovalov State-Changed-From-To: feedback->closed State-Changed-By: jh State-Changed-When: Thu Apr 14 20:15:11 UTC 2011 State-Changed-Why: Feedback timeout. Possibly already fixed (see PR kern/149807). http://www.freebsd.org/cgi/query-pr.cgi?pr=149948 >Unformatted: from followup (not filed): # addr2line -e /boot/kernel/kernel.symbols 0xffffffff806aa114 /usr/src/sys/amd64/amd64/support.S:101 panic: page fault GNU gdb 6.1.1 [FreeBSD] Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "amd64-marcel-freebsd"... Cannot access memory at address 0xffffff019dffffe0 (kgdb) #0 0x0000000000000000 in ?? () Cannot access memory at address 0x0 (kgdb)