From owner-freebsd-current@freebsd.org Mon Mar 28 12:57:13 2016 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 929F9AE0300 for ; Mon, 28 Mar 2016 12:57:13 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 7D4B8107E for ; Mon, 28 Mar 2016 12:57:13 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: by mailman.ysv.freebsd.org (Postfix) id 78CDEAE02FF; Mon, 28 Mar 2016 12:57:13 +0000 (UTC) Delivered-To: current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 76225AE02FD for ; Mon, 28 Mar 2016 12:57:13 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from kib.kiev.ua (kib.kiev.ua [IPv6:2001:470:d5e7:1::1]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 1229C107D for ; Mon, 28 Mar 2016 12:57:12 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from tom.home (kostik@localhost [127.0.0.1]) by kib.kiev.ua (8.15.2/8.15.2) with ESMTPS id u2SCv1SW008245 (version=TLSv1 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Mon, 28 Mar 2016 15:57:01 +0300 (EEST) (envelope-from kostikbel@gmail.com) DKIM-Filter: OpenDKIM Filter v2.10.3 kib.kiev.ua u2SCv1SW008245 Received: (from kostik@localhost) by tom.home (8.15.2/8.15.2/Submit) id u2SCv1Qp008244; Mon, 28 Mar 2016 15:57:01 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com using -f Date: Mon, 28 Mar 2016 15:57:01 +0300 From: Konstantin Belousov To: David Wolfskill , current@freebsd.org Subject: Re: Panic after update from r297313 -> r297348 Message-ID: <20160328125701.GF1741@kib.kiev.ua> References: <20160328123613.GI4205@albert.catwhisker.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20160328123613.GI4205@albert.catwhisker.org> User-Agent: Mutt/1.5.24 (2015-08-30) X-Spam-Status: No, score=-2.0 required=5.0 tests=ALL_TRUSTED,BAYES_00, DKIM_ADSP_CUSTOM_MED,FREEMAIL_FROM,NML_ADSP_CUSTOM_MED autolearn=no autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on tom.home X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.21 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: Mon, 28 Mar 2016 12:57:13 -0000 On Mon, Mar 28, 2016 at 05:36:13AM -0700, David Wolfskill wrote: > Unfortunately, the serial console only seemed to be echoing characters > in quasi-random spurts, yielding such things as: > > ... > r() at lcpu_initcpu_initclocks_bsp+0x37f/frame 0xffffffff820dbb40 > initclocks() at initclocks+0x20/frame 0xffffffff820dbb50 > mi_start+0x2c > > Tracing td 0xffc_et_start+0x2d9/frame 0xffffffff820dbaa0 > loadtimer() at lrame 0xf configtsp() at clocks_bsp+0x37f/frame 0xffffffff820dbb40 > initclocks() at initclocks+0x20/ > Tracing pid 0 tid 100000 td 0xffffffff81d11200 > lapic_et_start()c_et_start+0x2d9/frame 0xffffffff820dbaa0 > +0x2cimeoadtimer+0x102/frame 0xf20dbac0 > db> > pid 0 tid 100000 td 0xffffffff81d11200 > lapic_et_start() at lapic_et_start+0x2d9xffffffff820dbaa0 > loadtimer() at loadtimer+0x102/frame 0xffffffff8imer+0x239/frame 0xffffffff820dbb10 > cpu_initsp() at f820dbb7pid 0 ti td 0xffffffff81_start()c_et_staf820dbaa0 > r() at loadtimer+0x102/ffffffff8 > configtimer() atcpu_initxfffffffpid 0 tif820dbaa0| |___ _ __ ___ ___ | |_) | (___ | | | ___| '__/ _ \/ _ \| _ < \___ \| | | |dtimer() at loadtimer+0x102/frame 0xffffffff8 0xffffffff820dbb10 > c| | | | | __/ __/| |_) |____) | |__| | > b| | | | \___|\|200 > configtimer() at configtimer+0x239/frame 0xffffffff820dbb10 > cpu_initclocks_bcpu_initsp+0x37f/frame 0f820dbb40 > initclocks() at initclocks+0x20/frame 0x820dbb50 > mi_startup() at mi_startup+0x118/frame 0 > Tracing d 100000lapic_et_start() at lapic_et_start+0x2d9sp+0x37f+0x2c > db> 0 > 0xffffffff820dbsp+0x37ff820dbb4ks() at > mi_startup() at up+0x118/frame 0xffffffff820dbb70 > btext() at btext+0x2c > db> bd 100000+0x102/frame 0xfcpu_initframe 0xffffffff+0x2c > pic [K]ernel (1 of 2) > r|m 6.bConfigure Boot [O]ptions... > H| vpanic+0x182/frame 0xffffffff820db4a0+ > db_commaf0 .-- > sp+0x37f0/frame 0xffffffff820db6kdb_trapf820d .---.....----.______ ____ _____ _____ ____| | _ \ / ____| __ \ > bte > Uptime: 1s -c0+0x4db8+0x15eef8+0x8+0x]+-y+:. `:` > > > at which point I had already (semi-blindly) tried "panic", so I > tried "reset", then I was able to escape to the loader, unload the > new kernel, boot the previous one, move the various kernel* > difrectories around in /boot, then reboot again to old kernel: > > FreeBSD freebeast.catwhisker.org 11.0-CURRENT FreeBSD 11.0-CURRENT #2028 r297313M/297313:1100104: Sun Mar 27 06:27:24 PDT 2016 root@freebeast.catwhisker.org:/common/S4/obj/usr/src/sys/GENERIC amd64 > > I'm still building on my laptop; while I hope I don't have the character- > dropping issues there (as I have no serial console on it), I also don't > have much of a way to communicate what it displays if it (also) panics. > > Apparently my attempt at "panic" didn't get a crash dump.. :-( > > Any suggestions for diagnosing this? > Show me verbose dmesg of the running kernel. Also, does anything change with the faulting kernel if you set hw.lapic_tsc_deadline to 0 in loader ?