From: "Marek Marczykowski-Górecki" <marmarek@invisiblethingslab.com>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: virtualization@lists.linux-foundation.org
Subject: Re: bochs_drm: failed bochs_hw_init() results in panic
Date: Sat, 11 Jan 2020 01:07:45 +0100 [thread overview]
Message-ID: <20200111000745.GF2507@mail-itl> (raw)
In-Reply-To: <20200110053553.4gqlagjdpfi6pg3b@sirius.home.kraxel.org>
[-- Attachment #1.1: Type: text/plain, Size: 2155 bytes --]
On Fri, Jan 10, 2020 at 06:35:53AM +0100, Gerd Hoffmann wrote:
> On Fri, Jan 10, 2020 at 02:33:28AM +0100, Marek Marczykowski-Górecki wrote:
> > Hi,
> >
> > It looks like bochs_kms_fini() don't like being called if
> > bochs_kms_init() wasn't. Regardless of the reason for the
> > bochs_hw_init() failure (that's another story), it shouldn't cause a
> > panic. Any idea how to fix it?
>
> maybe this?
Yes, it prevents the panic, with a little fix. Thanks!
Of course(?) I don't have working framebuffer then, but I can interact
with the system in other ways, at least to diagnose what's wrong.
Now the messages looks like this:
[ 29.800835] bochs-drm 0000:00:02.0: remove_conflicting_pci_framebuffers: bar 0: 0xc0000000 -> 0xc0ffffff
[ 29.800840] bochs-drm 0000:00:02.0: remove_conflicting_pci_framebuffers: bar 2: 0xc1087000 -> 0xc1087fff
[ 29.800842] checking generic (c0000000 1000000) vs hw (c0000000 1000000)
[ 29.800843] fb0: switching to bochsdrmfb from EFI VGA
[ 29.805542] bochs-drm 0000:00:02.0: vgaarb: deactivate vga console
[ 29.805742] bochs-drm 0000:00:02.0: BAR 0: can't reserve [mem 0xc0000000-0xc0ffffff pref]
[ 29.805749] [drm:bochs_hw_init [bochs_drm]] *ERROR* Cannot request framebuffer
[ 29.805781] bochs-drm: probe of 0000:00:02.0 failed with error -16
[ 30.129014] Trying to free nonexistent resource <00000000c0000000-00000000c0ffffff>
Is the last one an issue?
> diff --git a/drivers/gpu/drm/bochs/bochs_kms.c b/drivers/gpu/drm/bochs/bochs_kms.c
> index 3f0006c2470d..322be68a238a 100644
> --- a/drivers/gpu/drm/bochs/bochs_kms.c
> +++ b/drivers/gpu/drm/bochs/bochs_kms.c
> @@ -192,6 +192,9 @@ int bochs_kms_init(struct bochs_device *bochs)
>
> void bochs_kms_fini(struct bochs_device *bochs)
> {
> + if (!dev->mode_config.num_connector)
bochs->dev->...
> + return;
> +
> drm_atomic_helper_shutdown(bochs->dev);
> drm_mode_config_cleanup(bochs->dev);
> }
>
--
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-11 0:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-10 1:33 bochs_drm: failed bochs_hw_init() results in panic Marek Marczykowski-Górecki
2020-01-10 5:35 ` Gerd Hoffmann
2020-01-11 0:07 ` Marek Marczykowski-Górecki [this message]
2020-01-13 7:03 ` 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=20200111000745.GF2507@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