From owner-freebsd-current@freebsd.org Sun Mar 12 18:22:49 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 23EF9D09E78 for ; Sun, 12 Mar 2017 18:22:49 +0000 (UTC) (envelope-from subbsd@gmail.com) Received: from mail-it0-x22f.google.com (mail-it0-x22f.google.com [IPv6:2607:f8b0:4001:c0b::22f]) (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 E542E1D59 for ; Sun, 12 Mar 2017 18:22:48 +0000 (UTC) (envelope-from subbsd@gmail.com) Received: by mail-it0-x22f.google.com with SMTP id g138so20863262itb.0 for ; Sun, 12 Mar 2017 11:22:48 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=dWEDQmSGeXbKGxU+Gfg2DgAASecZiqfSadz7udWunnU=; b=WNi7XXIjflDZmFETCP/OLSgtJt9fxJM/QdvCV3l0y+OBCLSB56WS1S0jPYrtTszcfa Z0ZHCLW2ohZe4jThR8gSUWKpBVZBMEvQwKFelDl/jmp5fDwS2bSEd3jHupzgHuKsQRfG GZDOTheNifJufLTaZQC2XRrutNGHKneadPYvE0vkh54lHUltmWrMi7HGN2qHbt7UuMUF mdbS2XOWiYnHKpMM9GBM6tlR8B5U+jAobiydydih7aIcHswcab4ev5IeAJoyIB5LU9GQ ERsQBpZqamRlEpP9FkXbNuFfZYW/lnkBtu1hmTJljYeHc70xqKKTxY1D9Jzaffr8SAY7 cxWw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=dWEDQmSGeXbKGxU+Gfg2DgAASecZiqfSadz7udWunnU=; b=tVeG8vtjoyigHKBOoo1lpluvZ2Vvt98IWDX7priK6bHWkAxTAt+yv80lSkKy7v0s5F xvzvGnJPRiwE2Un3RWsiLCKgtx/200ucEqMgYL+4IN/WN6IJ61TibD+rxD285aE92wRj P1pT5vjermuQTI3NUhtJvE0TBLksfkNSb3uFWsq88j1+CICu5Kkv50lw4Qjq60pZrwHv XRPdEWqidlypWC9SYEkiaYU2CEEg8asjPQiSgJhaVX1b980NNZSAaYyVRIcTDlSD7lHV WoFCNiXaj0DWk3YEg/MaRIuoNQcKpXb5J1o/s3kXlbguB7l3lcQqTRS0bpOwzhcAxxId WMSw== X-Gm-Message-State: AFeK/H1IZFlTN7hFpiYzxfuWm/MzbUTf84vlHBc6S1iYBq0yRM3iESbGFnW9NBimFWac9bPhQmp5EMJ5b7lNZw== X-Received: by 10.36.211.67 with SMTP id n64mr4663988itg.13.1489342968289; Sun, 12 Mar 2017 11:22:48 -0700 (PDT) MIME-Version: 1.0 Received: by 10.79.167.24 with HTTP; Sun, 12 Mar 2017 11:22:47 -0700 (PDT) From: Subbsd Date: Sun, 12 Mar 2017 21:22:47 +0300 Message-ID: Subject: FreeBSD-current, panic on UEFI boot after recent changes To: freebsd-current Current Content-Type: text/plain; charset=UTF-8 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, 12 Mar 2017 18:22:49 -0000 Hi, ( I apologize if this is a duplicate - first I wrote this as reply-all on https://lists.freebsd.org/pipermail/freebsd-current/2017-March/064971.html thread ) After recent changes and fixes ( https://lists.freebsd.org/pipermail/freebsd-current/2017-March/065093.html ) I still had problems on host with increased EFI_STAGING_SIZE value. I have custom FreeBSD distribution which has a sufficiently large mfsroot which is loaded through UEFI mode. To solve the problem, it was suggested to increase this variable and rebuild /sys/boot: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=209944 Also, it has to be increased periodically for some reason: https://svnweb.freebsd.org/base/stable/11/sys/boot/efi/loader/copy.c?r1=305779&r2=305778&pathrev=305779 I've try to ask why than threatens to increase this parameter at once large (or make it dependent on RAM): https://lists.freebsd.org/pipermail/freebsd-hackers/2016-November/050142.html but there are no answer options. At the moment, on r315141 boot via UEFI is fine with default EFI_STAGING_SIZE (64) With EFI_STAGING_SIZE=768 i got panic after recent changes with follow message: failed to allocate staging area:9 failed to allocate stating area Failed to start image provided by ZFS (5) http://pasteboard.co/IvbhU9Ffu.jpg I believe that there mfsroot may be greater than 64MB soon or later. Also there are no problems with loading big mfsroot images when MBR method is used. PS: I have ZFS-on-root system. With EFI_STAGING_SIZE=768 I lived with constant CURRENT svnup/rebuilds for about a year. So I will be glad if you pay attention to this. PPS: How to reproduce: 1) EFI_STAGING_SIZE=768 in /etc/make.conf 2) make -C /sys/boot clean 3) make -C /sys/boot 4) make -C /sys/boot install 5) reboot Thanks!