bochs_drm: failed bochs_hw_init() results in panic

2020-01-09 Thread Marek Marczykowski-Górecki
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? Full message: [ 33.032576] [drm:bochs_hw_init [bochs_drm]] *ERROR* Cannot r

Re: bochs_drm: failed bochs_hw_init() results in panic

2020-01-09 Thread Gerd Hoffmann
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 t

Re: bochs_drm: failed bochs_hw_init() results in panic

2020-01-10 Thread Marek Marczykowski-Górecki
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() f

Re: bochs_drm: failed bochs_hw_init() results in panic

2020-01-12 Thread Gerd Hoffmann
> Now the messages looks like this: > > [ 29.800835] bochs-drm :00:02.0: remove_conflicting_pci_framebuffers: > bar 0: 0xc000 -> 0xc0ff > [ 29.800840] bochs-drm :00:02.0: remove_conflicting_pci_framebuffers: > bar 2: 0xc1087000 -> 0xc1087fff > [ 29.800842] checking generic