From owner-freebsd-stable@freebsd.org Sun Jan 21 05:45:20 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B2580EBA34F for ; Sun, 21 Jan 2018 05:45:20 +0000 (UTC) (envelope-from marklmi26-fbsd@yahoo.com) Received: from sonic302-2.consmr.mail.bf2.yahoo.com (sonic302-2.consmr.mail.bf2.yahoo.com [74.6.135.41]) (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 7CBAB7CA0B for ; Sun, 21 Jan 2018 05:45:20 +0000 (UTC) (envelope-from marklmi26-fbsd@yahoo.com) X-YMail-OSG: YbgAjaYVM1kQ_.Xf3i_phZ0PqObl1aKgC3BM.hB770xnvA8VqI0TkS8SKf_i.CU B8xFB2KX7MODkY1YDMLjicyhuRKTtJTOQ3IY_ROorNUp0mh0U2i6aP1FCEKJaFbkiOTc5_nmxZ2R 6qcmISodj8Fj1vr0fEOb7X1vPVthymhMYXMOxkAT9gIVqtCSC4u2FlW_K2b05ue_2lGqZ7DzNKUj quohk1WSJ2A44iOSFJbstijixQMV5MF4pgp3bF5BghQDoZFpNWZCynnjKWp5mkJYxpNE8KFwzbKY BuqE76URuF8okfhaiJavDAdEwk0vgaXL53FFnW1r3cV3NFTWXDcviywC6QD7PSPj7oUTYl_UCbu7 SLIEqVva8azDJU90LPEvHpR2bpPgjNK.vYa5Bv2CRwuZ5LygqyJggEmrOJ7Hc5DXZ86Sjdl5bHkj 6xgHxjqeBR6ZtP6ylzm4hubQGTP2na9dSqSxo.rcmicuCXVVnKfnCg2fgtqoFjABN.e3q Received: from sonic.gate.mail.ne1.yahoo.com by sonic302.consmr.mail.bf2.yahoo.com with HTTP; Sun, 21 Jan 2018 05:45:18 +0000 Received: from smtp101.rhel.mail.bf1.yahoo.com (EHLO [192.168.1.25]) ([68.142.231.32]) by smtp406.mail.bf1.yahoo.com (JAMES SMTP Server ) with ESMTPA ID 9f113e08b0ed9d35724c74f10c242fb7; Sun, 21 Jan 2018 05:45:15 +0000 (UTC) From: Mark Millard Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Re: Ryzen issues on FreeBSD ? Message-Id: Date: Sat, 20 Jan 2018 21:45:14 -0800 To: Don Lewis , FreeBSD-STABLE Mailing List X-Mailer: Apple Mail (2.3273) 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, 21 Jan 2018 05:45:20 -0000 Don Lewis truckman at FreeBSD.org wrote on Sat Jan 20 02:35:40 UTC 2018 : > The only real problem with the old CPUs is the random segfault problem > and some other random strangeness, like the lang/ghc build almost always > failing. At one time you had written ( https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221029 comment #103 on 2017-Oct-09): QUOTE The ghc build failure seems to be gone after upgrading the a more recent 12.0-CURRENT. I will try to bisect for the fix when I have a chance. END QUOTE Did that not pan out? Did you conclude it was hardware-context specific? === Mark Millard marklmi26-fbsd at yahoo.com ( markmi at dsl-only.net is going away in 2018-Feb, late) From owner-freebsd-stable@freebsd.org Sun Jan 21 13:25:16 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 739FEECAA5A for ; Sun, 21 Jan 2018 13:25:16 +0000 (UTC) (envelope-from nimrod@nimrod.is-a-geek.net) Received: from mail-yb0-x231.google.com (mail-yb0-x231.google.com [IPv6:2607:f8b0:4002:c09::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 32A976BC3B for ; Sun, 21 Jan 2018 13:25:15 +0000 (UTC) (envelope-from nimrod@nimrod.is-a-geek.net) Received: by mail-yb0-x231.google.com with SMTP id z90so2289306ybh.11 for ; Sun, 21 Jan 2018 05:25:15 -0800 (PST) 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=Ib9tOmEuDzrqehabAOYH2+3oZAD9l5hFIcGA/7ndKnY=; b=C1f3OhFlZtYWaUnLpma/MMG3kSrH3yNXupyk0WRx+L8M1/RURDxeAxUk/GdftN/39D iKuhXIJFsyZZnkpytufm89h6YSYxFyKb8odKekqTTcdQyH8V6zgOstkIHUxzBF3TASM6 ywR2zwtuKztnV003Btw2t4QqgIzvvj1mt1W6dNesACqON00DFiw6YSXmdRZ9z2yux+9n SXc/oJW2c9kRxfqaZEpXcj8AQtthnXLWsBX0fc4uyI4UTQhbxwvMMoW7VHSO4FS4TZuq 8hnQrDkapD/PJdQABrSb6SIhIXBGC4jKpDw8FvjFvXWyY4pn5tGT5rGWy0OUukIeY1lo 9RUA== 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=Ib9tOmEuDzrqehabAOYH2+3oZAD9l5hFIcGA/7ndKnY=; b=M4jMs/uN4hRYAlBqGUfJ8uqBxaR+/+Y0Z4jBL4oa85DOnQxF1Yy/4TcujqnPA1wGqG nHEUqQ8mjZIenpr5n8Pm/57/pWfAKHJyXp5kkoeJc0aoqqceSbKhJTw2r3IpW3CSFxiw KxMU4fzI52rG5SOdkfu7Rg+2aXtrNlh/GXtQLzVHXyRmLmPiLOZQ41JyZxewDDRngDtt nEzyZiYuHXEU9I7auwMmSPawGoAkmrQa+pBEZ2tW549Q9yYu8kLca7ur1H+9+yUY6tFC TDUApA07kiQkHiVHH105vpCTlbqH/H/VGvVyXf8Ro135UPwoP8qokeBIjaDChPd+3ZXf RBig== X-Gm-Message-State: AKwxyte9nGEnkZ8GGeMkcmIa1akYyZNvYIDWMb9MpRpAw9NYiFHWC7uu IaYgiV+uAMjgt5L1WMQ3TDAnCPj0+Cq5AYIH1FhHmw== X-Google-Smtp-Source: AH8x226IPbTIYIks2uIuCjtJX/q/qE1h4vE2QQnuu1Y9zYCPezborULrD7JZ20SciltyR2Bay9dWwP2FQEKybs6abz8= X-Received: by 10.37.97.205 with SMTP id v196mr4377293ybb.511.1516541114721; Sun, 21 Jan 2018 05:25:14 -0800 (PST) MIME-Version: 1.0 References: <8e842dec-ade7-37d1-6bd8-856ea1a827ca@sentex.net> <3b625072-dfb3-6b4f-494d-7fe1b2fa554c@ingresso.co.uk> <2c6ce4dd-f43c-7c40-abc2-732d6f8996ec@sentex.net> <795dbb79-3c18-d967-98b9-5d09a740dbfe@sentex.net> <9b769e4e-b098-b294-0bce-8bb1c42e8a59@rootautomation.com> In-Reply-To: From: Nimrod Levy Date: Sun, 21 Jan 2018 13:25:03 +0000 Message-ID: Subject: Re: Ryzen issues on FreeBSD ? To: Mike Tancsa Cc: Ryan Root , freebsd-stable@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, 21 Jan 2018 13:25:16 -0000 almost 2 days uptime with a lower memory clock. still holding my breath, but this seems promising. On Fri, Jan 19, 2018 at 4:02 PM Nimrod Levy wrote: > I can try lowering my memory clock and see what happens. I'm a little > skeptical because I have been able to run memtest with no errors for some > time. I'm glad to give anything a try... > > > On Fri, Jan 19, 2018 at 3:49 PM Mike Tancsa wrote: > >> On 1/19/2018 3:23 PM, Ryan Root wrote: >> > This looks like the QVL list for your MB -> >> > >> http://download.gigabyte.us/FileList/Memory/mb_memory_ga-ax370-Gaming5.pdf >> >> Its an Asus MB, but the memory I have is in the above PDF list >> >> I dont see CT16G4DFD824A, but I do see other crucial products with >> slower clock speeds. Right now I do have it set to 2133 where as it was >> 2400 before. >> >> ---Mike >> >> >> > >> > >> > On 1/19/2018 12:13 PM, Mike Tancsa wrote: >> >> Drag :( I have mine disabled as well as lowering the RAM freq to 2100 >> >> from 2400. For me the hangs are infrequent. Its only been a day and a >> >> half, so not sure if its gone or I have been "lucky"... Either ways, >> >> this platform feels way too fragile to deploy on anything :( >> >> >> >> ---Mike >> >> >> >> On 1/19/2018 3:08 PM, Nimrod Levy wrote: >> >>> Looks like disabling the C- states in the bios didn't change >> anything. >> >>> >> >>> On Wed, Jan 17, 2018 at 9:22 PM Nimrod Levy > >>> > wrote: >> >>> >> >>> That looks promising. I just found that seeing in the bios and >> >>> disabled it. I'll see how it runs. >> >>> >> >>> Thanks >> >>> >> >>> >> >>> On Wed, Jan 17, 2018, 18:38 Don Lewis > >>> > wrote: >> >>> >> >>> On 17 Jan, Nimrod Levy wrote: >> >>> > I'm running 11-STABLE from 12/9. amdtemp works for me. It >> >>> also has the >> >>> > systl indicating that it it has the shared page fix. I'm >> >>> pretty sure I've >> >>> > seen the lockups since then. I'll update to the latest >> STABLE >> >>> and see >> >>> > what happens. >> >>> > >> >>> > One weird thing about my experience is that if I keep >> >>> something running >> >>> > continuously like the distributed.net < >> http://distributed.net> >> >>> client on 6 of 12 possible threads, >> >>> > it keeps the system up for MUCH longer than without. This >> is >> >>> a home server >> >>> > and very lightly loaded (one could argue insanely >> overpowered >> >>> for the use >> >>> > case). >> >>> >> >>> This sounds like the problem with the deep Cx states that has >> been >> >>> reported by numerous Linux users. I think some motherboard >> >>> brands are >> >>> more likely to have the problem. See: >> >>> >> http://forum.asrock.com/forum_posts.asp?TID=5963&title=taichi-x370-with-ubuntu-idle-lock-ups-idle-freeze >> >>> >> >>> -- >> >>> >> >>> -- >> >>> Nimrod >> >>> >> >>> >> >>> >> >>> -- >> >>> >> >>> -- >> >>> Nimrod >> >>> >> >> >> > >> > >> > _______________________________________________ >> > 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" >> > >> > >> >> >> -- >> ------------------- >> Mike Tancsa, tel +1 519 651 3400 <(519)%20651-3400> >> Sentex Communications, mike@sentex.net >> Providing Internet services since 1994 www.sentex.net >> Cambridge, Ontario Canada http://www.tancsa.com/ >> _______________________________________________ >> 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 Jan 21 19:06:05 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 34A3DEB4E2E for ; Sun, 21 Jan 2018 19:06:05 +0000 (UTC) (envelope-from peter@hda3.com) Received: from mail-qt0-x22f.google.com (mail-qt0-x22f.google.com [IPv6:2607:f8b0:400d:c0d::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id E5BEE77B0D for ; Sun, 21 Jan 2018 19:06:04 +0000 (UTC) (envelope-from peter@hda3.com) Received: by mail-qt0-x22f.google.com with SMTP id s39so15788289qth.7 for ; Sun, 21 Jan 2018 11:06:04 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hda3-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=VRJABj1lr8fH57xoX8YeMLbR+v1cGVG6Dk5COsHxpb4=; b=stt3M7sa8eQBX0XFVANGulAcZHRQii36ReG7OaKDltb+r4etd28tO9g13AzIxouIw9 CXMAKQGsvBNcnlQJ2IC8/u+Dee7aITaNi2N50Ng+oNWz6/ViczMMRaM1JKpgobiyEwUH JRSuDc20Y07xVClgYSLqZqUO5yA1Q0lLGKH9qIOTxH61sbgjP0epc7eitJKBB+NfI9TD F5NArgxMDtPAepQvNBPllJ1pkAowHkyRTveajwuS+0kJBiM0Gla6Gfu83VV+BrO0UbEp BKjA0t7U6mjLqroBcgSJ82Daf1QsTtlOgGFUQP4ICwdgZq6C1k+j1LcCVkf/3ou+eYH6 Vd1Q== 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=VRJABj1lr8fH57xoX8YeMLbR+v1cGVG6Dk5COsHxpb4=; b=Y3lJ8uhfhIbu9UQU7mhlVkupBZ4wbxyUYni9QRUvmosvy8lEbLrzTEiU6fuhbusfwh GE2JmUT+hAUxSJ9zs309daWjZ4DmsyKDE3rNTgWKYuSuGnGvjov//1HGIOc216QKYrcp O+GFr8J2kPt8ZFuy2y7LVuOpLZQrMD88Y/V1ajh3j983+omLw+C22sLy3aBJo1Cjr4+8 2vLS+cw3tajZQECJkA20xks+XWBGBO8f9XUfOyhH63eigH/6n04ciMgWGNRABtPZFCEX XSaig9LznStEIjrtwmLsg1bs82XRb5h+KRo9VP8CfYoy+pN04FgrGzagRlqPNjY3AMYH xoCA== X-Gm-Message-State: AKwxytdXsx86viR1LKrD/kxtorB1c9BOQGWpsVbs2v/W4M9byG06QENz rA7PBSiQqLEmct1MRqo9p47bGItyqbvwc08WYbfYSg== X-Google-Smtp-Source: AH8x224XBAXFNfK8hFslZS9eBnMyCswlbO1YapSqbdTipBBkiQq+vo7V8NcZOygjfLo6rEJVgj/IVnl2D2xdBeOSsTw= X-Received: by 10.200.23.66 with SMTP id u2mr7459832qtk.294.1516561563730; Sun, 21 Jan 2018 11:06:03 -0800 (PST) MIME-Version: 1.0 Received: by 10.140.39.83 with HTTP; Sun, 21 Jan 2018 11:05:43 -0800 (PST) In-Reply-To: References: <8e842dec-ade7-37d1-6bd8-856ea1a827ca@sentex.net> <3b625072-dfb3-6b4f-494d-7fe1b2fa554c@ingresso.co.uk> <2c6ce4dd-f43c-7c40-abc2-732d6f8996ec@sentex.net> <795dbb79-3c18-d967-98b9-5d09a740dbfe@sentex.net> <9b769e4e-b098-b294-0bce-8bb1c42e8a59@rootautomation.com> From: Peter Moody Date: Sun, 21 Jan 2018 11:05:43 -0800 Message-ID: Subject: Re: Ryzen issues on FreeBSD ? To: Nimrod Levy Cc: Mike Tancsa , freebsd-stable@freebsd.org, Ryan Root Content-Type: text/plain; charset="UTF-8" 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, 21 Jan 2018 19:06:05 -0000 hm, so i've got nearly 3 days of uptime with smt disabled. unfortunately this means that my otherwise '12' cores is actually only '6'. I'm also getting occasional segfaults compiling go programs. should I just RMA this beast again? On Sun, Jan 21, 2018 at 5:25 AM, Nimrod Levy wrote: > almost 2 days uptime with a lower memory clock. still holding my breath, > but this seems promising. > > > > On Fri, Jan 19, 2018 at 4:02 PM Nimrod Levy wrote: > >> I can try lowering my memory clock and see what happens. I'm a little >> skeptical because I have been able to run memtest with no errors for some >> time. I'm glad to give anything a try... >> >> >> On Fri, Jan 19, 2018 at 3:49 PM Mike Tancsa wrote: >> >>> On 1/19/2018 3:23 PM, Ryan Root wrote: >>> > This looks like the QVL list for your MB -> >>> > >>> http://download.gigabyte.us/FileList/Memory/mb_memory_ga-ax370-Gaming5.pdf >>> >>> Its an Asus MB, but the memory I have is in the above PDF list >>> >>> I dont see CT16G4DFD824A, but I do see other crucial products with >>> slower clock speeds. Right now I do have it set to 2133 where as it was >>> 2400 before. >>> >>> ---Mike >>> >>> >>> > >>> > >>> > On 1/19/2018 12:13 PM, Mike Tancsa wrote: >>> >> Drag :( I have mine disabled as well as lowering the RAM freq to 2100 >>> >> from 2400. For me the hangs are infrequent. Its only been a day and a >>> >> half, so not sure if its gone or I have been "lucky"... Either ways, >>> >> this platform feels way too fragile to deploy on anything :( >>> >> >>> >> ---Mike >>> >> >>> >> On 1/19/2018 3:08 PM, Nimrod Levy wrote: >>> >>> Looks like disabling the C- states in the bios didn't change >>> anything. >>> >>> >>> >>> On Wed, Jan 17, 2018 at 9:22 PM Nimrod Levy >> >>> > wrote: >>> >>> >>> >>> That looks promising. I just found that seeing in the bios and >>> >>> disabled it. I'll see how it runs. >>> >>> >>> >>> Thanks >>> >>> >>> >>> >>> >>> On Wed, Jan 17, 2018, 18:38 Don Lewis >> >>> > wrote: >>> >>> >>> >>> On 17 Jan, Nimrod Levy wrote: >>> >>> > I'm running 11-STABLE from 12/9. amdtemp works for me. It >>> >>> also has the >>> >>> > systl indicating that it it has the shared page fix. I'm >>> >>> pretty sure I've >>> >>> > seen the lockups since then. I'll update to the latest >>> STABLE >>> >>> and see >>> >>> > what happens. >>> >>> > >>> >>> > One weird thing about my experience is that if I keep >>> >>> something running >>> >>> > continuously like the distributed.net < >>> http://distributed.net> >>> >>> client on 6 of 12 possible threads, >>> >>> > it keeps the system up for MUCH longer than without. This >>> is >>> >>> a home server >>> >>> > and very lightly loaded (one could argue insanely >>> overpowered >>> >>> for the use >>> >>> > case). >>> >>> >>> >>> This sounds like the problem with the deep Cx states that has >>> been >>> >>> reported by numerous Linux users. I think some motherboard >>> >>> brands are >>> >>> more likely to have the problem. See: >>> >>> >>> http://forum.asrock.com/forum_posts.asp?TID=5963&title=taichi-x370-with-ubuntu-idle-lock-ups-idle-freeze >>> >>> >>> >>> -- >>> >>> >>> >>> -- >>> >>> Nimrod >>> >>> >>> >>> >>> >>> >>> >>> -- >>> >>> >>> >>> -- >>> >>> Nimrod >>> >>> >>> >> >>> > >>> > >>> > _______________________________________________ >>> > 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" >>> > >>> > >>> >>> >>> -- >>> ------------------- >>> Mike Tancsa, tel +1 519 651 3400 <(519)%20651-3400> >>> Sentex Communications, mike@sentex.net >>> Providing Internet services since 1994 www.sentex.net >>> Cambridge, Ontario Canada http://www.tancsa.com/ >>> _______________________________________________ >>> 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 > _______________________________________________ > 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 Sun Jan 21 20:02:54 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A7358EB7BBE for ; Sun, 21 Jan 2018 20:02:54 +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 6F89379F1E; Sun, 21 Jan 2018 20:02:54 +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 6736B2EC2B; Sun, 21 Jan 2018 21:02:43 +0100 (CET) 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 MCJ5Rj1aFvK3; Sun, 21 Jan 2018 21:02:42 +0100 (CET) Received: from [192.168.11.152] (unknown [192.168.11.152]) (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 A71FD2EC2A; Sun, 21 Jan 2018 21:02:42 +0100 (CET) Subject: Re: Ryzen issues on FreeBSD ? To: Don Lewis , Pete French Cc: freebsd-stable@freebsd.org References: <8e842dec-ade7-37d1-6bd8-856ea1a827ca@sentex.net> <8dcf6cc8fad788ac8168a4a9f392b02e@foolishgames.com> <23c1d162-dcd8-c422-3114-d70b65b6c271@sentex.net> <00875e4d-740f-63f1-496c-6cda82b1a403@ingresso.co.uk> From: Willem Jan Withagen Message-ID: <52744797-0606-44e7-72dd-242a6b56066a@digiware.nl> Date: Sun, 21 Jan 2018 21:02:43 +0100 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.5.2 MIME-Version: 1.0 In-Reply-To: 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: Sun, 21 Jan 2018 20:02:54 -0000 On 19/01/2018 23:29, Don Lewis wrote: > On 19 Jan, Pete French wrote: >> Out of interest, is there anyone out there running Ryzen who *hasnt* >> seen lockups ? I'd be curious if there a lot of lurkers thinking "mine >> works fine" > > No hangs or silent reboots here with either my original CPU or warranty > replacement once the shared page fix was in place. Perhaps a too weird reference: I have supplied a customer with a Ryzen5 and a 350MB motherboard. But he runs Windows 10, but I haven't heard him complain about anything like this. But I'll ask him specific. --WjW From owner-freebsd-stable@freebsd.org Sun Jan 21 20:17:59 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B57A2EB86B2 for ; Sun, 21 Jan 2018 20:17: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 938D97A5D1 for ; Sun, 21 Jan 2018 20:17:59 +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 w0LKIMQm088878 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=FAIL); Sun, 21 Jan 2018 20:18:24 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 w0LKHnFB040195 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 21 Jan 2018 12:17:51 -0800 (PST) (envelope-from truckman@FreeBSD.org) Date: Sun, 21 Jan 2018 12:17:44 -0800 (PST) From: Don Lewis Subject: Re: Ryzen issues on FreeBSD ? To: Mark Millard cc: FreeBSD-STABLE Mailing List 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, 21 Jan 2018 20:17:59 -0000 On 20 Jan, Mark Millard wrote: > Don Lewis truckman at FreeBSD.org wrote on > Sat Jan 20 02:35:40 UTC 2018 : > >> The only real problem with the old CPUs is the random segfault problem >> and some other random strangeness, like the lang/ghc build almost always >> failing. > > > At one time you had written > ( https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221029 > comment #103 on 2017-Oct-09): > > QUOTE > The ghc build failure seems to be gone after upgrading the a > more recent 12.0-CURRENT. I will try to bisect for the fix > when I have a chance. > END QUOTE > > Did that not pan out? Did you conclude it was > hardware-context specific? I was never able to reproduce the problem. It seems like it failed on the first ports build run after I replaced the CPU. When I upgraded the OS and ports, the build succeeded. I tried going back to much earlier OS and ports versions, but I could never get the ghc build to fail again. I'm baffled by this ... From owner-freebsd-stable@freebsd.org Sun Jan 21 20:24:16 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 23458EB8EB4 for ; Sun, 21 Jan 2018 20:24:16 +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 023427AC61 for ; Sun, 21 Jan 2018 20:24:15 +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 w0LKOYg7088898 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=FAIL); Sun, 21 Jan 2018 20:24:35 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 w0LKHnFE040195 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 21 Jan 2018 12:24:02 -0800 (PST) (envelope-from truckman@FreeBSD.org) Date: Sun, 21 Jan 2018 12:24:02 -0800 (PST) From: Don Lewis Subject: Re: Ryzen issues on FreeBSD ? To: Willem Jan Withagen cc: Pete French , freebsd-stable@freebsd.org In-Reply-To: <52744797-0606-44e7-72dd-242a6b56066a@digiware.nl> Message-ID: References: <8e842dec-ade7-37d1-6bd8-856ea1a827ca@sentex.net> <8dcf6cc8fad788ac8168a4a9f392b02e@foolishgames.com> <23c1d162-dcd8-c422-3114-d70b65b6c271@sentex.net> <00875e4d-740f-63f1-496c-6cda82b1a403@ingresso.co.uk> <52744797-0606-44e7-72dd-242a6b56066a@digiware.nl> 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, 21 Jan 2018 20:24:16 -0000 On 21 Jan, Willem Jan Withagen wrote: > On 19/01/2018 23:29, Don Lewis wrote: >> On 19 Jan, Pete French wrote: >>> Out of interest, is there anyone out there running Ryzen who *hasnt* >>> seen lockups ? I'd be curious if there a lot of lurkers thinking "mine >>> works fine" >> >> No hangs or silent reboots here with either my original CPU or warranty >> replacement once the shared page fix was in place. > > Perhaps a too weird reference: > > I have supplied a customer with a Ryzen5 and a 350MB motherboard. > But he runs Windows 10, but I haven't heard him complain about anything > like this. > But I'll ask him specific. Only the BSDs were affected by the shared page issue. I think Linux already had a guard page. I don't think Windows was affected by the idle C-state issue. I suspect it is caused by software not doing the right thing during C-state transitions, but the publicly available documentation from AMD is pretty lacking. The random segfault issue is primarily triggered by heavy parallel software build loads and how many Windows users do that? From owner-freebsd-stable@freebsd.org Sun Jan 21 20:50:53 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 11D0FEBA5FA for ; Sun, 21 Jan 2018 20:50:53 +0000 (UTC) (envelope-from wjw@digiware.nl) Received: from smtp.digiware.nl (smtp.digiware.nl [176.74.240.9]) (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 CA7567BB70; Sun, 21 Jan 2018 20:50:52 +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 043752E952; Sun, 21 Jan 2018 21:50:50 +0100 (CET) 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 68mqbj8tkfxL; Sun, 21 Jan 2018 21:50:49 +0100 (CET) Received: from [192.168.11.152] (unknown [192.168.11.152]) (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 643652E951; Sun, 21 Jan 2018 21:50:49 +0100 (CET) Subject: Re: Ryzen issues on FreeBSD ? To: Don Lewis Cc: Pete French , freebsd-stable@freebsd.org References: <8e842dec-ade7-37d1-6bd8-856ea1a827ca@sentex.net> <8dcf6cc8fad788ac8168a4a9f392b02e@foolishgames.com> <23c1d162-dcd8-c422-3114-d70b65b6c271@sentex.net> <00875e4d-740f-63f1-496c-6cda82b1a403@ingresso.co.uk> <52744797-0606-44e7-72dd-242a6b56066a@digiware.nl> From: Willem Jan Withagen Message-ID: <86eba4e4-f9a7-7177-a6bf-12700b1defa0@digiware.nl> Date: Sun, 21 Jan 2018 21:50:50 +0100 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.5.2 MIME-Version: 1.0 In-Reply-To: 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: Sun, 21 Jan 2018 20:50:53 -0000 On 21/01/2018 21:24, Don Lewis wrote: > On 21 Jan, Willem Jan Withagen wrote: >> On 19/01/2018 23:29, Don Lewis wrote: >>> On 19 Jan, Pete French wrote: >>>> Out of interest, is there anyone out there running Ryzen who *hasnt* >>>> seen lockups ? I'd be curious if there a lot of lurkers thinking "mine >>>> works fine" >>> >>> No hangs or silent reboots here with either my original CPU or warranty >>> replacement once the shared page fix was in place. >> >> Perhaps a too weird reference: >> >> I have supplied a customer with a Ryzen5 and a 350MB motherboard. >> But he runs Windows 10, but I haven't heard him complain about anything >> like this. >> But I'll ask him specific. > > Only the BSDs were affected by the shared page issue. I think Linux > already had a guard page. I don't think Windows was affected by the > idle C-state issue. I suspect it is caused by software not doing the > right thing during C-state transitions, but the publicly available > documentation from AMD is pretty lacking. The random segfault issue is > primarily triggered by heavy parallel software build loads and how many > Windows users do that? This is an adobe workstation where several users remote login and do work. So I would assume that the system is seriously (ab)used. Adn as expected I'm know aware of any of the detailed things that Windows does while powering into lesser active states. --WjW From owner-freebsd-stable@freebsd.org Sun Jan 21 20:52:29 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id ADCD7EBA9C9 for ; Sun, 21 Jan 2018 20:52:29 +0000 (UTC) (envelope-from kraduk@gmail.com) Received: from mail-io0-x235.google.com (mail-io0-x235.google.com [IPv6:2607:f8b0:4001:c06::235]) (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 747327BF0F for ; Sun, 21 Jan 2018 20:52:29 +0000 (UTC) (envelope-from kraduk@gmail.com) Received: by mail-io0-x235.google.com with SMTP id f34so7406842ioi.13 for ; Sun, 21 Jan 2018 12:52:29 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=tozlLvKNHslStnxgpQe0y+wT8bUEPT47gVcDrqoru4w=; b=XbeRNPzLif1mw9MSJKzxoPN8DAYP4F1U7KyEw7MB35kr7FXwx3bdr10vfNA9OnON8k Iz5xHoN2vCUzIVzDSEISvBYzKNbIExRZ72Bj7e/IAznESYZCq7a364VyL/Y9zBJlqFsc T5cnXcr4rMG/aS+Dkfu+SYI5MaL7IcQwBrRuqdzY4vM+YyIEr5jFaFw6AMei0nmPh6Vo EyYt2NV4q7rRLZpUKvFhfqrMD954VbanKXUMB3OVWviIoWHVr3Lw2s5qBw44n30N3X4t odQklrEqHDtWMJKQHxVJOtLqN3abQlt28DbEgRbz6785wmxTSROMo/ZacMtf4eRdFUc5 ZqoQ== 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=tozlLvKNHslStnxgpQe0y+wT8bUEPT47gVcDrqoru4w=; b=RV+kFMRjEz9HxENA/yUxoz4++O8q0+V3muomccjNTtXATKlQCyzl70RDERM2jfeUJY RPCEWHzUBH1fm1Gw8FnKqUT0h/VVYcoTHoZhbsZcQNsN2gk3mYGuPwp3+keTbn4FyR7O 4Gk1OZhWVKuOFhXWyJZ4qok/OH97dX2vIs8nOx3u3Il+ZCKIXwXa13L3ukU3G8fQWC0J Ese8pSoJ/U4tIpMVHXiT1Ttc0Jczf36f+V40WhfJEc9FJSwE60Cn2z6CqxvqUTWSuHxu poqw2pMr7EdR92yb5fK1V6lglNxCmnKVlII9B9KXv8oXTBWHZWixo9WIgLTQRQnxSHxu oVoA== X-Gm-Message-State: AKwxytdcaOxaUmrL60sZT7yvwL+384WVyr3kdu85kFlAFgRKPeOAOAeb bEUBqNiJ1xsn//Ge9WZ2U0EBv2YP17nQ6sb67Ek= X-Google-Smtp-Source: AH8x225vUIgqfTxuowT7B3xC54fCwYpMZoZEzgqnvpfqxJFAfNTsgXAPE/rwRWDZXx94ymj/HRF90JFCvjLqBUY3Khg= X-Received: by 10.107.134.76 with SMTP id i73mr5605715iod.29.1516567948809; Sun, 21 Jan 2018 12:52:28 -0800 (PST) MIME-Version: 1.0 Received: by 10.2.69.12 with HTTP; Sun, 21 Jan 2018 12:52:28 -0800 (PST) In-Reply-To: <20180120011710.05B9C156E7E7@mail.bitblocks.com> References: <03c972a8f098b1b547da690efaad771f@schema31.it> <20180120011710.05B9C156E7E7@mail.bitblocks.com> From: krad Date: Sun, 21 Jan 2018 20:52:28 +0000 Message-ID: Subject: Re: Ancient FreeBSD update path To: Bakul Shah Cc: Andrea Brancatelli , 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: Sun, 21 Jan 2018 20:52:29 -0000 Back everything up. Forget about upgrading you are making your life harder. Do a ZFS install with BE's then port your apps. It will be quicker less prone to errors and you will end up with a better system in the end. If the system is a bit of a rats nest, then this would be the ideal time to document all its quirks, and tidy up. If it really is that hairy consider running the old applications in jails ontop of a new pristine OS build. If its on hardware consider new kit as well if its an important service, or consolidate it into a jail on something else. On 20 January 2018 at 01:16, Bakul Shah wrote: > On Fri, 19 Jan 2018 13:28:41 +0100 Andrea Brancatelli < > abrancatelli@schema31.it> wrote: > Andrea Brancatelli writes: > > Hello guys. > > > > I have a couple of ancient FreeBSD install that I have to bring into > > this century (read either 10.4 or 11.1) :-) > > > > I'm talking about a FreeBSD 8.0-RELEASE-p4 and a couple of FreeBSD > > 9.3-RELEASE-p53. > > > > What upgrade strategy would you suggest? > > > > Direct jump into the future (8 -> 11)? Progressive steps (8 -> 9 -> 10 > > -> 11)? Boiling water on the HDs? :-) > > > > Thanks, any suggestion in more than welcome. > > Incremental update will take a long time and if something gets > messed up in the middle, you will be much worse off. You may > also not find relevant packages any more for an EOLed release. > And you may have to solve problems that no longer exist on > newer packages. > > What I would do is to make a backup of everything, make a list > of installed packages and config files, and do a fresh install > of the latest release. Then get the critical packages working. > Then add others as needed. > > If possible do this on a separate machine so that you can > check config/program behavior on the original machine. When > you are satisfied, either switch to the other machine or copy > things back to the original. When one of my computers was > starting to fall apart, I did this with an inexpensive used > thinkpad. > > One more thing to consider: your ancient machine hardware may > need to be maintenance/repais/replacement. A fully > operational second (temporary) machine gives you a chance to > try to do maintenace such as remove dust and cat hair > carefully, check fans and replace them if needed, replace > disks if older than 4 years, etc. > _______________________________________________ > 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 Mon Jan 22 00:52:45 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 72827EC5293 for ; Mon, 22 Jan 2018 00:52: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 4524E83FB7 for ; Mon, 22 Jan 2018 00:52: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 w0M0r8YQ089475 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=FAIL); Mon, 22 Jan 2018 00:53:10 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 w0M0NREG048750 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 21 Jan 2018 16:52:37 -0800 (PST) (envelope-from truckman@FreeBSD.org) Date: Sun, 21 Jan 2018 16:52:36 -0800 (PST) From: Don Lewis Subject: Re: Ryzen issues on FreeBSD ? To: Peter Moody cc: Nimrod Levy , freebsd-stable@freebsd.org, Ryan Root In-Reply-To: Message-ID: References: <8e842dec-ade7-37d1-6bd8-856ea1a827ca@sentex.net> <3b625072-dfb3-6b4f-494d-7fe1b2fa554c@ingresso.co.uk> <2c6ce4dd-f43c-7c40-abc2-732d6f8996ec@sentex.net> <795dbb79-3c18-d967-98b9-5d09a740dbfe@sentex.net> <9b769e4e-b098-b294-0bce-8bb1c42e8a59@rootautomation.com> 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, 22 Jan 2018 00:52:45 -0000 On 21 Jan, Peter Moody wrote: > hm, so i've got nearly 3 days of uptime with smt disabled. > unfortunately this means that my otherwise '12' cores is actually only > '6'. I'm also getting occasional segfaults compiling go programs. Both my original and replacement CPUs croak on go, so I don't think an RMA is likely to help with that. Go is a heavy user of threads and my suspicion is that there is some sort of issue with the locking that is uses. I'm guessing a memory barrier issue of some sort ... From owner-freebsd-stable@freebsd.org Mon Jan 22 01:00:37 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B6EAAEC57F5 for ; Mon, 22 Jan 2018 01:00:37 +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 95093284 for ; Mon, 22 Jan 2018 01:00:37 +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 w0M10wth089512 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=FAIL); Mon, 22 Jan 2018 01:00:59 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 w0M0NREJ048750 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 21 Jan 2018 17:00:26 -0800 (PST) (envelope-from truckman@FreeBSD.org) Date: Sun, 21 Jan 2018 17:00:25 -0800 (PST) From: Don Lewis Subject: Re: Ryzen issues on FreeBSD ? To: Willem Jan Withagen cc: Pete French , freebsd-stable@freebsd.org In-Reply-To: <86eba4e4-f9a7-7177-a6bf-12700b1defa0@digiware.nl> Message-ID: References: <8e842dec-ade7-37d1-6bd8-856ea1a827ca@sentex.net> <8dcf6cc8fad788ac8168a4a9f392b02e@foolishgames.com> <23c1d162-dcd8-c422-3114-d70b65b6c271@sentex.net> <00875e4d-740f-63f1-496c-6cda82b1a403@ingresso.co.uk> <52744797-0606-44e7-72dd-242a6b56066a@digiware.nl> <86eba4e4-f9a7-7177-a6bf-12700b1defa0@digiware.nl> 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, 22 Jan 2018 01:00:37 -0000 On 21 Jan, Willem Jan Withagen wrote: > On 21/01/2018 21:24, Don Lewis wrote: >> On 21 Jan, Willem Jan Withagen wrote: >>> On 19/01/2018 23:29, Don Lewis wrote: >>>> On 19 Jan, Pete French wrote: >>>>> Out of interest, is there anyone out there running Ryzen who *hasnt* >>>>> seen lockups ? I'd be curious if there a lot of lurkers thinking "mine >>>>> works fine" >>>> >>>> No hangs or silent reboots here with either my original CPU or warranty >>>> replacement once the shared page fix was in place. >>> >>> Perhaps a too weird reference: >>> >>> I have supplied a customer with a Ryzen5 and a 350MB motherboard. >>> But he runs Windows 10, but I haven't heard him complain about anything >>> like this. >>> But I'll ask him specific. >> >> Only the BSDs were affected by the shared page issue. I think Linux >> already had a guard page. I don't think Windows was affected by the >> idle C-state issue. I suspect it is caused by software not doing the >> right thing during C-state transitions, but the publicly available >> documentation from AMD is pretty lacking. The random segfault issue is >> primarily triggered by heavy parallel software build loads and how many >> Windows users do that? > > This is an adobe workstation where several users remote login and do > work. So I would assume that the system is seriously (ab)used. > > Adn as expected I'm know aware of any of the detailed things that > Windows does while powering into lesser active states. It might depend on the scheduler details. On Linux and the FreeBSD ULE scheduler, runnable threads migrate between CPUs to balance the loading across all cores. When I did some experiments to disable that, the rate of build failures greatly decreased. AMD has been very vague about the cause of the problem (a "performance marginality") and resorted to replacing CPUs with this problem without suggesting any sort of software workaround. From owner-freebsd-stable@freebsd.org Mon Jan 22 01:02:52 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8E513EC5B17 for ; Mon, 22 Jan 2018 01:02:52 +0000 (UTC) (envelope-from marklmi26-fbsd@yahoo.com) Received: from sonic309-15.consmr.mail.bf2.yahoo.com (sonic309-15.consmr.mail.bf2.yahoo.com [74.6.129.125]) (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 56CE992F for ; Mon, 22 Jan 2018 01:02:51 +0000 (UTC) (envelope-from marklmi26-fbsd@yahoo.com) X-YMail-OSG: IRa.incVM1mkkWD.5c47acRgc45oUCuKy.VOZXTwDY0QZb8CyOSeI_9qX_beN_Z 5YIh9FiKjRP1AVrjEiYksQgg3fXZ.KgofHd3n7T568sy.lB4pCNItcA87fOm4k6OXRqFQlbtUkhv 6ouxiS54WkiEE6ocMs6KTdGjD5aI4dMpiCkKO4og4rmjHYm6mCiakG7u5ycix1FFIyYI3qbxtvGO nocU42YskqCp2gtujUdDh2hbl5p2WHN_z1Tjsrad3X50z0FvCFeORoOVI0sGYIXPcovXESPhz2aZ vaUI1n1S9G6KSGqOG9yMbjoGVV.YDo4caBtG_Ye54R0gbTbvGJU4OuWHpYCvlaUsAafTjtC6akpK i5tCSwdmg.V8RAVVzsvBKbPw7JpO8RGOFSixqkP8jUvvPcTlZe6RtE3pMYjACfwb2hccAVri1NKL zVHTehgArGFaJPw6duqd0aWVZprqaAJU8J2nVaf.ccjO0bWMal0OhUbBvRmT8q6Tl9oPX Received: from sonic.gate.mail.ne1.yahoo.com by sonic309.consmr.mail.bf2.yahoo.com with HTTP; Mon, 22 Jan 2018 01:02:44 +0000 Received: from smtpgate102.mail.bf1.yahoo.com (EHLO [192.168.1.25]) ([72.30.28.113]) by smtp416.mail.bf1.yahoo.com (JAMES SMTP Server ) with ESMTPA ID 5be0b94c2a6cd1b2e7b53d583f096639; Mon, 22 Jan 2018 01:02:43 +0000 (UTC) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 11.2 \(3445.5.20\)) Subject: Re: Ryzen issues on FreeBSD ? From: Mark Millard In-Reply-To: Date: Sun, 21 Jan 2018 17:02:41 -0800 Cc: FreeBSD-STABLE Mailing List Content-Transfer-Encoding: 7bit Message-Id: <7F3E20DB-9BAB-4FD7-A574-5F1635FB2B8D@yahoo.com> References: To: Don Lewis X-Mailer: Apple Mail (2.3445.5.20) 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, 22 Jan 2018 01:02:52 -0000 On 2018-Jan-21, at 12:17 PM, Don Lewis wrote: > On 20 Jan, Mark Millard wrote: >> Don Lewis truckman at FreeBSD.org wrote on >> Sat Jan 20 02:35:40 UTC 2018 : >> >>> The only real problem with the old CPUs is the random segfault problem >>> and some other random strangeness, like the lang/ghc build almost always >>> failing. >> >> >> At one time you had written >> ( https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221029 >> comment #103 on 2017-Oct-09): >> >> QUOTE >> The ghc build failure seems to be gone after upgrading the a >> more recent 12.0-CURRENT. I will try to bisect for the fix >> when I have a chance. >> END QUOTE >> >> Did that not pan out? Did you conclude it was >> hardware-context specific? > > I was never able to reproduce the problem. It seems like it failed on > the first ports build run after I replaced the CPU. When I upgraded the > OS and ports, the build succeeded. I tried going back to much earlier > OS and ports versions, but I could never get the ghc build to fail > again. I'm baffled by this ... Sounds like the overall information is then: Old CPU: frequent problem building ghc (nearly always fails as far as I know) New CPU: rare problem building ghc (possibly never for some softare version combinations?) (On a Ryzen Threadripper 1950X I've not seen a failure. For the above I'm including what I observed under Hyper-V for the 1800X and 1950X as contributing evidence: The 1800X was a early one and fit the "Old CPU" case above. AMD has stated that threadrippers never had the problems that other, early Ryzen CPUs did for heavy compiling use. So far, for me, that seems true.) So, it sounds like building ghc is still a good test. Back when I had access to the 1800X Ryzen system ghc was the most reliable failure-to-build of what I tried. It still may be useful for that sort of test activity to classify Ryzen CPUs for the one type of issue. === Mark Millard marklmi at yahoo.com ( markmi at dsl-only.net is going away in 2018-Feb, late) From owner-freebsd-stable@freebsd.org Mon Jan 22 09:17:54 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id AD2DFEB4F98 for ; Mon, 22 Jan 2018 09:17:54 +0000 (UTC) (envelope-from bennett@sdf.org) Received: from mx.sdf.org (mx.sdf.org [205.166.94.20]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "ol.sdf.org", Issuer "ol.sdf.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 9537F73346 for ; Mon, 22 Jan 2018 09:17:53 +0000 (UTC) (envelope-from bennett@sdf.org) Received: from sdf.org (IDENT:bennett@otaku.freeshell.org [205.166.94.9]) by mx.sdf.org (8.15.2/8.14.5) with ESMTPS id w0M9HnRr028788 (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256 bits) verified NO) for ; Mon, 22 Jan 2018 09:17:49 GMT Received: (from bennett@localhost) by sdf.org (8.15.2/8.12.8/Submit) id w0M9HnB5002106 for freebsd-stable@freebsd.org; Mon, 22 Jan 2018 03:17:49 -0600 (CST) From: Scott Bennett Message-Id: <201801220917.w0M9HnB5002106@sdf.org> Date: Mon, 22 Jan 2018 03:17:49 -0600 To: freebsd-stable@freebsd.org Subject: why does buildworld fail on stable/11 ? User-Agent: Heirloom mailx 12.5 6/20/10 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii 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: Mon, 22 Jan 2018 09:17:54 -0000 I tried asking for help on this several days ago on freebsd-questions@, but got no responses. I'm trying freebsd-stable@ next because it involves trying to build world on a 11.1-STABLE system from a freshly checked out, unaltered source tree at r328251. The system currently installed is from a 11.1-STABLE installer image: FreeBSD hellas 11.1-STABLE FreeBSD 11.1-STABLE #0 r326620: Wed Dec 6 15:08:03 UTC 2017 root@releng2.nyi.freebsd.org:/usr/obj/usr/src/sys/GENERIC amd64 I would like to keep it reasonably up to date, but I am stumped. I did a fresh svn checkout into a completely empty /usr/src, but when I tried to run a "make buildworld", it failed like this. Script started on Mon Jan 22 02:11:21 2018 hellas# setenv CCACHE_DIR /buildwork/ccache.freebsd hellas# cd /usr/src hellas# date && \ ? time nice +11 make buildworld && date Mon Jan 22 02:13:05 CST 2018 Unknown modifier 'U' Unknown modifier 'U' Unknown modifier 'U' Unknown modifier 'U' Unknown modifier 'U' Unknown modifier 'U' Unknown modifier 'U' Unknown modifier 'U' Unknown modifier 'U' Unknown modifier 'U' Unknown modifier 'U' Unknown modifier 'U' Unknown modifier 'U' Unknown modifier 'U' Unknown modifier 'U' Unknown modifier 'U' Unknown modifier 'U' Unknown modifier 'U' Unknown modifier 'U' Unknown modifier 'U' Unknown modifier 'U' Unknown modifier 'U' Unknown modifier 'U' Unknown modifier 'U' "/usr/src/share/mk/src.sys.mk", line 28: Option DIRDEPS_BUILD may only be defined in , environment, or make argument, not /etc/src.conf. *** Error code 1 Stop. make: stopped in /usr/src 0.035u 0.047s 0:01.65 4.2% 15254+422k 88+21io 31pf+0w hellas# exit exit Script done on Mon Jan 22 02:13:19 2018 Note that 'U' has not always been the letter complained of in the "Unknown modifier" messages. The content of /etc/src.conf is as follows. PORTS_MODULES=multimedia/cuse4bsd-kmod sysutils/pefs-kmod emulators/virtualbox-ose-kmod net/ndproxy WITH_LLDB=yes #WITH_FAST_DEPEND=yes WITH_CCACHE_BUILD=yes As you can see, there is no DIRDEPS_BUILD in /etc/src.conf. I don't even know what DIRDEPS_BUILD is. Anyway, I'm stuck. Can someone please tell me what is going wrong and how to fix it? I'd really like to be able to update my system, not only to keep it reasonably current, but also to be able to customize a kernel. Thanks in advance for any suggestions/solutions. Scott Bennett, Comm. ASMELG, CFIAG ********************************************************************** * Internet: bennett at sdf.org *xor* bennett at freeshell.org * *--------------------------------------------------------------------* * "A well regulated and disciplined militia, is at all times a good * * objection to the introduction of that bane of all free governments * * -- a standing army." * * -- Gov. John Hancock, New York Journal, 28 January 1790 * ********************************************************************** From owner-freebsd-stable@freebsd.org Mon Jan 22 11:48:19 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 69200EBC2D9 for ; Mon, 22 Jan 2018 11:48: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 3116D783AD for ; Mon, 22 Jan 2018 11:48:18 +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 1edaaF-000Je9-Eb for freebsd-stable@freebsd.org; Mon, 22 Jan 2018 11:48:15 +0000 Subject: Re: Ryzen issues on FreeBSD ? To: freebsd-stable@freebsd.org References: <8e842dec-ade7-37d1-6bd8-856ea1a827ca@sentex.net> <3b625072-dfb3-6b4f-494d-7fe1b2fa554c@ingresso.co.uk> <2c6ce4dd-f43c-7c40-abc2-732d6f8996ec@sentex.net> <795dbb79-3c18-d967-98b9-5d09a740dbfe@sentex.net> <9b769e4e-b098-b294-0bce-8bb1c42e8a59@rootautomation.com> From: Pete French Message-ID: <730eb882-1c6a-afb7-0ada-396db44fb34b@ingresso.co.uk> Date: Mon, 22 Jan 2018 11:48:15 +0000 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.5.2 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: Mon, 22 Jan 2018 11:48:19 -0000 On 21/01/2018 19:05, Peter Moody wrote: > hm, so i've got nearly 3 days of uptime with smt disabled. > unfortunately this means that my otherwise '12' cores is actually only > '6'. I'm also getting occasional segfaults compiling go programs. Isn't go known to have issues on BSD anyway though ? I have seen complaints of random crashes running go under BSD systems - and preseumably the go compiler itself is written in go, so those issues might surface when compiling. From owner-freebsd-stable@freebsd.org Mon Jan 22 12:43:02 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8CF7BEBF12A for ; Mon, 22 Jan 2018 12:43:02 +0000 (UTC) (envelope-from tech-lists@zyxst.net) Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) (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 5E3CE7A595 for ; Mon, 22 Jan 2018 12:43:01 +0000 (UTC) (envelope-from tech-lists@zyxst.net) Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id 9776F20853 for ; Mon, 22 Jan 2018 07:42:59 -0500 (EST) Received: from frontend2 ([10.202.2.161]) by compute4.internal (MEProxy); Mon, 22 Jan 2018 07:42:59 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=zyxst.net; h= content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=fm1; bh=vGarOgqOmPy5r8N7sdPa+yu8E3++y ygsq86WXipyOHY=; b=gdYy5/iPVBODstIT6r1XbaBB0tAt4phqtOW67evnt+z/n L8VkvWZEa/zYC+wd3vMw8Mgs3QrzMX5rm33T8Tf40MH34i343ikGss3SbKkJ058d jTqECzS0mmASE+vlKPNviUCVeu6IPncWjGJRznDNfN4iKsHdaDMjmBBRnvDOZdV6 hghZhr8oWmKetOgfN8DEfiRfBntqyMdu2oaGBBu5+H6GegnZ9vvwmI2wsZ4kbpdz u3CLnnztOfulZMpfH9BCFXPAlY3mpi+s6Yd26BjxeqcZJpkDF/NxrCRSwYae8Cpk p+qdjjMhfvJABoI/bK+3kny4PgAyXe3B1+OtoC1+Q== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=vGarOg qOmPy5r8N7sdPa+yu8E3++yygsq86WXipyOHY=; b=kRG+k+71N23JmX31g1jOo/ ssx35w42mKxO+lRMs+CIaUOLCvqJKrh16T1nu47INzt2CAJPtdWAs0cvznwduQTQ jbRZyLJNMBuP14KyMT56Z1vZJ//xUy2GNLKHp6LKEFsQLZ0rCCu71zAUxYKmaCPi 9Gi5v4UPjlpEfOYp7Zz5b8wJe1ML4sHK+cg/0PLeLaq2c4DynBzHgyVfAUTdKhMK W/cMLTXmjij5K3ObIu/EEzsIqWhqw0Dnu3r/B1MQu+TOTcJkMOWpxk2smYlsXZ/T zGYnsE92DbS16ZOBmTpnb/WKWsdFp2uwZ1k63qbKLJB8UMIedRLX6FjdbkeBQoqA == X-ME-Sender: Received: from desktop.parsley.growveg.org (parsley.growveg.org [82.70.91.97]) by mail.messagingengine.com (Postfix) with ESMTPA id 3205F246F4 for ; Mon, 22 Jan 2018 07:42:59 -0500 (EST) Subject: Re: why does buildworld fail on stable/11 ? To: freebsd-stable@freebsd.org References: <201801220917.w0M9HnB5002106@sdf.org> From: tech-lists Message-ID: <1440c3d4-ee8b-76a7-6727-d18641da7c2d@zyxst.net> Date: Mon, 22 Jan 2018 12:42:58 +0000 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.5.2 MIME-Version: 1.0 In-Reply-To: <201801220917.w0M9HnB5002106@sdf.org> Content-Type: text/plain; charset=utf-8 Content-Language: en-GB 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: Mon, 22 Jan 2018 12:43:02 -0000 On 22/01/2018 09:17, Scott Bennett wrote: > Anyway, I'm stuck. Can someone please tell me what is going wrong and > how to fix it? I'd really like to be able to update my system, not only to > keep it reasonably current, but also to be able to customize a kernel. Thanks > in advance for any suggestions/solutions. Hi, What I'd do is firstly to make things as simple as possible. First do the upgrade simply. Either delete or call make.conf & src.conf something else. Then get a fresh src and ports tree via svnlite. Then do rm -rf /buildwork/ccache.freebsd mkdir /buildwork/ccache.freebsd then [/usr/src #] make cleandir && make clean && make buildworld && make buildkernel && make installkernel && mergemaster -p [make changes if needed] [/usr/src #] make installworld && mergemaster [make more changes if needed] reboot then cd into /usr/src as root, then do yes | make delete-old yes | make delete-old-libs reboot again then re-enable your extra lines in make.conf and src.conf, if you need them. It may be down to something in the ccache dir, I guess. -- J. From owner-freebsd-stable@freebsd.org Mon Jan 22 17:07:53 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A5030ECAAD1 for ; Mon, 22 Jan 2018 17:07:53 +0000 (UTC) (envelope-from asomers@gmail.com) Received: from mail-lf0-x233.google.com (mail-lf0-x233.google.com [IPv6:2a00:1450:4010:c07::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 2852B84FC4 for ; Mon, 22 Jan 2018 17:07:53 +0000 (UTC) (envelope-from asomers@gmail.com) Received: by mail-lf0-x233.google.com with SMTP id t139so11496646lff.0 for ; Mon, 22 Jan 2018 09:07:53 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:sender:from:date:message-id:subject:to; bh=kqlyqTMDYc/aVrX1iI02jrMnJm8lHUSnmRnu3D9H94E=; b=hvzWJhvFIjkPRQbq8eX9WbGtqjnuxtm3nGCY1fYf1Fm/clNqp1nEapHzc1LDkfLhTA B1j+/TQEYEG0KyvJtcudt3OJV4A/RVXIABKS8O/kaqUY/d6lWvmk1BvF4Zl/dpdHDb9I ci/YK7ZxTBwDifaRXaoTjsAiFbK87hr48uKBNZZVFT2mXVzL9YdUyhwPnsyhu1ImW2+p UBOxemV8DFVc6D8ws3+frYyRWxSho3Q5+lvnCgY21BbvzU5/9kTwmYwEBy8/uQWcTCw6 nQQhVD2fF09QzW4xRdd96VWUqLSBkMj889PAj3IttBAHTLaV1PBNcfnC/HyqGHvBKDth 9Cdg== 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:from:date:message-id:subject :to; bh=kqlyqTMDYc/aVrX1iI02jrMnJm8lHUSnmRnu3D9H94E=; b=XBvqhfxvh0HmgDWg76t2cHocQsXzfqZqOy7QxVjvesf+oeQ5FFsyo4MtY48dyc4J+L JAFJ3KdHeylPOOgWC1ybVgCQP6kYP8D2LZ/lHgrxiaF7ta0TtMa3Wy799Pu348uBCXT2 u1v8gvDRrxr7fXXrzrG35NFQP11UOqF4OyXnssqSe7azvY1P9foLHfrmcx3CAp4GFFK+ 1qVJTcjHNh48XzFQHJ3VDdfUVMoxLOSdBWMtoqMtyMgPEMhCyX31V6PvSa+phFZkb+7g eCEK/fvdwq0u/NUAmSMf2bynR2NebM2khqCocy4TYBfpBrpjOnSROQHoV+61nmZMTFr8 fQbA== X-Gm-Message-State: AKwxyteCpEsicQGBU1YdNGQi+Y9KrcZwZVdXvXLFuR/6Pe9R1c8il+jN mY1oMlm72BXK31SUyvE0flUrxvTsykJYwbxugk08kA== X-Google-Smtp-Source: AH8x225tuaksWFHEJZcZUBKxhYbXY3fxbLa3N80Dfdhx7Uux7qyYbZZVRGvtDU0Vok6pw1WdL/xW7pjOIAsHVKNR3nE= X-Received: by 10.46.93.210 with SMTP id v79mr3799243lje.80.1516640870905; Mon, 22 Jan 2018 09:07:50 -0800 (PST) MIME-Version: 1.0 Sender: asomers@gmail.com Received: by 10.179.87.131 with HTTP; Mon, 22 Jan 2018 09:07:50 -0800 (PST) From: Alan Somers Date: Mon, 22 Jan 2018 10:07:50 -0700 X-Google-Sender-Auth: Hpp8TvwsfeSUZzpvasnqX3AKle8 Message-ID: Subject: Clock occasionally jumps backwards on 11.1-RELEASE To: FreeBSD 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: Mon, 22 Jan 2018 17:07:53 -0000 Since upgrading my jail server to 11.1-RELEASE, the clock occasionally jumps backwards by 5-35 minutes for no apparent reason. Has anybody seen something like this? Details ===== * Happens about once a day on my jail server, and has happened at least once on a separate bhyve server. * The jumps almost always happen between 1 and 3 AM, but I've also seen them happen at 06:30 and 20:15. * The jumps are always backwards, never forwards. * Inspecting the logs of both the host and its jails shows nothing interesting that's correlated with the jumps. Sometimes I find Amanda doing a backup, but not always. * Sometimes the jumps happen immediately after ntpd adds a new server to its list, but not always. * I'm using the default ntp.conf file. * ntpd is running on both, and it should be the only process touching the clock. I have a script running "ntpq -c peers" once a minute, which shows the offset for one server suddenly jump to a large negative number. Then the offsets for other servers jump to the same value, then either ntpd fixes the clock or exits because the offset is too high. * Said script is sleeping using the monotonic clock, not the realtime clock. As expected, successive timestamps differ by about 6.5 minutes when ntpd corrects a 5.5 minute clock offset. However, when the clock presumably jumps backwards I _don't_ see successive timestamps go backwards too. They keep marching forward at the expected rate. This makes me wonder if the entire machine is hanging. But it would have to be a pretty serious hang to stop the clock from ticking. Any ideas? From owner-freebsd-stable@freebsd.org Mon Jan 22 18:08:52 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B7521ECD3BC for ; Mon, 22 Jan 2018 18:08:52 +0000 (UTC) (envelope-from fusionfoto@gmail.com) Received: from mail-yb0-x229.google.com (mail-yb0-x229.google.com [IPv6:2607:f8b0:4002:c09::229]) (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 769AF2D79 for ; Mon, 22 Jan 2018 18:08:52 +0000 (UTC) (envelope-from fusionfoto@gmail.com) Received: by mail-yb0-x229.google.com with SMTP id i13so3571596ybl.9 for ; Mon, 22 Jan 2018 10:08:52 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=NFm7kplEL51xv6/fdxS+LcJcUDoc0+Qs3qnNVmAIigE=; b=Jwd4MyuH5XnrDBk70u1TgYpPZ07gKP/Rbful+yy2+bJOELmXysq391rDh2jGupbvb5 o1kdG/wmKPEdYMMqWcD89kGkGNxMIWHDEgeS6KfQP/OGJmE8YW4QyJZHBsUvHw6HWX9D pcr0/nFmHvtanwrOfdOzUnPvltrCQXVCzkrLZ6Ja6XJorlyNOwtvq8dnflc+IriJCRia pLdljfbO0l2DCcwrrXDVbO/Pg/I2EuTKcbNN68yw6F5m3lGkMsJoJDYx8aywoYA+PZ1x dVqa7WvovbGRFo95mMFjfwmlmACmOdoe12Oqe7aSOX9PbbHo6P0F6SZexmjZ8RGicevL Knkw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=NFm7kplEL51xv6/fdxS+LcJcUDoc0+Qs3qnNVmAIigE=; b=qs14dPIvpG1Bgusube2Mco+Wp/msT47pMNWXQy5/Mb48tMk+jrgM8aURNa8xdcWrl8 D5X3C2eNEQVMEaLusSdc2Y+sYuTAxdSC2XwhbaWW9tthJ5HioGEuKDio87hBg3mmPVoi dbApqFfZ+uH35lo9fKs2cKw1g0CmRTCu1mj7DP7p8eqM2x4tmNO3C9VdkoRvg1bv7kyf 2peuvKwdPaZgfdjCd5I+gBCVljKveczpXn7c2pY4h/n4jkylX3nJl9gIK/Moy85RUtsF Q5gHUaY3j8DTRgSWyR7weya8FrBulqGsh7ZrPPD2mcgT0cOADfsM8x2XStuDqfU/S3aj KosA== X-Gm-Message-State: AKwxyteUk+HHiRtgmS+vY3Isl4JZKq9LKqNs4z8YtykfQtu8Rcb05wDv In/AYnzi9IV8faseH4eJMId2EnxtrKWF8yfsV8M= X-Google-Smtp-Source: AH8x224CoY1oCMH5f68GaKkcw01Q2NjONqoKBxn0UK7ST4Ek3xOqGymDtcSYjflBJQo12sV+ALPhVJDIEAkWPhNtxMk= X-Received: by 10.37.189.5 with SMTP id f5mr7206257ybk.237.1516644531226; Mon, 22 Jan 2018 10:08:51 -0800 (PST) MIME-Version: 1.0 Received: by 10.37.175.20 with HTTP; Mon, 22 Jan 2018 10:08:50 -0800 (PST) From: FF Date: Mon, 22 Jan 2018 13:08:50 -0500 Message-ID: Subject: AHCI and Highpoint Rocket 750 To: freebsd-stable@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: Mon, 22 Jan 2018 18:08:52 -0000 I have a machine with the Highpoint card and motherboard based SATA drives. The drives from the MB support AHCI and appear as ada0-8. The drives on the highpoint card whether using native FreeBSD support or the Highpoint provided driver show up as da9-39. It is my understanding that AHCI is needed to support NCQ... I'm wondering what I need to do to get AHCI enabled. This seems to happen in both FreeBSD 9 and FreeBSD 10. thanks in advance! -- FF From owner-freebsd-stable@freebsd.org Mon Jan 22 18:25:39 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C6C10ECE01C for ; Mon, 22 Jan 2018 18:25:39 +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 9DC7D3BF9 for ; Mon, 22 Jan 2018 18:25:39 +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 w0MIQ3e0092005 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=FAIL); Mon, 22 Jan 2018 18:26:05 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 w0MIPUSm086645 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 22 Jan 2018 10:25:31 -0800 (PST) (envelope-from truckman@FreeBSD.org) Date: Mon, 22 Jan 2018 10:25:24 -0800 (PST) From: Don Lewis Subject: Re: Ryzen issues on FreeBSD ? To: Pete French cc: freebsd-stable@freebsd.org In-Reply-To: <730eb882-1c6a-afb7-0ada-396db44fb34b@ingresso.co.uk> Message-ID: References: <8e842dec-ade7-37d1-6bd8-856ea1a827ca@sentex.net> <3b625072-dfb3-6b4f-494d-7fe1b2fa554c@ingresso.co.uk> <2c6ce4dd-f43c-7c40-abc2-732d6f8996ec@sentex.net> <795dbb79-3c18-d967-98b9-5d09a740dbfe@sentex.net> <9b769e4e-b098-b294-0bce-8bb1c42e8a59@rootautomation.com> <730eb882-1c6a-afb7-0ada-396db44fb34b@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: Mon, 22 Jan 2018 18:25:39 -0000 On 22 Jan, Pete French wrote: > > > On 21/01/2018 19:05, Peter Moody wrote: >> hm, so i've got nearly 3 days of uptime with smt disabled. >> unfortunately this means that my otherwise '12' cores is actually only >> '6'. I'm also getting occasional segfaults compiling go programs. > > Isn't go known to have issues on BSD anyway though ? I have seen > complaints of random crashes running go under BSD systems - and > preseumably the go compiler itself is written in go, so those issues > might surface when compiling. Not that I'm aware of. I'm not a heavy go user on FreeBSD, but I don't recall any unexpected go crashes and I haven't seen problems building go on my older AMD machines. From owner-freebsd-stable@freebsd.org Mon Jan 22 18:26:59 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 72459ECE19C for ; Mon, 22 Jan 2018 18:26:59 +0000 (UTC) (envelope-from asomers@gmail.com) Received: from mail-lf0-x232.google.com (mail-lf0-x232.google.com [IPv6:2a00:1450:4010:c07::232]) (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 E9A623D89 for ; Mon, 22 Jan 2018 18:26:58 +0000 (UTC) (envelope-from asomers@gmail.com) Received: by mail-lf0-x232.google.com with SMTP id o89so11778440lfg.10 for ; Mon, 22 Jan 2018 10:26:58 -0800 (PST) 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=vgRGu5cC1DvA++BJyvxO29js/C7QcbbAVEwKutW0oks=; b=axvPfsPMIQ1p2sZIkf9kJwgvokB5M+oPPSzB1nriqyZ+2uDkiKqWwwig5mMU9X0v+6 6wtJPGKez8Je3kPAqGmhxpPNYYQ/LkXeshw2Uc0p2qvFwocaOYf4q0s+K7+pIkf3KF7p 7qFOsYZPzwqyo9/fhv8bpxK0mHIynJ04Czo5Jl0kRfX8T8BDywhMzVg6whrgffpe43uu 5My6oCsYVDbVmLFSz6NzW2M411MoKgaAtQKUyl73w9Xlrb4YN1ek3xxRKdEU9LLFjwcv ziTApCW2/upOV7fcjzm3ln93Yw3BoGCgqh6W8Y90T6PTBCuBOuL9BQi+V55Ys92mR7gB fRXg== 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=vgRGu5cC1DvA++BJyvxO29js/C7QcbbAVEwKutW0oks=; b=hBfzFIkUhOpdH+H8jKg47NciMKklTnDS3vYq8uYmpzD4wzbaLgjZhVbPKKxP8baSp7 9ockseEOT6W3DsHbrUv2NePXHi8xoGaGMfxb8rua63JMGmjRkKFX2hPayUs2TrqvQVKu Ui/v8ax2lAy7bxeIPwfpbCtT5B/2ipWbdyDqJHUr+damHFqOv9v/xlMqI2RYxueL4kb8 UbgXqzV5EHNOfOEJErB4vS2J6Y8GM6Wu6XzdakB/t3mrs6PXw45Ar0B/Tq84MosC/JOS ZhklzEtEJZ84fgcPbcdpfuZXHYQ9kCnviV2QhJeyFUH3PIO6W/unBzMkE2U1YfdaGSul 7hYg== X-Gm-Message-State: AKwxytduCQPStU8zoaLoq/0EE345wnfEssUy+qju6EZxaluJfGK6v5Ho To+jAyBgUYZEI8PVqkmv5zU+ww1CveeZ/oJ8upw= X-Google-Smtp-Source: AH8x224pCscYVme4DjU3geAhacoEGXtD7GDumcEMxZo7AGTOAY6gTEvauhniNc3Md1ucbTFsPCRWRc8RFKSFPv+EBes= X-Received: by 10.46.93.210 with SMTP id v79mr3915095lje.80.1516645616277; Mon, 22 Jan 2018 10:26:56 -0800 (PST) MIME-Version: 1.0 Sender: asomers@gmail.com Received: by 10.179.87.131 with HTTP; Mon, 22 Jan 2018 10:26:55 -0800 (PST) In-Reply-To: References: From: Alan Somers Date: Mon, 22 Jan 2018 11:26:55 -0700 X-Google-Sender-Auth: 1v3OvO-mvGqLfG0HMPfr1R9aP94 Message-ID: Subject: Re: AHCI and Highpoint Rocket 750 To: FF Cc: FreeBSD 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: Mon, 22 Jan 2018 18:26:59 -0000 On Mon, Jan 22, 2018 at 11:08 AM, FF wrote: > I have a machine with the Highpoint card and motherboard based SATA drives. > The drives from the MB support AHCI and appear as ada0-8. The drives on the > highpoint card whether using native FreeBSD support or the Highpoint > provided driver show up as da9-39. > > It is my understanding that AHCI is needed to support NCQ... I'm wondering > what I need to do to get AHCI enabled. This seems to happen in both FreeBSD > 9 and FreeBSD 10. > > thanks in advance! > AHCI has nothing to do with it. The driver presents itself to the OS as a SCSI HBA, even though the drives are SATA. In fact, it might actually be using a SCSI IC, but firmware-restricted to only connect to SATA drives. In any case, the OS is going to try to use TCQ, and either the driver or the firmware is going to translate those queued commands into NCQ. You don't need to change anything. -Alan From owner-freebsd-stable@freebsd.org Mon Jan 22 18:32:19 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8B167ECE5F7 for ; Mon, 22 Jan 2018 18:32:19 +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 3A7316352D; Mon, 22 Jan 2018 18:32:19 +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 w0MIWHiW035347 (version=TLSv1 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Mon, 22 Jan 2018 13:32:18 -0500 (EST) (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 w0MIWFNk056471; Mon, 22 Jan 2018 13:32:15 -0500 (EST) (envelope-from mike@sentex.net) Subject: Re: Ryzen issues on FreeBSD ? To: Don Lewis , Pete French Cc: freebsd-stable@freebsd.org References: <8e842dec-ade7-37d1-6bd8-856ea1a827ca@sentex.net> <3b625072-dfb3-6b4f-494d-7fe1b2fa554c@ingresso.co.uk> <2c6ce4dd-f43c-7c40-abc2-732d6f8996ec@sentex.net> <795dbb79-3c18-d967-98b9-5d09a740dbfe@sentex.net> <9b769e4e-b098-b294-0bce-8bb1c42e8a59@rootautomation.com> <730eb882-1c6a-afb7-0ada-396db44fb34b@ingresso.co.uk> From: Mike Tancsa Organization: Sentex Communications Message-ID: <8b882970-4d5d-2a96-4dac-779cab07b9ae@sentex.net> Date: Mon, 22 Jan 2018 13:32:16 -0500 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.5.2 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, 22 Jan 2018 18:32:19 -0000 On 1/22/2018 1:25 PM, Don Lewis wrote: > On 22 Jan, Pete French wrote: >> >> >> On 21/01/2018 19:05, Peter Moody wrote: >>> hm, so i've got nearly 3 days of uptime with smt disabled. >>> unfortunately this means that my otherwise '12' cores is actually only >>> '6'. I'm also getting occasional segfaults compiling go programs. >> >> Isn't go known to have issues on BSD anyway though ? I have seen >> complaints of random crashes running go under BSD systems - and >> preseumably the go compiler itself is written in go, so those issues >> might surface when compiling. > > Not that I'm aware of. I'm not a heavy go user on FreeBSD, but I don't > recall any unexpected go crashes and I haven't seen problems building > go on my older AMD machines. We use go quite a bit on one customer app and its quite stable. But thats a FreeBSD RELENG_10 box on an intel chip. ---Mike -- ------------------- Mike Tancsa, tel +1 519 651 3400 Sentex Communications, mike@sentex.net Providing Internet services since 1994 www.sentex.net Cambridge, Ontario Canada http://www.tancsa.com/ From owner-freebsd-stable@freebsd.org Mon Jan 22 18:42:01 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 114B8ECF1DC for ; Mon, 22 Jan 2018 18:42:01 +0000 (UTC) (envelope-from peter@hda3.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 CC7D768012 for ; Mon, 22 Jan 2018 18:42:00 +0000 (UTC) (envelope-from peter@hda3.com) Received: by mail-qt0-x244.google.com with SMTP id l20so22037066qtj.11 for ; Mon, 22 Jan 2018 10:42:00 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hda3-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=SIn8WSpdJcU/AlOR0cNScssHTvhvJi/NUCHSc/EPZl0=; b=KgLOAd+qXOogxaE3HNdkwWv1Ez+7BZHzpYvJCPbpBpY9f5tZqUgetmhJN3bmrIFzrF c566/OtphXS4HhO5ohSTKXg1qgETXUuawsLmvXime7ZqTTFx/wUdKuzbo7yR5TMDbh8f tvtRMbKOjzGr5fYUbKSia/VPfVlJhes1+3XeWZxqlTsTu8mN9j3RQ8vVhB2CLPrt2X0O EXsklbstkQNE4yn1kyCy/VmuXoA41z2uqX5zBEcuxau1VXfVmG0Rzih/6HJAt/bMvMuj XukUBGgVoJ2CIvqDqEN97T36dCqi1DsVnhM4QaKffuAB6BW2Fttxea0AJmrXC03ulh+Y M4kA== 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=SIn8WSpdJcU/AlOR0cNScssHTvhvJi/NUCHSc/EPZl0=; b=IB49BM+ChfchS2vjcMhTVMwXfjLBpJllc49eKP6ZOyJL1lfbpcp5bCHW1ShAdtnTrY uS6kKYV9krNwWCufW+oQt6J1CRIyuo2RDy71o0m4jBjte4WDDf1puDhFvvyCpWI/3rHZ PCZ+3+eIygad/PdJJrdg2YBpLcG/rSRZ2kVJNRMfc1RQXB89zOCJrWri9ANl7yvvm2sE BXD9Bvd6N1XE8hYBIq5mY8aPzl91yCpJtk27YP24pyEIVp7jW5gf5wSHM/VI9K/FbqwT HMQi5R80la0XN7Xi2j+4cXQTI7mNHaEezf7pKvu6E3diLtnc9l1smdapgZb7Tk693SWp 34tA== X-Gm-Message-State: AKwxytc8ZmIVvLaMVaUdvB+8vxjVXkOn3qhJlf5iXK8WmOY1IcOfQbsi XjOECeGxwrYocffEedCOockU9KHs6t2vZ8cyovHrXQ== X-Google-Smtp-Source: AH8x2249NhdlagUx+f3vw+QvWpClcHOY8kPYK08csK28kRTJMF0bRrfwkgv96Qe+Z/DBNfaO7XrzvKwOhUWytPU7kDE= X-Received: by 10.55.171.5 with SMTP id u5mr10532434qke.20.1516646519756; Mon, 22 Jan 2018 10:41:59 -0800 (PST) MIME-Version: 1.0 Received: by 10.140.39.83 with HTTP; Mon, 22 Jan 2018 10:41:39 -0800 (PST) In-Reply-To: <8b882970-4d5d-2a96-4dac-779cab07b9ae@sentex.net> References: <8e842dec-ade7-37d1-6bd8-856ea1a827ca@sentex.net> <3b625072-dfb3-6b4f-494d-7fe1b2fa554c@ingresso.co.uk> <2c6ce4dd-f43c-7c40-abc2-732d6f8996ec@sentex.net> <795dbb79-3c18-d967-98b9-5d09a740dbfe@sentex.net> <9b769e4e-b098-b294-0bce-8bb1c42e8a59@rootautomation.com> <730eb882-1c6a-afb7-0ada-396db44fb34b@ingresso.co.uk> <8b882970-4d5d-2a96-4dac-779cab07b9ae@sentex.net> From: Peter Moody Date: Mon, 22 Jan 2018 10:41:39 -0800 Message-ID: Subject: Re: Ryzen issues on FreeBSD ? To: Mike Tancsa Cc: Don Lewis , Pete French , freebsd-stable@freebsd.org Content-Type: text/plain; charset="UTF-8" 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, 22 Jan 2018 18:42:01 -0000 fwiw, I upgraded to 11-STABLE (11.1-STABLE #6 r328223), applied the hw.lower_amd64_sharedpage setting to my loader.conf and got a crash last night following the familiar high load -> idle. this was with SMT re-enabled. no crashdump, so it was the hard crash that I've been getting. all of the builds that had been failing before were fine; net/samba47, lang/ghc (though hadn't actually done this before to verify that it failed on my rig), so that's at least a plus. The only other out-of-the-ordinary thing I was doing at the time was that I'd started a zpool scrub. That succeeded fine the day before when SMT was disabled. shrug, I'm at a loss here. On Mon, Jan 22, 2018 at 10:32 AM, Mike Tancsa wrote: > On 1/22/2018 1:25 PM, Don Lewis wrote: >> On 22 Jan, Pete French wrote: >>> >>> >>> On 21/01/2018 19:05, Peter Moody wrote: >>>> hm, so i've got nearly 3 days of uptime with smt disabled. >>>> unfortunately this means that my otherwise '12' cores is actually only >>>> '6'. I'm also getting occasional segfaults compiling go programs. >>> >>> Isn't go known to have issues on BSD anyway though ? I have seen >>> complaints of random crashes running go under BSD systems - and >>> preseumably the go compiler itself is written in go, so those issues >>> might surface when compiling. >> >> Not that I'm aware of. I'm not a heavy go user on FreeBSD, but I don't >> recall any unexpected go crashes and I haven't seen problems building >> go on my older AMD machines. > > We use go quite a bit on one customer app and its quite stable. But > thats a FreeBSD RELENG_10 box on an intel chip. > > ---Mike > > > -- > ------------------- > Mike Tancsa, tel +1 519 651 3400 > Sentex Communications, mike@sentex.net > Providing Internet services since 1994 www.sentex.net > Cambridge, Ontario Canada http://www.tancsa.com/ > _______________________________________________ > 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 Mon Jan 22 18:50:53 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id DB8CBECFB2A for ; Mon, 22 Jan 2018 18:50:53 +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 98723687F2; Mon, 22 Jan 2018 18:50:53 +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 w0MIoq21038729 (version=TLSv1 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Mon, 22 Jan 2018 13:50:52 -0500 (EST) (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 w0MIootX056518; Mon, 22 Jan 2018 13:50:50 -0500 (EST) (envelope-from mike@sentex.net) Subject: Re: Ryzen issues on FreeBSD ? To: Peter Moody Cc: Don Lewis , Pete French , freebsd-stable@freebsd.org References: <8e842dec-ade7-37d1-6bd8-856ea1a827ca@sentex.net> <795dbb79-3c18-d967-98b9-5d09a740dbfe@sentex.net> <9b769e4e-b098-b294-0bce-8bb1c42e8a59@rootautomation.com> <730eb882-1c6a-afb7-0ada-396db44fb34b@ingresso.co.uk> <8b882970-4d5d-2a96-4dac-779cab07b9ae@sentex.net> From: Mike Tancsa Organization: Sentex Communications Message-ID: <343acf99-3e9e-093a-7390-c142396c2985@sentex.net> Date: Mon, 22 Jan 2018 13:50:50 -0500 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.5.2 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, 22 Jan 2018 18:50:54 -0000 On 1/22/2018 1:41 PM, Peter Moody wrote: > fwiw, I upgraded to 11-STABLE (11.1-STABLE #6 r328223), applied the > hw.lower_amd64_sharedpage setting to my loader.conf and got a crash > last night following the familiar high load -> idle. this was with SMT > re-enabled. no crashdump, so it was the hard crash that I've been > getting. hw.lower_amd64_sharedpage=1 is the default on AMD boxes no ? I didnt need to set mine to 1 > > shrug, I'm at a loss here. I am trying an RMA with AMD. ---Mike > > On Mon, Jan 22, 2018 at 10:32 AM, Mike Tancsa wrote: >> On 1/22/2018 1:25 PM, Don Lewis wrote: >>> On 22 Jan, Pete French wrote: >>>> >>>> >>>> On 21/01/2018 19:05, Peter Moody wrote: >>>>> hm, so i've got nearly 3 days of uptime with smt disabled. >>>>> unfortunately this means that my otherwise '12' cores is actually only >>>>> '6'. I'm also getting occasional segfaults compiling go programs. >>>> >>>> Isn't go known to have issues on BSD anyway though ? I have seen >>>> complaints of random crashes running go under BSD systems - and >>>> preseumably the go compiler itself is written in go, so those issues >>>> might surface when compiling. >>> >>> Not that I'm aware of. I'm not a heavy go user on FreeBSD, but I don't >>> recall any unexpected go crashes and I haven't seen problems building >>> go on my older AMD machines. >> >> We use go quite a bit on one customer app and its quite stable. But >> thats a FreeBSD RELENG_10 box on an intel chip. >> >> ---Mike >> >> >> -- >> ------------------- >> Mike Tancsa, tel +1 519 651 3400 >> Sentex Communications, mike@sentex.net >> Providing Internet services since 1994 www.sentex.net >> Cambridge, Ontario Canada http://www.tancsa.com/ >> _______________________________________________ >> 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" > > -- ------------------- Mike Tancsa, tel +1 519 651 3400 Sentex Communications, mike@sentex.net Providing Internet services since 1994 www.sentex.net Cambridge, Ontario Canada http://www.tancsa.com/ From owner-freebsd-stable@freebsd.org Mon Jan 22 19:05:55 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 34719ED06A1 for ; Mon, 22 Jan 2018 19:05:55 +0000 (UTC) (envelope-from fusionfoto@gmail.com) Received: from mail-yw0-x22e.google.com (mail-yw0-x22e.google.com [IPv6:2607:f8b0:4002:c05::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id E562669515; Mon, 22 Jan 2018 19:05:54 +0000 (UTC) (envelope-from fusionfoto@gmail.com) Received: by mail-yw0-x22e.google.com with SMTP id c78so3603273ywb.13; Mon, 22 Jan 2018 11:05:54 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=zw6b1z8C2Wfq95txdcwXecfiqkaO2Sagt9y//Eixzcw=; b=XKgBtoOTeQUjetB2ATrNRUPkMsEwbYjx/dYnO2rR5WfohLGEA6WIpRX/XhDzLB+g25 oY0gOO0IA32gbUUSa40KduV0JC5rypcWVrKDNUJ/0yPd4ShBYX0YFUbFbi2APEUhx07F prrD4LGFlKEPotuZw6EiN8TYz+bRZZkcBCA9P3QcWp3YTo3Ub6zhwHKyaUG250ZyXtyp ejLHK6n62yJdhUBRpoRqjlI2T3NvN4bZCfKWH/MUaWWYmgyv9jyQP1Q3/aJ6wo7mBFTy nZbOTlQ7kiEQn/pnGznwnwfjAjDEOoa3geT8fMXRB04Ce38lWS954adb8hoKv7jNMkvP xzAA== 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=zw6b1z8C2Wfq95txdcwXecfiqkaO2Sagt9y//Eixzcw=; b=M6J5fqFSXlIw57YopdJPjlAlc7j6NF2fmCifvwut7A5hpyaWmdUW/2PpVAjkUwCHm+ Ihjc5d0fba1UwWAajpIeZpNMgOhfgm8oWBDAdYKm9VJVGd8hVISP3U6l8/uMOvyXRdjd dJ2m0O3U5CmZW1XotmB5JpHQXDiEPLxHG9Xou497wPSYqa1UoB5SQLucjbOvR6bBxKOG JKw2cIm/GbPiHtCDFPSvKOdMaqlMu7dPr21vUK96DX2QP/hTBWuKPWJjMCRgPL/FF1qd 6OC7WYmqjfFRs/4uCdM/ebtTcx+85G7cudXrD19TobXNxkMJkhp8wx/U6DGyXPz3GrxN oucg== X-Gm-Message-State: AKwxyteXI+10bRwC0tprp04P3o27W1ZsvX57/x5ah5VnCXERAtzgWD36 cgIGsCouwaeO2IYAQLuFxY5loL02uXK9fu13cZ8= X-Google-Smtp-Source: AH8x224vxOGgbBd4T6xHAY2jZIRkOskXxXaSnqU5K+LBewfF1XgMtOnV9AOfKutTKZgCgL+4SUx2q+ImM+jstyPndks= X-Received: by 10.129.70.193 with SMTP id t184mr8366114ywa.246.1516647953734; Mon, 22 Jan 2018 11:05:53 -0800 (PST) MIME-Version: 1.0 Received: by 10.37.175.20 with HTTP; Mon, 22 Jan 2018 11:05:53 -0800 (PST) In-Reply-To: References: From: FF Date: Mon, 22 Jan 2018 14:05:53 -0500 Message-ID: Subject: Re: AHCI and Highpoint Rocket 750 To: Alan Somers Cc: FreeBSD 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: Mon, 22 Jan 2018 19:05:55 -0000 oh nice! so it "just works" -- is there any way to verify it? Is there any reason to use the highpoint driver when the native FreeBSD one seems to work? thanks!! On Mon, Jan 22, 2018 at 1:26 PM, Alan Somers wrote: > On Mon, Jan 22, 2018 at 11:08 AM, FF wrote: > >> I have a machine with the Highpoint card and motherboard based SATA >> drives. >> The drives from the MB support AHCI and appear as ada0-8. The drives on >> the >> highpoint card whether using native FreeBSD support or the Highpoint >> provided driver show up as da9-39. >> >> It is my understanding that AHCI is needed to support NCQ... I'm wondering >> what I need to do to get AHCI enabled. This seems to happen in both >> FreeBSD >> 9 and FreeBSD 10. >> >> thanks in advance! >> > > AHCI has nothing to do with it. The driver presents itself to the OS as a > SCSI HBA, even though the drives are SATA. In fact, it might actually be > using a SCSI IC, but firmware-restricted to only connect to SATA drives. > In any case, the OS is going to try to use TCQ, and either the driver or > the firmware is going to translate those queued commands into NCQ. You > don't need to change anything. > > -Alan > > -- FF From owner-freebsd-stable@freebsd.org Mon Jan 22 19:48:49 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 71835ED22F0 for ; Mon, 22 Jan 2018 19:48:49 +0000 (UTC) (envelope-from asomers@gmail.com) Received: from mail-lf0-x22e.google.com (mail-lf0-x22e.google.com [IPv6:2a00:1450:4010:c07::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id E7AEF6B3F0 for ; Mon, 22 Jan 2018 19:48:48 +0000 (UTC) (envelope-from asomers@gmail.com) Received: by mail-lf0-x22e.google.com with SMTP id g72so12104577lfg.5 for ; Mon, 22 Jan 2018 11:48:48 -0800 (PST) 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=yXAAwGATUZ0DyDThWHqn8yp2TJAO6184+tY+/PwEJZY=; b=Mrox6G9lBrDNRFJHEisxW5dUgzFB0HyvRCK5imiM2ZTqo+y4YS0UyXm74kyHcqlvV+ TMAlHEo4FmfT/+rthPuCbII4RSRrS9hpoQZvzYClRvc3nRVAW9F2yZfZC1/nlzOSDbkm p/cifEyu4Cb4HyGWG/NcLIcDUy7cPzxCO2KdHVBB/UD9vJ2+KTIjjqCzH/morgo7mFgl K3niGZhQLSmavtQaR4w8qMMAHYLl+X4N+IWUAS6jo6qiBdbP/KWuZ7Y+HsV9FP7NzEin 3fPGgpZr6x12ZNC3P8i/bvBeBqxHlGTb0axVmpbuJQY4k0ZrIFkuuq9i9IPQ73TTOPF2 nqpQ== 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=yXAAwGATUZ0DyDThWHqn8yp2TJAO6184+tY+/PwEJZY=; b=ETC80Cg3xcYxGAxJDOf9ea4VL56V4t6yFvOHSTTLgpOqRyQplgsZ8iz7ktS6E/2X4e sj2EUFObuEkR50MxcxDDigCivQtqrBmDiNZxQuwC7YY7mxqC6oyn6pDxRkcRxZIXtXUX SGx5h5nORWj7spl4npBIlvbeN7tt9NyHM7IYp6+ISelo6I3gaBOXdM/A+oQUhPyoYxs4 49zY7JWEG1laKPcq6SwBBBiwySYQZnUb9jjQrrrPNAj2RJnIaUJu4/zvVfZm02abZG+9 i11YNjQbfrlAYG1N/YgHP16H8TPs9F/ij9vcB6IUPPC91CBxMQWhspfD7vckWPdtCQjs 5t0A== X-Gm-Message-State: AKwxytfC1nA7ZPyMPXysmeVrk83ESlf8XV1IP3pRPq/tSPlK8z2z3Oel W9TiEYeO1wSGv3F7zz2scEm3dg55n/ZUbH4CVhc= X-Google-Smtp-Source: AH8x225y7hDMP6iHXD1YvH2S/z/HjkchKNO18KydqJh5s91sCbPlXEAMe8mBgNAgdpcgexKpnnJF9kZS+v0lqf65kWc= X-Received: by 10.25.178.217 with SMTP id t86mr4076238lfk.51.1516650526449; Mon, 22 Jan 2018 11:48:46 -0800 (PST) MIME-Version: 1.0 Sender: asomers@gmail.com Received: by 10.179.87.131 with HTTP; Mon, 22 Jan 2018 11:48:45 -0800 (PST) In-Reply-To: References: From: Alan Somers Date: Mon, 22 Jan 2018 12:48:45 -0700 X-Google-Sender-Auth: 3n-Jx79bC_WzEMaKVEc47RcCjg0 Message-ID: Subject: Re: AHCI and Highpoint Rocket 750 To: FF Cc: FreeBSD 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: Mon, 22 Jan 2018 19:48:49 -0000 On Mon, Jan 22, 2018 at 12:05 PM, FF wrote: > oh nice! so it "just works" -- is there any way to verify it? > Not easily. You could try putting a load on those disks, then use "gstat -a" to watch the queue depth (the "L(q)" column). If it's >1, that means that geom is trying to use queued commands. A more accurate but more difficult method would be to use a benchmark program like benchmarks/fio to do a random write test on a single disk. If the throughput is higher when fio is using a queue depth > 1, then that would indicate that queued commands are making it all the way to the drive. OTOH, it would probably be a better use of your time just to benchmark whatever application you're using. Only if that's too slow should you dig into minutiae like this. With 40 drives, you may have plenty of IOPs even without NCQ. > > Is there any reason to use the highpoint driver when the native FreeBSD > one seems to work? > Nope. > > thanks!! > > On Mon, Jan 22, 2018 at 1:26 PM, Alan Somers wrote: > >> On Mon, Jan 22, 2018 at 11:08 AM, FF wrote: >> >>> I have a machine with the Highpoint card and motherboard based SATA >>> drives. >>> The drives from the MB support AHCI and appear as ada0-8. The drives on >>> the >>> highpoint card whether using native FreeBSD support or the Highpoint >>> provided driver show up as da9-39. >>> >>> It is my understanding that AHCI is needed to support NCQ... I'm >>> wondering >>> what I need to do to get AHCI enabled. This seems to happen in both >>> FreeBSD >>> 9 and FreeBSD 10. >>> >>> thanks in advance! >>> >> >> AHCI has nothing to do with it. The driver presents itself to the OS as >> a SCSI HBA, even though the drives are SATA. In fact, it might actually be >> using a SCSI IC, but firmware-restricted to only connect to SATA drives. >> In any case, the OS is going to try to use TCQ, and either the driver or >> the firmware is going to translate those queued commands into NCQ. You >> don't need to change anything. >> >> -Alan >> >> > > > -- > FF > From owner-freebsd-stable@freebsd.org Mon Jan 22 20:57:34 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1AC82ED53C5 for ; Mon, 22 Jan 2018 20:57:34 +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 BFB8F6E639; Mon, 22 Jan 2018 20:57:33 +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 w0MKvWpS063772 (version=TLSv1 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Mon, 22 Jan 2018 15:57:32 -0500 (EST) (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 w0MKvUea058244; Mon, 22 Jan 2018 15:57:30 -0500 (EST) (envelope-from mike@sentex.net) Subject: Re: Ryzen issues on FreeBSD ? To: Don Lewis Cc: freebsd-stable@freebsd.org, Pete French References: <8e842dec-ade7-37d1-6bd8-856ea1a827ca@sentex.net> <8dcf6cc8fad788ac8168a4a9f392b02e@foolishgames.com> <23c1d162-dcd8-c422-3114-d70b65b6c271@sentex.net> <00875e4d-740f-63f1-496c-6cda82b1a403@ingresso.co.uk> <52744797-0606-44e7-72dd-242a6b56066a@digiware.nl> From: Mike Tancsa Organization: Sentex Communications Message-ID: <4e53080c-4257-d3b6-a097-0d54602e0e62@sentex.net> Date: Mon, 22 Jan 2018 15:57:30 -0500 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.5.2 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, 22 Jan 2018 20:57:34 -0000 On 1/21/2018 3:24 PM, Don Lewis wrote: >> >> I have supplied a customer with a Ryzen5 and a 350MB motherboard. >> But he runs Windows 10, but I haven't heard him complain about anything >> like this. >> But I'll ask him specific. > > Only the BSDs were affected by the shared page issue. I think Linux > already had a guard page. I don't think Windows was affected by the > idle C-state issue. I suspect it is caused by software not doing the > right thing during C-state transitions, but the publicly available > documentation from AMD is pretty lacking. The random segfault issue is > primarily triggered by heavy parallel software build loads and how many > Windows users do that? Are all the AMD accomodations that DragonFly did in FreeBSD ? http://lists.dragonflybsd.org/pipermail/commits/2017-August/626190.html ---Mike -- ------------------- Mike Tancsa, tel +1 519 651 3400 Sentex Communications, mike@sentex.net Providing Internet services since 1994 www.sentex.net Cambridge, Ontario Canada http://www.tancsa.com/ From owner-freebsd-stable@freebsd.org Mon Jan 22 21:07:44 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 73366ED5D81 for ; Mon, 22 Jan 2018 21:07:44 +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 5109D6EE9C for ; Mon, 22 Jan 2018 21:07:44 +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 w0ML88RR092335 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=FAIL); Mon, 22 Jan 2018 21:08:10 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 w0ML7ZQu092390 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 22 Jan 2018 13:07:36 -0800 (PST) (envelope-from truckman@FreeBSD.org) Date: Mon, 22 Jan 2018 13:07:30 -0800 (PST) From: Don Lewis Subject: Re: Ryzen issues on FreeBSD ? To: Mike Tancsa cc: freebsd-stable@freebsd.org, Pete French In-Reply-To: <4e53080c-4257-d3b6-a097-0d54602e0e62@sentex.net> Message-ID: References: <8e842dec-ade7-37d1-6bd8-856ea1a827ca@sentex.net> <8dcf6cc8fad788ac8168a4a9f392b02e@foolishgames.com> <23c1d162-dcd8-c422-3114-d70b65b6c271@sentex.net> <00875e4d-740f-63f1-496c-6cda82b1a403@ingresso.co.uk> <52744797-0606-44e7-72dd-242a6b56066a@digiware.nl> <4e53080c-4257-d3b6-a097-0d54602e0e62@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, 22 Jan 2018 21:07:44 -0000 On 22 Jan, Mike Tancsa wrote: > On 1/21/2018 3:24 PM, Don Lewis wrote: >>> >>> I have supplied a customer with a Ryzen5 and a 350MB motherboard. >>> But he runs Windows 10, but I haven't heard him complain about anything >>> like this. >>> But I'll ask him specific. >> >> Only the BSDs were affected by the shared page issue. I think Linux >> already had a guard page. I don't think Windows was affected by the >> idle C-state issue. I suspect it is caused by software not doing the >> right thing during C-state transitions, but the publicly available >> documentation from AMD is pretty lacking. The random segfault issue is >> primarily triggered by heavy parallel software build loads and how many >> Windows users do that? > > > Are all the AMD accomodations that DragonFly did in FreeBSD ? > > http://lists.dragonflybsd.org/pipermail/commits/2017-August/626190.html We only lowered the top of user space by 4KB, which should be sufficient, and we unmapped the boundary page. The signal trampoline was already in a separate page than the stack. From owner-freebsd-stable@freebsd.org Mon Jan 22 22:13:22 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 875ADED88C0 for ; Mon, 22 Jan 2018 22:13:22 +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 5E9BC71A14 for ; Mon, 22 Jan 2018 22:13:22 +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 w0MMDkrG092473 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=FAIL); Mon, 22 Jan 2018 22:13:47 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 w0ML7ZQx092390 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 22 Jan 2018 14:13:13 -0800 (PST) (envelope-from truckman@FreeBSD.org) Date: Mon, 22 Jan 2018 14:13:13 -0800 (PST) From: Don Lewis Subject: Re: Ryzen issues on FreeBSD ? To: Mike Tancsa cc: Peter Moody , Pete French , freebsd-stable@freebsd.org In-Reply-To: <343acf99-3e9e-093a-7390-c142396c2985@sentex.net> Message-ID: References: <8e842dec-ade7-37d1-6bd8-856ea1a827ca@sentex.net> <795dbb79-3c18-d967-98b9-5d09a740dbfe@sentex.net> <9b769e4e-b098-b294-0bce-8bb1c42e8a59@rootautomation.com> <730eb882-1c6a-afb7-0ada-396db44fb34b@ingresso.co.uk> <8b882970-4d5d-2a96-4dac-779cab07b9ae@sentex.net> <343acf99-3e9e-093a-7390-c142396c2985@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, 22 Jan 2018 22:13:22 -0000 On 22 Jan, Mike Tancsa wrote: > On 1/22/2018 1:41 PM, Peter Moody wrote: >> fwiw, I upgraded to 11-STABLE (11.1-STABLE #6 r328223), applied the >> hw.lower_amd64_sharedpage setting to my loader.conf and got a crash >> last night following the familiar high load -> idle. this was with SMT >> re-enabled. no crashdump, so it was the hard crash that I've been >> getting. > > hw.lower_amd64_sharedpage=1 is the default on AMD boxes no ? I didnt > need to set mine to 1 > >> >> shrug, I'm at a loss here. > > I am trying an RMA with AMD. Something else that you might want to try is 12.0-CURRENT. There might be some changes in HEAD that need to be merged back to 11.1-STABLE. From owner-freebsd-stable@freebsd.org Tue Jan 23 10:16:52 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 281C8EC89AA for ; Tue, 23 Jan 2018 10:16:52 +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 C016772CF2; Tue, 23 Jan 2018 10:16:51 +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 1edvdD-00088M-Gj; Tue, 23 Jan 2018 10:16:43 +0000 Subject: Re: Ryzen issues on FreeBSD ? To: Don Lewis Cc: freebsd-stable@freebsd.org References: <8e842dec-ade7-37d1-6bd8-856ea1a827ca@sentex.net> <3b625072-dfb3-6b4f-494d-7fe1b2fa554c@ingresso.co.uk> <2c6ce4dd-f43c-7c40-abc2-732d6f8996ec@sentex.net> <795dbb79-3c18-d967-98b9-5d09a740dbfe@sentex.net> <9b769e4e-b098-b294-0bce-8bb1c42e8a59@rootautomation.com> <730eb882-1c6a-afb7-0ada-396db44fb34b@ingresso.co.uk> From: Pete French Message-ID: Date: Tue, 23 Jan 2018 10:17:06 +0000 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:52.0) Gecko/20100101 Thunderbird/52.5.2 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: Tue, 23 Jan 2018 10:16:52 -0000 On 22/01/2018 18:25, Don Lewis wrote: > On 22 Jan, Pete French wrote: >> >> >> On 21/01/2018 19:05, Peter Moody wrote: >>> hm, so i've got nearly 3 days of uptime with smt disabled. >>> unfortunately this means that my otherwise '12' cores is actually only >>> '6'. I'm also getting occasional segfaults compiling go programs. >> >> Isn't go known to have issues on BSD anyway though ? I have seen >> complaints of random crashes running go under BSD systems - and >> preseumably the go compiler itself is written in go, so those issues >> might surface when compiling. > > Not that I'm aware of. I'm not a heavy go user on FreeBSD, but I don't > recall any unexpected go crashes and I haven't seen problems building > go on my older AMD machines. From the go 1.9 release notes: "Known Issues There are some instabilities on FreeBSD that are known but not understood. These can lead to program crashes in rare cases. See issue 15658. Any help in solving this FreeBSD-specific issue would be appreciated." ( link is to https://github.com/golang/go/issues/15658 ) Having said that, we use it internally and have not seen any issues with it ourselves. Just I am wary of the release notes, and that issue report. From owner-freebsd-stable@freebsd.org Tue Jan 23 10:48:38 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9FF7DECA856 for ; Tue, 23 Jan 2018 10:48:38 +0000 (UTC) (envelope-from michaelp@bsquare.com) Received: from NAM01-SN1-obe.outbound.protection.outlook.com (mail-sn1nam01on0130.outbound.protection.outlook.com [104.47.32.130]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (Client CN "mail.protection.outlook.com", Issuer "Microsoft IT TLS CA 4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 574AF745E7 for ; Tue, 23 Jan 2018 10:48:37 +0000 (UTC) (envelope-from michaelp@bsquare.com) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=BsquareO365.onmicrosoft.com; s=selector1-bsquare-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=s30Uvt54rksNRjgs14t4fTej8vM7z1QcOGt3aetzM3E=; b=UBBbgV7h+lFoVUGm7f4p05DB4Ajlr58ox26M2bruNI3i3Wr1SZhi5k8qJf3hBkeW7MDMblqjO/D2Xm3oyWrr1zl8W8gptf/CSaWncxxoi27QJyrGowQIURsPRX33hI1wNywsSKZYtEHrcMCTueIvVB59zfRrOFx868HYb6mmjiQ= Authentication-Results: spf=none (sender IP is ) smtp.mailfrom=michaelp@bsquare.com; Received: from [10.150.16.65] (82.33.218.74) by CY4PR1301MB2023.namprd13.prod.outlook.com (10.171.223.157) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.444.5; Tue, 23 Jan 2018 10:48:35 +0000 Subject: Re: Clock occasionally jumps backwards on 11.1-RELEASE To: freebsd-stable@freebsd.org References: From: Mike Pumford Message-ID: <0b170dae-b816-ea49-3516-40bfd1deaa2a@bsquare.com> Date: Tue, 23 Jan 2018 10:48:29 +0000 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.5.2 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-Originating-IP: [82.33.218.74] X-ClientProxiedBy: DB6P193CA0017.EURP193.PROD.OUTLOOK.COM (10.175.237.27) To CY4PR1301MB2023.namprd13.prod.outlook.com (10.171.223.157) X-MS-PublicTrafficType: Email X-MS-Office365-Filtering-Correlation-Id: 1f73334a-c6ab-422b-9ac0-08d5624edade X-Microsoft-Antispam: UriScan:; BCL:0; PCL:0; RULEID:(7020095)(4652020)(7021125)(4534165)(7022125)(4603075)(4627221)(201702281549075)(7048125)(7024125)(7027125)(7028125)(7023125)(5600026)(4604075)(2017052603307)(7153060)(7193020); SRVR:CY4PR1301MB2023; X-Microsoft-Exchange-Diagnostics: 1; CY4PR1301MB2023; 3:Pe2OHEYu3cbWTwtjaaVbLkiyvYYjeqCAibHt65oE2V0zQDKygT/GthAZm2okoLCFw+Og1AlNjPosXnoXpFhRTrnJCwBSOBz2LPf7TqptH3/It7nmfH++tCXjxLP3csHtE5vPXsuXT6NiTDSbBXbGyA0JjQJiHUhC0/TAFUb2hihxqswN8JCcfOpbtexe4xtnFW1a+d4vANgZw/Re14UWOkxnHpcrz8MA3YZNvDRi4lK9bz8Sed+TjV1ZmWT/b7tC; 25:6SbfBaNztPmfFZyDc5qftd3NSzNy/wH2r9WFZLyH7NbK/j4VS1/LJHav6Wv2fY4hmcs6u3u8WhGtt7l+3CI1iVX9Ht/och7fYHqDknANhwXEq5foEQDVQApaHCFM9cUhIX+NWHmNf5KYfyR1mAPlbbaMJhQVGFwBVq1H+tN+1qwgknI6+NJpSW8qQ7podjIgN5tERwUImoqiMYFcoHRQDxf4jtA20SAx32wPgQvF9wJ9jSwQN93xahf/9Z5SQFtFO36WmSvAZInXZCrY2sQdJ5m5pSg/cL6FAtRw3x089SIYjRsPUfBWyNXQyKA6QwSZ0ePjXZs5mSEUakIoKr4ZuQ==; 31:u4x6NY1HhvnMqUvMDBCcSYo/kE7hTla8i9pMgUAcmHloz+FdwjYR3J1vNi8Yz2kBBAU4W5V4dtzDPQmi+NeU6bsriCmZ6Ze3YsKsTlbrO2ewJj+ersg1U4B0SyknkYxs/v+k5D9pbkPV6O7spp5wlhvzjlKg9SSNwwWuzjQsVtP3MpPypUSoAeANh0p+57DGAd/wWhwKc6E7NqUtIWw757Daydmu1Wa1PB1S2NSgSCk= X-MS-TrafficTypeDiagnostic: CY4PR1301MB2023: X-Microsoft-Antispam-PRVS: X-Exchange-Antispam-Report-Test: UriScan:(158342451672863)(17755550239193); X-Exchange-Antispam-Report-CFA-Test: BCL:0; PCL:0; RULEID:(6040501)(2401047)(8121501046)(5005006)(10201501046)(3002001)(93006095)(93001095)(3231023)(2400081)(944501161)(6041288)(2016111802025)(20161123560045)(20161123558120)(20161123564045)(20161123562045)(6043046)(6072148)(201708071742011); SRVR:CY4PR1301MB2023; BCL:0; PCL:0; RULEID:(100000803101)(100110400095); SRVR:CY4PR1301MB2023; X-Microsoft-Exchange-Diagnostics: 1; CY4PR1301MB2023; 4:u0OAFHzIDEM1YVpOzDDRCGZUVpTdtRgvZ6+Pt1K8cvjHyvFtm+RCYpKzijkUrWYg2O575bEFovYt3I+iRBBwRhZCiYKJWbKOvdjT42x/vXVnLTtlls4XNmAYqLJXkXA+z9JTFXz4AU+k3GrXTSC3iwJYH19HhNp7uyLkTvT5MgKtQhmmSVkLNd1jRokXyYTFbOH9MkanW0uNkVTZx+nYxIXPgW1a7g3/U0FKxNTYDL0IAIsgrwQtXiTZ6mAryAzEALm4OWc78NKm4CAihQtrT8Ob9wwNczHjSATd6DF5ly2iO6TQ7tPt2wQGGT2iDPP3n6BhdFxPIWmoZhW3PkZgR9XQZ7G4mWM21YFS+hZf7qM= X-Forefront-PRVS: 05610E64EE X-Forefront-Antispam-Report: SFV:NSPM; SFS:(10019020)(6049001)(39380400002)(396003)(39840400004)(376002)(366004)(346002)(199004)(189003)(2906002)(2950100002)(6916009)(25786009)(81156014)(81166006)(3260700006)(8676002)(15974865002)(16526018)(386003)(229853002)(68736007)(8936002)(7736002)(83506002)(53936002)(5660300001)(305945005)(90366009)(6246003)(6486002)(66066001)(6306002)(53546011)(65806001)(76176011)(6116002)(65956001)(230700001)(3846002)(2361001)(105586002)(2351001)(64126003)(50466002)(26005)(77096007)(23676004)(2486003)(52116002)(52146003)(106356001)(65826007)(31686004)(97736004)(67846002)(31696002)(6666003)(478600001)(59450400001)(58126008)(86362001)(36756003)(47776003)(316002)(16576012)(42262002); DIR:OUT; SFP:1102; SCL:1; SRVR:CY4PR1301MB2023; H:[10.150.16.65]; FPR:; SPF:None; PTR:InfoNoRecords; A:1; MX:1; LANG:en; Received-SPF: None (protection.outlook.com: bsquare.com does not designate permitted sender hosts) X-Microsoft-Exchange-Diagnostics: =?utf-8?B?MTtDWTRQUjEzMDFNQjIwMjM7MjM6WGMwS2NzNG9WaVR0aDhuenBnL3BPdDFx?= =?utf-8?B?YzZOUVlzK1VlWnB0RWFtRlZSdld3Y3NKd0E1Wm9DNjhjeWJzUFBPMmUzKy9H?= =?utf-8?B?cTNUanlSeEVYbWNzQ3pLY3NNZml5T0VjbHN1MU9PTGhtai8zSHljdyt1aEwx?= =?utf-8?B?ZExodStRMG5jQXJxUThiME9tV3lSbHdLZEhFT2RmdWpERTJPd1ltU2dhU2xa?= =?utf-8?B?bU5RNHdMRjd0dTh3Z3k1NUNCV0txL1lVbXJMSFlWbTZ1Y1dEalFuZG42T1k4?= =?utf-8?B?SWtrY0VuLzA0QnpSL3krczVBemErZEJVL2hjR283TFdTSmhLWi8vbXpFY2l4?= =?utf-8?B?V0thdmVaWEdxNUhyQXA1eFppcytPTkprSUowYm1IMWkzZzJDd3RucEFWZzJn?= =?utf-8?B?MGlWM2dZbkVnQk82VHdVcXplazJTaVRlY09LM2F3QjM5YWkxYngvMXF6bXBi?= =?utf-8?B?aDl4eHA4YVBJbFRra2hpL3JzK2I4L0RtL0Y0RXhqOTZuc3I5YXZHVTZWMlFl?= =?utf-8?B?bjA2dkRCdGZmWDE3U0dCMGpXNkZYZFNmUzNBWW9nQzZKSlFoZEpFVGlGWUdC?= =?utf-8?B?UjhOMzJEd1kydWtZV3hVNFM5QmY0aFp1em0vbjE3WTZ1akpLRGRCbnY2MWts?= =?utf-8?B?SmlUSHRBblFqWWMyUU03Mkk4RDYrU2lEQjNqRERDMWx2blVZQ25Ma3hMOXhv?= =?utf-8?B?MlNvOEhrZWZ1TDVVU05LeHhRR0hXcXc4NVJIZllsV1B1RmJ6cFlDdnpxTlFZ?= =?utf-8?B?c25UNzhPY3FSYkpmUGFNc0hrN3JBYzR3bzFmNlIxRi8xNjBoREJXbmFleTVy?= =?utf-8?B?cHNOdXd0MEtYMGFUbW43ajJGTkU5bmh4cGc4VVdLbHBOOW5zV056SE92ZklW?= =?utf-8?B?S2xUUG9makUrYWRoakM2SytaM3BGWDliNGhWTHg0dmQ3citWRVI3cFpKemxy?= =?utf-8?B?clU1d1lMcFpQbEtvV08wNTlHM3NwdWx2d203ZXEzUTdJeklYU0R4RkVuU2pl?= =?utf-8?B?VmtIbGpQL2hBeCsxaldXT1FpQ0Y2Mzc3WXJkcTBSTmFRc2lTWmZuQjNVeklP?= =?utf-8?B?b1ZRbW9kbEk5cThvbFUxTGh4RHVidzF5VXFWNUQyeE9uY29veFVYb0ZtenJD?= =?utf-8?B?N1FkSk5ZdHAxeWNCNEYydjN4am4zenAvRFZISDRIcmxSQjBhWElzTHRqWW9x?= =?utf-8?B?b2pKdmpJNHpBTUUxWUVWMVRWNkYwNGdxN3piVXdIekExUHNIRUh2c3FmNU01?= =?utf-8?B?T3BLR0VNYVg2YmVBUXhyUjJLRzgySW1qMy8rTE05ZFVYcG1kUDh2anU1SzQ5?= =?utf-8?B?Uzk1UVRQRXNRRFFZdFA0b3JqR0ZLb3c1dDUvMFZRcVIyMFd6dnh1ZHNibFpq?= =?utf-8?B?anRJNFkvWWN3MFhsMWNtSHB0d0ZuVXdkVUwyLzBxcUhURUpWZEpMajFTMm5K?= =?utf-8?B?dWl2Z2FDOHBqNDRUUDNoWkg3YzZoWGRoYXdzSUIxSkthZWtZTWdoeUxTNnE5?= =?utf-8?B?WTVaWGZRWGM5S2JUU2FTMExNUWlHQXhselREU2l5VHdHNjVMRFp1WFJJSEZv?= =?utf-8?B?Y1pyYk02TUl2ckU3eWpaTEtDaXlhUXVFMDhIb1FocENqU01hSjVLUFBTRG14?= =?utf-8?B?ZGo1UDVVNEZqSDlNcEJvamhweDladnpqK095SWJoMWFZMGJJOFFxb0V0SFZH?= =?utf-8?B?WGVxYjFZVDhUZ20yWUZwUG9pViswZ05xMXlxN09nZTBpbjl0RkxHdGdvZE1r?= =?utf-8?B?QnduT3lzNWV4QlNiVFYxaXpKUGpJU2hGNkQrNm8xMmIxbUU2MXFPNHhlZ1I3?= =?utf-8?B?UXZGYzcwMjFYaElRejBkSTI0MU1scmdqMnlGemdHV0NEODExRFpvcDlrTXFF?= =?utf-8?B?MlROajBYZjBETHZwK28wa21hdUtVSnRSTG1GQWl3U0d6MmxtaXB4bmtsMFR4?= =?utf-8?B?WXlDdm1EUWRMR3pVSytJbUtDL3V0ejVHREpNREgxUENhYkNOdHZHbUdmTW5x?= =?utf-8?B?Q0RDNzVTeVM4cWtRNHBqT3d2MDhHeGYwbVdmUW92UkRFNGpGamg1V3ZVZmRX?= =?utf-8?Q?0dnGgbNXryiIie3g81XSIFGJEUj?= X-Microsoft-Exchange-Diagnostics: 1; CY4PR1301MB2023; 6:y/ejbBgfv85kkAxcAec4mOcmDxtnUTLGKZvnMwV2PzDQiAq7jx98JoZjv9l4ltWHEdxUZRHaRIYLanlQ6HVmeO78h+to2tc+JEmiQBf/mSGpriXDd0ze7y2G6WIzqe/D8wiywsnTrOnu2o6NRK9f0qui6sk/Cskq+2mi8KbptZf8qCLnRs1f0+nC7iwzQFI2za5kCwtFLlwcNxHU6AvX8vHp52grs2Hgj2Vk3t8tQ51d/anm+l/6+eFuTQHP/PoFWSGqEQx04gC0yr73f6Aem+URTB3han8KmoiT2WRcxBNRwWRcpRqafcGqArJ6G3R30Vj4SpKstbnyLvXzhf2IsBY49ehFxZbH05BGn3Jw4Gk=; 5:9HWnwqcVtv6P7+EoCE+3oWmoMrgMgU6YqAYs+65riiP3M5MHZJdAWvdJXzxFiry9erx7LP/FmZJFQw2s4VeLenQ0mNqi5H4jIGxdysJnl248aYFuKvo02MFI9xcBApi6cCHM8MXZ20k9xtaMi+T0ReexTIDlRQo2Ka/+SwqYSag=; 24:KHDQBVnGnKBw+8urb5tCumVJZ7p/MXMBUIIaxZBcLwzNGk4ZM5XUNeKuEQ+Q8cdDNzHVC7wSGuK//6GL1m7t20HLY0zVIaRQRAclf2xoD6c=; 7:XWwcTT6MEocDSx65Gt6X4RI5gO18iN+QYnDu1xqJ1rqAr8DKFIUAboAYtrQsjqTok36c3rTkagfWfjGw5TeYuaTVud00la8LEyfIsAEXNapyEfSRWdTxFP29HwI7keCU6kHFzwlpwOlQkIfDkuEG18wapSld6xds5o6FzumM+xEcllIE+1sM9eXzR/YG7UR7iVIF2ERhvOOCJRVfEqdlj6xFYLlelR84On4Ip/LM7nFd+vPeFdcXvLClGeICmKSq SpamDiagnosticOutput: 1:99 SpamDiagnosticMetadata: NSPM X-OriginatorOrg: bsquare.com X-MS-Exchange-CrossTenant-OriginalArrivalTime: 23 Jan 2018 10:48:35.7563 (UTC) X-MS-Exchange-CrossTenant-Network-Message-Id: 1f73334a-c6ab-422b-9ac0-08d5624edade X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted X-MS-Exchange-CrossTenant-Id: c078f217-c3b7-46c6-bf76-ff2c451cfe9a X-MS-Exchange-Transport-CrossTenantHeadersStamped: CY4PR1301MB2023 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, 23 Jan 2018 10:48:38 -0000 On 22/01/2018 17:07, Alan Somers wrote: > Since upgrading my jail server to 11.1-RELEASE, the clock occasionally > jumps backwards by 5-35 minutes for no apparent reason. Has anybody seen > something like this? > > Details > ===== > > * Happens about once a day on my jail server, and has happened at least > once on a separate bhyve server. > > * The jumps almost always happen between 1 and 3 AM, but I've also seen > them happen at 06:30 and 20:15. > That's the window when the period scripts are run which if you have a default configuration and a lot of jails will put the system under a lot of stress. > * I'm using the default ntp.conf file. > Are you running ntpd inside the jail or on the jail host? On my jail systems (which are 10.3 and 11.1) I run ntpd out the jail host (outside all jails) and not inside the jails and the jails then get the accurate time as the underlying host has accurate time. Mike -- Mike Pumford | Senior Software Engineer T: +44 (0) 1225 710635 BSQUARE - The business of IoT www.bsquare.com From owner-freebsd-stable@freebsd.org Tue Jan 23 13:34:13 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 67A5DED4501 for ; Tue, 23 Jan 2018 13:34:13 +0000 (UTC) (envelope-from rblayzor.bulk@inoc.net) Received: from cp1.c0.inoc.net (cp1.c0.inoc.net [64.246.141.1]) (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 340CA7BBD2; Tue, 23 Jan 2018 13:34:13 +0000 (UTC) (envelope-from rblayzor.bulk@inoc.net) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=inoc.net; s=default; h=To:References:Message-Id:Content-Transfer-Encoding:Cc:Date: In-Reply-To:From:Subject:Mime-Version:Content-Type:Sender:Reply-To:Content-ID :Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To: Resent-Cc:Resent-Message-ID:List-Id:List-Help:List-Unsubscribe:List-Subscribe :List-Post:List-Owner:List-Archive; bh=na4oysyqlzHj7N315IKxsInSPXKhfzy8H1Fdn1JMUQk=; b=Azx/w0rCdpHwweARzUPq5XbTJp FRa28HYKGXEDBUaebC4PmucmAcLPiKK/LQRz9e2W9hOmBwbao8wqlXI6WHOjSXDouQ+iw+frervS1 ofbjTSd/HHzrFmy/BM7X91VlGOV3CpO+h/oFObjqGPBqqWvezGlY94K/7o9Vqp+TVEHy+Tk10/OKp gI28Hp7UFnV21dbi0A4Afwo185NbVIjA+4eH7jHuIhvEPQwCKPvGsL/RMGf8wOyxbco7VZB0Yq4Th rSLl7/S/q0UHgQtqliiSWBpJVKMH8xrf2cA1jVoHelhsYgBPuBX6tFiNh3W4jsyNtY9rZCA5zNR6n +f1dW5Xw==; Received: from pool-108-4-157-162.albyny.fios.verizon.net ([108.4.157.162]:64920 helo=[10.99.3.101]) by cp1.c0.inoc.net with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.89_1) (envelope-from ) id 1edxzN-0006fj-IR; Tue, 23 Jan 2018 12:47:45 +0000 Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 11.2 \(3445.5.20\)) Subject: Re: Clock occasionally jumps backwards on 11.1-RELEASE From: Robert Blayzor In-Reply-To: Date: Tue, 23 Jan 2018 07:47:44 -0500 Cc: FreeBSD Content-Transfer-Encoding: quoted-printable Message-Id: References: To: Alan Somers X-Mailer: Apple Mail (2.3445.5.20) X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - cp1.c0.inoc.net X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - inoc.net X-Get-Message-Sender-Via: cp1.c0.inoc.net: authenticated_id: rblayzor@inoc.net X-Authenticated-Sender: cp1.c0.inoc.net: rblayzor@inoc.net X-Source: X-Source-Args: X-Source-Dir: 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, 23 Jan 2018 13:34:13 -0000 On Jan 22, 2018, at 12:07 PM, Alan Somers wrote: >=20 > * Sometimes the jumps happen immediately after ntpd adds a new server = to > its list, but not always. >=20 > * I'm using the default ntp.conf file. >=20 > * ntpd is running on both, and it should be the only process touching = the > clock. I have a script running "ntpq -c peers" once a minute, which = shows > the offset for one server suddenly jump to a large negative number. = Then > the offsets for other servers jump to the same value, then either ntpd > fixes the clock or exits because the offset is too high. - Lose ntpd running in jails and run it only on the host. Running in the = jail is totally unnecessary. - Is this a bare metal server or VM? Lots of clock issues with VM=E2=80=99= s=E2=80=A6 - Stagger your periodic jobs on the host and the jail so they don=E2=80=99= t all run at the same time slamming the host. -- inoc.net!rblayzor XMPP: rblayzor.AT.inoc.net PGP: https://inoc.net/~rblayzor/ From owner-freebsd-stable@freebsd.org Tue Jan 23 15:40:55 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 02C09ED9C2C for ; Tue, 23 Jan 2018 15:40:55 +0000 (UTC) (envelope-from asomers@gmail.com) Received: from mail-lf0-x22d.google.com (mail-lf0-x22d.google.com [IPv6:2a00:1450:4010:c07::22d]) (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 79C7082886 for ; Tue, 23 Jan 2018 15:40:54 +0000 (UTC) (envelope-from asomers@gmail.com) Received: by mail-lf0-x22d.google.com with SMTP id t139so1177242lff.0 for ; Tue, 23 Jan 2018 07:40:54 -0800 (PST) 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=6791LFUdMussVrBAFHsud4R7FE3mvDzH7kq8Xq3AoVk=; b=MY/1gjMB3XtHYs5b2gUIVE2Ohehw13ErbJC2qJfIVtJ8eeYkAXLQ6n3HJ+ONabGDn7 9VcIjDnNfdnOC9La1/tJXxyaNf7A73P5ikDH+0fLd5DWUuSLv/w+3Ni2k0cDOFG9gePU gwqW3avBAo4MKoBq8UBzFFCwTTOiU4zarldoLWv75yVJOqNvjfhRNo/UHlwp5y/LyQWG dek5hg4VPHnEeoPd99CSt5GoROFkcjDawLa0YC+OXUWTRwUdIjL43fOYijjxe+09z42R ZPa3B7rfeNBFH7LrD4DdvLbf/qkKTN1iA5o6nxiqIKnAYb1I5c/oBUYd/H+nwpQ5a88b Q8Mw== 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=6791LFUdMussVrBAFHsud4R7FE3mvDzH7kq8Xq3AoVk=; b=UJUP/1xkQcJ2wBj9uNYrlkJVg0kFn4NHltJ1idHNJXhXrmbeD4A27CObynutJfCRns /wpE94/9SKg/N/pA1ZALovCMn94T+WhAa8RHxgNr068nKECpoTeabY2nNWbXY2tB8Pjw wI8OZ5nDQZvarQPf1K7mL/kLkN2H4+UH7sB3Yp6GFbkmrC3JFcojUlSLIdA/n91aqdUp J1gFXHgZmVwks3xurHpEhey6/dVDzQNH/LjPKmDTq9uE0HzQi0YYrG1FpsREKsA1xQPi 07x0wDKM9r833c9dkqZXG20pNmcRHqwmr0sjlWp5L15vdM/G5mtpMFE0iXAxG2hOf5U/ nZsQ== X-Gm-Message-State: AKwxytc3kVSJtRywpR8+x1wvNQn2twkXHVO5Rb/CFmVz3VpFyE2FbNhu Zo0t63SS0WCbs4LCAcKPwktVw576hqQePoNyS3o= X-Google-Smtp-Source: AH8x2270BSNFG9uq9taoUKVua1UrQZSluGXq6ocU0ONeOTG3UfRNp18JlISzJiN92NWmLM5MGKJHXI89oCi4M0AFqLY= X-Received: by 10.46.22.9 with SMTP id w9mr1383140ljd.91.1516722052396; Tue, 23 Jan 2018 07:40:52 -0800 (PST) MIME-Version: 1.0 Sender: asomers@gmail.com Received: by 10.179.87.131 with HTTP; Tue, 23 Jan 2018 07:40:51 -0800 (PST) In-Reply-To: <0b170dae-b816-ea49-3516-40bfd1deaa2a@bsquare.com> References: <0b170dae-b816-ea49-3516-40bfd1deaa2a@bsquare.com> From: Alan Somers Date: Tue, 23 Jan 2018 08:40:51 -0700 X-Google-Sender-Auth: hXnH5p4ZWRHe0KuRwT3MkOJKB6Q Message-ID: Subject: Re: Clock occasionally jumps backwards on 11.1-RELEASE To: Mike Pumford Cc: FreeBSD 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, 23 Jan 2018 15:40:55 -0000 On Tue, Jan 23, 2018 at 3:48 AM, Mike Pumford wrote: > On 22/01/2018 17:07, Alan Somers wrote: > >> Since upgrading my jail server to 11.1-RELEASE, the clock occasionally >> jumps backwards by 5-35 minutes for no apparent reason. Has anybody seen >> something like this? >> >> Details >> ===== >> >> * Happens about once a day on my jail server, and has happened at least >> once on a separate bhyve server. >> >> * The jumps almost always happen between 1 and 3 AM, but I've also seen >> them happen at 06:30 and 20:15. >> >> That's the window when the period scripts are run which if you have a > default configuration and a lot of jails will put the system under a lot of > stress. > That did not fail to escape my notice. However, none of the jails' periodic jobs involve the clock in any way. And I wouldn't think that a high CPU load could cause clock drift, could it? This isn't Windows XP, after all. > * I'm using the default ntp.conf file. >> >> Are you running ntpd inside the jail or on the jail host? On my jail > systems (which are 10.3 and 11.1) I run ntpd out the jail host (outside all > jails) and not inside the jails and the jails then get the accurate time as > the underlying host has accurate time. > Only on the host. New info: there is a possibility that my NFS server is hanging for awhile. That would explain my problem's timing. However, ntpd shouldn't be accessing any NFS shares, and I wouldn't think that a hung NFS server should be able to pause the clock. I'm doing a new experiment that should be more informative. But I'll have to wait until the problem recurs to learn anything. -Alan From owner-freebsd-stable@freebsd.org Tue Jan 23 17:15:44 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id AC16FEB8964 for ; Tue, 23 Jan 2018 17:15:44 +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 5EB031BF4; Tue, 23 Jan 2018 17:15:44 +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 w0NHFgRN079895 (version=TLSv1 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Tue, 23 Jan 2018 12:15:42 -0500 (EST) (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 w0NHFeRj062243; Tue, 23 Jan 2018 12:15:40 -0500 (EST) (envelope-from mike@sentex.net) Subject: Re: Ryzen issues on FreeBSD ? To: Don Lewis Cc: Peter Moody , Pete French , freebsd-stable@freebsd.org References: <8e842dec-ade7-37d1-6bd8-856ea1a827ca@sentex.net> <9b769e4e-b098-b294-0bce-8bb1c42e8a59@rootautomation.com> <730eb882-1c6a-afb7-0ada-396db44fb34b@ingresso.co.uk> <8b882970-4d5d-2a96-4dac-779cab07b9ae@sentex.net> <343acf99-3e9e-093a-7390-c142396c2985@sentex.net> From: Mike Tancsa Organization: Sentex Communications Message-ID: <3dd9a61b-511d-db2e-80ca-cbc9a4b65f92@sentex.net> Date: Tue, 23 Jan 2018 12:15:41 -0500 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.5.2 MIME-Version: 1.0 In-Reply-To: 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, 23 Jan 2018 17:15:44 -0000 On 1/22/2018 5:13 PM, Don Lewis wrote: > On 22 Jan, Mike Tancsa wrote: >> On 1/22/2018 1:41 PM, Peter Moody wrote: >>> fwiw, I upgraded to 11-STABLE (11.1-STABLE #6 r328223), applied the >>> hw.lower_amd64_sharedpage setting to my loader.conf and got a crash >>> last night following the familiar high load -> idle. this was with SMT >>> re-enabled. no crashdump, so it was the hard crash that I've been >>> getting. >> >> hw.lower_amd64_sharedpage=1 is the default on AMD boxes no ? I didnt >> need to set mine to 1 >> >>> >>> shrug, I'm at a loss here. >> >> I am trying an RMA with AMD. > > Something else that you might want to try is 12.0-CURRENT. There might > be some changes in HEAD that need to be merged back to 11.1-STABLE. Temp works as expected now. However, a (similar?) hang building Samba47. ctrl+T shows load: 1.98 cmd: python2.7 53438 [usem] 54.70r 14.98u 6.04s 0% 230992k make: Working in: /usr/ports/net/samba47 load: 0.34 cmd: python2.7 53438 [usem] 168.48r 14.98u 6.04s 0% 230992k make: Working in: /usr/ports/net/samba47 load: 0.31 cmd: python2.7 53438 [usem] 174.12r 14.98u 6.04s 0% 230992k make: Working in: /usr/ports/net/samba47 Going to try the RMA route and see if the replacement CPU avoids this problem. # uname -a FreeBSD amdtestr12.sentex.ca 12.0-CURRENT FreeBSD 12.0-CURRENT #1 r328282: Tue Jan 23 11:34:18 EST 2018 mdtancsa@amdtestr12.sentex.ca:/usr/obj/usr/src/amd64.amd64/sys/server amd64 dev.amdtemp.0.core0.sensor0: 52.6C dev.amdtemp.0.sensor_offset: 0 dev.amdtemp.0.%parent: hostb0 dev.amdtemp.0.%pnpinfo: dev.amdtemp.0.%location: dev.amdtemp.0.%driver: amdtemp dev.amdtemp.0.%desc: AMD CPU On-Die Thermal Sensors dev.amdtemp.%parent: dev.cpu.11.temperature: 52.6C dev.cpu.10.temperature: 52.6C dev.cpu.9.temperature: 52.6C dev.cpu.8.temperature: 52.6C dev.cpu.7.temperature: 52.6C dev.cpu.6.temperature: 52.6C dev.cpu.5.temperature: 52.6C dev.cpu.4.temperature: 52.6C dev.cpu.3.temperature: 52.6C dev.cpu.2.temperature: 52.6C dev.cpu.1.temperature: 52.6C dev.cpu.0.temperature: 52.6C -- ------------------- Mike Tancsa, tel +1 519 651 3400 Sentex Communications, mike@sentex.net Providing Internet services since 1994 www.sentex.net Cambridge, Ontario Canada http://www.tancsa.com/ From owner-freebsd-stable@freebsd.org Tue Jan 23 18:15:24 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id DC3C4EBE0CC for ; Tue, 23 Jan 2018 18:15:24 +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 B481163B8A for ; Tue, 23 Jan 2018 18:15:24 +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 w0NIFnfg095285 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=FAIL); Tue, 23 Jan 2018 18:15:50 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 w0NIFF82037616 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 23 Jan 2018 10:15:16 -0800 (PST) (envelope-from truckman@FreeBSD.org) Date: Tue, 23 Jan 2018 10:15:10 -0800 (PST) From: Don Lewis Subject: Re: Ryzen issues on FreeBSD ? To: Pete French cc: freebsd-stable@freebsd.org In-Reply-To: Message-ID: References: <8e842dec-ade7-37d1-6bd8-856ea1a827ca@sentex.net> <3b625072-dfb3-6b4f-494d-7fe1b2fa554c@ingresso.co.uk> <2c6ce4dd-f43c-7c40-abc2-732d6f8996ec@sentex.net> <795dbb79-3c18-d967-98b9-5d09a740dbfe@sentex.net> <9b769e4e-b098-b294-0bce-8bb1c42e8a59@rootautomation.com> <730eb882-1c6a-afb7-0ada-396db44fb34b@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: Tue, 23 Jan 2018 18:15:25 -0000 On 23 Jan, Pete French wrote: > On 22/01/2018 18:25, Don Lewis wrote: >> On 22 Jan, Pete French wrote: >>> >>> >>> On 21/01/2018 19:05, Peter Moody wrote: >>>> hm, so i've got nearly 3 days of uptime with smt disabled. >>>> unfortunately this means that my otherwise '12' cores is actually only >>>> '6'. I'm also getting occasional segfaults compiling go programs. >>> >>> Isn't go known to have issues on BSD anyway though ? I have seen >>> complaints of random crashes running go under BSD systems - and >>> preseumably the go compiler itself is written in go, so those issues >>> might surface when compiling. >> >> Not that I'm aware of. I'm not a heavy go user on FreeBSD, but I don't >> recall any unexpected go crashes and I haven't seen problems building >> go on my older AMD machines. > > > From the go 1.9 release notes: > > "Known Issues > There are some instabilities on FreeBSD that are known but not > understood. These can lead to program crashes in rare cases. See issue > 15658. Any help in solving this FreeBSD-specific issue would be > appreciated." > > ( link is to https://github.com/golang/go/issues/15658 ) > > Having said that, we use it internally and have not seen any issues with > it ourselves. Just I am wary of the release notes, and that issue report. Interesting ... I've only seen problems on my Ryzen machine, which has >= 2x the number of cores as any of my other machines. All are AMD CPUs. From owner-freebsd-stable@freebsd.org Tue Jan 23 19:08:41 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D711AEC0D1E for ; Tue, 23 Jan 2018 19:08:41 +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 78AB369D8B; Tue, 23 Jan 2018 19:08:41 +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 w0NJ8eOf004629 (version=TLSv1 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Tue, 23 Jan 2018 14:08:40 -0500 (EST) (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 w0NJ8cck064334; Tue, 23 Jan 2018 14:08:38 -0500 (EST) (envelope-from mike@sentex.net) Subject: Re: Ryzen issues on FreeBSD ? To: Don Lewis Cc: Peter Moody , Pete French , freebsd-stable@freebsd.org References: <8e842dec-ade7-37d1-6bd8-856ea1a827ca@sentex.net> <9b769e4e-b098-b294-0bce-8bb1c42e8a59@rootautomation.com> <730eb882-1c6a-afb7-0ada-396db44fb34b@ingresso.co.uk> <8b882970-4d5d-2a96-4dac-779cab07b9ae@sentex.net> <343acf99-3e9e-093a-7390-c142396c2985@sentex.net> From: Mike Tancsa Organization: Sentex Communications Message-ID: Date: Tue, 23 Jan 2018 14:08:38 -0500 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.5.2 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, 23 Jan 2018 19:08:41 -0000 On 1/22/2018 5:13 PM, Don Lewis wrote: >> >> I am trying an RMA with AMD. > > Something else that you might want to try is 12.0-CURRENT. There might > be some changes in HEAD that need to be merged back to 11.1-STABLE. It looks like this thread got mention on phorix :) In the comments section (comment #9) a post makes reference to http://blog.programster.org/ubuntu-16-04-compile-custom-kernel-for-ryzen I guess Linux is still working through similar lockups too :( ---Mike -- ------------------- Mike Tancsa, tel +1 519 651 3400 Sentex Communications, mike@sentex.net Providing Internet services since 1994 www.sentex.net Cambridge, Ontario Canada http://www.tancsa.com/ From owner-freebsd-stable@freebsd.org Tue Jan 23 19:22:28 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B5F81EC1ACD for ; Tue, 23 Jan 2018 19:22:28 +0000 (UTC) (envelope-from agapon@gmail.com) Received: from mail-lf0-f49.google.com (mail-lf0-f49.google.com [209.85.215.49]) (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 3F1C46A915; Tue, 23 Jan 2018 19:22:27 +0000 (UTC) (envelope-from agapon@gmail.com) Received: by mail-lf0-f49.google.com with SMTP id x196so2005981lfd.12; Tue, 23 Jan 2018 11:22:27 -0800 (PST) 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:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=tU7J/Fxz+nw8GhFqYVX+2DhpHwRwvg6hHRAoJ1vdrcI=; b=BJy/ZyThMtRIHvcsKiuudNOxxBwjr6IQZ9Ve0uYVUm4dkc43gfr24jAbS744Bfp1rd AMjOfNHFk/mgWIuJhO8zpMmNa4dH13iowGJMuIS9O0CH2Qh2maVCjYkaZS7RDm3XkmaO J2odCUn7JEBZzcTfz01Cqx5TJoAgmcm76sbDsH/AxVo6s5B85100Rur1H8uZJfS/ePGb AXjau7GRSHSLw3VE8yEdUiBhZkWTGu31QdZyvgIJuxLgVLHOZ5BpMOi9ZhqDiriRHFzy LT1qw+g1oEBE1axq7uLYHtkELVg/ZzYC2nrbK7RSKEw8Fufrv8emKkrqqPUmy/qWKfkJ sMyw== X-Gm-Message-State: AKwxytfs7w4Wa2NVbqtFeMDQOuqiolrXXidM5ZUNdvkLASXJPYPjR4uW 04/TUmqG6vyLbBb5ksz/p17Vhezh X-Google-Smtp-Source: AH8x227lUUII/JtR7Qo/Al8jw+wGH4BG2HvvLcSjjsUrjiz62W1MvORBB2mgKbcX1ssaXhUH4MFpvg== X-Received: by 10.25.215.223 with SMTP id q92mr1633326lfi.107.1516735339542; Tue, 23 Jan 2018 11:22:19 -0800 (PST) Received: from [192.168.0.88] (east.meadow.volia.net. [93.72.151.96]) by smtp.googlemail.com with ESMTPSA id n24sm2797063ljc.45.2018.01.23.11.22.17 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 23 Jan 2018 11:22:18 -0800 (PST) Subject: Re: Ryzen issues on FreeBSD ? To: Mike Tancsa Cc: Don Lewis , freebsd-stable@freebsd.org References: <8e842dec-ade7-37d1-6bd8-856ea1a827ca@sentex.net> <9b769e4e-b098-b294-0bce-8bb1c42e8a59@rootautomation.com> <730eb882-1c6a-afb7-0ada-396db44fb34b@ingresso.co.uk> <8b882970-4d5d-2a96-4dac-779cab07b9ae@sentex.net> <343acf99-3e9e-093a-7390-c142396c2985@sentex.net> <3dd9a61b-511d-db2e-80ca-cbc9a4b65f92@sentex.net> From: Andriy Gapon Message-ID: <0cde9097-a454-a979-fac9-2d5b63a82759@FreeBSD.org> Date: Tue, 23 Jan 2018 21:22:17 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.5.2 MIME-Version: 1.0 In-Reply-To: <3dd9a61b-511d-db2e-80ca-cbc9a4b65f92@sentex.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: Tue, 23 Jan 2018 19:22:28 -0000 On 23/01/2018 19:15, Mike Tancsa wrote: > On 1/22/2018 5:13 PM, Don Lewis wrote: >> On 22 Jan, Mike Tancsa wrote: >>> On 1/22/2018 1:41 PM, Peter Moody wrote: >>>> fwiw, I upgraded to 11-STABLE (11.1-STABLE #6 r328223), applied the >>>> hw.lower_amd64_sharedpage setting to my loader.conf and got a crash >>>> last night following the familiar high load -> idle. this was with SMT >>>> re-enabled. no crashdump, so it was the hard crash that I've been >>>> getting. >>> >>> hw.lower_amd64_sharedpage=1 is the default on AMD boxes no ? I didnt >>> need to set mine to 1 >>> >>>> >>>> shrug, I'm at a loss here. >>> >>> I am trying an RMA with AMD. >> >> Something else that you might want to try is 12.0-CURRENT. There might >> be some changes in HEAD that need to be merged back to 11.1-STABLE. > > > Temp works as expected now. However, a (similar?) hang building Samba47. > > ctrl+T shows If that works, then maybe you can get procstat -kk -a or a crash dump. Maybe this is not a hardware problem at all (or maybe it is). > load: 1.98 cmd: python2.7 53438 [usem] 54.70r 14.98u 6.04s 0% 230992k > make: Working in: /usr/ports/net/samba47 > load: 0.34 cmd: python2.7 53438 [usem] 168.48r 14.98u 6.04s 0% 230992k > make: Working in: /usr/ports/net/samba47 > load: 0.31 cmd: python2.7 53438 [usem] 174.12r 14.98u 6.04s 0% 230992k > make: Working in: /usr/ports/net/samba47 -- Andriy Gapon From owner-freebsd-stable@freebsd.org Tue Jan 23 19:26:19 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id BD012EC1DE6 for ; Tue, 23 Jan 2018 19:26:19 +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 8282D6AB3D; Tue, 23 Jan 2018 19:26:19 +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 w0NJQIlJ008395 (version=TLSv1 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Tue, 23 Jan 2018 14:26:18 -0500 (EST) (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 w0NJQGj2064372; Tue, 23 Jan 2018 14:26:16 -0500 (EST) (envelope-from mike@sentex.net) Subject: Re: Ryzen issues on FreeBSD ? To: Andriy Gapon Cc: Don Lewis , freebsd-stable@freebsd.org References: <8e842dec-ade7-37d1-6bd8-856ea1a827ca@sentex.net> <9b769e4e-b098-b294-0bce-8bb1c42e8a59@rootautomation.com> <730eb882-1c6a-afb7-0ada-396db44fb34b@ingresso.co.uk> <8b882970-4d5d-2a96-4dac-779cab07b9ae@sentex.net> <343acf99-3e9e-093a-7390-c142396c2985@sentex.net> <3dd9a61b-511d-db2e-80ca-cbc9a4b65f92@sentex.net> <0cde9097-a454-a979-fac9-2d5b63a82759@FreeBSD.org> From: Mike Tancsa Organization: Sentex Communications Message-ID: <3142acce-5df1-d09c-b320-c59a226662ac@sentex.net> Date: Tue, 23 Jan 2018 14:26:17 -0500 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.5.2 MIME-Version: 1.0 In-Reply-To: <0cde9097-a454-a979-fac9-2d5b63a82759@FreeBSD.org> 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, 23 Jan 2018 19:26:19 -0000 On 1/23/2018 2:22 PM, Andriy Gapon wrote: >> >> ctrl+T shows > > If that works, then maybe you can get procstat -kk -a or a crash dump. > Maybe this is not a hardware problem at all (or maybe it is). Unfortunately all 3 CPUs are packed up now and on their way to AMD for RMA. As soon as I get some replacements, I will get back to this. I am thinking of looking at a ThreadRipper board in the mean time as the Epyc ones are on 2-4week back order from my suppliers :( > >> load: 1.98 cmd: python2.7 53438 [usem] 54.70r 14.98u 6.04s 0% 230992k >> make: Working in: /usr/ports/net/samba47 >> load: 0.34 cmd: python2.7 53438 [usem] 168.48r 14.98u 6.04s 0% 230992k >> make: Working in: /usr/ports/net/samba47 >> load: 0.31 cmd: python2.7 53438 [usem] 174.12r 14.98u 6.04s 0% 230992k >> make: Working in: /usr/ports/net/samba47 > > > -- ------------------- Mike Tancsa, tel +1 519 651 3400 Sentex Communications, mike@sentex.net Providing Internet services since 1994 www.sentex.net Cambridge, Ontario Canada http://www.tancsa.com/ From owner-freebsd-stable@freebsd.org Tue Jan 23 20:13:49 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 97956EC45E4 for ; Tue, 23 Jan 2018 20:13:49 +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 3998E6CB20; Tue, 23 Jan 2018 20:13: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 w0NKDmLD019409 (version=TLSv1 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Tue, 23 Jan 2018 15:13:48 -0500 (EST) (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 w0NKDjF8064478; Tue, 23 Jan 2018 15:13:45 -0500 (EST) (envelope-from mike@sentex.net) Subject: Re: Ryzen issues on FreeBSD ? From: Mike Tancsa To: Don Lewis Cc: freebsd-stable@freebsd.org, Peter Moody , Pete French References: <8e842dec-ade7-37d1-6bd8-856ea1a827ca@sentex.net> <9b769e4e-b098-b294-0bce-8bb1c42e8a59@rootautomation.com> <730eb882-1c6a-afb7-0ada-396db44fb34b@ingresso.co.uk> <8b882970-4d5d-2a96-4dac-779cab07b9ae@sentex.net> <343acf99-3e9e-093a-7390-c142396c2985@sentex.net> Organization: Sentex Communications Message-ID: <879f7f7b-00ad-ede6-9f86-50a3bbda6616@sentex.net> Date: Tue, 23 Jan 2018 15:13:46 -0500 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.5.2 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, 23 Jan 2018 20:13:49 -0000 On 1/23/2018 2:08 PM, Mike Tancsa wrote: > On 1/22/2018 5:13 PM, Don Lewis wrote: >>> >>> I am trying an RMA with AMD. >> >> Something else that you might want to try is 12.0-CURRENT. There might >> be some changes in HEAD that need to be merged back to 11.1-STABLE. > > It looks like this thread got mention on phorix :) In the comments > section (comment #9) a post makes reference to > > http://blog.programster.org/ubuntu-16-04-compile-custom-kernel-for-ryzen > > I guess Linux is still working through similar lockups too :( Ubuntu has a patch / workaround for these random lockups which symptomatically sound very similar to what some of us have been experiencing https://bugs.launchpad.net/linux/+bug/1690085/comments/69 ---Mike -- ------------------- Mike Tancsa, tel +1 519 651 3400 Sentex Communications, mike@sentex.net Providing Internet services since 1994 www.sentex.net Cambridge, Ontario Canada http://www.tancsa.com/ From owner-freebsd-stable@freebsd.org Tue Jan 23 20:34:23 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3AD64EC59B4 for ; Tue, 23 Jan 2018 20:34:23 +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 5E6476DA38; Tue, 23 Jan 2018 20:34:22 +0000 (UTC) (envelope-from petefrench@ingresso.co.uk) Received: from [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 1ee5Fm-000D1N-7V; Tue, 23 Jan 2018 20:33:10 +0000 Subject: Re: Ryzen issues on FreeBSD ? To: Mike Tancsa , Don Lewis Cc: Peter Moody , freebsd-stable@freebsd.org References: <8e842dec-ade7-37d1-6bd8-856ea1a827ca@sentex.net> <9b769e4e-b098-b294-0bce-8bb1c42e8a59@rootautomation.com> <730eb882-1c6a-afb7-0ada-396db44fb34b@ingresso.co.uk> <8b882970-4d5d-2a96-4dac-779cab07b9ae@sentex.net> <343acf99-3e9e-093a-7390-c142396c2985@sentex.net> From: Pete French Message-ID: <0bb2b241-6e79-0cc6-2046-9960609aedc2@ingresso.co.uk> Date: Tue, 23 Jan 2018 20:32:48 +0000 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:52.0) Gecko/20100101 Thunderbird/52.5.2 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: Tue, 23 Jan 2018 20:34:23 -0000 On 23/01/2018 19:08, Mike Tancsa wrote: > It looks like this thread got mention on phorix :) In the comments > section (comment #9) a post makes reference to > > http://blog.programster.org/ubuntu-16-04-compile-custom-kernel-for-ryzen > > I guess Linux is still working through similar lockups too :( Interesting - do we have anything like RCU implemented in the kernel which might be worth looking at ? From a quick glance it looks like its just a software technique, so I cant see which bits of the CPU it's tickling that might cause issues though. From owner-freebsd-stable@freebsd.org Tue Jan 23 22:28:24 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id F18BAECBF03 for ; Tue, 23 Jan 2018 22:28:23 +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 C753672DA9 for ; Tue, 23 Jan 2018 22:28:23 +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 w0NMSm3Q095829 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=FAIL); Tue, 23 Jan 2018 22:28:49 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 w0NMSEJh046441 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 23 Jan 2018 14:28:15 -0800 (PST) (envelope-from truckman@FreeBSD.org) Date: Tue, 23 Jan 2018 14:28:09 -0800 (PST) From: Don Lewis Subject: Re: Ryzen issues on FreeBSD ? To: Mike Tancsa cc: Peter Moody , Pete French , freebsd-stable@freebsd.org In-Reply-To: Message-ID: References: <8e842dec-ade7-37d1-6bd8-856ea1a827ca@sentex.net> <9b769e4e-b098-b294-0bce-8bb1c42e8a59@rootautomation.com> <730eb882-1c6a-afb7-0ada-396db44fb34b@ingresso.co.uk> <8b882970-4d5d-2a96-4dac-779cab07b9ae@sentex.net> <343acf99-3e9e-093a-7390-c142396c2985@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: Tue, 23 Jan 2018 22:28:24 -0000 On 23 Jan, Mike Tancsa wrote: > On 1/22/2018 5:13 PM, Don Lewis wrote: >>> >>> I am trying an RMA with AMD. >> >> Something else that you might want to try is 12.0-CURRENT. There might >> be some changes in HEAD that need to be merged back to 11.1-STABLE. > > It looks like this thread got mention on phorix :) In the comments > section (comment #9) a post makes reference to > > http://blog.programster.org/ubuntu-16-04-compile-custom-kernel-for-ryzen > > I guess Linux is still working through similar lockups too :( Yes. Interesting (and fairly concise) thread here: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1690085 From owner-freebsd-stable@freebsd.org Wed Jan 24 08:16:03 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 134DAEC6712 for ; Wed, 24 Jan 2018 08:16:03 +0000 (UTC) (envelope-from bennett@sdf.org) Received: from mx.sdf.org (ol.sdf.org [205.166.94.20]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "ol.sdf.org", Issuer "ol.sdf.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 986E27DA80 for ; Wed, 24 Jan 2018 08:16:02 +0000 (UTC) (envelope-from bennett@sdf.org) Received: from sdf.org (IDENT:bennett@otaku.freeshell.org [205.166.94.9]) by mx.sdf.org (8.15.2/8.14.5) with ESMTPS id w0O8Fj30025177 (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256 bits) verified NO); Wed, 24 Jan 2018 08:15:46 GMT Received: (from bennett@localhost) by sdf.org (8.15.2/8.12.8/Submit) id w0O8Fjo7010887; Wed, 24 Jan 2018 02:15:45 -0600 (CST) From: Scott Bennett Message-Id: <201801240815.w0O8Fjo7010887@sdf.org> Date: Wed, 24 Jan 2018 02:15:45 -0600 To: freebsd-stable@freebsd.org Subject: Re: why does buildworld fail on stable/11 ? Cc: lists User-Agent: Heirloom mailx 12.5 6/20/10 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii 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, 24 Jan 2018 08:16:03 -0000 Subject: Re: why does buildworld fail on stable/11 ? On Mon, 22 Jan 2018 12:42:58 +0000 lists wrote: >On 22/01/2018 09:17, Scott Bennett wrote: >> Anyway, I'm stuck. Can someone please tell me what is going wrong and >> how to fix it? I'd really like to be able to update my system, not only to >> keep it reasonably current, but also to be able to customize a kernel. Thanks >> in advance for any suggestions/solutions. > >Hi, Thank you for responding with your thoughts on this. > >What I'd do is firstly to make things as simple as possible. First do >the upgrade simply. Either delete or call make.conf & src.conf something Okay. >else. Then get a fresh src and ports tree via svnlite. Then do /usr/src has not been altered since I ran the checkout. Is there some reason to use svnlite rather than svn, which is how I did the checkout? > >rm -rf /buildwork/ccache.freebsd >mkdir /buildwork/ccache.freebsd I'm not following your thinking here. If I've eliminated /etc/make.conf from the picture, then ccache is not involved at all, so why should I wipe out the cache contents? > >then > >[/usr/src #] make cleandir && make clean && make buildworld && make >buildkernel && make installkernel && mergemaster -p At this point, that looks very optimistic, to say the least. :-) I've tried "make cleanworld" (with /etc/make.conf still in place), and it failed exactly like the buildworld example I posted before. > >[make changes if needed] > >[/usr/src #] make installworld && mergemaster > >[make more changes if needed] > >reboot > >then cd into /usr/src as root, then do > >yes | make delete-old >yes | make delete-old-libs What do you expect the above to accomplish on a freshly installed system on which no obsolete directories or libraries from a previous release should exist? > >reboot again > >then re-enable your extra lines in make.conf and src.conf, if you need them. > >It may be down to something in the ccache dir, I guess. > I will try it with no /etc/{make,src}.conf then just to find out what will happen, but I will still need a way to build from source with ccache involved in the process for normal use because it typically cuts the build times by 50% - 75% from the usual five or six hours elapsed time. Thanks again for your suggestions. I will try it without /etc/{make,src}.conf and report back. Scott Bennett, Comm. ASMELG, CFIAG ********************************************************************** * Internet: bennett at sdf.org *xor* bennett at freeshell.org * *--------------------------------------------------------------------* * "A well regulated and disciplined militia, is at all times a good * * objection to the introduction of that bane of all free governments * * -- a standing army." * * -- Gov. John Hancock, New York Journal, 28 January 1790 * ********************************************************************** From owner-freebsd-stable@freebsd.org Wed Jan 24 08:52:01 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 6A95BEC7EF1 for ; Wed, 24 Jan 2018 08:52:01 +0000 (UTC) (envelope-from bennett@sdf.org) Received: from mx.sdf.org (ol.sdf.org [205.166.94.20]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "ol.sdf.org", Issuer "ol.sdf.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id EB1167ED7B for ; Wed, 24 Jan 2018 08:52:00 +0000 (UTC) (envelope-from bennett@sdf.org) Received: from sdf.org (IDENT:bennett@otaku.freeshell.org [205.166.94.9]) by mx.sdf.org (8.15.2/8.14.5) with ESMTPS id w0O8pnRB022856 (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256 bits) verified NO); Wed, 24 Jan 2018 08:51:50 GMT Received: (from bennett@localhost) by sdf.org (8.15.2/8.12.8/Submit) id w0O8pnDl008705; Wed, 24 Jan 2018 02:51:49 -0600 (CST) From: Scott Bennett Message-Id: <201801240851.w0O8pnDl008705@sdf.org> Date: Wed, 24 Jan 2018 02:51:49 -0600 To: freebsd-stable@freebsd.org Subject: Re: why does buildworld fail on stable/11 ? Cc: lists User-Agent: Heirloom mailx 12.5 6/20/10 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii 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, 24 Jan 2018 08:52:01 -0000 Subject: Re: why does buildworld fail on stable/11 ? I wrote: > On Mon, 22 Jan 2018 12:42:58 +0000 lists wrote: >>On 22/01/2018 09:17, Scott Bennett wrote: >>> Anyway, I'm stuck. Can someone please tell me what is going wrong and >>> how to fix it? I'd really like to be able to update my system, not only to >>> keep it reasonably current, but also to be able to customize a kernel. Thanks >>> in advance for any suggestions/solutions. >> [much deleted --SB] >>then >> >>[/usr/src #] make cleandir && make clean && make buildworld && make >>buildkernel && make installkernel && mergemaster -p > > At this point, that looks very optimistic, to say the least. :-) I've >tried "make cleanworld" (with /etc/make.conf still in place), and it failed >exactly like the buildworld example I posted before. Okay. Here's what happened. Script started on Wed Jan 24 02:17:30 2018 hellas# mv /etc/make.conf{,.save} hellas# mv /etc/src.conf{,.save} hellas# cd /usr/src hellas# make cleandir "/usr/src/share/mk/local.sys.mk", line 51: Malformed conditional (${.MAKE.MODE:Mmeta*} != "") "/usr/src/share/mk/local.sys.mk", line 58: Malformed conditional (${.MAKE.MODE:Mnofilemon} == "") "/usr/src/share/mk/local.sys.mk", line 76: if-less else "/usr/src/share/mk/local.sys.mk", line 79: if-less endif "/usr/src/share/mk/sys.mk", line 476: if-less endif bmake: fatal errors encountered -- cannot continue *** Error code 1 Stop. make: stopped in /usr/src hellas# exit exit Script done on Wed Jan 24 02:19:04 2018 Does anyone have any idea what is so horribly broken in 11.1-STABLE? FWIW, this is on a ZFS installation done by the utterly braindead bsdinstall provided in stable/11 ISO images. Scott Bennett, Comm. ASMELG, CFIAG ********************************************************************** * Internet: bennett at sdf.org *xor* bennett at freeshell.org * *--------------------------------------------------------------------* * "A well regulated and disciplined militia, is at all times a good * * objection to the introduction of that bane of all free governments * * -- a standing army." * * -- Gov. John Hancock, New York Journal, 28 January 1790 * ********************************************************************** From owner-freebsd-stable@freebsd.org Wed Jan 24 11:39: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 43D22ECE9AF for ; Wed, 24 Jan 2018 11:39:44 +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 AAB0A84BCB for ; Wed, 24 Jan 2018 11:39:43 +0000 (UTC) (envelope-from dim@FreeBSD.org) Received: from coleburn.avinity.tv (unknown [77.95.97.98]) (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 393546C06; Wed, 24 Jan 2018 12:39:36 +0100 (CET) From: Dimitry Andric Message-Id: <0A86F03E-DB69-4DD0-B67B-E9BFBE3DC739@FreeBSD.org> Content-Type: multipart/signed; boundary="Apple-Mail=_DC6A645C-5AF6-4C3F-BE15-B19439F1FFA1"; protocol="application/pgp-signature"; micalg=pgp-sha1 Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Re: why does buildworld fail on stable/11 ? Date: Wed, 24 Jan 2018 12:39:35 +0100 In-Reply-To: <201801240851.w0O8pnDl008705@sdf.org> Cc: freebsd-stable@freebsd.org, lists To: Scott Bennett References: <201801240851.w0O8pnDl008705@sdf.org> X-Mailer: Apple Mail (2.3273) 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, 24 Jan 2018 11:39:44 -0000 --Apple-Mail=_DC6A645C-5AF6-4C3F-BE15-B19439F1FFA1 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii On 24 Jan 2018, at 09:51, Scott Bennett wrote: >=20 > Subject: Re: why does buildworld fail on stable/11 ? >=20 > I wrote: >> On Mon, 22 Jan 2018 12:42:58 +0000 lists = wrote: >>> On 22/01/2018 09:17, Scott Bennett wrote: >>>> Anyway, I'm stuck. Can someone please tell me what is going = wrong and >>>> how to fix it? I'd really like to be able to update my system, not = only to >>>> keep it reasonably current, but also to be able to customize a = kernel. Thanks >>>> in advance for any suggestions/solutions. >>>=20 > [much deleted --SB] >>> then >>>=20 >>> [/usr/src #] make cleandir && make clean && make buildworld && make >>> buildkernel && make installkernel && mergemaster -p >>=20 >> At this point, that looks very optimistic, to say the least. :-) = I've >> tried "make cleanworld" (with /etc/make.conf still in place), and it = failed >> exactly like the buildworld example I posted before. >=20 > Okay. Here's what happened. >=20 > Script started on Wed Jan 24 02:17:30 2018 > hellas# mv /etc/make.conf{,.save} > hellas# mv /etc/src.conf{,.save} > hellas# cd /usr/src > hellas# make cleandir > "/usr/src/share/mk/local.sys.mk", line 51: Malformed conditional = (${.MAKE.MODE:Mmeta*} !=3D "") > "/usr/src/share/mk/local.sys.mk", line 58: Malformed conditional = (${.MAKE.MODE:Mnofilemon} =3D=3D "") > "/usr/src/share/mk/local.sys.mk", line 76: if-less else > "/usr/src/share/mk/local.sys.mk", line 79: if-less endif > "/usr/src/share/mk/sys.mk", line 476: if-less endif > bmake: fatal errors encountered -- cannot continue Looks like your make is broken. What is the output of "which make"? -Dimitry --Apple-Mail=_DC6A645C-5AF6-4C3F-BE15-B19439F1FFA1 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 iF0EARECAB0WIQR6tGLSzjX8bUI5T82wXqMKLiCWowUCWmhwdwAKCRCwXqMKLiCW o+jaAJ9rlgJMxero4m2fJaggTBequzKB2QCfX2szPFsRMhtv5H7XNBa/x7dK2RQ= =hmvO -----END PGP SIGNATURE----- --Apple-Mail=_DC6A645C-5AF6-4C3F-BE15-B19439F1FFA1-- From owner-freebsd-stable@freebsd.org Wed Jan 24 11:55: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 5BE69ECF5DE for ; Wed, 24 Jan 2018 11:55:26 +0000 (UTC) (envelope-from nimrod@nimrod.is-a-geek.net) Received: from mail-yb0-x229.google.com (mail-yb0-x229.google.com [IPv6:2607:f8b0:4002:c09::229]) (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 DE918858D4 for ; Wed, 24 Jan 2018 11:55:25 +0000 (UTC) (envelope-from nimrod@nimrod.is-a-geek.net) Received: by mail-yb0-x229.google.com with SMTP id v12so1420833ybl.3 for ; Wed, 24 Jan 2018 03:55:25 -0800 (PST) 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=1GPsIUJSPbqhv1hlAWMhnFuqwuhWjevuYmqs8KkSWmA=; b=cfsDDctMMn+oSk6cv7oCktq/RKozZt4XXaLipDtVKFPBsEYyz8S20lpZ/dmiYSrLJw dnuyhEweuYxebvukWCFyDRyZYMK8EiBcfpFjnvo48ao/g2hbhStMhhSev4u62HNZZPrh 0s0wYkGSMD66XlxaSbbW6hbAPXuN+HattAwd7rToKUy8oK10mEoWSwz7lbSUatIjoanp ZzVmB+yV6Uv4NXWAyiOOQNsB2yQ/mcm2jX8PV86VbE9uDBNjSvgwTy5b4Ubhr3mBNleC zxW1DEj1DfptNV9NlY84whYYgRuVHLmCH2pesZ61RxQ4CqPyYl/LIY+0XQN0LqPGLTlM 3wew== 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=1GPsIUJSPbqhv1hlAWMhnFuqwuhWjevuYmqs8KkSWmA=; b=jaBCXJrRkhTQf8fJ4Fbtfa1mp/OxpzszivTXJ4EqIYE+MQwsQZqWjo+0uAJc4D2BXC 5Dw5VfsMswOe7+K6K58FeyhBqs/L/Td6f7F4tec0i6HBdgtryQPGW9MruxB/V9IRXPn+ 1KGKdc9owJFD2do2YPO2BZCpBptF88tkfb+Z6OHnfqLruDw/j5Uua/ejjySzQp042aWF Tr10/KJ0rruhNyAyVrI1I6+Z08ON2WFzNZEoASzYzvtVlJgSqrvVxyRvWcdnOyUl3aIe +Pl9tSZyYfPOks01XaA/3xdXpwTAJmnpLW1I5BOmZcNZbX9ndbiFZSnbO9hgYmYe4JpY UyTw== X-Gm-Message-State: AKwxyte+RrlvaulRFSaMHf09Ge3K0WOAzbacka460rrdtbdKOdyn5VIu eAx6jE/1dJgoVwvmHLgJ/C+PBT10rUzmv5nShTXszTmc X-Google-Smtp-Source: AH8x224TRvGvyWkCpl2esAvQ/CmQkH+alAAPdWFDk+Sz8mKZd8YOSD8NqDBo4Qkc4DPGtQ4K5SCFTlVV5XykWXXRoE4= X-Received: by 10.37.136.14 with SMTP id c14mr4767895ybl.177.1516794924852; Wed, 24 Jan 2018 03:55:24 -0800 (PST) MIME-Version: 1.0 References: <8e842dec-ade7-37d1-6bd8-856ea1a827ca@sentex.net> <3b625072-dfb3-6b4f-494d-7fe1b2fa554c@ingresso.co.uk> <2c6ce4dd-f43c-7c40-abc2-732d6f8996ec@sentex.net> <795dbb79-3c18-d967-98b9-5d09a740dbfe@sentex.net> <9b769e4e-b098-b294-0bce-8bb1c42e8a59@rootautomation.com> In-Reply-To: From: Nimrod Levy Date: Wed, 24 Jan 2018 11:55:14 +0000 Message-ID: Subject: Re: Ryzen issues on FreeBSD ? To: Nimrod Levy Cc: freebsd-stable@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: Wed, 24 Jan 2018 11:55:26 -0000 Changing the memory speed from 2400 to 2133 in the BIOS has given me 4.5 days of uptime so far. The memory is supposed to be 2400. I'm still confused, but I'll accept the result On Fri, Jan 19, 2018 at 4:02 PM Nimrod Levy wrote: > I can try lowering my memory clock and see what happens. I'm a little > skeptical because I have been able to run memtest with no errors for some > time. I'm glad to give anything a try... > > > On Fri, Jan 19, 2018 at 3:49 PM Mike Tancsa wrote: > >> On 1/19/2018 3:23 PM, Ryan Root wrote: >> > This looks like the QVL list for your MB -> >> > >> http://download.gigabyte.us/FileList/Memory/mb_memory_ga-ax370-Gaming5.pdf >> >> Its an Asus MB, but the memory I have is in the above PDF list >> >> I dont see CT16G4DFD824A, but I do see other crucial products with >> slower clock speeds. Right now I do have it set to 2133 where as it was >> 2400 before. >> >> ---Mike >> >> >> > >> > >> > On 1/19/2018 12:13 PM, Mike Tancsa wrote: >> >> Drag :( I have mine disabled as well as lowering the RAM freq to 2100 >> >> from 2400. For me the hangs are infrequent. Its only been a day and a >> >> half, so not sure if its gone or I have been "lucky"... Either ways, >> >> this platform feels way too fragile to deploy on anything :( >> >> >> >> ---Mike >> >> >> >> On 1/19/2018 3:08 PM, Nimrod Levy wrote: >> >>> Looks like disabling the C- states in the bios didn't change >> anything. >> >>> >> >>> On Wed, Jan 17, 2018 at 9:22 PM Nimrod Levy > >>> > wrote: >> >>> >> >>> That looks promising. I just found that seeing in the bios and >> >>> disabled it. I'll see how it runs. >> >>> >> >>> Thanks >> >>> >> >>> >> >>> On Wed, Jan 17, 2018, 18:38 Don Lewis > >>> > wrote: >> >>> >> >>> On 17 Jan, Nimrod Levy wrote: >> >>> > I'm running 11-STABLE from 12/9. amdtemp works for me. It >> >>> also has the >> >>> > systl indicating that it it has the shared page fix. I'm >> >>> pretty sure I've >> >>> > seen the lockups since then. I'll update to the latest >> STABLE >> >>> and see >> >>> > what happens. >> >>> > >> >>> > One weird thing about my experience is that if I keep >> >>> something running >> >>> > continuously like the distributed.net < >> http://distributed.net> >> >>> client on 6 of 12 possible threads, >> >>> > it keeps the system up for MUCH longer than without. This >> is >> >>> a home server >> >>> > and very lightly loaded (one could argue insanely >> overpowered >> >>> for the use >> >>> > case). >> >>> >> >>> This sounds like the problem with the deep Cx states that has >> been >> >>> reported by numerous Linux users. I think some motherboard >> >>> brands are >> >>> more likely to have the problem. See: >> >>> >> http://forum.asrock.com/forum_posts.asp?TID=5963&title=taichi-x370-with-ubuntu-idle-lock-ups-idle-freeze >> >>> >> >>> -- >> >>> >> >>> -- >> >>> Nimrod >> >>> >> >>> >> >>> >> >>> -- >> >>> >> >>> -- >> >>> Nimrod >> >>> >> >> >> > >> > >> > _______________________________________________ >> > 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" >> > >> > >> >> >> -- >> ------------------- >> Mike Tancsa, tel +1 519 651 3400 <(519)%20651-3400> >> Sentex Communications, mike@sentex.net >> Providing Internet services since 1994 www.sentex.net >> Cambridge, Ontario Canada http://www.tancsa.com/ >> _______________________________________________ >> 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 Wed Jan 24 12:03: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 C4528ED0301 for ; Wed, 24 Jan 2018 12:03:03 +0000 (UTC) (envelope-from michaelp@bsquare.com) Received: from NAM02-BL2-obe.outbound.protection.outlook.com (mail-bl2nam02on0109.outbound.protection.outlook.com [104.47.38.109]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (Client CN "mail.protection.outlook.com", Issuer "Microsoft IT TLS CA 4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 41BD9860B5 for ; Wed, 24 Jan 2018 12:03:02 +0000 (UTC) (envelope-from michaelp@bsquare.com) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=BsquareO365.onmicrosoft.com; s=selector1-bsquare-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=K2r0F+pooPWJGecbD4yLXdM9MYPq+o9aAZdpPwi7vz8=; b=RMB2mquSjngiXFK0w8dN0bhPwk+utC9gcFah1IJ+DJTidFv/8lhogY9VU2UhUyPQ4ay7vgLWc1NoAqUAEPqUyYfDR/ut6rfOhqXHWr3u35jXJd4FgZRrorlNSrK00T2BDRqiLSdIjgDpAtiCZOixgujzuONy9MhdpfgPe88nKc8= Received: from [10.150.16.65] (82.33.218.74) by CY4PR1301MB2021.namprd13.prod.outlook.com (10.171.223.155) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.20.444.5; Wed, 24 Jan 2018 12:03:01 +0000 Subject: Re: Ryzen issues on FreeBSD ? To: freebsd-stable@freebsd.org References: <8e842dec-ade7-37d1-6bd8-856ea1a827ca@sentex.net> <3b625072-dfb3-6b4f-494d-7fe1b2fa554c@ingresso.co.uk> <2c6ce4dd-f43c-7c40-abc2-732d6f8996ec@sentex.net> <795dbb79-3c18-d967-98b9-5d09a740dbfe@sentex.net> <9b769e4e-b098-b294-0bce-8bb1c42e8a59@rootautomation.com> From: Mike Pumford Message-ID: <508a8c83-a449-3c5d-c3bf-b308d91c80c0@bsquare.com> Date: Wed, 24 Jan 2018 12:02:54 +0000 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.5.2 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-Originating-IP: [82.33.218.74] X-ClientProxiedBy: DB6P192CA0008.EURP192.PROD.OUTLOOK.COM (10.171.111.18) To CY4PR1301MB2021.namprd13.prod.outlook.com (10.171.223.155) X-MS-PublicTrafficType: Email X-MS-Office365-Filtering-Correlation-Id: 451a50c6-9116-4331-0cbe-08d563226ae2 X-Microsoft-Antispam: UriScan:; BCL:0; PCL:0; RULEID:(7020095)(4652020)(7021125)(4534165)(7022125)(4603075)(4627221)(201702281549075)(7048125)(7024125)(7027125)(7028125)(7023125)(5600026)(4604075)(2017052603307)(7153060)(7193020); SRVR:CY4PR1301MB2021; X-Microsoft-Exchange-Diagnostics: 1; CY4PR1301MB2021; 3:HLbIUkFXzs2l3Q6iCmnaCsuOh+isz7wz26qEoxCuVnsAKD934mF900zJcZJ35ypEu+rRskOaGHDup+MdSgsVlB8J0irfW6K4VD/sKNa/lfX2RuDBOHlwlMNC6WGQwlpAYAo1RXPlIUvfd/qciZ3uKSXjCs0mhpv3XQaWZ+fB/3ZELPihuvN/s8bH2oteugpjT6aVEdxTMYUKMLKmBG1kZp24m695QMOuqM9H3IpnZHNYZfz/k91KVVQtXdFybl01; 25:B1VcqhHeUpeqB3Tnb0N7+yVvPRsWVpmG6aVsP9npv8dcirvKT7ogQ7t7I+SMDY6+nJn1eTEkaRxHbnhennN+vto7a7c0kMnZhIKhLL6NPDfHeOtd6FO/eoJ97LNsPTFQ0JJ0dS6ALYXNAMMbPBXdDKCd1G9NZIGiuWOCTMot0MzXjm2iwkt1YJN2LGnAcRQ9+NwbM/5kcfv0+TVNnyywBeXaMGHJOAeg6D4COwSQwMiMNPqd5+tT9ny34ZZK9pRYO36a89BWK3G4Er9K78i4dxUz3Sl/NZ7l5Rzh7umyThhX6BT7KFbKwTZC/DoJhhQMiZ1yl9dl84eLlEMGIC+O/A==; 31:gQ4ng0u3+F+ZhCz5zpehHuSOt1LRw0hZnAN+zOTbbZpmToxeps/etYkgBNgNUHyvmwm+lkmbBvxOxPclMZXlSE/CzKyNPzGVvAp91Ho5wmCMMT5AyIgKla5o7VJl5n4jKMD9folys1Bai9Sk69kMmrv0Lt+WYOhpcHT4oaLlUZ343U1c+AhOaLZXcOuERTT8y9T2tT+28TI31RPblc+Od6oKsCoCG8XPfjft70IR7DA= X-MS-TrafficTypeDiagnostic: CY4PR1301MB2021: X-Microsoft-Antispam-PRVS: X-Exchange-Antispam-Report-Test: UriScan:; X-Exchange-Antispam-Report-CFA-Test: BCL:0; PCL:0; RULEID:(6040501)(2401047)(8121501046)(5005006)(93006095)(93001095)(10201501046)(3231046)(2400081)(944501161)(3002001)(6041288)(20161123564045)(20161123562045)(20161123560045)(20161123558120)(2016111802025)(6072148)(6043046)(201708071742011); SRVR:CY4PR1301MB2021; BCL:0; PCL:0; RULEID:; SRVR:CY4PR1301MB2021; X-Microsoft-Exchange-Diagnostics: 1; CY4PR1301MB2021; 4:QdtqPJT0QemsHBTZVonkGnOZI2ukmPO0NxNwqdDQK+J4t2dPWBLBaVeMOK/oaHX1qQyGRv6yKZrUPrVCIRPEZPN//g9sIB3gnPHketSAjc7g94yhywQJ2OFYeYj/zT3EkyC5lrY3Ebnyx+AI0XYB+n7wAhjuLOMR89ytojy8gdBdghZNlQnEriLt0NqaKtrZDeZ9AFC/l9qc74W6pauw4ztUcdnvIVTFUUMc1b8y7Aa6U03HqJvMFNL5Oe/Q3diKxjy6Wwa0qyjPHtatRGG7kg== X-Forefront-PRVS: 056297E276 X-Forefront-Antispam-Report: SFV:NSPM; SFS:(10019020)(6049001)(366004)(346002)(39380400002)(376002)(396003)(39840400004)(189003)(199004)(5660300001)(81156014)(76176011)(3846002)(6916009)(105586002)(2950100002)(6666003)(386003)(77096007)(65826007)(81166006)(305945005)(26005)(106356001)(86362001)(31686004)(52116002)(47776003)(97736004)(68736007)(53546011)(2351001)(7736002)(65956001)(66066001)(65806001)(67846002)(8676002)(6116002)(64126003)(478600001)(8936002)(6486002)(230700001)(90366009)(16576012)(316002)(15974865002)(229853002)(2906002)(58126008)(16526018)(2361001)(2486003)(93886005)(3480700004)(53936002)(23676004)(36756003)(6306002)(25786009)(3260700006)(52146003)(50466002)(83506002)(31696002)(6246003)(6346003)(42262002); DIR:OUT; SFP:1102; SCL:1; SRVR:CY4PR1301MB2021; H:[10.150.16.65]; FPR:; SPF:None; PTR:InfoNoRecords; MX:1; A:1; LANG:en; Received-SPF: None (protection.outlook.com: bsquare.com does not designate permitted sender hosts) Authentication-Results: spf=none (sender IP is ) smtp.mailfrom=michaelp@bsquare.com; X-Microsoft-Exchange-Diagnostics: =?utf-8?B?MTtDWTRQUjEzMDFNQjIwMjE7MjM6UUdFRlZiME40WncydW5zYk5jQXZXVjZX?= =?utf-8?B?dkQ2WmVyL21KdmhVSlo2QmxvbnNuY3BKVFJiUHFhZXZFbzExbW82WE1DUExI?= =?utf-8?B?OE5XaWxTby9KczBWRk1uZUNSbnE5TUdER244VWZveERnd2N0YTZUcERpeHpr?= =?utf-8?B?bisza0paOTBUN05EajZoa1d0cGJaVWROTTAzQ1VDMGpJandscENTdi9OZjlM?= =?utf-8?B?T1o5SjAvK04yUklvektVa3lRc0FPazRXKzh2Z1JzNEx2SzRaalZ1TUUvV01C?= =?utf-8?B?RkxobVo2Ky8wVGZ6Tk9zZDNEWitxNFI0bmMxZHZRV2lydkZicXJsWFNVNUZ0?= =?utf-8?B?NEYwSXJCL0RQbDJ4WHVsVll4NmlBMnp6clJZWjJtQ0o4ZUh1VGhhVlNuYzln?= =?utf-8?B?SU51bEJoYk9TazE4cCtaUng1T1VEN04vWDNZdWhqcEo0Z3FodlplOSs3bUhF?= =?utf-8?B?VDR2b3Y4bVArZXJjamtlRVRlcFBubzc1YUpZcGRjQW9USzZWYWRpb1E3UXlD?= =?utf-8?B?SHBkbWVSZkpyU0tGZDRqaDN4WVZ1OWJDQ2YwNWx5VGFHcVZ1U0ZEVGtWdGRu?= =?utf-8?B?N1FXaWQ2VVFhMDhnUGVHR0JxNkwrNlZaWk5aeEkzdmg0WXdZMnIxSzRKektI?= =?utf-8?B?VUNNaTh4N3orM2lIcUJaaE1Pd2l0clY4Vm5rcEZ3QUR1M1BqUUlsb05NNThF?= =?utf-8?B?dWZ5bUoxWjE2NG9mVUVGbklyc0xYZU03dkpUNUpWR2NocWs0TjdtWlp5TU9H?= =?utf-8?B?MkNiTGoyVGJyRjR4TDF2cFNnZ0lrZllVaHlseXJnb04zVUIvY2pWQ2RMb0dO?= =?utf-8?B?a0sxMnM3YmJPVGoyVEVybnJQNVV1S1U1RjlrSzcwdWVKQm55djJ0MWtwOEln?= =?utf-8?B?NWR1OExWdjZhSk44dXpOcVlhZGFpSzYzaVNHRndza1hBT1JNaXNwaXZOaEVx?= =?utf-8?B?ZlBiN3ZKMlB0WlIyLzhLaGFpOUNUVERWS0R6dDNkVHE4SWRyZXcrek11d1Bo?= =?utf-8?B?Z0lIbDlKa1VvRnU1NnY2VFkxcHlYbU1PNTlrVU1XdnJEVGNBUDhzVEk5TlJX?= =?utf-8?B?dVhKanRiL1gzcU1jYVp5U1RkeVdqQW9JWnBtU3VOS0VQd0YrTWI5eWdUYmkz?= =?utf-8?B?bStmWmZoMzNnbS9icHZJbzdVRVhWL1FqSXdQbVdPbWx1NlVOS0w2dUFtZ29M?= =?utf-8?B?dzhGVG5sUkR3WHJuRCtDVER0NEJuS2FXblNHRzJ2MHo5OEJOaHViVHIwekJu?= =?utf-8?B?ZlpxWHBJNys0ZHhwV3BENkZpWFRyZlhma3c2Y0VBWG5hZ1FaWGg3d0E1RjJo?= =?utf-8?B?a2JaRmtROEN2eWV5NDRpWUZ6bE91OUZ6WWs5clpxVkNHMHJ0NDBKR3cvNXdT?= =?utf-8?B?QktmSmZWZGZ5WGQzeXI1SEtsSlJTdGZydXJ3OFJ2NVZndlI5YTd2NXRtam1S?= =?utf-8?B?S2hZYXEweE5iMEQ4Tkg2eU95NUhSK0VXQVdqMVlEMVpDekxoYm0wMUl0bHox?= =?utf-8?B?ZldsYkhLMzJ1cmZ3OW55aG94d3R5UHErRGwzVE04RFh3cWlmV0VpZUNUZi9p?= =?utf-8?B?bzBZQnE0TGJxRXNFd3p1aEl3ZFNjSTR0aDhnM3E5WFpudnZiZ1c4SUZpMGhI?= =?utf-8?B?Snc5T1J4bjNjeHA3Z0cwalFOZnc4Z1pETk9mTjQrUEFFWEVPY3ZqRzZLaVhM?= =?utf-8?B?QXh2bUVrMHNjVm9kSDhSK3gveDYwM3dzeVRxWnkxOXpzci8vUEMraXRXWlhq?= =?utf-8?B?aXFpWTJNWHducko4WlZYWnhkZjJPOWFEbWw0cTNvZVh4RUx6NjJkYVlRaWJl?= =?utf-8?B?QUVHbXhYODNPMVkzL1AzNWN4WVR1ekRMdk40T1FTeWsxRVVYTWJiSURKVWsw?= =?utf-8?B?aXJWRTFjZjYyMFExeU1ZRDhVcHBXSW1nN3luY0piOXNkRnQzWkcvV3JlMEVO?= =?utf-8?B?cHlldjlnM1dackJoU0ZIQ2tEYnlhcXpzWGNWZ1BUMk9QcCtvS0YrdTk4LzFt?= =?utf-8?B?RmsvbFUwUjAxNW1UM05MdnZRWWdiNGF0cENSQkhPd0ZlRVNDYnROazEzUU0w?= =?utf-8?B?TjJGeDZjUEE2SUova0VZSEFxS1FkZUNyN2Q2OWFYSE1mWnZsUGN3WU5tSDZF?= =?utf-8?B?RzQrUT09?= X-Microsoft-Exchange-Diagnostics: 1; CY4PR1301MB2021; 6:olgalcd9fmb62LI6Bl1Ab1nnXduM2QtR3AOYK7NDiqcQ/Hei6DusmrVBdhoOPoLaIz2r3ktgWJg9s7T+V3cFzIGXdXcmShskAl0nMS2mez+t56R5D+ieqjSFKFB+yDE3mMyKKy93uqrN77wDPslP0DsbQdSBSVDXVZMe743z4rQ6Hhuc+czzBiG9qhm5DWK5+IEOix8gZiFtHEMBDDJxwcBARcs2pdqhtzD84CqPEpCSB8L+5516OXV4ZY7lHvTtyeUw5X5h4eDEYqobQevX1MRQPwaVTOLMVtyhnIrOaFVGfGgFbo8nZoKFwZOCv9P6vt6h0dv338t7g24gmknMGbLBVUTPnveWXPRkvfqrf0s=; 5:F5pjhjIq7IEnClpSmo3Q5dmE8irmU2Edjeulk5+TKpOUmb6+jOX318CnT9sx3CDy/iI+CPtEp0VxkFsEx5WFMf7ii33fnKQ08jzQKAVObcTmuii8OcSIeyObV5UTGth4ifRKPEK+Hb9LguzMWEwMrsvG2M9rAx2jDHzFhVUxVmo=; 24:vd9coxdCYOXx46HAY+gv3IOYn0uFsI7p5I+EAE1qU1j2BydW6sIv+RPFG7tnd68YwpyWaEa0OtoZL++2R22ybWfsVCwy27II/YoZGCPOFCY=; 7:jR+lLIGJYmDkB4gdXKZf447Auhhi/LG6yjBCZvBOgzLS9J+ajBpMr2VXZZ7ZGZtqPAuUYmO3ZmMudmnWZ7VYy4EmkfWo54MH3c2ZVdbjXBjZMts/+q+Fj41vAw4YUorQrqVajcxlLQVDsFMI/8DyLe/srhMQyK78e5dL6Lbp0idhMcJpJ9jDEtsjvirCK/KUEMEGWnZrt1Uu3B6ECQU4UJeiDzvVPnlE4IKf1sbQjnyRcvaPZPx1hJIBCMySuOMd SpamDiagnosticOutput: 1:99 SpamDiagnosticMetadata: NSPM X-OriginatorOrg: bsquare.com X-MS-Exchange-CrossTenant-OriginalArrivalTime: 24 Jan 2018 12:03:01.1967 (UTC) X-MS-Exchange-CrossTenant-Network-Message-Id: 451a50c6-9116-4331-0cbe-08d563226ae2 X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted X-MS-Exchange-CrossTenant-Id: c078f217-c3b7-46c6-bf76-ff2c451cfe9a X-MS-Exchange-Transport-CrossTenantHeadersStamped: CY4PR1301MB2021 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, 24 Jan 2018 12:03:04 -0000 On 24/01/2018 11:55, Nimrod Levy wrote: > Changing the memory speed from 2400 to 2133 in the BIOS has given me 4.5 > days of uptime so far. > The memory is supposed to be 2400. > I'm still confused, but I'll accept the result > I've run into this on modern Intel systems as well. The RAM is sold as 2400 but thats actually an overclock profile. If I actually enabled it (despite both board and RAM being qualified for that) the system ends up locking up or crashing as soon as you stress it. Go back to the standard DDR profile advertised by the RAM and it is totally stable. Mike -- Mike Pumford | Senior Software Engineer T: +44 (0) 1225 710635 BSQUARE - The business of IoT www.bsquare.com From owner-freebsd-stable@freebsd.org Wed Jan 24 12:11:14 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 5B41AED0B02 for ; Wed, 24 Jan 2018 12:11:14 +0000 (UTC) (envelope-from nimrod@nimrod.is-a-geek.net) Received: from mail-yb0-x22e.google.com (mail-yb0-x22e.google.com [IPv6:2607:f8b0:4002:c09::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id EAF2A86853 for ; Wed, 24 Jan 2018 12:11:13 +0000 (UTC) (envelope-from nimrod@nimrod.is-a-geek.net) Received: by mail-yb0-x22e.google.com with SMTP id p83so1435565yba.4 for ; Wed, 24 Jan 2018 04:11:13 -0800 (PST) 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=2hEnJPo3l3hov3szojY/w4ImtihklTuir09GTIIJZUg=; b=be7gIKjrO/wUPHL7yMdMmpmc0m6irxAhFJVPyiwzoMpZtvBYe/aytxm4i10MxvCHkt DPYt9Ee5eWJvopPnjGMoGFh4orC8Ui6SVKoeNu4t+JQM/C4kL7LJXLkTaGyxgizKt7il 2may3OB8Ka7qOzOx486afDN9ZFcskJcopAv63TFp5PAwP8RqZyM4VV/D4oxSix9YaEl9 paSh1vZesrKA3UVpy1cT+ioQ5RBfj68gRiYOYY78GMJGLRWyjs3mq3ukX4UqKHXKDMkO 5qspTC37k9MWCWrvaud3ubwlIWS60Rl+UsPaL3vJIwuQE1XW8iIw3NRcZso+Rbf+EvgR /zeQ== 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=2hEnJPo3l3hov3szojY/w4ImtihklTuir09GTIIJZUg=; b=iHvlD9PvuZ5JUBNnsUPrGssAdJQtwkuvB4mI9v9e7XI09fdyWSEt7TRWchw9ua4YSq +wUB09AGyc9DZSG8Md4QBJrWpm8rPb/rFqtJDFI9UNT+l1lScRMqSrbXLc+thAzDR4Xs BDEs2hFoDh67kWHjGqv94hoiK9cNCjDWQ8z2elYCJtSu8pdExPjyIazWB4KpoZ5vSsiQ w8gWYsac5TMEM6zhsHvbA/drRy+1gG/xahuY73URwqxsYaks7Rsf4d6tSFGgnEFssRju CFeDmNIEMyrtIjmVdCOwno4rgQVQAu/g9GlG60AMY276LgBNbDSbb9IiY6KincBhCOIu 6ehQ== X-Gm-Message-State: AKwxytdIF6IHGifC8G+UaLxghV2PkX/kzu0KjYIjOJJiRbbLrDG8OmoE 7Nxpy+2podRHyaYVlf+/YLlG68NHI4clwv6ls4cRkCMX X-Google-Smtp-Source: AH8x227QA7GB3g9dIRpXYGmi5nOTWzCH1qs/28Ktstrr4iCvWVvjeLafGob65ue5AzDpXjlyr3Nmx1mQptUTiz4g0eA= X-Received: by 10.37.109.8 with SMTP id i8mr4924791ybc.141.1516795872948; Wed, 24 Jan 2018 04:11:12 -0800 (PST) MIME-Version: 1.0 References: <8e842dec-ade7-37d1-6bd8-856ea1a827ca@sentex.net> <3b625072-dfb3-6b4f-494d-7fe1b2fa554c@ingresso.co.uk> <2c6ce4dd-f43c-7c40-abc2-732d6f8996ec@sentex.net> <795dbb79-3c18-d967-98b9-5d09a740dbfe@sentex.net> <9b769e4e-b098-b294-0bce-8bb1c42e8a59@rootautomation.com> <508a8c83-a449-3c5d-c3bf-b308d91c80c0@bsquare.com> In-Reply-To: <508a8c83-a449-3c5d-c3bf-b308d91c80c0@bsquare.com> From: Nimrod Levy Date: Wed, 24 Jan 2018 12:11:02 +0000 Message-ID: Subject: Re: Ryzen issues on FreeBSD ? To: Mike Pumford Cc: freebsd-stable@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: Wed, 24 Jan 2018 12:11:14 -0000 The RAM was detected by the MB as 2400. I didn't change it until I set it to the slower speed. On Wed, Jan 24, 2018 at 7:06 AM Mike Pumford wrote: > On 24/01/2018 11:55, Nimrod Levy wrote: > > Changing the memory speed from 2400 to 2133 in the BIOS has given me 4.5 > > days of uptime so far. > > The memory is supposed to be 2400. > > I'm still confused, but I'll accept the result > > > I've run into this on modern Intel systems as well. The RAM is sold as > 2400 but thats actually an overclock profile. If I actually enabled it > (despite both board and RAM being qualified for that) the system ends up > locking up or crashing as soon as you stress it. Go back to the standard > DDR profile advertised by the RAM and it is totally stable. > > Mike > -- > Mike Pumford | Senior Software Engineer > > T: +44 (0) 1225 710635 <+44%201225%20710635> > > BSQUARE - The business of IoT > > www.bsquare.com > _______________________________________________ > 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 From owner-freebsd-stable@freebsd.org Wed Jan 24 12: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 85AEDED16FF for ; Wed, 24 Jan 2018 12:24:56 +0000 (UTC) (envelope-from michaelp@bsquare.com) Received: from NAM01-BN3-obe.outbound.protection.outlook.com (mail-bn3nam01on0111.outbound.protection.outlook.com [104.47.33.111]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (Client CN "mail.protection.outlook.com", Issuer "Microsoft IT TLS CA 4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id F044F87079 for ; Wed, 24 Jan 2018 12:24:55 +0000 (UTC) (envelope-from michaelp@bsquare.com) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=BsquareO365.onmicrosoft.com; s=selector1-bsquare-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=oH5s32Yi0Kx7uHjo/tfdJgyt1dYYO/bp99hMT5bEHnQ=; b=PArrOsOzM2iq7SRXj02bCOxbBwVuReGbYZWf+8FqpKTT2LdoFHCyuUBTzWuFdNpw6VSnq/OlPJHZ6boJwywVHOtEeR6v86mI4AtqXFFFqVBh0qppA28yrHE7rJWHkoFV2ifirC+T4Yr5pM1Da5Shrni+qNOHkbpx43B/qfsuIdI= Received: from [10.150.16.65] (82.33.218.74) by CY4PR1301MB2021.namprd13.prod.outlook.com (10.171.223.155) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.20.444.5; Wed, 24 Jan 2018 12:24:54 +0000 Subject: Re: Ryzen issues on FreeBSD ? To: freebsd-stable@freebsd.org References: <8e842dec-ade7-37d1-6bd8-856ea1a827ca@sentex.net> <3b625072-dfb3-6b4f-494d-7fe1b2fa554c@ingresso.co.uk> <2c6ce4dd-f43c-7c40-abc2-732d6f8996ec@sentex.net> <795dbb79-3c18-d967-98b9-5d09a740dbfe@sentex.net> <9b769e4e-b098-b294-0bce-8bb1c42e8a59@rootautomation.com> <508a8c83-a449-3c5d-c3bf-b308d91c80c0@bsquare.com> From: Mike Pumford Message-ID: Date: Wed, 24 Jan 2018 12:24:48 +0000 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.5.2 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-GB Content-Transfer-Encoding: 8bit X-Originating-IP: [82.33.218.74] X-ClientProxiedBy: DB6PR07CA0173.eurprd07.prod.outlook.com (10.166.153.155) To CY4PR1301MB2021.namprd13.prod.outlook.com (10.171.223.155) X-MS-PublicTrafficType: Email X-MS-Office365-Filtering-Correlation-Id: be9522da-4a23-463a-d997-08d563257995 X-Microsoft-Antispam: UriScan:; BCL:0; PCL:0; RULEID:(7020095)(4652020)(7021125)(4534165)(7022125)(4603075)(4627221)(201702281549075)(7048125)(7024125)(7027125)(7028125)(7023125)(5600026)(4604075)(2017052603307)(7153060)(7193020); SRVR:CY4PR1301MB2021; X-Microsoft-Exchange-Diagnostics: 1; CY4PR1301MB2021; 3:oNY8NbbAQIvGzptfEsUtfnAHTZ8OiQJf1rWgThV94zr26fMkgROfMbUzLtFIgP9sxIgMEcAA326rCpHhr9to5pArvzw4ZDG4/WkIX7TuWOOrRUUi8mgwrh+OdXB9UugtntqfFttJtjkLHNQmJHw7QxUxPNG9wQQWsQrx39J7CCLnn9dxARJZyfqZOBhnZBCg0ae9Y3WAhuHTOsUKntKwFXxhq/u3Po4D+KSYtsfy3HretlsFFGDkBnyw8gJ6XV7D; 25:j9/rQxXkaW6XqeB/tTZSBz5Jntpw4rdg9S8Bfjve4T5RLfMy2U0bmrq0OGRfi2lM312YF6mjnVPrmKgpC54MrATt3HyPY8aW2E2DKtjIq65eduol6EKO5nyeUaCE/+BbLV1pmtZ8AEvdk9kl88xDSyrKejA+t802uNUvfuinec8NJQ1Vgpp5/3NLamOjMdaM4BOPjQOH60u/AufXN3zoiY97VNDgGg50ZP82ekP8ZMDM8xIR3NAWkD1JPdQ8iAVNm4Dy8j6/s7vD/X6EFkP07clXTKJCDi35jkByI4X87+1Cj5Wj8c5B2E+jC88qSkw+wOtnsuf91mPZZ7yioetbQQ==; 31:lfY0Ij1eSl6pp1nc+7TLhWJpy0ZhDMDiu9mPh/2LoolCfUrgwMukGF4HlfmqvWDWD2Q/1utvDvmcJTV1l53jp7pN9dHeShXrae3zNaiKwgCFzEZmIs7Q0yYJ6ukPv/FmhY/5eWMGe1UymaPD2YkHA/r2TvB2KuWG300HTJv0Fl1SuyM5Y/3xj0ZyC2j23fFAl+1Loz4c0SqGQXRDgOMB1oNCyDYVdwqGIQ4iwPF1Wt0= X-MS-TrafficTypeDiagnostic: CY4PR1301MB2021: X-Microsoft-Antispam-PRVS: X-Exchange-Antispam-Report-Test: UriScan:; X-Exchange-Antispam-Report-CFA-Test: BCL:0; PCL:0; RULEID:(6040501)(2401047)(8121501046)(5005006)(93006095)(93001095)(10201501046)(3231046)(2400081)(944501161)(3002001)(6041288)(20161123564045)(20161123562045)(20161123560045)(20161123558120)(2016111802025)(6072148)(6043046)(201708071742011); SRVR:CY4PR1301MB2021; BCL:0; PCL:0; RULEID:; SRVR:CY4PR1301MB2021; X-Microsoft-Exchange-Diagnostics: 1; CY4PR1301MB2021; 4:jhb56+VzwMTbosvoloxSVH8SRAvvorGbxPwfF5PNO1msJ6aR18LcSmBtaFrEQ8Tx97T6FEYLOQYzqxQw82jLrZlyohQVn//r207va/2wb2D7/e7jTn9HDFhktAOx+RZSmyHce7ndKKwVWkRrvlCyC9vSkUyWeGHzt06J/QriRcUjEu0N/kWIKiKQ/57Vq9q+r3T10l/yUKSEVK47fVzvtdZ0mtmtG5uMIjIpvkYCUYw+D0JKd3xLA1Vl7N2AivdZ+heppDnw77VKfk0Bg87+4w== X-Forefront-PRVS: 056297E276 X-Forefront-Antispam-Report: SFV:NSPM; SFS:(10019020)(6049001)(346002)(39850400004)(366004)(396003)(39380400002)(376002)(189003)(199004)(5660300001)(81156014)(76176011)(3846002)(6916009)(105586002)(2950100002)(6666003)(386003)(77096007)(65826007)(81166006)(305945005)(26005)(106356001)(86362001)(31686004)(52116002)(47776003)(97736004)(68736007)(53546011)(2351001)(7736002)(65806001)(66066001)(65956001)(67846002)(8676002)(6116002)(64126003)(478600001)(8936002)(6486002)(90366009)(16576012)(316002)(15974865002)(229853002)(2906002)(58126008)(16526018)(2486003)(59450400001)(2361001)(93886005)(3480700004)(53936002)(36756003)(23676004)(6306002)(3260700006)(52146003)(25786009)(50466002)(83506002)(31696002)(6246003)(6346003)(2870700001)(42262002); DIR:OUT; SFP:1102; SCL:1; SRVR:CY4PR1301MB2021; H:[10.150.16.65]; FPR:; SPF:None; PTR:InfoNoRecords; MX:1; A:1; LANG:en; Received-SPF: None (protection.outlook.com: bsquare.com does not designate permitted sender hosts) Authentication-Results: spf=none (sender IP is ) smtp.mailfrom=michaelp@bsquare.com; X-Microsoft-Exchange-Diagnostics: =?utf-8?B?MTtDWTRQUjEzMDFNQjIwMjE7MjM6MWtvMkxDeGViS01lZ0xhQkxRQ0p0ZlJO?= =?utf-8?B?b0k3WU5FNitmbUNDRURBTWdUNWgxTVU5UG90czY1R0ZGMTlXK0ZvTUdSUGIr?= =?utf-8?B?amxaa3QrMnBvOWRVUnhhY2hkc1VSUXoybmFqRVVNa3ZMZEhzakRaaDQvelhG?= =?utf-8?B?U0FVRElWdG5GbHlnZU14akxtUnEvT29JTHl1SGtaUjRxVWtBdGhGY0hKdzFX?= =?utf-8?B?eGVrMlprT2Y3ZUlsS0JiM05kKzdUL2hSU2kyYkVWenhsYXU4SUtsTW11ZWpC?= =?utf-8?B?emVua2RzbzMrQkhaMUhWeWlJbURnLzFrd3IwczQySC9VNmtMbDZOYTduZjV2?= =?utf-8?B?OTgyTlZWWXpjd3o4V005SlYzUVVESVJKWHROdVZDS1VPN3ZqWURqdVdGczJa?= =?utf-8?B?RFN0SEpxKzMvL3BEQlFONUIzNjY1UHMrNnM0SHcrZzFvNUZtM0tCQ3dsU2ZC?= =?utf-8?B?blorUjBiUUwxQ2t0d0NTazRROGNtSHZEVDhaTW8ybEVOUXg1Vlo0L1NPenNi?= =?utf-8?B?K1A1dVJaYnBlaDVzenN6UFlIS00xamZYUHU1bmJrTUUwSVpEMEhVSnNYRG1Q?= =?utf-8?B?UXY1V0ZRUis5dE4wUjU1RjAvYk9jYmVDNGNKVWFyS3pqV1FTWXF4VXZ2Q2JL?= =?utf-8?B?MEJVTTVPZjlkRUxwTzlOVFlQQzBzaWNLWEl2cXhpRVpmU1VwN3pXb1lHTjNq?= =?utf-8?B?VE9mdHlMTGh1WERzNVk1ejY3NkMvNU9FWmsrRGJEdi93ZlZQQ0dCMVlYcWFz?= =?utf-8?B?blBBZlRUbEFMSmdjcXRaWkxUK0ZhZUdhaEYvaUR3dFRzTm4xSDU4WmF1M2dz?= =?utf-8?B?bHNnVmxubDJxWm9BL2FJWmlraWEwYVkrZFh3Si9maDRpUWNjZ0VOa1Q3V2xo?= =?utf-8?B?cDc2NTdISk9maDFGOXdzVWZUbHVEOWJhQ0xkNlRHZVIrZ0RIMlZ2SWkyNnJY?= =?utf-8?B?ZlVRYytyaXcvRVpxYTRheVdNU3AxQ2t2TXBFWDI4TGdTTFFQZGE3MlhsSHo2?= =?utf-8?B?OVRONGNYcTRHRnRuOElkZWhaN0gzd2VBalNueXpaUkpCYmVqZ2poR21JZm9t?= =?utf-8?B?ZXJNS1BVbU9ZTHY1clpVVUl6OFJJRHFOdkpjcU90UHVKVG54YTFKMmp5dHNw?= =?utf-8?B?bkVLdElFdmpTSzdJeDFRQkVkN3VjWi8waW1UL0NDckpLYmFueXZsUGFxZEoz?= =?utf-8?B?Nm1aQ1BHNUNlZDNocDg0NUN6YkowTnk1bmtwcDZXSUpHRVpha2lsREsrMGRZ?= =?utf-8?B?aldEVlg2aG0rWFRUQloxenFvclZxTTFiNHNleW4yNjFtUlN5bkNvcXdBMnhW?= =?utf-8?B?emJJMzFvK0VPbmxlRjl2RmN6czBhV1ZubW9VYndINTJsWmhmTzlCanNwQms2?= =?utf-8?B?cEF6SlFBdVd0Y2pzbThGTEwyVHNKaGdWbnJqR24vTi9FQVFWTlMwb1BWajMx?= =?utf-8?B?eDZZNWZ6TFJNQmdkS3MvVEhMSnZmQnFyZ1VKdGVGaEE2VUw3ZXRVaGFndkNz?= =?utf-8?B?WE9Lbldkb21kSFpFYUhadTJ1c01iWVpPd3hJOWpPUXFyTzkzdFhKMjIwTnB1?= =?utf-8?B?TmV1bVFYVE9PaEdlY0lGVTNETEMzUzdCNWxWYkZQM2RjU2pjVnZUQTVDbEd0?= =?utf-8?B?bnd6VmNQeDJXeGIvVWVROFc4VEQvK0RZL3FieTJrRkw2KzZ2T2RzamlOdXdD?= =?utf-8?B?ajVjbkVxVDdzUHA3azB0aEdjOHhFeEVsaHFxajVIelJOVGNxbjNvbjdZOW5i?= =?utf-8?B?WUtFM2NJYjJYdm00bFR5N3RRZU1aYUZoSTdRYWc5ZUtyRVEwZlNRVzNzN1A3?= =?utf-8?B?UmVaRmVGVThIeGZUL3JwRGJMWElOV0pON0xqelhhcUJJTnlsTlczZFdMQzlp?= =?utf-8?B?eG81K2kxVGh2YXJZZDJyeGxTWGdSR0dDYU9IL3JTS29PeFVMcUhGczgrSnlU?= =?utf-8?B?UFJUSDIva3oyZWZtQ3RHL0dHOU5MbUtmZ3RVcU16c0krY0pEd3FHaTcrK2pO?= =?utf-8?B?bnZWVENrTklWSWcxaU1vdlQzd2VIZUQxdnhXRUJDU3h3ZW9abEwxVzlYTGpK?= =?utf-8?B?Q2RldW9CTGt2c25wY2xxM2RjbHAySkJhN1VQY3dlb2RJWS9XRjlGeTJEbHlm?= =?utf-8?Q?bua9XQWoRHUYXEqG6ZVFkrp5tw32dWDXK/bgMeVvgRZBiM?= X-Microsoft-Exchange-Diagnostics: 1; CY4PR1301MB2021; 6:f8+p9xSrwLeVdWxU9GJ9lt/VPTViS+3S3SXrFQmZ3viyN8cmxCG0CTB7srfPRXZ12VWQkdeQbjVN6c1pQVvrnzHTvRlAtL7njxNXTobLpKZQtOFA4JbSmxgYxrrGbAA2OFUaxGSpU3kkUKqIAss71JBLwH2xOcVBsZnWIYjONZf0cf4Gt89iSfD6GW2uMaTby9gk/98Ws9GaPcSKk9YrttXWF/YdJf7Qj4SsfBGTTApKxd9VkgjqgQqnNb6lL+e/5UuVQDmqhu9R92W8u6IVy3AK0c+pm7gC0JtRTxOx/YJFs/wT0xOTZNDrA7aM0Ztf4riM+JhXqKBXsrGcCC4+7Q9D42JYbNRZQQea3DkuW8I=; 5:BhG2fbJoE2RyymwRjBEy5x2c2SJoCuKnRzb7N3GEi/jxi+5E/ubAYebABIVBXGnMHix3KZ2DJy+iPsfeBA1xOKYFw4qU4Q5MZ5D9VX8ZEAoZpS3cLNZ3M9OG6XWHaKq3Sksj2Mx30/Ep5cOfdI1mpORjz2hwA2qwnnsefFTPCzo=; 24:QcQT6srZUgoyVWj9qUNoko/dKiaNo8bOTk1ncTZr/B5G0iqS+0IfIFHwiNBDA+DajgQsNAdi+CI8fJgYGO9H3ppzu1SJ1zErZWWULThfTXc=; 7:9sXnCfL9LHuMO1Sbs5StvOKNPxXQ3uE2XbjaiV4HZEyus+iWYFQ4Azta/XCSvkPFMPKF8rAt4tAr6ptULsXroeSfS9vohO0H+QI1IBp01qzm36sclmUkenKyMQr0Pq+8M4aL8ASEgluro9ecjkNwcVpLrz5M8RwpHrpou/8h19H2vAgWJkS0a2gFMKkXNcnGKaxORo8R7gyfzwgGZoccc7IURVNEKR3hzrPEihrpP2bFW87nUjdi2FhEHgkCsPVH SpamDiagnosticOutput: 1:99 SpamDiagnosticMetadata: NSPM X-OriginatorOrg: bsquare.com X-MS-Exchange-CrossTenant-OriginalArrivalTime: 24 Jan 2018 12:24:54.3065 (UTC) X-MS-Exchange-CrossTenant-Network-Message-Id: be9522da-4a23-463a-d997-08d563257995 X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted X-MS-Exchange-CrossTenant-Id: c078f217-c3b7-46c6-bf76-ff2c451cfe9a X-MS-Exchange-Transport-CrossTenantHeadersStamped: CY4PR1301MB2021 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, 24 Jan 2018 12:24:56 -0000 On 24/01/2018 12:11, Nimrod Levy wrote: > The RAM was detected by the MB as 2400.  I didn't change it until I set > it to the slower speed. > I guess the Intel motherboards I have are more conservative then. They default to the standard RAM profile (slower than what it is sold as) and you have to explicitly enable the faster profiles (which do also come from data read from RAM). So it seems like your BIOS vendor is picking the faster profile as a default. I've got a couple of intel systems like this (one windows and one BSD) and neither ran stable with the faster RAM profiles. From what I read at the time 2133 is the official upper limit of the DDR4 standard. Any speed faster than that is an overclock profile. Mike -- Mike Pumford | Senior Software Engineer T: +44 (0) 1225 710635 BSQUARE - The business of IoT www.bsquare.com From owner-freebsd-stable@freebsd.org Wed Jan 24 13:21:52 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 DEE17ED3B7B for ; Wed, 24 Jan 2018 13:21:51 +0000 (UTC) (envelope-from nimrod@nimrod.is-a-geek.net) Received: from mail-yb0-x22a.google.com (mail-yb0-x22a.google.com [IPv6:2607:f8b0:4002:c09::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 7D18A88ECB for ; Wed, 24 Jan 2018 13:21:51 +0000 (UTC) (envelope-from nimrod@nimrod.is-a-geek.net) Received: by mail-yb0-x22a.google.com with SMTP id k127so1499680ybc.12 for ; Wed, 24 Jan 2018 05:21:51 -0800 (PST) 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=KgReq6wxGj9mJKCTB1S8vJuoWBpJTewxhShaeFGB2y4=; b=bNcDDXXJnW/aKJTChPJx8RAiTxntecJL1dhS/NddahWunqdb3Bi8z1x0xbY1vfshDZ GdQp7IhlijSr1JGEyXSzMlaJFnPK0qR0hNocZN0DbxXAyTjhRoUWKwcq9sMcAuHmaCQ+ yjdXMffzAYA4Y5Y/foR95X9r6aqjEJ2h9n0TO5mOw6R1hcCEvNlJ10Mql7LqJglqRk3N rvqTeIqw8EWcBudY5/EB5SDfsATXdwj8f8exhK3Dc3yNNzFrhkcpEfyCMbxpaTbLVoQx yFuYH7CSdbJSW3qvYMt6Qk3Nd50DEtfN13UFiAckAoqG3lM4ANkgtkVUPfUjwWgvsbB3 2Pig== 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=KgReq6wxGj9mJKCTB1S8vJuoWBpJTewxhShaeFGB2y4=; b=OjsXXAbWhMg7VbeapFgyvW8hXebi85KZ+Z+7M+nziOgtJ6+dbIRfsJaaCMjQH4F1jy OaKPmkv0YEgEYvEpsm4WuUBlUrwvqFoFUX6LqyTwKN6/4QM97OlcP0OulNQo9EEIsmOI FKwV7E/tndgbfWck1jZSxXCr0d4yCvXYIgcLsKiDxa4kk57bk/CSjSwa5ej2cnhCKl2y GOqDVzM/IqmJziCeFCtDJhZuKkAtJmbligH/7fL+IAef8Eo6EqD+Z1RRxXUETvAbmWPz 5uDP8KjUIF/EeIz2ixpza4k8BziQRf457iOODcKEWlKxBTC9XNxYPfVZV1YN1iBcK6ta L6xQ== X-Gm-Message-State: AKwxyteUUglI4L5pzHwvdvwaQ5wMGa3m2PWOPwU6d70qiw5DvY5Eb1IG gOoAo9aMS/VEM6stYxtoudQam99fOJxMjRulGpmcSmO4 X-Google-Smtp-Source: AH8x224QUJoHb0w0ipN+iSrFe+++FfV8Ovrrg1nF3IOexwVFTgSRCgNhQYUC0/ABqkQj7p6Tw00EZtiS22+leFq026g= X-Received: by 10.37.147.144 with SMTP id a16mr5172388ybm.137.1516800110268; Wed, 24 Jan 2018 05:21:50 -0800 (PST) MIME-Version: 1.0 References: <8e842dec-ade7-37d1-6bd8-856ea1a827ca@sentex.net> <3b625072-dfb3-6b4f-494d-7fe1b2fa554c@ingresso.co.uk> <2c6ce4dd-f43c-7c40-abc2-732d6f8996ec@sentex.net> <795dbb79-3c18-d967-98b9-5d09a740dbfe@sentex.net> <9b769e4e-b098-b294-0bce-8bb1c42e8a59@rootautomation.com> <508a8c83-a449-3c5d-c3bf-b308d91c80c0@bsquare.com> In-Reply-To: From: Nimrod Levy Date: Wed, 24 Jan 2018 13:21:39 +0000 Message-ID: Subject: Re: Ryzen issues on FreeBSD ? To: Mike Pumford Cc: freebsd-stable@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: Wed, 24 Jan 2018 13:21:52 -0000 If my google-fu is any good today, DDR3 maxes out at 2133. DDR4 seems to go up to 3200[1]. The motherboard claims to support all speeds. This RAM is supposed to be DDR4-2400, but if it keeps things happy, I'll run it at 2133. [1] https://www.kingston.com/us/memory/ddr4 On Wed, Jan 24, 2018 at 7:28 AM Mike Pumford wrote: > On 24/01/2018 12:11, Nimrod Levy wrote: > > The RAM was detected by the MB as 2400. I didn't change it until I set > > it to the slower speed. > > > I guess the Intel motherboards I have are more conservative then. They > default to the standard RAM profile (slower than what it is sold as) and > you have to explicitly enable the faster profiles (which do also come > from data read from RAM). So it seems like your BIOS vendor is picking > the faster profile as a default. > > I've got a couple of intel systems like this (one windows and one BSD) > and neither ran stable with the faster RAM profiles. > > From what I read at the time 2133 is the official upper limit of the > DDR4 standard. Any speed faster than that is an overclock profile. > > Mike > > -- > Mike Pumford | Senior Software Engineer > > T: +44 (0) 1225 710635 <+44%201225%20710635> > > BSQUARE - The business of IoT > > www.bsquare.com > _______________________________________________ > 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 From owner-freebsd-stable@freebsd.org Wed Jan 24 13:28: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 5226FED3F51 for ; Wed, 24 Jan 2018 13:28:12 +0000 (UTC) (envelope-from michaelp@bsquare.com) Received: from NAM03-BY2-obe.outbound.protection.outlook.com (mail-by2nam03on0129.outbound.protection.outlook.com [104.47.42.129]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (Client CN "mail.protection.outlook.com", Issuer "Microsoft IT TLS CA 4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 8568A892E7 for ; Wed, 24 Jan 2018 13:28:11 +0000 (UTC) (envelope-from michaelp@bsquare.com) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=BsquareO365.onmicrosoft.com; s=selector1-bsquare-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=rXy9n659Y0711/aBPcoRDr+KWGczElcgVDRhEqE5vOU=; b=Jfy1lX7+l3OWZcPgSqB64YNV3wENW02SERxLYPs8NbLkCfh66/MYOlV4rWofNXgUDhGrC9P/ccnItBZAETXQ9ckgylPJ3faXNMC8PD3trSn6xBluDbdeipUbO6OJ9TRqiXN1dxL4zK2tUwfiB6PoYrUmPsw3VS5JJ6zCEBhG7/c= Authentication-Results: spf=none (sender IP is ) smtp.mailfrom=michaelp@bsquare.com; Received: from [10.150.16.65] (82.33.218.74) by BN6PR1301MB2018.namprd13.prod.outlook.com (10.174.89.154) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.20.444.5; Wed, 24 Jan 2018 13:28:08 +0000 Subject: Re: Ryzen issues on FreeBSD ? Cc: freebsd-stable@freebsd.org References: <8e842dec-ade7-37d1-6bd8-856ea1a827ca@sentex.net> <2c6ce4dd-f43c-7c40-abc2-732d6f8996ec@sentex.net> <795dbb79-3c18-d967-98b9-5d09a740dbfe@sentex.net> <9b769e4e-b098-b294-0bce-8bb1c42e8a59@rootautomation.com> <508a8c83-a449-3c5d-c3bf-b308d91c80c0@bsquare.com> From: Mike Pumford Message-ID: <7878977a-0340-9659-5c2f-12c67120facf@bsquare.com> Date: Wed, 24 Jan 2018 13:27:59 +0000 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.5.2 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-GB Content-Transfer-Encoding: 8bit X-Originating-IP: [82.33.218.74] X-ClientProxiedBy: VI1PR07CA0149.eurprd07.prod.outlook.com (10.170.235.36) To BN6PR1301MB2018.namprd13.prod.outlook.com (10.174.89.154) X-MS-PublicTrafficType: Email X-MS-Office365-Filtering-Correlation-Id: c469772a-6d46-42d7-ea4b-08d5632e4f51 X-Microsoft-Antispam: UriScan:; BCL:0; PCL:0; RULEID:(7020095)(4652020)(7021125)(4534165)(7022125)(4603075)(4627221)(201702281549075)(7048125)(7024125)(7027125)(7028125)(7023125)(5600026)(4604075)(2017052603307)(7153060)(7193020); SRVR:BN6PR1301MB2018; X-Microsoft-Exchange-Diagnostics: 1; BN6PR1301MB2018; 3:4fEuAKT9CW50Z7BxIWe51qwMo/8PnVfjnfJnI6/p5K07D1LeuKfkrvNTX9a/taxxP473XUC5m2AtspnYxs0TToeglG+1LxFi06hT6IsDrISCP15QM08kbH1+YWVg1rlh4th1z0+ExiIdvKMYzRMvqT3PvT0gsqPbqqblgQTM+ogDMai+MTAzmvZ/xsvEsMnHbCDlHc58QEijm30zHtOBM4JlrQpEhZCm7t3gd88D5BVgjruMZNy2HWLAdQYuHdgW; 25:dYnusxT7astNzGCgnakrORdnNpXjwbCYMDleTh7qXGfeRMz9kXoPWaAkPrCFxGKvbpo4REeDPgzmtDjzYbeA1AuVA9EKhjjZroBxHUqtzCMz3QqjMAb2WzMrYDq8FE30dobZ1XwLFsKSA25nuQqEDNcsVMmR5Pdd47ZbwCkMXlw42UJoIGwK50WlVMBWfhMcMa9bzt527dxQrWPjMRN7hueFOy6AXJLRtrZZlyfhStLnqXwdn9bpqVn03ZcrPT/kFBM2AYPRKuNkGFIAk3aPhCKL16FDlI+h7R2axV3IKk5ofaFW3Xfr1ukbGBZRAgR52djQBLV8giiiNuMAMcUg2A==; 31:2UyfRCN1TPuyVw2DnoTQI2sv5eDGB1HpAsJxxDxThOa/VqvKFDizX8X7z5qohxdauJFJPIx+udZlA0z2pcpmg0rBuNySuGHZy9G/jg0hAKa9UASCgg7AN0vTM0H7JbIkOlMfPnkN7CZt6aMQAGpf4iw/6llbsazKJuBy+Yvam4oQZNvDV4ZU8vesx+BsQsjEkqxh9aRY1cYyUjFM2Y7pDRzKzRl/vpzqYnUCzxPAZfo= X-MS-TrafficTypeDiagnostic: BN6PR1301MB2018: X-Microsoft-Antispam-PRVS: X-Exchange-Antispam-Report-Test: UriScan:(80398974133516); X-Exchange-Antispam-Report-CFA-Test: BCL:0; PCL:0; RULEID:(6040501)(2401047)(5005006)(8121501046)(3231023)(2400081)(944501161)(93006095)(93001095)(10201501046)(3002001)(6041288)(2016111802025)(20161123560045)(20161123564045)(20161123558120)(20161123562045)(6043046)(6072148)(201708071742011); SRVR:BN6PR1301MB2018; BCL:0; PCL:0; RULEID:; SRVR:BN6PR1301MB2018; X-Microsoft-Exchange-Diagnostics: 1; BN6PR1301MB2018; 4:U27bRG+GTnPiH9UEpayOJxNyN6r1uRuoaUPJzaVH1GBCS4yIQSFK8eHA30rM4RPiiSJqF+rdOnJ4vVLiD+RTLTan8owEyZ3YSJgSp9qYNrdbSMTCqqqK0yQj5h51yR9M4B5rGJb8ubo67sTrG7A6h9KxMaZN0xjxi8qyzvSOhwegksHjYuxOg5is8GTxnm7mrW4/hbJ19gkA3KiUMjz0PmdeoUKvPg1aLFvrb9XiLXsc5y60HgsoGgHZwoEIj+L/66ryPFkklDw4b+GNZCtl7BZ67ttNtOevm33Cs4ScmYCfrC89wk6fzsGSL94nkLgZ X-Forefront-PRVS: 056297E276 X-Forefront-Antispam-Report: SFV:NSPM; SFS:(10019020)(6049001)(366004)(39840400004)(346002)(376002)(396003)(39380400002)(189003)(199004)(50466002)(93886005)(26005)(77096007)(86362001)(97736004)(67846002)(53936002)(64126003)(6486002)(1671002)(6306002)(229853002)(386003)(59246006)(53546011)(106356001)(7736002)(966005)(31686004)(105586002)(90366009)(3846002)(305945005)(6116002)(25786009)(2870700001)(8936002)(31696002)(81156014)(47776003)(68736007)(65806001)(6246003)(65956001)(66066001)(16526018)(4326008)(15974865002)(3260700006)(81166006)(3480700004)(109986005)(8676002)(2906002)(36756003)(52116002)(52146003)(5660300001)(2486003)(23676004)(65826007)(83506002)(58126008)(16576012)(76176011)(478600001)(316002)(6666003)(2950100002)(42262002); DIR:OUT; SFP:1102; SCL:1; SRVR:BN6PR1301MB2018; H:[10.150.16.65]; FPR:; SPF:None; PTR:InfoNoRecords; MX:1; A:1; LANG:en; Received-SPF: None (protection.outlook.com: bsquare.com does not designate permitted sender hosts) X-Microsoft-Exchange-Diagnostics: =?utf-8?B?MTtCTjZQUjEzMDFNQjIwMTg7MjM6ZkZFWVkvSzJBL05IdlZHWEo3VWhqU0hV?= =?utf-8?B?QWZ5M2xzR09WRzJkVHZoTWZFeU4yQWlxbXRzUkZnSTJiRE9jWHVFNjlFOG9r?= =?utf-8?B?Y3NDMVNsa1pCQk1hR1lwOUZhVzArVldodkp5NGpRUVh6amxoNEo1UzQvU1Fy?= =?utf-8?B?d2dxSm9TMEZTZXliT2RHbXJjcFRGTTBHM1dnWWJwRWJzUjVrZE5vMUNFNk9U?= =?utf-8?B?S0ZuV3NMWlZ5ajR4Q0syNmNKekliQzNhRWZLM05oeXN3T3A4dTdhSFJmbzZU?= =?utf-8?B?S2FOaFJEOFlxWWI0Qy8xaGlrLzJsK0RHcFV6blFHY2M2MithVlVrTm1mK202?= =?utf-8?B?K2tYY1JacGdRUFE2di82SEFaRjRkQTVsMFpEci9iR0RHUzQxckVQVDIvb0RO?= =?utf-8?B?by8wSW5iZVc4TUhqTTJsN0cvWWF6UW1PMDVUVm0xZ3RIK1FlUkUzODAxRyty?= =?utf-8?B?dWFPMzB5T2IrbXdOdkhHYmwrTUJOTDg2UU5mdXFhL2NYS3dCY2VYVi81MDBL?= =?utf-8?B?VHRtZURWalFXRnBXSkZUYVRzV2lySi9tNTBlbzhZQk82azV1aFpUMVpKb3Bu?= =?utf-8?B?TDVJK09Ld0pKdjAvOFc0dk81N01GaUduNHdlOTIzSk5tam5UWmxORjdiVWhJ?= =?utf-8?B?aXRWeWNlU1B1b0lyMWpmaFhpTHhNMExRL0NZdFB1TThSOFROQmRwOWdZSWgw?= =?utf-8?B?V1IrUDVOQThjazYwWGxjNVRwZDdhNHdqbThrTnZGMGRvSE1NTlIwQW9KWWZB?= =?utf-8?B?ZGJidUN3MnJLK1p6K3lvNDZ6NVNrT2lWL3B5MHdEUVVuMzFBS0cxTzhpYXVU?= =?utf-8?B?WG5YVUhQWWdiQUUwcXFlWnVkQTZ4TVVsUUdNU0hEbVRRUlRjWm12SXpsZEZZ?= =?utf-8?B?V0xhU2lENGk1S2pHcVdvY1FtY3R0ZlRjN1J6dVlsREhIdVMwUjVGZDV0YWky?= =?utf-8?B?RVNEZU1kMnN4VkJTcmViMTlrWkFoQnFsdGFEMjBWazNUSURWc0d0RFdGZ2Qw?= =?utf-8?B?b0hReExyOW5KdHR0eFQ3SHJTSVJlcUsvamJHdDV4eXRwZ2F5SndoVkpBSWZN?= =?utf-8?B?Sk5vWkkzMnFjeVFjcy9UT2VUcWRLeWJhWkk5VjJyYkErb0R1eEFoWExwNFJH?= =?utf-8?B?dklCOU1WL1QzT3ZBSTNib3JtTm1tMzFJK04yNDFuVTZTampRVjVHMWxyZVNu?= =?utf-8?B?bkxpc2VjNUEyVVJNeVJ1UjNrdHJnMFUzNFovRkNPQmp6a0JBVmp4MmhoL0tP?= =?utf-8?B?SVlLVjdTYkhMSFAwWkY3N1NpTHIzV2ZNLzZoMEd4WFlsR1lxZ1RIMWtMbUxK?= =?utf-8?B?QXVYaE1ORGVrWTdxTE9CYU8rcDFkSmk3UVpNTURQQ3oyeDM3cTVkOXUyWHZW?= =?utf-8?B?aUl4SUlvWjZJekpOeDFtZWN5cndXRjMxb0dNTXNHaXJTWm9TVXJRTmlhSHF6?= =?utf-8?B?ZVpuYXlvUzNRZTRnbVhnMDg2ZWpEMTJHTi9hRzU2SnJ0bnhGNjBUME5JaGJZ?= =?utf-8?B?TTkvdmhhLzcyaGdkTDRVR0tFUCtDZDdZYUgzdGgwaSsvSm81ZXdTclQ4QUY5?= =?utf-8?B?ZXlqVk0xR3ExeXFqa0F5TlhUc1Nvdk8xejN4dkQwNTkvb2ZIdmZybWxTTm9j?= =?utf-8?B?L3FpYis0dzl0WUZ4NlNXWUxlUCtMZEVHRlV4Z1k5eHdVQ3NJL01VNUpzd1Fy?= =?utf-8?B?RGdJVHhKcTNsNlZjdHUzR285d3RtR1hadW9WbU9vb0luNXFmYktMT3pncUpw?= =?utf-8?B?eGc0ZHpialBZdTRWQ2pIbWRkTk92dGQ3VGYySkhCZDByK0p3aEY5bWxRQ0Z5?= =?utf-8?B?bW5obGtpaTNqK1BMc2VqejFZU1dQSUZlUHhlUytKOThwM3U4R2JISHBqd3pv?= =?utf-8?B?VUFjVGZBcml6bi9HWDdwb2g3UjhBVVI0clZacnNqTVRQOE80NUQzODBvdWFq?= =?utf-8?B?c01RRXRiZWVJWVBkRUxuUHRKamhpSHNpb2pvZGRRcHkvMGYyUVZpSWlWT242?= =?utf-8?B?VXlTaitucU1SUVRrdEl3UHYyWjFoM281MEUvUkVTZ0VPTnZnTWdYSjJxQ1Zs?= =?utf-8?B?cmJnV1lUY3g4cWlmaVdlT0srRHh2RHo1QzVUUGJXN3V1elhTb2ZVMWhmSEt3?= =?utf-8?Q?iTBW4zghojzdqOUXuy4t2RxsI=3D?= X-Microsoft-Exchange-Diagnostics: 1; BN6PR1301MB2018; 6:E4sYVfSdOMyG+SjNLxiBDggy3rFCHFh08UZTiTXDLrJNQ73fMjK7X/4a39fIFNevLAubwulrgeUKomhIMnFxqyz4XzGl23bmEg7JkeT0J4pdMVTxaJpIkZ17eFutsjyHECmso9GWtGwqTGOrzWPQFeuTdNFTadPVJQ/A5NpAr7f0mbmBvLldbpxVyQVnWx/RIxcs3GAmvlUzmeB9zlewUlbs9zcFII1SxwMFccVqWrSqQTMK8FUTL4yYzYd+m5OzRarPXtJJIeIHPzLpSavKFwm6SGwbFxCDO8A5Uw9zB61kJ6niPIKeBSr0/X1tNodw8JmnwPgMy5jMBntgq8X1eCR+bgqjZQFwzetJPJkAytg=; 5:71idlg6KlOWD/OVPCzCXzBCsq7QHEJGj2jGkJCxF8QcKVcuqLG1ZiacuX9inDLeRPei7Mvv7GExNpnEUIIX0uEYRyJBwzsxRi3hd5HN6fjMWIe/WS6FZry1y/pGYZW2lrvQYTQ2dkVajzOV7sFyDpRIL6TyNKXqUPw2g/gLK/XA=; 24:C23PmfBALE4fHlN2y8tGUE61KYpQ9KIqVXNKlKNnPMXNqqv7qWo5LdzClRtMgluFYcRfH8aFjSRa+1iYHW0HlLT5LNJm/+hE9UcDpWrqNus=; 7:eWzoS2FcWzb/8QGD6iUprassu+38uBam5+7hb2xZA4ipUKCAnnLANmk7fvICsA+h/SE/RdzUi/dZdZvKXs1E/a3JL0Wq0DzOZAWEBUh7f5XkynV3SIc3tAqNO9lF6nYzjbbtA8dIZBoUnwvMVouLY7YoLL6Hhl8/hifuoo8/cc6oRuQqcTEXzwnjwSQJEpTu4Lo7JdTWFV9lXdQRSIEg181wUZwW7p/4t1iX2hGiRX2g719wTN5ApAQS1bC1/OU1 SpamDiagnosticOutput: 1:99 SpamDiagnosticMetadata: NSPM X-OriginatorOrg: bsquare.com X-MS-Exchange-CrossTenant-OriginalArrivalTime: 24 Jan 2018 13:28:08.8988 (UTC) X-MS-Exchange-CrossTenant-Network-Message-Id: c469772a-6d46-42d7-ea4b-08d5632e4f51 X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted X-MS-Exchange-CrossTenant-Id: c078f217-c3b7-46c6-bf76-ff2c451cfe9a X-MS-Exchange-Transport-CrossTenantHeadersStamped: BN6PR1301MB2018 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, 24 Jan 2018 13:28:12 -0000 On 24/01/2018 13:21, Nimrod Levy wrote: > If my google-fu is any good today, DDR3 maxes out at 2133.  DDR4 seems > to go up to 3200[1]. The motherboard claims to support all speeds. > > This RAM is supposed to be DDR4-2400, but if it keeps things happy, I'll > run it at 2133. > > [1] https://www.kingston.com/us/memory/ddr4 > Seems you are right. Its possible at least one of my systems is a DDR3 one then as the reading I did at the time said that 2133 was the max. I'll recheck my systems and double check what they actually are. ;) I do know that I tried the faster than default memory profiles on both and it introduced instability that went away when I went back to the standard profile. I've done BIOS updates since then so its worth me checking that again anyway. Mike -- Mike Pumford | Senior Software Engineer T: +44 (0) 1225 710635 BSQUARE - The business of IoT www.bsquare.com From owner-freebsd-stable@freebsd.org Wed Jan 24 14:22:14 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 1229BED69CF for ; Wed, 24 Jan 2018 14:22:14 +0000 (UTC) (envelope-from marklmi26-fbsd@yahoo.com) Received: from sonic313-13.consmr.mail.bf2.yahoo.com (sonic313-13.consmr.mail.bf2.yahoo.com [74.6.133.123]) (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 AFC358B582 for ; Wed, 24 Jan 2018 14:22:13 +0000 (UTC) (envelope-from marklmi26-fbsd@yahoo.com) X-YMail-OSG: Gsj0NkcVM1kRUiULzFa526IvpqbLfMk7O.nVJO2pYQ3MTmMFHT5WyHfaNkv7xak KZLJYdGyUCdXIeG3F6CufSEAl19tALwAeSXU9zDY2Us77IkFdjj8jZfw_9aY0r30C8EacaGdyyva .XzAIzFBSYVsKqjNYGZFMKUgarh1pj4V0Aci0LEGFBl2r1vfUvqW3twCnM.EdvcmjlQgaGpTH9AM ap5W8.s6Yv6Eiu9mvnhQVtbh9kiDt4cEhdk2l_Cf5wsF_i49Ntq31c.TW9olPyrxkT9gp6XD3cwM 1VET5ab9vgQAVr1plNl1IACmLZQ75AH6tkQrJDzebs9Dcf7F37MQLx78wCkJONj7lTVVFdpmiR58 WtpZH09sNG5GBTS3zTi_g33MExHneQzg_9xOH525c3p5yQj.7gJVixrzASjiQjoFyUW4oqHh3jl7 4Wlex3OqVUc_JLNWe3b7DbLIo5jsLFgYzjZsDeVoWNwqYgZRBZvo9l8x3Xzf_NVRkorY- Received: from sonic.gate.mail.ne1.yahoo.com by sonic313.consmr.mail.bf2.yahoo.com with HTTP; Wed, 24 Jan 2018 14:22:07 +0000 Received: from smtp104.rhel.mail.bf1.yahoo.com (EHLO [192.168.1.25]) ([98.139.230.215]) by smtp409.mail.bf1.yahoo.com (JAMES SMTP Server ) with ESMTPA ID 170b2f3726a0d666f3526f64f209f2d0; Wed, 24 Jan 2018 14:22:02 +0000 (UTC) From: Mark Millard Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Mac OS X Mail 11.2 \(3445.5.20\)) Subject: Re: Ryzen issues on FreeBSD ? Message-Id: Date: Wed, 24 Jan 2018 06:22:00 -0800 To: nimrodl@gmail.com, michaelp@bsquare.com, FreeBSD-STABLE Mailing List X-Mailer: Apple Mail (2.3445.5.20) 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, 24 Jan 2018 14:22:14 -0000 Mike Pumford michaelp at bsquare.com wrote on Wed Jan 24 12:03:04 UTC 2018 : > I've run into this on modern Intel systems as well. The RAM is sold as > 2400 but thats actually an overclock profile. If I actually enabled it > (despite both board and RAM being qualified for that) the system ends up > locking up or crashing as soon as you stress it. Go back to the standard > DDR profile advertised by the RAM and it is totally stable. The reported fails are during idle time as I understand. Things are working when the CPU's are kept busy from what I've read in the various notes. The hang-ups are during idle times. "the system ends up locking up or crashing as soon as you stress it" does not sound like a matching context. That a slower RAM speed might help idle behave correctly is interesting given the Zen and Ryzen dependence on RAM speed for the speed of its internal interconnect-fabric's operation. I'll note that, if one goes through the referenced Linux exchanges about this, Ryzen Threadripper's examples are also reported to have the problem. === Mark Millard marklmi at yahoo.com ( markmi at dsl-only.net is going away in 2018-Feb, late) From owner-freebsd-stable@freebsd.org Wed Jan 24 14:42: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 09A31ED75D6 for ; Wed, 24 Jan 2018 14:42:53 +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 9383B8C0A0 for ; Wed, 24 Jan 2018 14:42:52 +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 w0OEgppu018067 (version=TLSv1 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for ; Wed, 24 Jan 2018 09:42:51 -0500 (EST) (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 w0OEgnnm068256; Wed, 24 Jan 2018 09:42:49 -0500 (EST) (envelope-from mike@sentex.net) Subject: Re: Ryzen issues on FreeBSD ? (summary of 4 issues) To: Mark Millard , nimrodl@gmail.com, michaelp@bsquare.com, FreeBSD-STABLE Mailing List References: From: Mike Tancsa Organization: Sentex Communications Message-ID: <744bbe18-80c4-d057-c88d-fbe480ee9abb@sentex.net> Date: Wed, 24 Jan 2018 09:42:50 -0500 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.5.2 MIME-Version: 1.0 In-Reply-To: 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: Wed, 24 Jan 2018 14:42:53 -0000 I think perhaps a good time to summarize as a few issues seem to be going on a) fragile BIOS settings. There seems to be a number of issues around RAM speeds and disabled C-STATES that impact stability. Specifically, lowering the default frequency from 2400 to 2133 seems to help some users with crashes / lockups under heavy loads. b) CPUs manufactured prior to week 25 (some say week 33?) have a hardware defect that manifests itself as segfaults in heavy compiles. I was able to confirm this on 1 of the CPUs I had using a Linux setup. It seems to confirm this, you need to physically look at the CPU for the manufacturing date :( Not sure how to trigger it on FreeBSD reliably, but there is a github project I used to verify on Linux (https://github.com/suaefar/ryzen-test) c) The idle lockup bug. This *seems* to be confirmed on Linux as well http://blog.programster.org/ubuntu-16-04-compile-custom-kernel-for-ryzen and https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1690085 d) Compile failures of some ports. For myself and one other user, compiling net/samba47 reliably hangs in roughly the same place. Its not clear if this is related to any of the above bugs or not. Right now I have RMA'd my 3 CPUs back to AMD. Hopefully, I will get replacements in a week and can get back to testing c) and d). ---Mike On 1/24/2018 9:22 AM, Mark Millard via freebsd-stable wrote: > Mike Pumford michaelp at bsquare.com wrote on > Wed Jan 24 12:03:04 UTC 2018 : > >> I've run into this on modern Intel systems as well. The RAM is sold as >> 2400 but thats actually an overclock profile. If I actually enabled it >> (despite both board and RAM being qualified for that) the system ends up >> locking up or crashing as soon as you stress it. Go back to the standard >> DDR profile advertised by the RAM and it is totally stable. > > The reported fails are during idle time as I understand. Things are > working when the CPU's are kept busy from what I've read in the > various notes. The hang-ups are during idle times. > > "the system ends up locking up or crashing as soon as you stress it" > does not sound like a matching context. > > That a slower RAM speed might help idle behave correctly is interesting > given the Zen and Ryzen dependence on RAM speed for the speed of its > internal interconnect-fabric's operation. > > I'll note that, if one goes through the referenced Linux exchanges about > this, Ryzen Threadripper's examples are also reported to have the problem. > > === > Mark Millard > marklmi at yahoo.com > ( markmi at dsl-only.net is > going away in 2018-Feb, late) > > _______________________________________________ > 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" > > -- ------------------- Mike Tancsa, tel +1 519 651 3400 Sentex Communications, mike@sentex.net Providing Internet services since 1994 www.sentex.net Cambridge, Ontario Canada http://www.tancsa.com/ From owner-freebsd-stable@freebsd.org Wed Jan 24 15:07:27 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 79CDFED857F for ; Wed, 24 Jan 2018 15:07:27 +0000 (UTC) (envelope-from nimrod@nimrod.is-a-geek.net) Received: from mail-yw0-x22d.google.com (mail-yw0-x22d.google.com [IPv6:2607:f8b0:4002:c05::22d]) (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 154C28CFD7 for ; Wed, 24 Jan 2018 15:07:26 +0000 (UTC) (envelope-from nimrod@nimrod.is-a-geek.net) Received: by mail-yw0-x22d.google.com with SMTP id x62so1584997ywg.11 for ; Wed, 24 Jan 2018 07:07:26 -0800 (PST) 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=EG2QoPsZFySmP4EROcu1dKB9WicvwXGKMjYrYCpI6e8=; b=DbkwyLy5x5l6YH/GtYfluH4Wnp2T4p8NJ2uwuIINwytjKlGfTUYaf9hsq5tH8F8F7n hn9eVUW7DDW8SVQ+rBVAykE/sxxOns/JkYwsw6Fd4feZkKTz5Be6e3mJVy6xlwMCGRDO 2dZ3cBadCK5Vmb0loyH+7GkTR/bQzOC+2quysW+g4YJl+loF04lqzm5rD43gAiFcm2Ao D7cy+r5CRU6JLkh3r9asVGRfMnoSdiLVRiegQJ2dQKwOXC0gIaQHc7+NzlXD8JPZGwL8 tmuPMlD/dhdHgap6GAyFOeQaPfsVleXW5CXzJiX5a8mHVKnNiSpCO9J9SdvFZ1dIx+wI t46g== 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=EG2QoPsZFySmP4EROcu1dKB9WicvwXGKMjYrYCpI6e8=; b=KqYgD9Ex+4z86NoFh/Pg7bafsgHJdO3Va0TKtMbNpEE5PODMzLVhgPOXmNIc20To3j M9Jhrs7gSXwblZQxu5trVa6IaMASxetM1wUyofUIZKICKaYZUDcd+n4AEWv1HcybkjFr nnjn/le9CXtD2xlP1WabFowK4BM5oQNGxlRUFvKKHD/u606LWE8jQ/geLkI8qrkKsVNx xRHTlvErrleNJJtGgnCHLFzwrcEqOyoGzXi6SZgKFcpriuNfbR13DdJOyc7xZfpYKyXa IdZ+6de0cMylztUbH3VFlmKcJ+/cAavbiA4pfHICpxrRk+MaX4u9L9ECqJbAfohb4l8+ 3MaA== X-Gm-Message-State: AKwxytcTPyehz/a5Fpn9H+vHntEoUYPD9zey/G2Ozfdal02jR9zgoMzu c5KmINpVAIJSsTnZZZUeMoBvGkUROj7liv0vMcXrsg== X-Google-Smtp-Source: AH8x227kx2dYnJDnQShiyU87TUj++Xabnf4ONQxoOe596h/7GwMtZAKNMbZ28B6w/QgUySJJ8MZEMJ9ELcEp2un5X6s= X-Received: by 10.129.40.207 with SMTP id o198mr5533986ywo.320.1516806446056; Wed, 24 Jan 2018 07:07:26 -0800 (PST) MIME-Version: 1.0 References: <744bbe18-80c4-d057-c88d-fbe480ee9abb@sentex.net> In-Reply-To: <744bbe18-80c4-d057-c88d-fbe480ee9abb@sentex.net> From: Nimrod Levy Date: Wed, 24 Jan 2018 15:07:15 +0000 Message-ID: Subject: Re: Ryzen issues on FreeBSD ? (summary of 4 issues) To: Mike Tancsa Cc: Mark Millard , michaelp@bsquare.com, FreeBSD-STABLE Mailing List 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, 24 Jan 2018 15:07:27 -0000 I'm not sure this is characterized quite right. I've been seeing c) where the system freezes completely and seems to be related to idle/ low load, but the workaround that seems to be working around the issue is part of a) where I lowered the memory speed. On Wed, Jan 24, 2018 at 9:42 AM Mike Tancsa wrote: > I think perhaps a good time to summarize as a few issues seem to be going > on > > a) fragile BIOS settings. There seems to be a number of issues around > RAM speeds and disabled C-STATES that impact stability. Specifically, > lowering the default frequency from 2400 to 2133 seems to help some > users with crashes / lockups under heavy loads. > > b) CPUs manufactured prior to week 25 (some say week 33?) have a > hardware defect that manifests itself as segfaults in heavy compiles. I > was able to confirm this on 1 of the CPUs I had using a Linux setup. It > seems to confirm this, you need to physically look at the CPU for the > manufacturing date :( Not sure how to trigger it on FreeBSD reliably, > but there is a github project I used to verify on Linux > (https://github.com/suaefar/ryzen-test) > > c) The idle lockup bug. This *seems* to be confirmed on Linux as well > http://blog.programster.org/ubuntu-16-04-compile-custom-kernel-for-ryzen > and > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1690085 > > d) Compile failures of some ports. For myself and one other user, > compiling net/samba47 reliably hangs in roughly the same place. Its not > clear if this is related to any of the above bugs or not. > > Right now I have RMA'd my 3 CPUs back to AMD. Hopefully, I will get > replacements in a week and can get back to testing c) and d). > > ---Mike > > -- -- Nimrod From owner-freebsd-stable@freebsd.org Wed Jan 24 15:12: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 2D1BFED8944 for ; Wed, 24 Jan 2018 15:12:15 +0000 (UTC) (envelope-from tech-lists@zyxst.net) Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28]) (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 CCAC08D3A7 for ; Wed, 24 Jan 2018 15:12:14 +0000 (UTC) (envelope-from tech-lists@zyxst.net) Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id 90DC7223AC; Wed, 24 Jan 2018 10:10:28 -0500 (EST) Received: from frontend2 ([10.202.2.161]) by compute4.internal (MEProxy); Wed, 24 Jan 2018 10:10:28 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=zyxst.net; h=cc :content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=fm1; bh=5SCq5W1CHJzMiNMtbHNzbyUp4L+9r Vw0PEfgO7rqqVk=; b=SQq7BP7a+rnRw5JS0kt26e8f7cPRwOHpinG7UIm3tqlh2 M/BA7FFXFx+pHNE3l3VZxikZQBrnhqLNAfypPgOnTzOEaxrKTE3nXh1rj5eL1T0t PbRx10COcnsR52/ZRL6wg3FNO/wijMMvRTI0JfLi29oawGA7/GSLmkfK4sq+xz+6 eJzwMpVX8/xO37UFpCCOZ6qHnb0PPOGTnUy5lKHd41Tyay6rpzeg1iT8HApPrlQ/ tMDEbSfwsCP+OtavsOHF3G17HiSt3GWbONuc7+DOH7GluQOSXuwT1wL05UnnIF+T 4gI7A8gxJmUUaD71h7kPUjPqOc+A66IPJvgNTVw3g== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=5SCq5W 1CHJzMiNMtbHNzbyUp4L+9rVw0PEfgO7rqqVk=; b=mfOCBQqss4BzKi++oAG64v XaeGq4KDHShzjsn7KSpHbNHv3dDfXr2S9BlHBS8IbGIMDbTll3+TPlb4Nyxin6uW DOeP8d5/+NjKk0ujq2c8EXvU87FStZCt/5ooJGiUHydpNqK8awp4rDh56rlF5bEc Pqgf0knHA2a5rxKMQoaSfFk7LRTPDntjT8EL7X6wog1im30rToGJKGoBEuZouiNq LgAgHUGD+aMx/Gar/ZhUJdrCdp7hZYY68Or3cVzGn78oOgQ8FZLGuqBAq0uaKJbG Glerl+DP+g0Q3pdJHvr7BdwVkmzAHzkZOgmW75esWo1m8zKsp7wOd5jGwQx38L1g == X-ME-Sender: Received: from desktop.parsley.growveg.org (parsley.growveg.org [82.70.91.97]) by mail.messagingengine.com (Postfix) with ESMTPA id 12964240F8; Wed, 24 Jan 2018 10:10:27 -0500 (EST) Subject: Re: why does buildworld fail on stable/11 ? To: Scott Bennett References: <201801240851.w0O8pnDl008705@sdf.org> Cc: freebsd-stable@freebsd.org From: tech-lists Message-ID: Date: Wed, 24 Jan 2018 15:10:25 +0000 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.5.2 MIME-Version: 1.0 In-Reply-To: <201801240851.w0O8pnDl008705@sdf.org> Content-Type: text/plain; charset=utf-8 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, 24 Jan 2018 15:12:15 -0000 On 24/01/2018 08:51, Scott Bennett wrote: > hellas# mv /etc/make.conf{,.save} > hellas# mv /etc/src.conf{,.save} > hellas# cd /usr/src > hellas# make cleandir > "/usr/src/share/mk/local.sys.mk", line 51: Malformed conditional (${.MAKE.MODE:Mmeta*} != "") > "/usr/src/share/mk/local.sys.mk", line 58: Malformed conditional (${.MAKE.MODE:Mnofilemon} == "") > "/usr/src/share/mk/local.sys.mk", line 76: if-less else > "/usr/src/share/mk/local.sys.mk", line 79: if-less endif > "/usr/src/share/mk/sys.mk", line 476: if-less endif > bmake: fatal errors encountered -- cannot continue > *** Error code 1 Move the /usr/src somewhere else, make a new /usr/src dir and then svnlite co https://svn.FreeBSD.org/base/stable/11 /usr/src make sure it completes normally then cd into it and make cleandir. What happens? -- J. From owner-freebsd-stable@freebsd.org Wed Jan 24 15:17: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 28885ED8DAB for ; Wed, 24 Jan 2018 15:17:43 +0000 (UTC) (envelope-from tech-lists@zyxst.net) Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28]) (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 C89DA8D897 for ; Wed, 24 Jan 2018 15:17:42 +0000 (UTC) (envelope-from tech-lists@zyxst.net) Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id 5B97B2231E for ; Wed, 24 Jan 2018 10:17:42 -0500 (EST) Received: from frontend2 ([10.202.2.161]) by compute4.internal (MEProxy); Wed, 24 Jan 2018 10:17:42 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=zyxst.net; h= content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=fm1; bh=oq71F+MuVI+qtG6ImX1PvbuKBZPkS pzNIxpCZTTxFUA=; b=iHoFZ6jmDpq4XB3vTbe0Av9UDlx3MsdiN//T+oPwp3ZEo PnbKRgfbQI0CEJAWxRjWSmsk6UpVf2s4gfmKVOWRXAGnF9jDpiVGbyoNc934A/fo gKEIGEzyqH0H56HETRbQT2UlEomQVq2d1THllfuKXVB23GTvc2QPQaAYBMrLUigH APXQeHNzYnci8uqk+igfWQqCOm8A9wbd6NNMSvNIYfuAA/E1zvcX1YJgxyJwfu/N f4F6J6Wk54qqBOY8Mt8NmJ8491OVUqHuxulncAdkffYNTDzhM4jmzigLAR/uhQxR zVEnLdm7mVJQy1+cRB8bKrK5nA/77+KtVufWjRWGg== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=oq71F+ MuVI+qtG6ImX1PvbuKBZPkSpzNIxpCZTTxFUA=; b=ei8IStUynwzXUPhvJm6rd8 +VnmUZ6L0ov9Ithsz+2+S0KSAwCqXrazqzMfn1w7Gcc74LuM339mDmh9Dqrib0I4 lZMcD1glGHi7zQBtJD+HPN10M+Q50dd7eX2EPgyR2wfdj7x4XrzvfAlpX88RJFK5 5SJuj/vaVyTsq4oYO2h1ihLKqNS8OKjcs9crrjs5I+MxdHTeyp+q3syDJzc3fgCg MlN+37TQ3lL4qxW6HpQ2EJelnWkpSJrvk6TPjmXSH1eSfPWUEbBNDwho3yE957Ih G3nJmGJfHS09tgz1g4WpoupxmHdqqTO3eGAKYCfJzY/rsI7CwzI/yoz53nmfDCrA == X-ME-Sender: Received: from desktop.parsley.growveg.org (parsley.growveg.org [82.70.91.97]) by mail.messagingengine.com (Postfix) with ESMTPA id ED59224697 for ; Wed, 24 Jan 2018 10:17:41 -0500 (EST) Subject: Re: why does buildworld fail on stable/11 ? To: freebsd-stable@freebsd.org References: <201801240815.w0O8Fjo7010887@sdf.org> From: tech-lists Message-ID: <6dbb4810-1bd9-2a65-dcad-576b57cb6e85@zyxst.net> Date: Wed, 24 Jan 2018 15:17:39 +0000 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.5.2 MIME-Version: 1.0 In-Reply-To: <201801240815.w0O8Fjo7010887@sdf.org> Content-Type: text/plain; charset=utf-8 Content-Language: en-GB 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, 24 Jan 2018 15:17:43 -0000 On 24/01/2018 08:15, Scott Bennett wrote: >> Hi, > > Thank you for responding with your thoughts on this. >> >> What I'd do is firstly to make things as simple as possible. First do >> the upgrade simply. Either delete or call make.conf & src.conf something > > Okay. > >> else. Then get a fresh src and ports tree via svnlite. Then do > > /usr/src has not been altered since I ran the checkout. Is there some reason > to use svnlite rather than svn, which is how I did the checkout? I use svnlite because it's in base, and in your type of situation I'd want to use base tools. When did you run the checkout? Did it complete without error? >> >> rm -rf /buildwork/ccache.freebsd >> mkdir /buildwork/ccache.freebsd > > I'm not following your thinking here. If I've eliminated /etc/make.conf > from the picture, then ccache is not involved at all, so why should I wipe out > the cache contents? that's the way it *should* work. But by doing this, we eliminate the possibility of ccache being in the equation at all. >> then cd into /usr/src as root, then do >> >> yes | make delete-old >> yes | make delete-old-libs > > What do you expect the above to accomplish on a freshly installed system > on which no obsolete directories or libraries from a previous release should > exist? *should* exist. What I'm suggesting makes *certain*. What we know is make is encountering a problem. What I'm suggesting removes things make might be picking up, for certain. It's how I've overcome similar issues in the past - elmiminate all the variables I can, then run it in a vanilla way, to see if it's still broken. -- J. From owner-freebsd-stable@freebsd.org Wed Jan 24 15:18: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 3BC3EED8E90 for ; Wed, 24 Jan 2018 15:18:55 +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 C5B1D8D97A for ; Wed, 24 Jan 2018 15:18:54 +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 w0OFIsFA026820 (version=TLSv1 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for ; Wed, 24 Jan 2018 10:18:54 -0500 (EST) (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 w0OFIqZt068341; Wed, 24 Jan 2018 10:18:52 -0500 (EST) (envelope-from mike@sentex.net) Subject: Re: Ryzen issues on FreeBSD ? (summary of 4 issues) To: Nimrod Levy Cc: Mark Millard , michaelp@bsquare.com, FreeBSD-STABLE Mailing List References: <744bbe18-80c4-d057-c88d-fbe480ee9abb@sentex.net> From: Mike Tancsa Organization: Sentex Communications Message-ID: <5d13e877-88d9-30a3-3ec1-0824f48a9a64@sentex.net> Date: Wed, 24 Jan 2018 10:18:53 -0500 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.5.2 MIME-Version: 1.0 In-Reply-To: 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: Wed, 24 Jan 2018 15:18:55 -0000 On 1/24/2018 10:07 AM, Nimrod Levy wrote: > I'm not sure this is characterized quite right.  I've been seeing c) > where the system freezes completely and seems to be related to idle/ low > load, but the workaround that seems to be working around the issue is > part of a) where I lowered the memory speed. It did seem to reduce the frequencies of the lockups, but I still had at least one with the RAM speed reduced. I want to rule out b) from all this with replacement CPUs so will revisit in a week. ---Mike > > > On Wed, Jan 24, 2018 at 9:42 AM Mike Tancsa > wrote: > > I think perhaps a good time to summarize as a few issues seem to be > going on > > a) fragile BIOS settings. There seems to be a number of issues around > RAM speeds and disabled C-STATES that impact stability.  Specifically, > lowering the default frequency from 2400 to 2133 seems to help some > users with crashes / lockups under heavy loads. > > b) CPUs manufactured prior to week 25 (some say week 33?) have a > hardware defect that manifests itself as segfaults in heavy compiles.  I > was able to confirm this on 1 of the CPUs I had using a Linux setup. It > seems to confirm this, you need to physically look at the CPU for the > manufacturing date :( Not sure how to trigger it on FreeBSD reliably, > but there is a github project I used to verify on Linux > (https://github.com/suaefar/ryzen-test) > > c) The idle lockup bug.  This *seems* to be confirmed on Linux as well > http://blog.programster.org/ubuntu-16-04-compile-custom-kernel-for-ryzen > and > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1690085 > > d) Compile failures of some ports.  For myself and one other user, > compiling net/samba47 reliably hangs in roughly the same place.  Its not > clear if this is related to any of the above bugs or not. > > Right now I have RMA'd my 3 CPUs back to AMD. Hopefully, I will get > replacements in a week and can get back to testing c) and d). > >         ---Mike > > -- > > -- > Nimrod > -- ------------------- Mike Tancsa, tel +1 519 651 3400 Sentex Communications, mike@sentex.net Providing Internet services since 1994 www.sentex.net Cambridge, Ontario Canada http://www.tancsa.com/ From owner-freebsd-stable@freebsd.org Wed Jan 24 16:29:21 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 29F91EDB978 for ; Wed, 24 Jan 2018 16:29:21 +0000 (UTC) (envelope-from haramrae@gmail.com) Received: from mail-ua0-x233.google.com (mail-ua0-x233.google.com [IPv6:2607:f8b0:400c:c08::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id BC64E8FE93 for ; Wed, 24 Jan 2018 16:29:20 +0000 (UTC) (envelope-from haramrae@gmail.com) Received: by mail-ua0-x233.google.com with SMTP id t6so3070181ual.7 for ; Wed, 24 Jan 2018 08:29:20 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=R29oP+AGNj2Xzj1IDRrwBRbHLwcw55xTKo6sU0DPIW0=; b=juD9fm4HvQOGIKq3r+ht3ib8TDeTgUINB+Kdtvmc7eCt0D7n5j702uXwT9nYLPmzRv Q1gwvPi7jKA6wQymFNA+d7lRr7/LdcLFXsHAh+TDYgTWTcwaupd5qeQPkXT+vxviwuR0 1ri7P1RO+r5YaVqra4aW4dDbzCfSRMvLaBHnVoWz1Fsf/xMHK/uZSFsqjgSjpDM7cwV+ nTQebVBJBX+NHk+XCxNIIKphvvIswdBp+DBun+Z4bWjQ2/eqq9EOfs87HNqIhDS3juLa vuB8lipPLam6MvzSmB7BJZUf4r1KWxklgGqanAjqo2L9ZYKQ3qK4BoLFn7/i5MD0u7yE Ji3g== 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=R29oP+AGNj2Xzj1IDRrwBRbHLwcw55xTKo6sU0DPIW0=; b=FIc7nRVjdDBWg0gmn+BA1jUQoTBjWRB9CHY+epyY7SiT9At6S9Z/0TEiaprV5aqMO2 mGcokc12shxwuzRbuDgMmw9azho3LZTumehaCLifXpCYwOfW/GNkCLPR+rhhutMvbjv6 v1IS0MH6EYOUayXp160pErJf+ZIwfdpN5XR8B7XPL1fv4Eq49Kj4pN5qiPFuQdQFgSsq p8V0+n9wkLBCxxA2yc7POmd6fxqwQAyihLN0d+4R8qibeli0320UMuxlVeCHxacpwcDk L+LJqaHsRG6gykyVwNtMNDBe4ZDotF6zhoDhwERfjkQCCrghkUDtCvZQh3jFAYRQA0K3 qxSA== X-Gm-Message-State: AKwxytdmAIHlZP3bRBPSe+yla2qlFSlo6wBjbDhX3pu8gfMY+f3K2ZSA Jdo0E6P7/xQdybE63gjq7cK+ysXnFt5hzT9j0Sg= X-Google-Smtp-Source: AH8x227Qmg6YAfhXdUAf0PQwDnTPGGHAH0owA+X8vckmWHZMXNzxk5gzrib87dWsI883Ntl/Oimv1mpTL3aCmhqSaS0= X-Received: by 10.176.19.16 with SMTP id g16mr5040676uae.11.1516811360190; Wed, 24 Jan 2018 08:29:20 -0800 (PST) MIME-Version: 1.0 Received: by 10.176.89.236 with HTTP; Wed, 24 Jan 2018 08:29:19 -0800 (PST) In-Reply-To: <744bbe18-80c4-d057-c88d-fbe480ee9abb@sentex.net> References: <744bbe18-80c4-d057-c88d-fbe480ee9abb@sentex.net> From: Alban Hertroys Date: Wed, 24 Jan 2018 17:29:19 +0100 Message-ID: Subject: Re: Ryzen issues on FreeBSD ? (summary of 4 issues) To: Mike Tancsa Cc: Mark Millard , nimrodl@gmail.com, michaelp@bsquare.com, FreeBSD-STABLE Mailing List Content-Type: text/plain; charset="UTF-8" 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, 24 Jan 2018 16:29:21 -0000 On 24 January 2018 at 15:42, Mike Tancsa wrote: > b) CPUs manufactured prior to week 25 (some say week 33?) have a > hardware defect that manifests itself as segfaults in heavy compiles. I > was able to confirm this on 1 of the CPUs I had using a Linux setup. It > seems to confirm this, you need to physically look at the CPU for the > manufacturing date :( Not sure how to trigger it on FreeBSD reliably, > but there is a github project I used to verify on Linux > (https://github.com/suaefar/ryzen-test) According to post #39 in the referenced Linux thread (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1690085): "It was officially fixed for all ryzen manufactured after week 30." I currently have a Ryzen 1600X from week 17/30, which suggests it will have the bug. Unfortunately, I don't have it built into a system yet as I'm waiting for DDR4 prices to become reasonable again before ordering any, so I can't test it. I'm not sure how solid this info is, should I RMA it without even having tested that it has a problem? Alban Hertroys -- If you can't see the forest for the trees, Cut the trees and you'll see there is no forest. From owner-freebsd-stable@freebsd.org Wed Jan 24 16:37:03 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 CC4EFEB40C9 for ; Wed, 24 Jan 2018 16:37:03 +0000 (UTC) (envelope-from ian@freebsd.org) Received: from outbound1a.eu.mailhop.org (outbound1a.eu.mailhop.org [52.58.109.202]) (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 5C54F68794 for ; Wed, 24 Jan 2018 16:37:03 +0000 (UTC) (envelope-from ian@freebsd.org) X-MHO-User: c631426f-0124-11e8-91c6-33ffc249f3e8 X-Report-Abuse-To: https://support.duocircle.com/support/solutions/articles/5000540958-duocircle-standard-smtp-abuse-information X-Originating-IP: 73.78.92.27 X-Mail-Handler: DuoCircle Outbound SMTP Received: from ilsoft.org (unknown [73.78.92.27]) by outbound1.eu.mailhop.org (Halon) with ESMTPSA id c631426f-0124-11e8-91c6-33ffc249f3e8; Wed, 24 Jan 2018 16:36:51 +0000 (UTC) Received: from rev (rev [172.22.42.240]) by ilsoft.org (8.15.2/8.15.2) with ESMTP id w0OGamNf008913; Wed, 24 Jan 2018 09:36:48 -0700 (MST) (envelope-from ian@freebsd.org) Message-ID: <1516811808.42536.173.camel@freebsd.org> Subject: Re: why does buildworld fail on stable/11 ? From: Ian Lepore To: Dimitry Andric , Scott Bennett Cc: freebsd-stable@freebsd.org, lists Date: Wed, 24 Jan 2018 09:36:48 -0700 In-Reply-To: <0A86F03E-DB69-4DD0-B67B-E9BFBE3DC739@FreeBSD.org> References: <201801240851.w0O8pnDl008705@sdf.org> <0A86F03E-DB69-4DD0-B67B-E9BFBE3DC739@FreeBSD.org> Content-Type: text/plain; charset="ISO-8859-1" X-Mailer: Evolution 3.18.5.1 FreeBSD GNOME Team Port Mime-Version: 1.0 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, 24 Jan 2018 16:37:04 -0000 On Wed, 2018-01-24 at 12:39 +0100, Dimitry Andric wrote: > On 24 Jan 2018, at 09:51, Scott Bennett wrote: > > > > > > Subject: Re: why does buildworld fail on stable/11 ? > > > >     I wrote: > > > > > >    On Mon, 22 Jan 2018 12:42:58 +0000 lists wrote: > > > > > > > > On 22/01/2018 09:17, Scott Bennett wrote: > > > > > > > > > >    Anyway, I'm stuck.  Can someone please tell me what is going wrong and > > > > > how to fix it?  I'd really like to be able to update my system, not only to > > > > > keep it reasonably current, but also to be able to customize a kernel.  Thanks > > > > > in advance for any suggestions/solutions. > >     [much deleted  --SB] > > > > > > > > > > > then > > > > > > > > [/usr/src #] make cleandir && make clean && make buildworld && make > > > > buildkernel && make installkernel && mergemaster -p > > >    At this point, that looks very optimistic, to say the least. :-)  I've > > > tried "make cleanworld" (with /etc/make.conf still in place), and it failed > > > exactly like the buildworld example I posted before. > >     Okay.  Here's what happened. > > > > Script started on Wed Jan 24 02:17:30 2018 > > hellas# mv /etc/make.conf{,.save} > > hellas# mv /etc/src.conf{,.save} > > hellas# cd /usr/src > > hellas# make cleandir > > "/usr/src/share/mk/local.sys.mk", line 51: Malformed conditional (${.MAKE.MODE:Mmeta*} != "") > > "/usr/src/share/mk/local.sys.mk", line 58: Malformed conditional (${.MAKE.MODE:Mnofilemon} == "") > > "/usr/src/share/mk/local.sys.mk", line 76: if-less else > > "/usr/src/share/mk/local.sys.mk", line 79: if-less endif > > "/usr/src/share/mk/sys.mk", line 476: if-less endif > > bmake: fatal errors encountered -- cannot continue > Looks like your make is broken.  What is the output of "which make"? > > -Dimitry > And also the output of "make -V MAKE_VERSION".  To me, this looks a lot like what happens when you try to use old fmake from freebsd 8 to build modern freebsd source. -- Ian From owner-freebsd-stable@freebsd.org Wed Jan 24 17:35:23 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 20F87EB74DC for ; Wed, 24 Jan 2018 17:35:23 +0000 (UTC) (envelope-from peter@hda3.com) Received: from mail-qt0-x229.google.com (mail-qt0-x229.google.com [IPv6:2607:f8b0:400d:c0d::229]) (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 ADFC96B4A3 for ; Wed, 24 Jan 2018 17:35:22 +0000 (UTC) (envelope-from peter@hda3.com) Received: by mail-qt0-x229.google.com with SMTP id l20so12321398qtj.11 for ; Wed, 24 Jan 2018 09:35:22 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hda3-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=Jgq6MLTrU7yySeBWoqne/PrrmvdxsaERNcSJ/h58Rzo=; b=CYAonkQmp3sJWYRwKsWjAPcJ8Yu2iHTo+I15eaezul+L/mHP9Ih3gvgAg6Dhq55pg9 uuLS2akl5FK6NqR53iXgfbk87zImRn9wsa5Ck94kOxmAtdxVs+5i2YnbmpXc5FP7YuB0 0t7vDPZnPGELvvZYGxMJvQPN5jHu2j6skNtN1ZFIgpdcuxJ+Jw2YexkQhzuzjV+O947a FbRuwoTJrZdZHJCw2BQgQFpScfcuHbA82AcOzngQW7ky7mE/Q1n1wa3lutWAH3CP2uE+ Zo7lMNJDF2w4hnBy2qrcRoiAY+hWzlxflWFPFhSDAUmRkAqPmMtI+0LML3ndMK51NFEO cksQ== 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=Jgq6MLTrU7yySeBWoqne/PrrmvdxsaERNcSJ/h58Rzo=; b=UOx2Ga5jIaSgElqkV+otLwQfB7mpZhB7NsNJJoXqMTeIBjxEKq0NJePcg7gVANxwUU JjCHPAj/I+KR31pPAcTqERYdLd4Da3FappRWI9V0cpIeobJcTA6iedM7R6BjWybXkMbp 3rmpmXUCuF8d8m5F3taKawZdfUL+0BppJYbLopWVptu8lCcT7OLTjB5T9X3g4jwCC2EU KjAQTGQhC9ZkQzgf3BtF6BRABF4GVy6P0Au2SraIMhq7Ra3Gi6tvnOB5RwUhFH9+TWFj 81k1hIJE9C530I+u0upvzRkzxhZ2C2ELVivsQWY350dvEvrzjbMCNA1FNi/OJANjrkVY duyQ== X-Gm-Message-State: AKwxyteitIlRj1LdrNi2KvYpnTmgiV+WY/sbNbIttTGjrVvdPl8/o7UQ Q7HijyNxq+QaeUwHNfKhVSpMW1c1KeOyTd1AcH4uRQ== X-Google-Smtp-Source: AH8x224X2Ds3jAWZ9FVh6hTK1T/4tTcbrHNHfXIsKjpfZIu949bvkPcG2+VqgNmCX07/KG/bTNQ6n6p0IsCN3sBbmzE= X-Received: by 10.237.43.70 with SMTP id p64mr10739836qtd.5.1516815322086; Wed, 24 Jan 2018 09:35:22 -0800 (PST) MIME-Version: 1.0 Received: by 10.140.39.83 with HTTP; Wed, 24 Jan 2018 09:35:01 -0800 (PST) In-Reply-To: References: <744bbe18-80c4-d057-c88d-fbe480ee9abb@sentex.net> From: Peter Moody Date: Wed, 24 Jan 2018 09:35:01 -0800 Message-ID: Subject: Re: Ryzen issues on FreeBSD ? (summary of 4 issues) To: Alban Hertroys Cc: Mike Tancsa , Mark Millard , FreeBSD-STABLE Mailing List , Nimrod Levy Content-Type: text/plain; charset="UTF-8" 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, 24 Jan 2018 17:35:23 -0000 > I currently have a Ryzen 1600X from week 17/30, which suggests it will > have the bug. Unfortunately, I don't have it built into a system yet > as I'm waiting for DDR4 prices to become reasonable again before > ordering any, so I can't test it. I've seen the blanking screen lockup on a 1600X from 1739SUS and 1740SUS. Only with SMT enabled though. On the 1739 chip I'm also seeing cc segfaults on make -j 18 buildworld (again, just with SMT enabled). This is all so frustrating. > I'm not sure how solid this info is, should I RMA it without even > having tested that it has a problem? > > Alban Hertroys > -- > If you can't see the forest for the trees, > Cut the trees and you'll see there is no forest. > _______________________________________________ > 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 Wed Jan 24 17: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 09ED4EB7DAE for ; Wed, 24 Jan 2018 17:44:11 +0000 (UTC) (envelope-from ykhodo@gmail.com) Received: from mail-ua0-x233.google.com (mail-ua0-x233.google.com [IPv6:2607:f8b0:400c:c08::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 9076F6BD56 for ; Wed, 24 Jan 2018 17:44:10 +0000 (UTC) (envelope-from ykhodo@gmail.com) Received: by mail-ua0-x233.google.com with SMTP id n2so3229281uak.9 for ; Wed, 24 Jan 2018 09:44:10 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=+7IPD5+UUKbzMNapTwCRKWZcsSSKF7Jb1Wau9uDsURg=; b=ZE97vipdwjqdgOYTOpZOtYDI62L3CZoqDKCwAhXKLWc5AN8+F73B3AnwAXCbLBU5fj LUOYu3eqt9igZ/7yvjZs/jtQd9pDJsuztmFQLba3X/POg2nOLRl0u77/1gI0QYf7IUYf OSih+BhiHG/LCOBnuS8y2/Th8o7nHOJJE9DVHp+Sx4M/ldJo5SYXBtFjXShmBuFQfQn5 7Ow42kQ3HNRm9RDBYOhvOYrZ/oLgLwRKtt+RMClxCDkVR0suSUwcxTvuQNiXnAwBidEk G4jEkcBF8YufXdsXcyaOUMK2I06Vfi9KegEZyWWFx+KYwSVP+vwf2sxzRVmtxA4dIdB+ vYTQ== 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=+7IPD5+UUKbzMNapTwCRKWZcsSSKF7Jb1Wau9uDsURg=; b=CT/GfGFZFw/KIGZkXc0EAq0xRrBgvfyBgFW4NPEsrPsqcsv/3ourJ5GFSy3vN6bGge QsPvJ8deB2GLhX5B5iMgNI5z1lrn8sKCcHPGrkNSHdpDdW2VVdrrqNsoQM09VclgAchi weeFAkBWVxnvo2yXE3N8vBZhWrGpE57iZpaT4OOEBT/dl7lOfJDg8qGGbQRL5Tf5b9oO 2BYG18Xbt4Ewjgz+sV0ghy6+ndIxspg1SJe9y6q3hbPDJEYRpdHk0sg5GG0h6F8L8Zcb iAlMfgkyMh0svL0SCIHUpQtP9RDbAV/ZRYGLmwE7DFeen56t+yMh5swFNdF4zV2RLiXz r94Q== X-Gm-Message-State: AKwxyteMGMWAPsE+g0jeGo13CszGwN9v2cAa22kZZf4Ode8M84tj5zRz V9neROL3+ommWG6mXXLhbHjeefASsJvtZgy+8h8= X-Google-Smtp-Source: AH8x2251Kl3kmOEePP04KcZi7txRISHh7jtV8mE/evAXIKYNToyf6jKvliIVTQ42ceNryE6z6SaebGu4wPGOQ1bNpb0= X-Received: by 10.159.58.66 with SMTP id r2mr5512371uag.35.1516815850063; Wed, 24 Jan 2018 09:44:10 -0800 (PST) MIME-Version: 1.0 Received: by 10.159.51.72 with HTTP; Wed, 24 Jan 2018 09:44:09 -0800 (PST) In-Reply-To: References: <744bbe18-80c4-d057-c88d-fbe480ee9abb@sentex.net> From: Yuli Khodorkovskiy Date: Wed, 24 Jan 2018 12:44:09 -0500 Message-ID: Subject: Re: Ryzen issues on FreeBSD ? (summary of 4 issues) To: Peter Moody Cc: Alban Hertroys , Mark Millard , Nimrod Levy , FreeBSD-STABLE Mailing List 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, 24 Jan 2018 17:44:11 -0000 I am seeing the same behavior as you. Disabling SMT resolve freezing issues at idle. I am using a Ryzen 1700. On Wed, Jan 24, 2018 at 12:35 PM, Peter Moody wrote: > > I currently have a Ryzen 1600X from week 17/30, which suggests it will > > have the bug. Unfortunately, I don't have it built into a system yet > > as I'm waiting for DDR4 prices to become reasonable again before > > ordering any, so I can't test it. > > I've seen the blanking screen lockup on a 1600X from 1739SUS and > 1740SUS. Only with SMT enabled though. On the 1739 chip I'm also > seeing cc segfaults on make -j 18 buildworld (again, just with SMT > enabled). > > This is all so frustrating. > > > I'm not sure how solid this info is, should I RMA it without even > > having tested that it has a problem? > > > > Alban Hertroys > > -- > > If you can't see the forest for the trees, > > Cut the trees and you'll see there is no forest. > > _______________________________________________ > > 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 > " > _______________________________________________ > 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 Thu Jan 25 06:13:27 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 4D356EC1A60 for ; Thu, 25 Jan 2018 06:13:27 +0000 (UTC) (envelope-from bennett@sdf.org) Received: from mx.sdf.org (mx.sdf.org [205.166.94.20]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "ol.sdf.org", Issuer "ol.sdf.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id D0DD86D324; Thu, 25 Jan 2018 06:13:26 +0000 (UTC) (envelope-from bennett@sdf.org) Received: from sdf.org (IDENT:bennett@otaku.freeshell.org [205.166.94.9]) by mx.sdf.org (8.15.2/8.14.5) with ESMTPS id w0P6Cmiw010137 (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256 bits) verified NO); Thu, 25 Jan 2018 06:12:49 GMT Received: (from bennett@localhost) by sdf.org (8.15.2/8.12.8/Submit) id w0P6ClAr011958; Thu, 25 Jan 2018 00:12:47 -0600 (CST) From: Scott Bennett Message-Id: <201801250612.w0P6ClAr011958@sdf.org> Date: Thu, 25 Jan 2018 00:12:47 -0600 To: david@catwhisker.org, dim@FreeBSD.org Subject: Re: why does buildworld fail on stable/11 ? Cc: freebsd-stable@freebsd.org References: <201801240851.w0O8pnDl008705@sdf.org> <0A86F03E-DB69-4DD0-B67B-E9BFBE3DC739@FreeBSD.org> In-Reply-To: <0A86F03E-DB69-4DD0-B67B-E9BFBE3DC739@FreeBSD.org> User-Agent: Heirloom mailx 12.5 6/20/10 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii 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, 25 Jan 2018 06:13:27 -0000 Dimitry Andric wrote: > On 24 Jan 2018, at 09:51, Scott Bennett wrote: > > > > Subject: Re: why does buildworld fail on stable/11 ? > > > > I wrote: > >> On Mon, 22 Jan 2018 12:42:58 +0000 lists wrote: > >>> On 22/01/2018 09:17, Scott Bennett wrote: > >>>> Anyway, I'm stuck. Can someone please tell me what is going wrong and > >>>> how to fix it? I'd really like to be able to update my system, not only to > >>>> keep it reasonably current, but also to be able to customize a kernel. Thanks > >>>> in advance for any suggestions/solutions. > >>> > > [much deleted --SB] > >>> then > >>> > >>> [/usr/src #] make cleandir && make clean && make buildworld && make > >>> buildkernel && make installkernel && mergemaster -p > >> > >> At this point, that looks very optimistic, to say the least. :-) I've > >> tried "make cleanworld" (with /etc/make.conf still in place), and it failed > >> exactly like the buildworld example I posted before. > > > > Okay. Here's what happened. > > > > Script started on Wed Jan 24 02:17:30 2018 > > hellas# mv /etc/make.conf{,.save} > > hellas# mv /etc/src.conf{,.save} > > hellas# cd /usr/src > > hellas# make cleandir > > "/usr/src/share/mk/local.sys.mk", line 51: Malformed conditional (${.MAKE.MODE:Mmeta*} != "") > > "/usr/src/share/mk/local.sys.mk", line 58: Malformed conditional (${.MAKE.MODE:Mnofilemon} == "") > > "/usr/src/share/mk/local.sys.mk", line 76: if-less else > > "/usr/src/share/mk/local.sys.mk", line 79: if-less endif > > "/usr/src/share/mk/sys.mk", line 476: if-less endif > > bmake: fatal errors encountered -- cannot continue > > Looks like your make is broken. What is the output of "which make"? > hellas# echo $PATH /usr/local/libexec/ccache:/sbin:/bin:/usr/sbin:/usr/bin:/usr/games:/usr/local/sbin:/usr/local/bin:/root/bin hellas# which make /usr/bin/make hellas# file /usr/bin/make /usr/bin/make: ELF 64-bit LSB executable, x86-64, version 1 (FreeBSD), statically linked, for FreeBSD 11.1 (1101506), FreeBSD-style, stripped hellas# Thanks, both of you, for something to try. With enough ideas, maybe the problem can be uncovered. Scott Bennett, Comm. ASMELG, CFIAG ********************************************************************** * Internet: bennett at sdf.org *xor* bennett at freeshell.org * *--------------------------------------------------------------------* * "A well regulated and disciplined militia, is at all times a good * * objection to the introduction of that bane of all free governments * * -- a standing army." * * -- Gov. John Hancock, New York Journal, 28 January 1790 * ********************************************************************** From owner-freebsd-stable@freebsd.org Thu Jan 25 06:22:17 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 8FC06EC2274 for ; Thu, 25 Jan 2018 06:22:17 +0000 (UTC) (envelope-from bennett@sdf.org) Received: from mx.sdf.org (mx.sdf.org [205.166.94.20]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "ol.sdf.org", Issuer "ol.sdf.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 1CF0E6D874 for ; Thu, 25 Jan 2018 06:22:16 +0000 (UTC) (envelope-from bennett@sdf.org) Received: from sdf.org (IDENT:bennett@otaku.freeshell.org [205.166.94.9]) by mx.sdf.org (8.15.2/8.14.5) with ESMTPS id w0P6M3F6001337 (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256 bits) verified NO); Thu, 25 Jan 2018 06:22:03 GMT Received: (from bennett@localhost) by sdf.org (8.15.2/8.12.8/Submit) id w0P6M3Id020498; Thu, 25 Jan 2018 00:22:03 -0600 (CST) From: Scott Bennett Message-Id: <201801250622.w0P6M3Id020498@sdf.org> Date: Thu, 25 Jan 2018 00:22:02 -0600 To: tech-lists@zyxst.net Subject: Re: why does buildworld fail on stable/11 ? Cc: freebsd-stable@freebsd.org References: <201801240851.w0O8pnDl008705@sdf.org> In-Reply-To: User-Agent: Heirloom mailx 12.5 6/20/10 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii 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, 25 Jan 2018 06:22:17 -0000 tech-lists wrote: > On 24/01/2018 08:51, Scott Bennett wrote: > > hellas# mv /etc/make.conf{,.save} > > hellas# mv /etc/src.conf{,.save} > > hellas# cd /usr/src > > hellas# make cleandir > > "/usr/src/share/mk/local.sys.mk", line 51: Malformed conditional (${.MAKE.MODE:Mmeta*} != "") > > "/usr/src/share/mk/local.sys.mk", line 58: Malformed conditional (${.MAKE.MODE:Mnofilemon} == "") > > "/usr/src/share/mk/local.sys.mk", line 76: if-less else > > "/usr/src/share/mk/local.sys.mk", line 79: if-less endif > > "/usr/src/share/mk/sys.mk", line 476: if-less endif > > bmake: fatal errors encountered -- cannot continue > > *** Error code 1 > > Move the /usr/src somewhere else, make a new /usr/src dir and then > > svnlite co https://svn.FreeBSD.org/base/stable/11 /usr/src > > make sure it completes normally > > then cd into it and make cleandir. What happens? Before I do that, please answer my earlier question regarding svnlite vs. svn. The make is failing on a clean checkout of /usr/src, as I stated before. The only difference is that I used svn to do the checkout, not svnlite. If they give identical checkout output, then repeating that rather lengthy download would give an identical result and thus would serve no purpose. Scott Bennett, Comm. ASMELG, CFIAG ********************************************************************** * Internet: bennett at sdf.org *xor* bennett at freeshell.org * *--------------------------------------------------------------------* * "A well regulated and disciplined militia, is at all times a good * * objection to the introduction of that bane of all free governments * * -- a standing army." * * -- Gov. John Hancock, New York Journal, 28 January 1790 * ********************************************************************** From owner-freebsd-stable@freebsd.org Thu Jan 25 06:26: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 A42B8EC2700 for ; Thu, 25 Jan 2018 06:26:10 +0000 (UTC) (envelope-from bennett@sdf.org) Received: from mx.sdf.org (mx.sdf.org [205.166.94.20]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "ol.sdf.org", Issuer "ol.sdf.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 3658D6DA26; Thu, 25 Jan 2018 06:26:09 +0000 (UTC) (envelope-from bennett@sdf.org) Received: from sdf.org (IDENT:bennett@otaku.freeshell.org [205.166.94.9]) by mx.sdf.org (8.15.2/8.14.5) with ESMTPS id w0P6Pu54017507 (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256 bits) verified NO); Thu, 25 Jan 2018 06:25:56 GMT Received: (from bennett@localhost) by sdf.org (8.15.2/8.12.8/Submit) id w0P6Pukm014218; Thu, 25 Jan 2018 00:25:56 -0600 (CST) From: Scott Bennett Message-Id: <201801250625.w0P6Pukm014218@sdf.org> Date: Thu, 25 Jan 2018 00:25:56 -0600 To: ian@freebsd.org, dim@FreeBSD.org, bennett@sdf.org Subject: Re: why does buildworld fail on stable/11 ? Cc: tech-lists@zyxst.net, freebsd-stable@freebsd.org References: <201801240851.w0O8pnDl008705@sdf.org> <0A86F03E-DB69-4DD0-B67B-E9BFBE3DC739@FreeBSD.org> <1516811808.42536.173.camel@freebsd.org> In-Reply-To: <1516811808.42536.173.camel@freebsd.org> User-Agent: Heirloom mailx 12.5 6/20/10 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii 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, 25 Jan 2018 06:26:11 -0000 Ian Lepore wrote: > On Wed, 2018-01-24 at 12:39 +0100, Dimitry Andric wrote: > > On 24 Jan 2018, at 09:51, Scott Bennett wrote: > > > > > > > > > Subject: Re: why does buildworld fail on stable/11 ? > > > > > > ????I wrote: > > > > > > > > ???On Mon, 22 Jan 2018 12:42:58 +0000 lists wrote: > > > > > > > > > > On 22/01/2018 09:17, Scott Bennett wrote: > > > > > > > > > > > > ???Anyway, I'm stuck.??Can someone please tell me what is going wrong and > > > > > > how to fix it???I'd really like to be able to update my system, not only to > > > > > > keep it reasonably current, but also to be able to customize a kernel.??Thanks > > > > > > in advance for any suggestions/solutions. > > > ????[much deleted??--SB] > > > > > > > > > > > > > > then > > > > > > > > > > [/usr/src #] make cleandir && make clean && make buildworld && make > > > > > buildkernel && make installkernel && mergemaster -p > > > > ???At this point, that looks very optimistic, to say the least. :-)??I've > > > > tried "make cleanworld" (with /etc/make.conf still in place), and it failed > > > > exactly like the buildworld example I posted before. > > > ????Okay.??Here's what happened. > > > > > > Script started on Wed Jan 24 02:17:30 2018 > > > hellas# mv /etc/make.conf{,.save} > > > hellas# mv /etc/src.conf{,.save} > > > hellas# cd /usr/src > > > hellas# make cleandir > > > "/usr/src/share/mk/local.sys.mk", line 51: Malformed conditional (${.MAKE.MODE:Mmeta*} != "") > > > "/usr/src/share/mk/local.sys.mk", line 58: Malformed conditional (${.MAKE.MODE:Mnofilemon} == "") > > > "/usr/src/share/mk/local.sys.mk", line 76: if-less else > > > "/usr/src/share/mk/local.sys.mk", line 79: if-less endif > > > "/usr/src/share/mk/sys.mk", line 476: if-less endif > > > bmake: fatal errors encountered -- cannot continue > > Looks like your make is broken.??What is the output of "which make"? > > > > -Dimitry > > > > And also the output of "make -V MAKE_VERSION". ?To me, this looks a lot > like what happens when you try to use old fmake from freebsd 8 to build > modern freebsd source. > hellas# make -V MAKE_VERSION 20170720 hellas# Scott Bennett, Comm. ASMELG, CFIAG ********************************************************************** * Internet: bennett at sdf.org *xor* bennett at freeshell.org * *--------------------------------------------------------------------* * "A well regulated and disciplined militia, is at all times a good * * objection to the introduction of that bane of all free governments * * -- a standing army." * * -- Gov. John Hancock, New York Journal, 28 January 1790 * ********************************************************************** From owner-freebsd-stable@freebsd.org Thu Jan 25 12:40: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 0497CED56F2 for ; Thu, 25 Jan 2018 12:40:11 +0000 (UTC) (envelope-from tech-lists@zyxst.net) Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) (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 A1F787A2DD for ; Thu, 25 Jan 2018 12:40:10 +0000 (UTC) (envelope-from tech-lists@zyxst.net) Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id 1FE7620FAC; Thu, 25 Jan 2018 07:40:04 -0500 (EST) Received: from frontend2 ([10.202.2.161]) by compute4.internal (MEProxy); Thu, 25 Jan 2018 07:40:04 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=zyxst.net; h=cc :content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=fm1; bh=JTfMmSkDTRQfQEG4rReyLy+Xtt+af 1aH6+iS5OxJFZk=; b=NY0FD7VE95sjVk5vw1RTvsIhyhPnBxYYqooBJoYMsB46p CsplfojtsrlJnVVjCeI8F7uh689QgAnZDjFP3Lx/69KxrqiSz73gVGvs24nt1Xj1 PedYatkrbVahHftSFdXNO1rYK5HFbDM6DkGT2QVTJOVJFkI59PYeltkhVpD2+Dg+ l+e1360P+AUIkMfT7w5tQJgqIORWA1CzzGRlUhOm6OWwYan3rnyUOZEPUYq1wvqM dLNWhCdg+YnT15hAkAZ+T162jTDdSLg/KQktg9xKIqxjzqUWjiTNFUp4T3QNm3m/ qHyUSWMceOPojeRxSdkSoiQ8rIMXrdUiUSvys76wQ== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=JTfMmS kDTRQfQEG4rReyLy+Xtt+af1aH6+iS5OxJFZk=; b=saqopjkOTcYTZMHycTc+n2 eZxGwUg5URZ9k2EuaSc+N2EmVFTFrL9OX6NxM8MQmkJLOkMvAg0LL/aRvEp16q3v mD2P/Eu570snw1fp1ZELRnTIgAqI/Z7Z+pYO6wb44EShREADE7A7Ulp5FnEhfmTu YTajuS57xHQPxjKD+j1rBmhxx/pSBpULV/xoGEvA6lXPHe9YqowUUKiE236ujg1l 5GAXyMd4SQ5HPzMi+BEULSZE4TGKFUm2HdEyIEvnSxD/vik4PtXQ67Dff7qjbB9I /G4g/btin9GPtAOzHm8epGbU+684aervepLX0kfaaUrXDJ9G5AjxbvvNTQ6/r5ew == X-ME-Sender: Received: from desktop.parsley.growveg.org (parsley.growveg.org [82.70.91.97]) by mail.messagingengine.com (Postfix) with ESMTPA id 6832724636; Thu, 25 Jan 2018 07:40:03 -0500 (EST) Subject: Re: why does buildworld fail on stable/11 ? To: Scott Bennett Cc: freebsd-stable@freebsd.org References: <201801240851.w0O8pnDl008705@sdf.org> <201801250622.w0P6M3Id020498@sdf.org> From: tech-lists Message-ID: <5ff60dd8-734c-8b97-3dca-891910299be4@zyxst.net> Date: Thu, 25 Jan 2018 12:40:01 +0000 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.5.2 MIME-Version: 1.0 In-Reply-To: <201801250622.w0P6M3Id020498@sdf.org> Content-Type: text/plain; charset=utf-8 Content-Language: en-GB 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, 25 Jan 2018 12:40:11 -0000 On 25/01/2018 06:22, Scott Bennett wrote: > tech-lists wrote: > >> On 24/01/2018 08:51, Scott Bennett wrote: >>> hellas# mv /etc/make.conf{,.save} >>> hellas# mv /etc/src.conf{,.save} >>> hellas# cd /usr/src >>> hellas# make cleandir >>> "/usr/src/share/mk/local.sys.mk", line 51: Malformed conditional (${.MAKE.MODE:Mmeta*} != "") >>> "/usr/src/share/mk/local.sys.mk", line 58: Malformed conditional (${.MAKE.MODE:Mnofilemon} == "") >>> "/usr/src/share/mk/local.sys.mk", line 76: if-less else >>> "/usr/src/share/mk/local.sys.mk", line 79: if-less endif >>> "/usr/src/share/mk/sys.mk", line 476: if-less endif >>> bmake: fatal errors encountered -- cannot continue >>> *** Error code 1 >> >> Move the /usr/src somewhere else, make a new /usr/src dir and then >> >> svnlite co https://svn.FreeBSD.org/base/stable/11 /usr/src >> >> make sure it completes normally >> >> then cd into it and make cleandir. What happens? > > Before I do that, please answer my earlier question regarding svnlite > vs. svn. The make is failing on a clean checkout of /usr/src, as I stated *Was* it a *clean* checkout? Clearly, something is broken in at least /usr/local/share/mk if you're just running tools in base. > before. The only difference is that I used svn to do the checkout, not > svnlite. If they give identical checkout output, *If*. > then repeating that rather > lengthy download would give an identical result and thus would serve no > purpose. All I know is this: 1. You should be able to make buildworld et al with base tools, i.e. without any ports installed. You should be able to use ccache (I do) but for the purposes of debugging this, that's another uncontrolled variable. 2. I don't know the difference between svnlite and svn. All I know is that svnlite is in base and it will be in base for reasons and one of those reasons will be that it works reliably. I think svn in ports might be more featureful, but maybe it's more buggy because of it, maybe it does more - I don't know. In your position I'd like fewer unknowns. I mean, even make cleandir fails. In circumstances like that, the first thing I'd do is get fresh sources. I just ran a full checkout on 11.1-stable src which took about 9 minutes on a 19Mbit DSL: $ pwd /tmp/test $ date >>time.txt && svnlite co https://svn.FreeBSD.org/base/stable/11 /tmp/test && date >>time.txt [loads of output] A rescue/rescue/Makefile.depend A rescue/README A LOCKS U . Checked out revision 328393. $ cat time.txt Thu 25 Jan 2018 11:51:04 GMT Thu 25 Jan 2018 12:01:07 GMT $ make cleandir ===> lib (cleandir) ===> lib/csu (cleandir) ===> lib/csu/amd64 (cleandir) rm -f crt1.o crti.o crtn.o Scrt1.o gcrt1.o crt1.s gcrt1.s Scrt1.s rm -f .depend .depend.* GPATH GRTAGS GSYMS GTAGS ===> lib/libc (cleandir) rm -f tags gdtoa_strtorx.c gdtoa_dmisc.c gdtoa_dtoa.c gdtoa_gdtoa.c gdtoa_gethex.c gdtoa_gmisc.c gdtoa_hd_init.c gdtoa_hexnan.c gdtoa_misc.c gdtoa_smisc.c gdtoa_strtod.c gdtoa_strtodg.c gdtoa_strtof.c gdtoa_strtord.c gdtoa_sum.c gdtoa_ulp.c cancelpoints_sem.c cancelpoints_sem_new.c subr_acl_nfs4.c C99_Exit.c jemalloc [loads of output] $ which make /usr/bin/make $ file /usr/bin/make /usr/bin/make: ELF 64-bit LSB executable, x86-64, version 1 (FreeBSD), statically linked, for FreeBSD 11.1 (1101506), FreeBSD-style, stripped -- J. From owner-freebsd-stable@freebsd.org Thu Jan 25 13:49: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 39739ED8B76 for ; Thu, 25 Jan 2018 13:49:11 +0000 (UTC) (envelope-from nbe@renzel.net) Received: from nijmegen.renzel.net (mx1.renzel.net [195.243.213.130]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client CN "mail.renzel.net", Issuer "renzel.net Root CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id BC7C17D17F for ; Thu, 25 Jan 2018 13:49:10 +0000 (UTC) (envelope-from nbe@renzel.net) X-Virus-Scanned: GDATA Antivirus at gdata-milter.renzel.de.isb X-Spam-Score: 0 X-Spam-Level: X-Spam-Status: No, score=-8.0 required=7.0 tests=ALL_TRUSTED,BAYES_00 autolearn=ham version=3.3.2 Received: from dublin.vkf.isb.de.renzel.net (unknown [10.0.0.80]) by nijmegen.renzel.net (smtpd) with ESMTP id BCD1B1414876 for ; Thu, 25 Jan 2018 14:48:30 +0100 (CET) Received: from asbach.renzel.net (unknown [172.18.96.1]) by dublin.vkf.isb.de.renzel.net (Postfix) with ESMTPA id B6B03867B3 for ; Thu, 25 Jan 2018 14:48:30 +0100 (CET) Subject: Re: Ryzen issues on FreeBSD ? References: <8e842dec-ade7-37d1-6bd8-856ea1a827ca@sentex.net> To: freebsd-stable@freebsd.org From: Nils Beyer Message-ID: <8c8e458b-8ddd-08e6-1d2e-487d95583790@renzel.net> Date: Thu, 25 Jan 2018 14:48:30 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.5.2 MIME-Version: 1.0 In-Reply-To: <8e842dec-ade7-37d1-6bd8-856ea1a827ca@sentex.net> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on nijmegen.renzel.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, 25 Jan 2018 13:49:11 -0000 On 01/17/18 14:38, Mike Tancsa wrote: > However, we are seeing random lockups on both boxes. [...] go into your BIOS: - load default settings - disable SMT - disable Cool&Quiet - disable global C-state control - disable anything with C-states only with SMT _and_ Cool&Quiet _and_ C-state-stuff all together disabled, my system is still running (uptime now is 49 days). Every other fiddling around with RAM, PSU and timing settings is fruitless. Before, my system locked up after a run time of six to ten days. And, yes, I have a replacement CPU and the shared page fix active - these didn't help. This does not help with your compilation problems though... BR, Nils From owner-freebsd-stable@freebsd.org Thu Jan 25 14:00:35 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 EE309ED940A for ; Thu, 25 Jan 2018 14:00:34 +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 452387DA58 for ; Thu, 25 Jan 2018 14:00:34 +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 w0PE0Xce075671 (version=TLSv1 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for ; Thu, 25 Jan 2018 09:00:33 -0500 (EST) (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 w0PE0V6Q074247; Thu, 25 Jan 2018 09:00:31 -0500 (EST) (envelope-from mike@sentex.net) Subject: Re: Ryzen issues on FreeBSD ? To: Nils Beyer , freebsd-stable@freebsd.org References: <8e842dec-ade7-37d1-6bd8-856ea1a827ca@sentex.net> <8c8e458b-8ddd-08e6-1d2e-487d95583790@renzel.net> From: Mike Tancsa Organization: Sentex Communications Message-ID: Date: Thu, 25 Jan 2018 09:00:30 -0500 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.5.2 MIME-Version: 1.0 In-Reply-To: <8c8e458b-8ddd-08e6-1d2e-487d95583790@renzel.net> 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: Thu, 25 Jan 2018 14:00:35 -0000 On 1/25/2018 8:48 AM, Nils Beyer wrote: > > And, yes, I have a replacement CPU and the shared page fix active - > these didn't help. > > This does not help with your compilation problems though... > Thanks. So you see the same or similar compile issues too ? ---Mike -- ------------------- Mike Tancsa, tel +1 519 651 3400 Sentex Communications, mike@sentex.net Providing Internet services since 1994 www.sentex.net Cambridge, Ontario Canada http://www.tancsa.com/ From owner-freebsd-stable@freebsd.org Thu Jan 25 14:03: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 CDA4FED97D6 for ; Thu, 25 Jan 2018 14:03:15 +0000 (UTC) (envelope-from nbe@renzel.net) Received: from nijmegen.renzel.net (mx1.renzel.net [195.243.213.130]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client CN "mail.renzel.net", Issuer "renzel.net Root CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 6CB067DF2A for ; Thu, 25 Jan 2018 14:03:14 +0000 (UTC) (envelope-from nbe@renzel.net) X-Virus-Scanned: GDATA Antivirus at gdata-milter.renzel.de.isb X-Spam-Score: 0 X-Spam-Level: X-Spam-Status: No, score=-8.0 required=7.0 tests=ALL_TRUSTED,BAYES_00 autolearn=ham version=3.3.2 Received: from dublin.vkf.isb.de.renzel.net (unknown [10.0.0.80]) by nijmegen.renzel.net (smtpd) with ESMTP id DD3FA141482F; Thu, 25 Jan 2018 15:03:11 +0100 (CET) Received: from asbach.renzel.net (unknown [172.18.96.1]) by dublin.vkf.isb.de.renzel.net (Postfix) with ESMTPA id CA71086A19; Thu, 25 Jan 2018 15:03:11 +0100 (CET) Subject: Re: Ryzen issues on FreeBSD ? To: Mike Tancsa , freebsd-stable@freebsd.org References: <8e842dec-ade7-37d1-6bd8-856ea1a827ca@sentex.net> <8c8e458b-8ddd-08e6-1d2e-487d95583790@renzel.net> From: Nils Beyer Organization: VKF Renzel GmbH Message-ID: Date: Thu, 25 Jan 2018 15:03:11 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.5.2 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-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on nijmegen.renzel.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, 25 Jan 2018 14:03:16 -0000 On 01/25/18 15:00, Mike Tancsa wrote: >> This does not help with your compilation problems though... > > Thanks. So you see the same or similar compile issues too ? slightly: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219399 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221029 From owner-freebsd-stable@freebsd.org Thu Jan 25 15:13: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 EBCD1EB4866 for ; Thu, 25 Jan 2018 15:13:29 +0000 (UTC) (envelope-from ian@freebsd.org) Received: from pmta2.delivery6.ore.mailhop.org (pmta2.delivery6.ore.mailhop.org [54.200.129.228]) (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 79A23812F9 for ; Thu, 25 Jan 2018 15:13:28 +0000 (UTC) (envelope-from ian@freebsd.org) X-MHO-User: 45a5a537-01e2-11e8-b951-f99fef315fd9 X-Report-Abuse-To: https://support.duocircle.com/support/solutions/articles/5000540958-duocircle-standard-smtp-abuse-information X-Originating-IP: 73.78.92.27 X-Mail-Handler: DuoCircle Outbound SMTP Received: from ilsoft.org (unknown [73.78.92.27]) by outbound2.ore.mailhop.org (Halon) with ESMTPSA id 45a5a537-01e2-11e8-b951-f99fef315fd9; Thu, 25 Jan 2018 15:13:18 +0000 (UTC) Received: from rev (rev [172.22.42.240]) by ilsoft.org (8.15.2/8.15.2) with ESMTP id w0PFDJ9T011461; Thu, 25 Jan 2018 08:13:19 -0700 (MST) (envelope-from ian@freebsd.org) Message-ID: <1516893199.42536.223.camel@freebsd.org> Subject: Re: why does buildworld fail on stable/11 ? From: Ian Lepore To: Scott Bennett , dim@FreeBSD.org Cc: freebsd-stable@freebsd.org, tech-lists@zyxst.net Date: Thu, 25 Jan 2018 08:13:19 -0700 In-Reply-To: <201801250625.w0P6Pukm014218@sdf.org> References: <201801240851.w0O8pnDl008705@sdf.org> <0A86F03E-DB69-4DD0-B67B-E9BFBE3DC739@FreeBSD.org> <1516811808.42536.173.camel@freebsd.org> <201801250625.w0P6Pukm014218@sdf.org> Content-Type: text/plain; charset="ISO-8859-1" X-Mailer: Evolution 3.18.5.1 FreeBSD GNOME Team Port Mime-Version: 1.0 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, 25 Jan 2018 15:13:30 -0000 On Thu, 2018-01-25 at 00:25 -0600, Scott Bennett wrote: > Ian Lepore wrote: > > > > > On Wed, 2018-01-24 at 12:39 +0100, Dimitry Andric wrote: > > > > > > On 24 Jan 2018, at 09:51, Scott Bennett wrote: > > > > > > > > > > > > > > > > Subject: Re: why does buildworld fail on stable/11 ? > > > > > > > > ????I wrote: > > > > > > > > > > > > > > > ???On Mon, 22 Jan 2018 12:42:58 +0000 lists wrote: > > > > > > > > > > > > > > > > > > On 22/01/2018 09:17, Scott Bennett wrote: > > > > > > > > > > > > > > > > > > > > > ???Anyway, I'm stuck.??Can someone please tell me what is going wrong and > > > > > > > how to fix it???I'd really like to be able to update my system, not only to > > > > > > > keep it reasonably current, but also to be able to customize a kernel.??Thanks > > > > > > > in advance for any suggestions/solutions. > > > > ????[much deleted??--SB] > > > > > > > > > > > > > > > > > > > > > > > > > > > > then > > > > > > > > > > > > [/usr/src #] make cleandir && make clean && make buildworld && make > > > > > > buildkernel && make installkernel && mergemaster -p > > > > > ???At this point, that looks very optimistic, to say the least. :-)??I've > > > > > tried "make cleanworld" (with /etc/make.conf still in place), and it failed > > > > > exactly like the buildworld example I posted before. > > > > ????Okay.??Here's what happened. > > > > > > > > Script started on Wed Jan 24 02:17:30 2018 > > > > hellas# mv /etc/make.conf{,.save} > > > > hellas# mv /etc/src.conf{,.save} > > > > hellas# cd /usr/src > > > > hellas# make cleandir > > > > "/usr/src/share/mk/local.sys.mk", line 51: Malformed conditional (${.MAKE.MODE:Mmeta*} != "") > > > > "/usr/src/share/mk/local.sys.mk", line 58: Malformed conditional (${.MAKE.MODE:Mnofilemon} == "") > > > > "/usr/src/share/mk/local.sys.mk", line 76: if-less else > > > > "/usr/src/share/mk/local.sys.mk", line 79: if-less endif > > > > "/usr/src/share/mk/sys.mk", line 476: if-less endif > > > > bmake: fatal errors encountered -- cannot continue > > > Looks like your make is broken.??What is the output of "which make"? > > > > > > -Dimitry > > > > > And also the output of "make -V MAKE_VERSION". ?To me, this looks a lot > > like what happens when you try to use old fmake from freebsd 8 to build > > modern freebsd source. > > > hellas# make -V MAKE_VERSION > 20170720 > hellas# Well, that kills the wrong-version theory.  The thing I would try next is setting some make debug flags, but it'll generate a ton of output. I'd start with "make -dlp cleandir" that should list everything it's doing while reading makefiles, and list any commands it executes.  Capture that output (stdout and stderr), then a good first-look at the file might be something like "grep -v ParseReadLine make.log", that should show us what files it's reading from which directories.  My theory is maybe it's picking up a wrong include file somehow which leads it astray.  If that's not it, we may need to also examine all the ParseReadLine stuff, or add some other debug flags. -- Ian From owner-freebsd-stable@freebsd.org Thu Jan 25 15:18: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 56A06EB4D92 for ; Thu, 25 Jan 2018 15:18:16 +0000 (UTC) (envelope-from ian@freebsd.org) Received: from outbound1a.eu.mailhop.org (outbound1a.eu.mailhop.org [52.58.109.202]) (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 D6F1F81720 for ; Thu, 25 Jan 2018 15:18:15 +0000 (UTC) (envelope-from ian@freebsd.org) X-MHO-User: f126e879-01e2-11e8-91c6-33ffc249f3e8 X-Report-Abuse-To: https://support.duocircle.com/support/solutions/articles/5000540958-duocircle-standard-smtp-abuse-information X-Originating-IP: 73.78.92.27 X-Mail-Handler: DuoCircle Outbound SMTP Received: from ilsoft.org (unknown [73.78.92.27]) by outbound1.eu.mailhop.org (Halon) with ESMTPSA id f126e879-01e2-11e8-91c6-33ffc249f3e8; Thu, 25 Jan 2018 15:18:06 +0000 (UTC) Received: from rev (rev [172.22.42.240]) by ilsoft.org (8.15.2/8.15.2) with ESMTP id w0PFI5Av011476; Thu, 25 Jan 2018 08:18:05 -0700 (MST) (envelope-from ian@freebsd.org) Message-ID: <1516893485.42536.226.camel@freebsd.org> Subject: Re: why does buildworld fail on stable/11 ? From: Ian Lepore To: tech-lists , Scott Bennett Cc: freebsd-stable@freebsd.org Date: Thu, 25 Jan 2018 08:18:05 -0700 In-Reply-To: <5ff60dd8-734c-8b97-3dca-891910299be4@zyxst.net> References: <201801240851.w0O8pnDl008705@sdf.org> <201801250622.w0P6M3Id020498@sdf.org> <5ff60dd8-734c-8b97-3dca-891910299be4@zyxst.net> Content-Type: text/plain; charset="ISO-8859-1" X-Mailer: Evolution 3.18.5.1 FreeBSD GNOME Team Port Mime-Version: 1.0 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, 25 Jan 2018 15:18:16 -0000 On Thu, 2018-01-25 at 12:40 +0000, tech-lists wrote: > 2. I don't know the difference between svnlite and svn. All I know is > that svnlite is in base and it will be in base for reasons and one of > those reasons will be that it works reliably. I think svn in ports might > be more featureful, but maybe it's more buggy because of it, maybe it > does more - I don't know. In your position I'd like fewer unknowns. I > mean, even make cleandir fails. In circumstances like that, the first > thing I'd do is get fresh sources. The svn in ports is what freebsd committers use.  It works fine.   svnlite is basically the full svn without the support for things like perl and python plugins so that base freebsd doesn't have dependencies on those things. -- Ian From owner-freebsd-stable@freebsd.org Thu Jan 25 19:55: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 851A2EC9728 for ; Thu, 25 Jan 2018 19:55:15 +0000 (UTC) (envelope-from raysnyder@lpleads.net) Received: from server1.lpsalesleads.com (server1.lpsalesleads.com [107.161.94.35]) by mx1.freebsd.org (Postfix) with ESMTP id 2A5D56E248 for ; Thu, 25 Jan 2018 19:55:14 +0000 (UTC) (envelope-from raysnyder@lpleads.net) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; s=asdzxcv; d=lpleads.net; h=MIME-Version:From:Reply-To:To:Subject:Content-Type:Content-Transfer-Encoding:Date:Message-ID; i=raysnyder@lpleads.net; bh=OhrR51ATCpTtaknX+8BmDNL098c=; b=WAXFAUISUFBbbdGvzW7sYfCRs74WlfWf30kPM2ZdpAmiz4i1zOyWx2BPwQE8cHazgfzV6DOgGFPE J32+UyUcYeywVCEMKMmaU+P6+W+4g0mvmZOkAjI7OgoMCaRF4Wsg3b+NPsyoaPxkzaQFZaOwyYD4 K41I8PO0hhL6ysGYl9w= DomainKey-Signature: a=rsa-sha1; c=nofws; q=dns; s=asdzxcv; d=lpleads.net; b=gfdPKDIHZ7UvzGOancZKgJ3LsDhP+kl/4/4afvPejg4pJwyPkUTlYD5oR8pk/VjB0EpKmFTPEuLm Ee8plDlJUh58DzlIXFMNmhvYW2amdJmV5JF+M3AZ0KkJAIUgQHscNpEl40C8FcstMmEfnBkqjm2A H3lSKZ7B6GFHCOge4GI=; From: "Ray Snyder" Reply-To: raysnyder@lpleads.net To: freebsd-stable@freebsd.org Subject: Marketring List-2018 X-Mailer: Smart_Send_2_0_132 Date: Thu, 25 Jan 2018 13:45:01 -0600 Message-ID: <12521298916401182715380@user8-PC> MIME-Version: 1.0 Content-Type: text/plain 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, 25 Jan 2018 19:55:15 -0000 From owner-freebsd-stable@freebsd.org Fri Jan 26 08:05:05 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 2D978EC8780 for ; Fri, 26 Jan 2018 08:05:05 +0000 (UTC) (envelope-from bennett@sdf.org) Received: from mx.sdf.org (ol.sdf.org [205.166.94.20]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "ol.sdf.org", Issuer "ol.sdf.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 8AAFA68599; Fri, 26 Jan 2018 08:05:03 +0000 (UTC) (envelope-from bennett@sdf.org) Received: from sdf.org (IDENT:bennett@otaku.freeshell.org [205.166.94.9]) by mx.sdf.org (8.15.2/8.14.5) with ESMTPS id w0Q84tXv002994 (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256 bits) verified NO); Fri, 26 Jan 2018 08:04:55 GMT Received: (from bennett@localhost) by sdf.org (8.15.2/8.12.8/Submit) id w0Q84t2f018882; Fri, 26 Jan 2018 02:04:55 -0600 (CST) From: Scott Bennett Message-Id: <201801260804.w0Q84t2f018882@sdf.org> Date: Fri, 26 Jan 2018 02:04:55 -0600 To: ian@freebsd.org, dim@FreeBSD.org, bennett@sdf.org Subject: Re: why does buildworld fail on stable/11 ? Cc: tech-lists@zyxst.net, freebsd-stable@freebsd.org References: <201801240851.w0O8pnDl008705@sdf.org> <0A86F03E-DB69-4DD0-B67B-E9BFBE3DC739@FreeBSD.org> <1516811808.42536.173.camel@freebsd.org> <201801250625.w0P6Pukm014218@sdf.org> <1516893199.42536.223.camel@freebsd.org> In-Reply-To: <1516893199.42536.223.camel@freebsd.org> User-Agent: Heirloom mailx 12.5 6/20/10 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii 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: Fri, 26 Jan 2018 08:05:05 -0000 Ian Lepore wrote: > On Thu, 2018-01-25 at 00:25 -0600, Scott Bennett wrote: > > Ian Lepore wrote: > > > > > > > > On Wed, 2018-01-24 at 12:39 +0100, Dimitry Andric wrote: > > > > > > > > On 24 Jan 2018, at 09:51, Scott Bennett wrote: > > > > > > > > > > > > > > > > > > > > Subject: Re: why does buildworld fail on stable/11 ? > > > > > > > > > > ????I wrote: > > > > > > > > > > > > > > > > > > ???On Mon, 22 Jan 2018 12:42:58 +0000 lists wrote: > > > > > > > > > > > > > > > > > > > > > On 22/01/2018 09:17, Scott Bennett wrote: > > > > > > > > > > > > > > > > > > > > > > > > ???Anyway, I'm stuck.??Can someone please tell me what is going wrong and > > > > > > > > how to fix it???I'd really like to be able to update my system, not only to > > > > > > > > keep it reasonably current, but also to be able to customize a kernel.??Thanks > > > > > > > > in advance for any suggestions/solutions. > > > > > ????[much deleted??--SB] > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > then > > > > > > > > > > > > > > [/usr/src #] make cleandir && make clean && make buildworld && make > > > > > > > buildkernel && make installkernel && mergemaster -p > > > > > > ???At this point, that looks very optimistic, to say the least. :-)??I've > > > > > > tried "make cleanworld" (with /etc/make.conf still in place), and it failed > > > > > > exactly like the buildworld example I posted before. > > > > > ????Okay.??Here's what happened. > > > > > > > > > > Script started on Wed Jan 24 02:17:30 2018 > > > > > hellas# mv /etc/make.conf{,.save} > > > > > hellas# mv /etc/src.conf{,.save} > > > > > hellas# cd /usr/src > > > > > hellas# make cleandir > > > > > "/usr/src/share/mk/local.sys.mk", line 51: Malformed conditional (${.MAKE.MODE:Mmeta*} != "") > > > > > "/usr/src/share/mk/local.sys.mk", line 58: Malformed conditional (${.MAKE.MODE:Mnofilemon} == "") > > > > > "/usr/src/share/mk/local.sys.mk", line 76: if-less else > > > > > "/usr/src/share/mk/local.sys.mk", line 79: if-less endif > > > > > "/usr/src/share/mk/sys.mk", line 476: if-less endif > > > > > bmake: fatal errors encountered -- cannot continue > > > > Looks like your make is broken.??What is the output of "which make"? > > > > > > > > -Dimitry > > > > > > > And also the output of "make -V MAKE_VERSION". ?To me, this looks a lot > > > like what happens when you try to use old fmake from freebsd 8 to build > > > modern freebsd source. > > > > > hellas# make -V MAKE_VERSION > > 20170720 > > hellas# > > Well, that kills the wrong-version theory. ?The thing I would try next > is setting some make debug flags, but it'll generate a ton of output. > > I'd start with "make -dlp cleandir" that should list everything it's > doing while reading makefiles, and list any commands it executes. > ?Capture that output (stdout and stderr), then a good first-look at the > file might be something like "grep -v?ParseReadLine make.log", that > should show us what files it's reading from which directories. ?My > theory is maybe it's picking up a wrong include file somehow which > leads it astray. ?If that's not it, we may need to also examine all the > ParseReadLine stuff, or add some other debug flags. > Okay. If you really want all of it, let me know, and I'll email it to you directly. Here are the last 50 lines or so of it. # .MAIN, flags 0, type 1, made 0 # _guard, flags 0, type 0, made 0 ParseDoDependency(_guard: .PHONY) ParseDoDependency(world: .PHONY) ParseDoDependency(kernel: buildkernel installkernel .PHONY) # ParseLinkSrc: added child kernel - buildkernel # kernel, flags 0, type 1, made 0 # buildkernel, flags 0, type 8010201, made 0 # ParseLinkSrc: added child kernel - installkernel # kernel, flags 0, type 1, made 0 # installkernel, flags 0, type 8010201, made 0 ParseDoDependency(upgrade_checks: .PHONY) ParseDoDependency(bmake: .PHONY) ParseDoDependency(regress: .PHONY) ParseDoDependency(tinderbox toolchains kernel-toolchains kernels worlds: upgrade_checks) # ParseLinkSrc: added child tinderbox - upgrade_checks # tinderbox, flags 0, type 201, made 0 # upgrade_checks, flags 0, type 10001, made 0 # ParseLinkSrc: added child toolchains - upgrade_checks # toolchains, flags 0, type 201, made 0 # upgrade_checks, flags 0, type 10001, made 0 # ParseLinkSrc: added child kernel-toolchains - upgrade_checks # kernel-toolchains, flags 0, type 201, made 0 # upgrade_checks, flags 0, type 10001, made 0 # ParseLinkSrc: added child kernels - upgrade_checks # kernels, flags 0, type 1, made 0 # upgrade_checks, flags 0, type 10001, made 0 # ParseLinkSrc: added child worlds - upgrade_checks # worlds, flags 0, type 1, made 0 # upgrade_checks, flags 0, type 10001, made 0 ParseDoDependency(tinderbox: .PHONY) ParseDoDependency(toolchains: .PHONY) ParseDoDependency(kernel-toolchains: .PHONY) ParseDoDependency(kernels: .PHONY) ParseDoDependency(worlds: .PHONY) ParseDoDependency(buildLINT: .PHONY) cd /usr/src; PATH=/sbin:/bin:/usr/sbin:/usr/bin MAKE_CMD=make /usr/obj/usr/src/make.amd64/bmake -m /usr/src/share/mk -f Makefile.inc1 TARGET=amd64 TARGET_ARCH=amd64 MK_META_MODE=no cleandir bmake: illegal argument to d option -- p usage: make [-BPSXeiknpqrstv] [-C directory] [-D variable] [-d flags] [-E variable] [-f makefile] [-I directory] [-j max_jobs] [-m directory] [-V variable] [variable=value] [target ...] *** Error code 2 Stop. make: stopped in /usr/src hellas# exit exit Script done on Fri Jan 26 01:33:18 2018 Scott Bennett, Comm. ASMELG, CFIAG ********************************************************************** * Internet: bennett at sdf.org *xor* bennett at freeshell.org * *--------------------------------------------------------------------* * "A well regulated and disciplined militia, is at all times a good * * objection to the introduction of that bane of all free governments * * -- a standing army." * * -- Gov. John Hancock, New York Journal, 28 January 1790 * ********************************************************************** From owner-freebsd-stable@freebsd.org Fri Jan 26 09:56:36 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 84471ECD144 for ; Fri, 26 Jan 2018 09:56:36 +0000 (UTC) (envelope-from Holger.Kipp@alogis.com) Received: from alogis.com (firewall.alogis.com [212.184.102.1]) (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 03C276BED2; Fri, 26 Jan 2018 09:56:35 +0000 (UTC) (envelope-from Holger.Kipp@alogis.com) Received: from alogis.com with ESMTP id w0Q9qphq019340; Fri, 26 Jan 2018 10:52:52 +0100 From: Holger Kipp To: Scott Bennett CC: Ian Lepore , "dim@FreeBSD.org" , "freebsd-stable@freebsd.org" , "tech-lists@zyxst.net" Subject: Re: why does buildworld fail on stable/11 ? Thread-Topic: why does buildworld fail on stable/11 ? Thread-Index: AQHTlPCSWTcTNS/45U2pJk7s7VKmaqOC1V+AgABTCgCAAOepAIAAk1mAgAEao4CAAB4nAA== Date: Fri, 26 Jan 2018 09:52:50 +0000 Message-ID: <054FD748-B28B-4573-BF50-2E77D8C3C793@alogis.com> References: <201801240851.w0O8pnDl008705@sdf.org> <0A86F03E-DB69-4DD0-B67B-E9BFBE3DC739@FreeBSD.org> <1516811808.42536.173.camel@freebsd.org> <201801250625.w0P6Pukm014218@sdf.org> <1516893199.42536.223.camel@freebsd.org> <201801260804.w0Q84t2f018882@sdf.org> In-Reply-To: <201801260804.w0Q84t2f018882@sdf.org> Accept-Language: de-DE, en-GB, en-US Content-Language: de-DE X-MS-Has-Attach: yes X-MS-TNEF-Correlator: x-originating-ip: [10.1.1.31] MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable 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, 26 Jan 2018 09:56:37 -0000 Dear Scott, Am 26.01.2018 um 09:07 schrieb Scott Bennett >: cd /usr/src; PATH=3D/sbin:/bin:/usr/sbin:/usr/bin MAKE_CMD=3Dmake /usr/obj/= usr/src/make.amd64/bmake -m /usr/src/share/mk -f Makefile.inc1 TARGET=3Damd= 64 TARGET_ARCH=3Damd64 MK_META_MODE=3Dno cleandir bmake: illegal argument to d option -- p usage: make [-BPSXeiknpqrstv] [-C directory] [-D variable] [-d flags] [-E variable] [-f makefile] [-I directory] [-j max_jobs] [-m directory] [-V variable] [variable=3Dvalue] [target ...] *** Error code 2 Stop. make: stopped in /usr/src hellas# exit exit Script done on Fri Jan 26 01:33:18 2018 Scott Bennett, Comm. ASMELG, CFIAG This sound similar to an issue with make in 2013: 20130613: Some people report the following error after the switch to bmake: make: illegal option -- J usage: make [-BPSXeiknpqrstv] [-C directory] [-D variable] ... *** [buildworld] Error code 2 this likely due to an old instance of make in ${MAKEPATH} (${MAKEOBJDIRPREFIX}${.CURDIR}/make.${MACHINE}) which src/Makefile will use that blindly, if it exists, so if you see the above error: rm -rf `make -V MAKEPATH` should resolve it. Can you check if you have an older version of make in your makepath and del= ete / rename it? Best regards, Holger Diplom-Mathematiker Holger Kipp Senior Consultant [When logistics needs SAP competence] Fon: +49 30 436 58 114 Fax: +49 30 436 58 214 Mobil:?+49 178 36 58 114 alogis AG Alt-Moabit 90 B 10559 Berlin holger.kipp@alogis.com www.alogis.com alogis AG Sitz/Registergericht: Berlin/AG Charlottenburg, HRB 71484 Vorstand: Arne Friedrichs, Joern Samuelson Aufsichtsratsvorsitzender: Dirk Nedderhoff [Spenden statt schenken mit alogis!] From owner-freebsd-stable@freebsd.org Fri Jan 26 16:33: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 B6F67EDE964 for ; Fri, 26 Jan 2018 16:33:26 +0000 (UTC) (envelope-from ian@freebsd.org) Received: from outbound1b.ore.mailhop.org (outbound1b.ore.mailhop.org [54.200.247.200]) (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 3FE267A257 for ; Fri, 26 Jan 2018 16:33:25 +0000 (UTC) (envelope-from ian@freebsd.org) X-MHO-User: 9c52d0fa-02b6-11e8-bb8e-b35b57339d60 X-Report-Abuse-To: https://support.duocircle.com/support/solutions/articles/5000540958-duocircle-standard-smtp-abuse-information X-Originating-IP: 73.78.92.27 X-Mail-Handler: DuoCircle Outbound SMTP Received: from ilsoft.org (unknown [73.78.92.27]) by outbound1.ore.mailhop.org (Halon) with ESMTPSA id 9c52d0fa-02b6-11e8-bb8e-b35b57339d60; Fri, 26 Jan 2018 16:33:17 +0000 (UTC) Received: from rev (rev [172.22.42.240]) by ilsoft.org (8.15.2/8.15.2) with ESMTP id w0QGXHWD013949; Fri, 26 Jan 2018 09:33:17 -0700 (MST) (envelope-from ian@freebsd.org) Message-ID: <1516984397.42536.245.camel@freebsd.org> Subject: Re: why does buildworld fail on stable/11 ? From: Ian Lepore To: Holger Kipp , Scott Bennett Cc: "freebsd-stable@freebsd.org" , "dim@FreeBSD.org" , "tech-lists@zyxst.net" Date: Fri, 26 Jan 2018 09:33:17 -0700 In-Reply-To: <054FD748-B28B-4573-BF50-2E77D8C3C793@alogis.com> References: <201801240851.w0O8pnDl008705@sdf.org> <0A86F03E-DB69-4DD0-B67B-E9BFBE3DC739@FreeBSD.org> <1516811808.42536.173.camel@freebsd.org> <201801250625.w0P6Pukm014218@sdf.org> <1516893199.42536.223.camel@freebsd.org> <201801260804.w0Q84t2f018882@sdf.org> <054FD748-B28B-4573-BF50-2E77D8C3C793@alogis.com> Content-Type: text/plain; charset="ISO-8859-1" X-Mailer: Evolution 3.18.5.1 FreeBSD GNOME Team Port Mime-Version: 1.0 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: Fri, 26 Jan 2018 16:33:26 -0000 On Fri, 2018-01-26 at 09:52 +0000, Holger Kipp wrote: > Dear Scott, > > Am 26.01.2018 um 09:07 schrieb Scott Bennett >: > > cd /usr/src; PATH=/sbin:/bin:/usr/sbin:/usr/bin MAKE_CMD=make /usr/obj/usr/src/make.amd64/bmake -m /usr/src/share/mk -f Makefile.inc1 TARGET=amd64 TARGET_ARCH=amd64 MK_META_MODE=no cleandir > bmake: illegal argument to d option -- p > usage: make [-BPSXeiknpqrstv] [-C directory] [-D variable] > [-d flags] [-E variable] [-f makefile] [-I directory] > [-j max_jobs] [-m directory] [-V variable] > [variable=value] [target ...] > *** Error code 2 > > Stop. > make: stopped in /usr/src > hellas# exit > exit > > Script done on Fri Jan 26 01:33:18 2018 > > >                                  Scott Bennett, Comm. ASMELG, CFIAG > > This sound similar to an issue with make in 2013: > > 20130613: > Some people report the following error after the switch to bmake: > > make: illegal option -- J > usage: make [-BPSXeiknpqrstv] [-C directory] [-D variable] > ... > *** [buildworld] Error code 2 > > this likely due to an old instance of make in > ${MAKEPATH} (${MAKEOBJDIRPREFIX}${.CURDIR}/make.${MACHINE}) > which src/Makefile will use that blindly, if it exists, so if > you see the above error: > > rm -rf `make -V MAKEPATH` > > should resolve it. > > Can you check if you have an older version of make in your makepath and delete / rename it? > Yep, it's definitely running a bad old version of make, and the thought that it's using /usr/obj/usr/src/make.amd64/bmake even though it's not up to date fits the symptoms.  I'm a bit confused by the "rm -rf" command at the end... when I do make -V MAKEPATH I get nothing, so the rm command would just be an error -- since that's from UPDATING in 2013, I'm thinking it may be out of date advice now. I think the right fix here is probably "rm -rf /usr/obj/*" followed by a make buildworld. -- Ian From owner-freebsd-stable@freebsd.org Fri Jan 26 18:26: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 2DB8DEC19E3 for ; Fri, 26 Jan 2018 18:26:40 +0000 (UTC) (envelope-from caron.wallace@frankmethods.com) Received: from mail-io0-x247.google.com (mail-io0-x247.google.com [IPv6:2607:f8b0:4001:c06::247]) (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 B562C80CE2 for ; Fri, 26 Jan 2018 18:26:39 +0000 (UTC) (envelope-from caron.wallace@frankmethods.com) Received: by mail-io0-x247.google.com with SMTP id v5so1198893iog.10 for ; Fri, 26 Jan 2018 10:26:39 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=frankmethods-com.20150623.gappssmtp.com; s=20150623; h=mime-version:message-id:date:subject:from:to; bh=iBVktNsxJogLLE/EFf9T/E8t14+rTiJvgRxub4BdF8g=; b=WacBKcvdi3vrh8NKUXYeME1F2ZA6X7GTKNRWH903jWLln5jEw59qkXy9Isg3wnRwcq WNO2+ixgba75sl5YViBvhCgsh05C3lAyEA0nkputsuzrP73rGpWAxa95TzMWlBNCTp4+ sLfvMZfupgi5ybnDqbxirPYZbrMvNuVm6+LH8iJtlotQ0Ti+7MAut3SXmV+prdzKKb/k RNEQ6r/y/B8iYlkecocHKKZcmobLVInNpfZLy7zaijcZKZIUbziAXRWyuA9AkcjGTxzj lDpOdnxfFer0+GFouAsqgsF4ibxpl7wUGG0dxJyYWuQYNnxr+p76M0eZFgOo+4zskMbD xoUw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:message-id:date:subject:from:to; bh=iBVktNsxJogLLE/EFf9T/E8t14+rTiJvgRxub4BdF8g=; b=HFgrkpJBrycUQqClUARzkPCyZkna11P5UPtkdtr1ODUN1Xn2ZlAsJZVw4EhXTBT2wp 5of9dU8oDLtuXU5zhvuZhonyTJxf9plY7j6d2OMSozsZV0cXIw0tjOUDeBnw/rrTNa6O rQFBg3gSCYW5t85Cpy+KsOKzB75TNIUwPa3spf6mnUnxpAkwAUjYh/eHMKFaqn72Je4E p022hvMyJXVFSLxBb88ETJcg4gajuPztLH2TQ/n9ymBGBJXPIEbrX3j1I3DXoCy8a/G6 ezAmgsMyndOh9JwG2IFU4OTbd20y9n4Bnn4bQdaX3RhiUyPlUwWiR6ql1Rc6OYVdFr0j lZ9g== X-Gm-Message-State: AKwxytcPvwXytXAPaVdjoQDvrnJ11kAQ0S97SOubE9K4/1IxPZqa2vu8 NUPlM8JxFst7NZLhuW5hMyGCfaIFxNAo X-Google-Smtp-Source: AH8x224RB4XFi1pxQvO9XDxX3Mny/pzRNgga2AEUaN3jLGTb1tpFD8vKldfz/PPh683DJCIgQBPYSxTi6A== MIME-Version: 1.0 X-Received: by 10.36.112.137 with SMTP id f131mr10644063itc.55.1516991199222; Fri, 26 Jan 2018 10:26:39 -0800 (PST) Message-ID: <001a114413708ea3e10563b209e9@google.com> Date: Fri, 26 Jan 2018 18:26:39 +0000 Subject: VoIP Clients/Customer List From: caron.wallace@frankmethods.com To: freebsd-stable@freebsd.org Content-Type: text/plain; charset="UTF-8"; format=flowed; delsp=yes Content-Transfer-Encoding: base64 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, 26 Jan 2018 18:26:40 -0000 PGRpdiBkaXI9Imx0ciI+PHAgY2xhc3M9Ik1zb05vcm1hbCIgIA0Kc3R5bGU9Im1hcmdpbi1ib3R0 b206MC4wMDAxcHQ7bGluZS1oZWlnaHQ6bm9ybWFsIj5IaSw8c3Bhbj48L3NwYW4+PC9wPg0KDQo8 cCBjbGFzcz0iTXNvTm9ybWFsIiAgDQpzdHlsZT0ibWFyZ2luLWJvdHRvbTowLjAwMDFwdDtsaW5l LWhlaWdodDpub3JtYWwiPjxzcGFuPsKgPC9zcGFuPjwvcD4NCg0KPHAgY2xhc3M9Ik1zb05vcm1h bCIgIA0Kc3R5bGU9Im1hcmdpbi1ib3R0b206MC4wMDAxcHQ7bGluZS1oZWlnaHQ6bm9ybWFsIj5X b3VsZCB5b3UgYmUgaW50ZXJlc3RlZCAgDQo8Yj5Wb0lQIGFuZCBWb0lQIFNlcnZpY2UgUHJvdmlk ZXJzIDwvYj5jb250YWN0DQppbmZvcm1hdGlvbiBmb3IgeW91ciBtYXJrZXRpbmcgY2FtcGFpZ25z PyBXZSBwcm92aWRlIHRoZSBEYXRhYmFzZSBhY3Jvc3MNCk5vcnRoIEFtZXJpY2EsIEVNRUEsIEFQ QUMgYW5kIExhdGluIEFtZXJpY2EuPGJyPg0KPGJyPg0KPGI+PHNwYW4+PC9zcGFuPjwvYj48L3A+ DQoNCjxwIGNsYXNzPSJNc29Ob3JtYWwiICANCnN0eWxlPSJtYXJnaW4tYm90dG9tOjAuMDAwMXB0 O2xpbmUtaGVpZ2h0Om5vcm1hbCI+PGI+PHU+RGF0YQ0KRmllbGRzPC91PjwvYj48Yj46PC9iPiBD b21wYW55LA0KRmlyc3QgTmFtZSwgTGFzdCBOYW1lLCBUaXRsZSwgRW1haWwgQWRkcmVzcywgQWRk cmVzcywgQ2l0eSwgU3RhdGUvUHJvdmluY2UsDQpaSVAvUG9zdGFsIENvZGUsIENvdW50cnksIFBo b25lLCBGYXgsIEVtcGxveWVlcywgUmV2ZW51ZSwgU0lDIENvZGUsIEluZHVzdHJ5DQphbmQgV2Vi IEFkZHJlc3M8YnI+DQo8YnI+DQo8Yj48c3Bhbj48L3NwYW4+PC9iPjwvcD4NCg0KPHAgY2xhc3M9 Ik1zb05vcm1hbCIgIA0Kc3R5bGU9Im1hcmdpbi1ib3R0b206MC4wMDAxcHQ7bGluZS1oZWlnaHQ6 bm9ybWFsIj48Yj7CoFdlIGFsc28gaGF2ZSBvdGhlciAgDQpUZWNobm9sb2d5IFVzZXJzIGxpa2U6 wqDCoCA8c3Bhbj48L3NwYW4+PC9iPjwvcD4NCg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgIA0Kc3R5 bGU9Im1hcmdpbi1ib3R0b206MC4wMDAxcHQ7bGluZS1oZWlnaHQ6bm9ybWFsIj48Yj7CoMKgwqDC oMKgICANCjxzcGFuPjwvc3Bhbj48L2I+PC9wPg0KDQo8cCBjbGFzcz0iZ21haWwtTXNvTGlzdFBh cmFncmFwaEN4U3BGaXJzdCIgc3R5bGU9Im1hcmdpbjowaW4gMGluIDAuMDAwMXB0ICANCjAuMjVp bjtsaW5lLWhlaWdodDpub3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LWZhbWlseTpXaW5nZGluZ3Mi PsO8PHNwYW4gIA0Kc3R5bGU9ImZvbnQtdmFyaWFudC1udW1lcmljOm5vcm1hbDtmb250LXZhcmlh bnQtZWFzdC1hc2lhbjpub3JtYWw7Zm9udC1zdHJldGNoOm5vcm1hbDtmb250LXNpemU6N3B0O2xp bmUtaGVpZ2h0Om5vcm1hbDtmb250LWZhbWlseTomcXVvdDtUaW1lcyAgDQpOZXcgUm9tYW4mcXVv dDsiPsKgIDwvc3Bhbj48L3NwYW4+PGI+U2hvcmV0ZWwgdXNlcnM8c3Bhbj48L3NwYW4+PC9iPjwv cD4NCg0KPHAgY2xhc3M9ImdtYWlsLU1zb0xpc3RQYXJhZ3JhcGhDeFNwTWlkZGxlIiBzdHlsZT0i bWFyZ2luOjBpbiAwaW4gMC4wMDAxcHQgIA0KMC4yNWluO2xpbmUtaGVpZ2h0Om5vcm1hbCI+PHNw YW4gc3R5bGU9ImZvbnQtZmFtaWx5OldpbmdkaW5ncyI+w7w8c3BhbiAgDQpzdHlsZT0iZm9udC12 YXJpYW50LW51bWVyaWM6bm9ybWFsO2ZvbnQtdmFyaWFudC1lYXN0LWFzaWFuOm5vcm1hbDtmb250 LXN0cmV0Y2g6bm9ybWFsO2ZvbnQtc2l6ZTo3cHQ7bGluZS1oZWlnaHQ6bm9ybWFsO2ZvbnQtZmFt aWx5OiZxdW90O1RpbWVzICANCk5ldyBSb21hbiZxdW90OyI+wqAgPC9zcGFuPjwvc3Bhbj48Yj5B dmF5YSB1c2VyczxzcGFuPjwvc3Bhbj48L2I+PC9wPg0KDQo8cCBjbGFzcz0iZ21haWwtTXNvTGlz dFBhcmFncmFwaEN4U3BNaWRkbGUiIHN0eWxlPSJtYXJnaW46MGluIDBpbiAwLjAwMDFwdCAgDQow LjI1aW47bGluZS1oZWlnaHQ6bm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1mYW1pbHk6V2luZ2Rp bmdzIj7DvDxzcGFuICANCnN0eWxlPSJmb250LXZhcmlhbnQtbnVtZXJpYzpub3JtYWw7Zm9udC12 YXJpYW50LWVhc3QtYXNpYW46bm9ybWFsO2ZvbnQtc3RyZXRjaDpub3JtYWw7Zm9udC1zaXplOjdw dDtsaW5lLWhlaWdodDpub3JtYWw7Zm9udC1mYW1pbHk6JnF1b3Q7VGltZXMgIA0KTmV3IFJvbWFu JnF1b3Q7Ij7CoCA8L3NwYW4+PC9zcGFuPjxiPk1pdGVsIHVzZXJzPHNwYW4+PC9zcGFuPjwvYj48 L3A+DQoNCjxwIGNsYXNzPSJnbWFpbC1Nc29MaXN0UGFyYWdyYXBoQ3hTcE1pZGRsZSIgc3R5bGU9 Im1hcmdpbjowaW4gMGluIDAuMDAwMXB0ICANCjAuMjVpbjtsaW5lLWhlaWdodDpub3JtYWwiPjxz cGFuIHN0eWxlPSJmb250LWZhbWlseTpXaW5nZGluZ3MiPsO8PHNwYW4gIA0Kc3R5bGU9ImZvbnQt dmFyaWFudC1udW1lcmljOm5vcm1hbDtmb250LXZhcmlhbnQtZWFzdC1hc2lhbjpub3JtYWw7Zm9u dC1zdHJldGNoOm5vcm1hbDtmb250LXNpemU6N3B0O2xpbmUtaGVpZ2h0Om5vcm1hbDtmb250LWZh bWlseTomcXVvdDtUaW1lcyAgDQpOZXcgUm9tYW4mcXVvdDsiPsKgIDwvc3Bhbj48L3NwYW4+PGI+ QnJvY2FkZSB1c2VyczxzcGFuPjwvc3Bhbj48L2I+PC9wPg0KDQo8cCBjbGFzcz0iZ21haWwtTXNv TGlzdFBhcmFncmFwaEN4U3BMYXN0IiBzdHlsZT0ibWFyZ2luOjBpbiAwaW4gMC4wMDAxcHQgIA0K MC4yNWluO2xpbmUtaGVpZ2h0Om5vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtZmFtaWx5Oldpbmdk aW5ncyI+w7w8c3BhbiAgDQpzdHlsZT0iZm9udC12YXJpYW50LW51bWVyaWM6bm9ybWFsO2ZvbnQt dmFyaWFudC1lYXN0LWFzaWFuOm5vcm1hbDtmb250LXN0cmV0Y2g6bm9ybWFsO2ZvbnQtc2l6ZTo3 cHQ7bGluZS1oZWlnaHQ6bm9ybWFsO2ZvbnQtZmFtaWx5OiZxdW90O1RpbWVzICANCk5ldyBSb21h biZxdW90OyI+wqAgPC9zcGFuPjwvc3Bhbj48Yj5KdW5pcGVyIE5ldHdvcmtzIHVzZXJzLCBDaXNj byB1c2VycyBhbmQgIA0KbWFueQ0KbW9yZS4uLjxzcGFuPjwvc3Bhbj48L2I+PC9wPg0KDQo8cCBj bGFzcz0iTXNvTm9ybWFsIiAgDQpzdHlsZT0ibWFyZ2luLWJvdHRvbTowLjAwMDFwdDtsaW5lLWhl aWdodDpub3JtYWwiPjxiPsKgPC9iPjwvcD4NCg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgIA0Kc3R5 bGU9Im1hcmdpbi1ib3R0b206MC4wMDAxcHQ7bGluZS1oZWlnaHQ6bm9ybWFsIj5QbGVhc2UgcmV2 aWV3IGFuZCBsZXQgbWUgIA0Ka25vdyBpZiB5b3UNCmFyZSBpbnRlcmVzdGVkIGluIGFueSBvZiB0 aGUgdGVjaG5vbG9neSB1c2VycyBvciBkaWZmZXJlbnQgY29udGFjdCBsaXN0IGZvcg0KeW91ciBj YW1wYWlnbnMgYW5kIEkgd2lsbCBwcm92aWRlIG1vcmUgaW5mb3JtYXRpb24gZm9yIHRoZSBzYW1l LiBBbmQgSeKAmWxsICANCnNlbmQNCmFjcm9zcyBhIGZldyBzYW1wbGUgcmVjb3JkcyBmb3IgeW91 IHRvIHJldmlldy48c3Bhbj48L3NwYW4+PC9wPg0KDQo8cCBjbGFzcz0iTXNvTm9ybWFsIiAgDQpz dHlsZT0ibWFyZ2luLWJvdHRvbTowLjAwMDFwdDtsaW5lLWhlaWdodDpub3JtYWwiPkFwcHJlY2lh dGUgeW91ciB0aW1lIGFuZCAgDQpsb29rIGZvcndhcmQNCnRvIGhlYXIgZnJvbSB5b3UuPHNwYW4+ PC9zcGFuPjwvcD4NCg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgIA0Kc3R5bGU9Im1hcmdpbi1ib3R0 b206MC4wMDAxcHQ7bGluZS1oZWlnaHQ6bm9ybWFsIj48Yj7CoDwvYj48L3A+DQoNCjxwIGNsYXNz PSJNc29Ob3JtYWwiICANCnN0eWxlPSJtYXJnaW4tYm90dG9tOjAuMDAwMXB0O2xpbmUtaGVpZ2h0 Om5vcm1hbCI+PGI+UmVnYXJkcyw8YnI+DQo8YnI+DQo8c3Bhbj48L3NwYW4+PC9iPjwvcD4NCg0K PHAgY2xhc3M9Ik1zb05vcm1hbCIgIA0Kc3R5bGU9Im1hcmdpbi1ib3R0b206MC4wMDAxcHQ7bGlu ZS1oZWlnaHQ6bm9ybWFsIj48Yj5DYXJvbiAgDQpXYWxhY2U8c3Bhbj48L3NwYW4+PC9iPjwvcD4N Cg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgIA0Kc3R5bGU9Im1hcmdpbi1ib3R0b206MC4wMDAxcHQ7 bGluZS1oZWlnaHQ6bm9ybWFsIj48Yj5NYXJrZXRpbmcNCkV4ZWN1dGl2ZTxzcGFuPjwvc3Bhbj48 L2I+PC9wPg0KDQo8cCBjbGFzcz0iTXNvTm9ybWFsIiAgDQpzdHlsZT0ibWFyZ2luLWJvdHRvbTow LjAwMDFwdDtsaW5lLWhlaWdodDpub3JtYWwiPjxiPsKgPC9iPjwvcD4NCg0KPHAgY2xhc3M9Ik1z b05vcm1hbCIgIA0Kc3R5bGU9Im1hcmdpbi1ib3R0b206MC4wMDAxcHQ7bGluZS1oZWlnaHQ6bm9y bWFsIj48Yj7CoDwvYj48L3A+DQoNCjxwIGNsYXNzPSJNc29Ob3JtYWwiIGFsaWduPSJjZW50ZXIi ICANCnN0eWxlPSJtYXJnaW4tYm90dG9tOjAuMDAwMXB0O3RleHQtYWxpZ246Y2VudGVyO2xpbmUt aGVpZ2h0Om5vcm1hbCI+PHNwYW4gIA0Kc3R5bGU9ImNvbG9yOnJnYigxNjYsMTY2LDE2NikiPlRv IE9wdCBPdXQsIHBsZWFzZQ0KcmVwbHkgd2l0aCBMZWF2ZSBPdXQgaW4gdGhlIFN1YmplY3QgTGlu ZS48L3NwYW4+PGI+PHNwYW4+PC9zcGFuPjwvYj48L3A+DQoNCjxwIGNsYXNzPSJNc29Ob3JtYWwi PjxzcGFuPsKgPC9zcGFuPjwvcD48L2Rpdj4NCjxwPiZuYnNwOzwvcD48YSBzdHlsZT0nZGlzcGxh eTogYmxvY2s7IG1hcmdpbjogMzJweCAwIDQwcHggMDsgcGFkZGluZzogIA0KMTBweDsgZm9udC1z aXplOiAxZW07IHRleHQtYWxpZ246IGNlbnRlcjsgYm9yZGVyOiAwOyBib3JkZXItdG9wOiAxcHgg c29saWQgIA0KZ3JheTsgJyBocmVmPSdodHRwczovL2dvby5nbC8ya3NkUnYnPnBvd2VyZWQgYnkg R1NNLiBGcmVlIG1haWwgbWVyZ2UgYW5kICANCmVtYWlsIG1hcmtldGluZyBzb2Z0d2FyZSBmb3Ig R21haWwuPC9hPg0K From owner-freebsd-stable@freebsd.org Sat Jan 27 08:23:27 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 5A5B0E7666E for ; Sat, 27 Jan 2018 08:23:27 +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 EF4A57C6C3 for ; Sat, 27 Jan 2018 08:23:26 +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 w0R8Nqb0009129 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=FAIL); Sat, 27 Jan 2018 08:23:54 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 w0R8NFlE020599 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 27 Jan 2018 00:23:17 -0800 (PST) (envelope-from truckman@FreeBSD.org) Date: Sat, 27 Jan 2018 00:23:10 -0800 (PST) From: Don Lewis Subject: Re: Ryzen issues on FreeBSD ? To: Mike Tancsa cc: Peter Moody , Pete French , freebsd-stable@freebsd.org In-Reply-To: <3dd9a61b-511d-db2e-80ca-cbc9a4b65f92@sentex.net> Message-ID: References: <8e842dec-ade7-37d1-6bd8-856ea1a827ca@sentex.net> <9b769e4e-b098-b294-0bce-8bb1c42e8a59@rootautomation.com> <730eb882-1c6a-afb7-0ada-396db44fb34b@ingresso.co.uk> <8b882970-4d5d-2a96-4dac-779cab07b9ae@sentex.net> <343acf99-3e9e-093a-7390-c142396c2985@sentex.net> <3dd9a61b-511d-db2e-80ca-cbc9a4b65f92@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: Sat, 27 Jan 2018 08:23:27 -0000 On 23 Jan, Mike Tancsa wrote: > On 1/22/2018 5:13 PM, Don Lewis wrote: >> On 22 Jan, Mike Tancsa wrote: >>> On 1/22/2018 1:41 PM, Peter Moody wrote: >>>> fwiw, I upgraded to 11-STABLE (11.1-STABLE #6 r328223), applied the >>>> hw.lower_amd64_sharedpage setting to my loader.conf and got a crash >>>> last night following the familiar high load -> idle. this was with SMT >>>> re-enabled. no crashdump, so it was the hard crash that I've been >>>> getting. >>> >>> hw.lower_amd64_sharedpage=1 is the default on AMD boxes no ? I didnt >>> need to set mine to 1 >>> >>>> >>>> shrug, I'm at a loss here. >>> >>> I am trying an RMA with AMD. >> >> Something else that you might want to try is 12.0-CURRENT. There might >> be some changes in HEAD that need to be merged back to 11.1-STABLE. > > > Temp works as expected now. However, a (similar?) hang building Samba47. > > ctrl+T shows > > > load: 1.98 cmd: python2.7 53438 [usem] 54.70r 14.98u 6.04s 0% 230992k > make: Working in: /usr/ports/net/samba47 > load: 0.34 cmd: python2.7 53438 [usem] 168.48r 14.98u 6.04s 0% 230992k > make: Working in: /usr/ports/net/samba47 > load: 0.31 cmd: python2.7 53438 [usem] 174.12r 14.98u 6.04s 0% 230992k > make: Working in: /usr/ports/net/samba47 I just ran into this for this first time with samba46. I kicked of a ports build this evening before leaving for several hours. When I returned, samba46 had failed with a build runaway. I just tried again and I see python stuck in the usem state. This is what I see with procstat -k: PID TID COMM TDNAME KSTACK 90692 100801 python2.7 - mi_switch sleepq_catch_signals sleepq_wait_sig _sleep umtxq_sleep do_sem2_wait __umtx_op_sem2_wait amd64_syscall fast_syscall_common 90692 100824 python2.7 - mi_switch sleepq_catch_signals sleepq_wait_sig _sleep umtxq_sleep do_sem2_wait __umtx_op_sem2_wait amd64_syscall fast_syscall_common 90692 100857 python2.7 - mi_switch sleepq_catch_signals sleepq_wait_sig _sleep umtxq_sleep do_sem2_wait __umtx_op_sem2_wait amd64_syscall fast_syscall_common 90692 100956 python2.7 - mi_switch sleepq_catch_signals sleepq_wait_sig _sleep umtxq_sleep do_sem2_wait __umtx_op_sem2_wait amd64_syscall fast_syscall_common 90692 100995 python2.7 - mi_switch sleepq_catch_signals sleepq_wait_sig _sleep umtxq_sleep do_sem2_wait __umtx_op_sem2_wait amd64_syscall fast_syscall_common 90692 101483 python2.7 - mi_switch sleepq_catch_signals sleepq_wait_sig _sleep umtxq_sleep do_sem2_wait __umtx_op_sem2_wait amd64_syscall fast_syscall_common 90692 101538 python2.7 - mi_switch sleepq_catch_signals sleepq_wait_sig _sleep umtxq_sleep do_sem2_wait __umtx_op_sem2_wait amd64_syscall fast_syscall_common 90692 101549 python2.7 - mi_switch sleepq_catch_signals sleepq_wait_sig _sleep umtxq_sleep do_sem2_wait __umtx_op_sem2_wait amd64_syscall fast_syscall_common 90692 101570 python2.7 - mi_switch sleepq_catch_signals sleepq_wait_sig _sleep umtxq_sleep do_sem2_wait __umtx_op_sem2_wait amd64_syscall fast_syscall_common 90692 101572 python2.7 - mi_switch sleepq_catch_signals sleepq_wait_sig _sleep umtxq_sleep do_sem2_wait __umtx_op_sem2_wait amd64_syscall fast_syscall_common 90692 101583 python2.7 - mi_switch sleepq_catch_signals sleepq_wait_sig _sleep umtxq_sleep do_sem2_wait __umtx_op_sem2_wait amd64_syscall fast_syscall_common 90692 101588 python2.7 - mi_switch sleepq_catch_signals sleepq_wait_sig _sleep umtxq_sleep do_sem2_wait __umtx_op_sem2_wait amd64_syscall fast_syscall_common 90692 101593 python2.7 - mi_switch sleepq_catch_signals sleepq_wait_sig _sleep umtxq_sleep do_sem2_wait __umtx_op_sem2_wait amd64_syscall fast_syscall_common 90692 101610 python2.7 - mi_switch sleepq_catch_signals sleepq_wait_sig _sleep umtxq_sleep do_sem2_wait __umtx_op_sem2_wait amd64_syscall fast_syscall_common 90692 101629 python2.7 - mi_switch sleepq_catch_signals sleepq_wait_sig _sleep umtxq_sleep do_lock_umutex __umtx_op_wait_umutex amd64_syscall fast_syscall_common 90692 101666 python2.7 - mi_switch sleepq_catch_signals sleepq_wait_sig _sleep umtxq_sleep do_sem2_wait __umtx_op_sem2_wait amd64_syscall fast_syscall_common 90692 102114 python2.7 - mi_switch sleepq_catch_signals sleepq_wait_sig _sleep umtxq_sleep do_sem2_wait __umtx_op_sem2_wait amd64_syscall fast_syscall_common and procstat -t: PID TID COMM TDNAME CPU PRI STATE WCHAN 90692 100801 python2.7 - -1 124 sleep usem 90692 100824 python2.7 - -1 124 sleep usem 90692 100857 python2.7 - -1 124 sleep usem 90692 100956 python2.7 - -1 125 sleep usem 90692 100995 python2.7 - -1 124 sleep usem 90692 101483 python2.7 - -1 124 sleep usem 90692 101538 python2.7 - -1 125 sleep usem 90692 101549 python2.7 - -1 124 sleep usem 90692 101570 python2.7 - -1 124 sleep usem 90692 101572 python2.7 - -1 124 sleep usem 90692 101583 python2.7 - -1 125 sleep usem 90692 101588 python2.7 - -1 124 sleep usem 90692 101593 python2.7 - -1 123 sleep usem 90692 101610 python2.7 - -1 124 sleep usem 90692 101629 python2.7 - -1 125 sleep umtxn 90692 101666 python2.7 - -1 124 sleep usem 90692 102114 python2.7 - -1 152 sleep usem The machine isn't totally idle. The last pid value in top increases by about 40 every two seconds. Looks like it might be poudriere polling something ... From owner-freebsd-stable@freebsd.org Sat Jan 27 16:52:20 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 1DF80ECB3B6 for ; Sat, 27 Jan 2018 16:52:20 +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 7CEF9701C6; Sat, 27 Jan 2018 16:52:19 +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 w0RGqIP4087399 (version=TLSv1 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Sat, 27 Jan 2018 11:52:18 -0500 (EST) (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 w0RGqGlJ088167; Sat, 27 Jan 2018 11:52:16 -0500 (EST) (envelope-from mike@sentex.net) Subject: Re: Ryzen issues on FreeBSD ? To: Don Lewis Cc: Peter Moody , Pete French , freebsd-stable@freebsd.org, Andriy Gapon References: <8e842dec-ade7-37d1-6bd8-856ea1a827ca@sentex.net> <9b769e4e-b098-b294-0bce-8bb1c42e8a59@rootautomation.com> <730eb882-1c6a-afb7-0ada-396db44fb34b@ingresso.co.uk> <8b882970-4d5d-2a96-4dac-779cab07b9ae@sentex.net> <343acf99-3e9e-093a-7390-c142396c2985@sentex.net> <3dd9a61b-511d-db2e-80ca-cbc9a4b65f92@sentex.net> From: Mike Tancsa Organization: Sentex Communications Message-ID: <55913e41-3a8a-9a4d-6862-e09a3d0f4d55@sentex.net> Date: Sat, 27 Jan 2018 11:52:16 -0500 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.5.2 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: Sat, 27 Jan 2018 16:52:20 -0000 On 1/27/2018 3:23 AM, Don Lewis wrote: > > I just ran into this for this first time with samba46. I kicked of a > ports build this evening before leaving for several hours. When I > returned, samba46 had failed with a build runaway. I just tried again > and I see python stuck in the usem state. This is what I see with > procstat -k: Hmmm, is this indicative of a processor bug or a FreeBSD bug or its indeterminate at this point ? > > PID TID COMM TDNAME KSTACK > 90692 100801 python2.7 - mi_switch sleepq_catch_signals sleepq_wait_sig _sleep umtxq_sleep do_sem2_wait __umtx_op_sem2_wait amd64_syscall fast_syscall_common > 90692 100824 python2.7 - mi_switch sleepq_catch_signals sleepq_wait_sig _sleep umtxq_sleep do_sem2_wait __umtx_op_sem2_wait amd64_syscall fast_syscall_common > 90692 100857 python2.7 - mi_switch sleepq_catch_signals sleepq_wait_sig _sleep umtxq_sleep do_sem2_wait __umtx_op_sem2_wait amd64_syscall fast_syscall_common > 90692 100956 python2.7 - mi_switch sleepq_catch_signals sleepq_wait_sig _sleep umtxq_sleep do_sem2_wait __umtx_op_sem2_wait amd64_syscall fast_syscall_common > 90692 100995 python2.7 - mi_switch sleepq_catch_signals sleepq_wait_sig _sleep umtxq_sleep do_sem2_wait __umtx_op_sem2_wait amd64_syscall fast_syscall_common > 90692 101483 python2.7 - mi_switch sleepq_catch_signals sleepq_wait_sig _sleep umtxq_sleep do_sem2_wait __umtx_op_sem2_wait amd64_syscall fast_syscall_common > 90692 101538 python2.7 - mi_switch sleepq_catch_signals sleepq_wait_sig _sleep umtxq_sleep do_sem2_wait __umtx_op_sem2_wait amd64_syscall fast_syscall_common > 90692 101549 python2.7 - mi_switch sleepq_catch_signals sleepq_wait_sig _sleep umtxq_sleep do_sem2_wait __umtx_op_sem2_wait amd64_syscall fast_syscall_common > 90692 101570 python2.7 - mi_switch sleepq_catch_signals sleepq_wait_sig _sleep umtxq_sleep do_sem2_wait __umtx_op_sem2_wait amd64_syscall fast_syscall_common > 90692 101572 python2.7 - mi_switch sleepq_catch_signals sleepq_wait_sig _sleep umtxq_sleep do_sem2_wait __umtx_op_sem2_wait amd64_syscall fast_syscall_common > 90692 101583 python2.7 - mi_switch sleepq_catch_signals sleepq_wait_sig _sleep umtxq_sleep do_sem2_wait __umtx_op_sem2_wait amd64_syscall fast_syscall_common > 90692 101588 python2.7 - mi_switch sleepq_catch_signals sleepq_wait_sig _sleep umtxq_sleep do_sem2_wait __umtx_op_sem2_wait amd64_syscall fast_syscall_common > 90692 101593 python2.7 - mi_switch sleepq_catch_signals sleepq_wait_sig _sleep umtxq_sleep do_sem2_wait __umtx_op_sem2_wait amd64_syscall fast_syscall_common > 90692 101610 python2.7 - mi_switch sleepq_catch_signals sleepq_wait_sig _sleep umtxq_sleep do_sem2_wait __umtx_op_sem2_wait amd64_syscall fast_syscall_common > 90692 101629 python2.7 - mi_switch sleepq_catch_signals sleepq_wait_sig _sleep umtxq_sleep do_lock_umutex __umtx_op_wait_umutex amd64_syscall fast_syscall_common > 90692 101666 python2.7 - mi_switch sleepq_catch_signals sleepq_wait_sig _sleep umtxq_sleep do_sem2_wait __umtx_op_sem2_wait amd64_syscall fast_syscall_common > 90692 102114 python2.7 - mi_switch sleepq_catch_signals sleepq_wait_sig _sleep umtxq_sleep do_sem2_wait __umtx_op_sem2_wait amd64_syscall fast_syscall_common > > and procstat -t: > > PID TID COMM TDNAME CPU PRI STATE WCHAN > 90692 100801 python2.7 - -1 124 sleep usem > 90692 100824 python2.7 - -1 124 sleep usem > 90692 100857 python2.7 - -1 124 sleep usem > 90692 100956 python2.7 - -1 125 sleep usem > 90692 100995 python2.7 - -1 124 sleep usem > 90692 101483 python2.7 - -1 124 sleep usem > 90692 101538 python2.7 - -1 125 sleep usem > 90692 101549 python2.7 - -1 124 sleep usem > 90692 101570 python2.7 - -1 124 sleep usem > 90692 101572 python2.7 - -1 124 sleep usem > 90692 101583 python2.7 - -1 125 sleep usem > 90692 101588 python2.7 - -1 124 sleep usem > 90692 101593 python2.7 - -1 123 sleep usem > 90692 101610 python2.7 - -1 124 sleep usem > 90692 101629 python2.7 - -1 125 sleep umtxn > 90692 101666 python2.7 - -1 124 sleep usem > 90692 102114 python2.7 - -1 152 sleep usem > > The machine isn't totally idle. The last pid value in top increases by > about 40 every two seconds. Looks like it might be poudriere polling > something ... > > > -- ------------------- Mike Tancsa, tel +1 519 651 3400 Sentex Communications, mike@sentex.net Providing Internet services since 1994 www.sentex.net Cambridge, Ontario Canada http://www.tancsa.com/ From owner-freebsd-stable@freebsd.org Sat Jan 27 17:41:36 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 AEA8FECD9E2 for ; Sat, 27 Jan 2018 17:41:36 +0000 (UTC) (envelope-from marklmi26-fbsd@yahoo.com) Received: from sonic306-20.consmr.mail.gq1.yahoo.com (sonic306-20.consmr.mail.gq1.yahoo.com [98.137.68.83]) (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 2B0F1721E0 for ; Sat, 27 Jan 2018 17:41:35 +0000 (UTC) (envelope-from marklmi26-fbsd@yahoo.com) X-YMail-OSG: XPYe.WMVM1mOTY_0zw3_iNziTQQq0nZGkazSl9Aoh7EToxBfMzDhK4Rw5tx4khe j1wQ9Z1X3emCNexG.Dk97R_84ghLCcEMRP.5nN8G6ykRKF6tsEelHlO6t6XU4dig4d.Pij7pEUjc wySmjhX.PkS8RCh_t.3RWWwJ5qK1bCuITFjqTrm_zaQIXAV4zJhrgjpOO280mg5SqEpHmv5duZFi ex.vBZwnwP6e8pE9A4vhamEoX50LEZQB6ngNZIGPbyypR4DTARx_UWcJS.ly4jEM2iMh721Bjscg zgbgSmp4hZbbHf6iuawnkVvGXggYjxZ8XQ9ymIjOgUyB3Z169lCe.lkw8pHHNVRE2iM2RdwbtheG f6YF.NQkNWtkbHm4OoOLFqvL2yQm278FATetXpZIR8HkyG58M4AcVa3wusMshhvTrxK1_GQ4uMku VcPzFtPcgLeV7jNJQTtwB00.cxTebbkXMKudVSP4NUnyqqZu3v.aG_N15DvUetHYta.ro Received: from sonic.gate.mail.ne1.yahoo.com by sonic306.consmr.mail.gq1.yahoo.com with HTTP; Sat, 27 Jan 2018 17:41:34 +0000 Received: from smtp103.rhel.mail.gq1.yahoo.com (EHLO [192.168.1.25]) ([68.180.227.11]) by smtp411.mail.gq1.yahoo.com (JAMES SMTP Server ) with ESMTPA ID 2844b21d794d965d0883d86affdf0fb5; Sat, 27 Jan 2018 17:41:29 +0000 (UTC) From: Mark Millard Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 11.2 \(3445.5.20\)) Subject: Re: Ryzen issues on FreeBSD ? Message-Id: <0641905F-6D9D-4157-9DCC-88A2EBCBB720@yahoo.com> Date: Sat, 27 Jan 2018 09:41:28 -0800 To: Don Lewis , FreeBSD-STABLE Mailing List X-Mailer: Apple Mail (2.3445.5.20) 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, 27 Jan 2018 17:41:36 -0000 Don Lewis truckman at FreeBSD.org wrote on Sat Jan 27 08:23:27 UTC 2018 : > PID TID COMM TDNAME CPU PRI STATE = WCHAN =20 > 90692 100801 python2.7 - -1 124 sleep = usem =20 > 90692 100824 python2.7 - -1 124 sleep = usem =20 . . . # grep -r '"usem"' /usr/src/sys/ /usr/src/sys/dev/qlnx/qlnxe/ecore_dbg_fw_funcs.c: "usem", { true, = true, true }, true, DBG_USTORM_ID, /usr/src/sys/kern/kern_umtx.c: error =3D umtxq_sleep(uq, "usem", = timeout =3D=3D NULL ? NULL : &timo); /usr/src/sys/kern/kern_umtx.c: error =3D umtxq_sleep(uq, "usem", = timeout =3D=3D NULL ? NULL : &timo); /usr/src/sys/kern/kern_umtx.c has : #if defined(COMPAT_FREEBSD9) || defined(COMPAT_FREEBSD10) static int do_sem_wait(struct thread *td, struct _usem *sem, struct _umtx_time = *timeout) { . . . error =3D umtxq_sleep(uq, "usem", timeout =3D=3D NULL ? NULL : = &timo); . . . #endif . . . static int do_sem2_wait(struct thread *td, struct _usem2 *sem, struct _umtx_time = *timeout) { . . . error =3D umtxq_sleep(uq, "usem", timeout =3D=3D NULL ? NULL : = &timo); . . . The comparison/contrast for: > 90692 101629 python2.7 - -1 125 sleep = umtxn =20 # grep -r '"umtxn"' /usr/src/sys/ /usr/src/sys/kern/kern_umtx.c: error =3D = umtxq_sleep(uq, "umtxn", timeout =3D=3D NULL ? /usr/src/sys/kern/kern_umtx.c has: static int do_lock_normal(struct thread *td, struct umutex *m, uint32_t flags, struct _umtx_time *timeout, int mode) { . . . /* * We set the contested bit, sleep. Otherwise the lock = changed * and we need to retry or we lost a race to the thread * unlocking the umtx. */ umtxq_lock(&uq->uq_key); umtxq_unbusy(&uq->uq_key); if (old =3D=3D owner) error =3D umtxq_sleep(uq, "umtxn", timeout =3D=3D = NULL ? NULL : &timo); umtxq_remove(uq); umtxq_unlock(&uq->uq_key); umtx_key_release(&uq->uq_key); . . . Both contexts are umtxq_sleep usage: /* * Put thread into sleep state, before sleeping, check if * thread was removed from umtx queue. */ static inline int umtxq_sleep(struct umtx_q *uq, const char *wmesg, struct abs_timeout = *abstime) . . . Note: I'm guessing that /usr/src/sys/dev/qlnx/qlnxe/ecore_dbg_fw_funcs.c is not involved. =3D=3D=3D Mark Millard marklmi at yahoo.com ( markmi at dsl-only.net is going away in 2018-Feb, late)