From owner-freebsd-bugs@freebsd.org Sat Jun 29 10:29:22 2019 Return-Path: Delivered-To: freebsd-bugs@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 18DAF15D951E for ; Sat, 29 Jun 2019 10:29:22 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) 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 A28F970C7D for ; Sat, 29 Jun 2019 10:29:21 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 6667E15D951C; Sat, 29 Jun 2019 10:29:21 +0000 (UTC) Delivered-To: bugs@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 5368F15D951B for ; Sat, 29 Jun 2019 10:29:21 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id E1C3C70C78 for ; Sat, 29 Jun 2019 10:29:20 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id 2C2AC1F17D for ; Sat, 29 Jun 2019 10:29:20 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id x5TATKDT026561 for ; Sat, 29 Jun 2019 10:29:20 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id x5TATKQe026559 for bugs@FreeBSD.org; Sat, 29 Jun 2019 10:29:20 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 235509] BTX Freezes during boot on Supermicro H8DGi-F after update to 12.0 Date: Sat, 29 Jun 2019 10:29:20 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: misc X-Bugzilla-Version: 12.0-RELEASE X-Bugzilla-Keywords: regression X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: nelson4088@yahoo.com.hk X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: bugs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 29 Jun 2019 10:29:22 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D235509 Nelson Leung changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |nelson4088@yahoo.com.hk --- Comment #6 from Nelson Leung --- (In reply to john from comment #4) I just upgraded my system from 11.2p9 to 12.0 and ran into the same issue a= nd would like to try the patch.=20 Could you mind giving some pointers on how to build the loader only. Or do I have to follow the handbook to compile the kernel? FYI I have a system with only zfs drive. One simple pool for system and ano= ther raidz2 pool for data. I noticed previously in the boot log on 11.2, there are message complaining some of the disks in raidz2 have some inconsistent (? Sorry I can't recall)= GPT headers. These were probably because the drives were pre-formatted but the disks were attached to the pool without properly destroying the GPT Thanks. --=20 You are receiving this mail because: You are the assignee for the bug.=