Received: by 2002:a6b:fb09:0:0:0:0:0 with SMTP id h9csp1892664iog; Tue, 14 Jun 2022 16:10:34 -0700 (PDT) X-Google-Smtp-Source: AGRyM1vKt5noWFP0NlX19b6kiu3KHOVAfs1/TDvjyDfOJETnlVext2Xr3utkcRzOwPS0x9ehX6k+ X-Received: by 2002:a17:90b:3510:b0:1ea:c198:fa09 with SMTP id ls16-20020a17090b351000b001eac198fa09mr6844222pjb.137.1655248233866; Tue, 14 Jun 2022 16:10:33 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1655248233; cv=none; d=google.com; s=arc-20160816; b=WPAI6l/OtKsDBejGjWy0rKvaQmvng+7YlGSkV1VNYmqxu6qumj+h35kOXeZ/y1iqHA 6K/t0NKCZ6suW8l3GWIeQJLjwZQ4OYZ9afvV7iMybAmxuZcs5MpWkk+O2R+81DdIX58L ge05Ir8Yz8t94w24YRACORTmQMlNHd6+QA8IWWBcuKLfm0FubmPoJEDek/tRqqM8xiQM 78x7bmoXuPIBlT9XFworefujiUNk6dEdBfbUY3kYXUUHRSPPPsZV3pTJJunj1iGMkgEa Kc8z5GcZhWXsbNdJdjIMe9Cp6TMx14bdP3ye2upBctFlv+KZnx653MPOZE4M6qkHNl6J flug== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:in-reply-to:content-disposition:mime-version :message-id:subject:cc:to:from:date:dkim-signature; bh=Q6dtF1K+pJ6nMjh/i5v/KubJyDg4kO4UBoQXKNwWlII=; b=hT3xQxYWzM8U+wpvExELP2OYgvechMZvAEOqiDrFqcRBHWfc5dPFlSSXK4GSWe3u7r wrdx4fM/Krxb2IJuWpMUxwTMxWudsLUCLnkduiIMDrr1I61dGKIrqWJKhK+H9G1wiztG SbehBMUu9thFIoeEM9IsoAP/JGVhukndJZ99ER1FBSSdGxXeazE+ON6djCFhldQAt3JF yenoBY1B4c2q73ClA0Dd/dX2jhLksQF00XwesxgT8a6nDOVAanTrzeAsjruTDeCoE/ER S5F4hFAGiU1WRenNBnbSb4GewEIdHGmZYjvoIYsBjKc8BtMfpFVtfrDtKe78X9cicidH s9Nw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=k20201202 header.b=eFWD1zQ5; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id b4-20020a630c04000000b00401b83a1fd0si15980850pgl.40.2022.06.14.16.10.22; Tue, 14 Jun 2022 16:10:33 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@kernel.org header.s=k20201202 header.b=eFWD1zQ5; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1357433AbiFNXBg (ORCPT + 99 others); Tue, 14 Jun 2022 19:01:36 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:56078 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231812AbiFNXBc (ORCPT ); Tue, 14 Jun 2022 19:01:32 -0400 Received: from dfw.source.kernel.org (dfw.source.kernel.org [IPv6:2604:1380:4641:c500::1]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 6060F52E6F; Tue, 14 Jun 2022 16:01:31 -0700 (PDT) Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by dfw.source.kernel.org (Postfix) with ESMTPS id EEFF66189B; Tue, 14 Jun 2022 23:01:30 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 1EEE1C3411B; Tue, 14 Jun 2022 23:01:30 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1655247690; bh=0uCD3AXwENO/Bxz69LYMMOQrPnOqlOLGdU2KJqwaCX4=; h=Date:From:To:Cc:Subject:In-Reply-To:From; b=eFWD1zQ5yiMvhfQ5Jytt3I/far5PQRv7d1h4eCpI+rsb0iF3OI4f1TnsZY3mvcuk8 NP4MpkRZgSswh3eMRZl/fAYke9hBR64YvUCtB4ttC0/xYvOE93t+//LziPpT/WbGQn e7ceGkopIGC3w5P7xIaUKdnRna8u0N5keaXaEgU3eNmS3cNKKNBf5u5WkZMeUxxo0I y5t/V0+/yjyYbOH5WuKBRfdcnfzAlMve9oyied4NAeJVcfEloxxkAYd0k3bpmmdpqE 5P4eJbtzARugGiokJYLBlLYJehe/DN4Oc8xiztb5Jk7b5ScUbdmT4iYnsVykjPZP0Z Ld+ipjnaHCoYA== Date: Tue, 14 Jun 2022 18:01:28 -0500 From: Bjorn Helgaas To: "Guilherme G. Piccoli" Cc: Hans de Goede , "Rafael J . Wysocki" , Mika Westerberg , Krzysztof =?utf-8?Q?Wilczy=C5=84ski?= , Bjorn Helgaas , Myron Stowe , Juha-Pekka Heikkila , Thomas Gleixner , Ingo Molnar , Borislav Petkov , "H . Peter Anvin" , Benoit =?iso-8859-1?Q?Gr=E9goire?= , Hui Wang , linux-acpi@vger.kernel.org, linux-pci@vger.kernel.org, x86@kernel.org, linux-kernel@vger.kernel.org, Keith Busch , Jens Axboe , Christoph Hellwig , Sagi Grimberg , linux-nvme@lists.infradead.org Subject: Re: [PATCH] x86/PCI: Revert: "Clip only host bridge windows for E820 regions" Message-ID: <20220614230128.GA901712@bhelgaas> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <6eae37ce-dd44-9c32-3f68-2b4e102dce8e@igalia.com> X-Spam-Status: No, score=-8.3 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_HI, SPF_HELO_NONE,SPF_PASS,T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org [+cc NVMe folks] On Tue, Jun 14, 2022 at 07:49:27PM -0300, Guilherme G. Piccoli wrote: > On 14/06/2022 12:47, Hans de Goede wrote: > > [...] > > > > Have you looked at the log of the failed boot in the Steam Deck kernel > > bugzilla? Everything there seems to work just fine and then the system > > just hangs. I think that maybe it cannot find its root disk, so maybe > > an NVME issue ? > > *Exactly* that - NVMe device is the root disk, it cannot boot since the > device doesn't work, hence no rootfs =) Beginning of thread: https://lore.kernel.org/r/20220612144325.85366-1-hdegoede@redhat.com Steam Deck broke because we erroneously trimmed out the PCI host bridge window where BIOS had placed most devices, successfully reassigned all the PCI bridge windows and BARs, but some devices, apparently including NVMe, didn't work at the new addresses. Do you NVMe folks know of gotchas in this area? I want to know because we'd like to be able to move devices around someday to make room for hot-added devices. This reassignment happened before drivers claimed the devices, so from a PCI point of view, I don't know why the NVMe device wouldn't work at the new address. Bjorn