Bug 254247 - logos per CPU remain persistent after tty switch under VirtualBox
Summary: logos per CPU remain persistent after tty switch under VirtualBox
Status: Closed FIXED
Alias: None
Product: Base System
Classification: Unclassified
Component: kern (show other bugs)
Version: 12.2-STABLE
Hardware: amd64 Any
: --- Affects Only Me
Assignee: Virtualbox Team (Nobody)
URL:
Keywords: vt
Depends on:
Blocks:
 
Reported: 2021-03-12 22:28 UTC by freebsd
Modified: 2022-01-12 18:51 UTC (History)
3 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description freebsd 2021-03-12 22:28:50 UTC 
I currently use FreeBSD 12-STABLE under VirutalBox 5.2.42.

After switching from ttyv0 to any other ttyv, logos-per-CPU appear and remain persistent. I have not noticed during boot; do not see after boot.

Is there no option to turn off logos per CPU on vt (https://reviews.freebsd.org/D2181) but by (re)building FreeBSD kernel sans "device splash"?
Comment 1 freebsd 2021-03-15 05:11:38 UTC 
(In reply to parv from comment #0)

I should have noted originally that FreeBSD is being booted via EFI.
Comment 2 freebsd 2021-03-24 23:08:03 UTC 
I had since recompiled the kernel with "nodevice splash". Now I do not see the logos-per-CPU after switching (virtual)consoles.

That is less than good enough solution when using GENERIC kernel & for anyone who do not want to recompile the kernel for whatever reasons.
Comment 3 Ed Maste freebsd_committer freebsd_triage 2021-09-26 21:27:23 UTC 
If you can build and test on a stable branch, please give it a try now. Ensure that the stable branch includes at least:

stable/13 9352de39c3dc
stable/12 e4fcff8ee124
Comment 4 freebsd 2021-09-27 08:17:11 UTC 
After switching to stable/13 some time ago (certainly after 2021-03-24 23:08:03 UTC of comment 2), I have been unable to make the orbs or penguins appear again on the console at all. (Still in VirtualBox 5.2 with EFI)

I need to get /usr/src for stable/12; will report back on that.
Comment 5 Graham Perrin freebsd_committer freebsd_triage 2022-01-11 20:33:33 UTC 
FreeBSD-SA-22:01.vt

<https://www.freebsd.org/security/advisories/>