From owner-freebsd-stable@freebsd.org Tue Apr 17 14:49:49 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id DAA49F808C5 for ; Tue, 17 Apr 2018 14:49:48 +0000 (UTC) (envelope-from kevans@freebsd.org) Received: from smtp.freebsd.org (unknown [IPv6:2610:1c1:1:606c::24b:4]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "smtp.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 85B867D483 for ; Tue, 17 Apr 2018 14:49:48 +0000 (UTC) (envelope-from kevans@freebsd.org) Received: from mail-lf0-f46.google.com (mail-lf0-f46.google.com [209.85.215.46]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) (Authenticated sender: kevans) by smtp.freebsd.org (Postfix) with ESMTPSA id 39A53EB28 for ; Tue, 17 Apr 2018 14:49:48 +0000 (UTC) (envelope-from kevans@freebsd.org) Received: by mail-lf0-f46.google.com with SMTP id r125-v6so11031246lfe.2 for ; Tue, 17 Apr 2018 07:49:48 -0700 (PDT) X-Gm-Message-State: ALQs6tB9SYNxtdYMNo/J4ZdQqkGxyQ1Zvshf5IVksbtTWrrKv3kZBN4W 8VLwYKpTcix/xmcf6RKLMtHqSuRBs8A9KUEvNP8= X-Google-Smtp-Source: AIpwx4/avDBnQ7O8sfPlNasjRes7Zn1+RbJMNKEgBC9DpnjRGy18XxD+2Xl13dlWS6kB5XxNXr4WyjcWjXdCpNIuhto= X-Received: by 10.46.148.202 with SMTP id r10mr1732798ljh.22.1523976586774; Tue, 17 Apr 2018 07:49:46 -0700 (PDT) MIME-Version: 1.0 Received: by 10.46.129.90 with HTTP; Tue, 17 Apr 2018 07:49:26 -0700 (PDT) In-Reply-To: References: From: Kyle Evans Date: Tue, 17 Apr 2018 09:49:26 -0500 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: amd64 kernel crash introduced between 20180329 & 20180408 To: Dan Allen Cc: FreeBSD-STABLE Mailing List Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 Apr 2018 14:49:49 -0000 On Tue, Apr 17, 2018 at 9:44 AM, Dan Allen wrote: > I run FreeBSD 11-STABLE on actual machines, and I build the system every few days. Things have been fine. > > However, I also run FreeBSD 11 via the qemu emulator on my Mac. I run lots of different BSD & Linux OSes here to test them out. I have been running the same binary of qemu-system-x86_64 v1.2 for six years. It runs great. > > Then recently this happened: > > This snapshot dated 20180329, after doing a fresh install, runs fine: > > https://download.freebsd.org/ftp/snapshots/ISO-IMAGES/11.1/FreeBSD-11.1-STABLE-amd64-20180329-r331742-disc1.iso > > I can run pkg install and begin adding stuff to the system and life is good. > > BUT > > This snapshot dated 20180408, after doing a fresh install, will crash when running pkg install: > > https://download.freebsd.org/ftp/snapshots/ISO-IMAGES/11.1/FreeBSD-11.1-STABLE-amd64-20180408-r332308-disc1.iso > > It crashes about 90% of the way through updating the pkg snapshot. It does not matter what pkg you try and install. > > However, the latest release in the i386 flavor works fine on qemu: > > https://download.freebsd.org/ftp/snapshots/ISO-IMAGES/11.1/FreeBSD-11.1-STABLE-i386-20180412-r332428-disc1.iso > > So sometime between March 29th & April 8th, in amd64 boot code, I believe the problem was introduced. As "the guy most likely to have broken boot code in stable," may I ask what leads you specifically to amd64 boot code? Mostly curious if there's something beyond "i386 works well" that lead you to this conclusion. > I cannot debug the crash, because it does a kernel dump, and then when the system reboots, almost anything again triggers a kernel crash and it reboots again and again: no chance to inspect a mini dump or whatever. When you say it crashes and does a kernel dump- you're landing at a ddb prompt, yeah? What does executing bt at that prompt look like>? > I wish I had more to go on, but I am happy to off list work with anyone that wants to pursue this, by testing out stuff or answering more questions. >