linux-kernel - Re: [PATCH] pci: Don't call resume callback for nearly bound devices

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20211110212647.GA1262229@bhelgaas>
Date:   Wed, 10 Nov 2021 15:26:47 -0600
From:   Bjorn Helgaas <helgaas@...nel.org>
To:     Robert Święcki <robert@...ecki.net>
Cc:     Uwe Kleine-König 
        <u.kleine-koenig@...gutronix.de>,
        Bjorn Helgaas <bhelgaas@...gle.com>, linux-pci@...r.kernel.org,
        "Rafael J. Wysocki" <rafael@...nel.org>, linux-pm@...r.kernel.org,
        linux-kernel@...r.kernel.org,
        Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Subject: Re: [PATCH] pci: Don't call resume callback for nearly bound devices

On Tue, Nov 09, 2021 at 01:42:29PM +0100, Robert Święcki wrote:
> Also, this might be unrelated, but the following happened around this
> patch (ie https://github.com/torvalds/linux/commit/0c5c62ddf88c34bc83b66e4ac9beb2bb0e1887d4)
> 
> 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.

Bjorn