All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gerd Hoffmann <kraxel@redhat.com>
To: "Marek Marczykowski-Górecki" <marmarek@invisiblethingslab.com>
Cc: virtualization@lists.linux-foundation.org
Subject: Re: bochs_hw_init fails to request framebuffer on EFI boot with plymouth visible
Date: Mon, 13 Jan 2020 08:19:39 +0100	[thread overview]
Message-ID: <20200113071939.rtqb7yw45zi63fqy@sirius.home.kraxel.org> (raw)
In-Reply-To: <20200110163211.GB29736@mail-itl>

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.

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

cheers,
  Gerd

  reply	other threads:[~2020-01-13  7:19 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-10 16:32 bochs_hw_init fails to request framebuffer on EFI boot with plymouth visible Marek Marczykowski-Górecki
2020-01-13  7:19 ` Gerd Hoffmann [this message]
2020-01-15  0:33   ` Marek Marczykowski-Górecki
     [not found]     ` <20200115100821.qcdraolkoki6e5tz@sirius.home.kraxel.org>
2020-01-15 13:41       ` Marek Marczykowski-Górecki
2020-01-15 14:13         ` Gerd Hoffmann
2020-01-15 14:27           ` Marek Marczykowski-Górecki
2020-01-15 16:16             ` Gerd Hoffmann
2020-01-16  2:52               ` Marek Marczykowski-Górecki
2020-01-17 12:58                 ` Gerd Hoffmann
2020-01-17 15:22                   ` Marek Marczykowski-Górecki
2020-01-20  9:58                     ` Gerd Hoffmann

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20200113071939.rtqb7yw45zi63fqy@sirius.home.kraxel.org \
    --to=kraxel@redhat.com \
    --cc=marmarek@invisiblethingslab.com \
    --cc=virtualization@lists.linux-foundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.