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 15:27:41 +0100 [thread overview]
Message-ID: <20200115142741.GM2507@mail-itl> (raw)
In-Reply-To: <20200115141353.3kse3uj2mg6ik6k5@sirius.home.kraxel.org>
[-- Attachment #1.1: Type: text/plain, Size: 1338 bytes --]
On Wed, Jan 15, 2020 at 03:13:53PM +0100, Gerd Hoffmann wrote:
> Hi,
>
> > > And "grep -A1 0000:00:02.0 /proc/iomem" ?
> >
> > c0000000-c0ffffff : 0000:00:02.0
> > c1000000-c103ffff : 0000:00:04.0
>
> So no reservation left. Whatever blocked the pci bar resource (efifb
> probably) is gone now.
>
> So the interesting question is why that reservation sticked long enough
> to prevent bochs-drm from initializing. In theory efifb de-init should
> be completed when drm_fb_helper_remove_conflicting_pci_framebuffers()
> returns.
Maybe the fact that switching to text mode plymouth help, gives some
hint?
> Bisecting could help, or springkling printk's into efifb ...
That's a pretty broad range of commits...
I'll try adding some printks.
> > [46921.562805] fbcon: bochs-drmdrmfb (fb0) is primary device
> > [46921.562808] fbcon: Deferring console take-over
>
> I think that is just some eye candy which delays fbcon init until
> something is actually printed.
>
> Try "echo hello world > /dev/tty0".
> Maybe tapping enter (to make getty re-print the login prompt) works too.
Oh, yes, indeed it works.
--
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
next prev parent reply other threads:[~2020-01-15 14:27 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
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 [this message]
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=20200115142741.GM2507@mail-itl \
--to=marmarek@invisiblethingslab.com \
--cc=kraxel@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).