Received: by 2002:a05:6a10:9848:0:0:0:0 with SMTP id x8csp1272715pxf; Fri, 12 Mar 2021 06:14:00 -0800 (PST) X-Google-Smtp-Source: ABdhPJx2eMeWdF11rluUJUuJgOXSIBBXdc8bMS71j67Iwzmo0qFceClT2rvXvLxixfIaqhQNt1JH X-Received: by 2002:aa7:cb90:: with SMTP id r16mr14630178edt.139.1615558440110; Fri, 12 Mar 2021 06:14:00 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1615558440; cv=none; d=google.com; s=arc-20160816; b=02Gs81kcvk4/v0vvAL7qcoRzZzbg8NxybyuliuivlDzHAxCicOuIcZKskUo/ADOQVR CUahKFsDSGBwHPjugEbJVuKEnSmt716l3UYD9UGvYP6pk214QdpcCw1rAODJ5PYbPqfr RyKZD4Rphdc5Cd+fdNeN56PAmnViSWVCI/FKrt1iw+mNnJhtjh9SXhCnOq2V0vm1rjtr 2Ju8rsXWoPqefum/9pMb7x4bCemvlZSSRrcnVkYujeZb9L8rLJ4EasIHJNB93oJtgsSG +F1HX1tdW6piJtbphwVymEdFwzcwtSNGObU2xszC1gQ/N2F8qIrtkZldB7BX0gxINDDV wV0Q== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:content-language :in-reply-to:mime-version:user-agent:date:message-id:subject :organization:from:references:cc:to:dkim-signature; bh=o1r6EhPV88gm94Egq81KekYoIA71BcwdVAvPViuRiMU=; b=yqtCy9az1VNILyF65yYM7fTEVG+70VrilbY6U1jD6CX1HLzsEGi6gSb/YVNd5g1pAz 4ljpcBiMRdTNfyRQRmsiArKNP7krb0wI0EqUGoIWBUK5qZyX/C+VsnTBg7OlEqQlkJVr O0ntmOLFhEi3bV2Ng1nvYblZvpfz4yq4A4CTd57JvV9T7tluX0p+ZQO4ymhoiGbirMZK EQv2enyJN2WdRI5smgPW+Lqvi4c+f4IHJSWQ7bWUv4sX2vxWVBW4r4B4gP3a0/upDmxi osOCZiVicKvJge80MyFQDDUzCF7c7fl7KGZzqN6IR8KOZgiO5idfFJA5DQ3SCvU0AMNz eWTA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=ZQL57iR+; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id g25si4032025ejf.697.2021.03.12.06.13.31; Fri, 12 Mar 2021 06:14:00 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=ZQL57iR+; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231512AbhCLOM1 (ORCPT + 99 others); Fri, 12 Mar 2021 09:12:27 -0500 Received: from us-smtp-delivery-124.mimecast.com ([63.128.21.124]:50756 "EHLO us-smtp-delivery-124.mimecast.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229728AbhCLOML (ORCPT ); Fri, 12 Mar 2021 09:12:11 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1615558329; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=o1r6EhPV88gm94Egq81KekYoIA71BcwdVAvPViuRiMU=; b=ZQL57iR+mM3w2qJyC7VZQhGgqzJVrfBsp9X1UIzH0KYyOhWi713UtNT0Yd5P05nUwqGyWK 35oTBHf/+PrQ3tfqcTK2hZ6WsI1hh08Yttz9HLApa6VwYbPXqfw1HW+66kHTKIGQSdtDkb BKo1vaibvATz/njuaXFLvHcrL0l87c8= Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-450-P1mZUFPQPqeTRjKDISWN9g-1; Fri, 12 Mar 2021 09:12:07 -0500 X-MC-Unique: P1mZUFPQPqeTRjKDISWN9g-1 Received: from smtp.corp.redhat.com (int-mx04.intmail.prod.int.phx2.redhat.com [10.5.11.14]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id ACEC318460E0; Fri, 12 Mar 2021 14:12:05 +0000 (UTC) Received: from [10.36.114.197] (ovpn-114-197.ams2.redhat.com [10.36.114.197]) by smtp.corp.redhat.com (Postfix) with ESMTP id C0C5E5DEAD; Fri, 12 Mar 2021 14:12:03 +0000 (UTC) To: "Deucher, Alexander" , "linux-kernel@vger.kernel.org" , amd-gfx list , Andrew Morton Cc: "Huang, Ray" , "Koenig, Christian" , "Liang, Liang (Leo)" , Mike Rapoport , "Rafael J. Wysocki" , George Kennedy References: <2f7c20ea-888f-65b6-6607-c86aab65acce@redhat.com> From: David Hildenbrand Organization: Red Hat GmbH Subject: Re: slow boot with 7fef431be9c9 ("mm/page_alloc: place pages to tail in __free_pages_core()") Message-ID: <15faeb97-d031-f70a-adab-f2966e0b1221@redhat.com> Date: Fri, 12 Mar 2021 15:12:03 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.8.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=iso-2022-jp; format=flowed; delsp=yes Content-Language: en-US Content-Transfer-Encoding: 8bit X-Scanned-By: MIMEDefang 2.79 on 10.5.11.14 Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 12.03.21 15:06, Deucher, Alexander wrote: > [AMD Public Use] > >> -----Original Message----- >> From: David Hildenbrand >> Sent: Thursday, March 11, 2021 10:03 AM >> To: Deucher, Alexander ; linux- >> kernel@vger.kernel.org; amd-gfx list ; >> Andrew Morton >> Cc: Huang, Ray ; Koenig, Christian >> ; Liang, Liang (Leo) ; >> Mike Rapoport ; Rafael J. Wysocki >> ; George Kennedy >> Subject: Re: slow boot with 7fef431be9c9 ("mm/page_alloc: place pages to >> tail in __free_pages_core()") >> >> On 11.03.21 15:41, Deucher, Alexander wrote: >>> [AMD Public Use] >>> >>> Booting kernels on certain AMD platforms takes 2-3 minutes with the patch >> in the subject. Reverting it restores quick boot times (few seconds). Any >> ideas? >>> >> >> Hi, >> >> We just discovered latent BUGs in ACPI code whereby ACPI tables are >> exposed to the page allocator as ordinary, free system RAM. With the >> patch you mention, the order in which pages get allocated from the page >> allocator are changed - which makes the BUG trigger more easily. >> >> I could imagine that someone allocates and uses that memory on your >> platform, and I could imagine that such accesses are very slow. >> >> I cannot tell if that is the root cause, but at least it would make sense. >> >> See >> https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Flore. >> kernel.org%2Fpatchwork%2Fpatch%2F1389314%2F&data=04%7C01%7C >> alexander.deucher%40amd.com%7Cd1533aaddccd464c59f308d8e49ec563%7 >> C3dd8961fe4884e608e11a82d994e183d%7C0%7C0%7C637510717893096801% >> 7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLC >> JBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=xpty77D54Z5S%2FKK >> JO5SsVQaNsHoojWMR73whpu8VT%2B4%3D&reserved=0 >> >> You might want to give that patch a try (not sure if it's the latest >> version). CCing George > > Thanks for the patch. Unfortunately it didn't help. Any other ideas? Is there a newer version of that patch? > @George? It's interesting that this only applies to these special AMD systems so far. Is there anything particular about these systems? How much memory do these systems have? Increasing the boot time from a few seconds to 2-3 minutes does not smell like some corner case cache effects we might be hitting in this particular instance - there have been minor reports that it either slightly increased or slightly decreases initial system performance, but that was about it. Either, yet another latent BUG (but why? why should memory access suddenly be that slow? I could only guess that we are now making sooner use of very slow memory), or there is really something else weird going on. Cheers! > Alex -- Thanks, David / dhildenb