Bug #257

ASUS P5QPL-AM w/ Coreboot v. Windows 10: STOP 0xa5 BSOD

Added by Mr. Z. 7 months ago. Updated 7 months ago.

Status:ResolvedStart date:03/20/2020
Priority:NormalDue date:
Assignee:-% Done:

0%

Category:-
Target version:-

Description

Hi There :)

I've Been Fiddling Quite a Bit With This Issue, However, None of The Paths I Took Led Me To a Solution. Help, Please ? :)

The Vendor F/W Enables a Windows 10 x64 1909 OS To Boot,
However It's NO Usable For My Purpose - As It Has NO Support for Booting from PCIe/NVMe Drives & I Really Wish To Keep It Simple (This System Is Meant To Be Donated To Those Who Can't Afford Buying a Computer, So No Wizard Should Be Required For a Future OS Re-Installation...).

Coreboot F/W, OTOH, Only Enables a Windows OS - Both Windows 7 x64 pre-SP2 & Windows 10 x64 1909 - To Produce a "STOP 0x000000A5" BSOD on Boot ( Parameter1 = 0x0000000D ; See: https://support.microsoft.com/en-us/help/314830/stop-error-code-0x000000a5-error-when-you-are-installing-windows-xp ).

*

Hardware Specs. -

Mainboard: ASUS P5QPL-AM
CPU: Intel Xeon L5420
RAM: 4GB (2x2GB)
SSD: Kingston A2000 250GB PCIe/NVMe (on PCIe*16/PEG Port)

*

Firmware Specs. -

Vendor: 0416
Coreboot: 4.10-455-g44449192ab from 27/08/2019 & 4.11-1706-g34473ea6c9 from 20/03/2020

*

I Also Have The Means To Externally Re-Flash This Mainboard F/W IC - If Needed.

ASUS-P5QPL_AM-ACPI-VENDOR.zip - Vendor F/W 0416 - ACPI Tables (16.4 KB) Mr. Z., 03/20/2020 10:52 PM

IMG_20200320_054340_HDR-A.jpg - Windows 7 x64 pre-SP2 - BSOD on Boot (628 KB) Mr. Z., 03/20/2020 10:53 PM

lspci-VENDOR.out - Vendor F/W - lspci -nnnvvv - output (17.9 KB) Mr. Z., 03/20/2020 10:54 PM

lspci-coreboot-20200320-3-non-working.out - Coreboot F/W 4.11-1706-g34473ea6c9 - lspci -nnnvvv - output (21.9 KB) Mr. Z., 03/20/2020 10:55 PM

defconfig.ASUS-P5QPL_AM.debug - Coreboot - defconfig (668 Bytes) Mr. Z., 03/21/2020 12:29 PM

console.log Magnifier - Coreboot - console log (Windows 7 x64 pre-SP2 - BSOD on Boot) (256 KB) Mr. Z., 03/21/2020 12:29 PM

coreboot-ASUS_P5QPL-AM_20200321-1-debug.dmesg.out - Coreboot - linux 5.3.5 - dmesg output (50.6 KB) Mr. Z., 03/21/2020 12:30 PM

coreboot-ASUS_P5QPL-AM_20200321-1-debug.fwts-result.zip - Coreboot - fwts V20.01.00 - results (77.3 KB) Mr. Z., 03/21/2020 12:31 PM

defconfig.GIGABYTE_GA-G41M-ES2L.debug - Coreboot - defconfig (537 Bytes) Mr. Z., 03/21/2020 01:40 PM

coreboot-GIGABYTE_GA-G41M-ES2L-20200321_1_debug.console.log Magnifier - Coreboot - console log (Windows 10 x64 1909 - Successful Boot) (256 KB) Mr. Z., 03/21/2020 01:41 PM

coreboot-GIGABYTE-GA_G41M_ES2L_20200321-1-debug.dmesg.out - Coreboot - linux 5.3.5 - dmesg output (52 KB) Mr. Z., 03/21/2020 01:47 PM

fwts-result.GIGABYTE-GA_G41M_ES2L.zip - Coreboot - fwts V20.01.00 - results (74.9 KB) Mr. Z., 03/21/2020 01:48 PM

coreboot-ASUS_P5QPL-AM_20200321-1-debug.seabios_debug_8.console.log Magnifier - Coreboot - console log (Windows 7 x64 pre-SP2 - BSOD on Boot) (256 KB) Mr. Z., 03/21/2020 04:39 PM

IMG_20200321_174957_HDR-A.jpg - Windows 7 x64 pre-SP2 - BSOD on Boot (561 KB) Mr. Z., 03/21/2020 04:47 PM

.seabiosconfig.defconfig.debug - SeaBIOS - make savedefconfig (157 Bytes) Mr. Z., 03/21/2020 04:48 PM

IMG_20200322_031105_HDR-A.jpg - Windows 7 x64 pre-SP2 - BSOD on Boot (w/ SIO "_PS3" Patch Applied) (423 KB) Mr. Z., 03/22/2020 01:18 AM

Untitled.jpg - It Boots ! :) (215 KB) Mr. Z., 03/22/2020 02:57 AM

board_status.asus-p5qpl_am.tar.gz - Board Status - Asus P5QPL-AM Mainboard - Coreboot 4.11-1737-g7e57965aac (7.19 KB) Mr. Z., 03/22/2020 06:37 PM

History

#1 Updated by Mr. Z. 7 months ago

Also, FWIW, On a Very Similiar Mainboard - Gigabyte GA-G41M-ES2L ( w/ The Same Chipset (Intel G41 + ICH7) ), Coreboot F/W ( Coreboot 4.10-455-g44449192ab from 27/08/2019 ), Does Enable a Windows 10 x64 1909 OS To Boot.

#2 Updated by Paul Menzel 7 months ago

Please try to transcribe the full error next time – I removed some zeros from the parameters.

0xD, 0xFFFFFA8004753360, 0x000000003353505F,0x0

Here is the error description.

(0x0000000D, Parameter2, Parameter3, Parameter4):

There are many objects that must be defined in the ACPI namespace, and one or more of these was not found. This error generally occurs if either the _HID or _ADR object is missing. An _ADR is used to define the address of a device on its parent bus. The _ADR is a static address that defines slot numbers for devices that reside on any number of bus types, including EISA, floppy, IDE controller, IDE channel, PCI, PCMCIA, and CardBus. The _HID contains objects that supply the operating system with Plug and Play hardware ID for a device. Technically, these objects are optional, but they absolutely must be present to describe any device that is enumerated by an ACPI driver.

Please do the following:

  1. Please attach defconfig created by make savedefconfig.
  2. Please attach the coreboot logs, for example retrieved by cbmem -1 or from the serial console.
  3. Please start GNU/Linux (some latest version), and attach the Linux kernel console.
  4. In GNU/Linux, please install FWTS (https://wiki.ubuntu.com/FirmwareTestSuite), and run it, and look out for errors.

PS: Unrelated, it’d be nice if you uploaded the Linux logs to the board status repository. See util/board_status/README.

#3 Updated by Mr. Z. 7 months ago

Dear Paul, 1st & Foremost, I'd Like To Thank You For Taking The Time To Look Into This Issue: a Working Solution Will Enable Me To Release This System, That I Worked Tirelessly To Bring Together, To Some Underprivileged K-12 People :)

The Additional Info. Requested Is Attached (Lacking a USB<>RS-232 Adapter On Hand, I Opted To Use Coreboot's SPI Flash Based Console Logging).

#4 Updated by Mr. Z. 7 months ago

FWIW, Here's Also The Same Info. - from The Aforementioned Other Mainboard: Gigabyte GA-G41M-ES2L ( w/ Coreboot 4.11-1728-g96cf680c3d from 21/03/2020 ), On Which Windows 10 x64 1909 Successfully Boots.

#5 Updated by Mr. Z. 7 months ago

[ w.r.t. Mainboard: ASUS P5QPL-AM ]

Updated Coreboot Console Log: SeaBIOS Now Built w/ CONFIG_DEBUG_LEVEL=8 (Earlier It Was Set To '1').

Updated Windows 7 x64 BSoD Details: Stop Error Code=0xA5 (as Before), Parameter1=0xD, Parameter2=0xFFFFFA8004815A00, Parameter3=0x000000003353505F, Parameter4=0x0 .

#6 Updated by Nico Huber 7 months ago

Parameter3 0x3353505F is ASCII and translates to "_PS3". That's a power-state function which seems to be missing for the Super-I/O chip (which is one of the major differences between these boards).

Please try this patch, maybe we are lucky:
https://review.coreboot.org/c/coreboot/+/39746

#7 Updated by Mr. Z. 7 months ago

Dear Nico, Y'all Have No Idea How Much I Appreciate Your Kind Willingness To Assist Me Bringing a Good Working Computer To One In Need ! :)

& As Per The Proposed Patch, It Resulted In The Same BSoD on Boot, Only With Parameter2=0xFFFFFA8004815A90 .

#8 Updated by Mr. Z. 7 months ago

Dear Nico, It Was, Actually, a Pointer In The Right Direction:

Replacing The File 'src/mainboard/asus/p5qpl-am/acpi/superio.asl' with a Dummy (Merely an Empty File), Did The Trick - Finally ! :)

I'm Currently Still Able & Willing To Test a (Patched) ACPI SuperIO Block, If You're Willing To Try Along.

#9 Updated by Nico Huber 7 months ago

I was too tired last night to grep properly, there were many more occurences of the same problem. I've updated the patch, hopefully caught all cases now.

#10 Updated by Mr. Z. 7 months ago

Patch Rev. # 3 Tested & Working - Both on OS Setup & an Installed OS ! You're Like Magicians: a Major Thank You ! :)

#11 Updated by Nico Huber 7 months ago

  • Status changed from New to Resolved

#12 Updated by Mr. Z. 7 months ago

[For The Board Status Repository: Asus P5QPL-AM Mainboard w/ Coreboot 4.11-1737-g7e57965aac ]

#13 Updated by Paul Menzel 7 months ago

Great that Nico was able to come up with a fix so quickly.

In the board status archive, I saw, that you select the unneeded DRIVERS_PS2_KEYBOARD=y in coreboot. GRUB, SeaBIOS and TianoCore have their own drivers for that, so you do not need that.

Additionally, the archive misses the logs from coreboot and Linux. If the fix is in the master branch, it’d be great if you could do another run of board_status.sh.

Also available in: Atom PDF