From owner-freebsd-stable@freebsd.org Wed Aug 29 08:11:36 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 82FBD1080DE7; Wed, 29 Aug 2018 08:11:36 +0000 (UTC) (envelope-from karu.pruun@gmail.com) Received: from mail-oi0-x22e.google.com (mail-oi0-x22e.google.com [IPv6:2607:f8b0:4003:c06::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 1F7E681B27; Wed, 29 Aug 2018 08:11:36 +0000 (UTC) (envelope-from karu.pruun@gmail.com) Received: by mail-oi0-x22e.google.com with SMTP id k12-v6so7622763oiw.8; Wed, 29 Aug 2018 01:11:36 -0700 (PDT) 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=5nbQfoZPfL3RocRjqN2W0Hs9Tah2+3TNWtWblMla8QY=; b=MWioYp1b57fCfy4WVAUj9HgxG9Aptmah23PJ2EdZf8FO/npv+/s5KHtXQAj8PkVwvv 40iK/NiPYL16jpN47YsNgYQ19i4+Nv9VbGK9C8YSKrxVEo4NmZFFtcTWSNjG0v3naA7p KaadQnJMNV02pg8W7VY+c0G2xIDsbA0t5qW3b5C9K8PLjm+RGuO8nY6vxsZ28WwJfg/O yJVIUiIP0LFhX21d9vZ76sWlvWuRLiLYrqtAT81miX6M1DCXdIjJrJ1ZiRLqSLDYyIH8 Wq+EfCuxFcsDeoCHOpqx0eqpZrLEkMXEoL1Nbo/npGrMW0zttsngJqwcqt9dtGtpa0gL F+GQ== 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=5nbQfoZPfL3RocRjqN2W0Hs9Tah2+3TNWtWblMla8QY=; b=AzJUOYbje3LhRv2ixB96xzUQLApbL2VjtgJfRuMwuavsBt4bqUkhAk/TQVnIG3YUAS jdpmH9oLPDKkPxmjHPBBhoFNQCRnt3hd9rVUqeCMaes3cgtZvGBEDf4bePjXmt+nWmru 9nOmLvjCZHpo/YOoC2TPqUjUmyXlY3HoyM7rU5jTN6EX4srQmLl3rEefFCbFZmO0CsDx mn9fqGuLHAxp3Zzqey+xOv0T+gQlz3rfmq8KJfL55DrDF/ComJ12ZklVdvVIz1VfH/XI aqw5AXOaL7UKneH7MKuh8ov9HXWnBClxEaUdVenYbVtd5oEzWgat3xEytHt4I8kI1v0t 4wBg== X-Gm-Message-State: APzg51BMckyEQexHtEhHPsCYM671ZJCstQLfZ2bKzrTWGe8G3H29n6hz 1zH3e17DHC8QtV5wHN0c/JAP8APcb2K7MOHCjCM= X-Google-Smtp-Source: ANB0VdaZPdnDT3zX8vf24tG1jU7z+epH8FJ4JNjAqcGQJAJ5/ht/EwHShVzrssFnoUminYpdmp5aucsXb93/oEK5XKI= X-Received: by 2002:aca:b1c1:: with SMTP id a184-v6mr1549838oif.182.1535530295134; Wed, 29 Aug 2018 01:11:35 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: "karu.pruun" Date: Wed, 29 Aug 2018 11:11:24 +0300 Message-ID: Subject: Re: Help diagnose my Ryzen build problem (in progress) To: Si Miao Cc: freebsd-hackers@freebsd.org, freebsd-stable@freebsd.org Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.27 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, 29 Aug 2018 08:11:36 -0000 On Wed, Aug 29, 2018 at 5:28 AM Meowthink wrote: > > Update: > > machdep.idle = hlt and machdep.idle_mwait = 0 failed also. It can't > last even longer than machdep.idle = mwait, which could normally panic > after a few passes of building gcc. I tried hlt twice, both not longer > than half hour. > > Now, as another round of building 4 gccs in parallel is going to finish, with > machdep.idle = spin and machdep.idle_mwait = 0. > Can I say Ryzen 2400G probably have issues with both mwait and hlt? I suppose we can conclude that HLT is a culprit as it causes issues both on FreeBSD and DragonFly. On DragonFly it occurs in an isolated case where I had to run java. Otherwise the desktop would last for 3 - 4 weeks with no problems (and I only had to reboot since I built a new kernel). Also, when I finished running java, I switched on HLT again to get better power saving. But that said, yes, Ryzen 2400G has an issue with HLT in general. This has not been mentioned in the Revision guide for family 17h, and the latter does not explicitly include 2400G, which is model 11h as you said. https://support.amd.com/TechDocs/55449_Fam_17h_M_00h-0Fh_Rev_Guide.pdf Regarding MWAIT, the DragonFly bug report says that the microcode update 0x0810100B fixes this. But I can't comment since I did not touch that at all. Cheers Peeter --