From: Kevin O'Connor <kevin@koconnor.net>
To: David Woodhouse <dwmw2@infradead.org>
Cc: seabios@seabios.org, kexec <kexec@lists.infradead.org>
Subject: Re: [SeaBIOS] Real mode kexec failure with non-IDE disk
Date: Tue, 30 Apr 2019 22:56:01 -0400 [thread overview]
Message-ID: <20190501025601.GA5342@morn.lan> (raw)
In-Reply-To: <e5872703412f9a56c10df52d9793ca2a6401d7f0.camel@infradead.org>
On Mon, Apr 29, 2019 at 12:05:33AM +0300, David Woodhouse wrote:
> When I kexec either Xen or Linux in real mode, from either Xen or
> Linux, it fails.
>
> The last thing I see looks like SeaBIOS trying to use SMM for call32:
>
> ----------------
> IN:
> 0x00000000000f70ec: mov %eax,%esi
> 0x00000000000f70ef: mov $0xb5,%eax
> 0x00000000000f70f5: mov $0x1234,%ecx
> 0x00000000000f70fb: mov $0xef3dc,%ebx
> 0x00000000000f7101: out %al,$0xb2
> 0x00000000000f7103: pause
>
> ----------------
> IN:
> 0x00000000000ef3db: hlt
>
> This happens when the real mode boot code calls INT 13h to read from
> the disk. It seems to happen with virtio and SATA disks.
>
> This is with the Ubuntu-packaged 1.10.2-1ubuntu1 SeaBIOS. Switching to
> an IDE disk, or booting with 'edd=skipmbr', makes Xen work and Linux
> get a little further before it dies anyway.
Hi David,
That call trace certainly looks odd. The SeaBIOS debugging info would
help - try compiling SeaBIOS with debug level 8 and grab the log (as
described at: https://www.seabios.org/Debugging#Diagnostic_information
).
-Kevin
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next prev parent reply other threads:[~2019-05-01 2:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-28 21:05 Real mode kexec failure with non-IDE disk David Woodhouse
2019-05-01 2:56 ` Kevin O'Connor [this message]
2019-05-01 20:16 ` [SeaBIOS] " David Woodhouse
2019-05-07 15:17 ` Kevin O'Connor
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=20190501025601.GA5342@morn.lan \
--to=kevin@koconnor.net \
--cc=dwmw2@infradead.org \
--cc=kexec@lists.infradead.org \
--cc=seabios@seabios.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.