From owner-freebsd-stable@freebsd.org Mon Jan 15 09:31: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 4B94EE65D85 for ; Mon, 15 Jan 2018 09:31:44 +0000 (UTC) (envelope-from marko.cupac@mimar.rs) Received: from mail.mimar.rs (tazar.mimar.rs [193.53.106.132]) (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 06D1968B56 for ; Mon, 15 Jan 2018 09:31:42 +0000 (UTC) (envelope-from marko.cupac@mimar.rs) Received: from tazar.mimar.rs (localhost [127.0.2.132]) by mail.mimar.rs (Postfix) with ESMTP id 85168625A244 for ; Mon, 15 Jan 2018 10:31:39 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=mimar.rs; h= content-transfer-encoding:content-type:content-type:mime-version :x-mailer:organization:message-id:subject:subject:from:from:date :date:received:received; s=1711; t=1516008689; x=1517823090; bh= OsiJBUeMpR0/MRUN5Z/qrKb9OpZzXOKYCYNeOpldB0E=; b=bi59D77VOAdAG1vy mncJYWHptB3yPYB+khjhxdrpV6a9/u0L+p/yVBUw+yfE2GPH0RVg/8lYncE5if5V yjk7u9f5HayoAZ+YrqdGulR/wa8vLTFgU1g++/Y2bNwg0L7OjRWX/XYTYp4kHY7Q CM5t+JZXUJ4E3w299bErCgYeCR5ccG8y+MnAcHq8L4J6+wlz0pHxjkW3xKIX6hjq ZfUJu7GOwEe/sc3ASUwty1C9a+u9kENBP3eHbJcjZ7+/nHsnV8x2tTVeZRCEtUij J30L8qisVTdpVZwScUTMqNKBfNANH3eeSx/R0E/Ju21KETc3mq07GBMppmhQXwTQ KyCa7Q== X-Virus-Scanned: amavisd-new at mimar.rs Received: from mail.mimar.rs ([127.0.2.132]) by tazar.mimar.rs (amavis.mimar.rs [127.0.2.132]) (amavisd-new, port 10026) with LMTP id vnUptYL0LR4Q for ; Mon, 15 Jan 2018 10:31:29 +0100 (CET) Received: from efreet-freebsd.kappastar.com (nat-nat.kappastar.com [193.53.106.34]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: marko.cupac) by mail.mimar.rs (Postfix) with ESMTPSA id 122C3625A23E for ; Mon, 15 Jan 2018 10:31:28 +0100 (CET) Date: Mon, 15 Jan 2018 10:31:28 +0100 From: Marko =?UTF-8?B?Q3VwYcSH?= To: Subject: troubleshooting before hard reset Message-ID: <20180115103128.014f27f8@efreet-freebsd.kappastar.com> Organization: Mimar X-Mailer: Claws Mail 3.16.0 (GTK+ 2.24.31; amd64-portbld-freebsd11.1) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable 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, 15 Jan 2018 09:31:44 -0000 Hi, one of my ageing servers, HP DL380g5, which is serving a bunch of non-critical production jails on FreeBSD 11.1, bacame inaccessible over weekend. I have physical access, its disks and NICs are showing activity, but it doesn't send anything to monitor over VGA, also I guess it doesn't recognise keyboard (num lock led does nothing). Before I hard reset it, is there anything I can do to troubleshoot the problem? I tried serial port as well but it gives nothing on either 9600 or 115200 baud. I guess OS needs to be configured beforehand for serial access. Thank you in advance, --=20 Before enlightenment - chop wood, draw water. After enlightenment - chop wood, draw water. Marko Cupa=C4=87 https://www.mimar.rs/ From owner-freebsd-stable@freebsd.org Mon Jan 15 09:40: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 011D7E6CAB5 for ; Mon, 15 Jan 2018 09:40:53 +0000 (UTC) (envelope-from eugen@grosbein.net) Received: from hz.grosbein.net (hz.grosbein.net [78.47.246.247]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "hz.grosbein.net", Issuer "hz.grosbein.net" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 89B0869502 for ; Mon, 15 Jan 2018 09:40:51 +0000 (UTC) (envelope-from eugen@grosbein.net) Received: from eg.sd.rdtc.ru (root@eg.sd.rdtc.ru [62.231.161.221] (may be forged)) by hz.grosbein.net (8.15.2/8.15.2) with ESMTPS id w0F9ehqk033319 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Mon, 15 Jan 2018 10:40:44 +0100 (CET) (envelope-from eugen@grosbein.net) X-Envelope-From: eugen@grosbein.net X-Envelope-To: marko.cupac@mimar.rs Received: from [10.58.0.4] ([10.58.0.4]) by eg.sd.rdtc.ru (8.15.2/8.15.2) with ESMTPS id w0F9eZDQ092153 (version=TLSv1.2 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Mon, 15 Jan 2018 16:40:35 +0700 (+07) (envelope-from eugen@grosbein.net) Subject: Re: troubleshooting before hard reset To: =?UTF-8?Q?Marko_Cupa=c4=87?= , freebsd-stable@freebsd.org References: <20180115103128.014f27f8@efreet-freebsd.kappastar.com> From: Eugene Grosbein Message-ID: <5A5C770F.4080806@grosbein.net> Date: Mon, 15 Jan 2018 16:40:31 +0700 User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.7.2 MIME-Version: 1.0 In-Reply-To: <20180115103128.014f27f8@efreet-freebsd.kappastar.com> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-Spam-Status: No, score=2.2 required=5.0 tests=BAYES_00, LOCAL_FROM, RDNS_NONE autolearn=no autolearn_force=no version=3.4.1 X-Spam-Report: * -2.3 BAYES_00 BODY: Bayes spam probability is 0 to 1% * [score: 0.0000] * 2.6 LOCAL_FROM From my domains * 1.9 RDNS_NONE Delivered to internal network by a host with no rDNS X-Spam-Level: ** X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on hz.grosbein.net X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Jan 2018 09:40:53 -0000 15.01.2018 16:31, Marko Cupać wrote: > Hi, > > one of my ageing servers, HP DL380g5, which is serving a bunch of > non-critical production jails on FreeBSD 11.1, bacame inaccessible over > weekend. I have physical access, its disks and NICs are showing > activity, but it doesn't send anything to monitor over VGA, also I > guess it doesn't recognise keyboard (num lock led does nothing). > > Before I hard reset it, is there anything I can do to troubleshoot the > problem? I tried serial port as well but it gives nothing on either > 9600 or 115200 baud. I guess OS needs to be configured beforehand for > serial access. Yes. If keyboard seems to be dead and there is no video output, I'm afraid you can't get anything useful from the box other than sniffing traffic from its MAC address, if any. And check MAC address table of network switch for server's MAC address if you have managed switch. Else, just reset it. From owner-freebsd-stable@freebsd.org Mon Jan 15 13:21:25 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 BA384E7CD01 for ; Mon, 15 Jan 2018 13:21:25 +0000 (UTC) (envelope-from clay@milos.co.za) Received: from lisa.milos.co.za (moe.milos.co.za [109.169.49.127]) by mx1.freebsd.org (Postfix) with SMTP id 2A59574730 for ; Mon, 15 Jan 2018 13:21:23 +0000 (UTC) (envelope-from clay@milos.co.za) Received: (qmail 29038 invoked by uid 89); 15 Jan 2018 13:14:39 -0000 Received: from unknown (HELO roundcube) (172.16.15.33) by vpopmail with SMTP; 15 Jan 2018 13:14:39 -0000 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Date: Mon, 15 Jan 2018 14:14:39 +0100 From: clay@milos.co.za To: Eugene Grosbein Cc: =?UTF-8?Q?Marko_Cupa=C4=87?= , freebsd-stable@freebsd.org, owner-freebsd-stable@freebsd.org Subject: Re: troubleshooting before hard reset In-Reply-To: <5A5C770F.4080806@grosbein.net> References: <20180115103128.014f27f8@efreet-freebsd.kappastar.com> <5A5C770F.4080806@grosbein.net> Message-ID: <5ea0cb77a7805906b7da0ba150d65a9a@milos.co.za> X-Sender: clay@milos.co.za User-Agent: Roundcube Webmail/1.3.3 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, 15 Jan 2018 13:21:25 -0000 On 2018-01-15 10:40, Eugene Grosbein wrote: > 15.01.2018 16:31, Marko Cupać wrote: >> Hi, >> >> one of my ageing servers, HP DL380g5, which is serving a bunch of >> non-critical production jails on FreeBSD 11.1, bacame inaccessible >> over >> weekend. I have physical access, its disks and NICs are showing >> activity, but it doesn't send anything to monitor over VGA, also I >> guess it doesn't recognise keyboard (num lock led does nothing). >> >> Before I hard reset it, is there anything I can do to troubleshoot the >> problem? I tried serial port as well but it gives nothing on either >> 9600 or 115200 baud. I guess OS needs to be configured beforehand for >> serial access. > > Yes. > > If keyboard seems to be dead and there is no video output, I'm afraid > you can't get anything useful from the box other than sniffing traffic > from its MAC address, if any. And check MAC address table of network > switch > for server's MAC address if you have managed switch. Else, just reset > it. > Have you tried remote console access via the iLO? Sometimes that still works when the physical VGA doesn't. \\Clay From owner-freebsd-stable@freebsd.org Wed Jan 17 06:48: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 1EB0EEA6001 for ; Wed, 17 Jan 2018 06:48:16 +0000 (UTC) (envelope-from mark.saad@ceal.com.br) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 05C7C7FB9B for ; Wed, 17 Jan 2018 06:48:16 +0000 (UTC) (envelope-from mark.saad@ceal.com.br) Received: by mailman.ysv.freebsd.org (Postfix) id 05177E80000; Wed, 17 Jan 2018 06:48:16 +0000 (UTC) Delivered-To: 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 04B72E7FFFF for ; Wed, 17 Jan 2018 06:48:16 +0000 (UTC) (envelope-from mark.saad@ceal.com.br) Received: from mail.eletrobrasalagoas.com (mail.eletrobrasalagoas.com [200.217.241.72]) (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 BF2AC7FB9A for ; Wed, 17 Jan 2018 06:48:14 +0000 (UTC) (envelope-from mark.saad@ceal.com.br) Received: from localhost (localhost [127.0.0.1]) by mail.eletrobrasalagoas.com (Postfix) with ESMTP id 86FAE16E32F for ; Wed, 17 Jan 2018 03:23:32 -0300 (BRT) Received: from mail.eletrobrasalagoas.com ([127.0.0.1]) by localhost (mail.eletrobrasalagoas.com [127.0.0.1]) (amavisd-new, port 10032) with ESMTP id TIDZZ64A32ai for ; Wed, 17 Jan 2018 03:23:32 -0300 (BRT) Received: from localhost (localhost [127.0.0.1]) by mail.eletrobrasalagoas.com (Postfix) with ESMTP id 2B6641415CB1 for ; Wed, 17 Jan 2018 03:23:32 -0300 (BRT) X-Virus-Scanned: amavisd-new at eletrobrasalagoas.com Received: from mail.eletrobrasalagoas.com ([127.0.0.1]) by localhost (mail.eletrobrasalagoas.com [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id TrDxZYB2_Lmd for ; Wed, 17 Jan 2018 03:23:32 -0300 (BRT) Received: from mail.ceal.com.br (unknown [106.203.68.175]) by mail.eletrobrasalagoas.com (Postfix) with ESMTPSA id 48D7916E32F for ; Wed, 17 Jan 2018 03:23:28 -0300 (BRT) Date: Wed, 17 Jan 2018 09:37:54 +0300 Subject: FWD: Interested Message-Id: From: "mark.saad" To: "FreeBSD" MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: base64 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, 17 Jan 2018 06:48:16 -0000 SGl5YSBGcmVlQlNEDQoNCg0KaHR0cDovL2JpdC5seS8ybUp4bkpPDQoNCg0KDQoNCg0KbWFyay5z YWFk From owner-freebsd-stable@freebsd.org Wed Jan 17 13:38:26 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 24630E70AD2 for ; Wed, 17 Jan 2018 13:38:26 +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 E7CCD6F3E1 for ; Wed, 17 Jan 2018 13:38:25 +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 w0HDcOCx084784 (version=TLSv1 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for ; Wed, 17 Jan 2018 08:38:24 -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 w0HDcN4U016747 for ; Wed, 17 Jan 2018 08:38:23 -0500 (EST) (envelope-from mike@sentex.net) To: FreeBSD-STABLE Mailing List From: Mike Tancsa Subject: Ryzen issues on FreeBSD ? Organization: Sentex Communications Message-ID: <8e842dec-ade7-37d1-6bd8-856ea1a827ca@sentex.net> Date: Wed, 17 Jan 2018 08:38:22 -0500 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.5.2 MIME-Version: 1.0 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, 17 Jan 2018 13:38:26 -0000 With the Intel issues exposed in meltdown, we were looking at possibly deploying some Ryzen based servers for FreeBSD. We got a pair of ASUS PRIME X370-PRO and CPU: AMD Ryzen 5 1600X Six-Core Processor (3593.34-MHz K8-class CPU) Origin="AuthenticAMD" Id=0x800f11 Family=0x17 Model=0x1 Stepping=1 Everything is at its default in the BIOS, no overclocking etc. However, we are seeing random lockups on both boxes. It doesnt seem to correspond with load/activity. And its a hard lockup. Keyboard not responsive and I cant break to serial debugger, so it doesnt seem to be an issue with something in the kernel going into deadlock. It sort of feels like a hardware issue, but it seems odd that both boxes are showing the same issue with random lockups like that. It could be twice in a day or once every 3 days. Anyone have any insights ? Anyone have any suggestions about better motherboards out there ? We are waiting for Supermicro's Epyc availability, but nothing yet. It would be nice if we could find a board with at least some hardware watchdog on it. ---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 Wed Jan 17 13:43: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 DCAB1E71036 for ; Wed, 17 Jan 2018 13:43:13 +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 AB66A6F81A for ; Wed, 17 Jan 2018 13:43:13 +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 1ebnzh-000BjP-GW for freebsd-stable@freebsd.org; Wed, 17 Jan 2018 13:43:09 +0000 Subject: Re: Ryzen issues on FreeBSD ? To: freebsd-stable@freebsd.org References: <8e842dec-ade7-37d1-6bd8-856ea1a827ca@sentex.net> From: Pete French Message-ID: <3b625072-dfb3-6b4f-494d-7fe1b2fa554c@ingresso.co.uk> Date: Wed, 17 Jan 2018 13:43:09 +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: <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-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, 17 Jan 2018 13:43:14 -0000 I am in much the same situation as you (want to deploy Epyc, waiting for SM stuff to become available). I currently have here a set of parts to make a test Ryzen box, so you are ahead of me on that though. Should have that gong this week I hope. Are you running the latest STABLE ? There were some patches for Ryzen which went in I belive, and might affect te stability. Specificly the chnages to stop it locking up when executing code in the top page ? I'll get back to you when I have done some more testing... -pete. On 17/01/2018 13:38, Mike Tancsa wrote: > With the Intel issues exposed in meltdown, we were looking at possibly > deploying some Ryzen based servers for FreeBSD. We got a pair of > ASUS PRIME X370-PRO and > > CPU: AMD Ryzen 5 1600X Six-Core Processor (3593.34-MHz > K8-class CPU) > Origin="AuthenticAMD" Id=0x800f11 Family=0x17 Model=0x1 Stepping=1 > > Everything is at its default in the BIOS, no overclocking etc. > > However, we are seeing random lockups on both boxes. It doesnt seem to > correspond with load/activity. And its a hard lockup. Keyboard not > responsive and I cant break to serial debugger, so it doesnt seem to be > an issue with something in the kernel going into deadlock. > > It sort of feels like a hardware issue, but it seems odd that both boxes > are showing the same issue with random lockups like that. It could be > twice in a day or once every 3 days. > > Anyone have any insights ? Anyone have any suggestions about better > motherboards out there ? We are waiting for Supermicro's Epyc > availability, but nothing yet. It would be nice if we could find a > board with at least some hardware watchdog on it. > > > ---Mike > From owner-freebsd-stable@freebsd.org Wed Jan 17 13:47: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 B1EFBE715A6 for ; Wed, 17 Jan 2018 13:47:05 +0000 (UTC) (envelope-from nimrod@nimrod.is-a-geek.net) Received: from mail-yw0-x229.google.com (mail-yw0-x229.google.com [IPv6:2607:f8b0:4002:c05::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 781DC70325 for ; Wed, 17 Jan 2018 13:47:05 +0000 (UTC) (envelope-from nimrod@nimrod.is-a-geek.net) Received: by mail-yw0-x229.google.com with SMTP id m19so8304200ywh.12 for ; Wed, 17 Jan 2018 05:47:05 -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=zXgOlz73V7aYiN0dRlgZi65AAuA9wu4p4y+WpWzGDtM=; b=TqAECLJCpXGxlf/1MU2HhkXCxmwSSYZWLRRUx4dRCh+VDc2lg4gXraFmUCUZcPKeLR i5MAwFTRfLFnKyVgyG/egJ9MJERC9pWsLABMCTo7vDNTvq2246FNItvc9K/SOkMPszIF u9PZMvmn43IDGlaM5/4anDAjAyNr7nInSLBw16XXoTYSCa/Bzz5Q3zhuKUWXwLzfM63k VoKnpld9lpw4/WqPNznnNNxUlIMFCcUBarYj5OaYH2hmVu+9Q66AeVzrwwhd8WBFqgGU M6KrIHaswFobb1kLTNeDiVhrDXMGOO5nc05Zt9JLFRqFKFwe4ZrFxcWXwLKSvXu2O8jk OmgQ== 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=zXgOlz73V7aYiN0dRlgZi65AAuA9wu4p4y+WpWzGDtM=; b=F07rIFM6SRytwuOQ/fokUniNHRE/6RGraxRE9Aweus2I/PwetFIrgW/rTdSive+THH bnUDxt63umjcavXu2MnXVzdFx/msypt7XkNRF/VIPXmvl2DenTUNmJ3065Ad2TaQjF4S viFp1XynkIX1NdNpHGxrsW0zmjtWNbBMSk+uw/HD0bv3GKMqqtzMtNPEgaQ/IVmzACoK JiuDxZpuJ6zElyqDUM79y/+6sTbTuA4euLQGPPlkigfkYMZlkg4I7iw+Ty7Lg+ecNvrg l6mvP616NSlhb1G1u5RnhDHPy7pDX5n48dD2cB+92pefTtw7oy+my3lLwPTqr331UYwa +oPA== X-Gm-Message-State: AKwxytfnScAoJ6u2mvsY21F91foZ2hkh5ZUoCc7zENMu/agkClhmjO/w IjPH9qjeiKm3c4hwgQmGemSWm1/R9Siqd6UxESbeOQ== X-Google-Smtp-Source: ACJfBosnf97NieLeLnMwUesp8oikTWStwEMUCH6zlSWqZZOaXb6VBAEIdvadkEzi1Rjw0SFe/xLjtTAAkdQ/W+Uh0V8= X-Received: by 10.129.159.17 with SMTP id w17mr2724152ywg.23.1516196824081; Wed, 17 Jan 2018 05:47:04 -0800 (PST) MIME-Version: 1.0 References: <8e842dec-ade7-37d1-6bd8-856ea1a827ca@sentex.net> In-Reply-To: <8e842dec-ade7-37d1-6bd8-856ea1a827ca@sentex.net> From: Nimrod Levy Date: Wed, 17 Jan 2018 13:46:53 +0000 Message-ID: Subject: Re: Ryzen issues on FreeBSD ? To: Mike Tancsa Cc: 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, 17 Jan 2018 13:47:05 -0000 I've been seeing similar issues on Ryzen and asked some questions, here https://lists.freebsd.org/pipermail/freebsd-stable/2017-December/088121.html My previous queries didn't go anywhere. -- Nimrod On Wed, Jan 17, 2018 at 8:38 AM Mike Tancsa wrote: > With the Intel issues exposed in meltdown, we were looking at possibly > deploying some Ryzen based servers for FreeBSD. We got a pair of > ASUS PRIME X370-PRO and > > CPU: AMD Ryzen 5 1600X Six-Core Processor (3593.34-MHz > K8-class CPU) > Origin="AuthenticAMD" Id=0x800f11 Family=0x17 Model=0x1 Stepping=1 > > Everything is at its default in the BIOS, no overclocking etc. > > However, we are seeing random lockups on both boxes. It doesnt seem to > correspond with load/activity. And its a hard lockup. Keyboard not > responsive and I cant break to serial debugger, so it doesnt seem to be > an issue with something in the kernel going into deadlock. > > It sort of feels like a hardware issue, but it seems odd that both boxes > are showing the same issue with random lockups like that. It could be > twice in a day or once every 3 days. > > Anyone have any insights ? Anyone have any suggestions about better > motherboards out there ? We are waiting for Supermicro's Epyc > availability, but nothing yet. It would be nice if we could find a > board with at least some hardware watchdog on it. > > > ---Mike > > -- > ------------------- > 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 From owner-freebsd-stable@freebsd.org Wed Jan 17 14:31:50 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 9D77AE73DA7 for ; Wed, 17 Jan 2018 14:31:50 +0000 (UTC) (envelope-from mike@sentex.net) Received: from smarthost2.sentex.ca (smarthost2.sentex.ca [IPv6:2607:f3e0:80:80::2]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client CN "smarthost.sentex.ca", Issuer "smarthost.sentex.ca" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 64FBE71E9C for ; Wed, 17 Jan 2018 14:31:50 +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 w0HEVnxD095421 (version=TLSv1 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for ; Wed, 17 Jan 2018 09:31:49 -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 w0HEVlOW016860; Wed, 17 Jan 2018 09:31:48 -0500 (EST) (envelope-from mike@sentex.net) Subject: Re: Ryzen issues on FreeBSD ? To: Nimrod Levy Cc: FreeBSD-STABLE Mailing List References: <8e842dec-ade7-37d1-6bd8-856ea1a827ca@sentex.net> From: Mike Tancsa Organization: Sentex Communications Message-ID: <90f00307-6ce6-a116-9736-3d4a4518de24@sentex.net> Date: Wed, 17 Jan 2018 09:31:47 -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, 17 Jan 2018 14:31:50 -0000 On 1/17/2018 8:46 AM, Nimrod Levy wrote: > I've been seeing similar issues on Ryzen and asked some questions, > here https://lists.freebsd.org/pipermail/freebsd-stable/2017-December/088121.html > > My previous queries didn't go anywhere.   > Thats not very promising :( Googling around, shows lots of similar reports both on FreeBSD and Linux, but its a lot of "I tweaked this BIOS setting and so far so good" but nothing definitive / conclusive. Having to mess about with hardware settings for days on end hoping to fix random lockups is .... not good. ---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 Wed Jan 17 15:04:36 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 B0AC7E75945 for ; Wed, 17 Jan 2018 15:04:36 +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 67D2273246 for ; Wed, 17 Jan 2018 15:04:36 +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 w0HF4ZWD001828 (version=TLSv1 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for ; Wed, 17 Jan 2018 10:04:35 -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 w0HF4Xmu016952; Wed, 17 Jan 2018 10:04:33 -0500 (EST) (envelope-from mike@sentex.net) Subject: Re: Ryzen issues on FreeBSD ? To: Pete French , freebsd-stable@freebsd.org References: <8e842dec-ade7-37d1-6bd8-856ea1a827ca@sentex.net> <3b625072-dfb3-6b4f-494d-7fe1b2fa554c@ingresso.co.uk> From: Mike Tancsa Organization: Sentex Communications Message-ID: <2c6ce4dd-f43c-7c40-abc2-732d6f8996ec@sentex.net> Date: Wed, 17 Jan 2018 10:04:33 -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: <3b625072-dfb3-6b4f-494d-7fe1b2fa554c@ingresso.co.uk> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 8bit X-Scanned-By: MIMEDefang 2.78 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Jan 2018 15:04:36 -0000 On 1/17/2018 8:43 AM, Pete French wrote: > > Are you running the latest STABLE ? There were some patches for Ryzen > which went in I belive, and might affect te stability. Specificly the > chnages to stop it locking up when executing code in the top page ? Hi, I was testing with RELENG_11 as of 2 days ago. The fix seems to be there # sysctl -A hw.lower_amd64_sharedpage hw.lower_amd64_sharedpage: 1 Would love to find a class of motherboard that pushes its "You dont need to dork around with any BIOS settings. It just works. Oh, and we have a hardware watchdog too".... ipmi would be stellar. ---Mike From owner-freebsd-stable@freebsd.org Wed Jan 17 19:42:30 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 D627DEB3443 for ; Wed, 17 Jan 2018 19:42:30 +0000 (UTC) (envelope-from firmdog@gmail.com) Received: from mail-wm0-x22f.google.com (mail-wm0-x22f.google.com [IPv6:2a00:1450:400c:c09::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 5D9387EDFF for ; Wed, 17 Jan 2018 19:42:30 +0000 (UTC) (envelope-from firmdog@gmail.com) Received: by mail-wm0-x22f.google.com with SMTP id i11so17992785wmf.4 for ; Wed, 17 Jan 2018 11:42:30 -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=eNyIJO62nTHNbyPPf+KJ3Sbqz/6Es+etlfSxJ4JrpAc=; b=u1VtZPXixPfOgP/e7SUJe54FUjKFuCfEWdBaMYLe3CTA+MbJakcA+MQxHONcpeG+ne LuMu1ul7NNHxvM9Iw3fNCc0NoYU4HJKRpdMqwAFmGoQpzasKTxy6Ap4FYn/+sEL5623A clC8Owq0c0F/hsKuRmCDn3yGX4m+Q6QpGXqrh6zVVD4oA1O3rXJ6dxdztOk1ZYGTA2/d bxp/kdIngDtqPcH/wcemCCBT5l89PX9cFWgGl1haflXlUMI5eUQOvlE53tia/jhy0PnQ hCuri5SBkRldRKRG8e1bxDwP91qJxU6kakey+rV/1B6tySM36b1dFGsaRT/f3gyVZ82i CwHg== 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=eNyIJO62nTHNbyPPf+KJ3Sbqz/6Es+etlfSxJ4JrpAc=; b=MA5LDEaOD7urOKeqcJI/5tlSqDczrpRVFR9Boy1jCLTygkEIdTFN7BsKWHOHZerPJa /q1rOlJYJTcfRMlOHnaA4ZBSXYpeiiQDGk2XqrozeWWS7ruh0Hx/+3GjO7+28Bwy5sra iqu8cFcz2cD+G1PBEUy5k980C5Pufb6/G9q1uUc7i1OapSmSs6d9Cef0LcFeU9i8vr/r H5Czp/9a46iGRTo4yxnn+vWfr87d8V7abK0zjvjldL7YwY6x/V8GJCZ3lBuifbiaDVrn jagTlK70WfaPXLl+7ln+YkaeO8PS525wb68AVtfFIuOFdyQsNrOA2Z+gUWUTGThjfr/N LXSQ== X-Gm-Message-State: AKwxytdTRmP+fw3M2rwdMRoz6oHJJv8CsEEDdqtydyBUKyMtVw9emWIF E6aAXhawap3bJ1EWlq4nVtg64hQ4RLOyh3CtKqU= X-Google-Smtp-Source: ACJfBou/J9TQBTQc8gIYyqagG4xADfrSpLDDQQ4TLMLvtmfUy1sTrvZhM/vdLEBs7O22NZ3mI328LfXByZ4iWQ7GzD0= X-Received: by 10.28.54.221 with SMTP id y90mr2918606wmh.156.1516218148592; Wed, 17 Jan 2018 11:42:28 -0800 (PST) MIME-Version: 1.0 Received: by 10.223.154.102 with HTTP; Wed, 17 Jan 2018 11:42:28 -0800 (PST) In-Reply-To: References: From: Andy Firman Date: Wed, 17 Jan 2018 14:42:28 -0500 Message-ID: Subject: Re: upgrading from 10.0 to 10.3 problem To: Peter Lai Cc: freebsd-stable@freebsd.org, sem@semmy.ru 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, 17 Jan 2018 19:42:30 -0000 On Tue, Aug 23, 2016 at 1:47 PM, Peter Lai wrote: > > Hello. I tried to upgrade from 10.0-RELEASE: # freebsd-update -r > 10.3-RELEASE upgrade > > ... > > # freebsd-update install > > ... > > # reboot > > ... > > # freebsd-update install > > Installing updates...Segmentation fault (core dumped) > > Segmentation fault (core dumped) > > Segmentation fault (core dumped) > > Segmentation fault (core dumped) > > Segmentation fault (core dumped) > > Segmentation fault (core dumped) > > Segmentation fault (core dumped) > > Segmentation fault (core dumped) Now I have: > > # freebsd-version -ku > > 10.3-RELEASE-p4 > > 10.0-RELEASE It's not looking good. How to fix? PS. In /var/log/messages > I see "(gunzip), uid 0: exited on signal 11" > > And yes: > > # gunzip > > Segmentation fault (core dumped) > > Hi Sergey: > > I ran into this problem the week before you did: > https://lists.freebsd.org/pipermail/freebsd-stable/2016-July/085115.html > Because just about all of the binaries were trashed (including /lib, > /[s]bin, /usr/lib, /usr/[s]bin files were truncated to 0), I had to > /rescue/nc > base.txz (where I fetched base.txz from the ftp site in > the 10.3-RELEASE distribution), then /rescue/tar -zxvf base.txz into a > directory, then tar | tar each of /lib and so on to get my binaries > back (apparently /rescue does not have a statically compiled cpio). > > After sending the above to the mailing list I went ahead and replaced > the kernel that the broken freebsd-update install installed with the > one from 10.3-RELEASE (from the distribution base.txz:boot/kernel), > which made the system entirely binary 10.3-RELEASE then I was able to > freebsd-update to FreeBSD-10.3-RELEASE-p6 with no problems. Note that > the initial freebsd-update from 10.0 also severely trashed my /etc, I > had to restore master.passwd and friends! (many of /etc files were > also truncated to 0), even though the merge process seemed to complete > ok before the broken freebsd-update install. > _______________________________________________ > > I just experienced the same thing. Sent this to freebsd-questions last night, no response yet, so thought I would also try here on this thread. Here is my disaster from last night: *Following this guide:* https://www.freebsd.org/doc/handbook/updating-upgrading-freebsdupdate.html # uname -a FreeBSD 10.0-RELEASE-p9 FreeBSD 10.0-RELEASE-p9 #0: Mon Sep 15 14:35:52 UTC 2014 root@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64 *Run this command:* # freebsd-update -r 10.4-RELEASE upgrade # freebsd-update install reboot *Success...system came back up as 10.4* # uname -a FreeBSD 10.4-RELEASE-p3 FreeBSD 10.4-RELEASE-p3 #0: Tue Nov 14 09:43:55 UTC 2017 root@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64 *Run this command one more time per the guide above:* # freebsd-update install Installing updates...Segmentation fault (core dumped) Segmentation fault (core dumped) Segmentation fault (core dumped) Segmentation fault (core dumped) Segmentation fault (core dumped) *System is totally down and had to recover from snaphot* *What on earth happened here?* From owner-freebsd-stable@freebsd.org Wed Jan 17 20:39: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 908C7EB5FE4 for ; Wed, 17 Jan 2018 20:39: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 70DA981060 for ; Wed, 17 Jan 2018 20:39: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 w0HKe5ca073755 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=FAIL); Wed, 17 Jan 2018 20:40:07 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 w0HKdZbV022581 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 17 Jan 2018 12:39:36 -0800 (PST) (envelope-from truckman@FreeBSD.org) Date: Wed, 17 Jan 2018 12:39:30 -0800 (PST) From: Don Lewis Subject: Re: Ryzen issues on FreeBSD ? To: Mike Tancsa cc: Pete French , freebsd-stable@freebsd.org In-Reply-To: <2c6ce4dd-f43c-7c40-abc2-732d6f8996ec@sentex.net> 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> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=us-ascii Content-Disposition: INLINE X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Jan 2018 20:39:45 -0000 On 17 Jan, Mike Tancsa wrote: > On 1/17/2018 8:43 AM, Pete French wrote: >> >> Are you running the latest STABLE ? There were some patches for Ryzen >> which went in I belive, and might affect te stability. Specificly the >> chnages to stop it locking up when executing code in the top page ? > > Hi, > I was testing with RELENG_11 as of 2 days ago. The fix seems to be there > > # sysctl -A hw.lower_amd64_sharedpage > hw.lower_amd64_sharedpage: 1 > > Would love to find a class of motherboard that pushes its "You dont need > to dork around with any BIOS settings. It just works. Oh, and we have a > hardware watchdog too".... ipmi would be stellar. The shared page change fixed the random lockup and silent reboot problem for me. I've got a 1700X eight core CPU and a Gigabyte X370 Gaming 5. I did have to RMA my CPU (it was an early one) because it had the problem with random segfaults that seemed to be triggered by process migration between CPU cores. I still haven't switched over to using it for package builds because I see more random fallout than on my older package builder. I'm not blaming the hardware for that at this point because I see a lot of the same issues on my older machine, but less frequently. One thing to watch (though it should be less critical with a six core CPU) is VRM cooling. I removed the stupid plastic shroud over the VRM sink on my motherboard so that it gets some more airflow. From owner-freebsd-stable@freebsd.org Wed Jan 17 21:00:57 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 91F48EB71F2 for ; Wed, 17 Jan 2018 21:00:57 +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 3F99182100; Wed, 17 Jan 2018 21:00:57 +0000 (UTC) (envelope-from mike@sentex.net) Received: from lava.sentex.ca (lava.sentex.ca [IPv6:2607:f3e0:0:5::11]) by smarthost2.sentex.ca (8.15.2/8.15.2) with ESMTPS id w0HL0tQH077751 (version=TLSv1 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Wed, 17 Jan 2018 16:00:56 -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 w0HL0rPq020699; Wed, 17 Jan 2018 16:00:53 -0500 (EST) (envelope-from mike@sentex.net) Subject: Re: Ryzen issues on FreeBSD ? To: Don Lewis Cc: Pete French , 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> From: Mike Tancsa Organization: Sentex Communications Message-ID: <795dbb79-3c18-d967-98b9-5d09a740dbfe@sentex.net> Date: Wed, 17 Jan 2018 16:00: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, 17 Jan 2018 21:00:57 -0000 On 1/17/2018 3:39 PM, Don Lewis wrote: > On 17 Jan, Mike Tancsa wrote: >> On 1/17/2018 8:43 AM, Pete French wrote: >>> >>> Are you running the latest STABLE ? There were some patches for Ryzen >>> which went in I belive, and might affect te stability. Specificly the >>> chnages to stop it locking up when executing code in the top page ? >> >> Hi, >> I was testing with RELENG_11 as of 2 days ago. The fix seems to be there >> >> # sysctl -A hw.lower_amd64_sharedpage >> hw.lower_amd64_sharedpage: 1 >> >> Would love to find a class of motherboard that pushes its "You dont need >> to dork around with any BIOS settings. It just works. Oh, and we have a >> hardware watchdog too".... ipmi would be stellar. > > The shared page change fixed the random lockup and silent reboot problem > for me. I've got a 1700X eight core CPU and a Gigabyte X370 Gaming 5. I > did have to RMA my CPU (it was an early one) because it had the problem > with random segfaults that seemed to be triggered by process migration > between CPU cores. I still haven't switched over to using it for > package builds because I see more random fallout than on my older > package builder. I'm not blaming the hardware for that at this point > because I see a lot of the same issues on my older machine, but less > frequently. > > One thing to watch (though it should be less critical with a six core > CPU) is VRM cooling. I removed the stupid plastic shroud over the VRM > sink on my motherboard so that it gets some more airflow. Thanks! I will confirm the cooling. I tried just now looking at the CPU FAN control in the BIOS and up'd it to "turbo" from the default. Does amdtmp.ko work with your chipset ? Nothing on mine unfortunately, so I cant tell from the OS if its running hot. Is there a way to see if your CPU is old and has that bug ? I havent seen any segfaults on the few dozen buildworlds I have done. So far its always been a total lockup and not crash with RELENG11. x86info v1.31pre Found 12 identical CPUs Extended Family: 8 Extended Model: 0 Family: 15 Model: 1 Stepping: 1 CPU Model (x86info's best guess): AMD Zen Series Processor (ZP-B1) Processor name string (BIOS programmed): AMD Ryzen 5 1600 Six-Core Processor Monitor/Mwait: min/max line size 64/64, ecx bit 0 support, enumeration extension SVM: revision 1, 32768 ASIDs, np, lbrVirt, SVMLock, NRIPSave, TscRateMsr, VmcbClean, FlushByAsid, DecodeAssists, PauseFilter, PauseFilterThreshold Address Size: 48 bits virtual, 48 bits physical The physical package has 12 of 16 possible cores implemented. running at an estimated 3.20GHz ---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 Wed Jan 17 21:45:43 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 D1DD5EB9786 for ; Wed, 17 Jan 2018 21:45:43 +0000 (UTC) (envelope-from nimrod@nimrod.is-a-geek.net) Received: from mail-yw0-x235.google.com (mail-yw0-x235.google.com [IPv6:2607:f8b0:4002:c05::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 9C9E183A35 for ; Wed, 17 Jan 2018 21:45:43 +0000 (UTC) (envelope-from nimrod@nimrod.is-a-geek.net) Received: by mail-yw0-x235.google.com with SMTP id x190so9538422ywd.10 for ; Wed, 17 Jan 2018 13:45:43 -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=F/edqvqdK50pau7AIJAKGnU7/j4gxtKzi6LpgTFo1nw=; b=WC7L9vTDh3VfhlE5M/tzF75Qtncp94AJSdjzJTHVo33MiOUotf6xQ8WaRhOuELmmEG 2/Ju/8wYyGlDC3jJJpF3/mnGSaXu9E+7bCmDdNE7iXSOpIQNq7Cxl1HkEpuV6DbpOkY4 068UhIRUzodSg1TCMYdTy/v11M5CEVA8f5LMN5/MX1F+swnijb5UZk4F+Z4vbTKXBgPf RJlZuSkyWqzZbfLCmEAZpRWv6A6K6rzx7W9jVqka3xOz/TKNvweoI7TbVxUstO4Zx3SP ZYWmlLndaP2zcE4s/78I87Q7yOpnT+qrDlsuyI6AuLoT0/n9IrNsTtGOZR6oWxMRvptT tbDw== 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=F/edqvqdK50pau7AIJAKGnU7/j4gxtKzi6LpgTFo1nw=; b=n/w7GCw1D233q5oXBBfd1vCb/3l2aXM1/YZ2rm4Qx5W03MB3iG74YtTTitctQ9BpoK k53FMqdoHhN4jU/4F2qI1/2vKyWBTvTTIzIjZ448D4okpEi8PGj/exHz3yv+hJXbZ013 i3Iokj+pgq0WV7Ycw80lLPTmElwvfXVyVioS4fe1QXpV5zZsCO7mymXgTdXyqF5FzGQu W2MqkDhTuKxa0XJgFcDy2IX4hA9fXIrUNpK3eZD5yyncKXvmnvqO6tyRtMzyq0Q0T/qR swu1nGtozbk1BYokG0JlvElAHOBEpxLvuun48a4XzjfDp5zZP572VIo03+9R4NhE//Xk NQ4Q== X-Gm-Message-State: AKwxytf8qxxQ/POMlt9gwS1x++/5T2mSEUH8QTbugxipzBo/N6mZYl44 h7Q9lUy4iBhFJZtPV2BIZINrBzU6fZQtgajgLzEfqA9I X-Google-Smtp-Source: ACJfBotASqrHzPf1l9mBpKHqNcavi9ELU12XrtczsPxegZa+wdXKxhJ0y0ATxCEl0B1S3X3oG71HCwKNDwwgsz7Zesw= X-Received: by 10.37.136.14 with SMTP id c14mr8159168ybl.177.1516225542148; Wed, 17 Jan 2018 13:45:42 -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> In-Reply-To: <795dbb79-3c18-d967-98b9-5d09a740dbfe@sentex.net> From: Nimrod Levy Date: Wed, 17 Jan 2018 21:45:31 +0000 Message-ID: Subject: Re: Ryzen issues on FreeBSD ? To: Mike Tancsa Cc: Don Lewis , freebsd-stable@freebsd.org, Pete French 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, 17 Jan 2018 21:45:43 -0000 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 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). I'm glad to see that there has been some attention on this. I was a little disappointed by the earlier thread. I'm happy to help troubleshoot, but I'm not sure what information I can gather from a hard locked system that doesn't even show anything on the console. -- Nimrod On Wed, Jan 17, 2018 at 4:01 PM Mike Tancsa wrote: > On 1/17/2018 3:39 PM, Don Lewis wrote: > > On 17 Jan, Mike Tancsa wrote: > >> On 1/17/2018 8:43 AM, Pete French wrote: > >>> > >>> Are you running the latest STABLE ? There were some patches for Ryzen > >>> which went in I belive, and might affect te stability. Specificly the > >>> chnages to stop it locking up when executing code in the top page ? > >> > >> Hi, > >> I was testing with RELENG_11 as of 2 days ago. The fix seems to > be there > >> > >> # sysctl -A hw.lower_amd64_sharedpage > >> hw.lower_amd64_sharedpage: 1 > >> > >> Would love to find a class of motherboard that pushes its "You dont need > >> to dork around with any BIOS settings. It just works. Oh, and we have a > >> hardware watchdog too".... ipmi would be stellar. > > > > The shared page change fixed the random lockup and silent reboot problem > > for me. I've got a 1700X eight core CPU and a Gigabyte X370 Gaming 5. I > > did have to RMA my CPU (it was an early one) because it had the problem > > with random segfaults that seemed to be triggered by process migration > > between CPU cores. I still haven't switched over to using it for > > package builds because I see more random fallout than on my older > > package builder. I'm not blaming the hardware for that at this point > > because I see a lot of the same issues on my older machine, but less > > frequently. > > > > One thing to watch (though it should be less critical with a six core > > CPU) is VRM cooling. I removed the stupid plastic shroud over the VRM > > sink on my motherboard so that it gets some more airflow. > > Thanks! I will confirm the cooling. I tried just now looking at the CPU > FAN control in the BIOS and up'd it to "turbo" from the default. Does > amdtmp.ko work with your chipset ? Nothing on mine unfortunately, so I > cant tell from the OS if its running hot. > > Is there a way to see if your CPU is old and has that bug ? I havent > seen any segfaults on the few dozen buildworlds I have done. So far its > always been a total lockup and not crash with RELENG11. > > x86info v1.31pre > Found 12 identical CPUs > Extended Family: 8 Extended Model: 0 Family: 15 Model: 1 Stepping: 1 > CPU Model (x86info's best guess): AMD Zen Series Processor (ZP-B1) > Processor name string (BIOS programmed): AMD Ryzen 5 1600 Six-Core > Processor > > Monitor/Mwait: min/max line size 64/64, ecx bit 0 support, enumeration > extension > SVM: revision 1, 32768 ASIDs, np, lbrVirt, SVMLock, NRIPSave, > TscRateMsr, VmcbClean, FlushByAsid, DecodeAssists, PauseFilter, > PauseFilterThreshold > Address Size: 48 bits virtual, 48 bits physical > The physical package has 12 of 16 possible cores implemented. > running at an estimated 3.20GHz > > > > > ---Mike > > > > -- > ------------------- > 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 From owner-freebsd-stable@freebsd.org Wed Jan 17 21:46:03 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 19F17EB9822 for ; Wed, 17 Jan 2018 21:46:03 +0000 (UTC) (envelope-from marklmi26-fbsd@yahoo.com) Received: from sonic302-49.consmr.mail.ne1.yahoo.com (sonic302-49.consmr.mail.ne1.yahoo.com [66.163.186.175]) (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 D962583B33 for ; Wed, 17 Jan 2018 21:46:02 +0000 (UTC) (envelope-from marklmi26-fbsd@yahoo.com) X-YMail-OSG: PtW6cqUVM1n.T74bTNXWqDMI149KVK1njFd.USVbgbXpTpy8UmvL7nIgefnS6qM UKxKTuMjMIF38tGXTLrlchSGSkWVUUw9KosQnsYMeofkdC16hxOoH9BVMGc783Qr.2JZmveQ87V9 jMb4eYG8UO.SfU.m7E7xhRmfXz4YcNKLuUZxjEzDoZAecy7lcGNQKR2aWmJfDDwicP5ws0Ck2ugI 9fWDbGAzxEJKszl1wYVabFgaBtp0SB0VralIZDiIAblEWpGXvcWTyWSJFIIns_CK6VDebCGVgyBQ Qn7QqG.TEYdRFarxyaM6eLPHjXihhtSGEiCNzJefY5N3P12J_tkziBkIVNsSIdZ0BO1XMFWnjqzk dHY_Rr2QtSifnxhIqGzhfRGiLp8qAiiXvIq6h2ounkqFMszeShvAuWrrL.vTKCzhpzNn8OZHjVCg I1_aTKqiPnTX_tfSepfqEHNELFDUyZZbqg6JgpJCm_Y1FVE2GvsjtoWAOokSaEiChg21ggIiOZNJ jwg-- Received: from sonic.gate.mail.ne1.yahoo.com by sonic302.consmr.mail.ne1.yahoo.com with HTTP; Wed, 17 Jan 2018 21:45:55 +0000 Received: from smtp235.mail.ne1.yahoo.com (EHLO [192.168.1.25]) ([10.218.253.206]) by smtp414.mail.ne1.yahoo.com (JAMES SMTP Server ) with ESMTPA ID fa2db8d0081cf196d10a9d3861c8d989; Wed, 17 Jan 2018 21:21:42 +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 10.3 \(3273\)) Subject: Re: Ryzen issues on FreeBSD ? Message-Id: <11FD366F-9C52-4AB8-BB25-A94A97832300@yahoo.com> Date: Wed, 17 Jan 2018 13:21:41 -0800 To: mike@sentex.net, nimrodl@gmail.com, 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: Wed, 17 Jan 2018 21:46:03 -0000 Mike Tancsa mike at sentex.net wrote on: Wed Jan 17 14:31:50 UTC 2018 : > On 1/17/2018 8:46 AM, Nimrod Levy wrote: > > I've been seeing similar issues on Ryzen and asked some questions, > > here = https://lists.freebsd.org/pipermail/freebsd-stable/2017-December/088121.ht= ml > >=20 > > My previous queries didn't go anywhere. =20 > > > =20 >=20 >=20 > Thats not very promising :( Googling around, shows lots of similar > reports both on FreeBSD and Linux, but its a lot of "I tweaked this = BIOS > setting and so far so good" but nothing definitive / conclusive. = Having > to mess about with hardware settings for days on end hoping to fix > random lockups is .... not good. See Bugzilla 219399 and 221029 : https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D219399 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D221029 I'm not sure how much stable/11 and the like have been tracking things that were done in head (12) during this. My use has only been via versions of head. My 1800X use was basically after head was updated to deal with what 219399 eventually was isolated to. (221029 is from splitting off problems that were not originally known to be separate.) While I had problems for 1800X that are what the 221029 bugzilla above is about, I've not had such with a 1950X in the same sorts of contexts as I had been using the 1800X. But this was under Hyper-V for both processor variants (with matching boards). I've only tried the 1950X with a native FreeBSD boot once (a fair time ago). It showed a lockup problem fairly quickly (power switch/plug time). I've never seen such (or anything analogous) under Hyper-V with extensive use. It does not look like I'll be investigating native FreeBSD on the 1950X anytime soon. (I no longer have access to the 1800X.) =3D=3D=3D 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 Wed Jan 17 23:10: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 98A37EBE50F for ; Wed, 17 Jan 2018 23:10: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 7F0093FEA for ; Wed, 17 Jan 2018 23:10: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 w0HNB5DM074060 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=FAIL); Wed, 17 Jan 2018 23:11:07 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 w0HNAZJY027875 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 17 Jan 2018 15:10:36 -0800 (PST) (envelope-from truckman@FreeBSD.org) Date: Wed, 17 Jan 2018 15:10:30 -0800 (PST) From: Don Lewis Subject: Re: Ryzen issues on FreeBSD ? To: Mike Tancsa cc: Pete French , freebsd-stable@freebsd.org In-Reply-To: <795dbb79-3c18-d967-98b9-5d09a740dbfe@sentex.net> 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> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=us-ascii Content-Disposition: INLINE X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Jan 2018 23:10:45 -0000 On 17 Jan, Mike Tancsa wrote: > On 1/17/2018 3:39 PM, Don Lewis wrote: >> On 17 Jan, Mike Tancsa wrote: >>> On 1/17/2018 8:43 AM, Pete French wrote: >>>> >>>> Are you running the latest STABLE ? There were some patches for Ryzen >>>> which went in I belive, and might affect te stability. Specificly the >>>> chnages to stop it locking up when executing code in the top page ? >>> >>> Hi, >>> I was testing with RELENG_11 as of 2 days ago. The fix seems to be there >>> >>> # sysctl -A hw.lower_amd64_sharedpage >>> hw.lower_amd64_sharedpage: 1 >>> >>> Would love to find a class of motherboard that pushes its "You dont need >>> to dork around with any BIOS settings. It just works. Oh, and we have a >>> hardware watchdog too".... ipmi would be stellar. >> >> The shared page change fixed the random lockup and silent reboot problem >> for me. I've got a 1700X eight core CPU and a Gigabyte X370 Gaming 5. I >> did have to RMA my CPU (it was an early one) because it had the problem >> with random segfaults that seemed to be triggered by process migration >> between CPU cores. I still haven't switched over to using it for >> package builds because I see more random fallout than on my older >> package builder. I'm not blaming the hardware for that at this point >> because I see a lot of the same issues on my older machine, but less >> frequently. >> >> One thing to watch (though it should be less critical with a six core >> CPU) is VRM cooling. I removed the stupid plastic shroud over the VRM >> sink on my motherboard so that it gets some more airflow. > > Thanks! I will confirm the cooling. I tried just now looking at the CPU > FAN control in the BIOS and up'd it to "turbo" from the default. Does > amdtmp.ko work with your chipset ? Nothing on mine unfortunately, so I > cant tell from the OS if its running hot. > > Is there a way to see if your CPU is old and has that bug ? I havent > seen any segfaults on the few dozen buildworlds I have done. So far its > always been a total lockup and not crash with RELENG11. > > x86info v1.31pre > Found 12 identical CPUs > Extended Family: 8 Extended Model: 0 Family: 15 Model: 1 Stepping: 1 > CPU Model (x86info's best guess): AMD Zen Series Processor (ZP-B1) > Processor name string (BIOS programmed): AMD Ryzen 5 1600 Six-Core > Processor My original CPU had a date code of 1708SUT (8th week of 2017 I think), and the replacement has a date code of 1733SUS. There's a humungous discussion thread here where date codes are discussed. As I recall, the first replacement parts shipped had dates codes somewhere in the mid 20's, but I think AMD was still hand screening parts at that point. My replacement came in a sealed box, so it wasn't hand screened and AMD probably was able to screen for this problem in their production test. From owner-freebsd-stable@freebsd.org Wed Jan 17 23:38: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 C6C7FEBFA9D for ; Wed, 17 Jan 2018 23:38: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 9CE78687B6 for ; Wed, 17 Jan 2018 23:38: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 w0HNd6sY074106 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=FAIL); Wed, 17 Jan 2018 23:39:08 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 w0HNAZJe027875 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 17 Jan 2018 15:38:37 -0800 (PST) (envelope-from truckman@FreeBSD.org) Date: Wed, 17 Jan 2018 15:38:37 -0800 (PST) From: Don Lewis Subject: Re: Ryzen issues on FreeBSD ? To: Nimrod Levy cc: Mike Tancsa , freebsd-stable@freebsd.org, Pete French 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> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=us-ascii Content-Disposition: INLINE X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Jan 2018 23:38:45 -0000 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 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 From owner-freebsd-stable@freebsd.org Thu Jan 18 02:23: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 B9410E73CF6 for ; Thu, 18 Jan 2018 02:23:02 +0000 (UTC) (envelope-from nimrod@nimrod.is-a-geek.net) Received: from mail-yw0-x235.google.com (mail-yw0-x235.google.com [IPv6:2607:f8b0:4002:c05::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 864D56FF66 for ; Thu, 18 Jan 2018 02:23:02 +0000 (UTC) (envelope-from nimrod@nimrod.is-a-geek.net) Received: by mail-yw0-x235.google.com with SMTP id x24so9773713ywj.0 for ; Wed, 17 Jan 2018 18:23:02 -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=k1Gzt0pRcUfLiqICReXevAX1yVDmgLdTMdmkKWpSRh0=; b=sAVevUTPjoyUkfNzFBZIeNiKk59Cbgn9O/P6Rwpifgbca9ZGdBqv9J8NiLZZ1fH1mz Oaa6pshMwMAPUBLEaXi+m1K9lzSRxsWPWFsLi8CE9OskdMDHw7RIp1p/RB4AaNRqozwx 74QRWxNgRVpoLYuKWP6GV8cKHmmCnMGoP/qeFgY8Ce2NX43sHX3QoTuJBOnuwHgb8XnZ BxVJEHkh29uO09hQy0hhSQB1Hv+l/JskXT8wwrNqAaNMQx5sSfOPu4AhGxj+3l2A5oM7 rch58SuCASTUxSvSuwIPXyA+QXZxV/VqGnwD9oH9IKpJmeNM4WIY1mwFPQLbf0IN6diE gCIA== 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=k1Gzt0pRcUfLiqICReXevAX1yVDmgLdTMdmkKWpSRh0=; b=eTXSChV5c+ylYzOca5P9M3ncHE0iR8vAnchch2SzyzAC51q/Zivn3RVuswRFNA40yY DeiEBvXYwuVsjN2eO6+ztebnKxSn3//nZr6eU+Sj+vhMw/VYRXh+5k4K/t2Qy+NgXl7e XoRyoNeq4r5gvQpzoUxOgHBK/xzUHpJ+LleSTWO20f6K0I7G3aRxAQ5I69sWDD1UJ0xa 9Rop2dfBTmNrJ8U0O+y6iUALxUJ4v8Bab+e85xgY/K5KBNEgD3X8RFWMJQABkr0dI2ht J3Hh5KWa5VJKnwtf6beIxP46gAyzMq92pkEIa15nNmqGA7uSbQMqFDYrGZkH2uM7i5HL BzdA== X-Gm-Message-State: AKwxytdtfhM8K3ctI3f0Difx3FHA8S4OQSdGR5Rvl8ONYoFY5SgzW9P8 HM6d/5TEOY8C4DNhR+xvJe1Ui4na22oKJ9mKEsJJ5Q== X-Google-Smtp-Source: ACJfBosjEjA+rK7rYsehshk8YgEcE6NE14uvWmtLvCJkmwUUwwmlny790Q905LJGLmUpqf/UmOkgAMOuurm3POPCpgw= X-Received: by 10.13.246.1 with SMTP id g1mr4634185ywf.476.1516242181379; Wed, 17 Jan 2018 18:23:01 -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> In-Reply-To: From: Nimrod Levy Date: Thu, 18 Jan 2018 02:22:50 +0000 Message-ID: Subject: Re: Ryzen issues on FreeBSD ? To: Don Lewis Cc: Mike Tancsa , Pete French , 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: Thu, 18 Jan 2018 02:23:02 -0000 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 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 From owner-freebsd-stable@freebsd.org Fri Jan 19 12:28:46 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 30836ED3529 for ; Fri, 19 Jan 2018 12:28:46 +0000 (UTC) (envelope-from abrancatelli@schema31.it) Received: from benzedrina.milano.schema31.it (benzedrina.schema31.it [IPv6:2001:470:6d:3ff::2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "benzedrina.milano.schema31.it", Issuer "benzedrina.milano.schema31.it" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id B56657F343 for ; Fri, 19 Jan 2018 12:28:45 +0000 (UTC) (envelope-from abrancatelli@schema31.it) Received: from smtp.schema31.it (localhost [127.0.0.1]) by benzedrina.milano.schema31.it (8.15.2/8.15.2) with ESMTP id w0JCSfRQ011823 for ; Fri, 19 Jan 2018 13:28:41 +0100 (CET) (envelope-from abrancatelli@schema31.it) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=schema31.it; s=gCloud; t=1516364921; bh=Rltjb66ehOXN10whVyuOHX5t4fb4XKm3W64BK00sT38=; h=Date:From:To:Subject; b=CaXcPDyyO2+PwAtEKAR4o/SXfNpJRpdIyOuWAZMLkO1m4y3ETSV1QQYod8eXpDFpy YfMI1NU7Ri0htaRpgXudnyeBk/8RVuqUd4OxVMIIvp1KiEOko8elREhbXGZu3nw/v1 p/sJ4I0twQTDvqziN7tyJfkv9xqN6nTs+YuohivMuTSHJ5w/y4mQdAOmpwRQMl2tQx GmyRK0wTW1kVtfd95nsMqcPfzL+UW49d8rTcZcn6dXN6vml70I+mEMrPJ5ZSq3CtVh FvM34QKaclZECPIPFOiobTrDtRx4PJvWsKt5Sw+B27kHHIqf0f6u86xI9w2wyIYLwK NPJ0wwiUOuVVQ== MIME-Version: 1.0 Date: Fri, 19 Jan 2018 13:28:41 +0100 From: Andrea Brancatelli To: freebsd-stable@freebsd.org Subject: Ancient FreeBSD update path Organization: Schema31 s.r.l. Message-ID: <03c972a8f098b1b547da690efaad771f@schema31.it> X-Sender: abrancatelli@schema31.it User-Agent: Roundcube Webmail/1.3.4 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit 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, 19 Jan 2018 12:28:46 -0000 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. -- Andrea Brancatelli From owner-freebsd-stable@freebsd.org Fri Jan 19 12:59: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 1A9EBED45FC for ; Fri, 19 Jan 2018 12:59:22 +0000 (UTC) (envelope-from michaelp@bsquare.com) Received: from NAM03-DM3-obe.outbound.protection.outlook.com (mail-dm3nam03on0725.outbound.protection.outlook.com [IPv6:2a01:111:f400:fe49::725]) (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 B957480774 for ; Fri, 19 Jan 2018 12:59:21 +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=PYe1Nph2RAlHyBTH6jOOa6H0vA6zWmKnBNUrmX18uk8=; b=Kmd2dO6ByzQ8WeR05oJaqMAIyy3QEZil4nwl1TpQgAQt4Fr7YgcAcKJnOEM/MaXerU0/Ba6nQYsc7kKniuhYJUV/WHAUz1eMAMs7oASTMFXfnBiv/t5iIsw5MEi7LD+hPSvbQfGQ1KGhhtX180yYXD67h1yjXXx/sgeSbQcx1jk= 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.428.9; Fri, 19 Jan 2018 12:59:18 +0000 Subject: Re: Ancient FreeBSD update path To: freebsd-stable@freebsd.org References: <03c972a8f098b1b547da690efaad771f@schema31.it> From: Mike Pumford Message-ID: <1c0b0fb4-c324-b58f-3f2a-51a1272ce26b@bsquare.com> Date: Fri, 19 Jan 2018 12:59:09 +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: <03c972a8f098b1b547da690efaad771f@schema31.it> 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: AM5P190CA0008.EURP190.PROD.OUTLOOK.COM (10.161.47.149) To CY4PR1301MB2023.namprd13.prod.outlook.com (10.171.223.157) X-MS-PublicTrafficType: Email X-MS-Office365-Filtering-Correlation-Id: e79485a5-7b64-4c71-c9dc-08d55f3c73f1 X-Microsoft-Antispam: UriScan:; BCL:0; PCL:0; RULEID:(7020095)(4652020)(7021125)(5600026)(4604075)(4534125)(7022125)(4602075)(4603075)(4627221)(201702281549075)(7048125)(7024125)(7027125)(7028125)(7023125)(2017052603307)(7153060)(7193020); SRVR:CY4PR1301MB2023; X-Microsoft-Exchange-Diagnostics: 1; CY4PR1301MB2023; 3:F9ZQec5PJlImYWf6nizDutksnTGewqD17KUIRPeOOPVx8kDop5ps8dVfF2FjieMGQqwxH8By8yANCGFo3sgBw8S+kabnZnhTeqfzfcAo4s9ZmbeTRp9lz/c8kpAZN+vn7b3tVwX2dU6jT2QUdRh/3+CQNBWR+4s7/8EFY/HlsJLBKVM2C3qc+TGpEsKf9Kd9st6fFbm5dQutjwrL9jvgR88yaOlhJdznKp9LfxfJC0qW5c/PmU39FEGIt0/mi9td; 25:CRHknbsLRfgMCcGApiEx2MA+/yttqux0Hl1tLJ9KYPZaQeZkY7/+aVL5gCpNqyDjE1NSq/JmuTelogB3Ygjl9tjgUPyM8xFPB6P4R9gT5RM6xA5u+ESdTjuFriuNs1PaJ2bI78W95WHn0gradqpRX34iHGYie50XtL5SBdIRrCE8ODQHJM7zo771Rn7LAzj0H0WLHHoryNg2lY5Ysog90aZ6xYb1R1cKVJ7cWhvPeZQRyOaTTiC4rUPGYZJ4ZzQG7b5hOr+XMl7QSjs5pe/JILP5IzPhYOihDDi7YbUc0VfKKWRQ6xyKwvEZQlxSmLpTICHHHVZ+Q96Q6tbDDKxQUQ==; 31:PLmVt8c7ZyeV0szyYH3CzVIV1vcYdGJStdeI0CUqvhBqrfWRikvnCODNHkGBu+n3FxbcIEJXINC2RQBolIseW1dRQMNxHDRyb+ZCJWK1MCLSExkc+MNZ3FQsWrO3wo3WnR8TaU9KrlkoMpmdJNAHEK/y4UgFzq7n6bXpMAH2iXS3wHIpBReDwDKOINjxnUtTNV+cxWj/RAvdSxWx3d0+/zGspfGCekLeFv4hvMqln4A= X-MS-TrafficTypeDiagnostic: CY4PR1301MB2023: X-Microsoft-Antispam-PRVS: X-Exchange-Antispam-Report-Test: UriScan:(192374486261705); X-Exchange-Antispam-Report-CFA-Test: BCL:0; PCL:0; RULEID:(2401047)(8121501046)(5005006)(93006095)(93001095)(10201501046)(3002001)(3231023)(944501161)(2016111802025)(20161123562045)(20161123564045)(20161123560045)(20161123558120)(6072148)(6043046)(6042181)(201708071742011); SRVR:CY4PR1301MB2023; BCL:0; PCL:0; RULEID:(100000803101)(100110400095); SRVR:CY4PR1301MB2023; X-Microsoft-Exchange-Diagnostics: 1; CY4PR1301MB2023; 4:rcGbrNMDEE+EHsceAWGwtwWrKw+QM0j/CpZz7MoZ8Anj2qNsG8E34QvbZ70zbxS47WGqBajnWgYM/zUFQWTwTxr0KK/6V10GvvM/X1/k2GuVhp3s+wv2rO6mDu2OsBvD+1Z/ANvkjTTFFF5S8MvQyS2M1IY0nH0hQk0dHH4Ik9ZsOWT08ygs9eL0V/e0iuoKBF0DE1tmJ/0+0tIxFdavuTQ1mKW3tMRjhjTAsjHyCK7m1q2kCg0F23KTmRQoOSvhxl446uqXm0EKlBJ6Rfp4QZkfpY3ykLcSffuq1S0Zk1JJtAFaJGIynffrcymAsqZI X-Forefront-PRVS: 0557CBAD84 X-Forefront-Antispam-Report: SFV:NSPM; SFS:(10019020)(6049001)(396003)(39850400004)(39380400002)(346002)(366004)(376002)(199004)(189003)(229853002)(6246003)(6486002)(64126003)(2351001)(7736002)(31686004)(3260700006)(25786009)(83506002)(36756003)(26005)(105586002)(66066001)(47776003)(65806001)(65956001)(3846002)(230700001)(2361001)(16576012)(58126008)(2486003)(76176011)(77096007)(50466002)(86362001)(67846002)(23676004)(52146003)(97736004)(53546011)(81166006)(3480700004)(478600001)(15650500001)(8936002)(81156014)(2950100002)(305945005)(52116002)(386003)(6116002)(6916009)(106356001)(68736007)(31696002)(53936002)(59450400001)(90366009)(551544002)(6666003)(2906002)(5660300001)(316002)(16526018)(8676002)(65826007)(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?MTtDWTRQUjEzMDFNQjIwMjM7MjM6QVlBNTdQNlNOaVFpNE1sN0pnSlJGVzhZ?= =?utf-8?B?VjV5Z3plTDQxelE4NTRnV2s3MkJjNU56V2d3VXNNNjRjZGxjVlVucEJZclVF?= =?utf-8?B?cUFsZlN5RnFqOFlqOXRRRHRvc3BSNkVuczdBa0ZtcXl3bDJoeVM4ZElDYnl3?= =?utf-8?B?NFcybmp1dGNPMkNSYXhqY2t5UDhnMHBtTGpuYUNtemtPcHRTWVErelg1UEZR?= =?utf-8?B?d25pN2hreEdJbVlKQ3E3VDZ6eEp6Vi80ZWFOVlJySmVSNEg0NklSbWtiSytO?= =?utf-8?B?aExxRUJTVWpHSXJtTU4yZk0yMDVBeCtLcm13SFRQS0s5Q2VBNjdCbHFiMW5w?= =?utf-8?B?bkdSNWpYNlR0aG1LakQ0aXlSZmROdkZVdHRiZnZ1YWNrQjhCMFdISm54WlNU?= =?utf-8?B?NHM1VURFaG80bGY2WGtiU05HWlJxRjNYSEtxbWhiV0ZQY2ZyWTQyMkNpZmxR?= =?utf-8?B?N1l0dmlZWEtpTzlic1J0KzUzejJYV0VEMFVxaktOUHI3YzkyVmRtaFI4Um4w?= =?utf-8?B?empVOXRQNVVQYjZuTEFXUFEyaEhMQzZPSUsyb01EU3kzSzB3Vm9GUDdiSDRU?= =?utf-8?B?YkFVRklXbmpnSHlTQ3EvNVUrZDI2VjY2RmZyZmtKSTZJWm5RVjFrSWE5emNj?= =?utf-8?B?cmJDTTlsZ1B6S1hUTkV3YVR5OEVUbTZtcEpCRzV2ZUNJUVkvelVHZHJRaTEw?= =?utf-8?B?UVh1a0h0UzFSNDR3MnZvZWxBVjBNK2ZsTjR3dU5KUURVOFQzMEVQSHQrZXdS?= =?utf-8?B?a203dXNjWnE4NHpOd09zdXZDOUhKNEZsUjdtTytzbWdvWTJSWCt1elpsUUpl?= =?utf-8?B?TEVLQXhvNEdOUGVSUXJmakNBK2FWV1JxU3lsbmVxa2VwV291L1ZVWmw5Y0RY?= =?utf-8?B?UGdBTE5yald0QlFSajBlRVdWNjBIMVJxMUNZQ0VZb1FwSkhDQ0J5Um4zaWQ0?= =?utf-8?B?SmFiWHl2S3A4ZGhjaHFRYmJNc3VKSGU1QkZzM3ozNDBIeVZBaU5FajVSdTZR?= =?utf-8?B?UU9wRTFsNnhrZExFMmtDanNrNlVieFo2ZDk1Q0RyOXhocE1rbXczejZMN3FZ?= =?utf-8?B?NkhHWndyb25rcVZOeDZBLytubFpKQVMzV2pwVStZVTJTLzhoR3lpSDVHUGpz?= =?utf-8?B?YUcxeDZVaFMzT3dTS2lQZHg0YjJsNmNnbjArcS8zakZSRnA0VTN4TEpsSW5U?= =?utf-8?B?NFFYQS9PYnk2WVo0V0NUb0ZPYWd5cGF2UlFZZklBSlZUZWk5QVJtVzNRWThs?= =?utf-8?B?Y3JNemJCZ1Rwbkl6enNyVkcvVFllanMrU21CTUNRYXVDK1J4Wk5mYS9ZcG9O?= =?utf-8?B?enBHOUdibmpjamNLQk9jSUtOQ1o4KytkZTA4a013d1FUbjBld2k2czlJM0JB?= =?utf-8?B?LzkvbjM3Y3FzTkFEQ2NqMTgzZGdXcU8xQlNVY3Ewemw3ZkQ0VDVuL3JLRjN1?= =?utf-8?B?NjFtRHNvcUJMSzVodktSNGYzSkM4R1JCWWlpa1Z2a1RxUnhLci85eVRvbHE1?= =?utf-8?B?TitHVlZxc2NRRkdMZmlYVlZBREx6N2VjandqelAyKzU5SEZ5Vk1EUm5ZQkJZ?= =?utf-8?B?NXpaaS8zL1BLcytNenZJRmdmL0xUZE14MkkrNDBxZWtFd1Zpcm1yWlF6WEw1?= =?utf-8?B?TFFZQmRQdk1qeXg5aEd1ZDVPdmpqVU1JV1hMdTFMa2JvWklFdnhXS0kxQnFi?= =?utf-8?B?bWI1UVRvNFd3ZXZFWUVlRy8rYWNqbmZVdmg1dEliV0ltNTNqN3MzWWFkMmJu?= =?utf-8?B?WDdzaWdnZUNMUXJ1ZlYxZUZYZU9tQnFPczVUdXRYeGt2VFN4aTBhcjUwaDlD?= =?utf-8?B?dUIzR0Y5bkk0Y1Y2UjI2QzkySCtiWTVqbHJhZzJITzdiYmtOY3ZpY1BHN0Vi?= =?utf-8?B?VFRzQ2NzNCs3VHRmcUdWeGxmQzVadU1EU2xHdDZtdHdQODU1YjROVDNJelRp?= =?utf-8?B?WEN4bUZDT3ZpKzFQZkt2RDIzaVFXOXFwVjVxNXY0Z0lGSnN2Q3ZRUHVXQXNX?= =?utf-8?B?OThmQ29SWHB3OE9qZEx1c0IyRG1UWWhMQndYeTFuUVhkOFBEUGtLSnF1Mmxw?= =?utf-8?B?Tmc3SklLWmMwbzdsRUE3T2tBZ0pKL3RXVnV2ZzNDZlZrTkVSc3dKYUVTU2hZ?= =?utf-8?B?RVovZz09?= X-Microsoft-Exchange-Diagnostics: 1; CY4PR1301MB2023; 6:xSZ0xTBZ0GoDGtHN2ZcyO3hfUNxQYQmDY9jVJZvBnEr3fDD1eGtqNhKk7S809BsgjpL9z3j4c4nXkx6chqwsLJrWBUAqO0mdR8uqS7hvcxmEtJn6sxDiAn9a5OlGye95k98HsXG0w5JGYKGFllvHqfemufVzbnkAStWwjPy9C6ljnqdzqK6kDpvTQ0/4YiX4BacxsCMxQgAk7ybSvlCZ/vFeFMNKTkD5Aihh3m3kWpZ7SzQM4zWKk+NvThkAFO30dfq3XIgDchX59DBwJOLvZJBpH/HHJvScxLuxXbBu0C31m9uFECKa24nxc6Nkt9v3j1h0ra9fGafLEGtNLDwbDn/GE4lH/jtzbYTEnUjLrSI=; 5:Vf/25vPsDU418HOPXt4WUh5biITyY425SNk3shFQFkoi96G0IUbhnLfwbQ8EPxi9445tM8JsPCrbnbi/YBCh+hipy1lJH0HkMyI9K/UXI+GZUOkJD1XNC1Ui1KkIYwRny6uzIwZCQkgcveWdJP8hrjTtstBLXFyd3TD4SE0a7Fo=; 24:PClgEHXbb/N1X+0G21fNMz2ruHqJ6Ql4Ep5HOMyXOoaTzM84Ee+BdnRSEenHiYrpcPmohmrDIHt20vX48RGxgbSQZy/LOgzDivjLgWZNJng=; 7:eWgFjU5+uacNbW+2OZejA94siEbpReIRrku+3qBgpSDwbXicKfyqNA3/MHmMPavv+qlCvXW6rXFBAYiu6bAa3TCSTJs3vCeRYayQ4ZJDA70WZwdOZNmY8QDeKUL97SNluoezuxwSGS1U+TQWN97kwJZfVfpDikkqeZStLym2rCXC2+tZEHVAiWcYo4Q4A0OO8j7mCxBXBnHEe8obvthF8H7O7qds8ntz/RRaTa2LdKyfMeQoHEWTXi257VBJ2aLW SpamDiagnosticOutput: 1:99 SpamDiagnosticMetadata: NSPM X-OriginatorOrg: bsquare.com X-MS-Exchange-CrossTenant-OriginalArrivalTime: 19 Jan 2018 12:59:18.5851 (UTC) X-MS-Exchange-CrossTenant-Network-Message-Id: e79485a5-7b64-4c71-c9dc-08d55f3c73f1 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: Fri, 19 Jan 2018 12:59:22 -0000 On 19/01/2018 12:28, Andrea Brancatelli wrote: > 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. > I've just done a 9.3 to 10.3 upgrade with freebsd-update and pkg. Networking wasn't avalable when the system was running 10.3 kernel with 9.3 userland so I did that part of the update on the console. That system started life as a FreeBSD 5.x system and got left to rot at that version for a long time because it was an internal system with no external security exposure. I gradually upgraded it (using source builds) from major version to major version until I got to 9.3 and then did the 9.3 to 10.3 as a binary upgrade. Only other trap I fell into with was packages. The system uses ldap for auth although fortunately it does have some local network accessible accounts. ldap auth was broken until I did the package update as the 9.3 pam_ldap modules caused SSH to delay password based authentication and the auth processes seg-faulted. > What upgrade strategy would you suggest? > > Direct jump into the future (8 -> 11)? Progressive steps (8 -> 9 -> 10 > -> 11)? Boiling water on the HDs? :-) > If freebsd-update will do an upgrade from 8 to 10 or 8 to 11 and you have console access it ought to work. The upgrade process can be rolled back if the system doesn't like the new kernel for some reason and nothing gets installed anywhere else until the second stage of the upgrade. I'd probably go via 8->9.3->10/11 as those are the upgrade paths that were well tested. Also don't forget the full system backups before starting. :) Mike From owner-freebsd-stable@freebsd.org Fri Jan 19 14:24: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 A9B96EB5052 for ; Fri, 19 Jan 2018 14:24:55 +0000 (UTC) (envelope-from lists@opsec.eu) Received: from home.opsec.eu (home.opsec.eu [IPv6:2001:14f8:200::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 737A9838D0 for ; Fri, 19 Jan 2018 14:24:55 +0000 (UTC) (envelope-from lists@opsec.eu) Received: from pi by home.opsec.eu with local (Exim 4.89 (FreeBSD)) (envelope-from ) id 1ecXbB-000Mie-UC; Fri, 19 Jan 2018 15:24:53 +0100 Date: Fri, 19 Jan 2018 15:24:53 +0100 From: Kurt Jaeger To: Andrea Brancatelli Cc: freebsd-stable@freebsd.org Subject: Re: Ancient FreeBSD update path Message-ID: <20180119142453.GA58156@home.opsec.eu> References: <03c972a8f098b1b547da690efaad771f@schema31.it> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <03c972a8f098b1b547da690efaad771f@schema31.it> 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, 19 Jan 2018 14:24:55 -0000 Hi! > 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? The best way is to update stepwise using freebsd-update, so: 8.0 -> 8.3 -> 9.1 -> 9.3 -> 10.1 -> 10.3 > Direct jump into the future (8 -> 11)? Progressive steps (8 -> 9 -> 10 > -> 11)? Boiling water on the HDs? :-) Stepwise. Huge jumps have too many rough edges. -- pi@opsec.eu +49 171 3101372 2 years to go ! From owner-freebsd-stable@freebsd.org Fri Jan 19 16:23: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 5C04FEBADCF for ; Fri, 19 Jan 2018 16:23:52 +0000 (UTC) (envelope-from fjwcash@gmail.com) Received: from mail-lf0-x231.google.com (mail-lf0-x231.google.com [IPv6:2a00:1450:4010:c07::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id D464A638E3 for ; Fri, 19 Jan 2018 16:23:51 +0000 (UTC) (envelope-from fjwcash@gmail.com) Received: by mail-lf0-x231.google.com with SMTP id k19so2763360lfj.1 for ; Fri, 19 Jan 2018 08:23:51 -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=saQIj0HNUm6W4mIkW6+ST7TU3vSZT0kVVueD+xhZP8k=; b=qME0ZXbOeNYIsdc+9t8MqJiR/mWU7zaRLKzKmwdUsowVpJwhJJtK0kt3uQbzo4jscX GtxlAH1n8YxXKMsjerxB+SoVOMzzbfnRAcLI/uEJ2DW9YWvfcNiGk1i/enNfpFwOpq5P 0F9mXNOkc1GlJaVxMnOQg95EWgxcteHnzhnQKdI7Be7cLedRtZv81lC1dHViqz/eX7Up 8tc1BvbVwFPhmf8Qb5dh0IT2ElEehYL13FGEmhP+lxcVAAvVOhienC1bRmS2MNiScKoD 2qadXU26hlvUqNnyVpRLD1E856R/a0CVbO9mCkoYtuwa83W5Oz6fjK1zoptaGgOdZVmW yQDQ== 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=saQIj0HNUm6W4mIkW6+ST7TU3vSZT0kVVueD+xhZP8k=; b=n5U1BWpVbGEgAg/UXI2HvJo4sLXTXT0D8gXhkX5WbGyPKwUzxL9diyhY7z/MsbI9n6 zboJOSjjxYbTBVnl1q+nn3k4CaHXPJ/JtCTbODCOsd+IjwnSG4RUpalZsjJ4PtjKVh9p wOrWdfAEQYSfHA6XRt0bN9xbKwg8TM6fUTYk1H6RyQlwYrcIICTdxiLvGeIZLl4AEigG HZY7ZvcRFBA7uVhfrwmfuJ7vyZK7NJbi7RqCmWAR1GhOwdqwO+fjy/bme7JkCNHX2VQF KNMHlkfY2UKvA6gyDzzXRTAJdw8Vm0ILreFk21+diwa4BaBZI/v5EypfYQSrp7a02enC xSkg== X-Gm-Message-State: AKwxytcoiae3rBcOX+DRNP8ZmWv4LsKlSKvS+27TQkqkFlY3sBEcwvHU x4RAAsXrhwKiWFkFs4CfRWI7cp1uZxqWVvL8MunmDQ== X-Google-Smtp-Source: AH8x227BNeoSFDAWedq0rFr19DeTZTYZhU1m4x1/F1IL8OnPKeYbxTgiCL1aVJx4zzulHvjbWp4Q8oKfe1aGJo/WlCM= X-Received: by 10.25.163.68 with SMTP id m65mr1438522lfe.83.1516379029342; Fri, 19 Jan 2018 08:23:49 -0800 (PST) MIME-Version: 1.0 Received: by 10.25.15.199 with HTTP; Fri, 19 Jan 2018 08:23:48 -0800 (PST) In-Reply-To: <03c972a8f098b1b547da690efaad771f@schema31.it> References: <03c972a8f098b1b547da690efaad771f@schema31.it> From: Freddie Cash Date: Fri, 19 Jan 2018 08:23:48 -0800 Message-ID: Subject: Re: Ancient FreeBSD update path To: Andrea Brancatelli Cc: FreeBSD Stable Content-Type: text/plain; charset="UTF-8" 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, 19 Jan 2018 16:23:52 -0000 On Fri, Jan 19, 2018 at 4:28 AM, Andrea Brancatelli < abrancatelli@schema31.it> wrote: > 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? :-) > =E2=80=8BI like to do it in steps. It takes longer, but the results tend t= o be better. 8.0 --> last 8.x release --> 9.0 --> last 9.x release --> 10.0 --> last 10.x release --> 11.0 --> last 11.x release Backup /usr/local/etc and any other configuration files that are strewn about. Then format/delete /usr/ports/* and /usr/local/* and install the ports/packages you need. Of course, for something that ancient, it would probably be faster/better to just backup the config files, format the drives, and install 11.1 from scratch. :) --=20 Freddie Cash fjwcash@gmail.com From owner-freebsd-stable@freebsd.org Fri Jan 19 16:38:47 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 2A2DAEBB7C4 for ; Fri, 19 Jan 2018 16:38:47 +0000 (UTC) (envelope-from mat@aragorn.in.absolight.net) Received: from prod2.absolight.net (prod2.absolight.net [79.143.243.136]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "plouf.absolight.net", Issuer "CAcert Class 3 Root" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id E49776815C for ; Fri, 19 Jan 2018 16:38:46 +0000 (UTC) (envelope-from mat@aragorn.in.absolight.net) Received: from prod2.absolight.net (localhost [127.0.0.1]) by prod2.absolight.net (Postfix) with ESMTP id A737ABDD37; Fri, 19 Jan 2018 17:38:44 +0100 (CET) Received: from gw.in.absolight.net (gw-ecl.in.absolight.net [79.143.241.69]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "gw.in.absolight.net", Issuer "CA Cert Signing Authority" (not verified)) by prod2.absolight.net (Postfix) with ESMTPSA id 875DFBDD35; Fri, 19 Jan 2018 17:38:44 +0100 (CET) Received: from aragorn.in.absolight.net (aragorn.in.absolight.net [79.143.241.225]) by gw.in.absolight.net (Postfix) with ESMTP id 13558610F; Fri, 19 Jan 2018 17:38:44 +0100 (CET) Received: by aragorn.in.absolight.net (Postfix, from userid 1000) id D4DA63CCF2; Fri, 19 Jan 2018 17:38:43 +0100 (CET) Date: Fri, 19 Jan 2018 17:38:43 +0100 From: Mathieu Arnold To: Andrea Brancatelli Cc: freebsd-stable@freebsd.org Subject: Re: Ancient FreeBSD update path Message-ID: <20180119163843.GA2251@aragorn.in.absolight.net> References: <03c972a8f098b1b547da690efaad771f@schema31.it> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="8t9RHnE3ZwKMSgU+" Content-Disposition: inline In-Reply-To: <03c972a8f098b1b547da690efaad771f@schema31.it> User-Agent: Mutt/1.9.2 (2017-12-15) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Jan 2018 16:38:47 -0000 --8t9RHnE3ZwKMSgU+ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Jan 19, 2018 at 01:28:41PM +0100, Andrea Brancatelli wrote: > Hello guys.=20 >=20 > I have a couple of ancient FreeBSD install that I have to bring into > this century (read either 10.4 or 11.1) :-)=20 >=20 > I'm talking about a FreeBSD 8.0-RELEASE-p4 and a couple of FreeBSD > 9.3-RELEASE-p53.=20 >=20 > What upgrade strategy would you suggest?=20 >=20 > Direct jump into the future (8 -> 11)? Progressive steps (8 -> 9 -> 10 > -> 11)? Boiling water on the HDs? :-)=20 >=20 > Thanks, any suggestion in more than welcome. The *supported* upgrade strategy is to upgrade to the latest version of your current branch, and jump from latest version to latest version. So 8.4 -> 9.3 -> 10.4 -> 11.1. (Note that you can stay at 10.4, it still is supported.) --=20 Mathieu Arnold --8t9RHnE3ZwKMSgU+ Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQKTBAABCgB9FiEEOraXidLtEhBkQLpbOkUW81GDzkgFAlpiHxBfFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDNB QjY5Nzg5RDJFRDEyMTA2NDQwQkE1QjNBNDUxNkYzNTE4M0NFNDgACgkQOkUW81GD zkifoRAAsWJyOTUZFJFNs6DULRJlFBKDQBrASgWVtzYhQ539zJnFlO5v5l+5s55k 0NQGaH+WcGWmjB31/KLltQucnTsMxaLYSNXrgFPhFwIG8PfQzPgnzKprJj++9ReZ pEexhkkZNbrJvu3e+OkG/UHI8unvbDahCLnoRXpp1lFhsDPeSf2hboBZQE1Cq+ex uBkyZdo3cazZXYtcYqejSCTVo+qrIXybMkm+6vp17NZbFxR0qrtpa8bHFdRZjcxH 0iVs/337IeJu7oEyWosVIcyzng8s+K2fTU6wyz06kwK5E9DhvLOYh/z6V2fS2emY UO3sBEvCRal6oTL3uRkqm8vt9VgsXLK/ytMO714hSTZt5+RnN7wpNVIs+Z6gPjRR qMohMNfj+fa11ZWY2fDf5KWsvD95Y3ULItTfXBcY2PBoicde0fIAK3d7XrAv4zDs gkVOHOZhCTbsOznmlGNkqyH8qJ8Zh3ybyU0C6pui9HALwBSeCpkQ9RGqOx0UZh8G S+zaZCtGuK7zEfyV2XYR6/4lU5Ffj0BDtzUPvwuva+40ESVzjAPjcqcfY5oth5eN 5hI6exw5ABKym9PU7REk0cooIniZYbC79juPyvrbMxhdZ6b/z0aKWf9DyszTXZgA W2bgh458IlzMx8r1ssYx6pVm4GWBQvDslegpBbKKt5Ft4JJkQ40= =S0b2 -----END PGP SIGNATURE----- --8t9RHnE3ZwKMSgU+-- From owner-freebsd-stable@freebsd.org Fri Jan 19 16:44:08 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 04DF7EBBD45 for ; Fri, 19 Jan 2018 16:44:08 +0000 (UTC) (envelope-from SRS0=67Qk=EO=quip.cz=000.fbsd@elsa.codelab.cz) Received: from elsa.codelab.cz (elsa.codelab.cz [94.124.105.4]) (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 BEF0B6870B for ; Fri, 19 Jan 2018 16:44:07 +0000 (UTC) (envelope-from SRS0=67Qk=EO=quip.cz=000.fbsd@elsa.codelab.cz) Received: from elsa.codelab.cz (localhost [127.0.0.1]) by elsa.codelab.cz (Postfix) with ESMTP id 2A71A28417; Fri, 19 Jan 2018 17:43:59 +0100 (CET) Received: from illbsd.quip.test (ip-86-49-16-209.net.upcbroadband.cz [86.49.16.209]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by elsa.codelab.cz (Postfix) with ESMTPSA id 4CBDC2840C; Fri, 19 Jan 2018 17:43:58 +0100 (CET) Subject: Re: Ancient FreeBSD update path To: Kurt Jaeger , Andrea Brancatelli Cc: freebsd-stable@freebsd.org References: <03c972a8f098b1b547da690efaad771f@schema31.it> <20180119142453.GA58156@home.opsec.eu> From: Miroslav Lachman <000.fbsd@quip.cz> Message-ID: <6bd4212c-df36-2fa5-26cf-565c5ca4d576@quip.cz> Date: Fri, 19 Jan 2018 17:43:57 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Firefox/52.0 SeaMonkey/2.49.1 MIME-Version: 1.0 In-Reply-To: <20180119142453.GA58156@home.opsec.eu> Content-Type: text/plain; charset=UTF-8; format=flowed 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, 19 Jan 2018 16:44:08 -0000 Kurt Jaeger wrote on 2018/01/19 15:24: > Hi! > >> 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? > > The best way is to update stepwise using freebsd-update, so: > > 8.0 -> 8.3 -> 9.1 -> 9.3 -> 10.1 -> 10.3 I would recommend source upgrade instead of binary freebsd-update. It is more predictable then freebsd-update if you are updating sooo old system >> Direct jump into the future (8 -> 11)? Progressive steps (8 -> 9 -> 10 >> -> 11)? Boiling water on the HDs? :-) > > Stepwise. Huge jumps have too many rough edges. I did upgrade from 8.4 to 10.2 or 10.3, not sure. There was some make warning in make installworld phase so I did "make installworld" twice to be sure everything is OK. There is (maybe) simpler way - download (or create own) tar balls of base and kernel of your target version (10.4 or 11.1), unpack it over old system (in single user) then you can use make delete-old if you will have /usr/src with updated source. Miroslav Lachman From owner-freebsd-stable@freebsd.org Fri Jan 19 20:09:03 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 F0694EC50F9 for ; Fri, 19 Jan 2018 20:09:03 +0000 (UTC) (envelope-from nimrod@nimrod.is-a-geek.net) Received: from mail-yb0-x22c.google.com (mail-yb0-x22c.google.com [IPv6:2607:f8b0:4002:c09::22c]) (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 B2E3872145 for ; Fri, 19 Jan 2018 20:09:03 +0000 (UTC) (envelope-from nimrod@nimrod.is-a-geek.net) Received: by mail-yb0-x22c.google.com with SMTP id u35so1047074ybi.1 for ; Fri, 19 Jan 2018 12:09:03 -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=mrP8+asDxv7TezbXEZexCc8lk3XFK6ncoZ8n7wR4ju8=; b=lhek7w/srJZnInl6BHJTBc+CWMZP3VmW8e2/UqHem2hm+yKQiw7lOOkFodmOyX6Pzj f8t0OU/odrHT/1cyQhPhYl6jOfrE1lqd2AhEZ2m9buORUPiKKNSRSLqj6L/daBVXE8wY 0rBcgbVrlp4rKXcyDl2RTV6jFXeYUFhX1gpOZ9dJkNcPr2A7JDThBZNf4C6zQiYeoIJa 4TLGnIkutlPsISW4POM39KlWu2qGjo3CiSixsaPUhR0td2ND/8qX7WKuN24UyymXCS+L +2zismI6MItgeDxAYG3EU7zOv8tP2A59Oi7I4bRiMecmb7M+h6c+3IpcFjjYCFi76yq2 Bo1g== 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=mrP8+asDxv7TezbXEZexCc8lk3XFK6ncoZ8n7wR4ju8=; b=fPLDwHoUULxyjLrT57lwj9gEiSaMvPi2w3IvR/vF8O9w3RSNVB6qdZ3uZJUdi8Na6a 6vBbpuhDaSl5Gc8a3eebM7V2XvYYKMlxzRGaoh5mWCRuAODInhdHLkTxx7VbdR0yioG8 GHURWxK+3l0BJVoa26oqqWgemaMZhnJsLw6DM53bnQrlYgCkkRv/sL6qbU8Ev7SpIOln dwgWSAFasTV0oLHJ28d2fQqu8S4VydplSjl+pka2omDFRofneIJbQG8kGv4sFQuCXg0g 5ASerpsWO3kR5kDhx43ms2rfVqqc1echGG87GiyfxW6ERiO8KPCh6wyfH1aHiAoloy6E qEkQ== X-Gm-Message-State: AKwxytdJ10Mqngg8mY6b/2gJSnPuVlZV+AYGOuS+lDt8GpGYo+5mq+G+ yE+t45PET6TxuSiicRDGtojlwIE9Sd82X/u5C8bpxA== X-Google-Smtp-Source: ACJfBouOLWiTeLO4CPJ/9NYxVLSKiQD/7sxVQSoe/3HqZ27surGCwjMfj7qfwlX8emIayM9snnYoTlq9AktM+wtaRJI= X-Received: by 10.37.31.214 with SMTP id f205mr33934721ybf.236.1516392542237; Fri, 19 Jan 2018 12:09:02 -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> In-Reply-To: From: Nimrod Levy Date: Fri, 19 Jan 2018 20:08:51 +0000 Message-ID: Subject: Re: Ryzen issues on FreeBSD ? To: Don Lewis Cc: Mike Tancsa , Pete French , 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: Fri, 19 Jan 2018 20:09:04 -0000 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 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 From owner-freebsd-stable@freebsd.org Fri Jan 19 20:13: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 BD9F8EC54F4 for ; Fri, 19 Jan 2018 20:13:28 +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 6F6B47262B; Fri, 19 Jan 2018 20:13:28 +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 w0JKDQJi083332 (version=TLSv1 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Fri, 19 Jan 2018 15:13:26 -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 w0JKDOJa039415; Fri, 19 Jan 2018 15:13:24 -0500 (EST) (envelope-from mike@sentex.net) Subject: Re: Ryzen issues on FreeBSD ? To: Nimrod Levy , Don Lewis Cc: Pete French , 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> From: Mike Tancsa Organization: Sentex Communications Message-ID: Date: Fri, 19 Jan 2018 15:13:24 -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: Fri, 19 Jan 2018 20:13:28 -0000 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 > 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 > -- ------------------- 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 Fri Jan 19 20:22:18 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 A827FEC5D87; Fri, 19 Jan 2018 20:22:18 +0000 (UTC) (envelope-from luke@foolishgames.com) Received: from stargazer.midnightbsd.org (stargazer.midnightbsd.org [IPv6:2001:470:1f11:1c7::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "stargazer.midnightbsd.org", Issuer "COMODO RSA Domain Validation Secure Server CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 6940072F19; Fri, 19 Jan 2018 20:22:18 +0000 (UTC) (envelope-from luke@foolishgames.com) Received: from www.midnightbsd.org (stargazer.midnightbsd.org [IPv6:2001:470:1f11:1c7:0:0:0:1]) (authenticated bits=0) by stargazer.midnightbsd.org (8.15.2/8.15.2) with ESMTPA id w0JKMGpx046237; Fri, 19 Jan 2018 15:22:16 -0500 (EST) (envelope-from luke@foolishgames.com) X-Virus-Status: Clean X-Virus-Scanned: clamav-milter 0.99.2 at stargazer.midnightbsd.org X-Authentication-Warning: stargazer.midnightbsd.org: Host stargazer.midnightbsd.org [IPv6:2001:470:1f11:1c7:0:0:0:1] claimed to be www.midnightbsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Date: Fri, 19 Jan 2018 15:22:16 -0500 From: Lucas Holt To: Mike Tancsa Cc: FreeBSD-STABLE Mailing List , owner-freebsd-stable@freebsd.org Subject: Re: Ryzen issues on FreeBSD ? In-Reply-To: <8e842dec-ade7-37d1-6bd8-856ea1a827ca@sentex.net> References: <8e842dec-ade7-37d1-6bd8-856ea1a827ca@sentex.net> Message-ID: <8dcf6cc8fad788ac8168a4a9f392b02e@foolishgames.com> X-Sender: luke@foolishgames.com User-Agent: Roundcube Webmail/1.2.3 X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.4.3 (stargazer.midnightbsd.org [IPv6:2001:470:1f11:1c7:0:0:0:1]); Fri, 19 Jan 2018 15:22:17 -0500 (EST) 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, 19 Jan 2018 20:22:18 -0000 I have an Asus Prime X370-pro and a Ryzen 7 1700 that I bought in late April. Make sure you have the latest BIOS for these boards or else it will randomly freak out. While i haven't used it much with FreeBSD, I can confirm that I had a lot of stability issues solved with a December BIOS update on MidnightBSD. I back ported the shared page fix and amdtemp. (it's basically FreeBSD 9.1) I couldn't even get it to boot until the August BIOS update. I've had my box stay up at least a week, and it's my primary development box so I'm mostly doing src/ports builds all the time on it. If you have the latest BIOS, check the memory timings too. It's rather picky with some memory modules. Luke From owner-freebsd-stable@freebsd.org Fri Jan 19 20:30:09 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 EAABBEC6256; Fri, 19 Jan 2018 20:30:09 +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 8ED93731F1; Fri, 19 Jan 2018 20:30:09 +0000 (UTC) (envelope-from mike@sentex.net) Received: from lava.sentex.ca (lava.sentex.ca [IPv6:2607:f3e0:0:5::11]) by smarthost2.sentex.ca (8.15.2/8.15.2) with ESMTPS id w0JKU8fd087015 (version=TLSv1 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Fri, 19 Jan 2018 15:30:08 -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 w0JKU5ui039438; Fri, 19 Jan 2018 15:30:06 -0500 (EST) (envelope-from mike@sentex.net) Subject: Re: Ryzen issues on FreeBSD ? To: Lucas Holt Cc: FreeBSD-STABLE Mailing List , owner-freebsd-stable@freebsd.org References: <8e842dec-ade7-37d1-6bd8-856ea1a827ca@sentex.net> <8dcf6cc8fad788ac8168a4a9f392b02e@foolishgames.com> From: Mike Tancsa Organization: Sentex Communications Message-ID: <23c1d162-dcd8-c422-3114-d70b65b6c271@sentex.net> Date: Fri, 19 Jan 2018 15:30:05 -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: <8dcf6cc8fad788ac8168a4a9f392b02e@foolishgames.com> 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: Fri, 19 Jan 2018 20:30:10 -0000 On 1/19/2018 3:22 PM, Lucas Holt wrote: > I have an Asus Prime X370-pro and a Ryzen 7 1700 that I bought in late Thanks! Thats the board I have, but no luck with amdtemp. Did you have to change the source code for it to work ? dmidecode shows Manufacturer: ASUSTeK COMPUTER INC. Product Name: PRIME X370-PRO Vendor: American Megatrends Inc. Version: 3402 Release Date: 12/11/2017 Address: 0xF0000 Runtime Size: 64 kB ROM Size: 16 MB Characteristics: memory is Type: DDR4 Type Detail: Synchronous Unbuffered (Unregistered) Speed: 2133 MT/s Manufacturer: Unknown Serial Number: 192BE196 Asset Tag: Not Specified Part Number: CT16G4DFD824A.C16FHD Rank: 2 Configured Clock Speed: 1067 MT/s Minimum Voltage: 1.2 V Maximum Voltage: 1.2 V Configured Voltage: 1.2 V When I try and load the kld, I get nothing :( 0(ms-v1)# kldload amdtemp 0(ms-v1)# dmesg | tail -2 ums0: at uhub0, port 3, addr 1 (disconnected) ums0: detached 0(ms-v1)# > April.  Make sure you have the latest BIOS for these boards or else it > will randomly freak out. > > While i haven't used it much with FreeBSD, I can confirm that I had a > lot of stability issues solved with a December BIOS update on > MidnightBSD. I back ported the shared page fix and amdtemp.  (it's > basically FreeBSD 9.1) > > I couldn't even get it to boot until the August BIOS update.  I've had > my box stay up at least a week, and it's my primary development box so > I'm mostly doing src/ports builds all the time on it. > > If you have the latest BIOS, check the memory timings too.  It's rather > picky with some memory modules. > > Luke > > -- ------------------- 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 Fri Jan 19 20:32:35 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 DB07EEC66E6 for ; Fri, 19 Jan 2018 20:32:35 +0000 (UTC) (envelope-from rroot@rootautomation.com) Received: from mail.4fast.net (mail.4fast.net [209.232.198.3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.4fast.net", Issuer "Go Daddy Secure Certificate Authority - G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 98DED736C4 for ; Fri, 19 Jan 2018 20:32:35 +0000 (UTC) (envelope-from rroot@rootautomation.com) Received: (qmail 79967 invoked by uid 89); 19 Jan 2018 20:23:40 -0000 Received: by simscan 1.4.0 ppid: 79738, pid: 79954, t: 0.0803s scanners: clamav: 0.99.2/m:58/d:24236 Received: from 69-36-196-169.cot.net (HELO ?192.168.0.2?) (rroot@rootautomation.com@69.36.196.169) by mail.4fast.net with ESMTPA; 19 Jan 2018 20:23:40 -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> From: Ryan Root Message-ID: <9b769e4e-b098-b294-0bce-8bb1c42e8a59@rootautomation.com> Date: Fri, 19 Jan 2018 12:23:38 -0800 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-Transfer-Encoding: quoted-printable Content-Language: en-US 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, 19 Jan 2018 20:32:35 -0000 Have you double checked the qualified vendors list data for your motherboard.=C2=A0 Sometimes memory chips not on the list will work as it= 's probably only a list of ones they've tested but it might be the problem in this situation.=C2=A0 If that was already brought up by someone else s= orry for butting in. This looks like the QVL list for your MB -> http://download.gigabyte.us/FileList/Memory/mb_memory_ga-ax370-Gaming5.pd= f 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.= =C2=A0 >> >> 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.=C2=A0 amdtemp works for me.= =C2=A0 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.=C2=A0 I'll update to the latest= STABLE >> and see >> > what=C2=A0 happens. >> > >> > One weird thing about my experience is that if I keep >> something running >> > continuously like the distributed.net >> client on 6 of 12 possible threads, >> > it keeps the system up for MUCH longer than without.=C2=A0 T= his is >> a home server >> > and very lightly loaded (one could argue insanely overpowere= d >> for the use >> > case). >> >> This sounds like the problem with the deep Cx states that has = been >> reported by numerous Linux users.=C2=A0 I think some motherboa= rd >> brands are >> more likely to have the problem.=C2=A0 See: >> http://forum.asrock.com/forum_posts.asp?TID=3D5963&title=3Dtai= chi-x370-with-ubuntu-idle-lock-ups-idle-freeze >> >> --=20 >> >> -- >> Nimrod >> >> >> >> --=20 >> >> -- >> Nimrod >> > From owner-freebsd-stable@freebsd.org Fri Jan 19 20:32:56 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 EB86DEC6728 for ; Fri, 19 Jan 2018 20:32:55 +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 96DE273731 for ; Fri, 19 Jan 2018 20:32:55 +0000 (UTC) (envelope-from peter@hda3.com) Received: by mail-qt0-x22f.google.com with SMTP id i1so6907952qtj.8 for ; Fri, 19 Jan 2018 12:32:55 -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=B8zPbKHF2SStiPzXxerGlVjnfTF3nAQHQn6g9zyf61A=; b=t/oCAinbpp4WtZsEdvIj8giD+nUR2UZ0P85sxzvLZ1sOpYxKkJ+TR2m7m8A4mQV6Vy v05uSGRzcFaWQJ8fXIEDGmPsrU8yGMUoc7vOqpKjBmutNPB1O7pHmQYpuLeJoFXZcxWq B01b5klxHJsl+xafpaaYcrjH9Td+raXTIE50Xjn9j98vr1Psp0NXPqQeE4giNxGNhYKD 0jOirrN6pILJ3ccMvsGw853REQbwXM3h7wAsIr454kFE/yLQKEmhkkWT6m+8NQ6nSWyA t4/KmKx2NtyUeOYescf23HjjqvH4afwiWK74865qvcKFpaw4IEIu5OHZrV9FfGTgNdtE mWNA== 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=B8zPbKHF2SStiPzXxerGlVjnfTF3nAQHQn6g9zyf61A=; b=Mzerox5feT22pagQvgj87oLxkNz48rV1yTlo1XKFP8+U3mZIkZv7wPu0pppGBL9BkJ PWDGbPOCCuPgWfWn3iUVr+7fbIekld17buol8hAmSPRwF/NX9nzsN2Gl2Kppo/3mPxjT WeogeZgELCLEe34uo9u46/VZaKziMmWM6vzhVop/YuQYMjgmhZWRz7LbUIZNS2BNUk64 chjUw0YbPLR1WDPL8/RW0YVjes+I/Bj2eZsoEM/akSQgqRqUdByXnWthBoAj5faq8OQB dKfQRwdbjFj3ilkuiLSmy0JgERBR/eJhZCgCyiDt0fqk4CVsscd/mBrbohwuIewtBIDj U+lg== X-Gm-Message-State: AKwxytfSf/KZ0C9IgcpGRvucKErCZcxvFb2rpo+24841PZAlSAaeaDT3 LNceWgKIdCeM3Pq6+KsFO5OF+Zq7JMwgCo/MdwSBYo9F X-Google-Smtp-Source: ACJfBot4eppmt+2bvh85nAYrBODb1+A0a5dGH5Jb7tIGhuQz/Vg/NSyTtMelYSUMqElLW/erYTbilrTq/KZ7gUKgWtE= X-Received: by 10.200.23.66 with SMTP id u2mr38594308qtk.294.1516393974446; Fri, 19 Jan 2018 12:32:54 -0800 (PST) MIME-Version: 1.0 Received: by 10.140.39.83 with HTTP; Fri, 19 Jan 2018 12:32:33 -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> From: Peter Moody Date: Fri, 19 Jan 2018 12:32:33 -0800 Message-ID: Subject: Re: Ryzen issues on FreeBSD ? To: Mike Tancsa Cc: Nimrod Levy , Don Lewis , freebsd-stable@freebsd.org, Pete French 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: Fri, 19 Jan 2018 20:32:56 -0000 On Fri, Jan 19, 2018 at 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. it's too early for me to be 100% certain, but disabling SMT in the bios has thus far resulted in a more stable system. I have a ryzen5 1600X and an ASRock AB350M and I've tried just about everything in all of these threads; disabling C state (no effect), setting the sysctl (doesn't exist on my 11.1 RELEASE), tweaking voltage and cooling settings, rma'ing the board the cpu and the memory. nothing helped. last night I tried disabling SMT and, so far so good. >> 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 >> 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 >> > > > -- > ------------------- > 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 Fri Jan 19 20:37: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 64DD1EC6CB4; Fri, 19 Jan 2018 20:37:45 +0000 (UTC) (envelope-from luke@foolishgames.com) Received: from stargazer.midnightbsd.org (stargazer.midnightbsd.org [IPv6:2001:470:1f11:1c7::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "stargazer.midnightbsd.org", Issuer "COMODO RSA Domain Validation Secure Server CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 2CBEE73DD6; Fri, 19 Jan 2018 20:37:45 +0000 (UTC) (envelope-from luke@foolishgames.com) Received: from www.midnightbsd.org (stargazer.midnightbsd.org [IPv6:2001:470:1f11:1c7:0:0:0:1]) (authenticated bits=0) by stargazer.midnightbsd.org (8.15.2/8.15.2) with ESMTPA id w0JKbgU6046709; Fri, 19 Jan 2018 15:37:43 -0500 (EST) (envelope-from luke@foolishgames.com) X-Virus-Status: Clean X-Virus-Scanned: clamav-milter 0.99.2 at stargazer.midnightbsd.org X-Authentication-Warning: stargazer.midnightbsd.org: Host stargazer.midnightbsd.org [IPv6:2001:470:1f11:1c7:0:0:0:1] claimed to be www.midnightbsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Date: Fri, 19 Jan 2018 15:37:42 -0500 From: Lucas Holt To: Mike Tancsa Cc: FreeBSD-STABLE Mailing List , owner-freebsd-stable@freebsd.org Subject: Re: Ryzen issues on FreeBSD ? In-Reply-To: <23c1d162-dcd8-c422-3114-d70b65b6c271@sentex.net> References: <8e842dec-ade7-37d1-6bd8-856ea1a827ca@sentex.net> <8dcf6cc8fad788ac8168a4a9f392b02e@foolishgames.com> <23c1d162-dcd8-c422-3114-d70b65b6c271@sentex.net> Message-ID: X-Sender: luke@foolishgames.com User-Agent: Roundcube Webmail/1.2.3 X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.4.3 (stargazer.midnightbsd.org [IPv6:2001:470:1f11:1c7:0:0:0:1]); Fri, 19 Jan 2018 15:37:43 -0500 (EST) 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, 19 Jan 2018 20:37:45 -0000 We have the same bios version. I have corsair RAM Handle 0x003B, DMI type 17, 40 bytes Memory Device Array Handle: 0x0032 Error Information Handle: 0x003A Total Width: 64 bits Data Width: 64 bits Size: 16384 MB Form Factor: DIMM Set: None Locator: DIMM_A2 Bank Locator: BANK 1 Type: Type Detail: Synchronous Unbuffered (Unregistered) Speed: 2666 MHz Manufacturer: Unknown Serial Number: 00000000 Asset Tag: Not Specified Part Number: CMK32GX4M2A2666C16 Rank: 2 Configured Clock Speed: 1333 MHz Minimum voltage: 1.200 V Maximum voltage: 1.200 V Configured voltage: 1.200 V I just double checked and amdtemp isn't working correctly. I was probably thinking of my other system which has an FX 8350. Luke From owner-freebsd-stable@freebsd.org Fri Jan 19 20:39: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 E526FEC6F07 for ; Fri, 19 Jan 2018 20:39:38 +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 989A473F73; Fri, 19 Jan 2018 20:39:38 +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 w0JKdb19089135 (version=TLSv1 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Fri, 19 Jan 2018 15:39:37 -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 w0JKdZT3039460; Fri, 19 Jan 2018 15:39:35 -0500 (EST) (envelope-from mike@sentex.net) Subject: Re: Ryzen issues on FreeBSD ? To: Peter Moody Cc: Nimrod Levy , Don Lewis , freebsd-stable@freebsd.org, Pete French 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> From: Mike Tancsa Organization: Sentex Communications Message-ID: Date: Fri, 19 Jan 2018 15:39:35 -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: Fri, 19 Jan 2018 20:39:39 -0000 On 1/19/2018 3:32 PM, Peter Moody wrote: > > I have a ryzen5 1600X and an ASRock AB350M and I've tried just about > everything in all of these threads; disabling C state (no effect), > setting the sysctl (doesn't exist on my 11.1 RELEASE), tweaking > voltage and cooling settings, rma'ing the board the cpu and the > memory. nothing helped. > > last night I tried disabling SMT and, so far so good. Is there anything that can be done to trigger the lockup more reliably ? I havent found any patterns. I have had lockups with the system is 100% idle and lockups when lightly loaded. I have yet to see any segfaults or sig 11s while doing buildworld (make -j12 or make -j16 even) ---Mike From owner-freebsd-stable@freebsd.org Fri Jan 19 20:48:35 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 10A25EC768C for ; Fri, 19 Jan 2018 20:48:35 +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 8782974683 for ; Fri, 19 Jan 2018 20:48: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 w0JKmWdB090789 (version=TLSv1 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for ; Fri, 19 Jan 2018 15:48: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 w0JKmUa2039479; Fri, 19 Jan 2018 15:48:30 -0500 (EST) (envelope-from mike@sentex.net) Subject: Re: Ryzen issues on FreeBSD ? To: Ryan Root , 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 Tancsa Organization: Sentex Communications Message-ID: Date: Fri, 19 Jan 2018 15:48: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: <9b769e4e-b098-b294-0bce-8bb1c42e8a59@rootautomation.com> 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: Fri, 19 Jan 2018 20:48:35 -0000 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 >>> 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 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 Fri Jan 19 20:48:46 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 206BBEC76CD for ; Fri, 19 Jan 2018 20:48:46 +0000 (UTC) (envelope-from peter@hda3.com) Received: from mail-qt0-x236.google.com (mail-qt0-x236.google.com [IPv6:2607:f8b0:400d:c0d::236]) (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 A73617472B for ; Fri, 19 Jan 2018 20:48:45 +0000 (UTC) (envelope-from peter@hda3.com) Received: by mail-qt0-x236.google.com with SMTP id s3so6985602qtb.10 for ; Fri, 19 Jan 2018 12:48:45 -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=shCRsPhBHK8+Gz47qRHB/WyC0+U/ShLb1Xla320wV14=; b=jRy9NS+IosZThr121Z2rETIGevPqR1UrXB6J3T3u0DPLmVk67F20r88cAIdmuPleEi +t7SYgZREcF15whnJqcyjv5OU9WkFEiTG5C7fXKk6vRjkvZmrhEf4BJ7WKwkhVXtEvN4 UDwvH6PRQqSv46s0/yy5kZUJUuBm/GPpsmjkPM9fAagFK+Rrn8p/Eo2oooBiMp6gT+EY tUhvGDHi9uqPwvo7hv3RpQ1o7IMpWoFR+DXO8r8i5ysrZBLvV4GXMHOove4Ltb3xS05y gXOxqfFAFOjW1+BO/3R+j8VYMPd1goUlk6sQ9husXZuj0HGbyKxcl+UFOuK/N4N3WCaU GtKg== 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=shCRsPhBHK8+Gz47qRHB/WyC0+U/ShLb1Xla320wV14=; b=I5hnQIvefMI4Z4hWSPvlj8WKj5o62qUyGTszILgUv09OVINZ350o8xYQYOAiBI/wK9 aCyM9Sk7oEzbXT9X1ijk0M0PyJD7yVFJg2VCO4q02fTKuRdIpls1YZ4mrLgNHEla0RI0 tVaceRPI5iZd3Ze0q9D4VHjFiC/ZXn685+383Km4PWUB1jDIXLSGDCU6WBKE1vOD+yPK zIw9Ui/5sqKX9jxxB7xMxmsy3kcowtNGJp03MPkT3LMpi7mfUK4wHXtGHIQ2Vd4cyxmH pvQU+AW1s01+kT1qhusQabC20lrF0PrBBIFx4TqMrnnebqXMLJ55wn1nYCOmach5BSdq RFnw== X-Gm-Message-State: AKwxyterTpnMbBlBJVVlVpV22ZLJkqgMU002GOpzxdtxNibbfxBAlIde bwMiowePZ1/S7tpbQMDGMB6+Vl1sYnqCG9SCQ45flwTjG1s= X-Google-Smtp-Source: ACJfBotFKwX4hpxyrtKOHLRg0bkMc7ADcbX58rIp2m/siXtxMvrX9W+mE73nxdS34XDRUDlwI3CceffTDBLYCsTd/Sc= X-Received: by 10.200.4.19 with SMTP id v19mr30923875qtg.69.1516394924314; Fri, 19 Jan 2018 12:48:44 -0800 (PST) MIME-Version: 1.0 Received: by 10.140.39.83 with HTTP; Fri, 19 Jan 2018 12:48:23 -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> From: Peter Moody Date: Fri, 19 Jan 2018 12:48:23 -0800 Message-ID: Subject: Re: Ryzen issues on FreeBSD ? To: Mike Tancsa Cc: Nimrod Levy , Don Lewis , freebsd-stable@freebsd.org, Pete French 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: Fri, 19 Jan 2018 20:48:46 -0000 On Fri, Jan 19, 2018 at 12:39 PM, Mike Tancsa wrote: > On 1/19/2018 3:32 PM, Peter Moody wrote: >> >> I have a ryzen5 1600X and an ASRock AB350M and I've tried just about >> everything in all of these threads; disabling C state (no effect), >> setting the sysctl (doesn't exist on my 11.1 RELEASE), tweaking >> voltage and cooling settings, rma'ing the board the cpu and the >> memory. nothing helped. >> >> last night I tried disabling SMT and, so far so good. > > > Is there anything that can be done to trigger the lockup more reliably ? > I havent found any patterns. I have had lockups with the system is 100% > idle and lockups when lightly loaded. I have yet to see any segfaults > or sig 11s while doing buildworld (make -j12 or make -j16 even) "reliably" trigger the lockup, no. The general pattern was high load followed by low load would lock up; so a couple 'make -j 32 buildworld' would almost always result in a lock up a few hours after the last one completes. weirdly enough though, with SMT enabled, building net/samba47 would always hang (like compilation segfaults). with SMT disabled, no such problems. > ---Mike > From owner-freebsd-stable@freebsd.org Fri Jan 19 21:02: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 DEC8EEC8384 for ; Fri, 19 Jan 2018 21:02:59 +0000 (UTC) (envelope-from nimrod@nimrod.is-a-geek.net) Received: from mail-yw0-x233.google.com (mail-yw0-x233.google.com [IPv6:2607:f8b0:4002:c05::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 9DB20753DC for ; Fri, 19 Jan 2018 21:02:59 +0000 (UTC) (envelope-from nimrod@nimrod.is-a-geek.net) Received: by mail-yw0-x233.google.com with SMTP id m19so1118804ywh.12 for ; Fri, 19 Jan 2018 13:02:59 -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=wdZqbHNjJvru3dWFeS2S/+Hr+cPu0SS6lt7thY/h5N8=; b=Wbo/2Kg44AzgtAh4U9no24NKboXp2TTjQLAW31eItBX5oH7gKHheFqjnOBArvsXDyt HL0uw60SNHIyLaPK5cOvL6z1Tv2H3s/UInQzMbvFpDeT7LPfDpOH5aBjuSXphClTmi0A +Ds3yF76Sm9C8BQJ/XWE8iRtQgUjVRfRfGomZG1VunJFSPfIgfHXtai6zBZC1+Qk0AWy 6McX7ESvFSy49E5RXWAwHOKB8kH449Hw0LdDvxKreYgcEt2miG2Yfi/spyC2FfU512mT f2IJ62zmlADWv3wMEXl9ssfwYcZZwkbddcbgTDKRoqkYnGMeyzGAgwbIbnXJ/LtzHeRs HcHg== 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=wdZqbHNjJvru3dWFeS2S/+Hr+cPu0SS6lt7thY/h5N8=; b=ecaMILO1hLw7dAmvAszigEhcKvNSfPofeXoMKt5xyTyWWsMKawQLwjRI8cdlpppUiI quy+s0r0MZxznX4Hp4+vFFsR+DxfHL3Fx9RSE+WSRd5U7MuchTa+QmKWyZJjVUr/S0Ts B+i4oJw/0g4ZJXYg+Rx8wB25c2Hmm6aeZBHoiKVqzqeIbcfmux5VBXl/EdJTb210hr29 Ia2+1j1vY0oo2JxVPslkwHJDXrSD+0DlDFjyeGNtHLwjC5RKEccikDEFh8kzpn+mFSWx VVUq/4c47beq9CjLJYW1HsFV/SLK8hheQJV8OsIEYgPOuMv0r3U67AV1oZZ6vX0soJO9 0WwQ== X-Gm-Message-State: AKwxytcpENh23HtaOqgeWDKKCoU8Kvk48QOYjZq7H9Zn/ceXSy49qG7l HGp8Bc6C+9XxLloxmBg357C6kcaO5eDj9/G3BxqiZA== X-Google-Smtp-Source: ACJfBovEatZq/W8QVP5TVdnvFrT5MMBgf4UCAXwpDjv/BPLzuh8ybqOfE0iLQCnTK3ICIYK6NcndOK89u+jQ16E+Vqw= X-Received: by 10.129.159.17 with SMTP id w17mr11191619ywg.23.1516395778306; Fri, 19 Jan 2018 13:02:58 -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: Fri, 19 Jan 2018 21:02:47 +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: Fri, 19 Jan 2018 21:03:00 -0000 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 From owner-freebsd-stable@freebsd.org Fri Jan 19 21:14:12 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 C6BFEEC8B05 for ; Fri, 19 Jan 2018 21:14:12 +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 91FFC75B2B for ; Fri, 19 Jan 2018 21:14:12 +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 1ecdzF-0003CG-1b for freebsd-stable@freebsd.org; Fri, 19 Jan 2018 21:14:09 +0000 Subject: Re: Ryzen issues on FreeBSD ? To: freebsd-stable@freebsd.org References: <8e842dec-ade7-37d1-6bd8-856ea1a827ca@sentex.net> <8dcf6cc8fad788ac8168a4a9f392b02e@foolishgames.com> <23c1d162-dcd8-c422-3114-d70b65b6c271@sentex.net> From: Pete French Message-ID: <00875e4d-740f-63f1-496c-6cda82b1a403@ingresso.co.uk> Date: Fri, 19 Jan 2018 21:14:25 +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: Fri, 19 Jan 2018 21:14:12 -0000 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" To be honest this thread has put me off building my machine, the pile of boxes with motherboard, case, cpu and ram is still sitting next to me desk at work! -pete. From owner-freebsd-stable@freebsd.org Fri Jan 19 21:17:48 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 BFA18EC8F52 for ; Fri, 19 Jan 2018 21:17:48 +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 654CD75FDC; Fri, 19 Jan 2018 21:17:48 +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 w0JLHl6X096205 (version=TLSv1 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Fri, 19 Jan 2018 16:17:47 -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 w0JLHiv4039556; Fri, 19 Jan 2018 16:17:44 -0500 (EST) (envelope-from mike@sentex.net) Subject: Re: Ryzen issues on FreeBSD ? To: Peter Moody Cc: Nimrod Levy , Don Lewis , freebsd-stable@freebsd.org, Pete French 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> From: Mike Tancsa Organization: Sentex Communications Message-ID: <79e5c1c0-668c-2a91-73e0-6b2cdd0eac60@sentex.net> Date: Fri, 19 Jan 2018 16:17:44 -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: Fri, 19 Jan 2018 21:17:48 -0000 On 1/19/2018 3:48 PM, Peter Moody wrote: > > weirdly enough though, with SMT enabled, building net/samba47 would > always hang (like compilation segfaults). with SMT disabled, no such > problems. wow, thats so strange! I just tried,and the same thing and see it as well. [ 442/3804] Generating lib/ldb-samba/ldif_handlers_proto.h [ 443/3804] Generating source4/lib/registry/tools/common.h runner /usr/local/bin/perl "/usr/ports/net/samba47/work/samba-4.7.4/source4/script/mkproto.pl" --srcdir=.. --builddir=. --public=/dev/null --private="default/lib/ldb-samba/ldif_handlers_proto.h" ../lib/ldb-samba/ldif_handlers.c ../lib/ldb-samba/ldb_matching_rules.c [ 444/3804] Generating source4/lib/registry/tests/proto.h runner /usr/local/bin/perl "/usr/ports/net/samba47/work/samba-4.7.4/source4/script/mkproto.pl" --srcdir=.. --builddir=. --public=/dev/null --private="default/source4/lib/registry/tools/common.h" ../source4/lib/registry/tools/common.c And it just hangs there. No segfaults, but it just hangs. A ctrl+t shows just shows load: 0.16 cmd: python2.7 65754 [usem] 589.51r 10.52u 1.63s 0% 122360k make: Working in: /usr/ports/net/samba47 ---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 Fri Jan 19 21:27:33 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 4C666EC974A for ; Fri, 19 Jan 2018 21:27:33 +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 18E96768C1 for ; Fri, 19 Jan 2018 21:27: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 w0JLRVhK097882 (version=TLSv1 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for ; Fri, 19 Jan 2018 16:27: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 w0JLRTu4039578; Fri, 19 Jan 2018 16:27:29 -0500 (EST) (envelope-from mike@sentex.net) Subject: Re: Ryzen issues on FreeBSD ? To: 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> From: Mike Tancsa Organization: Sentex Communications Message-ID: Date: Fri, 19 Jan 2018 16:27:29 -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: <00875e4d-740f-63f1-496c-6cda82b1a403@ingresso.co.uk> 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: Fri, 19 Jan 2018 21:27:33 -0000 On 1/19/2018 4:14 PM, Pete French wrote: > To be honest this thread has put me off building my machine, the pile of > boxes with motherboard, case, cpu and ram is still sitting next to me > desk at work! It is quite discouraging, isnt it :( From my POV however, I really want a "plan b" to Spectre / Meltdown that at least slows down attackers. On a few servers, I do have ways to detect after that fact intrusions (tripwire etc), but I want to mitigate this attack from happening in the first place as much as possible. Supposedly Spectre exploits on AMD are MUCH harder (or so says AMD at least) so I am hoping I can at least have this as an option. We even ordered a Tyan Epyc based board to see what its like 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 Fri Jan 19 21:28:11 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 CD606EC981B for ; Fri, 19 Jan 2018 21:28:11 +0000 (UTC) (envelope-from peter@hda3.com) Received: from mail-qt0-x236.google.com (mail-qt0-x236.google.com [IPv6:2607:f8b0:400d:c0d::236]) (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 8F348769FF for ; Fri, 19 Jan 2018 21:28:11 +0000 (UTC) (envelope-from peter@hda3.com) Received: by mail-qt0-x236.google.com with SMTP id o35so7214531qtj.13 for ; Fri, 19 Jan 2018 13:28:11 -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=YHE/Xa/qUMWLcRZY+U/LDSWQzIB79CMujC+KzMUojnU=; b=cDRsvlwsfNe3SV4R3nOQ2czS2Qn/jSrn6zBulg+ebwuoFv8+Br3M2zvl/jK+TISwcC tTRBsuFYsaAleOewzAeHOKM5dyo1hv0Wvn8K5hlxiwslA7SD91JPdVYV7ZXMYcctnEYj uw0WleeoOq5cSqvGBVDOG282trFuzWCvX8hBamRH3CQAbmoDZUKYetrdYPTYz4QfoB/+ LBgTDxTJCHfJ2jPY3i7YYZrmhx3QEeX7i8N5Rx+tpJk6NMMQBwEQxsfMavm5aKE7KbxA fJkcbv5QMuw0q1iUs5EsoiX7s+6pfwu5P758/+JU4Kv8LoJrXiTKW1rhhxKOtS2XONq5 AG7g== 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=YHE/Xa/qUMWLcRZY+U/LDSWQzIB79CMujC+KzMUojnU=; b=Cgie14bZNOmkGF/cPMX6eF59uhapiH42bhmp1NbteBdVOmGvFeorPtrWkUTMXWi5sx jp3FbjLGepCwMnBDpGEyUwFbYECGCfsqAMVHh0wB5/M6CKtRYGxbB5deZNASB5kgSP75 ozQlt5Cqry0NzuqXByMhlXhIlJlZr2dyykDP0smWaBp7SCDfOa21uqT+yTBN2TGAA+a6 ie+dZAv2h7wU0AcqI7K+kPPaBgCNicAq2MKp/vYmtFiayg0ERc0H3VOfM18Ps0D4/MLf 0H3iF3biQA5+Jxzv+0+kIhyi5zRyI3ecWz7p7eWD5i5a5eOFiddsYEp8c89zmAasoWH+ TLBg== X-Gm-Message-State: AKwxytdFngWi1H3u9mR8DXzqgiJYRLZG08D+DIFreHXp+g+6/qeckVgs 5R8aK7hVU2hdy0CZZkuOZw2+Sd8uGJ0BKQVa7eXZ8Q== X-Google-Smtp-Source: ACJfBotxnCMVxy5hbQ/ap/QO5hX3L3IhxnFty62y6/l6y3afHpaQ8i97Q764/h+UV9rLugNgIfzlPiWrg8p0kU6bmC8= X-Received: by 10.55.171.5 with SMTP id u5mr7085779qke.20.1516397290477; Fri, 19 Jan 2018 13:28:10 -0800 (PST) MIME-Version: 1.0 Received: by 10.140.39.83 with HTTP; Fri, 19 Jan 2018 13:27:50 -0800 (PST) In-Reply-To: <79e5c1c0-668c-2a91-73e0-6b2cdd0eac60@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> <79e5c1c0-668c-2a91-73e0-6b2cdd0eac60@sentex.net> From: Peter Moody Date: Fri, 19 Jan 2018 13:27:50 -0800 Message-ID: Subject: Re: Ryzen issues on FreeBSD ? To: Mike Tancsa Cc: Nimrod Levy , Don Lewis , freebsd-stable@freebsd.org, Pete French 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: Fri, 19 Jan 2018 21:28:11 -0000 On Fri, Jan 19, 2018 at 1:17 PM, Mike Tancsa wrote: > On 1/19/2018 3:48 PM, Peter Moody wrote: >> >> weirdly enough though, with SMT enabled, building net/samba47 would >> always hang (like compilation segfaults). with SMT disabled, no such >> problems. > > wow, thats so strange! I just tried,and the same thing and see it as well. > > [ 442/3804] Generating lib/ldb-samba/ldif_handlers_proto.h > [ 443/3804] Generating source4/lib/registry/tools/common.h > runner /usr/local/bin/perl > "/usr/ports/net/samba47/work/samba-4.7.4/source4/script/mkproto.pl" > --srcdir=.. --builddir=. --public=/dev/null > --private="default/lib/ldb-samba/ldif_handlers_proto.h" > ../lib/ldb-samba/ldif_handlers.c ../lib/ldb-samba/ldb_matching_rules.c > [ 444/3804] Generating source4/lib/registry/tests/proto.h > runner /usr/local/bin/perl > "/usr/ports/net/samba47/work/samba-4.7.4/source4/script/mkproto.pl" > --srcdir=.. --builddir=. --public=/dev/null > --private="default/source4/lib/registry/tools/common.h" > ../source4/lib/registry/tools/common.c > > > And it just hangs there. No segfaults, but it just hangs. yeah whoops, sorry. I had compilation segfaults on my mind b/c of the linked amd forums posts about gcc segfaults. anyway, try disabling SMT and see if that helps .. ? this seems to make parallel stuff perceptibly slower (like a make -j12 buildworld at the same time as make -j 12 in net/samba47), but at this point I'm just happy with the relative stability. > A ctrl+t shows just shows > > load: 0.16 cmd: python2.7 65754 [usem] 589.51r 10.52u 1.63s 0% 122360k > make: Working in: /usr/ports/net/samba47 > > > ---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 Fri Jan 19 22:06: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 49A75ECB371 for ; Fri, 19 Jan 2018 22:06:37 +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 01E2A7837D; Fri, 19 Jan 2018 22:06:36 +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 w0JM6ZjM004882 (version=TLSv1 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Fri, 19 Jan 2018 17:06:36 -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 w0JM6XJD039679; Fri, 19 Jan 2018 17:06:33 -0500 (EST) (envelope-from mike@sentex.net) Subject: Re: Ryzen issues on FreeBSD ? To: Peter Moody Cc: Nimrod Levy , Don Lewis , freebsd-stable@freebsd.org, Pete French 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> <79e5c1c0-668c-2a91-73e0-6b2cdd0eac60@sentex.net> From: Mike Tancsa Organization: Sentex Communications Message-ID: Date: Fri, 19 Jan 2018 17:06:33 -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: Fri, 19 Jan 2018 22:06:37 -0000 On 1/19/2018 4:27 PM, Peter Moody wrote: >> And it just hangs there. No segfaults, but it just hangs. > > yeah whoops, sorry. I had compilation segfaults on my mind b/c of the > linked amd forums posts about gcc segfaults. > > anyway, try disabling SMT and see if that helps .. ? > Strange, still hangs, different location :( [ 386/3804] HEIMDAL_GSSAPI_ASN1_PRIV_H: bin/default/source4/heimdal/lib/gssapi/gssapi_asn1-priv.hx -> bin/default/source4/heimdal/lib/gssapi/gssapi_asn1-priv.h runner cp default/source4/heimdal/lib/gssapi/gssapi_asn1-priv.hx default/source4/heimdal/lib/gssapi/gssapi_asn1-priv.h load: 19.29 cmd: make 79210 [wait] 301.89r 0.04u 0.00s 0% 1560k make: Working in: /usr/ports/net/samba47 make[1]: 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 Fri Jan 19 22:08:08 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 BA489ECB4FF for ; Fri, 19 Jan 2018 22:08:08 +0000 (UTC) (envelope-from michael+lists@burnttofu.net) Received: from burnttofu.net (burnttofu.net [IPv6:2607:fc50:1:9d00::9977]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "burnttofu.net", Issuer "burnttofu.net" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 78184784F3 for ; Fri, 19 Jan 2018 22:08:08 +0000 (UTC) (envelope-from michael+lists@burnttofu.net) Received: from elwha.brokendns.net (elwha.brokendns.net [IPv6:2607:f2f8:a544:0:0:0:0:2]) by burnttofu.net (8.15.2/8.15.2) with ESMTPS id w0JM85UO033397 (version=TLSv1.2 cipher=DHE-RSA-AES128-GCM-SHA256 bits=128 verify=NOT) for ; Fri, 19 Jan 2018 17:08:06 -0500 (EST) (envelope-from michael+lists@burnttofu.net) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=burnttofu.net; s=bt; t=1516399687; bh=GeA80YVkADXHit+y7Wkmt9YgTmcszmO9Ebci4uuWf34=; h=Subject:To:References:From:Date:In-Reply-To; b=e869kGxsgyi8WhHqiZa4qdaGuW8O/7Kwn9KuOoMGq94p9sP/WB8wGmRKRY+JjVXrZ kyO6NBW9jRgPWL5+338X5CqnZuDev+UwfruFF32H4W7ZTtW/nVaXmXtOYE7JOdmqvL obhIKeIg6hrnW5jt2KzF+QIKzEXp4vu66ur/EKxO5ToyZmgP/oysGMPw+Gr7Ce7TkU 0vkFHb52I33tL5gVFHXIByFTPQKUNt1bvmVLS2CmjGcT/8vXpSINqG6Tex1sjEmUJr hLQ+ujHnrrgw3fnpDtrOl81j2IdiKX5hm180G1Orkt8MtJp1//LFVLy2EKTB7/XDd1 tMEp9xDtQoiFA== Received: from tulare.local (unknown [IPv6:2604:5500:c2c2:f100:b0b6:cada:8a3a:1f1f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by elwha.brokendns.net (5.65c/IDA-1.4.4/5.63) with ESMTPSA id EFB0D3F74D for ; Fri, 19 Jan 2018 14:08:04 -0800 (PST) Subject: Re: Ancient FreeBSD update path To: freebsd-stable@freebsd.org References: <03c972a8f098b1b547da690efaad771f@schema31.it> <1c0b0fb4-c324-b58f-3f2a-51a1272ce26b@bsquare.com> From: Michael Sinatra Message-ID: Date: Fri, 19 Jan 2018 14:08:04 -0800 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:58.0) Gecko/20100101 Thunderbird/58.0 MIME-Version: 1.0 In-Reply-To: <1c0b0fb4-c324-b58f-3f2a-51a1272ce26b@bsquare.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-Greylist: Default is to whitelist mail, not delayed by milter-greylist-4.6.2 (burnttofu.net [IPv6:2607:fc50:1:9d00:0:0:0:9977]); Fri, 19 Jan 2018 17:08:07 -0500 (EST) 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, 19 Jan 2018 22:08:08 -0000 On 1/19/18 4:59 AM, Mike Pumford wrote: > I've just done a 9.3 to 10.3 upgrade with freebsd-update and pkg. > Networking wasn't avalable when the system was running 10.3 kernel with > 9.3 userland so I did that part of the update on the console. I have run into this problem with 9.3 -> 10.x upgrades. Basically, the old 9.3 ifconfig(8) breaks with the new 10.x kernel. Even though it's not the supported method, I have had good luck running freebsd-update on a 9.3 system, installing the kernel and then immediately (no reboot) running `freebsd-update install` again to install userland. *Then* reboot. You should be able to complete the update (removing old files and updating ports/packages) without having to go to the console. This method does not appear to be necessary for any upgrades other than 9.3 -> 10.x. michael From owner-freebsd-stable@freebsd.org Fri Jan 19 22:29:33 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 3B6AFECC3DB for ; Fri, 19 Jan 2018 22:29:33 +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 1AFF27953D for ; Fri, 19 Jan 2018 22:29:33 +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 w0JMTt7t080940 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=FAIL); Fri, 19 Jan 2018 22:29:56 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 w0JMTNqf028743 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 19 Jan 2018 14:29:24 -0800 (PST) (envelope-from truckman@FreeBSD.org) Date: Fri, 19 Jan 2018 14:29:18 -0800 (PST) From: Don Lewis Subject: Re: Ryzen issues on FreeBSD ? To: Pete French cc: freebsd-stable@freebsd.org In-Reply-To: <00875e4d-740f-63f1-496c-6cda82b1a403@ingresso.co.uk> 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> 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: Fri, 19 Jan 2018 22:29:33 -0000 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. From owner-freebsd-stable@freebsd.org Fri Jan 19 22:32: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 66DBFECC7E6 for ; Fri, 19 Jan 2018 22:32:38 +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 3773B79A47 for ; Fri, 19 Jan 2018 22:32:38 +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 w0JMX0Su080947 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=FAIL); Fri, 19 Jan 2018 22:33:01 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 w0JMTNqi028743 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 19 Jan 2018 14:32:30 -0800 (PST) (envelope-from truckman@FreeBSD.org) Date: Fri, 19 Jan 2018 14:32:29 -0800 (PST) From: Don Lewis Subject: Re: Ryzen issues on FreeBSD ? To: Mike Tancsa cc: Peter Moody , Nimrod Levy , freebsd-stable@freebsd.org, Pete French 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> 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: Fri, 19 Jan 2018 22:32:38 -0000 On 19 Jan, Mike Tancsa wrote: > On 1/19/2018 3:32 PM, Peter Moody wrote: >> >> I have a ryzen5 1600X and an ASRock AB350M and I've tried just about >> everything in all of these threads; disabling C state (no effect), >> setting the sysctl (doesn't exist on my 11.1 RELEASE), tweaking >> voltage and cooling settings, rma'ing the board the cpu and the >> memory. nothing helped. >> >> last night I tried disabling SMT and, so far so good. > > > Is there anything that can be done to trigger the lockup more reliably ? > I havent found any patterns. I have had lockups with the system is 100% > idle and lockups when lightly loaded. I have yet to see any segfaults > or sig 11s while doing buildworld (make -j12 or make -j16 even) I never seen the idle lockup problem here. Prior to the shared page fix, I could almost always trigger a system hang or silent reboot by doing a parallel build of openjdk8. From owner-freebsd-stable@freebsd.org Fri Jan 19 22:45:43 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 E05E1ECD1B1 for ; Fri, 19 Jan 2018 22:45:43 +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 B8FCC7A667 for ; Fri, 19 Jan 2018 22:45:43 +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 w0JMk6aP080989 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=FAIL); Fri, 19 Jan 2018 22:46:07 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 w0JMTNql028743 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 19 Jan 2018 14:45:35 -0800 (PST) (envelope-from truckman@FreeBSD.org) Date: Fri, 19 Jan 2018 14:45:35 -0800 (PST) From: Don Lewis Subject: Re: Ryzen issues on FreeBSD ? To: Mike Tancsa cc: Peter Moody , Nimrod Levy , freebsd-stable@freebsd.org, Pete French In-Reply-To: <79e5c1c0-668c-2a91-73e0-6b2cdd0eac60@sentex.net> 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> <79e5c1c0-668c-2a91-73e0-6b2cdd0eac60@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: Fri, 19 Jan 2018 22:45:44 -0000 On 19 Jan, Mike Tancsa wrote: > On 1/19/2018 3:48 PM, Peter Moody wrote: >> >> weirdly enough though, with SMT enabled, building net/samba47 would >> always hang (like compilation segfaults). with SMT disabled, no such >> problems. > > wow, thats so strange! I just tried,and the same thing and see it as well. > > [ 442/3804] Generating lib/ldb-samba/ldif_handlers_proto.h > [ 443/3804] Generating source4/lib/registry/tools/common.h > runner /usr/local/bin/perl > "/usr/ports/net/samba47/work/samba-4.7.4/source4/script/mkproto.pl" > --srcdir=.. --builddir=. --public=/dev/null > --private="default/lib/ldb-samba/ldif_handlers_proto.h" > ../lib/ldb-samba/ldif_handlers.c ../lib/ldb-samba/ldb_matching_rules.c > [ 444/3804] Generating source4/lib/registry/tests/proto.h > runner /usr/local/bin/perl > "/usr/ports/net/samba47/work/samba-4.7.4/source4/script/mkproto.pl" > --srcdir=.. --builddir=. --public=/dev/null > --private="default/source4/lib/registry/tools/common.h" > ../source4/lib/registry/tools/common.c > > > And it just hangs there. No segfaults, but it just hangs. > > A ctrl+t shows just shows > > load: 0.16 cmd: python2.7 65754 [usem] 589.51r 10.52u 1.63s 0% 122360k > make: Working in: /usr/ports/net/samba47 I sometimes seen build runaways when using poudriere to build my standard set of packages on my Ryzen machine. I don't think this is a Ryzen-specific issue since I also see the same on older AMD FX-8320E machine, but much less frequently there. It looks like a lost wakeup issue, but I haven't had a chance to dig into it yet. =>> Killing runaway build after 7200 seconds with no output =>> Cleaning up wrkdir ===> Cleaning for doxygen-1.8.13_1,2 =>> Warning: Leftover processes: USER PID %CPU %MEM VSZ RSS TT STAT STARTED TIME COMMAND nobody 55576 0.0 0.0 10556 1528 0 I+J 00:32 0:00.04 /usr/bin/make -C /usr/ports/devel/doxygen build nobody 55625 0.0 0.0 11660 1952 0 I+J 00:32 0:00.00 - /bin/sh -e -c (cd /wrkdirs/usr/ports/devel/dox ygen/work/.build; if ! /usr/bin/env XDG_DATA_HOME=/wrkdirs/usr/ports/devel/doxygen/work XDG_CONFIG_HOME=/wr kdirs/usr/ports/devel/doxygen/work HOME=/wrkdirs/usr/ports/devel/doxygen/work TMPDIR="/tmp" PATH=/wrkdirs/u sr/ports/devel/doxygen/work/.bin:/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/sbin:/usr/local/bin:/nonexistent/b in NO_PIE=yes MK_DEBUG_FILES=no MK_KERNEL_SYMBOLS=no SHELL=/bin/sh NO_LINT=YES PREFIX=/usr/local LOCALBASE= /usr/local LIBDIR="/usr/lib" CC="cc" CFLAGS="-O2 -pipe -DLIBICONV_PLUG -fstack-protector -fno-strict-alia sing" CPP="cpp" CPPFLAGS="-DLIBICONV_PLUG" LDFLAGS=" -fstack-protector" LIBS="" CXX="c++" CXXFLAGS="-O2 - pipe -DLIBICONV_PLUG -fstack-protector -fno-strict-aliasing -DLIBICONV_PLUG" MANPREFIX="/usr/local" BSD_IN STALL_PROGRAM="install -s -m 555" BSD_INSTALL_LIB="install -s -m 0644" BSD_INSTALL_SCRIPT="install -m 5 55" BSD_INSTALL_DATA="install -m 0644" BSD_INSTALL_MAN="install -m 444" /usr/bin/make -f Makefile all docs; then if [ -n "" ] ; then echo "===> Compilation failed unexpectedly."; (echo "") | /usr/bin/fmt 75 79 ; fi; false; fi) nobody 55636 0.0 0.0 9988 1108 0 I+J 00:32 0:00.01 `-- /usr/bin/make -f Makefile all docs nobody 6734 0.0 0.0 10140 1216 0 I+J 00:42 0:00.00 `-- /usr/bin/make -f CMakeFiles/Makefile2 docs nobody 6764 0.0 0.0 10140 1216 0 I+J 00:42 0:00.01 `-- /usr/bin/make -f CMakeFiles/Makefile2 do c/CMakeFiles/docs.dir/all nobody 7107 0.0 0.0 10512 1536 0 I+J 00:42 0:00.03 `-- /usr/bin/make -f examples/CMakeFiles/e xamples.dir/build.make examples/CMakeFiles/examples.dir/build nobody 12111 0.0 0.0 61468 27060 0 I+J 00:43 0:00.16 `-- ../bin/doxygen diagrams.cfg Killed build of devel/doxygen | doxygen-1.8.13_1,2 ended at Sat Dec 30 18:44:47 PST 2017 build time: 02:14:51 !!! build failure encountered !!! From owner-freebsd-stable@freebsd.org Fri Jan 19 23:10:00 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 0356EECE33E for ; Fri, 19 Jan 2018 23:10:00 +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 B0AB57B728 for ; Fri, 19 Jan 2018 23:09: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 w0JNAMcu081038 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=FAIL); Fri, 19 Jan 2018 23:10:23 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 w0JMTNqo028743 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 19 Jan 2018 15:09:51 -0800 (PST) (envelope-from truckman@FreeBSD.org) Date: Fri, 19 Jan 2018 15:09:51 -0800 (PST) From: Don Lewis Subject: Re: Ryzen issues on FreeBSD ? To: Mike Tancsa cc: Peter Moody , Nimrod Levy , freebsd-stable@freebsd.org, Pete French In-Reply-To: <79e5c1c0-668c-2a91-73e0-6b2cdd0eac60@sentex.net> 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> <79e5c1c0-668c-2a91-73e0-6b2cdd0eac60@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: Fri, 19 Jan 2018 23:10:00 -0000 On 19 Jan, Mike Tancsa wrote: > On 1/19/2018 3:48 PM, Peter Moody wrote: >> >> weirdly enough though, with SMT enabled, building net/samba47 would >> always hang (like compilation segfaults). with SMT disabled, no such >> problems. > > wow, thats so strange! I just tried,and the same thing and see it as well. > > [ 442/3804] Generating lib/ldb-samba/ldif_handlers_proto.h > [ 443/3804] Generating source4/lib/registry/tools/common.h > runner /usr/local/bin/perl > "/usr/ports/net/samba47/work/samba-4.7.4/source4/script/mkproto.pl" > --srcdir=.. --builddir=. --public=/dev/null > --private="default/lib/ldb-samba/ldif_handlers_proto.h" > ../lib/ldb-samba/ldif_handlers.c ../lib/ldb-samba/ldb_matching_rules.c > [ 444/3804] Generating source4/lib/registry/tests/proto.h > runner /usr/local/bin/perl > "/usr/ports/net/samba47/work/samba-4.7.4/source4/script/mkproto.pl" > --srcdir=.. --builddir=. --public=/dev/null > --private="default/source4/lib/registry/tools/common.h" > ../source4/lib/registry/tools/common.c > > > And it just hangs there. No segfaults, but it just hangs. > > A ctrl+t shows just shows > > load: 0.16 cmd: python2.7 65754 [usem] 589.51r 10.52u 1.63s 0% 122360k > make: Working in: /usr/ports/net/samba47 I just tried building samba47 here. Top shows python spending a lot of time in that state and steadily growing in size, but forward progress does happen. I got a successful build: [00:07:54] [01] [00:06:31] Finished net/samba47 | samba47-4.7.4_1: Success I'm currently running: FreeBSD 12.0-CURRENT #0 r327261M: Wed Dec 27 22:44:16 PST 2017 From owner-freebsd-stable@freebsd.org Fri Jan 19 23:16: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 17CE1ECE801; Fri, 19 Jan 2018 23:16:19 +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 EBD4E7BBE2; Fri, 19 Jan 2018 23:16:18 +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 w0JNGdU3081059 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=FAIL); Fri, 19 Jan 2018 23:16:40 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 w0JMTNqr028743 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 19 Jan 2018 15:16:09 -0800 (PST) (envelope-from truckman@FreeBSD.org) Date: Fri, 19 Jan 2018 15:16:09 -0800 (PST) From: Don Lewis Subject: Re: Ryzen issues on FreeBSD ? To: Mike Tancsa cc: Lucas Holt , owner-freebsd-stable@freebsd.org, FreeBSD-STABLE Mailing List In-Reply-To: <23c1d162-dcd8-c422-3114-d70b65b6c271@sentex.net> Message-ID: References: <8e842dec-ade7-37d1-6bd8-856ea1a827ca@sentex.net> <8dcf6cc8fad788ac8168a4a9f392b02e@foolishgames.com> <23c1d162-dcd8-c422-3114-d70b65b6c271@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: Fri, 19 Jan 2018 23:16:19 -0000 On 19 Jan, Mike Tancsa wrote: > On 1/19/2018 3:22 PM, Lucas Holt wrote: >> I have an Asus Prime X370-pro and a Ryzen 7 1700 that I bought in late > > Thanks! Thats the board I have, but no luck with amdtemp. Did you have > to change the source code for it to work ? > > dmidecode shows > > Manufacturer: ASUSTeK COMPUTER INC. > Product Name: PRIME X370-PRO > > Vendor: American Megatrends Inc. > Version: 3402 > Release Date: 12/11/2017 > Address: 0xF0000 > Runtime Size: 64 kB > ROM Size: 16 MB > Characteristics: > > memory is > > Type: DDR4 > Type Detail: Synchronous Unbuffered (Unregistered) > Speed: 2133 MT/s > Manufacturer: Unknown > Serial Number: 192BE196 > Asset Tag: Not Specified > Part Number: CT16G4DFD824A.C16FHD > Rank: 2 > Configured Clock Speed: 1067 MT/s > Minimum Voltage: 1.2 V > Maximum Voltage: 1.2 V > Configured Voltage: 1.2 V > > > > When I try and load the kld, I get nothing :( > > 0(ms-v1)# kldload amdtemp > 0(ms-v1)# dmesg | tail -2 > ums0: at uhub0, port 3, addr 1 (disconnected) > ums0: detached > 0(ms-v1)# What FreeBSD version are you running? It looks like the amdtemp changes for Ryzen are only in 12.0-CURRENT. It looks like r323185 and r323195 need to be merged to stable/11. From owner-freebsd-stable@freebsd.org Sat Jan 20 00:04:30 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 73ACCED0BDF for ; Sat, 20 Jan 2018 00:04:30 +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 54B727DB3D; Sat, 20 Jan 2018 00:04:30 +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 w0K04qYS081181 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=FAIL); Sat, 20 Jan 2018 00:04:53 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 w0JMTNr2028743 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 19 Jan 2018 16:04:21 -0800 (PST) (envelope-from truckman@FreeBSD.org) Date: Fri, 19 Jan 2018 16:04:21 -0800 (PST) From: Don Lewis Subject: Re: Ancient FreeBSD update path To: Mathieu Arnold cc: Andrea Brancatelli , freebsd-stable@freebsd.org In-Reply-To: <20180119163843.GA2251@aragorn.in.absolight.net> Message-ID: References: <03c972a8f098b1b547da690efaad771f@schema31.it> <20180119163843.GA2251@aragorn.in.absolight.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, 20 Jan 2018 00:04:30 -0000 On 19 Jan, Mathieu Arnold wrote: > On Fri, Jan 19, 2018 at 01:28:41PM +0100, Andrea Brancatelli wrote: >> 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. > > The *supported* upgrade strategy is to upgrade to the latest version of > your current branch, and jump from latest version to latest version. So > 8.4 -> 9.3 -> 10.4 -> 11.1. (Note that you can stay at 10.4, it still is > supported.) Only until October 31, 2018. At this point I'd go all the way to 11.1 to avoid going through the pain of another major OS version upgrade in the nearish future. From owner-freebsd-stable@freebsd.org Sat Jan 20 01:27:12 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 9D4C9ED486C for ; Sat, 20 Jan 2018 01:27:12 +0000 (UTC) (envelope-from bakul@bitblocks.com) Received: from mail.bitblocks.com (ns1.bitblocks.com [173.228.5.8]) by mx1.freebsd.org (Postfix) with ESMTP id 8540B80C6B for ; Sat, 20 Jan 2018 01:27:11 +0000 (UTC) (envelope-from bakul@bitblocks.com) Received: from bitblocks.com (localhost [127.0.0.1]) by mail.bitblocks.com (Postfix) with ESMTP id 05B9C156E7E7; Fri, 19 Jan 2018 17:16:54 -0800 (PST) From: Bakul Shah To: Andrea Brancatelli cc: freebsd-stable@freebsd.org Subject: Re: Ancient FreeBSD update path In-reply-to: Your message of "Fri, 19 Jan 2018 13:28:41 +0100." <03c972a8f098b1b547da690efaad771f@schema31.it> References: <03c972a8f098b1b547da690efaad771f@schema31.it> Comments: In-reply-to Andrea Brancatelli message dated "Fri, 19 Jan 2018 13:28:41 +0100." MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <70029.1516411014.1@bitblocks.com> Content-Transfer-Encoding: quoted-printable Date: Fri, 19 Jan 2018 17:16:54 -0800 Message-Id: <20180120011710.05B9C156E7E7@mail.bitblocks.com> 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, 20 Jan 2018 01:27:12 -0000 On Fri, 19 Jan 2018 13:28:41 +0100 Andrea Brancatelli 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. From owner-freebsd-stable@freebsd.org Sat Jan 20 02:21: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 DF577EB3487; Sat, 20 Jan 2018 02:21:23 +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 9313A82DBE; Sat, 20 Jan 2018 02:21:23 +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 w0K2LMsL043677 (version=TLSv1 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Fri, 19 Jan 2018 21:21:22 -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 w0K2LJQh040188; Fri, 19 Jan 2018 21:21:19 -0500 (EST) (envelope-from mike@sentex.net) Subject: Re: Ryzen issues on FreeBSD ? To: Don Lewis Cc: Lucas Holt , owner-freebsd-stable@freebsd.org, FreeBSD-STABLE Mailing List References: <8e842dec-ade7-37d1-6bd8-856ea1a827ca@sentex.net> <8dcf6cc8fad788ac8168a4a9f392b02e@foolishgames.com> <23c1d162-dcd8-c422-3114-d70b65b6c271@sentex.net> From: Mike Tancsa Organization: Sentex Communications Message-ID: <04fd4338-e606-c6eb-2c76-07c778449bca@sentex.net> Date: Fri, 19 Jan 2018 21:21:19 -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, 20 Jan 2018 02:21:24 -0000 On 1/19/2018 6:16 PM, Don Lewis wrote: >> >> 0(ms-v1)# kldload amdtemp >> 0(ms-v1)# dmesg | tail -2 >> ums0: at uhub0, port 3, addr 1 (disconnected) >> ums0: detached >> 0(ms-v1)# > > What FreeBSD version are you running? It looks like the amdtemp changes > for Ryzen are only in 12.0-CURRENT. It looks like r323185 and r323195 > need to be merged to stable/11. releng11. It seems amdsmn is needed as well ---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 Sat Jan 20 02:22: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 6A2F6EB36AA for ; Sat, 20 Jan 2018 02:22: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 35A2182FC3; Sat, 20 Jan 2018 02:22: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 w0K2MX4D043854 (version=TLSv1 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Fri, 19 Jan 2018 21:22:33 -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 w0K2MUt6040203; Fri, 19 Jan 2018 21:22:30 -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> <8dcf6cc8fad788ac8168a4a9f392b02e@foolishgames.com> <23c1d162-dcd8-c422-3114-d70b65b6c271@sentex.net> <00875e4d-740f-63f1-496c-6cda82b1a403@ingresso.co.uk> From: Mike Tancsa Organization: Sentex Communications Message-ID: <79dbd1b8-3ade-751b-693c-48141d429211@sentex.net> Date: Fri, 19 Jan 2018 21:22: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: Sat, 20 Jan 2018 02:22:34 -0000 On 1/19/2018 5:29 PM, 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. Hmmm, I wonder if I have a pair of the old CPUs (came from 2 different suppliers however). ---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 Sat Jan 20 02:20:04 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 9BBD9EB32FE for ; Sat, 20 Jan 2018 02:20:04 +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 52EF182CD6; Sat, 20 Jan 2018 02:20:04 +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 w0K2K3uq043414 (version=TLSv1 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Fri, 19 Jan 2018 21:20:03 -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 w0K2K0Oj040183; Fri, 19 Jan 2018 21:20:00 -0500 (EST) (envelope-from mike@sentex.net) Subject: Re: Ryzen issues on FreeBSD ? To: Don Lewis Cc: Peter Moody , Nimrod Levy , freebsd-stable@freebsd.org, Pete French 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> <79e5c1c0-668c-2a91-73e0-6b2cdd0eac60@sentex.net> From: Mike Tancsa Organization: Sentex Communications Message-ID: <0a968440-8538-e2e3-021c-e0c478542c87@sentex.net> Date: Fri, 19 Jan 2018 21:20:00 -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: Sat, 20 Jan 2018 02:20:04 -0000 On 1/19/2018 6:09 PM, Don Lewis wrote: > > I just tried building samba47 here. Top shows python spending a lot of > time in that state and steadily growing in size, but forward progress > does happen. I got a successful build: > [00:07:54] [01] [00:06:31] Finished net/samba47 | samba47-4.7.4_1: Success > > I'm currently running: > FreeBSD 12.0-CURRENT #0 r327261M: Wed Dec 27 22:44:16 PST 2017 RELENG11 FreeBSD ms-v1.sentex.ca 11.1-STABLE FreeBSD 11.1-STABLE #0 r328163: Fri Jan 19 09:57:36 EST 2018 Still no luck building. Its been stuck here for 20 min [ 214/3804] Compiling source4/heimdal/lib/roken/estrdup.c runner cc -pipe -g -ggdb -gdwarf-2 -gstrict-dwarf -DLIBICONV_PLUG -fno-color-diagnostics -D_FUNCTION_DEF -g -fstack-protector -DLDAP_DEPRECATED -fno-strict-aliasing -fno-omit-frame-pointer -DSOCKET_WRAPPER_DISABLE=1 -D_SAMBA_HOSTCC_ -fPIC -D_REENTRANT -D_POSIX_PTHREAD_SEMANTICS -DSTATIC_ROKEN_HOSTCC_MODULES=NULL -DSTATIC_ROKEN_HOSTCC_MODULES_PROTO=extern void __ROKEN_HOSTCC_dummy_module_proto(void) -MD -Idefault/source4/heimdal_build -I../source4/heimdal_build -Idefault/source4/heimdal/lib/roken -I../source4/heimdal/lib/roken -Idefault/include/public -I../include/public -Idefault/source4 -I../source4 -Idefault/lib -I../lib -Idefault/source4/lib -I../source4/lib -Idefault/source4/include -I../source4/include -Idefault/include -I../include -Idefault/lib/replace -I../lib/replace -Idefault -I.. -I/usr/local/include -I/usr/local/include -DLIBICONV_PLUG -D_SAMBA_BUILD_=4 -DHAVE_CONFIG_H=1 -D_GNU_SOURCE=1 -D_XOPEN_SOURCE_EXTENDED=1 ../source4/heimdal/lib/roken/estrdup.c -c -o default/source4/heimdal/lib/roken/estrdup_3.o load: 0.11 cmd: python2.7 72089 [usem] 996.84r 10.84u 0.47s 0% 99788k make: Working in: /usr/ports/net/samba47 make[1]: 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 Sat Jan 20 02:11:14 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 C143FEB2B24 for ; Sat, 20 Jan 2018 02:11:14 +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 6481682963; Sat, 20 Jan 2018 02:11:14 +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 w0K2BD0h042337 (version=TLSv1 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Fri, 19 Jan 2018 21:11:13 -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 w0K2BAdH040178; Fri, 19 Jan 2018 21:11:10 -0500 (EST) (envelope-from mike@sentex.net) Subject: Re: Ryzen issues on FreeBSD ? To: Don Lewis Cc: Peter Moody , Nimrod Levy , freebsd-stable@freebsd.org, Pete French 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> <79e5c1c0-668c-2a91-73e0-6b2cdd0eac60@sentex.net> From: Mike Tancsa Organization: Sentex Communications Message-ID: <37920df6-0b1b-b425-b5af-aa45e7f40398@sentex.net> Date: Fri, 19 Jan 2018 21:11:10 -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, 20 Jan 2018 02:11:14 -0000 On 1/19/2018 5:45 PM, Don Lewis wrote: >> >> And it just hangs there. No segfaults, but it just hangs. >> >> A ctrl+t shows just shows >> >> load: 0.16 cmd: python2.7 65754 [usem] 589.51r 10.52u 1.63s 0% 122360k >> make: Working in: /usr/ports/net/samba47 > > I sometimes seen build runaways when using poudriere to build my > standard set of packages on my Ryzen machine. I don't think this is a > Ryzen-specific issue since I also see the same on older AMD FX-8320E > machine, but much less frequently there. It looks like a lost wakeup > issue, but I haven't had a chance to dig into it yet. Odd, does this happen on Intel machines 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 Sat Jan 20 02:22: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 248A3EB36D6; Sat, 20 Jan 2018 02:22:54 +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 0388E82FE5; Sat, 20 Jan 2018 02:22:53 +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 w0K2NE7H081477 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=FAIL); Sat, 20 Jan 2018 02:23:15 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 w0K2IZcG036823 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 19 Jan 2018 18:22:43 -0800 (PST) (envelope-from truckman@FreeBSD.org) Date: Fri, 19 Jan 2018 18:22:43 -0800 (PST) From: Don Lewis Subject: Re: Ryzen issues on FreeBSD ? To: Mike Tancsa cc: Lucas Holt , owner-freebsd-stable@freebsd.org, FreeBSD-STABLE Mailing List In-Reply-To: <04fd4338-e606-c6eb-2c76-07c778449bca@sentex.net> Message-ID: References: <8e842dec-ade7-37d1-6bd8-856ea1a827ca@sentex.net> <8dcf6cc8fad788ac8168a4a9f392b02e@foolishgames.com> <23c1d162-dcd8-c422-3114-d70b65b6c271@sentex.net> <04fd4338-e606-c6eb-2c76-07c778449bca@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, 20 Jan 2018 02:22:54 -0000 On 19 Jan, Mike Tancsa wrote: > On 1/19/2018 6:16 PM, Don Lewis wrote: >>> >>> 0(ms-v1)# kldload amdtemp >>> 0(ms-v1)# dmesg | tail -2 >>> ums0: at uhub0, port 3, addr 1 (disconnected) >>> ums0: detached >>> 0(ms-v1)# >> >> What FreeBSD version are you running? It looks like the amdtemp changes >> for Ryzen are only in 12.0-CURRENT. It looks like r323185 and r323195 >> need to be merged to stable/11. > > releng11. It seems amdsmn is needed as well That sounds right. From owner-freebsd-stable@freebsd.org Sat Jan 20 02:35: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 F2743EB3FE3 for ; Sat, 20 Jan 2018 02:35: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 D168E83667 for ; Sat, 20 Jan 2018 02:35: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 w0K2a2Wj081503 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=FAIL); Sat, 20 Jan 2018 02:36:03 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 w0K2IZcJ036823 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 19 Jan 2018 18:35:31 -0800 (PST) (envelope-from truckman@FreeBSD.org) Date: Fri, 19 Jan 2018 18:35:31 -0800 (PST) From: Don Lewis Subject: Re: Ryzen issues on FreeBSD ? To: Mike Tancsa cc: Pete French , freebsd-stable@freebsd.org In-Reply-To: <79dbd1b8-3ade-751b-693c-48141d429211@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> <79dbd1b8-3ade-751b-693c-48141d429211@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, 20 Jan 2018 02:35:40 -0000 On 19 Jan, Mike Tancsa wrote: > On 1/19/2018 5:29 PM, 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. > > > Hmmm, I wonder if I have a pair of the old CPUs (came from 2 different > suppliers however). 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. From owner-freebsd-stable@freebsd.org Sat Jan 20 02:18: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 251F1EB3216 for ; Sat, 20 Jan 2018 02:18: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 E89DD82CB7 for ; Sat, 20 Jan 2018 02:18:43 +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 w0K2J6a7081460 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=FAIL); Sat, 20 Jan 2018 02:19:07 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 w0K2IZcD036823 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 19 Jan 2018 18:18:35 -0800 (PST) (envelope-from truckman@FreeBSD.org) Date: Fri, 19 Jan 2018 18:18:29 -0800 (PST) From: Don Lewis Subject: Re: Ryzen issues on FreeBSD ? To: Mike Tancsa cc: Peter Moody , Nimrod Levy , freebsd-stable@freebsd.org, Pete French In-Reply-To: <37920df6-0b1b-b425-b5af-aa45e7f40398@sentex.net> 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> <79e5c1c0-668c-2a91-73e0-6b2cdd0eac60@sentex.net> <37920df6-0b1b-b425-b5af-aa45e7f40398@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, 20 Jan 2018 02:18:44 -0000 On 19 Jan, Mike Tancsa wrote: > On 1/19/2018 5:45 PM, Don Lewis wrote: >>> >>> And it just hangs there. No segfaults, but it just hangs. >>> >>> A ctrl+t shows just shows >>> >>> load: 0.16 cmd: python2.7 65754 [usem] 589.51r 10.52u 1.63s 0% 122360k >>> make: Working in: /usr/ports/net/samba47 >> >> I sometimes seen build runaways when using poudriere to build my >> standard set of packages on my Ryzen machine. I don't think this is a >> Ryzen-specific issue since I also see the same on older AMD FX-8320E >> machine, but much less frequently there. It looks like a lost wakeup >> issue, but I haven't had a chance to dig into it yet. > > Odd, does this happen on Intel machines too ? Unknown. The last one of those I had was a Pentium III ... From owner-freebsd-stable@freebsd.org Sat Jan 20 02:46:57 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 793C8EB4B66 for ; Sat, 20 Jan 2018 02:46:57 +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 3162794; Sat, 20 Jan 2018 02:46:57 +0000 (UTC) (envelope-from mike@sentex.net) Received: from lava.sentex.ca (lava.sentex.ca [IPv6:2607:f3e0:0:5::11]) by smarthost2.sentex.ca (8.15.2/8.15.2) with ESMTPS id w0K2ktjA047428 (version=TLSv1 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Fri, 19 Jan 2018 21:46:56 -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 w0K2kqCO040242; Fri, 19 Jan 2018 21:46:53 -0500 (EST) (envelope-from mike@sentex.net) Subject: Re: Ryzen issues on FreeBSD ? To: Don Lewis Cc: Peter Moody , Nimrod Levy , freebsd-stable@freebsd.org, Pete French 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> <79e5c1c0-668c-2a91-73e0-6b2cdd0eac60@sentex.net> <37920df6-0b1b-b425-b5af-aa45e7f40398@sentex.net> From: Mike Tancsa Organization: Sentex Communications Message-ID: <9de9252e-deb2-a076-be67-839bf62b4cda@sentex.net> Date: Fri, 19 Jan 2018 21:46: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: 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, 20 Jan 2018 02:46:57 -0000 On 1/19/2018 9:18 PM, Don Lewis wrote: > On 19 Jan, Mike Tancsa wrote: >> On 1/19/2018 5:45 PM, Don Lewis wrote: >>>> >>>> And it just hangs there. No segfaults, but it just hangs. >>>> >>>> A ctrl+t shows just shows >>>> >>>> load: 0.16 cmd: python2.7 65754 [usem] 589.51r 10.52u 1.63s 0% 122360k >>>> make: Working in: /usr/ports/net/samba47 >>> >>> I sometimes seen build runaways when using poudriere to build my >>> standard set of packages on my Ryzen machine. I don't think this is a >>> Ryzen-specific issue since I also see the same on older AMD FX-8320E >>> machine, but much less frequently there. It looks like a lost wakeup >>> issue, but I haven't had a chance to dig into it yet. >> >> Odd, does this happen on Intel machines too ? > > Unknown. The last one of those I had was a Pentium III ... it builds without issue on a couple of Intel boxes I tried. The AMD one is still stuck after 30 min at the same spot :( -- ------------------- 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/