From owner-freebsd-current@FreeBSD.ORG Tue Apr 9 16:59:11 2013 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 23E7C659 for ; Tue, 9 Apr 2013 16:59:11 +0000 (UTC) (envelope-from null@pozo.com) Received: from pozo.com (pozo.com [50.197.129.137]) by mx1.freebsd.org (Postfix) with ESMTP id E22E792E for ; Tue, 9 Apr 2013 16:59:10 +0000 (UTC) Received: from T61p.pozo.com (t61p.pozo.com [192.168.0.4]) (authenticated bits=0) by pozo.com (8.14.6/8.14.6) with ESMTP id r39GwG1w027257 (version=TLSv1/SSLv3 cipher=DHE-DSS-AES256-SHA bits=256 verify=NOT); Tue, 9 Apr 2013 09:58:16 -0700 (PDT) (envelope-from null@pozo.com) Message-Id: <201304091658.r39GwG1w027257@pozo.com> X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9 Date: Tue, 09 Apr 2013 09:58:11 -0700 To: David Wolfskill , current@freebsd.org From: Manfred Antar Subject: Re: panic during transition to multi-user mode @r249303 [i386] In-Reply-To: <20130409162123.GL2722@albert.catwhisker.org> References: <20130409162123.GL2722@albert.catwhisker.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-Spam-Status: No, score=-0.9 required=5.0 tests=ALL_TRUSTED,MISSING_MID autolearn=no version=3.3.2, No X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on pozo.com X-pozocom-MailScanner-Information: Please contact the ISP for more information X-pozocom-MailScanner-ID: r39GwG1w027257 X-pozocom-MailScanner: Found to be clean X-pozocom-MailScanner-From: null@pozo.com X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 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: Tue, 09 Apr 2013 16:59:11 -0000 At 09:21 AM 4/9/2013, David Wolfskill wrote: >I saw this first on my laptop; backtrace mentioned something about >iwn(4), so after I saved the crash dump, I flippe dthe wireless switch >off and tried again... and got a different (but undoubtedly related) >panic, which I also saved. > >Then, after my build machine finished, that also got a panic (using a >GENERIC kernel), so I saved that away, as well. > >Gory details are available at >http://www.catwhisker.org/~david/FreeBSD/panic_09Apr2013/. > >Here's what's in there: > >freebeast: >total 126476 >-rw-r--r-- 1 david staff 44616 Apr 9 08:49:54 2013 core.txt.3 >-rw-r--r-- 1 david staff 7881 Apr 7 08:04:47 2013 dmesg.boot.10.0-CURRENT >-rw-r--r-- 1 david staff 491 Apr 9 08:41:09 2013 info.3 >-rw-r--r-- 1 david staff 129323008 Apr 9 08:41:16 2013 vmcore.3 > >laptop: >total 627248 >-rw-r--r-- 1 david staff 45055 Apr 9 06:35:36 2013 core.txt.5 >-rw-r--r-- 1 david staff 48156 Apr 9 06:35:46 2013 core.txt.6 >-rw-r--r-- 1 david staff 13606 Apr 7 05:53:33 2013 dmesg.boot.10.0-CURRENT >-rw-r--r-- 1 david staff 465 Oct 24 07:36:27 2012 info.5 >-rw-r--r-- 1 david staff 469 Apr 9 06:31:39 2013 info.6 >-rw-r--r-- 1 david staff 430333952 Oct 24 07:36:46 2012 vmcore.5 >-rw-r--r-- 1 david staff 211210240 Apr 9 06:31:49 2013 vmcore.6 > >(I'm not too concerned about passwords being in there, since I never >had a chance to even try to type one in. :-} > >Unfortunately, it appears that my invocation of "crashinfo" was >less than useflu, even though I pointed it at the kernel(s) that >had been running when the crash(es) occurred: the backtrace shown >is useless. I can try to boot the build machine under the previous >"head" kernel (vs. stable/9), and try that again...? > >AFK for a bit -- need to have laptop display replaced (unrelated). > >Peace, >david >-- >David H. Wolfskill david@catwhisker.org >Taliban: Evil men with guns afraid of truth from a 14-year old girl. > >See http://www.catwhisker.org/~david/publickey.gpg for my public key. > I'm also getting a panic on kernel (Current i386) the last day or two. The last good kernel: FreeBSD 10.0-CURRENT #0 r249251: Mon Apr 8 03:21:23 PDT 2013 it happens on rc.d/netwait The process is ping Something to do with new network stuff. The Interface is bge0 Manfred ======================== || null@pozo.com || || || ======================== -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.