From owner-freebsd-current@freebsd.org Tue Oct 10 21:20:13 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 DA6EEE3D4B5 for ; Tue, 10 Oct 2017 21:20:13 +0000 (UTC) (envelope-from lausts@laus.org) Received: from cdptpa-cmomta01.email.rr.com (cdptpa-outbound-snat.email.rr.com [107.14.166.231]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "Client", Issuer "CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 965376D569; Tue, 10 Oct 2017 21:20:12 +0000 (UTC) (envelope-from lausts@laus.org) Received: from mail.laus.org ([65.29.112.189]) by cmsmtp with ESMTP id 21wZeA9HV5iJO21wbelez2; Tue, 10 Oct 2017 21:20:06 +0000 Received: from mail.laus.org (localhost [127.0.0.1]) by mail.laus.org (8.15.2/8.15.2) with ESMTPS id v9ALK3VL035758 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Tue, 10 Oct 2017 17:20:03 -0400 (EDT) (envelope-from lausts@laus.org) Received: (from lausts@localhost) by mail.laus.org (8.15.2/8.15.2/Submit) id v9ALK32f035757; Tue, 10 Oct 2017 17:20:03 -0400 (EDT) (envelope-from lausts) Date: Tue, 10 Oct 2017 17:20:03 -0400 From: Thomas Laus To: Allan Jude Cc: freebsd-current@freebsd.org Subject: Re: Encrypted Swap Problem with 12.0-CURRENT r324427 Message-ID: <20171010212003.GA35726@mail.laus.org> Reply-To: lausts@acm.org References: <332f479e-87ab-8d5b-58f1-c7ee9bfa779b@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <332f479e-87ab-8d5b-58f1-c7ee9bfa779b@freebsd.org> X-Operating-System: FreeBSD 11.1-RELEASE-p1 on an amd64 User-Agent: Mutt/1.9.1 (2017-09-22) X-CMAE-Envelope: MS4wfMdp9w8y8PXVKNuRJ0x7PESIo3AWzaJXirqN+FieNVu9IcRQdsKdAsfmNC4kD4oaIr8NibFMLEvMV4Ul+ZfP7PYfyoLrBK0OPDdmF3f+bHcVGSR4DqeF MfvhgVSwGGd3UErRPLZmU+3b3GiBd5OsPnWnROwSTtn6BCzMVcPTS0UMxKpvLTnpf9vV2BsACxrTfWTzcKr1xeIDx51jSk1hfms= 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: Tue, 10 Oct 2017 21:20:14 -0000 Allan Jude [allanjude@freebsd.org] wrote: > > Before the ddb> prompt there should be a message explaining what has > gone wrong to make it drops into the debugger. If it has scrolled off > the top of the screen, press scroll-lock and then you can use the arrow > keys to navigate back up into the buffer. > The first message is from GEOM_ELI: Device ada0p2.eli created GEOM_ELI: Encryption AES-XTS 128 GEOM_ELI: Crypto: software panic: freeing invalid range. Next follows the stack trace then: --- syscall (85, FreeBSD ELF64, sys_swapon), rip = 0x800a88aea, rsp = 0x7fffffffea48, rbp 0x7fffffffea60 --- stopped at kdb_enter+0x3b:mmovq $0,kdb_why I can't save all of this to a file to attach, but this is just an overview of the panic. I get this everytime when going from single user to multi-user and about 3 out of 5 times with a normal boot. My other release has been flawless 100 percent of the time. Tom -- Public Keys: PGP KeyID = 0x5F22FDC1 GnuPG KeyID = 0x620836CF