Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

VBOX on x86_64 vmwgfx: probe failed w/ -EBUSY with 5.15 linux-yocto kernel

Description

Psplash never finishes it, I'm seeing some probe errors followed by a kernel trace saying it should reboot.

Seems that kernel 5.15 doesn't really work out with vbox. Needs more investigation.

VBOX 6.1.XX from debian testing.

Marlin seem to be unaffected, as it uses an older kernel and no errors from vmwgfx.

Environment

None

Activity

Show:

Walt Miner 
July 21, 2022 at 7:55 PM

Close for NN Milestone 1

Marius Vlad 
July 6, 2022 at 12:10 PM

Changed landed into master.

Marius Vlad 
June 30, 2022 at 12:31 PM

Okay, for the time being, I see that it loads correctly if we don't build it as a module, bur tather built-in, so I've added patch for that.

Marius Vlad 
June 29, 2022 at 2:02 PM

Still haven't really figured out what causes this but I got a bit further and noticed that building it in kernel rather than as a module, seems to be loading it:

[ 0.767048] vmwgfx 0000:00:02.0: vgaarb: deactivate vga console [ 0.769810] vmwgfx 0000:00:02.0: [drm] FIFO at 0x00000000e8400000 size is 2048 kiB [ 0.771082] vmwgfx 0000:00:02.0: [drm] VRAM at 0x00000000e0000000 size is 131072 kiB [ 0.772514] vmwgfx 0000:00:02.0: [drm] Running on SVGA version 2. [ 0.773576] vmwgfx 0000:00:02.0: [drm] DMA map mode: Caching DMA mappings. [ 0.775002] vmwgfx 0000:00:02.0: [drm] Legacy memory limits: VRAM = 131072 kB, FIFO = 2048 kB, surface = 393216 kB [ 0.776977] vmwgfx 0000:00:02.0: [drm] MOB limits: max mob size = 0 kB, max mob pages = 0 [ 0.778732] vmwgfx 0000:00:02.0: [drm] Capabilities: cursor, cursor bypass 2, alpha cursor, 3D, extended fifo, pitchlock, irq mask, gmr, traces, gmr2, screen object 2, [ 0.781289] vmwgfx 0000:00:02.0: [drm] Max GMR ids is 8192 [ 0.782343] vmwgfx 0000:00:02.0: [drm] Max number of GMR pages is 1048576 [ 0.783550] vmwgfx 0000:00:02.0: [drm] Maximum display memory size is 131072 kiB [ 0.786179] vmwgfx 0000:00:02.0: [drm] Screen Object display unit initialized [ 0.787722] vmwgfx 0000:00:02.0: [drm] Fifo max 0x00200000 min 0x00001000 cap 0x00000355 [ 0.789143] vmwgfx 0000:00:02.0: [drm] Available shader model: Legacy. [ 0.806797] [drm] Initialized vmwgfx 2.19.0 20210722 for 0000:00:02.0 on minor 0

Marius Vlad 
June 28, 2022 at 6:51 AM
(edited)

Further update:

  • Using linux-yocto-dev with 5.18 seems to be working, but other issues seems to happen and I can't get to a log in prompt (user-space sort of hangs)

  • Using linux-yocto with external/poky set to latest kirkstone (which bumps kernel to .44 I believe) still problematic.

  • returning -16 means EBUSY -> managed to load the driver after logging in.

  • Trace posted above is after booting, no longer seeing it now with latest external/poky.

Looks like a driver issue at this point, it should return some other err no, like EAGAIN, such that it would allow the kernel to probe it at a later point it time and load it.

Fixed

Details

Assignee

Reporter

Fix versions

Labels

Priority

Created June 22, 2022 at 1:30 PM
Updated July 21, 2022 at 7:55 PM
Resolved July 6, 2022 at 12:10 PM

Flag notifications