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"