SeaBIOS

seabios@seabios.org

4 participants
3801 discussions

Orom execution issue.
by Naresh G. Solanki 23 Mar '15

23 Mar '15

Dear All, I'm porting coreboot with seabios payload on a e6xx processor based board. Seabios is executing properly but when it tries to execute vga bios of pcie graphic card(copied @ C000:0000), it hangs and doesn't returns. Can anyone give me suggestion on how to find the cause of the issue and resolve it so that it executes properly. - N Solanki

1 0

Re: [SeaBIOS] IDT issue
by Kevin O'Connor 23 Mar '15

23 Mar '15

On Thu, Mar 19, 2015 at 07:24:09PM +0530, Naresh G. Solanki wrote: > As per the document > > http://www.intel.com/content/www/us/en/intelligent-systems/queens-bay/atom-… > > Table 15 specifies about how to enable 0xE0000/0xF0000 segment. > As per that I have enabled the segment. Is that OK. That sounds like it. But, if it still doesn't work, then it is something else. :-) You could also try asking on the coreboot list. They are likely more familiar with the intel chipsets. -Kevin

2 1

[PATCH 0/3] checkstack.py code cleanup
by Kevin O'Connor 22 Mar '15

22 Mar '15

The checkstack.py script (which tries to estimate the stack usage of generated C code) was in need of a little cleanup. I actually wanted to use the script in another project and so needed to clean it up. I think it's worthwhile to push the changes back into the repo though. There should be no functional changes in this series. -Kevin Kevin O'Connor (3): checkstack: Replace function information tuple with class checkstack: Simplify yield calculations checkstack: Prefer passing "function" class instead of function address scripts/checkstack.py | 184 ++++++++++++++++++++++++-------------------------- 1 file changed, 89 insertions(+), 95 deletions(-) -- 1.9.3

1 4

[PATCHv3] vgabios: Don't use extra stack if it appears a modern OS is in use
by Kevin O'Connor 22 Mar '15

22 Mar '15

If the last mode set (while not in vm86 mode) was done from a VBE mode set call then disable the extra stack. This works under the premise that only a modern OS would invoke the VBE mode changing facilities and a modern OS would always call the vgabios with sufficient stack space. This is an ugly hack to work around a problem Windows Vista (and possibly later Windows releases) has with the VGA BIOS using a stack in the e-segment. Reported-by: Richard Laager <rlaager(a)wiktel.com> Signed-off-by: Kevin O'Connor <kevin(a)koconnor.net> --- Unfortunately, the previous patch I sent would not work well if a boot loader issues a VBE mode set call. (Indeed, SeaBIOS itself will issue a vbe mode set call when a bootsplash image is in use.) In that situation, with the previous patch, the extra stack would be disabled prematurely. This patch extends the previous idea - it disables the extra stack if the last video mode switch was a vbe mode switch. Thus, if a bootloader (or seabios itself) switches modes via vbe, but then switches back using a legacy mode switch, the extra stack will get reenabled. I've also thrown in the extra check of only changing the extra stack setting if the last mode change was not done in vm86 mode. This wasn't required in my tests with skifree, but I added in to make sure a mode switch from within a Windows emulation session wouldn't reenable the extra stack and cause a fault. Patch is also at: https://github.com/KevinOConnor/seabios/tree/testing -Kevin --- src/x86.h | 5 +++++ vgasrc/vgabios.c | 3 +++ vgasrc/vgabios.h | 4 +++- vgasrc/vgaentry.S | 15 +++++++++++++++ 4 files changed, 26 insertions(+), 1 deletion(-) diff --git a/src/x86.h b/src/x86.h index 7798b1c..14ebb7d 100644 --- a/src/x86.h +++ b/src/x86.h @@ -83,6 +83,11 @@ static inline u32 getcr0(void) { static inline void setcr0(u32 cr0) { asm("movl %0, %%cr0" : : "r"(cr0)); } +static inline u16 getcr0_vm86(void) { + u16 cr0; + asm("smsww %0" : "=r"(cr0)); + return cr0; +} static inline u64 rdmsr(u32 index) { diff --git a/vgasrc/vgabios.c b/vgasrc/vgabios.c index 4aa50e1..ec064fd 100644 --- a/vgasrc/vgabios.c +++ b/vgasrc/vgabios.c @@ -304,6 +304,9 @@ vga_set_mode(int mode, int flags) SET_BDA(video_mode, 0xff); SET_BDA_EXT(vbe_mode, mode | (flags & MF_VBEFLAGS)); SET_BDA_EXT(vgamode_offset, (u32)vmode_g); + if (!(getcr0_vm86() & CR0_PE)) + MASK_BDA_EXT(flags, BF_LEGACY_MODE + , (flags & MF_LEGACY) ? BF_LEGACY_MODE : 0); if (memmodel == MM_TEXT) { SET_BDA(video_cols, width); SET_BDA(video_rows, height-1); diff --git a/vgasrc/vgabios.h b/vgasrc/vgabios.h index fd796f2..b3c5594 100644 --- a/vgasrc/vgabios.h +++ b/vgasrc/vgabios.h @@ -62,7 +62,8 @@ struct gfx_op { #define GO_MEMSET 3 #define GO_MEMMOVE 4 -// Custom internal storage in BDA +// Custom internal storage in BDA (don't change here without also +// updating vgaentry.S) #define VGA_CUSTOM_BDA 0xb9 struct vga_bda_s { @@ -74,6 +75,7 @@ struct vga_bda_s { #define BF_PM_MASK 0x0f #define BF_EMULATE_TEXT 0x10 #define BF_SWCURSOR 0x20 +#define BF_LEGACY_MODE 0x40 #define GET_BDA_EXT(var) \ GET_FARVAR(SEG_BDA, ((struct vga_bda_s *)VGA_CUSTOM_BDA)->var) diff --git a/vgasrc/vgaentry.S b/vgasrc/vgaentry.S index f9cf656..a1646a9 100644 --- a/vgasrc/vgaentry.S +++ b/vgasrc/vgaentry.S @@ -104,6 +104,9 @@ entry_10: ENTRY_ARG_VGA handle_10 iretw +#define VGA_CUSTOM_BDA_FLAGS 0xb9 +#define BF_LEGACY_MODE 0x40 + // Entry point using extra stack DECLFUNC entry_10_extrastack entry_10_extrastack: @@ -111,6 +114,13 @@ entry_10_extrastack: cld pushw %ds // Set %ds:%eax to space on ExtraStack pushl %eax + + movw $SEG_BDA, %ax // Check if extra stack is enabled + movw %ax, %ds + movb VGA_CUSTOM_BDA_FLAGS, %al + testb $BF_LEGACY_MODE, %al + jz 1f + movw %cs:ExtraStackSeg, %ds movl $(CONFIG_VGA_EXTRA_STACK_SIZE-PUSHBREGS_size-16), %eax SAVEBREGS_POP_DSEAX // Save registers on extra stack @@ -134,6 +144,11 @@ entry_10_extrastack: RESTOREBREGS_DSEAX iretw +1: // Use regular entry point if the extra stack is disabled + popl %eax + popw %ds + jmp entry_10 + // Timer irq handling DECLFUNC entry_timer_hook entry_timer_hook: -- 1.9.3

2 2

[PATCH] checkrom: Fix typo in error message
by Andreas Färber 21 Mar '15

21 Mar '15

increate -> increase Signed-off-by: Andreas Färber <afaerber(a)suse.de> --- scripts/checkrom.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/scripts/checkrom.py b/scripts/checkrom.py index 377277d..aced5e2 100755 --- a/scripts/checkrom.py +++ b/scripts/checkrom.py @@ -39,7 +39,7 @@ def main(): finalsize = 256*1024 if datasize > finalsize: print("Error! ROM doesn't fit (%d > %d)" % (datasize, finalsize)) - print(" You have to either increate the size (CONFIG_ROM_SIZE)") + print(" You have to either increase the size (CONFIG_ROM_SIZE)") print(" or turn off some features (such as hardware support not") print(" needed) to make it fit. Trying a more recent gcc version") print(" might work too.") -- 2.1.4

3 2

Re: [SeaBIOS] [ipxe-devel] [Qemu-devel] Emulation failure on booting/rebooting VMs
by Robin Smidsrød 20 Mar '15

20 Mar '15

On 19.03.2015 19:31, Mohammed Gamal wrote: > > On Wed, Mar 18, 2015 at 7:09 PM, Kevin O'Connor <kevin(a)koconnor.net > <mailto:kevin@koconnor.net>> wrote: > > On Wed, Mar 18, 2015 at 06:36:48PM +0100, Mohammed Gamal wrote: > > Hi, > > I've been sporadically getting my KVM virtual machines crashing > with this > > message while they're booting > > > > KVM internal error. Suberror: 1 > > emulation failure > > EAX=00000000 EBX=00000000 ECX=00000000 EDX=00600f12 > > ESI=00000000 EDI=00000000 EBP=00000000 ESP=0000fffa > > EIP=0000ff53 EFL=00000006 [-----P-] CPL=0 II=0 A20=1 SMM=0 HLT=0 > > ES =0000 00000000 0000ffff 00009300 > > CS =f000 000f0000 0000ffff 00009b00 > > SS =0000 00000000 0000ffff 00009200 > > DS =0000 00000000 0000ffff 00009300 > > FS =0000 00000000 0000ffff 00009300 > > GS =0000 00000000 0000ffff 00009300 > > LDT=0000 00000000 0000ffff 00008200 > > TR =0000 00000000 0000ffff 00008300 > > GDT= 00000000 0000ffff > > IDT= 00000000 0000ffff > > CR0=60000010 CR2=00000000 CR3=00000000 CR4=00000000 > > DR0=0000000000000000 DR1=0000000000000000 DR2=0000000000000000 > > DR3=0000000000000000 > > DR6=00000000ffff0ff0 DR7=0000000000000400 > > EFER=0000000000000000 > > Code=74 65 61 6d 2e 00 66 68 5f 55 00 00 e9 c3 f8 fb f4 cb 66 c3 > <cf> 66 68 > > ff e6 00 00 e9 8b b1 66 55 66 57 66 56 66 53 66 89 c1 66 89 d6 a8 > 07 75 23 > > 66 0f > > > > I am running qemu 1.2, seabios 1.7.3 and ipxe (1.0.0-f6840ba) and > the host > > CPU is AMD Opteron 6386 SE running kernel 3.4.71. > > To debug seabios issues, we need the full log - see: > http://www.seabios.org/Debugging > > But, your software versions are a bit old which makes diagnosing any > issues hard. I suggest updating to the latest software and seeing if > the problem is still present. > > -Kevin > > > Unfortunately I can't change that setup. The problem is also rather > sporadic so I have no other means to reproduce it and debug it. > I tried looking into the seabios code but it looks like the instruction > pointer is pointing at the default interrupt vector table entry > 'entry_iret_official'. I presume this means that was triggered with an > interrupt of some sort? The other register values don't seem to provide > any clues nevertheless. I thought maybe this commit was relevant, https://git.ipxe.org/wimboot.git/commitdiff/1f11d05addc7aab9097b59e07680a0d…, but noticed you're not using wimboot at all... -- Robin

1 0

Re: [SeaBIOS] [Qemu-devel] Emulation failure on booting/rebooting VMs
by Kevin O'Connor 19 Mar '15

19 Mar '15

On Wed, Mar 18, 2015 at 06:36:48PM +0100, Mohammed Gamal wrote: > Hi, > I've been sporadically getting my KVM virtual machines crashing with this > message while they're booting > > KVM internal error. Suberror: 1 > emulation failure > EAX=00000000 EBX=00000000 ECX=00000000 EDX=00600f12 > ESI=00000000 EDI=00000000 EBP=00000000 ESP=0000fffa > EIP=0000ff53 EFL=00000006 [-----P-] CPL=0 II=0 A20=1 SMM=0 HLT=0 > ES =0000 00000000 0000ffff 00009300 > CS =f000 000f0000 0000ffff 00009b00 > SS =0000 00000000 0000ffff 00009200 > DS =0000 00000000 0000ffff 00009300 > FS =0000 00000000 0000ffff 00009300 > GS =0000 00000000 0000ffff 00009300 > LDT=0000 00000000 0000ffff 00008200 > TR =0000 00000000 0000ffff 00008300 > GDT= 00000000 0000ffff > IDT= 00000000 0000ffff > CR0=60000010 CR2=00000000 CR3=00000000 CR4=00000000 > DR0=0000000000000000 DR1=0000000000000000 DR2=0000000000000000 > DR3=0000000000000000 > DR6=00000000ffff0ff0 DR7=0000000000000400 > EFER=0000000000000000 > Code=74 65 61 6d 2e 00 66 68 5f 55 00 00 e9 c3 f8 fb f4 cb 66 c3 <cf> 66 68 > ff e6 00 00 e9 8b b1 66 55 66 57 66 56 66 53 66 89 c1 66 89 d6 a8 07 75 23 > 66 0f > > I am running qemu 1.2, seabios 1.7.3 and ipxe (1.0.0-f6840ba) and the host > CPU is AMD Opteron 6386 SE running kernel 3.4.71. To debug seabios issues, we need the full log - see: http://www.seabios.org/Debugging But, your software versions are a bit old which makes diagnosing any issues hard. I suggest updating to the latest software and seeing if the problem is still present. -Kevin

2 1

Re: [SeaBIOS] IDT issue
by Kevin O'Connor 19 Mar '15

19 Mar '15

On Thu, Mar 19, 2015 at 06:59:19PM +0530, Naresh G. Solanki wrote: > Hi, > > With respect to the auto reset issue, > > I did detailed memory test on my board and found the following > 0xA0000 - 0xBFFFF & 0xE0000 - 0xFFFFF region is not writable and every byte > reads as 0xFF. 0xA0000-0xC0000 is the legacy vga range, it's not normally mapped to memory, and can not (in normal cicrcumstances) be used as memory. The 0xC0000-0x100000 region is the historic BIOS and option rom location. It almost certainly can be used as memory on your board, but it's common for chipsets to have some magic bit that makes the region read-only. So, I think you need to find that magic bit and set it properly. -Kevin

2 1

Re: [SeaBIOS] IDT issue
by Kevin O'Connor 19 Mar '15

19 Mar '15

On Tue, Mar 17, 2015 at 06:42:06PM +0530, Naresh G. Solanki wrote: > Dear All, > > I'm trying to port coreboot with seabios payload on Intel Atom E6xx based > board, > > The problem I'm facing is during malloc init, the board reboot & keeps on > rebooting after displaying malloc init debug message. > > I tried to track it & found that it might probably be due to dummy IDT > loaded @seabios entry point (entry_elf) > > Once it reboot I'm finding that breakpoints set are not working. > Breakpoints are set through JTAG-XDP. > > Can anyone give an idea to how to go about this issue. SeaBIOS loads a dummy IDT when in 32bit mode, because the code is never supposed to raise an interrupt (interrupts and NMIs are always disabled when in 32bit mode). So, if you're seeing a fault with the IDT, it likely indicates something is causing a software fault. If a fault is ocurring in malloc_init(), then I'd check that the memory between 0xc0000-0x100000 is fully read/writable. You could also try disabling CONFIG_MALLOC_UPPERMEMORY to see if that changes behavior. malloc_init() is also called right after self-relocation, so check that the memory map that coreboot provides is accurate. You could also try disabling CONFIG_RELOCATE_INIT to see if that changes the fault. -Kevin

2 1

Re: [SeaBIOS] [Qemu-devel] Emulation failure on booting/rebooting VMs
by Andrey Korolyov 18 Mar '15

18 Mar '15

On Wed, Mar 18, 2015 at 8:36 PM, Mohammed Gamal <mohammed.gamal(a)profitbricks.com> wrote: > Hi, > I've been sporadically getting my KVM virtual machines crashing with this > message while they're booting > > KVM internal error. Suberror: 1 > emulation failure > EAX=00000000 EBX=00000000 ECX=00000000 EDX=00600f12 > ESI=00000000 EDI=00000000 EBP=00000000 ESP=0000fffa > EIP=0000ff53 EFL=00000006 [-----P-] CPL=0 II=0 A20=1 SMM=0 HLT=0 > ES =0000 00000000 0000ffff 00009300 > CS =f000 000f0000 0000ffff 00009b00 > SS =0000 00000000 0000ffff 00009200 > DS =0000 00000000 0000ffff 00009300 > FS =0000 00000000 0000ffff 00009300 > GS =0000 00000000 0000ffff 00009300 > LDT=0000 00000000 0000ffff 00008200 > TR =0000 00000000 0000ffff 00008300 > GDT= 00000000 0000ffff > IDT= 00000000 0000ffff > CR0=60000010 CR2=00000000 CR3=00000000 CR4=00000000 > DR0=0000000000000000 DR1=0000000000000000 DR2=0000000000000000 > DR3=0000000000000000 > DR6=00000000ffff0ff0 DR7=0000000000000400 > EFER=0000000000000000 > Code=74 65 61 6d 2e 00 66 68 5f 55 00 00 e9 c3 f8 fb f4 cb 66 c3 <cf> 66 68 > ff e6 00 00 e9 8b b1 66 55 66 57 66 56 66 53 66 89 c1 66 89 d6 a8 07 75 23 > 66 0f > > I am running qemu 1.2, seabios 1.7.3 and ipxe (1.0.0-f6840ba) and the host > CPU is AMD Opteron 6386 SE running kernel 3.4.71. > > I digged a little into the kvm kernel module code and I can trace these > emulation failures only to either a call to pf_interception() - which is > highly unlikely since the machine doesn't appear to have setup paging yet - > and task_switch_interception(). I am suspecting that ipxe or seabios might > be executing some invalid code or something, since this failure only appears > sporadically and is not 100% reproducible. Any ideas why this might be > happening? > > Regards, > Mohammed Hello, would you mind to try seabios 1.8.1?

1 0

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

SeaBIOS