Re: bochs_hw_init fails to request framebuffer on EFI boot with plymouth visible - Marek Marczykowski-Górecki

From: "Marek Marczykowski-Górecki" <marmarek@invisiblethingslab.com>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: virtualization@lists.linux-foundation.org
Subject: Re: bochs_hw_init fails to request framebuffer on EFI boot with plymouth visible
Date: Wed, 15 Jan 2020 01:33:56 +0100	[thread overview]
Message-ID: <20200115003356.GL2507@mail-itl> (raw)
In-Reply-To: <20200113071939.rtqb7yw45zi63fqy@sirius.home.kraxel.org>

[-- Attachment #1.1: Type: text/plain, Size: 2146 bytes --]

On Mon, Jan 13, 2020 at 08:19:39AM +0100, Gerd Hoffmann wrote:
> On Fri, Jan 10, 2020 at 05:32:11PM +0100, Marek Marczykowski-Górecki wrote:
> > Hi,
> > 
> > This is the context of "bochs_drm: failed bochs_hw_init() results in
> > panic". When I boot the system, if plymouth is visible, it crashes. But
> > if I press ESC to hide it, it boots fine. bochs_drm is build as module
> > and _not_ included in the initramfs, so it is loaded only after root
> > filesystem is mounted. And before that, efifb works just fine, including
> > nice graphical disk passphrase prompt.
> 
> > [   32.951345] fb0: switching to bochsdrmfb from EFI VGA
> [ ... ]
> > [   33.030158] bochs-drm 0000:00:02.0: BAR 0: can't reserve [mem 0xc0000000-0xc0ffffff pref]
> 
> Looks like efifb continues to claim the framebuffer resource
> (0xc0000000-0xc0ffffff) for some reason, so bochs-drm can't
> reserve it.
> 
> No clue why, also doesn't reproduce here (standard fedora 31 5.4.7
> kernel).  I don't have an encrypted disk, so no passphrase prompt,
> maybe that makes a difference.

Extra data point: it worked on 4.19.89.

> How does /proc/iomem look after boot, specifically the 0000:00:02.0 pci
> bars?

grep 0000:00:02.0 /proc/iomem
  c0000000-c0ffffff : 0000:00:02.0
  c1087000-c1087fff : 0000:00:02.0

lspci -vvs 0000:00:02.0
00:02.0 VGA compatible controller: Device 1234:1111 (rev 02) (prog-if 00 [VGA controller])
        Subsystem: Red Hat, Inc. Device 1100
        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
        Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
        Latency: 0
        Region 0: Memory at c0000000 (32-bit, prefetchable) [size=16M]
        Region 2: Memory at c1087000 (32-bit, non-prefetchable) [size=4K]
        Expansion ROM at 000c0000 [disabled] [size=128K]
        Kernel modules: bochs_drm

-- 
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

[-- Attachment #2: Type: text/plain, Size: 183 bytes --]

_______________________________________________
Virtualization mailing list
Virtualization@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/virtualization