From: "Pedro Falcato" <pedro.falcato@gmail.com>
To: devel@edk2.groups.io, kraxel@redhat.com
Cc: Laszlo Ersek <lersek@redhat.com>,
Oliver Steffen <osteffen@redhat.com>,
Ard Biesheuvel <ardb+tianocore@kernel.org>,
Jiewen Yao <jiewen.yao@intel.com>,
dun.tan@intel.com
Subject: Re: [edk2-devel] [PATCH 1/1] OvmfPkg/QemuVideoDxe: purge VbeShim
Date: Tue, 13 Feb 2024 14:55:13 +0000 [thread overview]
Message-ID: <CAKbZUD0-HZRoN3RHV88BaYbdXmtQ2d4eZA=Y-1x-Or2PgvrdQg@mail.gmail.com> (raw)
In-Reply-To: <hqgwpcritser4r2n5u5gjvncjnx6ytj3rjvtrueacjbgaokrmp@mcijnl4prbvo>
On Tue, Feb 13, 2024 at 2:02 PM Gerd Hoffmann <kraxel@redhat.com> wrote:
>
> On Tue, Feb 13, 2024 at 11:44:17AM +0100, Laszlo Ersek wrote:
> > Hi Gerd,
> >
> > On 2/13/24 09:59, Gerd Hoffmann wrote:
> > > Removing CSM support broke VbeShim.
> > >
> > > I see ASSERTS being triggered, both in vbeshim code and elsewhere.
> > > Didn't investigate in detail, but apparently the real mode address space
> > > is not considered being special any more, which invalidates some
> > > assumptions of the vbeshim code.
> > >
> > > The guest os which depends on vbeshim for video support is -- according
> > > to the comments -- Windows 2008 R2. Which went EOL in January 2020,
> > > more than four years ago.
> > >
> > > Time to retire VbeShim. RIP.
> >
> > I don't understand this, and/or disagree.
> >
> > (1) Please collect more information about the ASSERT()s (the failure mode you are seeing).
> > Because, (a) in the code that's being removed in this patch, I don't see any ASSERT() that should fire, and (b) I cannot reproduce the issue. (In fact my log contains "InstallVbeShim: VBE shim installed".)
>
> Fair enough. The ASSERT() I see firing is this:
>
> ASSERT /home/kraxel/projects/edk2/OvmfPkg/QemuVideoDxe/VbeShim.c(142): Int0x10->Segment == 0x0000
>
> It reproduces for me when booting with a bunch of hot-pluggable CPUs (qemu -smp 2,maxcpus=32).
>
> I bisected this, and it seems indeed totally unrelated to CSM removal:
>
> 725acd0b9cc047b20a1b9379e46f05d3ebcf485e is the first bad commit
> commit 725acd0b9cc047b20a1b9379e46f05d3ebcf485e
> Author: Dun Tan <dun.tan@intel.com>
> Date: Fri Dec 1 10:53:32 2023 +0800
>
> UefiCpuPkg: Avoid assuming only one smmbasehob
>
> New theory: This is a NULL pointer dereference corrupting the zero page.
Tangentially related: Maybe it's time to unmap the NULL page? :)
--
Pedro
-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#115384): https://edk2.groups.io/g/devel/message/115384
Mute This Topic: https://groups.io/mt/104329097/7686176
Group Owner: devel+owner@edk2.groups.io
Unsubscribe: https://edk2.groups.io/g/devel/unsub [rebecca@openfw.io]
-=-=-=-=-=-=-=-=-=-=-=-
next prev parent reply other threads:[~2024-02-13 14:55 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-13 8:59 [edk2-devel] [PATCH 1/1] OvmfPkg/QemuVideoDxe: purge VbeShim Gerd Hoffmann
2024-02-13 10:41 ` Ard Biesheuvel
2024-02-13 10:44 ` Laszlo Ersek
2024-02-13 14:02 ` Gerd Hoffmann
2024-02-13 14:55 ` Pedro Falcato [this message]
2024-02-13 14:56 ` Ard Biesheuvel
2024-02-13 15:07 ` Pedro Falcato
2024-02-13 15:28 ` Gerd Hoffmann
2024-02-13 15:47 ` Pedro Falcato
2024-02-13 17:31 ` Laszlo Ersek
2024-02-13 17:28 ` Laszlo Ersek
2024-02-13 18:13 ` Laszlo Ersek
2024-02-13 20:25 ` Laszlo Ersek
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-list 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='CAKbZUD0-HZRoN3RHV88BaYbdXmtQ2d4eZA=Y-1x-Or2PgvrdQg@mail.gmail.com' \
--to=devel@edk2.groups.io \
/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