This entry in the DMI blacklist table is missing it's NO_MATCH
tags, which means the struct gets padded instead of filled with
the desired NO_MATCH data which is {255, NULL}
Usually not fatal it seems, but there have been numerous cases
in Red Hat bugzilla where this did get tripped up, and caused
an immediate reset on these boards. Not fun to track down.
Dave
Signed-off-by: Dave Jones <[email protected]>
--- linux-2.6.6/arch/i386/kernel/dmi_scan.c~ 2004-05-27 11:50:17.509303288 +0100
+++ linux-2.6.6/arch/i386/kernel/dmi_scan.c 2004-05-27 11:50:49.466445064 +0100
@@ -783,6 +783,7 @@
{ exploding_pnp_bios, "ASUS P4P800", { /* PnPBIOS GPF on boot */
MATCH(DMI_BOARD_VENDOR, "ASUSTeK Computer Inc."),
MATCH(DMI_BOARD_NAME, "P4P800"),
+ NO_MATCH, NO_MATCH
} },
/* Machines which have problems handling enabled local APICs */