From owner-freebsd-current@freebsd.org Sun Jun 25 12:32:39 2017 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 07A8FD90B6D for ; Sun, 25 Jun 2017 12:32:39 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id E24FC6A81C for ; Sun, 25 Jun 2017 12:32:38 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: by mailman.ysv.freebsd.org (Postfix) id DE903D90B6C; Sun, 25 Jun 2017 12:32:38 +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 DE0EAD90B6B for ; Sun, 25 Jun 2017 12:32:38 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from kib.kiev.ua (kib.kiev.ua [IPv6:2001:470:d5e7:1::1]) (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 73E0F6A81B for ; Sun, 25 Jun 2017 12:32:38 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from tom.home (kib@localhost [127.0.0.1]) by kib.kiev.ua (8.15.2/8.15.2) with ESMTPS id v5PCWQtL021610 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Sun, 25 Jun 2017 15:32:26 +0300 (EEST) (envelope-from kostikbel@gmail.com) DKIM-Filter: OpenDKIM Filter v2.10.3 kib.kiev.ua v5PCWQtL021610 Received: (from kostik@localhost) by tom.home (8.15.2/8.15.2/Submit) id v5PCWQwo021609; Sun, 25 Jun 2017 15:32:26 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com using -f Date: Sun, 25 Jun 2017 15:32:26 +0300 From: Konstantin Belousov To: Boris Samorodov , David Wolfskill , current@freebsd.org Subject: Re: Insta-panic for amd64 on reboot after upgrade from r320307 -> r320324 Message-ID: <20170625123226.GV3437@kib.kiev.ua> References: <20170625120731.GE1241@albert.catwhisker.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20170625120731.GE1241@albert.catwhisker.org> User-Agent: Mutt/1.8.3 (2017-05-23) 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.23 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: Sun, 25 Jun 2017 12:32:39 -0000 On Sun, Jun 25, 2017 at 05:07:31AM -0700, David Wolfskill wrote: > Fatal trap 12: page fault while in kernel mode > cpuid = 0; apic id = 00 > fault virtual address = 0x10000000020 This is clearly an impossible address. Did you built the kernel with NO_CLEAN ? If yes, try the full build, perhaps even after removing all previous kernel objects. The layout of the struct vm_map_entry was changed, the faulted address is somewhat consistent with ABI mismatch. > fault code = supervisor read data, page not present > instruction pointer = 0x20:0xffffffff80d585a4 > stack pointer = 0x28:0xffffffff82290a30 > frame pointer = 0x28:0xffffffff82290a60 > code segment = base 0x0, limit 0xfffff, type 0x1b > = DPL 0, pres 1, long 1, def32 0, gran 1 > processor eflags = resume, IOPL = 0 > current process = 0 () > [ thread pid 0 tid 0 ] > Stopped at vm_map_lookup_entry+0x24: cmpq %r15,0x20(%rbx) > db> bt > Tracing pid 0 tid 0 td 0xffffffff81e9e860 > vm_map_lookup_entry() at vm_map_lookup_entry+0x24/frame 0xffffffff82290a60 > vm_map_insert() at vm_map_insert+0x10b/frame 0xffffffff82290b00 > kmem_init() at kmem_init+0x72/frame 0xffffffff82290b30 > vm_mem_init() at vm_mem_init+0x46/frame 0xffffffff82290b50 > mi_startup() at mi_startup+0x9c/frame 0xffffffff82290b70 > btext() at btext+0x2c > db> > > > (The laptop seems to have repeated the: > > loading required module 'kernel' > module 'kernel' exists but with wrong version > > sequence a few times, based on the video I got of it.) > > > The "saving grace" is that the panic happens before the file systems > are mounted.... :-} > > Unloading the (r320324) kernel and loading the r320307 kernel > succeeds (at least enough to mount file systems). > > Peace, > david > -- > David H. Wolfskill david@catwhisker.org > Trump (et al.): Hiding information doesn't prove its falsity. > > See http://www.catwhisker.org/~david/publickey.gpg for my public key.