From owner-freebsd-stable@freebsd.org Fri Feb 9 11:43:11 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B38C7F1CB51 for ; Fri, 9 Feb 2018 11:43:11 +0000 (UTC) (envelope-from nimrod@nimrod.is-a-geek.net) Received: from mail-yw0-x22f.google.com (mail-yw0-x22f.google.com [IPv6:2607:f8b0:4002:c05::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 460AB7F37C for ; Fri, 9 Feb 2018 11:43:11 +0000 (UTC) (envelope-from nimrod@nimrod.is-a-geek.net) Received: by mail-yw0-x22f.google.com with SMTP id u17so4870395ywg.9 for ; Fri, 09 Feb 2018 03:43:11 -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=jaw9piNJ+NvCSf4n3Q17QkOL7dAaqCYll58EIXwjmGA=; b=CYjftpPRSTjAYjC2OtU0w2kHt02qq9wPswoNmMAQCUhqcAXBX28c5iUM02kOIM6jjT 9dYIJc3XAAt2URr8D8PTpr2vVl1zV6Bx8mxkpq/87EjRlImbofK1llYrgEp3xhilqXHo Lyoynu4PaO+OyiJHqhEIBdj/spwrmtPvD0nMNLYeLvtPn7mEkY1jjv12HAsmaKX6ahsb +4dr79uQneNcZIiQ7JavffjaCCj60atZQbUkxosJRZ3SRDphUxHbcbYkqyINyyp1J4V8 1zqM1XK/G4PK9ZXmZCL9Kaoebd9sTbDhuumJmgnVyqeU4bATwLQNQf5ZovbDTl/x0Jxj aIbg== 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=jaw9piNJ+NvCSf4n3Q17QkOL7dAaqCYll58EIXwjmGA=; b=PcL8JQ7ZZFJqpdEpBDRhnYnS613u6NvvcmLd1QOk9EPJ3TUv+HKDMmaapHeyfLdk69 N/mM6QfucJ/jR3rwUe1BEiUpn6L2fJFNvbKivESCthDety9OIIOuPdLNreCdYDXkNaLo qTb/M3voRZ/YNRW+CkX7KjFyG7HzCi4CmmzRvz6GqxDJJcCvzxaJ2wiF0YVCyZw3uQuW 5JBjWdNT0xRCO6UOl+s3/9AD0lRsevi14orSMUhnbyrA36+Mu9ZNuH0GD16uf4GGi/4d pCa7llO+6Mw8yz2yVhAydCL9Ib64Ao1m6XejQsrcy/7FxFS1fmHdheLkdRWlkYLuOV6V cPDg== X-Gm-Message-State: APf1xPDoNKWABKB+7wM6WjUKy7XErfv+CY1OTAx31CN1Vz1ZFXlJ4VE7 kQL3nFYn6cVUq97EiMM5z5vLGVpwfJjh5BFoPgYxYA== X-Google-Smtp-Source: AH8x225m1Ju9kUd7HjhcpuZQHZnHJNzvWa0aCH2Mav6/QnrTY9PhO6LLG0eZodet+j7vp4kfp079iPv0DGeaqbMtQWc= X-Received: by 10.129.90.84 with SMTP id o81mr1655115ywb.115.1518176590085; Fri, 09 Feb 2018 03:43:10 -0800 (PST) MIME-Version: 1.0 References: <8e842dec-ade7-37d1-6bd8-856ea1a827ca@sentex.net> <730eb882-1c6a-afb7-0ada-396db44fb34b@ingresso.co.uk> <8b882970-4d5d-2a96-4dac-779cab07b9ae@sentex.net> <343acf99-3e9e-093a-7390-c142396c2985@sentex.net> <3dd9a61b-511d-db2e-80ca-cbc9a4b65f92@sentex.net> <55913e41-3a8a-9a4d-6862-e09a3d0f4d55@sentex.net> <5e48bbc2-e872-46bd-eece-25acbb180f77@sentex.net> <38a14576-2dbd-a1ba-791c-197351d091c0@sentex.net> In-Reply-To: From: Nimrod Levy Date: Fri, 09 Feb 2018 11:42:59 +0000 Message-ID: Subject: Re: Ryzen issues on FreeBSD ? (with sort of workaround) To: Peter Moody Cc: Mike Tancsa , Ed Maste , freebsd-stable stable , Don Lewis , Andriy Gapon , 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: Fri, 09 Feb 2018 11:43:11 -0000 Mine was running so well. I had almost 3 weeks of uptime before it locked up twice last night. On Thu, Feb 8, 2018 at 10:24 PM Peter Moody wrote: > to close the loop on this thread (for me at least); I replaced the > asrock ab350 with an msi x370 and things now, just work (c). the msi > detects the memory as 2133 (rather than the 3000 mhz it was sold as). > i'm not sure if this because it really is 2133 mhz, or because the msi > just likes that frequency better. i'm also not sure to what extent the > issue was fixed by the slower memory versus the different mobo brand & > chipset. > > now my only issue is crashes when I scrub my zfs pool, though I > strongly suspect a dying disk is the cause of that. > > Cheers, > peter > > > On Thu, Feb 1, 2018 at 10:51 AM, Mike Tancsa wrote: > > On 2/1/2018 1:49 PM, Mike Tancsa wrote: > >> On 2/1/2018 1:40 PM, Ed Maste wrote: > >>>> root@amdtestr12:/home/mdtancsa # procstat -kk 6067 > >>>> PID TID COMM TDNAME KSTACK > >>>> > >>>> 6067 100865 python2.7 - ??+0 ??+0 ??+0 > ??+0 > >>>> ??+0 ??+0 ??+0 ??+0 ??+0 ??+0 > >>> > >>> I think this part is due to the broken loader change in r328536. > >>> Kernel symbol loading is broken, and this in particular isn't related > >>> to Ryzen issues. > >> > >> Just for the archives, after a buildworld to a newer rev of the source > >> tree, all was good :) > > Ugh, to clarify, all was good with the procstat issue. > > > > ---Mike > > > > > > -- > > ------------------- > > Mike Tancsa, tel +1 519 651 3400 x203 <(519)%20651-3400> > > Sentex Communications, mike@sentex.net > > Providing Internet services since 1994 www.sentex.net > > Cambridge, Ontario Canada > -- -- Nimrod