From: "Sebastian Herbszt" <herbszt@gmx.de>
To: "Kevin O'Connor" <kevin@koconnor.net>, "Bjørn Mork" <bjorn@mork.no>
Cc: Brandon Bennett <bennetb@gmail.com>,
seabios@seabios.org, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [SeaBIOS] SeaBIOS error with Juniper FreeBSD kernel
Date: Sun, 10 Jul 2011 23:25:36 +0200 [thread overview]
Message-ID: <0895461378D74EC49BD787BDBFF8C934@FSCPC> (raw)
In-Reply-To: <20110710204100.GA25495@morn.localdomain>
Kevin O'Connor wrote:
> I investigated this a bit and I believe the Juniper OS has two SMBIOS
> bugs: it crashes when the table is in high memory, and when searching
Are all versions based on FreeBSD 4.11?
Are newer versions still affected?
> So, moving the SMBIOS back to the f-segment would fix this. But,
> there's an issue with that.
>
> The SMBIOS table is normally pretty small (eg, 263 bytes), but it
> increases with the amount of ram and number of CPUs. If one starts
> QEmu with 255 cpus, the SMBIOS size is over 11K. Fitting that into
> the f-segment (64K shared with all the other 16bit code and data) is
> going to be a real problem. This is also an issue for the mptable
> (which is over 5K at 255 cpus), but newer OSes don't care about
> mptable - not so for the smbios table though.
You might want to introduce CONFIG_SMBIOS_LOCATION and check for
space shortage in the F-segment case. Bochs BIOS panics if all requested tables
don't fit into the available space.
Sebastian
next prev parent reply other threads:[~2011-07-10 21:25 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-21 0:23 [Qemu-devel] SeaBIOS error with Juniper FreeBSD kernel Brandon Bennett
2010-02-21 4:05 ` Kevin O'Connor
2010-02-21 23:04 ` Brandon Bennett
2010-02-21 23:18 ` Brandon Bennett
2010-02-22 2:56 ` [Qemu-devel] SeaBIOS error with Nextstep bootloader Natalia Portillo
2010-02-28 19:51 ` Kevin O'Connor
2010-03-01 2:00 ` Natalia Portillo
2010-03-11 9:44 ` Natalia Portillo
2010-03-12 1:59 ` Kevin O'Connor
2010-03-12 9:05 ` Natalia Portillo
2010-03-13 6:30 ` Roy Tam
2010-03-13 14:42 ` [Qemu-devel] PS/2 mouse emulation problems Natalia Portillo
2010-03-13 14:44 ` [Qemu-devel] " Roy Tam
2010-03-13 20:23 ` Kevin O'Connor
2010-03-14 2:49 ` Roy Tam
2010-03-14 3:11 ` Roy Tam
2010-03-14 3:43 ` Kevin O'Connor
2010-03-14 5:28 ` Roy Tam
2010-03-14 7:11 ` Kevin O'Connor
2010-03-13 16:52 ` [Qemu-devel] SeaBIOS error with Nextstep bootloader Kevin O'Connor
2010-02-28 19:39 ` [Qemu-devel] SeaBIOS error with Juniper FreeBSD kernel Kevin O'Connor
2010-02-28 20:41 ` Gleb Natapov
2010-04-13 18:48 ` [Qemu-devel] " Bjørn Mork
2010-04-14 1:27 ` Kevin O'Connor
2010-04-14 10:51 ` Bjørn Mork
2011-07-07 15:45 ` [Qemu-devel] " Bjørn Mork
2011-07-07 23:50 ` Kevin O'Connor
2011-07-08 7:46 ` Bjørn Mork
2011-07-10 20:41 ` Kevin O'Connor
2011-07-10 21:25 ` Sebastian Herbszt [this message]
2011-07-11 23:33 ` [Qemu-devel] [SeaBIOS] " Brandon Bennett
2011-08-01 13:49 ` Bjørn Mork
2011-08-02 0:36 ` Kevin O'Connor
2011-08-02 9:33 ` Bjørn Mork
2011-08-02 12:41 ` Kevin O'Connor
2011-08-03 12:42 ` Bjørn Mork
2011-08-03 13:31 ` Avi Kivity
2011-08-03 13:48 ` Bjørn Mork
2011-08-03 14:03 ` Avi Kivity
2011-08-03 23:48 ` 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=0895461378D74EC49BD787BDBFF8C934@FSCPC \
--to=herbszt@gmx.de \
--cc=bennetb@gmail.com \
--cc=bjorn@mork.no \
--cc=kevin@koconnor.net \
--cc=qemu-devel@nongnu.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).