From owner-freebsd-stable@freebsd.org Sun Apr 22 11:04:12 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 621A5FB6578 for ; Sun, 22 Apr 2018 11:04:12 +0000 (UTC) (envelope-from nimrod@nimrod.is-a-geek.net) Received: from mail-yw0-x22b.google.com (mail-yw0-x22b.google.com [IPv6:2607:f8b0:4002:c05::22b]) (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 029536F79B for ; Sun, 22 Apr 2018 11:04:11 +0000 (UTC) (envelope-from nimrod@nimrod.is-a-geek.net) Received: by mail-yw0-x22b.google.com with SMTP id l15-v6so3589068ywk.3 for ; Sun, 22 Apr 2018 04:04:11 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=4Y7CXh0APC/ux5xZI+3FzAEiP1xr8pIXStWOHq6Kjww=; b=pYHOh3Go/5UZ7q+UXJzzTXsmP9qiEXWAwwGW9BsHizWONzdT0KHBGREQDiYxycUIge 75bU40FEk/zshE+mJ1lljl/I41ELRthRVA0f7LywFOKiIup5rbQ+mUaFXrNt2ECHcWA2 HL2R6+W2ZqzOqpzSc0uRbptG363J0oIJIappaPLblB5zZnHj0e4O65Qy5g5/liTw3QJT SVwM72BbDqC7ZkR27KMR9bBMtEAOMHOf6KMpvTF6UegYOzPKpAT15HwurcYaXkF9T5xE G24IamkmbUUjKKGp3Dk8jrxTWz82M92HhERZc2MDMtEOGUfd1opHrJ1zjd5BaXDI/3nL jE2Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=4Y7CXh0APC/ux5xZI+3FzAEiP1xr8pIXStWOHq6Kjww=; b=Uq/q43kBwUKyj4EIOTaZ+LemJ/trFmtb9y7V1dbokgIytlTqDoP0Q4+a54jgBL49r/ wPy1nGpyOn5pkmODq5mGdT6fr3W62PPNeSnNrZdl/TyQfzgAknXllEqSoT7e9OQQ+69/ CIyHshbn40MWb+Jir0KZ8rx5asrFqoy2+CF7vtey6c+dgT7sA4OnKeC5FHMx/9igoLuk vdlTOTlLaUhecrjkJRQhqj3OxKcHVKCG9RcllMxLRNNz3ON3BEQ+Sox6vu4rMxpfxI0r QT6QoIVXHwr0kCteldU7oOHuOp+dqkxIu3NXbkwG7p52PM+NjW+YBD7unMLXigTORvN6 CM7g== X-Gm-Message-State: ALQs6tBHmEG/jFpJV5Uwq/7eT+rJ8IIyp9XprIW7QQuxvaLxwinaVU5l A8ymtUhn5r253YJhlRxkiPOYOtwv81e759wJEvj4hg== X-Google-Smtp-Source: AIpwx48r/qyRmQn/oWpavSPQSbuOmUo+6Txm/hAqsCJPDqS2KbM93NLrmxaJd0jUHieW6hGvPqxoAcEZCV/ziJo/5fo= X-Received: by 2002:a81:3612:: with SMTP id d18-v6mr8911441ywa.381.1524395050921; Sun, 22 Apr 2018 04:04:10 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Nimrod Levy Date: Sun, 22 Apr 2018 11:04:00 +0000 Message-ID: Subject: Re: Ryzen issues on FreeBSD ? (with sort of workaround) To: Pete French Cc: eric@vangyzen.net, freebsd@hda3.com, truckman@freebsd.org, freebsd-stable@freebsd.org, avg@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 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: Sun, 22 Apr 2018 11:04:12 -0000 And of course now that we say something about it, I get a lockup overnight... -- Nimrod On Fri, Apr 20, 2018 at 7:48 AM Nimrod Levy wrote: > I'm really glad to see that I'm not the only one still interested in this > thread. I don't really have anything new to contribute. I've been getting > about a week or so uptime out of my box. My habit has been to see if it > hangs, then reboot and rebuild latest stable and reboot and run that for a > while. Although now that this thread pops back up, I just realized it's > been 2 weeks since the last cycle. I don't trust it yet, but I've seen > clear improvement since this started. > > > On Fri, Apr 20, 2018 at 7:18 AM Pete French > wrote: > >> So, resurrecting the thread from a few weeks ago, as I finally found >> time yesterday to out together the Ryzen machine I bought the parts for in >> Jaunary (busy year at work....). All went smoothl;y, checked it >> booted up, used it for 15 minutes, was impressed by the speed and went >> home. >> >> ...and by the time I got home, an hour or so later, it had locked up hard. >> >> I was somewhat dissapointed, as I had seen various fixes go in,. and had >> hoped >> the issues were fixed. This morning I have booted the machine back up, >> tweaking the BIOPS to do things mentioned in this thread, viz: >> >> Disable Turbo Boost >> Disable SMT >> Disable global C-states >> >> The memory was already ruunning correctly at 2133 (though I have locked >> that >> in the BIOS too) and I was already using kern.eventtimer.periodic=1, so >> the lockup was not related to those. Its the latest BIOS, and a -STABLE >> build from yesterday. >> >> I suspect it will now be stable, but I was wondering if anyone was any >> further >> forward on working out which of the settings above are the ones which >> 'fix' >> the issue - or indeed if its really fixed, by them or just made far less >> likely >> to happen. >> >> Anyone got any more comments on this ? >> >> cheers, >> >> -pete. >> _______________________________________________ >> freebsd-stable@freebsd.org mailing list >> https://lists.freebsd.org/mailman/listinfo/freebsd-stable >> To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" >> > -- > > -- > Nimrod > -- -- Nimrod From owner-freebsd-stable@freebsd.org Sun Apr 22 21:29:59 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 3F876F9148B for ; Sun, 22 Apr 2018 21:29:59 +0000 (UTC) (envelope-from truckman@FreeBSD.org) Received: from mx2.catspoiler.org (mx2.catspoiler.org [IPv6:2607:f740:16::d18]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "amnesiac", Issuer "amnesiac" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id CD1307BD8D; Sun, 22 Apr 2018 21:29:58 +0000 (UTC) (envelope-from truckman@FreeBSD.org) Received: from gw.catspoiler.org ([76.212.85.177]) by mx2.catspoiler.org (8.15.2/8.15.2) with ESMTPS id w3MLVEcq035582 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=FAIL); Sun, 22 Apr 2018 21:31:16 GMT (envelope-from truckman@FreeBSD.org) Received: from mousie.catspoiler.org (mousie.catspoiler.org [192.168.101.2]) by gw.catspoiler.org (8.15.2/8.15.2) with ESMTPS id w3MLThaJ082655 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 22 Apr 2018 14:29:44 -0700 (PDT) (envelope-from truckman@FreeBSD.org) Date: Sun, 22 Apr 2018 14:29:38 -0700 (PDT) From: Don Lewis Subject: Re: Ryzen issues on FreeBSD ? (with sort of workaround) To: Pete French cc: eric@vangyzen.net, freebsd@hda3.com, avg@freebsd.org, freebsd-stable@freebsd.org In-Reply-To: Message-ID: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=us-ascii Content-Disposition: INLINE 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: Sun, 22 Apr 2018 21:29:59 -0000 On 20 Apr, Pete French wrote: > So, resurrecting the thread from a few weeks ago, as I finally found > time yesterday to out together the Ryzen machine I bought the parts for in > Jaunary (busy year at work....). All went smoothl;y, checked it > booted up, used it for 15 minutes, was impressed by the speed and went home. > > ...and by the time I got home, an hour or so later, it had locked up hard. > > I was somewhat dissapointed, as I had seen various fixes go in,. and had hoped > the issues were fixed. This morning I have booted the machine back up, > tweaking the BIOPS to do things mentioned in this thread, viz: > > Disable Turbo Boost > Disable SMT > Disable global C-states > > The memory was already ruunning correctly at 2133 (though I have locked that > in the BIOS too) and I was already using kern.eventtimer.periodic=1, so > the lockup was not related to those. Its the latest BIOS, and a -STABLE > build from yesterday. > > I suspect it will now be stable, but I was wondering if anyone was any further > forward on working out which of the settings above are the ones which 'fix' > the issue - or indeed if its really fixed, by them or just made far less likely > to happen. > > Anyone got any more comments on this ? In terms of hangs and system crashes, my Ryzen system has been stable since the fix to relocate the shared page. The random segfault problem during parallel builds went away when I RMAed my original, early-build CPU. This commit: r329254 | kib | 2018-02-13 16:31:45 -0800 (Tue, 13 Feb 2018) | 43 lines Ensure memory consistency on COW. Fixed most of the remaining random port build errors that I had. I think the only remaining problem is random build failures of guile-related ports, but I also see these on my FX-8320E, so they are not Ryzen-specific. Pretty much all of my BIOS settings are the defaults. I suspect that the idle hang issues are motherboard and/or BIOS specific. For the record my motherboard is a Gigabyte GA-AX370-Gaming 5. From owner-freebsd-stable@freebsd.org Mon Apr 23 09:40:41 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 91B43FAC474 for ; Mon, 23 Apr 2018 09:40:41 +0000 (UTC) (envelope-from petefrench@ingresso.co.uk) Received: from constantine.ingresso.co.uk (unknown [IPv6:2a02:b90:3002:411::3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 2E0C268893; Mon, 23 Apr 2018 09:40:41 +0000 (UTC) (envelope-from petefrench@ingresso.co.uk) Received: from [2a02:b90:3002:411::6] (helo=dilbert.ingresso.co.uk) by constantine.ingresso.co.uk with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.89 (FreeBSD)) (envelope-from ) id 1fAXxd-000On4-Ud; Mon, 23 Apr 2018 09:40:37 +0000 Received: from petefrench by dilbert.ingresso.co.uk with local (Exim 4.91 (FreeBSD)) (envelope-from ) id 1fAXxd-000JYr-Sh; Mon, 23 Apr 2018 10:40:37 +0100 Date: Mon, 23 Apr 2018 10:40:37 +0100 To: petefrench@ingresso.co.uk, nimrodl@gmail.com Subject: Re: Ryzen issues on FreeBSD ? (with sort of workaround) Cc: truckman@freebsd.org, freebsd@hda3.com, freebsd-stable@freebsd.org, eric@vangyzen.net, avg@freebsd.org References: In-Reply-To: User-Agent: Heirloom mailx 12.4 7/29/08 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: From: Pete French 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: Mon, 23 Apr 2018 09:40:41 -0000 > And of course now that we say something about it, I get a lockup > overnight... Sods law I guess. Mine survived the weekend quite happily though, so am fairly pleased with that. Am going to try the test case that Mike Tancsa posted to see if I can get it to lockup today though,. now that I am in front of it to reset of required. Will report results either way... -pete. From owner-freebsd-stable@freebsd.org Mon Apr 23 09:44:29 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 EDEF1FAC8B4 for ; Mon, 23 Apr 2018 09:44:28 +0000 (UTC) (envelope-from petefrench@ingresso.co.uk) Received: from constantine.ingresso.co.uk (unknown [IPv6:2a02:b90:3002:411::3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 8C7306AE22; Mon, 23 Apr 2018 09:44:28 +0000 (UTC) (envelope-from petefrench@ingresso.co.uk) Received: from [2a02:b90:3002:411::6] (helo=dilbert.ingresso.co.uk) by constantine.ingresso.co.uk with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.89 (FreeBSD)) (envelope-from ) id 1fAY1L-000OqU-LL; Mon, 23 Apr 2018 09:44:27 +0000 Received: from petefrench by dilbert.ingresso.co.uk with local (Exim 4.91 (FreeBSD)) (envelope-from ) id 1fAY1L-000LPH-Ji; Mon, 23 Apr 2018 10:44:27 +0100 Date: Mon, 23 Apr 2018 10:44:27 +0100 To: petefrench@ingresso.co.uk, lists@eitanadler.com Subject: Re: Ryzen issues on FreeBSD ? (with sort of workaround) Cc: truckman@freebsd.org, freebsd@hda3.com, freebsd-stable@freebsd.org, eric@vangyzen.net, avg@freebsd.org References: In-Reply-To: User-Agent: Heirloom mailx 12.4 7/29/08 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: From: Pete French 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: Mon, 23 Apr 2018 09:44:29 -0000 > I have a Ryzen system > parts: https://pcpartpicker.com/list/HhycYT > dmesg: http://dmesgd.nycbug.org/index.cgi?do=view&id=3516 > > which I have been using for months without issue and on completely > default settings. Thats encouranging -= and I think you are the first person to report that without any tweaking to the best of my recollection! > What mobo do you have? Did you update the BIOS to the latest version? MSI X370 Xpower Titanium - I upgraded to that one from my original choice ater comments on this thread about power which I hadnt considered (I had also decided to buy a larger Ryzen 7). The BIOS is the latest version, and I cleared CMOS to get the default settings. Memory is some Crucial DDR4 3200 which is underclocked to 2133. This microprocessor itself is a Ryzen 7 1700 (not X) which was made in week 33, so should not have the hardware fault on it. It's been stable over the weekend, as I posted in a different email, am going to try and knock it over today with some tests if I can. -pete. From owner-freebsd-stable@freebsd.org Mon Apr 23 12:19:44 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 E4AEFFB777F for ; Mon, 23 Apr 2018 12:19:43 +0000 (UTC) (envelope-from petefrench@ingresso.co.uk) Received: from constantine.ingresso.co.uk (unknown [IPv6:2a02:b90:3002:411::3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 889DE6D790; Mon, 23 Apr 2018 12:19:43 +0000 (UTC) (envelope-from petefrench@ingresso.co.uk) Received: from [2a02:b90:3002:411::6] (helo=dilbert.ingresso.co.uk) by constantine.ingresso.co.uk with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.89 (FreeBSD)) (envelope-from ) id 1fAaRZ-000133-5j; Mon, 23 Apr 2018 12:19:41 +0000 Received: from petefrench by dilbert.ingresso.co.uk with local (Exim 4.91 (FreeBSD)) (envelope-from ) id 1fAaRY-0000nB-Ut; Mon, 23 Apr 2018 13:19:41 +0100 To: nimrodl@gmail.com, petefrench@ingresso.co.uk, petefrench@ingresso.co.uk Subject: Re: Ryzen issues on FreeBSD ? (with sort of workaround) Cc: avg@freebsd.org, eric@vangyzen.net, freebsd-stable@freebsd.org, freebsd@hda3.com, truckman@freebsd.org Message-Id: From: Pete French Date: Mon, 23 Apr 2018 13:19:40 +0100 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: Mon, 23 Apr 2018 12:19:44 -0000 > fairly pleased with that. Am going to try the test case that Mike Tancsa > posted to see if I can get it to lockup today though,. now that I am in > front of it to reset of required. Will report results either way... So, I have been ran the iperf scripts all day (about 4 hours now) with the Ryzen box being the reciever and another BSD box as the sender. I had re-enabled SMT on the Ryzen box out of curiosity. All worked fine until just no,w when it did lockup. But the lockup happened when I fired up VirtualBox as well on the Ryzen machine, had that doing a lot of disc activity and also did a lot of ZFS activity on the box itself. Which I find interesting, because your lockups were also happenng when VirtualBox was running were they not ? So, am going to try that again (the iperf test and simultaneous Win10 in VirtualBox), but with SMT off, to see if I can reproduce it. -pete. From owner-freebsd-stable@freebsd.org Mon Apr 23 13:25:58 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 69842FBBEFE for ; Mon, 23 Apr 2018 13:25:58 +0000 (UTC) (envelope-from mike@sentex.net) Received: from smarthost2.sentex.ca (smarthost2.sentex.ca [IPv6:2607:f3e0:80:80::2]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client CN "smarthost.sentex.ca", Issuer "smarthost.sentex.ca" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id E137F7A47A; Mon, 23 Apr 2018 13:25:57 +0000 (UTC) (envelope-from mike@sentex.net) Received: from lava.sentex.ca (lava.sentex.ca [IPv6:2607:f3e0:0:5::11]) by smarthost2.sentex.ca (8.15.2/8.15.2) with ESMTPS id w3NDPt2V068011 (version=TLSv1 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Mon, 23 Apr 2018 09:25:56 -0400 (EDT) (envelope-from mike@sentex.net) Received: from [192.168.43.26] (saphire3.sentex.ca [192.168.43.26]) by lava.sentex.ca (8.15.2/8.15.2) with ESMTP id w3NDPsLj052468; Mon, 23 Apr 2018 09:25:54 -0400 (EDT) (envelope-from mike@sentex.net) Subject: Re: Ryzen issues on FreeBSD ? (with sort of workaround) To: Don Lewis , Pete French Cc: eric@vangyzen.net, freebsd-stable@freebsd.org, avg@freebsd.org, freebsd@hda3.com References: From: Mike Tancsa Openpgp: preference=signencrypt Organization: Sentex Communications Message-ID: <3d5dd3be-b3a3-ca1e-901d-00c5ee71efcd@sentex.net> Date: Mon, 23 Apr 2018 09:25:54 -0400 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.78 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: Mon, 23 Apr 2018 13:25:58 -0000 On 4/22/2018 5:29 PM, Don Lewis wrote: > Pretty much all of my BIOS settings are the defaults. > > I suspect that the idle hang issues are motherboard and/or BIOS > specific. For the record my motherboard is a Gigabyte > GA-AX370-Gaming 5. Hi Don, Any chance you could try that bhyve test ? Basically, or 3 VMs and then run iperf3 between the instances. I can lock up all 3 of my AMD boards (2 ASUS, one MSI) and both my Epyc (SuperMicro) boards. ---Mike -- ------------------- Mike Tancsa, tel +1 519 651 3400 x203 Sentex Communications, mike@sentex.net Providing Internet services since 1994 www.sentex.net Cambridge, Ontario Canada From owner-freebsd-stable@freebsd.org Mon Apr 23 16:56:08 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 98992FA6A29 for ; Mon, 23 Apr 2018 16:56:08 +0000 (UTC) (envelope-from truckman@FreeBSD.org) Received: from mx2.catspoiler.org (mx2.catspoiler.org [IPv6:2607:f740:16::d18]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "amnesiac", Issuer "amnesiac" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 30F1B6CCF4; Mon, 23 Apr 2018 16:56:08 +0000 (UTC) (envelope-from truckman@FreeBSD.org) Received: from gw.catspoiler.org ([76.212.85.177]) by mx2.catspoiler.org (8.15.2/8.15.2) with ESMTPS id w3NGvRoS038391 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=FAIL); Mon, 23 Apr 2018 16:57:29 GMT (envelope-from truckman@FreeBSD.org) Received: from mousie.catspoiler.org (mousie.catspoiler.org [192.168.101.2]) by gw.catspoiler.org (8.15.2/8.15.2) with ESMTPS id w3NGtwlW022700 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 23 Apr 2018 09:55:59 -0700 (PDT) (envelope-from truckman@FreeBSD.org) Date: Mon, 23 Apr 2018 09:55:53 -0700 (PDT) From: Don Lewis Subject: Re: Ryzen issues on FreeBSD ? (with sort of workaround) To: Mike Tancsa cc: Pete French , eric@vangyzen.net, freebsd-stable@freebsd.org, avg@freebsd.org, freebsd@hda3.com In-Reply-To: <3d5dd3be-b3a3-ca1e-901d-00c5ee71efcd@sentex.net> Message-ID: References: <3d5dd3be-b3a3-ca1e-901d-00c5ee71efcd@sentex.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=us-ascii Content-Disposition: INLINE 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: Mon, 23 Apr 2018 16:56:08 -0000 On 23 Apr, Mike Tancsa wrote: > On 4/22/2018 5:29 PM, Don Lewis wrote: >> Pretty much all of my BIOS settings are the defaults. >> >> I suspect that the idle hang issues are motherboard and/or BIOS >> specific. For the record my motherboard is a Gigabyte >> GA-AX370-Gaming 5. > Hi Don, > Any chance you could try that bhyve test ? Basically, or 3 VMs and then > run iperf3 between the instances. I can lock up all 3 of my AMD boards > (2 ASUS, one MSI) and both my Epyc (SuperMicro) boards. I should be able to do that, but it will likely be a few days before I can get around to it. From owner-freebsd-stable@freebsd.org Mon Apr 23 22:28:18 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 7C1DDFACBF6 for ; Mon, 23 Apr 2018 22:28:18 +0000 (UTC) (envelope-from kiri@kx.openedu.org) Received: from kx.openedu.org (flets-sg1027.kamome.or.jp [202.216.24.27]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id BBC3378CBC for ; Mon, 23 Apr 2018 22:28:16 +0000 (UTC) (envelope-from kiri@kx.openedu.org) Received: from kx.openedu.org (kx.openedu.org [202.216.24.27]) by kx.openedu.org (8.14.5/8.14.5) with ESMTP id w3NMS6UW042861; Tue, 24 Apr 2018 07:28:07 +0900 (JST) (envelope-from kiri@kx.openedu.org) Message-Id: <201804232228.w3NMS6UW042861@kx.openedu.org> Date: Tue, 24 Apr 2018 07:28:06 +0900 From: KIRIYAMA Kazuhiko To: freebsd-stable@freebsd.org Cc: kiri@kx.openedu.org Subject: What should do in chrooted environment? User-Agent: Wanderlust/2.14.0 (Africa) SEMI/1.14.6 (Maruoka) FLIM/1.14.9 (=?ISO-8859-4?Q?Goj=F2?=) APEL/10.6 MULE XEmacs/21.4 (patch 22) (Instant Classic) (amd64--freebsd) MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII 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: Mon, 23 Apr 2018 22:28:18 -0000 Hi, all I've make buildworld in chrooted environment. But failed at 'stage 4.2: building libraries' [1]: objcopy --only-keep-debug libproc.so.3.full libproc.so.3.debug objcopy --strip-debug --add-gnu-debuglink=libproc.so.3.debug libproc.so.3.full libproc.so.3 sh /usr/src/tools/install.sh -C -o root -g wheel -m 444 libproc.a /usr/obj/usr/src/tmp/usr/lib/ sh /usr/src/tools/install.sh -s -o root -g wheel -m 444 libproc.so.3 /usr/obj/usr/src/tmp/usr/lib/ sh /usr/src/tools/install.sh -o root -g wheel -m 444 libproc.so.3.debug /usr/obj/usr/src/tmp/usr/lib/debug/usr/lib/ sh /usr/src/tools/install.sh -l rs libproc.so.3 /usr/obj/usr/src/tmp/usr/lib/libproc.so sh /usr/src/tools/install.sh -C -o root -g wheel -m 444 /usr/src/lib/libproc/libproc.h /usr/obj/usr/src/tmp/usr/include/ make[5]: "/dev/null" line 1: Need an operator make[5]: Fatal errors encountered -- cannot continuemake[4]: "/usr/src/Makefile.inc1" line 421: warning: "MK_AUTO_OBJ=no MAKEFLAGS= CPUTYPE=dummy make -f /dev/null -m /usr/src/share/mk -V CPUTYPE" returned non-zero status make[4]: "/usr/src/Makefile.inc1" line 423: CPUTYPE global should be set with ?=. *** Error code 1 Stop. make[3]: stopped in /usr/src *** Error code 1 Stop. make[2]: stopped in /usr/src *** Error code 1 Stop. make[1]: stopped in /usr/src My chrooted environment is a bhyve vm attach & mounted one like this(*1): root@vms:~ # mdconfig -a -t vnode -f /vm/tbedfs/disk0.img md0 root@vms:~ # gpart show md0 => 40 16777136 md0 GPT (8.0G) 40 24 - free - (12K) 64 1024 1 freebsd-boot (512K) 1088 16776023 2 freebsd-ufs (8.0G) 16777111 41 - free - (21K) 16777152 23 3 freebsd-swap (12K) 16777175 1 - free - (512B) root@vms:~ # mount /dev/md0p2 /mnt And src and obj are nullfs mounted to latest src repository(r332874) and OBJDIR respectively: root@vms:~ # uname -a FreeBSD vms.pis 12.0-CURRENT FreeBSD 12.0-CURRENT #0 r331153: Tue Mar 20 10:13:56 JST 2018 admin@t.pis:/ds/obj/current/12.0/r331153/ds/src/current/12.0/r331153/amd64.amd64/sys/GENERIC amd64 root@vms:~ # admin@vms:~ % df Filesystem 1K-blocks Used Avail Capacity Mounted on /dev/aacd0p4 10143484 4624840 4707168 50% / devfs 1 1 0 100% /dev /dev/aacd0p5 14560423728 79273144 13316316688 1% /ds /ds/.dake 14560423728 79273144 13316316688 1% /.dake /ds/vm 14560423728 79273144 13316316688 1% /vm /dev/md0p2 5061084 3053316 1602884 66% /mnt /ds/src/stable/11.1/r332874 14560423728 79273144 13316316688 1% /mnt/usr/src /ds/obj/stable/11.1/r332874 14560423728 79273144 13316316688 1% /mnt/usr/obj admin@vms:~ % Then chroot to /mnt and make buildworld: root@vms:~ # chroot /mnt "make buildworld" Of course 'make buildworld' in vm was successfully finished [2]: admin@tbedfs:~ % uname -a FreeBSD tbedfs 11.1-STABLE FreeBSD 11.1-STABLE #0 r332428: Thu Apr 12 16:37:51 UTC 2018 root@releng2.nyi.freebsd.org:/usr/obj/usr/src/sys/GENERIC amd64 admin@tbedfs:~ % df Filesystem 1K-blocks Used Avail Capacity Mounted on /dev/vtbd0p2 8106116 849980 6607648 11% / devfs 1 1 0 100% /dev vms.pis:/.dake 14560423728 83720204 13311869628 1% /.dake vms.pis:/ds/src/stable/11.1/r332874 14560423728 83720204 13311869628 1% /usr/src vms.pis:/ds/obj/stable/11.1/r332874 14560423728 83720204 13311869628 1% /usr/obj admin@tbedfs:~ % su Password: root@tbedfs:/usr/home/admin # cd /usr/src/ root@tbedfs:/usr/src # make buildworld To make buildworld in chrooted environment, what should I do ? Best regards (*1) Acctually used vm-bhyve port(sysutils/vm-bhyve). [1] http://ds.truefc.org/~kiri/freebsd/stable/dake.log [2] http://ds.truefc.org/~kiri/freebsd/stable/make_buildworld.log --- KIRIYAMA Kazuhiko From owner-freebsd-stable@freebsd.org Mon Apr 23 22:44:11 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 C92F4FAD0FA for ; Mon, 23 Apr 2018 22:44:10 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [96.47.72.132]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "freefall.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 755897C1E2; Mon, 23 Apr 2018 22:44:10 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Received: from FreeBSD.org (freefall.freebsd.org [IPv6:2610:1c1:1:6074::16:84]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by freefall.freebsd.org (Postfix) with ESMTPS id 235C7E4A0; Mon, 23 Apr 2018 22:44:10 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Date: Mon, 23 Apr 2018 22:44:08 +0000 From: Glen Barber To: KIRIYAMA Kazuhiko Cc: freebsd-stable@freebsd.org Subject: Re: What should do in chrooted environment? Message-ID: <20180423224408.GC56778@FreeBSD.org> References: <201804232228.w3NMS6UW042861@kx.openedu.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="JWEK1jqKZ6MHAcjA" Content-Disposition: inline In-Reply-To: <201804232228.w3NMS6UW042861@kx.openedu.org> User-Agent: Mutt/1.9.1 (2017-09-22) 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: Mon, 23 Apr 2018 22:44:11 -0000 --JWEK1jqKZ6MHAcjA Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Apr 24, 2018 at 07:28:06AM +0900, KIRIYAMA Kazuhiko wrote: > Hi, all >=20 > I've make buildworld in chrooted environment. But failed at > 'stage 4.2: building libraries' [1]: >=20 > objcopy --only-keep-debug libproc.so.3.full libproc.so.3.debug > objcopy --strip-debug --add-gnu-debuglink=3Dlibproc.so.3.debug libproc.s= o.3.full libproc.so.3 > sh /usr/src/tools/install.sh -C -o root -g wheel -m 444 libproc.a /usr= /obj/usr/src/tmp/usr/lib/ > sh /usr/src/tools/install.sh -s -o root -g wheel -m 444 libproc.so.3= /usr/obj/usr/src/tmp/usr/lib/ > sh /usr/src/tools/install.sh -o root -g wheel -m 444 libproc.so.3.deb= ug /usr/obj/usr/src/tmp/usr/lib/debug/usr/lib/ > sh /usr/src/tools/install.sh -l rs libproc.so.3 /usr/obj/usr/src/tmp/usr= /lib/libproc.so > sh /usr/src/tools/install.sh -C -o root -g wheel -m 444 /usr/src/lib/li= bproc/libproc.h /usr/obj/usr/src/tmp/usr/include/ > make[5]: "/dev/null" line 1: Need an operator > make[5]: Fatal errors encountered -- cannot continuemake[4]: "/usr/src/Ma= kefile.inc1" line 421: warning: "MK_AUTO_OBJ=3Dno MAKEFLAGS=3D CPUTYPE=3Ddu= mmy make -f /dev/null -m /usr/src/share/mk -V CPUTYPE" returned non-zero s= tatus > make[4]: "/usr/src/Makefile.inc1" line 423: CPUTYPE global should be set = with ?=3D. > *** Error code 1 >=20 > Stop. > make[3]: stopped in /usr/src > *** Error code 1 >=20 > Stop. > make[2]: stopped in /usr/src > *** Error code 1 >=20 > Stop. > make[1]: stopped in /usr/src >=20 > My chrooted environment is a bhyve vm attach & mounted one > like this(*1): >=20 > root@vms:~ # mdconfig -a -t vnode -f /vm/tbedfs/disk0.img=20 > md0 > root@vms:~ # gpart show md0 > =3D> 40 16777136 md0 GPT (8.0G) > 40 24 - free - (12K) > 64 1024 1 freebsd-boot (512K) > 1088 16776023 2 freebsd-ufs (8.0G) > 16777111 41 - free - (21K) > 16777152 23 3 freebsd-swap (12K) > 16777175 1 - free - (512B) >=20 > root@vms:~ # mount /dev/md0p2 /mnt >=20 >=20 > And src and obj are nullfs mounted to latest src > repository(r332874) and OBJDIR respectively: >=20 >=20 > root@vms:~ # uname -a > FreeBSD vms.pis 12.0-CURRENT FreeBSD 12.0-CURRENT #0 r331153: Tue Mar 20 = 10:13:56 JST 2018 admin@t.pis:/ds/obj/current/12.0/r331153/ds/src/curre= nt/12.0/r331153/amd64.amd64/sys/GENERIC amd64 > root@vms:~ #=20 > admin@vms:~ % df > Filesystem 1K-blocks Used Avail Capacity Mo= unted on > /dev/aacd0p4 10143484 4624840 4707168 50% / > devfs 1 1 0 100% /d= ev > /dev/aacd0p5 14560423728 79273144 13316316688 1% /ds > /ds/.dake 14560423728 79273144 13316316688 1% /.= dake > /ds/vm 14560423728 79273144 13316316688 1% /vm > /dev/md0p2 5061084 3053316 1602884 66% /m= nt > /ds/src/stable/11.1/r332874 14560423728 79273144 13316316688 1% /m= nt/usr/src > /ds/obj/stable/11.1/r332874 14560423728 79273144 13316316688 1% /m= nt/usr/obj > admin@vms:~ %=20 >=20 >=20 > Then chroot to /mnt and make buildworld: >=20 >=20 > root@vms:~ # chroot /mnt "make buildworld" >=20 >=20 > Of course 'make buildworld' in vm was successfully finished [2]: >=20 >=20 > admin@tbedfs:~ % uname -a > FreeBSD tbedfs 11.1-STABLE FreeBSD 11.1-STABLE #0 r332428: Thu Apr 12 16:= 37:51 UTC 2018 root@releng2.nyi.freebsd.org:/usr/obj/usr/src/sys/GENERI= C amd64 > admin@tbedfs:~ % df > Filesystem 1K-blocks Used Avail Capa= city Mounted on > /dev/vtbd0p2 8106116 849980 6607648 1= 1% / > devfs 1 1 0 10= 0% /dev > vms.pis:/.dake 14560423728 83720204 13311869628 = 1% /.dake > vms.pis:/ds/src/stable/11.1/r332874 14560423728 83720204 13311869628 = 1% /usr/src > vms.pis:/ds/obj/stable/11.1/r332874 14560423728 83720204 13311869628 = 1% /usr/obj > admin@tbedfs:~ % su > Password: > root@tbedfs:/usr/home/admin # cd /usr/src/ > root@tbedfs:/usr/src # make buildworld >=20 >=20 > To make buildworld in chrooted environment, what should I do ? >=20 I think you might not have the devfs mount in the image. With the paths provided above, I think this should fix it: # mount -t devfs devfs /mnt/dev Glen --JWEK1jqKZ6MHAcjA Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEjRJAPC5sqwhs9k2jAxRYpUeP4pMFAlreYbgACgkQAxRYpUeP 4pPU3RAAnPkyTicQYW1s/Tq9VeLFGL28yhzAx9d0mPL6Sxl66vk/0Fr8PeMSldzE 06oCGbw2EQXRc9BMXOkPSg72BLh3gPq5XpLI0F0WwV9Fv7oKpvqZpb7GOKPJNcpF /DqoKIfNrMkobFt0T+5O8Cj+/n4kv9uCZH1JreXpltCkvRKFoczZ+7OH5yHi8WTo rTC8f8rov3cij8joGnG+SqKWeg6UCTcO4CWGAcGXXgSw6M5+GmSSlQ5ajW6Vrqg3 8E1oOwKX49Cp/3WBqfizT79T/HSQjrVC1WwA22vATMm/IcXlES4MqTv8yOyeoP3Y nlfInttrL9C1WbrjhAKjY9l2n45E2JqAQ2yusxyxl/aK/2XH9VQX6En6A2r3JVwV x9ngi47U+/zyaDthmBxnGJ8aPTckTebLOyKpEt5wI8SvTGmjpAJn6p418qneTFgB 6pMUrZ9U0vSuMcOR5WZ8I4sz0RH0X0OCE6i/VsWzO7BxGSfOcog2aYAhV+8Mvts+ Sy+GhXgmyOylr5XxWdEqkKgXQwssE5/49iY5VPd2nFlJJ2QqgXSsRXj/GybkvCg2 hdl2xStom/ispzVaGRe5KEdf4c9bLBrugqv3aTRp0nSUtW/3i2OuhEeoshWNwXel dH/edf1qf6VvfcxyemjpCW3/EW3KyU7+j4zeCCuA9wOa/+Mwg6o= =U9XW -----END PGP SIGNATURE----- --JWEK1jqKZ6MHAcjA-- From owner-freebsd-stable@freebsd.org Tue Apr 24 00:54:00 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 EDD67FAFC78 for ; Tue, 24 Apr 2018 00:53:59 +0000 (UTC) (envelope-from darius@dons.net.au) Received: from ipmail06.adl6.internode.on.net (ipmail06.adl6.internode.on.net [150.101.137.145]) by mx1.freebsd.org (Postfix) with ESMTP id 16C8D7883E for ; Tue, 24 Apr 2018 00:53:58 +0000 (UTC) (envelope-from darius@dons.net.au) Received: from ppp121-45-43-229.bras2.adl4.internode.on.net (HELO midget.dons.net.au) ([121.45.43.229]) by ipmail06.adl6.internode.on.net with ESMTP; 24 Apr 2018 10:23:51 +0930 Received: from midget.dons.net.au (localhost [127.0.0.1]) by midget.dons.net.au (8.15.1/8.14.9) with ESMTPS id w3O0ri3m021444 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for ; Tue, 24 Apr 2018 10:23:44 +0930 (CST) (envelope-from darius@dons.net.au) Received: (from mailnull@localhost) by midget.dons.net.au (8.15.1/8.14.9/Submit) id w3O0mG6x018097 for ; Tue, 24 Apr 2018 10:18:16 +0930 (CST) (envelope-from darius@dons.net.au) X-Authentication-Warning: midget.dons.net.au: mailnull set sender to using -f Received: from [203.31.81.59] ([203.31.81.59]) by ppp121-45-43-229.bras2.adl4.internode.on.net (envelope-sender ) (MIMEDefang) with ESMTP id w3O0m90M018091; Tue, 24 Apr 2018 10:18:16 +0930 Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 11.3 \(3445.6.18\)) Subject: Re: What should do in chrooted environment? From: "O'Connor, Daniel" In-Reply-To: <20180423224408.GC56778@FreeBSD.org> Date: Tue, 24 Apr 2018 10:18:08 +0930 Cc: KIRIYAMA Kazuhiko , freebsd-stable@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: References: <201804232228.w3NMS6UW042861@kx.openedu.org> <20180423224408.GC56778@FreeBSD.org> To: Glen Barber X-Mailer: Apple Mail (2.3445.6.18) X-Spam-Score: 1.5 (*) No, score=1.5 required=5.0 tests=HELO_MISC_IP, RDNS_NONE autolearn=no autolearn_force=no version=3.4.0 X-Scanned-By: MIMEDefang 2.75 on 10.0.2.1 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, 24 Apr 2018 00:54:00 -0000 > On 24 Apr 2018, at 08:14, Glen Barber wrote: > I think you might not have the devfs mount in the image. With the = paths > provided above, I think this should fix it: >=20 > # mount -t devfs devfs /mnt/dev I wonder if it's worth doing a basic sanity check that /dev/null and = /dev/zero look like device nodes. I've made this mistake too and it produces some very confusing error = messages :( -- Daniel O'Connor "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C From owner-freebsd-stable@freebsd.org Tue Apr 24 02:27:33 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 DA4F3FB4303 for ; Tue, 24 Apr 2018 02:27:33 +0000 (UTC) (envelope-from matheus@eternamente.info) Received: from hobbes.arroway.org (hobbes.arroway.org [173.199.118.77]) by mx1.freebsd.org (Postfix) with ESMTP id 956C26B9DC for ; Tue, 24 Apr 2018 02:27:33 +0000 (UTC) (envelope-from matheus@eternamente.info) Received: from [10.1.1.10] (unknown [179.156.16.23]) by hobbes.arroway.org (Postfix) with ESMTPA id F0DFF3AC85 for ; Mon, 23 Apr 2018 23:18:20 -0300 (BRT) Received: from 10.1.2.60 (SquirrelMail authenticated user matheus) by 10.1.1.10 with HTTP; Mon, 23 Apr 2018 23:18:21 -0300 Message-ID: <55533ad671792b7a30ff00cd1659a02b.squirrel@10.1.1.10> Date: Mon, 23 Apr 2018 23:18:21 -0300 Subject: Two USB 4 disk enclosure and a panic From: "Nenhum_de_Nos" To: freebsd-stable@freebsd.org User-Agent: SquirrelMail/1.4.23 [SVN] MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal 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, 24 Apr 2018 02:27:34 -0000 Hi, I would like to know how to debug this. I have two 4 disk enclosures: Mediasonic ProBox 4 Bay 3.5' SATA HDD Enclosure – USB 3.0 & eSATA (HF2-SU3S2) NexStar HX4 - NST-640SU3-BK and both have 4 disk on them, and not all disk are equal. The issue comes when I plug the probox usb3 enclosure on the system. I can't even read the /var/log/message, it crashes very quickly. I can see on the boot process up to the point where the second enclosure comes to be loaded. The 4 disk are shown on the dmesg/console, and then a core dump happens, the boot process goes to the debug screen and a restart happens like a flash. The motherboard is a Intel® Desktop Board D525MW running 8GB RAM. All disk use ZFS, 4 or 5 zpools, one raidz, one mirror and two or three single disk pools. FreeBSD xxx 11.1-RELEASE-p7 FreeBSD 11.1-RELEASE-p7 #1 r330596: Thu Mar 8 06:45:59 -03 2018 root@xxx:/usr/obj/usr/src/sys/FreeBSD-11-amd64-PF amd64 The kernel is a slightly modified generic, just to have altq. How can I debug this? I have no idea. I have to use two machines to run all those disks, and I would really like to have just one for it. Can it be the amount of RAM? The other box is and APU2 from PCEngines and have 4GB ram. apu2 uname -a: FreeBSD yyy 11.1-RELEASE-p4 FreeBSD 11.1-RELEASE-p4 #0: Tue Nov 14 06:12:40 UTC 2017 root@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64 I tried to plug the Vantec hardware on the apu2 box, but there it would not panic, but won't load all vantec disks neither. I really run out of ideas here :( thanks. -- "We will call you Cygnus, the God of balance you shall be." From owner-freebsd-stable@freebsd.org Tue Apr 24 10:49:48 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 00806F891C7 for ; Tue, 24 Apr 2018 10:49:48 +0000 (UTC) (envelope-from kraduk@gmail.com) Received: from mail-it0-x22a.google.com (mail-it0-x22a.google.com [IPv6:2607:f8b0:4001:c0b::22a]) (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 7F21881BE4; Tue, 24 Apr 2018 10:49:47 +0000 (UTC) (envelope-from kraduk@gmail.com) Received: by mail-it0-x22a.google.com with SMTP id x144-v6so12024631itc.0; Tue, 24 Apr 2018 03:49:47 -0700 (PDT) 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=0hKwrOqDAtgIZdD5c0XLIEhdFs+AnVZSIu6jhU4NU80=; b=kdZo0t6ZzDkz6bCTrc71LtmvxrM8FoHqdUMrhY5eaiMRzBlouNrOI02dFa3Kym323Q YS2Jt9mKVYIA4BzzWAYCF7+cbz7nvIYDLXlnaCCY4aQVjwJ51Nbn7TNFODMWoYI+S+2N etFDYsgtC2/7wgkitnnt8u0k9QPvyS/0TlHl8+qMWsPV99+yVzoBNxtkQRbGH7zJvY/O g3PyIochEiuJkMKygfFXSeAMALR9+3xgFNCMJxtLurxHQcnRbzoJDPA6e73aABnnCVbE itHASOM+Ewi1wMl+C4aTtaw0/9H1JwT8nQApcrQvdUi3Pr2waoNOrdnUzri8XL4fmXaJ vWyw== 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=0hKwrOqDAtgIZdD5c0XLIEhdFs+AnVZSIu6jhU4NU80=; b=qu1wfYoNYT2SM5f56501E2TJkFjI72w1J8vHD0aiQTmUMV8aAiBrlUKty8NwQAJQu+ yVYV/Da+qfnYT5QH0b2PNr0uO++H8O6vocuG9lkq1a07jDxyc6mcn2xnvhhtr0eetrYS H1LUOhPsWsWTKgOI/8ZBq+oTmWXlPQ3Cl8bVRZFU/tMYFuby7636e19F1krV9EbGb/+D uHu6ZdlHyKL2ppnMurB5udzN1I3z9FbdC2KqKt1mq9wHAFQNSSLrK72DnGIYROzcehPa UX7t+NljvvVnrfTXLpyo2PMoXfulOuonoq0QpQZmX1Iht4bq+Bgb5LYgPwZbRwS7zVkI TgNg== X-Gm-Message-State: ALQs6tCmq4z4/MYzQTWptiNz882S+K0Uj06Kz7eP9mOg+LlcR1eXIEU+ t5mbVr+9+ItUkQOHH6gleOdabbKw06WxcwHAbSI= X-Google-Smtp-Source: AIpwx4/c3B05Z7ZAVUENLtydeveU2HrYthoyEm4rg4Kch3Ktnl/4skrygehzTcDvbALlBakjKHjF+Pk4q2VDwujFkZs= X-Received: by 2002:a24:245:: with SMTP id 66-v6mr16421041itu.14.1524566986728; Tue, 24 Apr 2018 03:49:46 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a02:6f5e:0:0:0:0:0 with HTTP; Tue, 24 Apr 2018 03:49:46 -0700 (PDT) In-Reply-To: References: <201804232228.w3NMS6UW042861@kx.openedu.org> <20180423224408.GC56778@FreeBSD.org> From: krad Date: Tue, 24 Apr 2018 11:49:46 +0100 Message-ID: Subject: Re: What should do in chrooted environment? To: "O'Connor, Daniel" Cc: Glen Barber , KIRIYAMA Kazuhiko , freebsd-stable Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 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, 24 Apr 2018 10:49:48 -0000 wouldn't it just be easier to do this in a jail, and then all of these little bits would be taken care of? On 24 April 2018 at 01:48, O'Connor, Daniel wrote: > > > > On 24 Apr 2018, at 08:14, Glen Barber wrote: > > I think you might not have the devfs mount in the image. With the paths > > provided above, I think this should fix it: > > > > # mount -t devfs devfs /mnt/dev > > I wonder if it's worth doing a basic sanity check that /dev/null and > /dev/zero look like device nodes. > > I've made this mistake too and it produces some very confusing error > messages :( > > -- > Daniel O'Connor > "The nice thing about standards is that there > are so many of them to choose from." > -- Andrew Tanenbaum > GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C > > _______________________________________________ > freebsd-stable@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" > From owner-freebsd-stable@freebsd.org Tue Apr 24 13:24:56 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 E9B10FA40B8 for ; Tue, 24 Apr 2018 13:24:55 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2610:1c1:1:6074::16:84]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "freefall.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 998FD831C9; Tue, 24 Apr 2018 13:24:55 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Received: from FreeBSD.org (freefall.freebsd.org [IPv6:2610:1c1:1:6074::16:84]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by freefall.freebsd.org (Postfix) with ESMTPS id 39018ECE8; Tue, 24 Apr 2018 13:24:55 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Date: Tue, 24 Apr 2018 13:24:52 +0000 From: Glen Barber To: krad Cc: "O'Connor, Daniel" , KIRIYAMA Kazuhiko , freebsd-stable Subject: Re: What should do in chrooted environment? Message-ID: <20180424132452.GB70329@FreeBSD.org> References: <201804232228.w3NMS6UW042861@kx.openedu.org> <20180423224408.GC56778@FreeBSD.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="dc+cDN39EJAMEtIO" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.9.1 (2017-09-22) 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, 24 Apr 2018 13:24:56 -0000 --dc+cDN39EJAMEtIO Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable There are additional nits regarding jail(8) that chroot(8) does not have the same limitations. Setting/unsetting the immutable flag on something like /sbin/init, for example, comes to mind. Glen On Tue, Apr 24, 2018 at 11:49:46AM +0100, krad wrote: > wouldn't it just be easier to do this in a jail, and then all of these > little bits would be taken care of? >=20 > On 24 April 2018 at 01:48, O'Connor, Daniel wrote: >=20 > > > > > > > On 24 Apr 2018, at 08:14, Glen Barber wrote: > > > I think you might not have the devfs mount in the image. With the pa= ths > > > provided above, I think this should fix it: > > > > > > # mount -t devfs devfs /mnt/dev > > > > I wonder if it's worth doing a basic sanity check that /dev/null and > > /dev/zero look like device nodes. > > > > I've made this mistake too and it produces some very confusing error > > messages :( > > > > -- > > Daniel O'Connor > > "The nice thing about standards is that there > > are so many of them to choose from." > > -- Andrew Tanenbaum > > GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C > > > > _______________________________________________ > > freebsd-stable@freebsd.org mailing list > > https://lists.freebsd.org/mailman/listinfo/freebsd-stable > > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.or= g" > > --dc+cDN39EJAMEtIO Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEjRJAPC5sqwhs9k2jAxRYpUeP4pMFAlrfMCAACgkQAxRYpUeP 4pN8ZhAAjjLMLRMgG0UE5c5YieMO/arIQL7eFODXE1OMBi1Zpqba+275Byk8nnlH xqYd+oDx8qvkD9xFzPzQjQ6z0Q+ZLjwE6ohsloYespV49Bt9CB6p3ikY94EH40dl 1rE/8zCcUChSdvg8hMb3dVY2mEy7oKnQpCUoavcEvtRuLEakjAqx1++jqSVq+IGy qcBm4LE3v6kp6ENyzeJQYMjTfDw4bsCFryNcz10HEveLwdZkiYFGsTTbnIY1Ijwt ACA6j2MH0HO1gkthu/yTOzg2DGm0khhzC3V/Wz8p4FJjLEtoS1twYVBv5nnHBxGD dfHig+1HiPMrUxGdFvn3ZS0LxxPfi4HrkIjoEp8XW6ELOXRAOBKJXtPc59L5zOPZ FFLNxyQTe9V6uFuU3JF6N90JWKVGv3LApNTCXQf+ijZBV/qqmvvtF7l/034vUXnZ 3zj6jkCsB3sCaLsTqWkrFH8zjM79NBiqjGBVRDInzkfl3yRMM6LXLV6Do2k563Y3 Qqjsd9SsW6PyyvH26369XnJMJ9QOjZV09Y+OBoq2I7IZI9kxTvf+NYdGS2wRdJsJ YkG5QPrgO+KSZ/6dFrKp4WX3TOEYG0AXBdwL8L4QptqL3kSKEDgiLQCDV6qqZXMv nGuXiCiDO6CShjL9DxpVb2V12Gqz58XpHD0GWPgWwNcXaM7neAA= =BuyM -----END PGP SIGNATURE----- --dc+cDN39EJAMEtIO-- From owner-freebsd-stable@freebsd.org Tue Apr 24 13:56:12 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 E3D2CFA5516 for ; Tue, 24 Apr 2018 13:56:11 +0000 (UTC) (envelope-from mike@sentex.net) Received: from smarthost2.sentex.ca (smarthost2.sentex.ca [IPv6:2607:f3e0:80:80::2]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client CN "smarthost.sentex.ca", Issuer "smarthost.sentex.ca" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 68341698D6; Tue, 24 Apr 2018 13:56:11 +0000 (UTC) (envelope-from mike@sentex.net) Received: from lava.sentex.ca (lava.sentex.ca [IPv6:2607:f3e0:0:5::11]) by smarthost2.sentex.ca (8.15.2/8.15.2) with ESMTPS id w3ODuAld012347 (version=TLSv1 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Tue, 24 Apr 2018 09:56:10 -0400 (EDT) (envelope-from mike@sentex.net) Received: from [192.168.43.26] (saphire3.sentex.net [192.168.43.26]) by lava.sentex.ca (8.15.2/8.15.2) with ESMTP id w3ODu8HZ058856; Tue, 24 Apr 2018 09:56:08 -0400 (EDT) (envelope-from mike@sentex.net) Subject: Re: Ryzen issues on FreeBSD ? (with sort of workaround) To: Pete French , nimrodl@gmail.com Cc: truckman@freebsd.org, eric@vangyzen.net, freebsd-stable@freebsd.org, freebsd@hda3.com, avg@freebsd.org References: From: Mike Tancsa Openpgp: preference=signencrypt Organization: Sentex Communications Message-ID: <59b435cf-f4fb-0cc8-3bd0-0765ac0592da@sentex.net> Date: Tue, 24 Apr 2018 09:56:08 -0400 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.78 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, 24 Apr 2018 13:56:12 -0000 On 4/23/2018 8:19 AM, Pete French wrote: > > All worked fine until just no,w when it did lockup. But the lockup > happened when I fired up VirtualBox as well on the Ryzen machine, had that > doing a lot of disc activity and also did a lot of ZFS activity on the box > itself. Which I find interesting, because your lockups were also happenng > when VirtualBox was running were they not ? > > So, am going to try that again (the iperf test and simultaneous Win10 > in VirtualBox), but with SMT off, to see if I can reproduce it. > I was doing the tests with bhyve, and the iperf tests were between VMs on the same box. That seems to trigger it fairly quickly. The Epyc took a bit more work, but I could reliable do it there too. ---Mike -- ------------------- Mike Tancsa, tel +1 519 651 3400 x203 Sentex Communications, mike@sentex.net Providing Internet services since 1994 www.sentex.net Cambridge, Ontario Canada From owner-freebsd-stable@freebsd.org Tue Apr 24 14:01:40 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 561B9FA5E5F for ; Tue, 24 Apr 2018 14:01:40 +0000 (UTC) (envelope-from petefrench@ingresso.co.uk) Received: from constantine.ingresso.co.uk (unknown [IPv6:2a02:b90:3002:411::3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 972A96B09F; Tue, 24 Apr 2018 14:01:39 +0000 (UTC) (envelope-from petefrench@ingresso.co.uk) Received: from dilbert.london-internal.ingresso.co.uk ([10.64.50.6]) by constantine.ingresso.co.uk with esmtpsa (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.89 (FreeBSD)) (envelope-from ) id 1fAyVk-000L5K-1W; Tue, 24 Apr 2018 14:01:36 +0000 Subject: Re: Ryzen issues on FreeBSD ? (with sort of workaround) To: Mike Tancsa , nimrodl@gmail.com Cc: truckman@freebsd.org, eric@vangyzen.net, freebsd-stable@freebsd.org, freebsd@hda3.com, avg@freebsd.org References: <59b435cf-f4fb-0cc8-3bd0-0765ac0592da@sentex.net> From: Pete French Message-ID: <84898b9f-991c-420a-3ebd-f8c4ad9915e1@ingresso.co.uk> Date: Tue, 24 Apr 2018 15:01:35 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0 MIME-Version: 1.0 In-Reply-To: <59b435cf-f4fb-0cc8-3bd0-0765ac0592da@sentex.net> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit 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, 24 Apr 2018 14:01:40 -0000 On 24/04/2018 14:56, Mike Tancsa wrote: > I was doing the tests with bhyve, and the iperf tests were between VMs > on the same box. That seems to trigger it fairly quickly. The Epyc took > a bit more work, but I could reliable do it there too. Well, I ranh the iperf tests between real machine for 24 hours and that worked fine. I also then spun up a Virtualbox with Win10 in it, and ran iuperf to there at the same time as doing it betwene real machines, and also did a full virus scan to exercise the disc. the idea being to replicate Mondays lockup. But its all fine - the only differece being that I have disabled SMT again. Do you get lockup-s with SMT disabled ? I dint have any experince with bhyve and dont have the tiime to start learning right now, hence me testing with VB, which I already have pa nd running. I can repeat with SMt on again to veiry that it does then lock up. All very odd though - am pleased its stable, but dissapinted at the amout of stuff I have had to turn off to get it to that state. -pete. From owner-freebsd-stable@freebsd.org Tue Apr 24 14:09:43 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 A9871FA66D7 for ; Tue, 24 Apr 2018 14:09:43 +0000 (UTC) (envelope-from marcnarc@gmail.com) Received: from mail-qt0-x244.google.com (mail-qt0-x244.google.com [IPv6:2607:f8b0:400d:c0d::244]) (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 1738B6D957; Tue, 24 Apr 2018 14:09:43 +0000 (UTC) (envelope-from marcnarc@gmail.com) Received: by mail-qt0-x244.google.com with SMTP id b13-v6so22186010qtp.12; Tue, 24 Apr 2018 07:09:43 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:cc:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=SNBqNHy/e09dSDqEEZPPUzIoaP3P3B33x3GkMKOytP8=; b=RaNcS1Qm0pZiuS1fNG0ZDZc2TVJYkU+PpNeNE+R4ung0j7HrdXkQkN1005uNePj2JB UjnPpXQ2WHWAm4rItwfT2Nd9N/BswsqfUq7hODcvYoiseb5zkqa2P4dEZo3A3m0om4O0 n4aPbYoGkGTa/ATFuFSWs8cweeOcPDRRnjO8zIqbOIMn7xRlGgfGEroWF40Awxevoa3I Dpsut6a6S+se6yem64jEohmxrNYGWbr0UQCMExnHhxImtkefbGgvgIG+ub4yAhPeoCuw Ev6RGbY7ZWbucEC64rp5jVeK2aFSnbpYyugWmIHF0uQSK2gVSB0QHt0UBO19ECS9UEZY /kYQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:cc:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=SNBqNHy/e09dSDqEEZPPUzIoaP3P3B33x3GkMKOytP8=; b=E8hjpAtsvheEYpieeCkWUPvHAnohMtqWWkHNVDhVgbmDaISebtFJNQAd87DqoI4QEi kicDb6FtcsUdvuZUPK7FEK0ujcadOFpO9srg61mGrgHAyPRGwyIqYQku0fYD3+vz1W1I Nz0yu7jexFNDfw665bbs+ZcPWbd1rOIDSzYhaYdqoM8mgfjGEi9w5/yPZASGLT+kJR1n Q/2o8OAz0P1yneXLT6Bce/ybPBeVRd0TlkKswGarZKBTmgfkXRDVik2bk/Q7NnLi4ehL V/RMwjNHwdEsX39KGFu1HvPxl3sVvddQQ6WLI/ENaZ+2PcrBJFeMLTtFT+gPp6R4j8s6 ZFgg== X-Gm-Message-State: ALQs6tDyT0l6U15uRqiPFobSMaksYm6mqHJ9aSe0QZB5VWhoMexbwhzn fjFMLXQhokA/VnnOMfQ6GQ3+civh X-Google-Smtp-Source: AB8JxZoI26fDmd+8Mc739CWEsYa8F3/PkPjh/2skn00/QpK/qjdkKEJM+/ZrwZs3fQSva4Qak4mCpA== X-Received: by 2002:ac8:2779:: with SMTP id h54-v6mr4992688qth.85.1524578982399; Tue, 24 Apr 2018 07:09:42 -0700 (PDT) Received: from [10.10.1.32] ([192.252.130.194]) by smtp.gmail.com with ESMTPSA id i45-v6sm8437645qta.12.2018.04.24.07.09.41 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 24 Apr 2018 07:09:41 -0700 (PDT) Subject: Re: What should do in chrooted environment? To: Glen Barber , krad References: <201804232228.w3NMS6UW042861@kx.openedu.org> <20180423224408.GC56778@FreeBSD.org> <20180424132452.GB70329@FreeBSD.org> Cc: KIRIYAMA Kazuhiko , "O'Connor, Daniel" , freebsd-stable From: Marc Branchaud Message-ID: <5bfcd662-629c-43f0-0471-141cf6881a1f@gmail.com> Date: Tue, 24 Apr 2018 10:09:40 -0400 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0 MIME-Version: 1.0 In-Reply-To: <20180424132452.GB70329@FreeBSD.org> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit 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, 24 Apr 2018 14:09:43 -0000 On 2018-04-24 09:24 AM, Glen Barber wrote: > There are additional nits regarding jail(8) that chroot(8) does not have > the same limitations. Setting/unsetting the immutable flag on something > like /sbin/init, for example, comes to mind. Try allow.chflags in your jail.conf. M. > Glen > > On Tue, Apr 24, 2018 at 11:49:46AM +0100, krad wrote: >> wouldn't it just be easier to do this in a jail, and then all of these >> little bits would be taken care of? >> >> On 24 April 2018 at 01:48, O'Connor, Daniel wrote: >> >>> >>> >>>> On 24 Apr 2018, at 08:14, Glen Barber wrote: >>>> I think you might not have the devfs mount in the image. With the paths >>>> provided above, I think this should fix it: >>>> >>>> # mount -t devfs devfs /mnt/dev >>> >>> I wonder if it's worth doing a basic sanity check that /dev/null and >>> /dev/zero look like device nodes. >>> >>> I've made this mistake too and it produces some very confusing error >>> messages :( >>> >>> -- >>> Daniel O'Connor >>> "The nice thing about standards is that there >>> are so many of them to choose from." >>> -- Andrew Tanenbaum >>> GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C >>> >>> _______________________________________________ >>> freebsd-stable@freebsd.org mailing list >>> https://lists.freebsd.org/mailman/listinfo/freebsd-stable >>> To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" >>> From owner-freebsd-stable@freebsd.org Tue Apr 24 14:13: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 626B6FA6A7F for ; Tue, 24 Apr 2018 14:13:49 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2610:1c1:1:6074::16:84]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "freefall.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 086746F42B; Tue, 24 Apr 2018 14:13:49 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Received: from FreeBSD.org (freefall.freebsd.org [IPv6:2610:1c1:1:6074::16:84]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by freefall.freebsd.org (Postfix) with ESMTPS id 9507C1DC1E; Tue, 24 Apr 2018 14:13:48 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Date: Tue, 24 Apr 2018 14:13:46 +0000 From: Glen Barber To: Marc Branchaud Cc: krad , KIRIYAMA Kazuhiko , "O'Connor, Daniel" , freebsd-stable Subject: Re: What should do in chrooted environment? Message-ID: <20180424141346.GD70329@FreeBSD.org> References: <201804232228.w3NMS6UW042861@kx.openedu.org> <20180423224408.GC56778@FreeBSD.org> <20180424132452.GB70329@FreeBSD.org> <5bfcd662-629c-43f0-0471-141cf6881a1f@gmail.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="0/kgSOzhNoDC5T3a" Content-Disposition: inline In-Reply-To: <5bfcd662-629c-43f0-0471-141cf6881a1f@gmail.com> User-Agent: Mutt/1.9.1 (2017-09-22) 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, 24 Apr 2018 14:13:49 -0000 --0/kgSOzhNoDC5T3a Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Apr 24, 2018 at 10:09:40AM -0400, Marc Branchaud wrote: > On 2018-04-24 09:24 AM, Glen Barber wrote: > > There are additional nits regarding jail(8) that chroot(8) does not have > > the same limitations. Setting/unsetting the immutable flag on something > > like /sbin/init, for example, comes to mind. >=20 > Try > allow.chflags > in your jail.conf. >=20 Sure, this works, but it requires (IMHO) more "intervention" than a simple devfs(5) mount in the target build environment. Glen > M. >=20 > > Glen > >=20 > > On Tue, Apr 24, 2018 at 11:49:46AM +0100, krad wrote: > > > wouldn't it just be easier to do this in a jail, and then all of these > > > little bits would be taken care of? > > >=20 > > > On 24 April 2018 at 01:48, O'Connor, Daniel wrot= e: > > >=20 > > > >=20 > > > >=20 > > > > > On 24 Apr 2018, at 08:14, Glen Barber wrote: > > > > > I think you might not have the devfs mount in the image. With th= e paths > > > > > provided above, I think this should fix it: > > > > >=20 > > > > > # mount -t devfs devfs /mnt/dev > > > >=20 > > > > I wonder if it's worth doing a basic sanity check that /dev/null and > > > > /dev/zero look like device nodes. > > > >=20 > > > > I've made this mistake too and it produces some very confusing error > > > > messages :( > > > >=20 > > > > -- > > > > Daniel O'Connor > > > > "The nice thing about standards is that there > > > > are so many of them to choose from." > > > > -- Andrew Tanenbaum > > > > GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C > > > >=20 > > > > _______________________________________________ > > > > freebsd-stable@freebsd.org mailing list > > > > https://lists.freebsd.org/mailman/listinfo/freebsd-stable > > > > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebs= d.org" > > > >=20 >=20 --0/kgSOzhNoDC5T3a Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEjRJAPC5sqwhs9k2jAxRYpUeP4pMFAlrfO5oACgkQAxRYpUeP 4pMxJQ/9FluPlsNhn3xBE5kaj5aNF6hoJ/3lsbujBhE/MmLpAU6mcHagfA+w+tC6 g7WPbORGKnb6ciWG/WiobOi1+h8iCAm/JHEeA1rs3FmJ3bQWrolJStVpw8degdE8 36YDRsp+pttOCiEx80NWo3CORXYo/nAj6dipdZD8jc0Uhu94v4oygTXY0Q1NfqDz 6nvTk9b0lWdsBU417uouhGxwB+OdHVMVPjQrvnB6K+Qp5snMjdMLT0tzLMhZCV4T rjIEjMDybXjdsi8KGKbYGGnFGgUU7UCyJp4hKFe9RASeBrsjiAnmgW+WolSTtqPg EFT4zpYzvR1eXfeH8354iVbePVPP3Ui1dQ4NPtVQiPB9bXvS1xF8fu/G4JsKeftu 27wPlviSTkb4Q/zpKmaEzOiZF5rhrMuvmkq/8cxVo1GhaE9jewDKG3vJ9/weldE8 acNzOvvSZL3TnzGjsvcJGuGYjCMlhRRC6GUXrh7Q2N9bkvP4Pq89SFOwrWUZxAzD DEBm0C9ZADTF6dpjPWzCiRLAJ2mKOtwqJg7zx298rzS3+Ru3xfEyIpUkWxeco+7u 0aKRRMoyEmEkS3CmuVomtr4U26/drI8yBT6s7SR6sfwS8WFjNsvW0NdtOZ/NYFHP kXR1FOw8DQu5bCbUhzUKhF6bzIrHsa4ZLSS+HtJwLW3D9mMl2h0= =8wqD -----END PGP SIGNATURE----- --0/kgSOzhNoDC5T3a-- From owner-freebsd-stable@freebsd.org Tue Apr 24 14:22:50 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 03B50FA70B5 for ; Tue, 24 Apr 2018 14:22:50 +0000 (UTC) (envelope-from mike@sentex.net) Received: from smarthost2.sentex.ca (smarthost2.sentex.ca [IPv6:2607:f3e0:80:80::2]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client CN "smarthost.sentex.ca", Issuer "smarthost.sentex.ca" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 8AA3870BE0; Tue, 24 Apr 2018 14:22:49 +0000 (UTC) (envelope-from mike@sentex.net) Received: from lava.sentex.ca (lava.sentex.ca [IPv6:2607:f3e0:0:5::11]) by smarthost2.sentex.ca (8.15.2/8.15.2) with ESMTPS id w3OEMmuv017395 (version=TLSv1 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Tue, 24 Apr 2018 10:22:49 -0400 (EDT) (envelope-from mike@sentex.net) Received: from [192.168.43.26] (saphire3.sentex.net [192.168.43.26]) by lava.sentex.ca (8.15.2/8.15.2) with ESMTP id w3OEMkJF058913; Tue, 24 Apr 2018 10:22:46 -0400 (EDT) (envelope-from mike@sentex.net) Subject: Re: Ryzen issues on FreeBSD ? (with sort of workaround) To: Pete French , nimrodl@gmail.com Cc: truckman@freebsd.org, eric@vangyzen.net, freebsd-stable@freebsd.org, freebsd@hda3.com, avg@freebsd.org References: <59b435cf-f4fb-0cc8-3bd0-0765ac0592da@sentex.net> <84898b9f-991c-420a-3ebd-f8c4ad9915e1@ingresso.co.uk> From: Mike Tancsa Openpgp: preference=signencrypt Organization: Sentex Communications Message-ID: Date: Tue, 24 Apr 2018 10:22:46 -0400 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0 MIME-Version: 1.0 In-Reply-To: <84898b9f-991c-420a-3ebd-f8c4ad9915e1@ingresso.co.uk> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 8bit X-Scanned-By: MIMEDefang 2.78 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, 24 Apr 2018 14:22:50 -0000 On 4/24/2018 10:01 AM, Pete French wrote: > > Well, I ranh the iperf tests between real machine for 24 hours and that > worked fine. I also then spun up a Virtualbox with Win10 in it, and ran > iuperf to there at the same time as doing it betwene real machines, and > also did a full virus scan to exercise the disc. the idea being to > replicate Mondays lockup. I was able to lock it up with vbox. bhyve was just a little easier to script and also I figured would be good to get VBox out of the mix in case it was something specific to VBox. I dont recall if I tried it with SMT disabled. Regardless, on Intel based systems I ran these tests for 72hrs straight without issue. I can sort of believe hardware issue or flaky motherboard BIOSes (2 ASUS MBs, 1 MSI MB, 3 Ryzen chips), but the fact that two server class MBs from SuperMicro along with an Epyc chip also does the same thing makes me think something specific to FreeBSD and this class of AMD CPU :( ---Mike -- ------------------- Mike Tancsa, tel +1 519 651 3400 x203 Sentex Communications, mike@sentex.net Providing Internet services since 1994 www.sentex.net Cambridge, Ontario Canada From owner-freebsd-stable@freebsd.org Tue Apr 24 14:39:19 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 D09C2FA77CD for ; Tue, 24 Apr 2018 14:39:19 +0000 (UTC) (envelope-from petefrench@ingresso.co.uk) Received: from constantine.ingresso.co.uk (unknown [IPv6:2a02:b90:3002:411::3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 6900F75CF2; Tue, 24 Apr 2018 14:39:19 +0000 (UTC) (envelope-from petefrench@ingresso.co.uk) Received: from dilbert.london-internal.ingresso.co.uk ([10.64.50.6]) by constantine.ingresso.co.uk with esmtpsa (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.89 (FreeBSD)) (envelope-from ) id 1fAz6D-000Lbq-6j; Tue, 24 Apr 2018 14:39:17 +0000 Subject: Re: Ryzen issues on FreeBSD ? (with sort of workaround) To: Mike Tancsa , nimrodl@gmail.com Cc: truckman@freebsd.org, eric@vangyzen.net, freebsd-stable@freebsd.org, freebsd@hda3.com, avg@freebsd.org References: <59b435cf-f4fb-0cc8-3bd0-0765ac0592da@sentex.net> <84898b9f-991c-420a-3ebd-f8c4ad9915e1@ingresso.co.uk> From: Pete French Message-ID: <1b210d7d-dcbb-d8d5-ecf9-c2277c90dd9b@ingresso.co.uk> Date: Tue, 24 Apr 2018 15:39:17 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit 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, 24 Apr 2018 14:39:20 -0000 yes, I too think its definitely a Ryzen isssue with FreeBSD - is there a way you could try it (at least on the Desktop) with SMT off ? I havbe the following options tunred off: SMT Glocal C states Cool-n-quiet Core boost The last few obviously tweak processor clocks and thus dont surprise me too much as a soource of instabuloty, but I am surprised that SMT causes issues, as that should (I belive) simply present as two cores. On 24/04/2018 15:22, Mike Tancsa wrote: > On 4/24/2018 10:01 AM, Pete French wrote: >> >> Well, I ranh the iperf tests between real machine for 24 hours and that >> worked fine. I also then spun up a Virtualbox with Win10 in it, and ran >> iuperf to there at the same time as doing it betwene real machines, and >> also did a full virus scan to exercise the disc. the idea being to >> replicate Mondays lockup. > > I was able to lock it up with vbox. bhyve was just a little easier to > script and also I figured would be good to get VBox out of the mix in > case it was something specific to VBox. I dont recall if I tried it > with SMT disabled. Regardless, on Intel based systems I ran these tests > for 72hrs straight without issue. I can sort of believe hardware issue > or flaky motherboard BIOSes (2 ASUS MBs, 1 MSI MB, 3 Ryzen chips), but > the fact that two server class MBs from SuperMicro along with an Epyc > chip also does the same thing makes me think something specific to > FreeBSD and this class of AMD CPU :( > > ---Mike > > From owner-freebsd-stable@freebsd.org Tue Apr 24 14:45:07 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 360F3FA7CCA for ; Tue, 24 Apr 2018 14:45:07 +0000 (UTC) (envelope-from darius@dons.net.au) Received: from ipmail02.adl2.internode.on.net (ipmail02.adl2.internode.on.net [150.101.137.139]) by mx1.freebsd.org (Postfix) with ESMTP id 55A5376877 for ; Tue, 24 Apr 2018 14:45:05 +0000 (UTC) (envelope-from darius@dons.net.au) Received: from ppp121-45-17-192.bras1.adl4.internode.on.net (HELO midget.dons.net.au) ([121.45.17.192]) by ipmail02.adl2.internode.on.net with ESMTP; 25 Apr 2018 00:15:03 +0930 Received: from midget.dons.net.au (localhost [127.0.0.1]) by midget.dons.net.au (8.15.1/8.14.9) with ESMTPS id w3OEiYLU064065 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for ; Wed, 25 Apr 2018 00:14:59 +0930 (CST) (envelope-from darius@dons.net.au) Received: (from mailnull@localhost) by midget.dons.net.au (8.15.1/8.14.9/Submit) id w3OEFFp0046868 for ; Tue, 24 Apr 2018 23:45:15 +0930 (CST) (envelope-from darius@dons.net.au) X-Authentication-Warning: midget.dons.net.au: mailnull set sender to using -f Received: from [10.0.2.26] ([10.0.2.26]) by ns.dons.net.au (envelope-sender ) (MIMEDefang) with ESMTP id w3OEF9Hq046694; Tue, 24 Apr 2018 23:45:15 +0930 Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 11.3 \(3445.6.18\)) Subject: Re: What should do in chrooted environment? From: "O'Connor, Daniel" In-Reply-To: <5bfcd662-629c-43f0-0471-141cf6881a1f@gmail.com> Date: Tue, 24 Apr 2018 23:45:08 +0930 Cc: Glen Barber , krad , KIRIYAMA Kazuhiko , freebsd-stable Content-Transfer-Encoding: quoted-printable Message-Id: <084EA8AE-1228-493E-AD15-DFDE56F056AB@dons.net.au> References: <201804232228.w3NMS6UW042861@kx.openedu.org> <20180423224408.GC56778@FreeBSD.org> <20180424132452.GB70329@FreeBSD.org> <5bfcd662-629c-43f0-0471-141cf6881a1f@gmail.com> To: Marc Branchaud X-Mailer: Apple Mail (2.3445.6.18) X-Spam-Score: -1 () No, score=-1.0 required=5.0 tests=ALL_TRUSTED autolearn=unavailable autolearn_force=no version=3.4.0 X-Scanned-By: MIMEDefang 2.75 on 10.0.2.1 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, 24 Apr 2018 14:45:07 -0000 > On 24 Apr 2018, at 23:39, Marc Branchaud wrote: > On 2018-04-24 09:24 AM, Glen Barber wrote: >> There are additional nits regarding jail(8) that chroot(8) does not = have >> the same limitations. Setting/unsetting the immutable flag on = something >> like /sbin/init, for example, comes to mind. >=20 > Try > allow.chflags > in your jail.conf. I assume that this also isn't checked by the build so you end up wasting = some time as well (but probably only in installworld) I don't see an argument against doing some quick sanity checks before = starting a run (be it buildworld, installworld or whatever). -- Daniel O'Connor "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C From owner-freebsd-stable@freebsd.org Tue Apr 24 15:27:25 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 45354FA9106; Tue, 24 Apr 2018 15:27:25 +0000 (UTC) (envelope-from emaste@freebsd.org) Received: from freefall.freebsd.org (freefall.freebsd.org [96.47.72.132]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "freefall.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id E38DC7F9A3; Tue, 24 Apr 2018 15:27:24 +0000 (UTC) (envelope-from emaste@freebsd.org) Received: by freefall.freebsd.org (Postfix, from userid 1079) id DAC4613325; Tue, 24 Apr 2018 15:27:24 +0000 (UTC) Date: Tue, 24 Apr 2018 15:27:24 +0000 From: Ed Maste To: freebsd-current@freebsd.org, freebsd-stable@freebsd.org Subject: Deprecating the lmc(4) driver Message-ID: <20180424152724.GA30980@freebsd.org> Mail-Followup-To: Ed Maste , freebsd-current@freebsd.org, freebsd-stable@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.9.2 (2017-12-15) 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, 24 Apr 2018 15:27:25 -0000 The lmc(4) driver supports hardware for a number of legacy interfaces, including EIA612/613, T1/E1, T3, etc. The driver's license is ambiguous and attempts to contact the author failed. I would like to remove this driver from 12.0, and have a deprecation notice in review D15182 [1]; I would appreciate hearing from anyone who is currently using lmc(4) in case it is still providing some value. [1] https://reviews.freebsd.org/D15182 From owner-freebsd-stable@freebsd.org Wed Apr 25 00:04:45 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 A99D4FB7CA4 for ; Wed, 25 Apr 2018 00:04:45 +0000 (UTC) (envelope-from truckman@FreeBSD.org) Received: from mx2.catspoiler.org (mx2.catspoiler.org [IPv6:2607:f740:16::d18]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "amnesiac", Issuer "amnesiac" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 41C2C82465 for ; Wed, 25 Apr 2018 00:04:45 +0000 (UTC) (envelope-from truckman@FreeBSD.org) Received: from gw.catspoiler.org ([76.212.85.177]) by mx2.catspoiler.org (8.15.2/8.15.2) with ESMTPS id w3P065x9042939 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=FAIL); Wed, 25 Apr 2018 00:06:06 GMT (envelope-from truckman@FreeBSD.org) Received: from mousie.catspoiler.org (mousie.catspoiler.org [192.168.101.2]) by gw.catspoiler.org (8.15.2/8.15.2) with ESMTPS id w3P04VZc088649 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 24 Apr 2018 17:04:32 -0700 (PDT) (envelope-from truckman@FreeBSD.org) Date: Tue, 24 Apr 2018 17:04:26 -0700 (PDT) From: Don Lewis Subject: Re: Ryzen issues on FreeBSD ? (with sort of workaround) To: Mike Tancsa cc: Pete French , nimrodl@gmail.com, eric@vangyzen.net, freebsd-stable@freebsd.org, freebsd@hda3.com, avg@freebsd.org In-Reply-To: Message-ID: References: <59b435cf-f4fb-0cc8-3bd0-0765ac0592da@sentex.net> <84898b9f-991c-420a-3ebd-f8c4ad9915e1@ingresso.co.uk> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=us-ascii Content-Disposition: INLINE 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: Wed, 25 Apr 2018 00:04:45 -0000 On 24 Apr, Mike Tancsa wrote: > On 4/24/2018 10:01 AM, Pete French wrote: >> >> Well, I ranh the iperf tests between real machine for 24 hours and that >> worked fine. I also then spun up a Virtualbox with Win10 in it, and ran >> iuperf to there at the same time as doing it betwene real machines, and >> also did a full virus scan to exercise the disc. the idea being to >> replicate Mondays lockup. > > I was able to lock it up with vbox. bhyve was just a little easier to > script and also I figured would be good to get VBox out of the mix in > case it was something specific to VBox. I dont recall if I tried it > with SMT disabled. Regardless, on Intel based systems I ran these tests > for 72hrs straight without issue. I can sort of believe hardware issue > or flaky motherboard BIOSes (2 ASUS MBs, 1 MSI MB, 3 Ryzen chips), but > the fact that two server class MBs from SuperMicro along with an Epyc > chip also does the same thing makes me think something specific to > FreeBSD and this class of AMD CPU :( It would be interesting to test other AMD CPUs. I think AMD and Intel have some differences in the virtualization implementations. From owner-freebsd-stable@freebsd.org Wed Apr 25 09:14:09 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 3DE5CFC0EC8 for ; Wed, 25 Apr 2018 09:14:09 +0000 (UTC) (envelope-from petefrench@ingresso.co.uk) Received: from constantine.ingresso.co.uk (unknown [IPv6:2a02:b90:3002:411::3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id D1CE77043D; Wed, 25 Apr 2018 09:14:08 +0000 (UTC) (envelope-from petefrench@ingresso.co.uk) Received: from cpc73666-dals20-2-0-cust303.20-2.cable.virginm.net ([82.47.237.48] helo=foula.drayhouse.twisted.org.uk) by constantine.ingresso.co.uk with esmtpsa (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.89 (FreeBSD)) (envelope-from ) id 1fBGV3-0009eE-Al; Wed, 25 Apr 2018 09:14:05 +0000 Subject: Re: Ryzen issues on FreeBSD ? (with sort of workaround) To: Don Lewis , Mike Tancsa Cc: nimrodl@gmail.com, eric@vangyzen.net, freebsd-stable@freebsd.org, freebsd@hda3.com, avg@freebsd.org References: <59b435cf-f4fb-0cc8-3bd0-0765ac0592da@sentex.net> <84898b9f-991c-420a-3ebd-f8c4ad9915e1@ingresso.co.uk> From: Pete French Message-ID: <3533f777-e708-623d-b280-5be418fd4d50@ingresso.co.uk> Date: Wed, 25 Apr 2018 10:14:04 +0100 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:52.0) Gecko/20100101 Thunderbird/52.7.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-GB Content-Transfer-Encoding: 7bit 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: Wed, 25 Apr 2018 09:14:09 -0000 > It would be interesting to test other AMD CPUs. I think AMD and Intel > have some differences in the virtualization implementations. I've been using AMD CPU's pretty extensively since the early 90's - back then I was running NeXTStep and out of the three Intel alternatives it was the only one which ran properly. Never seen anything like this before now though. In particular this Ryzen replaces the CPU on an old Phenom II - i.e. its the same disc and hence the same OS and VirtualBox config - and that ran fine. So theres something odd about the Ryzen here. Am also not sure its to do with the virtualisation - I got my first lockup with no virtualisation going on at all. Disablign SMT and the system hasnt locked, despite heavy virtualbox use. -pete. From owner-freebsd-stable@freebsd.org Wed Apr 25 12:15:10 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 3E5C1FA433A for ; Wed, 25 Apr 2018 12:15:10 +0000 (UTC) (envelope-from matheus@eternamente.info) Received: from hobbes.arroway.org (hobbes.arroway.org [173.199.118.77]) by mx1.freebsd.org (Postfix) with ESMTP id D7833786BF for ; Wed, 25 Apr 2018 12:15:09 +0000 (UTC) (envelope-from matheus@eternamente.info) Received: from net.dyn.arroway.org (unknown [177.89.5.111]) by hobbes.arroway.org (Postfix) with ESMTPA id C64623AC84 for ; Wed, 25 Apr 2018 09:15:01 -0300 (BRT) Received: from 186.229.5.58 (SquirrelMail authenticated user matheus) by net.dyn.arroway.org with HTTP; Wed, 25 Apr 2018 09:15:03 -0300 Message-ID: In-Reply-To: <55533ad671792b7a30ff00cd1659a02b.squirrel@10.1.1.10> References: <55533ad671792b7a30ff00cd1659a02b.squirrel@10.1.1.10> Date: Wed, 25 Apr 2018 09:15:03 -0300 Subject: Re: Two USB 4 disk enclosure and a panic From: "Nenhum_de_Nos" To: freebsd-stable@freebsd.org User-Agent: SquirrelMail/1.4.23 [SVN] MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal 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: Wed, 25 Apr 2018 12:15:10 -0000 On Mon, April 23, 2018 23:18, Nenhum_de_Nos wrote: > Hi, > > I would like to know how to debug this. I have two 4 disk enclosures: > > Mediasonic ProBox 4 Bay 3.5' SATA HDD Enclosure – USB 3.0 & eSATA > (HF2-SU3S2) > NexStar HX4 - NST-640SU3-BK > > and both have 4 disk on them, and not all disk are equal. > > The issue comes when I plug the probox usb3 enclosure on the system. I > can't even read the /var/log/message, it crashes very quickly. > > I can see on the boot process up to the point where the second enclosure > comes to be loaded. The 4 disk are shown on the dmesg/console, and then a > core dump happens, the boot process goes to the debug screen and a restart > happens like a flash. > > The motherboard is a Intel® Desktop Board D525MW running 8GB RAM. > All disk use ZFS, 4 or 5 zpools, one raidz, one mirror and two or three > single disk pools. > FreeBSD xxx 11.1-RELEASE-p7 FreeBSD 11.1-RELEASE-p7 #1 r330596: Thu Mar 8 > 06:45:59 -03 2018 root@xxx:/usr/obj/usr/src/sys/FreeBSD-11-amd64-PF > amd64 > > The kernel is a slightly modified generic, just to have altq. > > How can I debug this? I have no idea. I have to use two machines to run > all those disks, and I would really like to have just one for it. > > Can it be the amount of RAM? The other box is and APU2 from PCEngines and > have 4GB ram. apu2 uname -a: FreeBSD yyy 11.1-RELEASE-p4 FreeBSD > 11.1-RELEASE-p4 #0: Tue Nov 14 06:12:40 UTC 2017 > root@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64 > > I tried to plug the Vantec hardware on the apu2 box, but there it would > not panic, but won't load all vantec disks neither. I really run out of > ideas here :( > > thanks. > > -- > "We will call you Cygnus, > the God of balance you shall be." Hi, I found some logs on the daily security output: +ZFS filesystem version: 5 +ZFS storage pool version: features support (5000) +panic: Solaris(panic): blkptr at 0xfffff8000b93c848 DVA 1 has invalid VDEV 1 +cpuid = 0 +KDB: stack backtrace: +#0 0xffffffff80ab65c7 at kdb_backtrace+0x67 +#1 0xffffffff80a746a6 at vpanic+0x186 +#2 0xffffffff80a74513 at panic+0x43 +#3 0xffffffff82623192 at vcmn_err+0xc2 +#4 0xffffffff824a73ba at zfs_panic_recover+0x5a +#5 0xffffffff824ce893 at zfs_blkptr_verify+0x2d3 +#6 0xffffffff824ce8dc at zio_read+0x2c +#7 0xffffffff82445fb4 at arc_read+0x6c4 +#8 0xffffffff824636a4 at dmu_objset_open_impl+0xd4 +#9 0xffffffff8247eafa at dsl_pool_init+0x2a +#10 0xffffffff8249b093 at spa_load+0x823 +#11 0xffffffff8249a2de at spa_load_best+0x6e +#12 0xffffffff82496a81 at spa_open_common+0x101 +#13 0xffffffff824e2879 at pool_status_check+0x29 +#14 0xffffffff824eba3d at zfsdev_ioctl+0x4ed +#15 0xffffffff809429f8 at devfs_ioctl_f+0x128 +#16 0xffffffff80ad1f15 at kern_ioctl+0x255 +CPU: Intel(R) Atom(TM) CPU D525 @ 1.80GHz (1800.11-MHz K8-class CPU) +avail memory = 8246845440 (7864 MB) +Timecounter "TSC" frequency 1800110007 Hz quality 1000 +GEOM_PART: integrity check failed (ada0s1, BSD) +GEOM_PART: integrity check failed (diskid/DISK-5LZ0ZDBBs1, BSD) +ugen1.2: at usbus1 +ukbd0 on uhub0 +ukbd0: on usbus1 +kbd2 at ukbd0 +ZFS filesystem version: 5 +ZFS storage pool version: features support (5000) +re0: link state changed to DOWN +uhid0 on uhub0 +uhid0: on usbus1 +ums0 on uhub0 +ums0: on usbus1 +ums0: 3 buttons and [XYZ] coordinates ID=0 +re0: promiscuous mode enabled +re0: link state changed to UP For what I see can be ZFS related. If anyone have any hints, please tell :) I kinda got curious about this: +ZFS storage pool version: features support (5000) How can I figure out if my pools are from different versions and may this be the culprit here? thanks, matheus -- "We will call you Cygnus, the God of balance you shall be." From owner-freebsd-stable@freebsd.org Wed Apr 25 13:39:10 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 0A860FA6597 for ; Wed, 25 Apr 2018 13:39:10 +0000 (UTC) (envelope-from mike@sentex.net) Received: from smarthost2.sentex.ca (smarthost2.sentex.ca [IPv6:2607:f3e0:80:80::2]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client CN "smarthost.sentex.ca", Issuer "smarthost.sentex.ca" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 82C6669475; Wed, 25 Apr 2018 13:39:09 +0000 (UTC) (envelope-from mike@sentex.net) Received: from lava.sentex.ca (lava.sentex.ca [IPv6:2607:f3e0:0:5::11]) by smarthost2.sentex.ca (8.15.2/8.15.2) with ESMTPS id w3PDd8Wi043700 (version=TLSv1 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Wed, 25 Apr 2018 09:39:08 -0400 (EDT) (envelope-from mike@sentex.net) Received: from [192.168.43.26] (saphire3.sentex.ca [192.168.43.26]) by lava.sentex.ca (8.15.2/8.15.2) with ESMTP id w3PDd6if065703; Wed, 25 Apr 2018 09:39:06 -0400 (EDT) (envelope-from mike@sentex.net) Subject: Re: Ryzen issues on FreeBSD ? (with sort of workaround) To: Don Lewis Cc: Pete French , nimrodl@gmail.com, eric@vangyzen.net, freebsd-stable@freebsd.org, freebsd@hda3.com, avg@freebsd.org References: <59b435cf-f4fb-0cc8-3bd0-0765ac0592da@sentex.net> <84898b9f-991c-420a-3ebd-f8c4ad9915e1@ingresso.co.uk> From: Mike Tancsa Openpgp: preference=signencrypt Organization: Sentex Communications Message-ID: <3bb5fef2-381c-8e1b-21dc-6b8687fb6c1e@sentex.net> Date: Wed, 25 Apr 2018 09:39:06 -0400 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.78 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: Wed, 25 Apr 2018 13:39:10 -0000 On 4/24/2018 8:04 PM, Don Lewis wrote: >> >> I was able to lock it up with vbox. bhyve was just a little easier to >> script and also I figured would be good to get VBox out of the mix in >> case it was something specific to VBox. I dont recall if I tried it >> with SMT disabled. Regardless, on Intel based systems I ran these tests >> for 72hrs straight without issue. I can sort of believe hardware issue >> or flaky motherboard BIOSes (2 ASUS MBs, 1 MSI MB, 3 Ryzen chips), but >> the fact that two server class MBs from SuperMicro along with an Epyc >> chip also does the same thing makes me think something specific to >> FreeBSD and this class of AMD CPU :( > > It would be interesting to test other AMD CPUs. I think AMD and Intel > have some differences in the virtualization implementations. I dont have any Opterons handy unfortunately. However, I have a feeling its not so much due to virtualization, as I am pretty sure I had a crash when I wasnt doing any VM testing as well. Peter Grehan speculated it might have something to do with a lot of IPIs being generated. Are there any non VM workloads that will generate many IPIs ? ---Mike -- ------------------- Mike Tancsa, tel +1 519 651 3400 x203 Sentex Communications, mike@sentex.net Providing Internet services since 1994 www.sentex.net Cambridge, Ontario Canada From owner-freebsd-stable@freebsd.org Wed Apr 25 14:38:53 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 C7604FA79BF for ; Wed, 25 Apr 2018 14:38:52 +0000 (UTC) (envelope-from bounce@ims11.isendservice.com.br) Received: from ims11.isendservice.com.br (ims11.isendservice.com.br [54.232.115.234]) by mx1.freebsd.org (Postfix) with ESMTP id 4144273B0D for ; Wed, 25 Apr 2018 14:38:52 +0000 (UTC) (envelope-from bounce@ims11.isendservice.com.br) Received: from localhost (localhost [127.0.0.1]) by ims11.isendservice.com.br (Postfix) with ESMTP id C3F5846AC0 for ; Wed, 25 Apr 2018 11:03:20 -0300 (BRT) Date: Wed, 25 Apr 2018 11:03:20 -0300 (BRT) From: FIERGS | FATEC - Faculdade SENAI de Tecnologia Reply-To: posgraduacao@senairs.org.br To: freebsd-stable@freebsd.org Message-ID: <1227290439.521172.1524665000647.JavaMail.root@ims11> Subject: =?ISO-8859-1?Q?P=F3s-gradua=E7=E3o_em_Engenharia_de_?= =?ISO-8859-1?Q?Automa=E7=E3o_e_Controle_Industrial?= bounce-key: <2420-22522874-2152873> MIME-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 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: Wed, 25 Apr 2018 14:38:53 -0000 From owner-freebsd-stable@freebsd.org Wed Apr 25 17:04:04 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 475C9FAA962 for ; Wed, 25 Apr 2018 17:04:04 +0000 (UTC) (envelope-from Andre.Albsmeier@siemens.com) Received: from thoth.sbs.de (thoth.sbs.de [192.35.17.2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "thoth.sbs.de", Issuer "Siemens Issuing CA Internet Server 2017" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 7598D71D96 for ; Wed, 25 Apr 2018 17:04:02 +0000 (UTC) (envelope-from Andre.Albsmeier@siemens.com) Received: from mail2.siemens.de (mail2.siemens.de [139.25.208.11]) by thoth.sbs.de (8.15.2/8.15.2) with ESMTPS id w3PGweMb023720 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK) for ; Wed, 25 Apr 2018 18:58:40 +0200 Received: from curry.mchp.siemens.de (curry.mchp.siemens.de [139.25.40.130]) by mail2.siemens.de (8.15.2/8.15.2) with ESMTP id w3PGwera004550 for ; Wed, 25 Apr 2018 18:58:40 +0200 Received: (from user@localhost) by curry.mchp.siemens.de (8.15.2/8.15.2) id w3PGweoH032834; Date: Wed, 25 Apr 2018 18:58:40 +0200 From: Andre Albsmeier To: freebsd-stable@freebsd.org Cc: Andre.Albsmeier@siemens.com Subject: gptboot broken when compiled with clang 6 and WITHOUT_LOADER_GELI -- clang 5 is OK Message-ID: <20180425165840.GA1330@bali> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.7.2 (2016-11-26) 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: Wed, 25 Apr 2018 17:04:04 -0000 I have set up a new system disk for an i386 11.2-PRERELEASE box. I did the usual gpart create -s gpt $disk gpart add -t freebsd-boot -s 984 $disk gpart bootcode -b /boot/pmbr -p /boot/gptboot -i 1 $disk ... thing, just to notice that the box wouldn't boot. It seems to hang where stage 2 should be run -- when the '\' should start spinning the screen turns white and the box hangs (tested on two machines, an Asus P5W and a Supermicro A2SAV). So I replaced gptboot on the new disk by the one from an older machine and everything was fine. I wanted to find out what is actually causing the issue and recompiled /usr/src/stand after updating the old sources in several steps. Eventually it turned out that it depends on the compiler. When compiling the latest /usr/src/stand with clang 5.0.1 the resulting gptboot works. When using 6.0.0 it doesn't. To be exact, it's gptboot.o which is causing the problems. When using a gptboot.o from a clang 5 system it is OK, when using a gptboot.o from a clang 6 system it fails. To add more confusion: I usually have WITHOUT_LOADER_GELI in my make.conf. When removing this, the resulting gptboot works even when compiled with clang 6... I can reproduce this in case s.o. wants me to do some tests... From owner-freebsd-stable@freebsd.org Wed Apr 25 19:56:13 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 6F043FAE755 for ; Wed, 25 Apr 2018 19:56:13 +0000 (UTC) (envelope-from marcnarc@gmail.com) Received: from mail-qt0-x22b.google.com (mail-qt0-x22b.google.com [IPv6:2607:f8b0:400d:c0d::22b]) (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 04F2E7870F for ; Wed, 25 Apr 2018 19:56:13 +0000 (UTC) (envelope-from marcnarc@gmail.com) Received: by mail-qt0-x22b.google.com with SMTP id d3-v6so28482984qth.8 for ; Wed, 25 Apr 2018 12:56:13 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:from:to:references:message-id:date:user-agent:mime-version :in-reply-to:content-language:content-transfer-encoding; bh=hrYT7W7/vbN9L8iG6ynkkVDNfqi7A9ETROP9A6dBsC8=; b=Pxq26V5lzDqDy1HzJOiWF4xd3gloEl7kpJB3Fp1C+47Z6RLvMnVw35cUqxkhomJc5Q heIkjSUJmKj/rNl90yLUpGUnSWhS3BkgyiazrZP+FGqa3En3mzOBOjAHhhlhBBIGDsSI Fv/GvstqYhfW52zSvgZQzdKJkOgze7ksZFx3w3LzdF49nJtBKC9Ao2/zXxy9xy/6itaB g3Lm6pj3M3ZOqpQkmzCd1TEUISuqR1TfbdP41ij3ri9F1MLOWUBu8ca48X32HGmFHE7x h/VTJrbvQxHutqcVCkTrkXas+rxw1S9Uq9IKKZpUBXMhYd5+UtStUYm1Zu2jUWIyrKWw bdqQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:from:to:references:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=hrYT7W7/vbN9L8iG6ynkkVDNfqi7A9ETROP9A6dBsC8=; b=jk39fFvAQqwsmnOnppW0o0cOItcgN4aZ368G+s1Mp3hgNAZgj93rC09GgOrgvf5FM8 7taPWHiERC30TRc2inH1ZAUU9AE48D/YuGyq8tCmD5VP8PbPl/MDsEKUL3BWximGvKkQ Sr9+1hIkIqigqrq2+Ff2IoKzo7bqXE4C4mVsVKvbcudxCZwy7AxuQThaR02bPpj393RG EUX7BigugtWETrnclyPgW4BvqcYHnen1sq9Z1GkrrRaxTRMC4qVF8IJQDCX9Z9sk5AE3 U9EQ2jIZ9JUXiZx6oeUtky3BS1vG188G6rsswOmRhi/LItKYiCPCaATgMwZwvhK057pD DpKA== X-Gm-Message-State: ALQs6tC3RB+yOK5FaWnzsD5zhp+IGbzxhg/rsClu16Yir+z6JzIkcd7B O6XsJYFWg35f4Zk0T+IEn//RyQ== X-Google-Smtp-Source: AIpwx4+XLPDNlTKz2/xXIP1svvWloUPQYysgL0HbFW+d3WczXaR2i9sywNXQ1WQ3F9ypgjtLwDcGfw== X-Received: by 2002:ac8:2c8b:: with SMTP id 11-v6mr31969194qtw.160.1524686172269; Wed, 25 Apr 2018 12:56:12 -0700 (PDT) Received: from [192.168.222.13] (cable-192.222.220.61.electronicbox.net. [192.222.220.61]) by smtp.googlemail.com with ESMTPSA id d52-v6sm16384309qta.25.2018.04.25.12.56.11 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 25 Apr 2018 12:56:11 -0700 (PDT) Subject: Re: Problems with ifconfig when starting all jails after 10.3 -> 10.4 upgrade From: Marc Branchaud To: freebsd-stable@FreeBSD.ORG References: <45483fb3-bd94-10f1-a75c-3a035ec69cfa@gmail.com> <94c4e3f3-dac5-2958-3ad4-b4c43e4d21cf@gmail.com> Message-ID: Date: Wed, 25 Apr 2018 15:56:10 -0400 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0 MIME-Version: 1.0 In-Reply-To: <94c4e3f3-dac5-2958-3ad4-b4c43e4d21cf@gmail.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-CA Content-Transfer-Encoding: 8bit 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: Wed, 25 Apr 2018 19:56:13 -0000 On 2018-04-06 02:26 PM, Marc Branchaud wrote: > On 2018-04-05 10:28 AM, Marc Branchaud wrote: >> Hi all, >> >> I just upgraded from 10.3 to 10.4, and "/etc/rc.d/jail start" is >> having problems starting all of my jails: >> >> # /etc/rc.d/jail start >> Starting jails:xipbuild_3_3: created >> ifconfig:: bad value >> jail: xipbuild_3_3_8: /sbin/ifconfig lo1 inet 10.1.1.38/32 alias: failed >> xipbuild_3_4: created >> ifconfig:: bad value >> jail: xipbuild_4_0: /sbin/ifconfig lo1 inet 10.1.1.5/32 alias: failed >> xipbuild: created >> xipbuild_4_9: created >> ifconfig:: bad value >> jail: xipbuild9: /sbin/ifconfig lo1 inet 10.1.1.209/32 alias: failed >> . > > More info: Things work fine with jail_parallel_start="YES". > > In 10.4, /etc/rc.d/jail now adds "-p1" to the jail command's arguments > when starting all jails with jail_parallel_start="NO".  It's definitely > this parameter that's causing my problems -- changing /etc/rc.d/jail to > not add the parameter fixes the problem. The problem stems from work for bug 209112, a patch for which (r302857) was MFC'd to stable-10. I've added a comment to bug 209112. M. >         M. > > >> This worked fine in 10.3.  I can individually start each jail, e.g. >> "/etc/rc.d/jail start xipbuild9". >> >> All the jails configure the same set of parameters.  Here's my jail.conf: >> >> --- 8< --- 8< --- 8< --- 8< --- 8< --- 8< --- 8< --- 8< --- >> xipbuild_3_3 { >>    path="/usr/build-jails/jails/3.3"; >>    host.hostname="xipbuild_3_3"; >>    ip4.addr="10.1.1.3/32"; >> >>    allow.chflags; >>    allow.mount; >>    mount.devfs; >> >>    persist; >> >>    mount="/usr/home  /usr/build-jails/jails/3.3/usr/home nullfs rw 0 0"; >>    interface="lo1"; >> } >> xipbuild_3_3_8 { >>    path="/usr/build-jails/jails/3.3.8"; >>    host.hostname="xipbuild_3_3_8"; >>    ip4.addr="10.1.1.38/32"; >> >>    allow.chflags; >>    allow.mount; >>    mount.devfs; >> >>    persist; >> >>    mount="/usr/home  /usr/build-jails/jails/3.3.8/usr/home nullfs rw 0 >> 0"; >>    interface="lo1"; >> } >> xipbuild_3_4 { >>    path="/usr/build-jails/jails/3.4"; >>    host.hostname="xipbuild_3_4"; >>    ip4.addr="10.1.1.4/32"; >> >>    allow.chflags; >>    allow.mount; >>    mount.devfs; >> >>    persist; >> >>    mount="/usr/home  /usr/build-jails/jails/3.4/usr/home nullfs rw 0 0"; >>    interface="lo1"; >> } >> xipbuild_4_0 { >>    path="/usr/build-jails/jails/4.0"; >>    host.hostname="xipbuild_4_0"; >>    ip4.addr="10.1.1.5/32"; >> >>    allow.chflags; >>    allow.mount; >>    mount.devfs; >> >>    persist; >> >>    mount="/usr/home  /usr/build-jails/jails/4.0/usr/home nullfs rw 0 0"; >>    interface="lo1"; >> } >> xipbuild { >>    path="/usr/build-jails/jails/latest"; >>    host.hostname="xipbuild"; >>    ip4.addr="10.1.1.200/32"; >> >>    allow.chflags; >>    allow.mount; >>    mount.devfs; >> >>    persist; >> >>    mount="/usr/home  /usr/build-jails/jails/latest/usr/home nullfs rw >> 0 0"; >>    interface="lo1"; >> } >> xipbuild_4_9 { >>    path="/usr/build-jails/jails/4.9"; >>    host.hostname="xipbuild_4_9"; >>    ip4.addr="10.1.1.90/32"; >> >>    allow.chflags; >>    allow.mount; >>    mount.devfs; >> >>    persist; >> >>    mount="/usr/home  /usr/build-jails/jails/4.9/usr/home nullfs rw 0 0"; >>    interface="lo1"; >> } >> xipbuild9 { >>    path="/usr/build-jails/jails/latest9"; >>    host.hostname="xipbuild9"; >>    ip4.addr="10.1.1.209/32"; >> >>    allow.chflags; >>    allow.mount; >>    mount.devfs; >> >>    persist; >> >>    mount="/usr/home  /usr/build-jails/jails/latest9/usr/home nullfs rw >> 0 0"; >>    interface="lo1"; >> } >> --- 8< --- 8< --- 8< --- 8< --- 8< --- 8< --- 8< --- 8< --- >> >> I use ipnat to give the jails network access.  Here's ipnat.rules: >> >> --- 8< --- 8< --- 8< --- 8< --- 8< --- 8< --- 8< --- 8< --- >> map em0 10.1.1.0/24 -> 0/32 proxy port ftp ftp/tcp >> map em0 10.1.1.0/24 -> 0/32 >> --- 8< --- 8< --- 8< --- 8< --- 8< --- 8< --- 8< --- 8< --- >> >> And here's my rc.conf: >> >> --- 8< --- 8< --- 8< --- 8< --- 8< --- 8< --- 8< --- 8< --- >> # Generated by Ansible >> >> # hostname must be FQDN >> hostname="devastator.xiplink.com" >> >> zfs_enable="False" >> >> # FIXME: previously auto-created? >> ifconfig_lo1="create" >> >> >> ifconfig_em0="DHCP SYNCDHCP" >> >> network_interfaces="em0" >> gateway_enable="YES" >> >> # Prevent rpc >> rpcbind_enable="NO" >> >> # Prevent sendmail to try to connect to localhost >> sendmail_enable="NO" >> sendmail_submit_enable="NO" >> sendmail_outbound_enable="NO" >> sendmail_msp_queue_enable="NO" >> >> # Bring up sshd, it takes some time and uses some entropy on first >> startup >> sshd_enable="YES" >> >> netwait_enable="YES" >> netwait_ip="10.10.0.35" >> netwait_if="em0" >> >> jenkins_swarm_enable="YES" >> jenkins_swarm_opts="-executors 8" >> >> # --- Build jails --- >> build_jails_enable="YES" >> jail_enable="YES" >> >> # Set rules in /etc/ipnat.rules >> ipnat_enable="YES" >> >> # Set interface name for ipnat >> network_interfaces="${network_interfaces} lo1" >> >> # Each jail needs to specify its IP address and mask bits in >> ipv4_addrs_lo1 >> ipv4_addrs_lo1="10.1.1.1/32" >> >> jail_chflags_allow="yes" >> >> varmfs="NO" >> --- 8< --- 8< --- 8< --- 8< --- 8< --- 8< --- 8< --- 8< --- >> >> Any insight would be deeply appreciated! >> >>          M. From owner-freebsd-stable@freebsd.org Wed Apr 25 23:26:30 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 7B996FB2BB5 for ; Wed, 25 Apr 2018 23:26:30 +0000 (UTC) (envelope-from dewayne.geraghty@heuristicsystems.com.au) Received: from hermes.heuristicsystems.com.au (hermes.heuristicsystems.com.au [203.41.22.115]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "hermes.heuristicsystems.com.au", Issuer "Heuristic Systems Type 4 Host CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id B0FE184612 for ; Wed, 25 Apr 2018 23:26:28 +0000 (UTC) (envelope-from dewayne.geraghty@heuristicsystems.com.au) Received: from [10.0.5.3] (noddy.hs [10.0.5.3]) (authenticated bits=0) by hermes.heuristicsystems.com.au (8.15.2/8.15.2) with ESMTPSA id w3PN4uPO056928 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NOT); Thu, 26 Apr 2018 09:04:56 +1000 (AEST) (envelope-from dewayne.geraghty@heuristicsystems.com.au) X-Authentication-Warning: b3.hs: Host noddy.hs [10.0.5.3] claimed to be [10.0.5.3] Subject: Re: gptboot broken when compiled with clang 6 and WITHOUT_LOADER_GELI -- clang 5 is OK To: Andre.Albsmeier@siemens.com References: <20180425165840.GA1330@bali> From: Dewayne Geraghty Cc: freebsd-stable@freebsd.org Message-ID: <181c9164-9c03-1a85-1210-f2878435c20c@heuristicsystems.com.au> Date: Thu, 26 Apr 2018 09:04:56 +1000 User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 In-Reply-To: <20180425165840.GA1330@bali> Content-Language: en-AU MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 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: Wed, 25 Apr 2018 23:26:30 -0000 From owner-freebsd-stable@freebsd.org Thu Apr 26 04:18:50 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 65A58FBF842 for ; Thu, 26 Apr 2018 04:18:50 +0000 (UTC) (envelope-from dewayne.geraghty@heuristicsystems.com.au) Received: from hermes.heuristicsystems.com.au (hermes.heuristicsystems.com.au [203.41.22.115]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "hermes.heuristicsystems.com.au", Issuer "Heuristic Systems Type 4 Host CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 8BD5B684F8 for ; Thu, 26 Apr 2018 04:18:48 +0000 (UTC) (envelope-from dewayne.geraghty@heuristicsystems.com.au) Received: from [10.0.5.3] (noddy.hs [10.0.5.3]) (authenticated bits=0) by hermes.heuristicsystems.com.au (8.15.2/8.15.2) with ESMTPSA id w3Q4HwrS018772 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NOT); Thu, 26 Apr 2018 14:17:59 +1000 (AEST) (envelope-from dewayne.geraghty@heuristicsystems.com.au) X-Authentication-Warning: b3.hs: Host noddy.hs [10.0.5.3] claimed to be [10.0.5.3] Subject: Re: gptboot broken when compiled with clang 6 and WITHOUT_LOADER_GELI -- clang 5 is OK To: Andre Albsmeier References: <20180425165840.GA1330@bali> Cc: freebsd-stable@freebsd.org, Dewayne From: Dewayne Geraghty Message-ID: Date: Thu, 26 Apr 2018 14:17:58 +1000 User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: <20180425165840.GA1330@bali> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Content-Language: en-AU 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: Thu, 26 Apr 2018 04:18:50 -0000 Andre, You're not alone.  I think there's a problem with clang6 on i386 FreeBSD 11.1X, refer: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227552 https://forums.freebsd.org/threads/uptime-w-i386-breakage.65584/ and perhaps also on amd64, search for https://bugs.freebsd.org/bugzilla/buglist.cgi?quicksearch=clang&list_id=226390. Without time to investigate I've reverted userland FreeBSD 11.2-PRERELEASE  r332843M    amd64 1101515 1101509 FreeBSD 11.2-PRERELEASE  r332843M    i386 1101515 1101509 Apologies for my earlier email, I'd missed setting content-type: text/plain instead of text/html (the latter strips content to the mailing list), too many management memo's! ;) From owner-freebsd-stable@freebsd.org Thu Apr 26 07:28:16 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 AEE9AFA3F1C; Thu, 26 Apr 2018 07:28:16 +0000 (UTC) (envelope-from eugene@zhegan.in) Received: from elf.hq.norma.perm.ru (mail.norma.perm.ru [IPv6:2a00:7540:1::5]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.norma.perm.ru", Issuer "Vivat-Trade UNIX Root CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 00D2875191; Thu, 26 Apr 2018 07:28:15 +0000 (UTC) (envelope-from eugene@zhegan.in) Received: from bsdrookie.norma.com. (asterisk.enaza.ru [91.237.76.254]) by elf.hq.norma.perm.ru (8.15.2/8.15.2) with ESMTPS id w3Q7S9dF027301 (version=TLSv1.2 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Thu, 26 Apr 2018 12:28:09 +0500 (YEKT) (envelope-from eugene@zhegan.in) To: freebsd-stable@freebsd.org Cc: freebsd-fs@freebsd.org From: "Eugene M. Zheganin" Subject: clear old pools remains from active vdevs Message-ID: Date: Thu, 26 Apr 2018 12:28:09 +0500 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.1.1 MIME-Version: 1.0 Content-Type: text/plain; charset=koi8-r; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-US X-Spamd-Result: default: False [-998.10 / 25.00] WHITELISTED_IPS(-999.00)[91.237.76.254] MIME_GOOD(-0.10)[text/plain] AUTH_NA(1.00)[] R_DKIM_NA(0.00)[] ASN(0.00)[asn:57973, ipnet:91.237.76.0/24, country:RU] RCVD_TLS_ALL(0.00)[] DMARC_NA(0.00)[zhegan.in] TO_MATCH_ENVRCPT_ALL(0.00)[] TO_DN_NONE(0.00)[] RCPT_COUNT_TWO(0.00)[2] RCVD_COUNT_TWO(0.00)[2] MID_RHS_MATCH_FROM(0.00)[] R_SPF_NA(0.00)[] FROM_HAS_DN(0.00)[] ARC_NA(0.00)[] FROM_EQ_ENVFROM(0.00)[] IP_SCORE(0.00)[ip: (-9.89), ipnet: 91.237.76.0/24(-7.83), asn: 57973(-4.90), country: RU(0.13)] X-Rspamd-Server: localhost X-Rspamd-Scan-Time: 1.79 X-Rspamd-Queue-ID: w3Q7S9dF027301 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: Thu, 26 Apr 2018 07:28:16 -0000 Hello, I have some active vdev disk members that used to be in pool that clearly have not beed destroyed properly, so I'm seeing in a "zpool import" output something like # zpool import pool: zroot id: 14767697319309030904 state: UNAVAIL status: The pool was last accessed by another system. action: The pool cannot be imported due to damaged devices or data. see: http://illumos.org/msg/ZFS-8000-EY config: zroot UNAVAIL insufficient replicas mirror-0 UNAVAIL insufficient replicas 5291726022575795110 UNAVAIL cannot open 2933754417879630350 UNAVAIL cannot open pool: esx id: 8314148521324214892 state: UNAVAIL status: The pool was last accessed by another system. action: The pool cannot be imported due to damaged devices or data. see: http://illumos.org/msg/ZFS-8000-EY config: esx UNAVAIL insufficient replicas mirror-0 UNAVAIL insufficient replicas 10170732803757341731 UNAVAIL cannot open 9207269511643803468 UNAVAIL cannot open is there any _safe_ way to get rid of this ? I'm asking because a gptzfsboot loader in recent -STABLE stumbles upon this and refuses to boot the system (https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227772). The workaround is to use the 11.1 loader, but I'm afraid this behavior will now be the intended one. Eugene. From owner-freebsd-stable@freebsd.org Thu Apr 26 07:50:28 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 05CABFA47ED; Thu, 26 Apr 2018 07:50:28 +0000 (UTC) (envelope-from agapon@gmail.com) Received: from mail-lf0-f48.google.com (mail-lf0-f48.google.com [209.85.215.48]) (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 549F17AAA1; Thu, 26 Apr 2018 07:50:27 +0000 (UTC) (envelope-from agapon@gmail.com) Received: by mail-lf0-f48.google.com with SMTP id h197-v6so1878363lfg.11; Thu, 26 Apr 2018 00:50:27 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:openpgp:autocrypt :message-id:date:user-agent:mime-version:in-reply-to :content-language:content-transfer-encoding; bh=gge1vlSNmEqNc7dBcPyGaa0iUGie1vC2NsgndxPkosw=; b=FU5fBfZALOg4iHk0I3LEmYsDOlx8sLsTxFm2zl40I128+ifjg4PGfJkLfyx2+JtsLA Y6VFTrtb75DhOSRTqi5I/pto6EpRY0axJQrTCN8mORFgwTZlWBs2HAWgA7DzXppE401P zSHOx6OTiHLUfnFV6mbdeV/Bn0akIPV878C6zkq/aNM0eMVeX/K0YIEGU59DzmuS9rTI V+5KwH0LXgDeBuZ08DNC6qSeCaP5KIjbPKki8xMEr4EdzQaem4ehulLSfDdQj9euSmrW 7vxlUsCdWvAeMIGNqQmKgCM0r5oyrbEnQvYyOyc3WT0USK6QA31fQIe6+0o6m08pQlS/ Lj1A== X-Gm-Message-State: ALQs6tD4ZFXmEeWifZGJCWUL7C2m7cyvBtoq/+IU0za6iKIomJVgeTZd C01drf2sVxw1/OlNruAOliBG1NWr X-Google-Smtp-Source: AB8JxZoEZ3koAm3M0cNi/9bX/PVjdHVFKu727h0GYifFKwYb7MogVF0sP3eSTP1wqVUOEoGYjynKFQ== X-Received: by 10.46.5.200 with SMTP id 191mr1843847ljf.136.1524729019823; Thu, 26 Apr 2018 00:50:19 -0700 (PDT) Received: from [192.168.0.88] (east.meadow.volia.net. [93.72.151.96]) by smtp.googlemail.com with ESMTPSA id e23-v6sm4308156lfi.58.2018.04.26.00.50.18 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 26 Apr 2018 00:50:19 -0700 (PDT) Subject: Re: clear old pools remains from active vdevs To: "Eugene M. Zheganin" , freebsd-stable@freebsd.org Cc: freebsd-fs@freebsd.org References: From: Andriy Gapon Openpgp: preference=signencrypt Autocrypt: addr=avg@FreeBSD.org; prefer-encrypt=mutual; keydata= xsFNBFm4LIgBEADNB/3lT7f15UKeQ52xCFQx/GqHkSxEdVyLFZTmY3KyNPQGBtyvVyBfprJ7 mAeXZWfhat6cKNRAGZcL5EmewdQuUfQfBdYmKjbw3a9GFDsDNuhDA2QwFt8BmkiVMRYyvI7l N0eVzszWCUgdc3qqM6qqcgBaqsVmJluwpvwp4ZBXmch5BgDDDb1MPO8AZ2QZfIQmplkj8Y6Z AiNMknkmgaekIINSJX8IzRzKD5WwMsin70psE8dpL/iBsA2cpJGzWMObVTtCxeDKlBCNqM1i gTXta1ukdUT7JgLEFZk9ceYQQMJJtUwzWu1UHfZn0Fs29HTqawfWPSZVbulbrnu5q55R4PlQ /xURkWQUTyDpqUvb4JK371zhepXiXDwrrpnyyZABm3SFLkk2bHlheeKU6Yql4pcmSVym1AS4 dV8y0oHAfdlSCF6tpOPf2+K9nW1CFA8b/tw4oJBTtfZ1kxXOMdyZU5fiG7xb1qDgpQKgHUX8 7Rd2T1UVLVeuhYlXNw2F+a2ucY+cMoqz3LtpksUiBppJhw099gEXehcN2JbUZ2TueJdt1FdS ztnZmsHUXLxrRBtGwqnFL7GSd6snpGIKuuL305iaOGODbb9c7ne1JqBbkw1wh8ci6vvwGlzx rexzimRaBzJxlkjNfMx8WpCvYebGMydNoeEtkWldtjTNVsUAtQARAQABzR5BbmRyaXkgR2Fw b24gPGF2Z0BGcmVlQlNELm9yZz7CwZQEEwEIAD4WIQS+LEO7ngQnXA4Bjr538m7TUc1yjwUC WbgsiAIbIwUJBaOagAULCQgHAgYVCAkKCwIEFgIDAQIeAQIXgAAKCRB38m7TUc1yj+JAEACV l9AK/nOWAt/9cufV2fRj0hdOqB1aCshtSrwHk/exXsDa4/FkmegxXQGY+3GWX3deIyesbVRL rYdtdK0dqJyT1SBqXK1h3/at9rxr9GQA6KWOxTjUFURsU7ok/6SIlm8uLRPNKO+yq0GDjgaO LzN+xykuBA0FlhQAXJnpZLcVfPJdWv7sSHGedL5ln8P8rxR+XnmsA5TUaaPcbhTB+mG+iKFj GghASDSfGqLWFPBlX/fpXikBDZ1gvOr8nyMY9nXhgfXpq3B6QCRYKPy58ChrZ5weeJZ29b7/ QdEO8NFNWHjSD9meiLdWQaqo9Y7uUxN3wySc/YUZxtS0bhAd8zJdNPsJYG8sXgKjeBQMVGuT eCAJFEYJqbwWvIXMfVWop4+O4xB+z2YE3jAbG/9tB/GSnQdVSj3G8MS80iLS58frnt+RSEw/ psahrfh0dh6SFHttE049xYiC+cM8J27Aaf0i9RflyITq57NuJm+AHJoU9SQUkIF0nc6lfA+o JRiyRlHZHKoRQkIg4aiKaZSWjQYRl5Txl0IZUP1dSWMX4s3XTMurC/pnja45dge/4ESOtJ9R 8XuIWg45Oq6MeIWdjKddGhRj3OohsltKgkEU3eLKYtB6qRTQypHHUawCXz88uYt5e3w4V16H lCpSTZV/EVHnNe45FVBlvK7k7HFfDDkryM7BTQRZuCyIARAAlq0slcsVboY/+IUJdcbEiJRW be9HKVz4SUchq0z9MZPX/0dcnvz/gkyYA+OuM78dNS7Mbby5dTvOqfpLJfCuhaNYOhlE0wY+ 1T6Tf1f4c/uA3U/YiadukQ3+6TJuYGAdRZD5EqYFIkreARTVWg87N9g0fT9BEqLw9lJtEGDY EWUE7L++B8o4uu3LQFEYxcrb4K/WKmgtmFcm77s0IKDrfcX4doV92QTIpLiRxcOmCC/OCYuO jB1oaaqXQzZrCutXRK0L5XN1Y1PYjIrEzHMIXmCDlLYnpFkK+itlXwlE2ZQxkfMruCWdQXye syl2fynAe8hvp7Mms9qU2r2K9EcJiR5N1t1C2/kTKNUhcRv7Yd/vwusK7BqJbhlng5ZgRx0m WxdntU/JLEntz3QBsBsWM9Y9wf2V4tLv6/DuDBta781RsCB/UrU2zNuOEkSixlUiHxw1dccI 6CVlaWkkJBxmHX22GdDFrcjvwMNIbbyfQLuBq6IOh8nvu9vuItup7qemDG3Ms6TVwA7BD3j+ 3fGprtyW8Fd/RR2bW2+LWkMrqHffAr6Y6V3h5kd2G9Q8ZWpEJk+LG6Mk3fhZhmCnHhDu6CwN MeUvxXDVO+fqc3JjFm5OxhmfVeJKrbCEUJyM8ESWLoNHLqjywdZga4Q7P12g8DUQ1mRxYg/L HgZY3zfKOqcAEQEAAcLBfAQYAQgAJhYhBL4sQ7ueBCdcDgGOvnfybtNRzXKPBQJZuCyIAhsM BQkFo5qAAAoJEHfybtNRzXKPBVwQAKfFy9P7N3OsLDMB56A4Kf+ZT+d5cIx0Yiaf4n6w7m3i ImHHHk9FIetI4Xe54a2IXh4Bq5UkAGY0667eIs+Z1Ea6I2i27Sdo7DxGwq09Qnm/Y65ADvXs 3aBvokCcm7FsM1wky395m8xUos1681oV5oxgqeRI8/76qy0hD9WR65UW+HQgZRIcIjSel9vR XDaD2HLGPTTGr7u4v00UeTMs6qvPsa2PJagogrKY8RXdFtXvweQFz78NbXhluwix2Tb9ETPk LIpDrtzV73CaE2aqBG/KrboXT2C67BgFtnk7T7Y7iKq4/XvEdDWscz2wws91BOXuMMd4c/c4 OmGW9m3RBLufFrOag1q5yUS9QbFfyqL6dftJP3Zq/xe+mr7sbWbhPVCQFrH3r26mpmy841ym dwQnNcsbIGiBASBSKksOvIDYKa2Wy8htPmWFTEOPRpFXdGQ27awcjjnB42nngyCK5ukZDHi6 w0qK5DNQQCkiweevCIC6wc3p67jl1EMFY5+z+zdTPb3h7LeVnGqW0qBQl99vVFgzLxchKcl0 R/paSFgwqXCZhAKMuUHncJuynDOP7z5LirUeFI8qsBAJi1rXpQoLJTVcW72swZ42IdPiboqx NbTMiNOiE36GqMcTPfKylCbF45JNX4nF9ElM0E+Y8gi4cizJYBRr2FBJgay0b9Cp Message-ID: <92b45b63-48c0-e9fe-c7c8-3ff24f37bf1f@FreeBSD.org> Date: Thu, 26 Apr 2018 10:50:18 +0300 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 8bit 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: Thu, 26 Apr 2018 07:50:28 -0000 On 26/04/2018 10:28, Eugene M. Zheganin wrote: > Hello, > > > I have some active vdev disk members that used to be in pool that clearly have > not beed destroyed properly, so I'm seeing in a "zpool import" output something > like > > > # zpool import >    pool: zroot >      id: 14767697319309030904 >   state: UNAVAIL >  status: The pool was last accessed by another system. >  action: The pool cannot be imported due to damaged devices or data. >    see: http://illumos.org/msg/ZFS-8000-EY >  config: > >         zroot                    UNAVAIL  insufficient replicas >           mirror-0               UNAVAIL  insufficient replicas >             5291726022575795110  UNAVAIL  cannot open >             2933754417879630350  UNAVAIL  cannot open > >    pool: esx >      id: 8314148521324214892 >   state: UNAVAIL >  status: The pool was last accessed by another system. >  action: The pool cannot be imported due to damaged devices or data. >    see: http://illumos.org/msg/ZFS-8000-EY >  config: > >         esx                       UNAVAIL  insufficient replicas >           mirror-0                UNAVAIL  insufficient replicas >             10170732803757341731  UNAVAIL  cannot open >             9207269511643803468   UNAVAIL  cannot open > > > is there any _safe_ way to get rid of this ? I'm asking because a gptzfsboot > loader in recent -STABLE stumbles upon this and refuses to boot the system > (https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227772). The workaround is to > use the 11.1 loader, but I'm afraid this behavior will now be the intended one. You can try to use zdb -l to find the stale labels. And then zpool labelclear to clear them. -- Andriy Gapon From owner-freebsd-stable@freebsd.org Thu Apr 26 09:55:31 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 30D19FA8618 for ; Thu, 26 Apr 2018 09:55:31 +0000 (UTC) (envelope-from dim@FreeBSD.org) Received: from tensor.andric.com (tensor.andric.com [87.251.56.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "tensor.andric.com", Issuer "COMODO RSA Domain Validation Secure Server CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id C2FB579831 for ; Thu, 26 Apr 2018 09:55:30 +0000 (UTC) (envelope-from dim@FreeBSD.org) Received: from coleburn.home.andric.com (coleburn.home.andric.com [192.168.0.15]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by tensor.andric.com (Postfix) with ESMTPSA id 069AD31850; Thu, 26 Apr 2018 11:55:23 +0200 (CEST) From: Dimitry Andric Message-Id: <1FDCF15C-E9FD-4746-9C89-F669EF4BA7C5@FreeBSD.org> Content-Type: multipart/signed; boundary="Apple-Mail=_6AEA95C7-1CE5-4615-9081-CB7C7C5FE091"; protocol="application/pgp-signature"; micalg=pgp-sha1 Mime-Version: 1.0 (Mac OS X Mail 11.3 \(3445.6.18\)) Subject: Re: gptboot broken when compiled with clang 6 and WITHOUT_LOADER_GELI -- clang 5 is OK Date: Thu, 26 Apr 2018 11:55:19 +0200 In-Reply-To: <20180425165840.GA1330@bali> Cc: FreeBSD Stable To: Andre Albsmeier References: <20180425165840.GA1330@bali> X-Mailer: Apple Mail (2.3445.6.18) 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: Thu, 26 Apr 2018 09:55:31 -0000 --Apple-Mail=_6AEA95C7-1CE5-4615-9081-CB7C7C5FE091 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii On 25 Apr 2018, at 18:58, Andre Albsmeier = wrote: >=20 > I have set up a new system disk for an i386 11.2-PRERELEASE box. I did = the > usual >=20 > gpart create -s gpt $disk > gpart add -t freebsd-boot -s 984 $disk > gpart bootcode -b /boot/pmbr -p /boot/gptboot -i 1 $disk > ... >=20 > thing, just to notice that the box wouldn't boot. It seems to hang = where > stage 2 should be run -- when the '\' should start spinning the screen > turns white and the box hangs (tested on two machines, an Asus P5W and = a > Supermicro A2SAV). >=20 > So I replaced gptboot on the new disk by the one from an older machine > and everything was fine. I wanted to find out what is actually causing > the issue and recompiled /usr/src/stand after updating the old sources > in several steps. >=20 > Eventually it turned out that it depends on the compiler. When = compiling > the latest /usr/src/stand with clang 5.0.1 the resulting gptboot = works. > When using 6.0.0 it doesn't. To be exact, it's gptboot.o which is = causing > the problems. When using a gptboot.o from a clang 5 system it is OK, = when > using a gptboot.o from a clang 6 system it fails. >=20 > To add more confusion: I usually have WITHOUT_LOADER_GELI in my = make.conf. > When removing this, the resulting gptboot works even when compiled = with > clang 6... >=20 > I can reproduce this in case s.o. wants me to do some tests... I can't reproduce it on my end, unfortunately. I downloaded the latest FreeBSD-11.2-PRERELEASE-i386-20180420-r332802 snapshot, installed it to a GPT partitioned disk, and it boots just fine. This snapshot corresponds to r332802, which has clang 6.0.0, with the EFLAGS change still reverted, so I assume its copy of gptboot is also compiled with that. Which exact revision of the base system were you using? -Dimitry --Apple-Mail=_6AEA95C7-1CE5-4615-9081-CB7C7C5FE091 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.2 iF0EARECAB0WIQR6tGLSzjX8bUI5T82wXqMKLiCWowUCWuGiBwAKCRCwXqMKLiCW oytNAJ9JUjejO5EFMja/42hOL4tLmopAQwCeM5sQ7yafqr3UwG30CyuqgESVoq8= =2bix -----END PGP SIGNATURE----- --Apple-Mail=_6AEA95C7-1CE5-4615-9081-CB7C7C5FE091-- From owner-freebsd-stable@freebsd.org Thu Apr 26 10:06:26 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 2DBA8FA8F2D for ; Thu, 26 Apr 2018 10:06:26 +0000 (UTC) (envelope-from dim@FreeBSD.org) Received: from tensor.andric.com (tensor.andric.com [87.251.56.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "tensor.andric.com", Issuer "COMODO RSA Domain Validation Secure Server CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id B5F8A7C5EA for ; Thu, 26 Apr 2018 10:06:25 +0000 (UTC) (envelope-from dim@FreeBSD.org) Received: from coleburn.home.andric.com (coleburn.home.andric.com [192.168.0.15]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by tensor.andric.com (Postfix) with ESMTPSA id 8990031852; Thu, 26 Apr 2018 12:06:24 +0200 (CEST) From: Dimitry Andric Message-Id: <3A857D03-607A-4983-A4C2-D3A93119297A@FreeBSD.org> Content-Type: multipart/signed; boundary="Apple-Mail=_FBD8AFD1-4377-4F69-9417-97F5F1704BD9"; protocol="application/pgp-signature"; micalg=pgp-sha1 Mime-Version: 1.0 (Mac OS X Mail 11.3 \(3445.6.18\)) Subject: Re: gptboot broken when compiled with clang 6 and WITHOUT_LOADER_GELI -- clang 5 is OK Date: Thu, 26 Apr 2018 12:06:21 +0200 In-Reply-To: Cc: Andre Albsmeier , FreeBSD Stable To: Dewayne Geraghty References: <20180425165840.GA1330@bali> X-Mailer: Apple Mail (2.3445.6.18) 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: Thu, 26 Apr 2018 10:06:26 -0000 --Apple-Mail=_FBD8AFD1-4377-4F69-9417-97F5F1704BD9 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii On 26 Apr 2018, at 06:17, Dewayne Geraghty = wrote: >=20 > Andre, You're not alone. I think there's a problem with clang6 on = i386 > FreeBSD 11.1X, refer: > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D227552 > https://forums.freebsd.org/threads/uptime-w-i386-breakage.65584/ > and perhaps also on amd64, search for > = https://bugs.freebsd.org/bugzilla/buglist.cgi?quicksearch=3Dclang&list_id=3D= 226390. >=20 > Without time to investigate I've reverted userland > FreeBSD 11.2-PRERELEASE r332843M amd64 1101515 1101509 > FreeBSD 11.2-PRERELEASE r332843M i386 1101515 1101509 As noted in another post, I cannot reproduce the problems with gptboot, but with FreeBSD-11.2-PRERELEASE-i386-20180420-r332802, I do indeed see w and uptime crashing in libxo: (gdb) bt #0 ifree (tsd=3D0x28000000) at arena.h:799 #1 0x2814b506 in __free (ptr=3D0x280601ef) at tsd.h:716 #2 0x2808bb07 in xo_do_emit_fields () at = /usr/src/contrib/libxo/libxo/libxo.c:6419 #3 0x28089a1c in xo_do_emit (xop=3D, flags=3D, fmt=3D0x804ad4d "{:time-of-day/%s} ") at = /usr/src/contrib/libxo/libxo/libxo.c:6470 #4 0x28089b61 in xo_emit (fmt=3D0x804ad4d "{:time-of-day/%s} ") at = /usr/src/contrib/libxo/libxo/libxo.c:6541 #5 0x08049f50 in main (argc=3D, argv=3D) at /usr/src/usr.bin/w/w.c:475 #6 0x080494cd in _start1 () #7 0x08049448 in _start () #8 0x00000000 in ?? () Not sure if this has anything to do with clang though, it looks more like a double free to me, at first glance. I'll do some debugging. -Dimitry --Apple-Mail=_FBD8AFD1-4377-4F69-9417-97F5F1704BD9 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.2 iF0EARECAB0WIQR6tGLSzjX8bUI5T82wXqMKLiCWowUCWuGknQAKCRCwXqMKLiCW o/EBAKDxBJJ7xA0p4eoQRt/xd+cTcIBTzwCeOkHqM3pfTLLR6F9LVvBPxl2L7jc= =dpf3 -----END PGP SIGNATURE----- --Apple-Mail=_FBD8AFD1-4377-4F69-9417-97F5F1704BD9-- From owner-freebsd-stable@freebsd.org Thu Apr 26 11:45:57 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 2F28BFAAF9A for ; Thu, 26 Apr 2018 11:45:57 +0000 (UTC) (envelope-from dim@FreeBSD.org) Received: from tensor.andric.com (tensor.andric.com [87.251.56.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "tensor.andric.com", Issuer "COMODO RSA Domain Validation Secure Server CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id BF94770AC8 for ; Thu, 26 Apr 2018 11:45:56 +0000 (UTC) (envelope-from dim@FreeBSD.org) Received: from coleburn.home.andric.com (coleburn.home.andric.com [192.168.0.15]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by tensor.andric.com (Postfix) with ESMTPSA id 5E9D73186C; Thu, 26 Apr 2018 13:45:55 +0200 (CEST) From: Dimitry Andric Message-Id: <55C3B174-0A2B-4954-BEB8-BF6688EBB02D@FreeBSD.org> Content-Type: multipart/signed; boundary="Apple-Mail=_D54C9553-0A66-4C26-9356-A3B9CB79E58D"; protocol="application/pgp-signature"; micalg=pgp-sha1 Mime-Version: 1.0 (Mac OS X Mail 11.3 \(3445.6.18\)) Subject: Re: gptboot broken when compiled with clang 6 and WITHOUT_LOADER_GELI -- clang 5 is OK Date: Thu, 26 Apr 2018 13:45:51 +0200 In-Reply-To: <3A857D03-607A-4983-A4C2-D3A93119297A@FreeBSD.org> Cc: FreeBSD Stable , Andre Albsmeier To: Dewayne Geraghty References: <20180425165840.GA1330@bali> <3A857D03-607A-4983-A4C2-D3A93119297A@FreeBSD.org> X-Mailer: Apple Mail (2.3445.6.18) 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: Thu, 26 Apr 2018 11:45:57 -0000 --Apple-Mail=_D54C9553-0A66-4C26-9356-A3B9CB79E58D Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii On 26 Apr 2018, at 12:06, Dimitry Andric wrote: >=20 > On 26 Apr 2018, at 06:17, Dewayne Geraghty = wrote: >>=20 >> Andre, You're not alone. I think there's a problem with clang6 on = i386 >> FreeBSD 11.1X, refer: >> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D227552 >> https://forums.freebsd.org/threads/uptime-w-i386-breakage.65584/ >> and perhaps also on amd64, search for >> = https://bugs.freebsd.org/bugzilla/buglist.cgi?quicksearch=3Dclang&list_id=3D= 226390. >>=20 >> Without time to investigate I've reverted userland >> FreeBSD 11.2-PRERELEASE r332843M amd64 1101515 1101509 >> FreeBSD 11.2-PRERELEASE r332843M i386 1101515 1101509 >=20 > As noted in another post, I cannot reproduce the problems with = gptboot, > but with FreeBSD-11.2-PRERELEASE-i386-20180420-r332802, I do indeed = see > w and uptime crashing in libxo: >=20 > (gdb) bt > #0 ifree (tsd=3D0x28000000) at arena.h:799 > #1 0x2814b506 in __free (ptr=3D0x280601ef) at tsd.h:716 > #2 0x2808bb07 in xo_do_emit_fields () at = /usr/src/contrib/libxo/libxo/libxo.c:6419 > #3 0x28089a1c in xo_do_emit (xop=3D, = flags=3D, fmt=3D0x804ad4d "{:time-of-day/%s} ") at = /usr/src/contrib/libxo/libxo/libxo.c:6470 > #4 0x28089b61 in xo_emit (fmt=3D0x804ad4d "{:time-of-day/%s} ") at = /usr/src/contrib/libxo/libxo/libxo.c:6541 > #5 0x08049f50 in main (argc=3D, argv=3D) at /usr/src/usr.bin/w/w.c:475 > #6 0x080494cd in _start1 () > #7 0x08049448 in _start () > #8 0x00000000 in ?? () >=20 > Not sure if this has anything to do with clang though, it looks more > like a double free to me, at first glance. I'll do some debugging. Strangely, simply recompiling libxo fixes the problem, or at least works around it. This is on the r332802 snapshot, so I guess the libxo.so.0 file shipped may be broken, somehow. -Dimitry --Apple-Mail=_D54C9553-0A66-4C26-9356-A3B9CB79E58D Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.2 iF0EARECAB0WIQR6tGLSzjX8bUI5T82wXqMKLiCWowUCWuG77wAKCRCwXqMKLiCW o9fuAKCZVy/0ZrYpGjQHPyJW12R0xpkkXwCbBPCoisn8aM/p0D7oFsfuDCz/o44= =JSWn -----END PGP SIGNATURE----- --Apple-Mail=_D54C9553-0A66-4C26-9356-A3B9CB79E58D-- From owner-freebsd-stable@freebsd.org Thu Apr 26 14:37:24 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 873DBFAEE2C; Thu, 26 Apr 2018 14:37:24 +0000 (UTC) (envelope-from eugen@grosbein.net) Received: from hz.grosbein.net (unknown [IPv6:2a01:4f8:d12:604::2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "hz.grosbein.net", Issuer "hz.grosbein.net" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 05D5F72D64; Thu, 26 Apr 2018 14:37:23 +0000 (UTC) (envelope-from eugen@grosbein.net) Received: from eg.sd.rdtc.ru (root@eg.sd.rdtc.ru [62.231.161.221] (may be forged)) by hz.grosbein.net (8.15.2/8.15.2) with ESMTPS id w3QEbH4Y035767 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Thu, 26 Apr 2018 16:37:17 +0200 (CEST) (envelope-from eugen@grosbein.net) X-Envelope-From: eugen@grosbein.net X-Envelope-To: avg@FreeBSD.org Received: from [10.58.0.4] ([10.58.0.4]) by eg.sd.rdtc.ru (8.15.2/8.15.2) with ESMTPS id w3QEbCvn027163 (version=TLSv1.2 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Thu, 26 Apr 2018 21:37:12 +0700 (+07) (envelope-from eugen@grosbein.net) Subject: Re: clear old pools remains from active vdevs To: Andriy Gapon , "Eugene M. Zheganin" , freebsd-stable@freebsd.org References: <92b45b63-48c0-e9fe-c7c8-3ff24f37bf1f@FreeBSD.org> Cc: freebsd-fs@freebsd.org From: Eugene Grosbein Message-ID: <5AE1E414.4010408@grosbein.net> Date: Thu, 26 Apr 2018 21:37:08 +0700 User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.7.2 MIME-Version: 1.0 In-Reply-To: <92b45b63-48c0-e9fe-c7c8-3ff24f37bf1f@FreeBSD.org> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=2.2 required=5.0 tests=BAYES_00, LOCAL_FROM, RDNS_NONE, SPF_PASS autolearn=no autolearn_force=no version=3.4.1 X-Spam-Report: * -0.0 SPF_PASS SPF: sender matches SPF record * -2.3 BAYES_00 BODY: Bayes spam probability is 0 to 1% * [score: 0.0000] * 2.6 LOCAL_FROM From my domains * 1.9 RDNS_NONE Delivered to internal network by a host with no rDNS X-Spam-Level: ** X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on hz.grosbein.net 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: Thu, 26 Apr 2018 14:37:24 -0000 26.04.2018 14:50, Andriy Gapon wrote: > You can try to use zdb -l to find the stale labels. > And then zpool labelclear to clear them. Our "zpool labelclear" implementation destroys everything (literally). Have you really tried it? From owner-freebsd-stable@freebsd.org Thu Apr 26 15:14:44 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 BB4B7FB0263; Thu, 26 Apr 2018 15:14:44 +0000 (UTC) (envelope-from asomers@gmail.com) Received: from mail-lf0-x231.google.com (mail-lf0-x231.google.com [IPv6:2a00:1450:4010:c07::231]) (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 1B1387AD67; Thu, 26 Apr 2018 15:14:44 +0000 (UTC) (envelope-from asomers@gmail.com) Received: by mail-lf0-x231.google.com with SMTP id h4-v6so4517190lfc.1; Thu, 26 Apr 2018 08:14:44 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=kQtFSmmDhGQuT9AJNRiFWh/sF/yxnJO516WILVhjTyc=; b=RWURpwN3CiYaHLE1odKgd8Ok6xrXcTKRyZ92lf7vfmrGIVq04zcEpZgd0wnsO/CHlt lAJzcxQ1D1B26GUm1GdzPHQz0I736RPn/hV6EfVFKB2U5LTIJ3z14L9kzXTmiPsYfpMo w/tk6OySTp/oHLKpqJGvk1cealqFII2gRSeZk6whTe0G/ZIIIuDWaxMUIdCwxkxW2dKC R4CdQBZCL6ds5Ga85Ens5eBj3naUJMiF+2AodnZMPvSxzgvYVvhPma+buiQh/1wxTgVM PHsvsbwFVsaQnC9OblaImpiAGWOn9WDGpGDGOO6owDn3TbnKbAVdl9VxDXQDlK9A7nTF rg7g== 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=kQtFSmmDhGQuT9AJNRiFWh/sF/yxnJO516WILVhjTyc=; b=M8O8+FVDUAfpDrA3n5CO3U82Nshx5Nu91Q2UtL2p5e0IlwU1d4diDlS72CYMv4IM+a NB0WopGV4gNXSWtTzMo9z6S/Zb6jGg20tOyZnDrif5aDGJhguBKigh/appvhqUgfPIPx nvfcegmF3KtjlLGi1fAwQa8XLvFn+/kwbni+j3ubal8PGg1fLUWtRVIUIkMvubUXCiX7 Iw6Xzwvn3+8BFLdUAUWaNEY0U7pz1J69+iZ70dChNIEt4YlnQl2UCVvSQgyFHmQUCRwh ZeDLC/44IpWXJiC2VREm480yewsAp+C0tCErC7p8Rb2YkYdaf2IiyjucefOwFD2NiQaj Ldow== X-Gm-Message-State: ALQs6tDUklrkPlO4FRHoRtKWoePZd4N9+QkIkXVxgwTwH0aFF1B33rns vHW0VntzPlV6pZruSIt/gTKTBlPS7iF07cJdYRo= X-Google-Smtp-Source: AIpwx49OYhLJB2qzmfNo/7DPGgSU1pldERiZxhxE0HC0/Nhdr2FDL/iHuLsJ7hoSXOlGqYBl3I4lVkr738G9Lq4Z0d0= X-Received: by 10.46.2.90 with SMTP id 87mr23872898ljc.46.1524755682549; Thu, 26 Apr 2018 08:14:42 -0700 (PDT) MIME-Version: 1.0 Sender: asomers@gmail.com Received: by 10.179.6.21 with HTTP; Thu, 26 Apr 2018 08:14:41 -0700 (PDT) In-Reply-To: <5AE1E414.4010408@grosbein.net> References: <92b45b63-48c0-e9fe-c7c8-3ff24f37bf1f@FreeBSD.org> <5AE1E414.4010408@grosbein.net> From: Alan Somers Date: Thu, 26 Apr 2018 09:14:41 -0600 X-Google-Sender-Auth: aff5XLq8b6Zs3Za6jknqFbazjdw Message-ID: Subject: Re: clear old pools remains from active vdevs To: Eugene Grosbein Cc: Andriy Gapon , "Eugene M. Zheganin" , FreeBSD , freebsd-fs Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 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: Thu, 26 Apr 2018 15:14:45 -0000 On Thu, Apr 26, 2018 at 8:37 AM, Eugene Grosbein wrote: > 26.04.2018 14:50, Andriy Gapon wrote: > > > You can try to use zdb -l to find the stale labels. > > And then zpool labelclear to clear them. > > Our "zpool labelclear" implementation destroys everything (literally). > Have you really tried it? > > _______________________________________________ > freebsd-stable@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" > "zpool labelclear" won't help in this case, because you have literally no devices with active labels. The problem is that the pool is still in your /boot/zfs/zpool.cache file. I think that plain "zpool destroy esx" will work in this case. From owner-freebsd-stable@freebsd.org Thu Apr 26 15:50:54 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 6A819FB0F60; Thu, 26 Apr 2018 15:50:54 +0000 (UTC) (envelope-from agapon@gmail.com) Received: from mail-lf0-f47.google.com (mail-lf0-f47.google.com [209.85.215.47]) (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 BE6A382750; Thu, 26 Apr 2018 15:50:53 +0000 (UTC) (envelope-from agapon@gmail.com) Received: by mail-lf0-f47.google.com with SMTP id b23-v6so31508755lfg.4; Thu, 26 Apr 2018 08:50:53 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:openpgp:autocrypt :message-id:date:user-agent:mime-version:in-reply-to :content-language:content-transfer-encoding; bh=KsGtaSeguFOFTT7e03cSHgODnc3OrUsYW5/Sijm2FDU=; b=BW/NXRD7/ca6Px0q6lzob9jWugjuLdrECldU5RnhPPgMOXkHHrWgGGEk3rslqdZHr+ N7xKCeX4498N89DZsTn7pvdb4t4zljwGCDKZpn+p57FBbkU9dMSg/dfQboEGzqug3kfU EVuBnXdIORXBI9ozxGzVHqCZ9mHvc+xeyoe1T30ctFl1qfIWdn2KJWZg/cJ9SC3anPPh kE+LUwn+aQvto0rZw2EIrPAn/i1UD+6y7suftul/RAKh9LVihhDeYXUYjWA0wAWk7UZU DzUIvscGAZgmYhL1PDlnzgkmJMsJ2IMDPii+0bbHlEuUH7S2uu/N736KzUI/0LZLE7Ej jB4Q== X-Gm-Message-State: ALQs6tD4iJ7dDg6oc2ViDA9a4J+JG1a1gRRrZMviFLgu/2pIr0PRyOFr DwNAgZg9VGUSW2YEywbeWjW86Ji+ X-Google-Smtp-Source: AB8JxZrEMmMBbfjrocUQqA8UUye56QempJbZpj6tuwyy+OA01OzhQpgxadFg1AmMD1xoGEo+/qD63Q== X-Received: by 2002:a19:b587:: with SMTP id g7-v6mr18057226lfk.90.1524757851545; Thu, 26 Apr 2018 08:50:51 -0700 (PDT) Received: from [192.168.0.88] (east.meadow.volia.net. [93.72.151.96]) by smtp.googlemail.com with ESMTPSA id l12sm2633594ljh.78.2018.04.26.08.50.49 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 26 Apr 2018 08:50:50 -0700 (PDT) Subject: Re: clear old pools remains from active vdevs To: Eugene Grosbein , "Eugene M. Zheganin" , freebsd-stable@FreeBSD.org Cc: freebsd-fs@FreeBSD.org References: <92b45b63-48c0-e9fe-c7c8-3ff24f37bf1f@FreeBSD.org> <5AE1E414.4010408@grosbein.net> From: Andriy Gapon Openpgp: preference=signencrypt Autocrypt: addr=avg@FreeBSD.org; prefer-encrypt=mutual; keydata= xsFNBFm4LIgBEADNB/3lT7f15UKeQ52xCFQx/GqHkSxEdVyLFZTmY3KyNPQGBtyvVyBfprJ7 mAeXZWfhat6cKNRAGZcL5EmewdQuUfQfBdYmKjbw3a9GFDsDNuhDA2QwFt8BmkiVMRYyvI7l N0eVzszWCUgdc3qqM6qqcgBaqsVmJluwpvwp4ZBXmch5BgDDDb1MPO8AZ2QZfIQmplkj8Y6Z AiNMknkmgaekIINSJX8IzRzKD5WwMsin70psE8dpL/iBsA2cpJGzWMObVTtCxeDKlBCNqM1i gTXta1ukdUT7JgLEFZk9ceYQQMJJtUwzWu1UHfZn0Fs29HTqawfWPSZVbulbrnu5q55R4PlQ /xURkWQUTyDpqUvb4JK371zhepXiXDwrrpnyyZABm3SFLkk2bHlheeKU6Yql4pcmSVym1AS4 dV8y0oHAfdlSCF6tpOPf2+K9nW1CFA8b/tw4oJBTtfZ1kxXOMdyZU5fiG7xb1qDgpQKgHUX8 7Rd2T1UVLVeuhYlXNw2F+a2ucY+cMoqz3LtpksUiBppJhw099gEXehcN2JbUZ2TueJdt1FdS ztnZmsHUXLxrRBtGwqnFL7GSd6snpGIKuuL305iaOGODbb9c7ne1JqBbkw1wh8ci6vvwGlzx rexzimRaBzJxlkjNfMx8WpCvYebGMydNoeEtkWldtjTNVsUAtQARAQABzR5BbmRyaXkgR2Fw b24gPGF2Z0BGcmVlQlNELm9yZz7CwZQEEwEIAD4WIQS+LEO7ngQnXA4Bjr538m7TUc1yjwUC WbgsiAIbIwUJBaOagAULCQgHAgYVCAkKCwIEFgIDAQIeAQIXgAAKCRB38m7TUc1yj+JAEACV l9AK/nOWAt/9cufV2fRj0hdOqB1aCshtSrwHk/exXsDa4/FkmegxXQGY+3GWX3deIyesbVRL rYdtdK0dqJyT1SBqXK1h3/at9rxr9GQA6KWOxTjUFURsU7ok/6SIlm8uLRPNKO+yq0GDjgaO LzN+xykuBA0FlhQAXJnpZLcVfPJdWv7sSHGedL5ln8P8rxR+XnmsA5TUaaPcbhTB+mG+iKFj GghASDSfGqLWFPBlX/fpXikBDZ1gvOr8nyMY9nXhgfXpq3B6QCRYKPy58ChrZ5weeJZ29b7/ QdEO8NFNWHjSD9meiLdWQaqo9Y7uUxN3wySc/YUZxtS0bhAd8zJdNPsJYG8sXgKjeBQMVGuT eCAJFEYJqbwWvIXMfVWop4+O4xB+z2YE3jAbG/9tB/GSnQdVSj3G8MS80iLS58frnt+RSEw/ psahrfh0dh6SFHttE049xYiC+cM8J27Aaf0i9RflyITq57NuJm+AHJoU9SQUkIF0nc6lfA+o JRiyRlHZHKoRQkIg4aiKaZSWjQYRl5Txl0IZUP1dSWMX4s3XTMurC/pnja45dge/4ESOtJ9R 8XuIWg45Oq6MeIWdjKddGhRj3OohsltKgkEU3eLKYtB6qRTQypHHUawCXz88uYt5e3w4V16H lCpSTZV/EVHnNe45FVBlvK7k7HFfDDkryM7BTQRZuCyIARAAlq0slcsVboY/+IUJdcbEiJRW be9HKVz4SUchq0z9MZPX/0dcnvz/gkyYA+OuM78dNS7Mbby5dTvOqfpLJfCuhaNYOhlE0wY+ 1T6Tf1f4c/uA3U/YiadukQ3+6TJuYGAdRZD5EqYFIkreARTVWg87N9g0fT9BEqLw9lJtEGDY EWUE7L++B8o4uu3LQFEYxcrb4K/WKmgtmFcm77s0IKDrfcX4doV92QTIpLiRxcOmCC/OCYuO jB1oaaqXQzZrCutXRK0L5XN1Y1PYjIrEzHMIXmCDlLYnpFkK+itlXwlE2ZQxkfMruCWdQXye syl2fynAe8hvp7Mms9qU2r2K9EcJiR5N1t1C2/kTKNUhcRv7Yd/vwusK7BqJbhlng5ZgRx0m WxdntU/JLEntz3QBsBsWM9Y9wf2V4tLv6/DuDBta781RsCB/UrU2zNuOEkSixlUiHxw1dccI 6CVlaWkkJBxmHX22GdDFrcjvwMNIbbyfQLuBq6IOh8nvu9vuItup7qemDG3Ms6TVwA7BD3j+ 3fGprtyW8Fd/RR2bW2+LWkMrqHffAr6Y6V3h5kd2G9Q8ZWpEJk+LG6Mk3fhZhmCnHhDu6CwN MeUvxXDVO+fqc3JjFm5OxhmfVeJKrbCEUJyM8ESWLoNHLqjywdZga4Q7P12g8DUQ1mRxYg/L HgZY3zfKOqcAEQEAAcLBfAQYAQgAJhYhBL4sQ7ueBCdcDgGOvnfybtNRzXKPBQJZuCyIAhsM BQkFo5qAAAoJEHfybtNRzXKPBVwQAKfFy9P7N3OsLDMB56A4Kf+ZT+d5cIx0Yiaf4n6w7m3i ImHHHk9FIetI4Xe54a2IXh4Bq5UkAGY0667eIs+Z1Ea6I2i27Sdo7DxGwq09Qnm/Y65ADvXs 3aBvokCcm7FsM1wky395m8xUos1681oV5oxgqeRI8/76qy0hD9WR65UW+HQgZRIcIjSel9vR XDaD2HLGPTTGr7u4v00UeTMs6qvPsa2PJagogrKY8RXdFtXvweQFz78NbXhluwix2Tb9ETPk LIpDrtzV73CaE2aqBG/KrboXT2C67BgFtnk7T7Y7iKq4/XvEdDWscz2wws91BOXuMMd4c/c4 OmGW9m3RBLufFrOag1q5yUS9QbFfyqL6dftJP3Zq/xe+mr7sbWbhPVCQFrH3r26mpmy841ym dwQnNcsbIGiBASBSKksOvIDYKa2Wy8htPmWFTEOPRpFXdGQ27awcjjnB42nngyCK5ukZDHi6 w0qK5DNQQCkiweevCIC6wc3p67jl1EMFY5+z+zdTPb3h7LeVnGqW0qBQl99vVFgzLxchKcl0 R/paSFgwqXCZhAKMuUHncJuynDOP7z5LirUeFI8qsBAJi1rXpQoLJTVcW72swZ42IdPiboqx NbTMiNOiE36GqMcTPfKylCbF45JNX4nF9ElM0E+Y8gi4cizJYBRr2FBJgay0b9Cp Message-ID: <5811ffb0-9afd-d6f3-6c04-febb0fab6be3@FreeBSD.org> Date: Thu, 26 Apr 2018 18:50:49 +0300 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0 MIME-Version: 1.0 In-Reply-To: <5AE1E414.4010408@grosbein.net> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit 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: Thu, 26 Apr 2018 15:50:54 -0000 On 26/04/2018 17:37, Eugene Grosbein wrote: > 26.04.2018 14:50, Andriy Gapon wrote: > >> You can try to use zdb -l to find the stale labels. >> And then zpool labelclear to clear them. > > Our "zpool labelclear" implementation destroys everything (literally). > Have you really tried it? > I have never needed it, so I have never used it. -- Andriy Gapon From owner-freebsd-stable@freebsd.org Thu Apr 26 15:59:09 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 07C80FB1442; Thu, 26 Apr 2018 15:59:09 +0000 (UTC) (envelope-from agapon@gmail.com) Received: from mail-lf0-f47.google.com (mail-lf0-f47.google.com [209.85.215.47]) (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 5A5CF848F1; Thu, 26 Apr 2018 15:59:08 +0000 (UTC) (envelope-from agapon@gmail.com) Received: by mail-lf0-f47.google.com with SMTP id v85-v6so9939503lfa.13; Thu, 26 Apr 2018 08:59:08 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:openpgp:autocrypt :message-id:date:user-agent:mime-version:in-reply-to :content-language:content-transfer-encoding; bh=7TRQZCwirU1oPkVKbX2Dy2RRmAgr0Sz5QA2VielJaaY=; b=giJjjpCqvcOsK9qi2RjmhoiPLIbI+FDENFGPmGQTnGXXrBMvcoD0Jw+nlb0ZziGxbI NAOxu+ntLjuc6qEk4coIcyTVJUAhTFGFOZ3AtG+hQ3tVx0uMUzKGq3yWWG8llv1Jt1JP oluM1Su/H0Xar1J5CYaTamctJqN/2Bvvg7C8yAJxSiv6S5GwK8DAX18I472BjFRLQZyj Qpi3gUZQQ/5MuwuTEYFgt+Phw1Lis3zINQfhQe8c+qABHRjK//7NjFQ2tbg0K7mX3aft XmYF6noBF4DOhKX+sTI+lzGtv0plC37xFbP/vfSa8lenoGOlc4ifZijXo+ITOHeh6MxV Tsdw== X-Gm-Message-State: ALQs6tCJ8j1xDCMT2wYBrwDaGrv1PGxmgCBR/iKKoJ0sYcna9mt1GG3S IrzgdBikYoZZJI/d7TvKRAqbn/Wj X-Google-Smtp-Source: AIpwx49T51sY8EObqnNvyVJGXAjPVRF6decsA2SPrzH2jJuNLRJAr39DVRzg35R4w9FV5FHJyAYyaQ== X-Received: by 10.46.146.204 with SMTP id k12mr17245078ljh.101.1524757969242; Thu, 26 Apr 2018 08:52:49 -0700 (PDT) Received: from [192.168.0.88] (east.meadow.volia.net. [93.72.151.96]) by smtp.googlemail.com with ESMTPSA id u5sm403398ljk.64.2018.04.26.08.52.48 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 26 Apr 2018 08:52:48 -0700 (PDT) Subject: Re: clear old pools remains from active vdevs To: Alan Somers , Eugene Grosbein Cc: "Eugene M. Zheganin" , FreeBSD , freebsd-fs References: <92b45b63-48c0-e9fe-c7c8-3ff24f37bf1f@FreeBSD.org> <5AE1E414.4010408@grosbein.net> From: Andriy Gapon Openpgp: preference=signencrypt Autocrypt: addr=avg@FreeBSD.org; prefer-encrypt=mutual; keydata= xsFNBFm4LIgBEADNB/3lT7f15UKeQ52xCFQx/GqHkSxEdVyLFZTmY3KyNPQGBtyvVyBfprJ7 mAeXZWfhat6cKNRAGZcL5EmewdQuUfQfBdYmKjbw3a9GFDsDNuhDA2QwFt8BmkiVMRYyvI7l N0eVzszWCUgdc3qqM6qqcgBaqsVmJluwpvwp4ZBXmch5BgDDDb1MPO8AZ2QZfIQmplkj8Y6Z AiNMknkmgaekIINSJX8IzRzKD5WwMsin70psE8dpL/iBsA2cpJGzWMObVTtCxeDKlBCNqM1i gTXta1ukdUT7JgLEFZk9ceYQQMJJtUwzWu1UHfZn0Fs29HTqawfWPSZVbulbrnu5q55R4PlQ /xURkWQUTyDpqUvb4JK371zhepXiXDwrrpnyyZABm3SFLkk2bHlheeKU6Yql4pcmSVym1AS4 dV8y0oHAfdlSCF6tpOPf2+K9nW1CFA8b/tw4oJBTtfZ1kxXOMdyZU5fiG7xb1qDgpQKgHUX8 7Rd2T1UVLVeuhYlXNw2F+a2ucY+cMoqz3LtpksUiBppJhw099gEXehcN2JbUZ2TueJdt1FdS ztnZmsHUXLxrRBtGwqnFL7GSd6snpGIKuuL305iaOGODbb9c7ne1JqBbkw1wh8ci6vvwGlzx rexzimRaBzJxlkjNfMx8WpCvYebGMydNoeEtkWldtjTNVsUAtQARAQABzR5BbmRyaXkgR2Fw b24gPGF2Z0BGcmVlQlNELm9yZz7CwZQEEwEIAD4WIQS+LEO7ngQnXA4Bjr538m7TUc1yjwUC WbgsiAIbIwUJBaOagAULCQgHAgYVCAkKCwIEFgIDAQIeAQIXgAAKCRB38m7TUc1yj+JAEACV l9AK/nOWAt/9cufV2fRj0hdOqB1aCshtSrwHk/exXsDa4/FkmegxXQGY+3GWX3deIyesbVRL rYdtdK0dqJyT1SBqXK1h3/at9rxr9GQA6KWOxTjUFURsU7ok/6SIlm8uLRPNKO+yq0GDjgaO LzN+xykuBA0FlhQAXJnpZLcVfPJdWv7sSHGedL5ln8P8rxR+XnmsA5TUaaPcbhTB+mG+iKFj GghASDSfGqLWFPBlX/fpXikBDZ1gvOr8nyMY9nXhgfXpq3B6QCRYKPy58ChrZ5weeJZ29b7/ QdEO8NFNWHjSD9meiLdWQaqo9Y7uUxN3wySc/YUZxtS0bhAd8zJdNPsJYG8sXgKjeBQMVGuT eCAJFEYJqbwWvIXMfVWop4+O4xB+z2YE3jAbG/9tB/GSnQdVSj3G8MS80iLS58frnt+RSEw/ psahrfh0dh6SFHttE049xYiC+cM8J27Aaf0i9RflyITq57NuJm+AHJoU9SQUkIF0nc6lfA+o JRiyRlHZHKoRQkIg4aiKaZSWjQYRl5Txl0IZUP1dSWMX4s3XTMurC/pnja45dge/4ESOtJ9R 8XuIWg45Oq6MeIWdjKddGhRj3OohsltKgkEU3eLKYtB6qRTQypHHUawCXz88uYt5e3w4V16H lCpSTZV/EVHnNe45FVBlvK7k7HFfDDkryM7BTQRZuCyIARAAlq0slcsVboY/+IUJdcbEiJRW be9HKVz4SUchq0z9MZPX/0dcnvz/gkyYA+OuM78dNS7Mbby5dTvOqfpLJfCuhaNYOhlE0wY+ 1T6Tf1f4c/uA3U/YiadukQ3+6TJuYGAdRZD5EqYFIkreARTVWg87N9g0fT9BEqLw9lJtEGDY EWUE7L++B8o4uu3LQFEYxcrb4K/WKmgtmFcm77s0IKDrfcX4doV92QTIpLiRxcOmCC/OCYuO jB1oaaqXQzZrCutXRK0L5XN1Y1PYjIrEzHMIXmCDlLYnpFkK+itlXwlE2ZQxkfMruCWdQXye syl2fynAe8hvp7Mms9qU2r2K9EcJiR5N1t1C2/kTKNUhcRv7Yd/vwusK7BqJbhlng5ZgRx0m WxdntU/JLEntz3QBsBsWM9Y9wf2V4tLv6/DuDBta781RsCB/UrU2zNuOEkSixlUiHxw1dccI 6CVlaWkkJBxmHX22GdDFrcjvwMNIbbyfQLuBq6IOh8nvu9vuItup7qemDG3Ms6TVwA7BD3j+ 3fGprtyW8Fd/RR2bW2+LWkMrqHffAr6Y6V3h5kd2G9Q8ZWpEJk+LG6Mk3fhZhmCnHhDu6CwN MeUvxXDVO+fqc3JjFm5OxhmfVeJKrbCEUJyM8ESWLoNHLqjywdZga4Q7P12g8DUQ1mRxYg/L HgZY3zfKOqcAEQEAAcLBfAQYAQgAJhYhBL4sQ7ueBCdcDgGOvnfybtNRzXKPBQJZuCyIAhsM BQkFo5qAAAoJEHfybtNRzXKPBVwQAKfFy9P7N3OsLDMB56A4Kf+ZT+d5cIx0Yiaf4n6w7m3i ImHHHk9FIetI4Xe54a2IXh4Bq5UkAGY0667eIs+Z1Ea6I2i27Sdo7DxGwq09Qnm/Y65ADvXs 3aBvokCcm7FsM1wky395m8xUos1681oV5oxgqeRI8/76qy0hD9WR65UW+HQgZRIcIjSel9vR XDaD2HLGPTTGr7u4v00UeTMs6qvPsa2PJagogrKY8RXdFtXvweQFz78NbXhluwix2Tb9ETPk LIpDrtzV73CaE2aqBG/KrboXT2C67BgFtnk7T7Y7iKq4/XvEdDWscz2wws91BOXuMMd4c/c4 OmGW9m3RBLufFrOag1q5yUS9QbFfyqL6dftJP3Zq/xe+mr7sbWbhPVCQFrH3r26mpmy841ym dwQnNcsbIGiBASBSKksOvIDYKa2Wy8htPmWFTEOPRpFXdGQ27awcjjnB42nngyCK5ukZDHi6 w0qK5DNQQCkiweevCIC6wc3p67jl1EMFY5+z+zdTPb3h7LeVnGqW0qBQl99vVFgzLxchKcl0 R/paSFgwqXCZhAKMuUHncJuynDOP7z5LirUeFI8qsBAJi1rXpQoLJTVcW72swZ42IdPiboqx NbTMiNOiE36GqMcTPfKylCbF45JNX4nF9ElM0E+Y8gi4cizJYBRr2FBJgay0b9Cp Message-ID: Date: Thu, 26 Apr 2018 18:52:47 +0300 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 8bit 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: Thu, 26 Apr 2018 15:59:09 -0000 On 26/04/2018 18:14, Alan Somers wrote: > On Thu, Apr 26, 2018 at 8:37 AM, Eugene Grosbein > wrote: > > 26.04.2018 14:50, Andriy Gapon wrote: > > > You can try to use zdb -l to find the stale labels. > > And then zpool labelclear to clear them. > > Our "zpool labelclear" implementation destroys everything (literally). > Have you really tried it? > > > "zpool labelclear" won't help in this case, because you have literally no > devices with active labels.  The problem is that the pool is still in your > /boot/zfs/zpool.cache file.  I think that plain "zpool destroy esx" will work in > this case. In the original message Eugene (Zheganin) mentioned that those phantom pools confused the boot chain. I do not think that anything in zpool.cache can do that. -- Andriy Gapon From owner-freebsd-stable@freebsd.org Thu Apr 26 16:05:55 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 379BEFB1940 for ; Thu, 26 Apr 2018 16:05:55 +0000 (UTC) (envelope-from freebsd-stable-local@be-well.ilk.org) Received: from be-well.ilk.org (be-well.ilk.org [23.30.133.173]) by mx1.freebsd.org (Postfix) with ESMTP id CE0A385F67; Thu, 26 Apr 2018 16:05:54 +0000 (UTC) (envelope-from freebsd-stable-local@be-well.ilk.org) Received: by be-well.ilk.org (Postfix, from userid 1147) id 79DE033C22; Thu, 26 Apr 2018 12:05:53 -0400 (EDT) From: Lowell Gilbert To: Dimitry Andric Cc: FreeBSD Stable Subject: Re: gptboot broken when compiled with clang 6 and WITHOUT_LOADER_GELI -- clang 5 is OK References: <20180425165840.GA1330@bali> <3A857D03-607A-4983-A4C2-D3A93119297A@FreeBSD.org> <55C3B174-0A2B-4954-BEB8-BF6688EBB02D@FreeBSD.org> Date: Thu, 26 Apr 2018 12:05:53 -0400 In-Reply-To: <55C3B174-0A2B-4954-BEB8-BF6688EBB02D@FreeBSD.org> (Dimitry Andric's message of "Thu, 26 Apr 2018 13:45:51 +0200") Message-ID: <44tvry9cm6.fsf@be-well.ilk.org> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.3 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain 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: Thu, 26 Apr 2018 16:05:55 -0000 Dimitry Andric writes: > On 26 Apr 2018, at 12:06, Dimitry Andric wrote: >> >> On 26 Apr 2018, at 06:17, Dewayne Geraghty wrote: >>> >>> Andre, You're not alone. I think there's a problem with clang6 on i386 >>> FreeBSD 11.1X, refer: >>> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227552 >>> https://forums.freebsd.org/threads/uptime-w-i386-breakage.65584/ >>> and perhaps also on amd64, search for >>> https://bugs.freebsd.org/bugzilla/buglist.cgi?quicksearch=clang&list_id=226390. >>> >>> Without time to investigate I've reverted userland >>> FreeBSD 11.2-PRERELEASE r332843M amd64 1101515 1101509 >>> FreeBSD 11.2-PRERELEASE r332843M i386 1101515 1101509 >> >> As noted in another post, I cannot reproduce the problems with gptboot, >> but with FreeBSD-11.2-PRERELEASE-i386-20180420-r332802, I do indeed see >> w and uptime crashing in libxo: >> >> (gdb) bt >> #0 ifree (tsd=0x28000000) at arena.h:799 >> #1 0x2814b506 in __free (ptr=0x280601ef) at tsd.h:716 >> #2 0x2808bb07 in xo_do_emit_fields () at /usr/src/contrib/libxo/libxo/libxo.c:6419 >> #3 0x28089a1c in xo_do_emit (xop=, flags=> optimized out>, fmt=0x804ad4d "{:time-of-day/%s} ") at >> /usr/src/contrib/libxo/libxo/libxo.c:6470 >> #4 0x28089b61 in xo_emit (fmt=0x804ad4d "{:time-of-day/%s} ") at /usr/src/contrib/libxo/libxo/libxo.c:6541 >> #5 0x08049f50 in main (argc=, argv=) at /usr/src/usr.bin/w/w.c:475 >> #6 0x080494cd in _start1 () >> #7 0x08049448 in _start () >> #8 0x00000000 in ?? () >> >> Not sure if this has anything to do with clang though, it looks more >> like a double free to me, at first glance. I'll do some debugging. > > Strangely, simply recompiling libxo fixes the problem, or at least works > around it. This is on the r332802 snapshot, so I guess the libxo.so.0 > file shipped may be broken, somehow. Actually, that is a recurring bug (https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227552) and does seem to be some kind of initialization problem with clang. From owner-freebsd-stable@freebsd.org Thu Apr 26 16:54:12 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 60875FB2A7F for ; Thu, 26 Apr 2018 16:54:12 +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 E26607354C for ; Thu, 26 Apr 2018 16:54:11 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 95811FB2A7E; Thu, 26 Apr 2018 16:54:11 +0000 (UTC) Delivered-To: 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 81A6AFB2A7D for ; Thu, 26 Apr 2018 16:54:11 +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.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 1649573525 for ; Thu, 26 Apr 2018 16:54:11 +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 46A6A174AF for ; Thu, 26 Apr 2018 16:54:10 +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 w3QGsAOb016251 for ; Thu, 26 Apr 2018 16:54:10 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w3QGsAuE016250 for stable@FreeBSD.org; Thu, 26 Apr 2018 16:54:10 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: stable@FreeBSD.org Subject: [Bug 227603] [panic] r323477: Sleeping thread owns a non-sleepable lock Date: Thu, 26 Apr 2018 16:54:10 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 11.1-STABLE X-Bugzilla-Keywords: crash X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: shurd@FreeBSD.org X-Bugzilla-Status: In Progress X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: shurd@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: 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-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: Thu, 26 Apr 2018 16:54:12 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D227603 --- Comment #4 from Stephen Hurd --- How's it looking? --=20 You are receiving this mail because: You are on the CC list for the bug.= From owner-freebsd-stable@freebsd.org Thu Apr 26 17:02:10 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 A1440FB2EF3 for ; Thu, 26 Apr 2018 17:02:10 +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 39FFB745DE for ; Thu, 26 Apr 2018 17:02:10 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id EDAC4FB2EEC; Thu, 26 Apr 2018 17:02:09 +0000 (UTC) Delivered-To: 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 DB052FB2EEB for ; Thu, 26 Apr 2018 17:02:09 +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.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 77322745D2 for ; Thu, 26 Apr 2018 17:02:09 +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 41996175F1 for ; Thu, 26 Apr 2018 17:02:08 +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 w3QH28p2048443 for ; Thu, 26 Apr 2018 17:02:08 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w3QH287S048441 for stable@FreeBSD.org; Thu, 26 Apr 2018 17:02:08 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: stable@FreeBSD.org Subject: [Bug 227603] [panic] r323477: Sleeping thread owns a non-sleepable lock Date: Thu, 26 Apr 2018 17:02:07 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 11.1-STABLE X-Bugzilla-Keywords: crash X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: eugen@freebsd.org X-Bugzilla-Status: Closed X-Bugzilla-Resolution: FIXED X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: shurd@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: resolution bug_status 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-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: Thu, 26 Apr 2018 17:02:10 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D227603 Eugene Grosbein changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED Status|In Progress |Closed --- Comment #5 from Eugene Grosbein --- (In reply to Stephen Hurd from comment #4) No problems at all with r332734 applied. Thank you! --=20 You are receiving this mail because: You are on the CC list for the bug.= From owner-freebsd-stable@freebsd.org Fri Apr 27 08:16:15 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 36905FC4171 for ; Fri, 27 Apr 2018 08:16:15 +0000 (UTC) (envelope-from ronald-lists@klop.ws) Received: from smarthost1.greenhost.nl (smarthost1.greenhost.nl [195.190.28.92]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id BCC9E753CD for ; Fri, 27 Apr 2018 08:16:14 +0000 (UTC) (envelope-from ronald-lists@klop.ws) Received: from smtp.greenhost.nl ([213.108.110.112]) by smarthost1.greenhost.nl with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.84_2) (envelope-from ) id 1fByJK-00082S-QL for freebsd-stable@freebsd.org; Fri, 27 Apr 2018 10:00:55 +0200 Content-Type: text/plain; charset=utf-8; format=flowed; delsp=yes To: freebsd-stable@freebsd.org Subject: Re: Two USB 4 disk enclosure and a panic References: <55533ad671792b7a30ff00cd1659a02b.squirrel@10.1.1.10> Date: Fri, 27 Apr 2018 10:00:56 +0200 MIME-Version: 1.0 Content-Transfer-Encoding: Quoted-Printable From: "Ronald Klop" Message-ID: In-Reply-To: User-Agent: Opera Mail/12.16 (FreeBSD) X-Authenticated-As-Hash: 398f5522cb258ce43cb679602f8cfe8b62a256d1 X-Virus-Scanned: by clamav at smarthost1.samage.net X-Spam-Level: / X-Spam-Score: -0.2 X-Spam-Status: No, score=-0.2 required=5.0 tests=ALL_TRUSTED, BAYES_50 autolearn=disabled version=3.4.0 X-Scan-Signature: d9e86a85729c02611f348d7c163f195f 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: Fri, 27 Apr 2018 08:16:15 -0000 On Wed, 25 Apr 2018 14:15:03 +0200, Nenhum_de_Nos = wrote: > On Mon, April 23, 2018 23:18, Nenhum_de_Nos wrote: >> Hi, >> >> I would like to know how to debug this. I have two 4 disk enclosures:= >> >> Mediasonic ProBox 4 Bay 3.5' SATA HDD Enclosure =E2=80=93 USB 3.0 & e= SATA >> (HF2-SU3S2) >> NexStar HX4 - NST-640SU3-BK >> >> and both have 4 disk on them, and not all disk are equal. >> >> The issue comes when I plug the probox usb3 enclosure on the system. = I >> can't even read the /var/log/message, it crashes very quickly. >> >> I can see on the boot process up to the point where the second enclos= ure >> comes to be loaded. The 4 disk are shown on the dmesg/console, and th= en = >> a >> core dump happens, the boot process goes to the debug screen and a = >> restart >> happens like a flash. >> >> The motherboard is a Intel=C2=AE Desktop Board D525MW running 8GB RAM= . >> All disk use ZFS, 4 or 5 zpools, one raidz, one mirror and two or thr= ee >> single disk pools. >> FreeBSD xxx 11.1-RELEASE-p7 FreeBSD 11.1-RELEASE-p7 #1 r330596: Thu = >> Mar 8 >> 06:45:59 -03 2018 root@xxx:/usr/obj/usr/src/sys/FreeBSD-11-amd64-= PF >> amd64 >> >> The kernel is a slightly modified generic, just to have altq. >> >> How can I debug this? I have no idea. I have to use two machines to r= un >> all those disks, and I would really like to have just one for it. >> >> Can it be the amount of RAM? The other box is and APU2 from PCEngines= = >> and >> have 4GB ram. apu2 uname -a: FreeBSD yyy 11.1-RELEASE-p4 FreeBSD >> 11.1-RELEASE-p4 #0: Tue Nov 14 06:12:40 UTC 2017 >> root@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd6= 4 >> >> I tried to plug the Vantec hardware on the apu2 box, but there it wou= ld >> not panic, but won't load all vantec disks neither. I really run out = of >> ideas here :( >> >> thanks. >> >> -- >> "We will call you Cygnus, >> the God of balance you shall be." > > Hi, > > I found some logs on the daily security output: > > +ZFS filesystem version: 5 > +ZFS storage pool version: features support (5000) > +panic: Solaris(panic): blkptr at 0xfffff8000b93c848 DVA 1 has invalid= = > VDEV 1 > +cpuid =3D 0 > +KDB: stack backtrace: > +#0 0xffffffff80ab65c7 at kdb_backtrace+0x67 > +#1 0xffffffff80a746a6 at vpanic+0x186 > +#2 0xffffffff80a74513 at panic+0x43 > +#3 0xffffffff82623192 at vcmn_err+0xc2 > +#4 0xffffffff824a73ba at zfs_panic_recover+0x5a > +#5 0xffffffff824ce893 at zfs_blkptr_verify+0x2d3 > +#6 0xffffffff824ce8dc at zio_read+0x2c > +#7 0xffffffff82445fb4 at arc_read+0x6c4 > +#8 0xffffffff824636a4 at dmu_objset_open_impl+0xd4 > +#9 0xffffffff8247eafa at dsl_pool_init+0x2a > +#10 0xffffffff8249b093 at spa_load+0x823 > +#11 0xffffffff8249a2de at spa_load_best+0x6e > +#12 0xffffffff82496a81 at spa_open_common+0x101 > +#13 0xffffffff824e2879 at pool_status_check+0x29 > +#14 0xffffffff824eba3d at zfsdev_ioctl+0x4ed > +#15 0xffffffff809429f8 at devfs_ioctl_f+0x128 > +#16 0xffffffff80ad1f15 at kern_ioctl+0x255 > +CPU: Intel(R) Atom(TM) CPU D525 @ 1.80GHz (1800.11-MHz K8-class CPU= ) > +avail memory =3D 8246845440 (7864 MB) > +Timecounter "TSC" frequency 1800110007 Hz quality 1000 > +GEOM_PART: integrity check failed (ada0s1, BSD) > +GEOM_PART: integrity check failed (diskid/DISK-5LZ0ZDBBs1, BSD) This error also looks interesting. > +ugen1.2: at usbus1 > +ukbd0 on uhub0 > +ukbd0: 2.00/1.30, addr > 2> on usbus1 > +kbd2 at ukbd0 > +ZFS filesystem version: 5 > +ZFS storage pool version: features support (5000) > +re0: link state changed to DOWN > +uhid0 on uhub0 > +uhid0: 2.00/1.30, addr > 2> on usbus1 > +ums0 on uhub0 > +ums0: 2.00/1.30, addr > 2> on usbus1 > +ums0: 3 buttons and [XYZ] coordinates ID=3D0 > +re0: promiscuous mode enabled > +re0: link state changed to UP > > For what I see can be ZFS related. > > If anyone have any hints, please tell :) > > I kinda got curious about this: > > +ZFS storage pool version: features support (5000) > > How can I figure out if my pools are from different versions and may t= his > be the culprit here? zpool upgrade [-v] But I think you can only run this if your machine does not panic. Maybe = on = another machine. Can you get the output of the coredump? On reboot the /etc/rc.d/savecore= = script will look for a valid core dump in the dumpdev (see /etc/rc.conf,= = /etc/defaults/rc.conf) and write it to /var/crash/. That will contain = information which can help people debug this. Regards, Ronald. > > thanks, > > matheus From owner-freebsd-stable@freebsd.org Fri Apr 27 17:54:00 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 44461FAE621 for ; Fri, 27 Apr 2018 17:54:00 +0000 (UTC) (envelope-from bounce@ims9.isendservice.com.br) Received: from ims9.isendservice.com.br (ims9.isendservice.com.br [54.232.186.15]) by mx1.freebsd.org (Postfix) with ESMTP id B27D47217A for ; Fri, 27 Apr 2018 17:53:59 +0000 (UTC) (envelope-from bounce@ims9.isendservice.com.br) Received: from localhost (localhost [127.0.0.1]) by ims9.isendservice.com.br (Postfix) with ESMTP id 05040425CF for ; Fri, 27 Apr 2018 14:44:17 -0300 (BRT) Date: Fri, 27 Apr 2018 14:44:17 -0300 (BRT) From: FIERGS | FATEC - Faculdade SENAI de Tecnologia Reply-To: faculdadesenai@senairs.org.br To: freebsd-stable@freebsd.org Message-ID: <251339140.166142.1524851057960.JavaMail.root@ims9> Subject: =?ISO-8859-1?Q?Vestibular_SENAI-RS_2018-2_|_P?= =?ISO-8859-1?Q?rimeiro_semestre_em_at=E9_9_vezes?= bounce-key: <2420-22522874-2154459> MIME-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 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: Fri, 27 Apr 2018 17:54:00 -0000 From owner-freebsd-stable@freebsd.org Fri Apr 27 17:54:08 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 D8661FAE633 for ; Fri, 27 Apr 2018 17:54:07 +0000 (UTC) (envelope-from Andre.Albsmeier@siemens.com) Received: from david.siemens.de (david.siemens.de [192.35.17.14]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "david.siemens.de", Issuer "Siemens Issuing CA Internet Server 2017" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 6A0597219C; Fri, 27 Apr 2018 17:54:06 +0000 (UTC) (envelope-from Andre.Albsmeier@siemens.com) Received: from mail1.siemens.de (mail1.siemens.de [139.23.33.14]) by david.siemens.de (8.15.2/8.15.2) with ESMTPS id w3RHnGEJ004770 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Fri, 27 Apr 2018 19:49:17 +0200 Received: from curry.mchp.siemens.de (curry.mchp.siemens.de [139.25.40.130]) by mail1.siemens.de (8.15.2/8.15.2) with ESMTP id w3RHnGiB024857; Fri, 27 Apr 2018 19:49:16 +0200 Received: (from user@localhost) by curry.mchp.siemens.de (8.15.2/8.15.2) id w3RHnG9I041800; Date: Fri, 27 Apr 2018 19:49:16 +0200 From: Andre Albsmeier To: Dimitry Andric Cc: Andre Albsmeier , FreeBSD Stable Subject: Re: gptboot broken when compiled with clang 6 and WITHOUT_LOADER_GELI -- clang 5 is OK Message-ID: <20180427174916.GA38967@bali> References: <20180425165840.GA1330@bali> <1FDCF15C-E9FD-4746-9C89-F669EF4BA7C5@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1FDCF15C-E9FD-4746-9C89-F669EF4BA7C5@FreeBSD.org> User-Agent: Mutt/1.7.2 (2016-11-26) 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: Fri, 27 Apr 2018 17:54:08 -0000 On Thu, 26-Apr-2018 at 11:55:19 +0200, Dimitry Andric wrote: > On 25 Apr 2018, at 18:58, Andre Albsmeier wrote: > > > > I have set up a new system disk for an i386 11.2-PRERELEASE box. I did the > > usual > > > > gpart create -s gpt $disk > > gpart add -t freebsd-boot -s 984 $disk > > gpart bootcode -b /boot/pmbr -p /boot/gptboot -i 1 $disk > > ... > > > > thing, just to notice that the box wouldn't boot. It seems to hang where > > stage 2 should be run -- when the '\' should start spinning the screen > > turns white and the box hangs (tested on two machines, an Asus P5W and a > > Supermicro A2SAV). > > > > So I replaced gptboot on the new disk by the one from an older machine > > and everything was fine. I wanted to find out what is actually causing > > the issue and recompiled /usr/src/stand after updating the old sources > > in several steps. > > > > Eventually it turned out that it depends on the compiler. When compiling > > the latest /usr/src/stand with clang 5.0.1 the resulting gptboot works. > > When using 6.0.0 it doesn't. To be exact, it's gptboot.o which is causing > > the problems. When using a gptboot.o from a clang 5 system it is OK, when > > using a gptboot.o from a clang 6 system it fails. > > > > To add more confusion: I usually have WITHOUT_LOADER_GELI in my make.conf. > > When removing this, the resulting gptboot works even when compiled with > > clang 6... > > > > I can reproduce this in case s.o. wants me to do some tests... > > I can't reproduce it on my end, unfortunately. I downloaded the latest > FreeBSD-11.2-PRERELEASE-i386-20180420-r332802 snapshot, installed it to > a GPT partitioned disk, and it boots just fine. > > This snapshot corresponds to r332802, which has clang 6.0.0, with the > EFLAGS change still reverted, so I assume its copy of gptboot is also > compiled with that. > > Which exact revision of the base system were you using? I have done some updates in the meantime and can't tell which revision it was (it was just a few days ago). Currently, the buildbox is at 333056 and I have just compiled gptboot (with WITHOUT_LOADER_GELI) and I am seeing its size is -rw-rw---- 1 andre wheel 20859 27 Apr 19:42 gptboot This is the size where it didn't work but I can't test it at the moment as the build machine and the test environment are @work. I am pretty sure it will fail as there weren't any changes to stand or clang in the last few days but let's wait until Monday when I can verify it... -Andre From owner-freebsd-stable@freebsd.org Fri Apr 27 17:55: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 65B06FAE6F2 for ; Fri, 27 Apr 2018 17:55:49 +0000 (UTC) (envelope-from Andre.Albsmeier@siemens.com) Received: from david.siemens.de (david.siemens.de [192.35.17.14]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "david.siemens.de", Issuer "Siemens Issuing CA Internet Server 2017" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id C250C724B0; Fri, 27 Apr 2018 17:55:48 +0000 (UTC) (envelope-from Andre.Albsmeier@siemens.com) Received: from mail1.siemens.de (mail1.siemens.de [139.23.33.14]) by david.siemens.de (8.15.2/8.15.2) with ESMTPS id w3RHtkKF011472 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Fri, 27 Apr 2018 19:55:46 +0200 Received: from curry.mchp.siemens.de (curry.mchp.siemens.de [139.25.40.130]) by mail1.siemens.de (8.15.2/8.15.2) with ESMTP id w3RHtjcl011495; Fri, 27 Apr 2018 19:55:45 +0200 Received: (from user@localhost) by curry.mchp.siemens.de (8.15.2/8.15.2) id w3RHtkVB041822; Date: Fri, 27 Apr 2018 19:55:45 +0200 From: Andre Albsmeier To: Dimitry Andric Cc: Dewayne Geraghty , FreeBSD Stable , Andre Albsmeier Subject: Re: gptboot broken when compiled with clang 6 and WITHOUT_LOADER_GELI -- clang 5 is OK Message-ID: <20180427175545.GB38967@bali> References: <20180425165840.GA1330@bali> <3A857D03-607A-4983-A4C2-D3A93119297A@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3A857D03-607A-4983-A4C2-D3A93119297A@FreeBSD.org> User-Agent: Mutt/1.7.2 (2016-11-26) 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: Fri, 27 Apr 2018 17:55:49 -0000 On Thu, 26-Apr-2018 at 12:06:21 +0200, Dimitry Andric wrote: > On 26 Apr 2018, at 06:17, Dewayne Geraghty wrote: > > > > Andre, You're not alone. I think there's a problem with clang6 on i386 > > FreeBSD 11.1X, refer: > > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227552 > > https://forums.freebsd.org/threads/uptime-w-i386-breakage.65584/ > > and perhaps also on amd64, search for > > https://bugs.freebsd.org/bugzilla/buglist.cgi?quicksearch=clang&list_id=226390. > > > > Without time to investigate I've reverted userland > > FreeBSD 11.2-PRERELEASE r332843M amd64 1101515 1101509 > > FreeBSD 11.2-PRERELEASE r332843M i386 1101515 1101509 > > As noted in another post, I cannot reproduce the problems with gptboot, > but with FreeBSD-11.2-PRERELEASE-i386-20180420-r332802, I do indeed see > w and uptime crashing in libxo: Scary, seems to be OK here: buildbox:~>cat /usr/src/.svn_revision 333056 buildbox:~>uname -K -m i386 1101515 buildbox:~>w 19:51 up 4:41, 1 user, load averages: 0,25 0,26 0,21 USER TTY FROM LOGIN@ IDLE WHAT andre pts/0 bali 19:42 - w buildbox:~>uptime 19:51 up 4:41, 1 user, load averages: 0,25 0,26 0,21 buildbox:~>ll /lib/libxo.so.0 -r--r--r-- 1 root wheel 97596 27 Apr 15:07 /lib/libxo.so.0 buildbox:~> -Andre > > (gdb) bt > #0 ifree (tsd=0x28000000) at arena.h:799 > #1 0x2814b506 in __free (ptr=0x280601ef) at tsd.h:716 > #2 0x2808bb07 in xo_do_emit_fields () at /usr/src/contrib/libxo/libxo/libxo.c:6419 > #3 0x28089a1c in xo_do_emit (xop=, flags=, fmt=0x804ad4d "{:time-of-day/%s} ") at /usr/src/contrib/libxo/libxo/libxo.c:6470 > #4 0x28089b61 in xo_emit (fmt=0x804ad4d "{:time-of-day/%s} ") at /usr/src/contrib/libxo/libxo/libxo.c:6541 > #5 0x08049f50 in main (argc=, argv=) at /usr/src/usr.bin/w/w.c:475 > #6 0x080494cd in _start1 () > #7 0x08049448 in _start () > #8 0x00000000 in ?? () > > Not sure if this has anything to do with clang though, it looks more > like a double free to me, at first glance. I'll do some debugging. > > -Dimitry > -- Unix is very userfriendly. It's just picky who its friends are. From owner-freebsd-stable@freebsd.org Sat Apr 28 12:46:48 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 8C0AAFAE1E3 for ; Sat, 28 Apr 2018 12:46:48 +0000 (UTC) (envelope-from wjw@digiware.nl) 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 1C9C87C213 for ; Sat, 28 Apr 2018 12:46:48 +0000 (UTC) (envelope-from wjw@digiware.nl) Received: by mailman.ysv.freebsd.org (Postfix) id C7878FAE1E2; Sat, 28 Apr 2018 12:46:47 +0000 (UTC) Delivered-To: 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 B4392FAE1E1 for ; Sat, 28 Apr 2018 12:46:47 +0000 (UTC) (envelope-from wjw@digiware.nl) Received: from smtp.digiware.nl (smtp.digiware.nl [IPv6:2001:4cb8:90:ffff::3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 3C49B7C212 for ; Sat, 28 Apr 2018 12:46:47 +0000 (UTC) (envelope-from wjw@digiware.nl) Received: from router.digiware.nl (localhost.digiware.nl [127.0.0.1]) by smtp.digiware.nl (Postfix) with ESMTP id A914D3D0F2; Sat, 28 Apr 2018 14:46:44 +0200 (CEST) X-Virus-Scanned: amavisd-new at digiware.com Received: from smtp.digiware.nl ([127.0.0.1]) by router.digiware.nl (router.digiware.nl [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4h7ho_wRZZyq; Sat, 28 Apr 2018 14:46:44 +0200 (CEST) Received: from [192.168.101.151] (unknown [192.168.101.151]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.digiware.nl (Postfix) with ESMTPSA id 24D233D0EC for ; Sat, 28 Apr 2018 14:46:44 +0200 (CEST) To: "stable@freebsd.org" From: Willem Jan Withagen Subject: ZFS: Can't find pool by guid Message-ID: Date: Sat, 28 Apr 2018 14:46:44 +0200 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: nl Content-Transfer-Encoding: 7bit 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: Sat, 28 Apr 2018 12:46:48 -0000 Hi, I upgraded a server from 10.4 to 11.1 and now al of a sudden the server complains about: ZFS: Can't find pool by guid And I end up in the boot prompt: lsdev gives disk0 withe on p1 the partion that the zroot is/was. This is an active server, so redoing install and stuf is nog going to be real workable.... So how do I get this to boot? Thanx, --WjW From owner-freebsd-stable@freebsd.org Sat Apr 28 15:19:02 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 033B9FB1DBF for ; Sat, 28 Apr 2018 15:19:02 +0000 (UTC) (envelope-from slw@zxy.spb.ru) 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 945CF76D19 for ; Sat, 28 Apr 2018 15:19:01 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: by mailman.ysv.freebsd.org (Postfix) id 5025EFB1DBE; Sat, 28 Apr 2018 15:19:01 +0000 (UTC) Delivered-To: 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 3DA0EFB1DBD for ; Sat, 28 Apr 2018 15:19:01 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from zxy.spb.ru (zxy.spb.ru [195.70.199.98]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id CED6E76CFE for ; Sat, 28 Apr 2018 15:19:00 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from slw by zxy.spb.ru with local (Exim 4.86 (FreeBSD)) (envelope-from ) id 1fCRci-000Fp0-1V for stable@freebsd.org; Sat, 28 Apr 2018 18:18:52 +0300 Date: Sat, 28 Apr 2018 18:18:52 +0300 From: Slawa Olhovchenkov To: stable@freebsd.org Subject: vmstat -m stranges Message-ID: <20180428151851.GB80496@zxy.spb.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.24 (2015-08-30) X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: slw@zxy.spb.ru X-SA-Exim-Scanned: No (on zxy.spb.ru); SAEximRunCond expanded to false 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: Sat, 28 Apr 2018 15:19:02 -0000 # vmstat -m|grep temp Type InUse MemUse HighUse Requests Size(s) temp 60 18014398509481829K - 32350974 16,32,64,128,256,512,1024,2048,4096,8192,16384,32768,65536 Is this normal? SVN rev: r328463