From owner-freebsd-current@freebsd.org Sat Mar 3 23:53:17 2018 Return-Path: Delivered-To: freebsd-current@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 283E0F4739C for ; Sat, 3 Mar 2018 23:53:17 +0000 (UTC) (envelope-from rysto32@gmail.com) Received: from mail-qt0-x233.google.com (mail-qt0-x233.google.com [IPv6:2607:f8b0:400d:c0d::233]) (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)) by mx1.freebsd.org (Postfix) with ESMTPS id BE3927DCA5 for ; Sat, 3 Mar 2018 23:53:16 +0000 (UTC) (envelope-from rysto32@gmail.com) Received: by mail-qt0-x233.google.com with SMTP id c7so16372699qtn.3 for ; Sat, 03 Mar 2018 15:53:16 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=y1v5ht39jzRzGHxOqsJXw0dbSOfPe6/68J7T+e+xuxg=; b=enXNdhWFfU8QriRFVl4Uh8vSDTEfGr0Lgli177hjdRuhywleXlOnkhxBVTbqC5+iu0 7aYm6YMf83f6duC3pUKBKSIxhgA/vD1y52csVNWXpGUozrv1+jBUrYCm2tLKb+HpGcw/ x/Wq4VIQLDvuTUnGzGMcR8LwprxIPkifopydyqoL9XveU4LuOTy3x7P3GD7NFEQVf3+K T27k0S+zy4aHQuFlIGFMMMzGdUOjS3ZN4jm9AlQ86XQOQMMr121DEOxK16jq1BxgTPBY 8RH6y1YUBeE7tdyMpOk8KN5zMq5h841PeqVSHJEArCVvdJ/GpcQsZjj9TpeAlH2xKO1m ZUBw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=y1v5ht39jzRzGHxOqsJXw0dbSOfPe6/68J7T+e+xuxg=; b=c+ajf0LLVS9cKo413pcKMfNV5TctHGQktFXqmH9qB1JrSbUPQSBstgNGgJXpKH143s LOXYfcoC6+lVOBXjvIRQ0SwWaXikATTEBMqaXlwI+03fct5XX4L+3v1X6BmZQw5YQ1LJ jZx1lJ6wK2Hc3L/zCKYfAciVeXkiFDKM3ef+pLqr1SOkhFJLtK7Lfh4bE47ssXxJ+Xm/ 92G7z7ruB/F8zBqZ5GPNmhsS7ri9ngXZv3eNAHY6hzcJ4EQdssHhH1JnzdEBd0q3HCgh f7XxTC6YZf1iLy2oAR1vkaxsju8CeCKCgzZuN6tqqvXsP1VF8eewlqwmIz8bTO9X4ZVQ 70hA== X-Gm-Message-State: AElRT7GphN7W2y4Nz6V+FRMtDtiPvwGZ22/MWbY2p6cEW9CuEk9xy+yN VJYACw5lBuWkp/rjhkJpOnfwotb3M7S7ffayjU8= X-Google-Smtp-Source: AG47ELvBzX2gaV0/fUNOJg6l0K9X9GNw1B0tXWHanBvF6sCh9eO5S2MmiiTSbw0hL9DBYO6GlG7ssKCIyy7aRpoXnLQ= X-Received: by 10.200.82.152 with SMTP id s24mr15025318qtn.63.1520121196268; Sat, 03 Mar 2018 15:53:16 -0800 (PST) MIME-Version: 1.0 Received: by 10.237.32.200 with HTTP; Sat, 3 Mar 2018 15:53:15 -0800 (PST) In-Reply-To: References: <20180212085852.GA94212@kib.kiev.ua> From: Ryan Stone Date: Sat, 3 Mar 2018 18:53:15 -0500 Message-ID: Subject: Re: Panic in prison_alloc() on boot To: Konstantin Belousov Cc: FreeBSD Current Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 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: Sat, 03 Mar 2018 23:53:17 -0000 To close the loop on this, the root cause ended up being a mistake on my end. This system had a rather convoluted boot process, and as a result of that was loading a nullfs.ko built for a months-old kernel. This setup accidentally worked for some time, but I guess some recent change to struct thread changed the ABI, causing the old nullfs.ko to be incompatible and fail to boot. Sorry for the noise, Ryan