Re: [coreboot] [PATCH] workaround for "An unexpected error (805262864) occurred at line 1768 of d:\xpclient\base\boot\setup\arcdisp.c"
Marc Jones wrote: > The attached patch works around a Windows XP or Server 2003 setup > failure where an error message such as: > "An unexpected error (805262864) occurred at line 1768 of > d:\xpclient\base\boot\setup\arcdisp.c" > The value 805262864 varies, and is the physical address, in decimal, > of one of the ACPI tables. > > Tested on Persimmon. Others abuild tested only. > Signed-off-by: Scott Duplichan > ]It looks like src/mainboard/amd/mahogany/acpi_tables.c has a double ]paste issue. Fix that and it looks good. ] ]Acked-by: Marc Jones ] ] ]Marc Hello Marc, Thanks for finding the double paste problem in mahogany. This change is revision 6600. Thanks, Scott -- coreboot mailing list: coreboot@coreboot.org http://www.coreboot.org/mailman/listinfo/coreboot
Re: [coreboot] [PATCH] workaround for "An unexpected error (805262864) occurred at line 1768 of d:\xpclient\base\boot\setup\arcdisp.c"
On Thu, May 19, 2011 at 2:59 AM, Marc Jones wrote: > On Wed, May 18, 2011 at 12:40 AM, Scott Duplichan wrote: >> The attached patch works around a Windows XP or Server 2003 setup >> failure where an error message such as: >> "An unexpected error (805262864) occurred at line 1768 of >> d:\xpclient\base\boot\setup\arcdisp.c" >> The value 805262864 varies, and is the physical address, in decimal, >> of one of the ACPI tables. >> >> Tested on Persimmon. Others abuild tested only. >> Signed-off-by: Scott Duplichan >> >> Detailed explanation: The error message is displayed when a 1024 dword >> page table array used by setupldr runs out of space. This table is used >> for mapping various physical addresses, such as those of ACPI tables >> (a separate table identity maps the lower 16MB used by setupldr code >> and data). Setupldr only looks at ACPI tables (FACP) to determine make >> and model of the system. The make and model of the system is needed when >> setupldr scans the good/bad bios lists contained in txtsetup.sif. The >> good/bad bios lists are used to bypass installation of the ACPI enabled >> kernel on certain systems known to have ACPI problems. The code loop >> that scans the lists creates a new mapping each time it reads an ACPI >> table, and never frees mappings. The code uses FACP OEM ID to determine >> the system model. The code sequentially reads tables listed in the RSDT >> array until the FACP is found. Each read consumes one page table entry. >> If more that 4 tables precede the FACP in the RSDT array, the 1024 >> entry page table array will run out of space before the good/bad bios >> list processing completes. BIOS can work around this Windows XP/Server >> 2003 limitation by placing the FACP early in the RSDT array. >> >> Thanks, >> Scott > > Hi Scott, > > Good find. This must have been a difficult debug. > > It looks like src/mainboard/amd/mahogany/acpi_tables.c has a double > paste issue. Fix that and it looks good. Seems to be an issue with the line endings. He could have edited something in windows and made the patch. - Thanks, Vikram -- coreboot mailing list: coreboot@coreboot.org http://www.coreboot.org/mailman/listinfo/coreboot
Re: [coreboot] [PATCH] workaround for "An unexpected error (805262864) occurred at line 1768 of d:\xpclient\base\boot\setup\arcdisp.c"
David Robinson wrote: > I can't see any compromises in applying this patch so should it be > considered it a fix rather than a workaround? No, as the problem is clearly not in coreboot. //Peter -- coreboot mailing list: coreboot@coreboot.org http://www.coreboot.org/mailman/listinfo/coreboot
Re: [coreboot] [PATCH] workaround for "An unexpected error (805262864) occurred at line 1768 of d:\xpclient\base\boot\setup\arcdisp.c"
ssess is to have an easy way to reflash the bios when >> > your image failes. >> >> Seems quite inspirational to the people who wanted to port for new >> boards. >> @ Stefan: Can you please share your opinions on this? > > The time required of course depends on many factors. In general > terms, these are: > > 1. Ability to understand or learn C and programming languages in > ? general, and hardware structure. > 2. Hardware differences. > 3. How much similar code there already exists in coreboot. > 4. How readable the code is that does exist in coreboot and is > ? relevant for the project. > > In concrete terms, they are: > > 1. Programming and electronics experience, and abstract thinking > 2. How similar your mainboard is to another already supported > ? mainboard. > 3. If *any* similar mainboard is already supported by coreboot. > ? By similar I mean exact same relevant components; cpu north south > ? superio. > 4. Quality of coreboot code for cpu north south superio. > > These are just the factors to consider *when all components are > supported already*. In ideal circumstances a board port needs to take > only one hour. In reality, circumstances are never ideal and the time > needed per board grows exponentially or even steeper still with the > number of less than ideal points to consider. > > Worst case is so far 8-12 man-months for a coreboot expert. Thank you. I think this can also be in Developer wiki. This might give an insight of how much work is involved. (or is it already there in the wiki?) - Thanks, Vikram -- Message: 4 Date: Wed, 18 May 2011 00:48:31 -0500 From: "Scott Duplichan" To: Subject: Re: [coreboot] Kconfig vs. devicetree vs. CMOS policy for options? Message-ID: Content-Type: text/plain;charset="us-ascii" Anders Jenbo wrote: ]You could use http://driverpacks.net/ to incorporate the AHCI driveres ]on your cd. Hello Anders, Thanks for the suggestion. I did find that site the other day. At first it looked like what I needed. But when I went to choose a download, I I could find x64 packs only for Vista/7. I use the x64 edition of XP or Server 2003. Thanks, Scott -- Message: 5 Date: Wed, 18 May 2011 01:40:08 -0500 From: "Scott Duplichan" To: Subject: [coreboot] [PATCH] workaround for "An unexpected error (805262864)occurred at line 1768 of d:\xpclient\base\boot\setup\arcdisp.c" Message-ID: Content-Type: text/plain; charset="us-ascii" The attached patch works around a Windows XP or Server 2003 setup failure where an error message such as: "An unexpected error (805262864) occurred at line 1768 of d:\xpclient\base\boot\setup\arcdisp.c" The value 805262864 varies, and is the physical address, in decimal, of one of the ACPI tables. Tested on Persimmon. Others abuild tested only. Signed-off-by: Scott Duplichan Detailed explanation: The error message is displayed when a 1024 dword page table array used by setupldr runs out of space. This table is used for mapping various physical addresses, such as those of ACPI tables (a separate table identity maps the lower 16MB used by setupldr code and data). Setupldr only looks at ACPI tables (FACP) to determine make and model of the system. The make and model of the system is needed when setupldr scans the good/bad bios lists contained in txtsetup.sif. The good/bad bios lists are used to bypass installation of the ACPI enabled kernel on certain systems known to have ACPI problems. The code loop that scans the lists creates a new mapping each time it reads an ACPI table, and never frees mappings. The code uses FACP OEM ID to determine the system model. The code sequentially reads tables listed in the RSDT array until the FACP is found. Each read consumes one page table entry. If more that 4 tables precede the FACP in the RSDT array, the 1024 entry page table array will run out of space before the good/bad bios list processing completes. BIOS can work around this Windows XP/Server 2003 limitation by placing the FACP early in the RSDT array. Thanks, Scott -- next part -- A non-text attachment was scrubbed... Name: xp-workaround.patch Type: application/octet-stream Size: 21959 bytes Desc: not available URL: <http://www.coreboot.org/pipermail/coreboot/attachments/20110518/d5dedce5/attachment.obj> -- ___ coreboot mailing list coreboot@coreboot.org http://www.coreboot.org/mailman/listinfo/coreboot End of coreboot Digest, Vol 75, Issue 54 Blue Chip Technology Limited. Chowley Oak Lane, Tattenhall, Chester, Cheshire CH3 9EX Tel: 01829 772000 Registered in England 3110403 Vat No: GB 618 374134 -- coreboot mailing list: coreboot@coreboot.org http://www.coreboot.org/mailman/listinfo/coreboot
Re: [coreboot] [PATCH] workaround for "An unexpected error (805262864) occurred at line 1768 of d:\xpclient\base\boot\setup\arcdisp.c"
On Wed, May 18, 2011 at 12:40 AM, Scott Duplichan wrote: > The attached patch works around a Windows XP or Server 2003 setup > failure where an error message such as: > "An unexpected error (805262864) occurred at line 1768 of > d:\xpclient\base\boot\setup\arcdisp.c" > The value 805262864 varies, and is the physical address, in decimal, > of one of the ACPI tables. > > Tested on Persimmon. Others abuild tested only. > Signed-off-by: Scott Duplichan > > Detailed explanation: The error message is displayed when a 1024 dword > page table array used by setupldr runs out of space. This table is used > for mapping various physical addresses, such as those of ACPI tables > (a separate table identity maps the lower 16MB used by setupldr code > and data). Setupldr only looks at ACPI tables (FACP) to determine make > and model of the system. The make and model of the system is needed when > setupldr scans the good/bad bios lists contained in txtsetup.sif. The > good/bad bios lists are used to bypass installation of the ACPI enabled > kernel on certain systems known to have ACPI problems. The code loop > that scans the lists creates a new mapping each time it reads an ACPI > table, and never frees mappings. The code uses FACP OEM ID to determine > the system model. The code sequentially reads tables listed in the RSDT > array until the FACP is found. Each read consumes one page table entry. > If more that 4 tables precede the FACP in the RSDT array, the 1024 > entry page table array will run out of space before the good/bad bios > list processing completes. BIOS can work around this Windows XP/Server > 2003 limitation by placing the FACP early in the RSDT array. > > Thanks, > Scott Hi Scott, Good find. This must have been a difficult debug. It looks like src/mainboard/amd/mahogany/acpi_tables.c has a double paste issue. Fix that and it looks good. Acked-by: Marc Jones Marc -- http://se-eng.com -- coreboot mailing list: coreboot@coreboot.org http://www.coreboot.org/mailman/listinfo/coreboot
[coreboot] [PATCH] workaround for "An unexpected error (805262864) occurred at line 1768 of d:\xpclient\base\boot\setup\arcdisp.c"
The attached patch works around a Windows XP or Server 2003 setup failure where an error message such as: "An unexpected error (805262864) occurred at line 1768 of d:\xpclient\base\boot\setup\arcdisp.c" The value 805262864 varies, and is the physical address, in decimal, of one of the ACPI tables. Tested on Persimmon. Others abuild tested only. Signed-off-by: Scott Duplichan Detailed explanation: The error message is displayed when a 1024 dword page table array used by setupldr runs out of space. This table is used for mapping various physical addresses, such as those of ACPI tables (a separate table identity maps the lower 16MB used by setupldr code and data). Setupldr only looks at ACPI tables (FACP) to determine make and model of the system. The make and model of the system is needed when setupldr scans the good/bad bios lists contained in txtsetup.sif. The good/bad bios lists are used to bypass installation of the ACPI enabled kernel on certain systems known to have ACPI problems. The code loop that scans the lists creates a new mapping each time it reads an ACPI table, and never frees mappings. The code uses FACP OEM ID to determine the system model. The code sequentially reads tables listed in the RSDT array until the FACP is found. Each read consumes one page table entry. If more that 4 tables precede the FACP in the RSDT array, the 1024 entry page table array will run out of space before the good/bad bios list processing completes. BIOS can work around this Windows XP/Server 2003 limitation by placing the FACP early in the RSDT array. Thanks, Scott xp-workaround.patch Description: Binary data -- coreboot mailing list: coreboot@coreboot.org http://www.coreboot.org/mailman/listinfo/coreboot
