Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 14B4DC433FE for ; Wed, 10 Nov 2021 22:01:52 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id E8D4561207 for ; Wed, 10 Nov 2021 22:01:51 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S233560AbhKJWEj (ORCPT ); Wed, 10 Nov 2021 17:04:39 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:60582 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S233552AbhKJWEh (ORCPT ); Wed, 10 Nov 2021 17:04:37 -0500 Received: from mail-ot1-x32d.google.com (mail-ot1-x32d.google.com [IPv6:2607:f8b0:4864:20::32d]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id ABFB1C061767 for ; Wed, 10 Nov 2021 14:01:49 -0800 (PST) Received: by mail-ot1-x32d.google.com with SMTP id g91-20020a9d12e4000000b0055ae68cfc3dso6016607otg.9 for ; Wed, 10 Nov 2021 14:01:49 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=swiecki.net; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=YUdZCO/hNfprbwtfZTPl8gI7fzwGN/mef1SZePWhdGQ=; b=CMeKc3cCRv5cPku84sXDxWyZtOKUSgVHaF691D2GsGw/rfrBZEWmN/+P4oYKri5W0Q Hom1d8v/i/X19PS31UoM6OrEr69rT8g6+QAsH/6kw/fcG2SV9e9X9V2p15W29ImmMHrF jwG+4wdK+6D1+HSKQCvoSOC5BG+2J1E+RSTnw= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=YUdZCO/hNfprbwtfZTPl8gI7fzwGN/mef1SZePWhdGQ=; b=HXUIrudZuAxrgQ5hXFn0imgxfsdAFtZ4dRBeqQYfx+CfcR3IFYFz/t2196kjQbpIvB 1apGKTJvpFnv6P4evEvvqcU6frl/ruQ0GPPjhJRN2SaJAWkIGJVHt+2sFYDkPo6J/H2l UNRmjHlUHoAZhMV5ZIATrCKhSOsADbZBZJJ7uC09Lb6x+yhlhMNijwsFm8HBFjw7YWQ5 l5t7K3YpZ2ZdYWN2ofHZ3Fue6cCAMuS16OGyw/mgP6a1nbcIdYHlFx4NKAo2zpVs0d2B BMc0C2xZwsATkKiblZvxR8eFWnowS5vDtvFfu1i2OEJmLOdmvhKFT36IymuT3UtX/fK4 eA6Q== X-Gm-Message-State: AOAM5322z9SpUyldZupAremKXjgePh4zVBceI643LYQt+NWVtS39VePw MMMfTBUUPtLZOHqbwcGXSwbjuAUmv1xexm/1Jfp9rg== X-Google-Smtp-Source: ABdhPJy/gqROCJ6wB4jz2whMB+ZkC2aUf8dXdseelcRFvHN7Y21FZ1S2dhIxLup+gHQ3lwU3mjjJfBH6MbJl12Wy1Ks= X-Received: by 2002:a05:6830:1690:: with SMTP id k16mr2073994otr.148.1636581708952; Wed, 10 Nov 2021 14:01:48 -0800 (PST) MIME-Version: 1.0 References: <20211110212647.GA1262229@bhelgaas> In-Reply-To: <20211110212647.GA1262229@bhelgaas> From: =?UTF-8?B?Um9iZXJ0IMWad2nEmWNraQ==?= Date: Wed, 10 Nov 2021 23:01:38 +0100 Message-ID: Subject: Re: [PATCH] pci: Don't call resume callback for nearly bound devices To: Bjorn Helgaas Cc: =?UTF-8?Q?Uwe_Kleine=2DK=C3=B6nig?= , Bjorn Helgaas , linux-pci@vger.kernel.org, "Rafael J. Wysocki" , linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org, Greg Kroah-Hartman Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi, =C5=9Br., 10 lis 2021 o 22:26 Bjorn Helgaas napisa=C5= =82(a): > > On Tue, Nov 09, 2021 at 01:42:29PM +0100, Robert =C5=9Awi=C4=99cki wrote: > > Also, this might be unrelated, but the following happened around this > > patch (ie https://github.com/torvalds/linux/commit/0c5c62ddf88c34bc83b6= 6e4ac9beb2bb0e1887d4) > > > > I sometimes run Win11 under qemu/kvm/vfio (gfx card), and it stopped > > booting (even with the latest patch for pci). Another Linux distro > > boots fine under the same qemu/kvm/vfio, but Win11 stops at the boot > > screen. > > > > It worked well with 5.15.0 and a few PRs later - with the git tip it's > > not booting - and it works well with 5.15.0-rc7 > > > > Maybe related to pci/vfio changes, maybe not, just leaving it here for > > track record. I'll try to debug it a bit. > > Hmm. I have no idea how to debug a Win11 boot issue. Unless there > are clues in the dmesg log or some qemu or kvm logs (if you find any > such logs, please put the complete logs somewhere), the only thing I > can think to do would be bisecting it. "git bisect" between v5.15 and > 0c5c62ddf88c looks like about 13 steps. I think I wouldn't worry about it just yet. It's a problem with many possible culprits (kvm, qemu, vfio, Win11 itself). Once the pci code is stable, I'll take another look and do some, at least basic, debugging. Though the problem is somewhat intermittent (mostly the system doesn't boot, but sometimes it does).