if failing for me with a seabios payload. Not a filo payload, mind you.
The failure is odd. It seems to be dying at first instruction with a triple fault.
Anyway, ideas welcome :-)
Devices initialized Copying Interrupt Routing Table to 0x000f0000... done. Moving GDT to 0x500...ok Multiboot Information structure has been written. Adjust low_table_end from 0x00000530 to 0x00001000 Adjust rom_table_end from 0x000f04b8 to 0x00100000 Wrote coreboot table at: 00000530 - 00000bc0 checksum bda7 Check CBFS header at fffeffd0 magic is 4f524243 Found CBFS header at fffeffd0 Check normal/payload Got a payload Segment fff80028 data: New segment dstaddr 0xf0000 memsize 0x10000 srcaddr 0xfff80060 filesize 0x10000 (cleaned up) New segment addr 0xf0000 size 0x10000 offset 0xfff80060 filesize 0x10000 Payload is overwriting Coreboot tables. Segment fff80044 Entry 000fa684 Loading Segment: addr: 0x00000000000f0000 memsz: 0x0000000000010000 filesz: 0x0000000000010000 it's not compressed! Jumping to boot code at fa684 qemu: fatal: triple fault EAX=2badb002 EBX=000f0400 ECX=00000000 EDX=00012000 ESI=03fee000 EDI=00016000 EBP=000fa684 ESP=03ffbe9c EIP=000fa684 EFL=00000002 [-------] CPL=0 II=0 A20=1 SMM=0 HLT=0 ES =0018 00000000 ffffffff 00cf9300 CS =0010 00000000 ffffffff 00cf9b00 SS =0018 00000000 ffffffff 00cf9300 DS =0018 00000000 ffffffff 00cf9300 FS =0018 00000000 ffffffff 00cf9300 GS =0018 00000000 ffffffff 00cf9300 LDT=0000 00000000 0000ffff 00008000 TR =0000 00000000 0000ffff 00008000 GDT= 00000500 00000027 IDT= 0000d100 0000009f CR0=60000011 CR2=00000000 CR3=00000000 CR4=00000000 CCS=00009000 CCD=00004800 CCO=SARL FCW=037f FSW=0000 [ST=0] FTW=00 MXCSR=00001f80 FPR0=0000000000000000 0000 FPR1=0000000000000000 0000 FPR2=0000000000000000 0000 FPR3=0000000000000000 0000 FPR4=0000000000000000 0000 FPR5=0000000000000000 0000 FPR6=0000000000000000 0000 FPR7=0000000000000000 0000 XMM00=00000000000000000000000000000000 XMM01=00000000000000000000000000000000 XMM02=00000000000000000000000000000000 XMM03=00000000000000000000000000000000 XMM04=00000000000000000000000000000000 XMM05=00000000000000000000000000000000 XMM06=00000000000000000000000000000000 XMM07=00000000000000000000000000000000 Aborted
This seabios was built locally from organically harvested electrons.
Thanks
ron
-----Original Message----- From: coreboot-bounces+mylesgw=gmail.com@coreboot.org [mailto:coreboot- bounces+mylesgw=gmail.com@coreboot.org] On Behalf Of ron minnich Sent: Tuesday, May 12, 2009 9:45 AM To: coreboot Subject: [coreboot] qemu, v2, latest
if failing for me with a seabios payload. Not a filo payload, mind you.
The failure is odd. It seems to be dying at first instruction with a triple fault.
Anyway, ideas welcome :-)
Devices initialized Copying Interrupt Routing Table to 0x000f0000... done. Moving GDT to 0x500...ok Multiboot Information structure has been written. Adjust low_table_end from 0x00000530 to 0x00001000 Adjust rom_table_end from 0x000f04b8 to 0x00100000 Wrote coreboot table at: 00000530 - 00000bc0 checksum bda7 Check CBFS header at fffeffd0 magic is 4f524243 Found CBFS header at fffeffd0 Check normal/payload Got a payload Segment fff80028 data: New segment dstaddr 0xf0000 memsize 0x10000 srcaddr 0xfff80060 filesize 0x10000 (cleaned up) New segment addr 0xf0000 size 0x10000 offset 0xfff80060 filesize 0x10000
Payload is overwriting Coreboot tables.
I don't see this line in mine. Could you try HAVE_LOW_TABLES=0 and see if that fixes it for you? If so we can try to debug why having both doesn't work. If not we can compare payloads. My entry point is different than yours too.
Thanks, Myles
On Tue, May 12, 2009 at 8:56 AM, Myles Watson mylesgw@gmail.com wrote:
Payload is overwriting Coreboot tables.
I don't see this line in mine. Could you try HAVE_LOW_TABLES=0 and see if that fixes it for you? If so we can try to debug why having both doesn't work. If not we can compare payloads. My entry point is different than yours too.
oops, I was not up to date on this one. Now the high tables are at Writing high table forward entry at 0x00000500 Wrote coreboot table at: 00000500 - 00000518 checksum f3df New low_table_end: 0x00000500 Now going to write high coreboot table at 0x03ff0800 rom_table_end = 0x03ff0800 Adjust low_table_end from 0x00000500 to 0x00001000 Adjust rom_table_end from 0x03ff0800 to 0x04000000 Adding high table area Wrote coreboot table at: 03ff0800 - 03ff0e8c checksum 1a86
which makes more sense. Still triple faulting however.
I'll just have coreboot dump the first 32 bytes of memory at entry point to make sure it's what I think it is.
If you can test latest coreboot with latest qemu I'd be interested. I have xxd'ed the coreboot rom and it certainly appears the data is in there correctly.
bbl. Gotta go.
ron
On Tue, May 12, 2009 at 10:12 AM, ron minnich rminnich@gmail.com wrote:
On Tue, May 12, 2009 at 8:56 AM, Myles Watson mylesgw@gmail.com wrote:
Payload is overwriting Coreboot tables.
I don't see this line in mine. Could you try HAVE_LOW_TABLES=0 and see if that fixes it for you? If so we can try to debug why having both doesn't work. If not we can compare payloads. My entry point is different than yours too.
oops, I was not up to date on this one. Now the high tables are at Writing high table forward entry at 0x00000500 Wrote coreboot table at: 00000500 - 00000518 checksum f3df New low_table_end: 0x00000500 Now going to write high coreboot table at 0x03ff0800 rom_table_end = 0x03ff0800 Adjust low_table_end from 0x00000500 to 0x00001000 Adjust rom_table_end from 0x03ff0800 to 0x04000000 Adding high table area Wrote coreboot table at: 03ff0800 - 03ff0e8c checksum 1a86
which makes more sense. Still triple faulting however.
I'll just have coreboot dump the first 32 bytes of memory at entry point to make sure it's what I think it is.
If you can test latest coreboot with latest qemu I'd be interested.
It triple faults for me too. I was using 0.9.1, and I downloaded 0.10.4.
I have xxd'ed the coreboot rom and it certainly appears the data is in there correctly.
It looks like a qemu change.
Thanks, Myles
I'll just have coreboot dump the first 32 bytes of memory at entry point to make sure it's what I think it is.
If you can test latest coreboot with latest qemu I'd be interested.
It triple faults for me too. I was using 0.9.1, and I downloaded 0.10.4.
Has anyone tried CONFIG_COMPRESS=0 lately? Is there some trick to getting it to work?
It dies where it normally uncompresses. I wanted to try it for debugging.
coreboot-2.0.0-r4277M-GRUB2 Tue May 12 13:07:12 MDT 2009 starting... Copying coreboot to RAM. Copying image to RAM.
Jumping to image.
Thanks, Myles
OK, the score at present for qemu latest tree, filo payload, boots fine latest tree, seabios, triple fault.
Note that seabios loads to f0000.
I am going to try to validate the payload after it is copied out now.
ron
-
Myles Watson -
ron minnich