From owner-freebsd-current@freebsd.org Thu Dec 14 16:24:28 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 92358E85B9A for ; Thu, 14 Dec 2017 16:24:28 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-it0-x22e.google.com (mail-it0-x22e.google.com [IPv6:2607:f8b0:4001:c0b::22e]) (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 5EC436AFE9 for ; Thu, 14 Dec 2017 16:24:28 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-it0-x22e.google.com with SMTP id r6so12361790itr.3 for ; Thu, 14 Dec 2017 08:24:28 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20150623.gappssmtp.com; s=20150623; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=FBz+CUxLX4JKlrDDd9jR/6F//2LdHtJn684UtS3e4e4=; b=GAyfW/Y+JgBij7JQey4nr/xTz8+UVF+D27R3bfBXUKs75Gse/jFs9R5mgnt9DT3eUi tD0jDNX+XsMKwgCtGH4Bc2TdXVrvzeZd9IvW1YWxGENnxe3GrGpnpzeEOh9jJdwfoMSh XZP2YBejSHyx1pqeGJSdWFiWOjNiRzDqaJS3QRGCWcwMPahZpGH/nRphYdUn95xx++0s u1xEGsgZykdZ8HGmk9B8yOG1coulCf364zm06EnQ9vNPuLaA19QJrbZMfc1n7Kl9UUzi 3xN0Qy6BkbNvSG9fo0l7Xhyjm/g5Wdpls6EEAVmSnPNkKlV5AyIq86fcWVYJR8YTjLrc pLOA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=FBz+CUxLX4JKlrDDd9jR/6F//2LdHtJn684UtS3e4e4=; b=Q30iratKhFAEO2cG7wUTpHDirh4nuF27dw07nviSkZZ7nKY11unQeLfOr3bjppzFgE gIa+7z6b5R4BIK+4905Cqqb29/YDLMVZRu/tlc1Yv/O5xdp5ZITjLD1JvcnrMGhi1lHr qPBapfCwdwy5GINqhTMzgpQMVFoMBWPGVIDWVFXB71EqDo8Lt1rg1eFkUf3C1lpiauvX UFfupSRpvKMMtziafpLV/hMXfIRxVIvrZ8TQhDGPPOMtjwbX21CYpursWdffnuNWfuZq ikfwLzknm16Ox8sGRjg81ipJQn48nkYpxSEKUb9hM+O2RdDC/q6cImHyAOGCKe7H8E0S ujDA== X-Gm-Message-State: AKGB3mJHKpm5uzoDrRSrJTzfEqVdEEBHgTvd644622gtPfJAeLaNoTss 0Bj3mM3FcIAH8tiyBC3639sieR5f/ItHRdwCjJViNA== X-Google-Smtp-Source: ACJfBoubR/TUlc1aIQERMDT8um9tXE8D/ZUqFoU+BAZzY+DyXpmLcQV4wnhAsDFEp9XrAvv97ugbnL/7hl+TnNnBX9Y= X-Received: by 10.107.30.81 with SMTP id e78mr7621060ioe.130.1513268667339; Thu, 14 Dec 2017 08:24:27 -0800 (PST) MIME-Version: 1.0 Sender: wlosh@bsdimp.com Received: by 10.79.108.204 with HTTP; Thu, 14 Dec 2017 08:24:26 -0800 (PST) X-Originating-IP: [2603:300b:6:5100:1052:acc7:f9de:2b6d] In-Reply-To: <20171214134652.052afeb1@thor.intern.walstatt.dynvpn.de> References: <4bf0ab6fe9f034b9ec007f13c72092af@udns.ultimatedns.net> <20171214134652.052afeb1@thor.intern.walstatt.dynvpn.de> From: Warner Losh Date: Thu, 14 Dec 2017 16:24:26 +0000 X-Google-Sender-Auth: UXHEBeJa7VPoJlxjyWfyvp3_Dxs Message-ID: Subject: Re: 12-r326622 install won't boot To: "O. Hartmann" Cc: Chris H , FreeBSD Current Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 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: Thu, 14 Dec 2017 16:24:28 -0000 On Thu, Dec 14, 2017 at 12:46 PM, O. Hartmann wrote: > Am Tue, 12 Dec 2017 15:24:34 -0800 > "Chris H" schrieb: > > > On Tue, 12 Dec 2017 13:56:56 -0800 said > > > > > On Tue, 12 Dec 2017 14:33:10 -0700 "Warner Losh" said > > > > > > > On Tue, Dec 12, 2017 at 2:28 PM, Chris H > wrote: > > > > > > > > > On Tue, 12 Dec 2017 11:37:33 -0800 said > > > > > > > > > > Hello all, > > > > >> I just blew away a old RELENG_11, to start working with current. I > > > > >> must admit I had several disappointments regarding the installer. > > > > >> But that's for another topic, and another time. > > > > >> To the point; > > > > >> I completed the install. The only event(s) that might be notable > > > > >> during the install. Was early on during (boot?) I saw a "dumped > core" > > > > >> race past on the screen. I also experienced at least 1 LOR. But > the > > > > >> install continued, seemingly un(interrupted|affected). That said, > I > > > > >> chose the reboot option after completion. Ejected the DVD during > POST, > > > > >> and I'm stuck at: > > > > >> > > > > >> BTX loader 1.00 BTX version is 1.02 > > > > >> > > > > > > >> > > > > >> followed by 2 gibberish characters; 1 appears as a right pointing > arrow, > > > > >> the other, kind of like a battlestar galactca spaceship. > > > > >> NOTE: those 2 characters did not show up on the initial reboot > from > > > > >> the install (just the 2 lines above). But after I attempted a hard > > > > >> reset after the first fail. > > > > >> > > > > > OK tried the installation again, and nothings changed. > > > > > Still left with the 2 lines listed above. > > > > > > > > > > Guess I'll have to wait until 12-CURRENT becomes a usable version. > > > > > Sigh... > > > > > I was really hoping to run 12, so I could better develop 11. > > > > > Oh well. Guess I'll grab a copy of 11 off one of the ftp servers, > and spin > > > > > it > > > > > up. > > > > > > > > > > Thanks anyway! :-) > > > > > > > > > > > > > > > > I think a two-week old snapshot would work a lot better if you > wanted to > > > > make the jump to -current. I've botched something in my boot loader > cleanup > > > > and it's taking a little time to get sorted out... > > > OH, thank you *very* much, Warner! > > > Whew! Just in time, too. I had almost slipped the 11 DVD into the box. > > > > > > Thanks again, Warner. Hope the things go well for you. > > > > > > --Chris > > Spot on, Warner! r326056 gave me a working 12-CURRENT. Including all > > the LORs. :-) > > > > Thank you! > > > [ ... deleted line ...] > > I have the same here. I just tried on a APU2C4 r326846 and, as I reported > in another > thread earlier, it gives me on a serial console the same: > > Consoles: internal video/keyboard > Nothing more. > > The last known-good version is r326583. r326584 won't build, the same with > r326586 (bails > out with some errors in geli related stuff, I believe) and then the > subsequent versions > start to fail. I realised the issues on the serial console driven APU with > r326734 and I > tried to "bi-sect", unsuccessfully due to lack of time and resources down > to r326583. > The problem is with r326593. If you hack r326584 to build right then roll forward, you'll get md5 identical .o's until 93. I'm investigating. > Obviously I'm not alone having issues with loader/boot loader and it would > be wise to put > out a warning for all the other brave CURRENT testers out ... > That's a good idea. Warner