From owner-freebsd-current@FreeBSD.ORG Fri Feb 9 09:03:07 2007 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id C7C3F16A400 for ; Fri, 9 Feb 2007 09:03:07 +0000 (UTC) (envelope-from ianf@clue.co.za) Received: from munchkin.clue.co.za (munchkin.clue.co.za [66.219.59.160]) by mx1.freebsd.org (Postfix) with ESMTP id A4D8D13C48E for ; Fri, 9 Feb 2007 09:03:07 +0000 (UTC) (envelope-from ianf@clue.co.za) Received: from uucp by munchkin.clue.co.za with local (Exim 4.62) (envelope-from ) id 1HFRes-0002pL-59; Fri, 09 Feb 2007 09:03:06 +0000 Received: from dhcp-250.clue.co.za ([10.0.0.250] helo=clue.co.za) by urchin.clue.co.za with esmtpa (Exim 4.62) (envelope-from ) id 1HFRe0-00076w-D9; Fri, 09 Feb 2007 09:02:14 +0000 Received: from localhost ([127.0.0.1]) by clue.co.za with esmtp (Exim 4.66 (FreeBSD)) (envelope-from ) id 1HFRdx-000KXu-EB; Fri, 09 Feb 2007 09:02:09 +0000 To: Kip Macy From: Ian FREISLICH In-Reply-To: Message from Kip Macy of "Thu, 08 Feb 2007 23:50:18 PST." <20070208234639.B15257@demos.bsdclusters.com> X-Attribution: BOFH Date: Fri, 09 Feb 2007 11:02:09 +0200 Message-Id: X-Spam-Scanner: urchin.clue.co.za X-Spam-Score: 1.0 (+) [INT 10] X-Spam-Report: 1.0/5.0 ---- Start SpamAssassin results * 0.9 MSGID_FROM_MTA_ID Message-Id for external message added locally * 0.1 AWL AWL: From: address is in the auto white-list ---- End SpamAssassin results Cc: freebsd-current@freebsd.org Subject: Re: Broadcom Wireless card X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 Feb 2007 09:03:07 -0000 Kip Macy wrote: > Apply the following small patch. I haven't committed it yet as it is not > a complete fix. However, it will allow you to trace past the trap. > > http://www.fsmware.com/kgdb.diff That doesn't seem to help on the old crashdump. Do I need a new kernel after applying this? (kgdb) bt #0 doadump () at pcpu.h:147 #1 0xc04fb34a in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:411 #2 0xc04fb64b in panic (fmt=0xc06a4376 "%s") at /usr/src/sys/kern/kern_shutdown.c:567 #3 0xc0681e68 in trap_fatal (frame=0xe64018d4, eva=0) at /usr/src/sys/i386/i386/trap.c:868 #4 0xc0681b88 in trap_pfault (frame=0xe64018d4, usermode=0, eva=2) at /usr/src/sys/i386/i386/trap.c:777 #5 0xc0681765 in trap (frame=0xe64018d4) at /usr/src/sys/i386/i386/trap.c:462 #6 0xc06709ab in calltrap () at /usr/src/sys/i386/i386/exception.s:139 #7 0x00000002 in ?? () Previous frame inner to this frame (corrupt stack?) Ian -- Ian Freislich