From owner-freebsd-hackers@freebsd.org Mon Aug 27 12:37:00 2018 Return-Path: Delivered-To: freebsd-hackers@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 6212910883A3 for ; Mon, 27 Aug 2018 12:37:00 +0000 (UTC) (envelope-from mitchell@wyatt672earp.force9.co.uk) Received: from avasout06.plus.net (avasout06.plus.net [212.159.14.18]) (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 CEC678E152 for ; Mon, 27 Aug 2018 12:36:59 +0000 (UTC) (envelope-from mitchell@wyatt672earp.force9.co.uk) Received: from [192.168.1.64] ([146.90.233.111]) by smtp with ESMTPA id uGdxfTGNYWLW2uGdyfacK7; Mon, 27 Aug 2018 13:29:19 +0100 X-CM-Score: 0.00 X-CNFS-Analysis: v=2.3 cv=fJUXI6Se c=1 sm=1 tr=0 a=DmGL1Jmrymuc02ZlcP2exw==:117 a=DmGL1Jmrymuc02ZlcP2exw==:17 a=IkcTkHD0fZMA:10 a=pGLkceISAAAA:8 a=waDbaBDWxNZZftWFd3gA:9 a=QEXdDO2ut3YA:10 X-AUTH: wyatt672earp@:2501 Subject: Ryzen Build Problem To: freebsd-hackers@freebsd.org, freebsd-stable@freebsd.org References: From: Mitchell Message-ID: <32e008cf-93d3-944d-9b11-e56f1bb425ef@wyatt672earp.force9.co.uk> Date: Mon, 27 Aug 2018 13:28:07 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.8.0 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-CMAE-Envelope: MS4wfPKOm9vFqyk4eCNNBpC8gkfvEmgRsRb0+kkEFGKHRv8QciQLb223GOzgbXXmDu7Pq2GgeiC/qXDCq/6DdenNIjUHqCARgPkuNSRiJXTG/4iCxroZPA2+ s8U5r1QatzsLoo/Ml4C4oVI5x1/sDXba7/KVxIGEhr6sF4rVfQ12S2e/r79sgaCxVo0deGk80ST9ig== X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Aug 2018 12:37:00 -0000 Hi Meowthink: I'm planning a Home Build, and I came across an issue which might apply to your design. Some AMD CPUs are designed for Over-Clocking automatically. But when I investigated Memory Compatibility I saw that some Memory wasn't. The "AMD Ryzen 5 2400G" looks like it can Over-Clock itself when it feels safe to do so. But the "Crucial 16GB DDR4-2400 EUDIMM CL17" seems to be classified as Server Memory, which could mean it's designed for a single speed. I couldn't find more details about Crucial Memory Over-Clocking. The Crucial Web Pages do feature a Help Facility which might enable you to check further if you input all your system details. I'm no expert here. This will be my first Home Build attempt and I haven't even started yet. You probably need a 2nd and 3rd opinion on this topic. I'm just hoping my contribution will prompt further comments from FreeBSD people with more know-how than I've got. Yours truly: Frank Mitchell On 27/08/18 09:13, Phil Norman wrote: > Hi. > > I have a similar setup: Ryzen 3 and Fatal1ty X370 mini-ITX. I had some > trouble with instability, although my problems weren't panics, but rather > two issues. One was random lockups (with no evidence left in logs), but I > *think* this was down to an inadequately cooled graphics card. > > The other problem I had was with USB. I got quite a spam of log messages > about the USB reinitialisation. However, eventually I figured out that the > problem didn't occur if I booted the system from a completely powered-down > state. That is, use the physical switch on the PSU to cut power entirely, > re-enable, then boot from that state. Since then I've had 67 days of > uninterrupted uptime, with no USB issues at all. > > It sounds like your problem is different, but trying a boot-from-cold might > be worthwhile, just in case ASRock have a consistent problem in this regard. > > Cheers, > Phil > > On 26 August 2018 at 13:20, Meowthink wrote: > >> Hello all, >> >> Recently I tried to build up a Ryzen system and run FreeBSD on it. >> CPU: AMD Ryzen 5 2400G with Radeon Vega Graphics (0x810f10) >> Mobo: Asrock Fatal1ty AB350 Gaming-ITX/ac ( with up-to-date BIOS with >> PinnaclePI-AM4_1.0.0.4, microcode 0x810100b ) >> Mem: 2x Crucial 16GB DDR4-2400 EUDIMM CL17 ( ECC Unregistered but ECC >> actually won't work :( ) >> >> But the system is unstable - it can't last few days even is nearly >> idle. System panics even at midnight. It almost panic while or after I >> built something large. Surprisly I didn't encourage a user program >> fault, bad binaries built etc., panics only. >> >> Then I tried lots of BIOS settings e.g. SMT, C6 idle current, >> underclock RAM, but none seems effect. >> It could pass memtest86 V7.5 without error, or various benchmarks >> under Windows. thus I think the problem is not in the hardware but >> software. >> >> In the mean time, I realized that the rate of irqs from xhci0 are too >> high - it's about 1998/s. I found [1] and tried to MFC r331665. It >> didn't fix the problem though, but disabling that bluetooth module >> stops the irq storm, after all. >> >> Then the system lasts much longer before panic. It eventually can >> compile ports tree, build the world, scrub the zpool, all done without >> annoying reboots. >> Then I assume this is [2] related? So I also tried cpuctl, bounding >> all processes to 2-7. >> But the problem is still there, only the chance become very low. It >> still panics occasionally, idling a week or stressing few hours - >> Stress seems to rise the chance of panic, but differently by types. >> Things like llvm will always build, but gcc will cause a panic per few >> passes. >> >> The system was 11.2 but then moved on to stable/11 (r337906 >> currently). I've got last 10 coredumps saved but my kernel isn't >> compile as debug. So I'll put some backtrace from core.txt.? in the >> end. >> >> Indeed I want to eliminate this problem. Could someone guide me how to >> figure out the problem? What should I try next? >> >> Best regards, >> Meowthink >>