[PATCH] workaround for "An unexpected error (805262864) occurred at line 1768 of d:\xpclient\base\boot\setup\arcdisp.c"

[Scott Duplichan]

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

[PATCH] workaround for "An unexpected error (805262864) occurred at line 1768 of d:\xpclient\base\boot\setup\arcdisp.c"

[Marc Jones]

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

[PATCH] workaround for "An unexpected error (805262864) occurred at line 1768 of d:\xpclient\base\boot\setup\arcdisp.c"

[Vikram Narayanan]

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

[PATCH] workaround for "An unexpected error (805262864) occurred at line 1768 of d:\xpclient\base\boot\setup\arcdisp.c"

[Scott Duplichan]

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

unifying `acpi_tables.c` (was: [PATCH] workaround for "An unexpected error (805262864) occurred at line 1768 of d:\xpclient\base\boot\setup\arcdisp.c")

[Paul Menzel]

Dear Scott and coreboot folks,

Am Mittwoch, den 18.05.2011, 01:40 -0500 schrieb Scott Duplichan:

[…]

looking at the change
> Index: src/mainboard/amd/bimini_fam10/acpi_tables.c
>
> --- src/mainboard/amd/bimini_fam10/acpi_tables.c        (revision 6599)
> +++ src/mainboard/amd/bimini_fam10/acpi_tables.c        (working copy)
> @@ -127,6 +127,31 @@
>         acpi_write_rsdp(rsdp, rsdt, NULL);
>         acpi_write_rsdt(rsdt);
>   /* DSDT */
>   current   = ( current + 0x07) & -0x08;
>   printk(BIOS_DEBUG, "ACPI:    * DSDT at %lx\n", current);
>   dsdt = (acpi_header_t *)current; // it will used by fadt
>   memcpy(dsdt, &AmlCode, sizeof(acpi_header_t));
>   current += dsdt->length;
>   memcpy(dsdt, &AmlCode, dsdt->length);
>   printk(BIOS_DEBUG, "ACPI:    * DSDT @ %p Length %x\n",dsdt,dsdt->length);
>   /* FACS */ // it needs 64 bit alignment
>   current   = ( current + 0x07) & -0x08;
>   printk(BIOS_DEBUG, "ACPI:       * FACS at %lx\n", current);
>   facs = (acpi_facs_t *) current; // it will be used by fadt
>   current += sizeof(acpi_facs_t);
>   acpi_create_facs(facs);
>   /* FADT */
>   current   = ( current + 0x07) & -0x08;
>   printk(BIOS_DEBUG, "ACPI:    * FADT at %lx\n", current);
>   fadt = (acpi_fadt_t *) current;
>   current += sizeof(acpi_fadt_t);
>   acpi_create_fadt(fadt, facs, dsdt);
>   acpi_add_table(rsdp, fadt);

[…]

the contents seems to very similar. Besides some comments even
identical.

Can `acpi_tables.c` be shared between certain families or even all new
boards?

If yes, maybe that could be put on a todo list.

Thanks,

Paul

unifying `acpi_tables.c`

[Peter Stuge]

Paul Menzel wrote:
> Can `acpi_tables.c` be shared between certain families or even all
> new boards?
>
> If yes, maybe that could be put on a todo list.

Yeah, I ranted about this a bit on IRC. Will take a look in Prague.

//Peter

unifying `acpi_tables.c`

[Stefan Reinauer]

On 5/18/11 3:21 PM, Peter Stuge wrote:
> Paul Menzel wrote:
> > Can `acpi_tables.c` be shared between certain families or even all
> > new boards?
> >
> > If yes, maybe that could be put on a todo list.
>
> Yeah, I ranted about this a bit on IRC. Will take a look in Prague.

I read a nice quote today:

"Why rant when you can also send a patch? "

Thanks for looking into this. :-)

unifying `acpi_tables.c`

[Peter Stuge]

Stefan Reinauer wrote:
> "Why rant when you can also send a patch? "

Because design is also important, not only implementation.

(Matter at hand requires no great feat of design. If someone else
sends a patch before me I will ack with a smile. :)

//Peter