From owner-freebsd-stable@freebsd.org Fri Feb 9 03:24:13 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1B0ADF1F283 for ; Fri, 9 Feb 2018 03:24:13 +0000 (UTC) (envelope-from peter@hda3.com) Received: from mail-qt0-x230.google.com (mail-qt0-x230.google.com [IPv6:2607:f8b0:400d:c0d::230]) (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 A48A86E481 for ; Fri, 9 Feb 2018 03:24:12 +0000 (UTC) (envelope-from peter@hda3.com) Received: by mail-qt0-x230.google.com with SMTP id f4so8959727qtj.6 for ; Thu, 08 Feb 2018 19:24:12 -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=k+WLsgEvz2/sF4qIRE6iv5l9QWraikfdAjkgbrCpUTQ=; b=r5Z+Qwvf4oSUsUqFPaxikZJ1vlFDRmSXkig2qJxwky858EK4bmN8DxJU3pY7o3TE1t Z5v9S/5q9QOvTL/P32RyJhXgHNIfhCYJP45S/Ia7qnoHlz3J2sPVT5lYFUbsgrakT6km PsAoxNK/tN/f4Jwy4Y1EfiC+Wmxt7gDG8AEh/v0KN+Zg7f23E233aP1tbGlhse77blOj BaDDqL+ukl+UJG6jVwVhYPh4G3eJeNvAzaCkkULZLU41wHIa3YO/YJwDRvWG/w6cjwaI 3Ym5b1e/xzDieQH9FC3U6f9RE4GcXUYv2Y56E33lgj5dRlZpyOwZiUI6Vl4VdvjJQNFk t1qg== 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=k+WLsgEvz2/sF4qIRE6iv5l9QWraikfdAjkgbrCpUTQ=; b=ifHw1IdbaGKEQKgSTF+CuxqRrDFtUMaFobxzGIBlF5CrqE+AsCi9N8h716I1DwBI6q p1eB9EGHjMKxQYG8dHERflghoCBL6qaQWI7oCJjzlWRdEW6zGDlIDVmc/Vp/0JX5ALTt iiPZIes0EiS16tCnayiLwI5QjiqAydVTyojBYIqAT1qrRuYOFpklU7k3zjGQDEqUdDZ0 s/CIcpn1WmsNIR9rOyFaDApYRMZeG8GatVfYRy7K1kPcmEnC7mdeDAt2uPCEkpXOcvL5 jyuKO19aoTOuVbgV2wJ5X/HgLOE/7JU2rJydHmjLjYKxreA5Go1MjAbFIQa91N+wgpTU Iqbg== X-Gm-Message-State: APf1xPCE8XdSNYmGAjos3yzEQ3wGHCV7+rsEtBHYiWS85BARYnJkyR+j zRADZui2KisjW6EXoel0UsqyEitMVLOIRx2jgrbD8Q== X-Google-Smtp-Source: AH8x224sWA1J2UO4v2CJ4qWHUVomLTpcT8HQdO8p0AVTlljTAn0wUBErbCRlCIZzQde2d5qLz3Okts5W8CY272xAUc0= X-Received: by 10.200.82.4 with SMTP id r4mr2329039qtn.75.1518146652178; Thu, 08 Feb 2018 19:24:12 -0800 (PST) MIME-Version: 1.0 Received: by 10.140.39.83 with HTTP; Thu, 8 Feb 2018 19:23:51 -0800 (PST) In-Reply-To: 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> From: Peter Moody Date: Thu, 8 Feb 2018 19:23:51 -0800 Message-ID: Subject: Re: Ryzen issues on FreeBSD ? (with sort of workaround) To: Mike Tancsa Cc: Ed Maste , freebsd-stable stable , Nimrod Levy , Don Lewis , Andriy Gapon , 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, 09 Feb 2018 03:24:13 -0000 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 > Sentex Communications, mike@sentex.net > Providing Internet services since 1994 www.sentex.net > Cambridge, Ontario Canada