Home Home > GIT Browse
summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorDave Jones <davej@redhat.com>2004-06-06 01:04:20 -0700
committerLinus Torvalds <torvalds@ppc970.osdl.org>2004-06-06 01:04:20 -0700
commitfddf7361101b2c61857ddf81e9ce0fc1c47e05af (patch)
treed915cf612c216b7772397e6c0279e7c89de05499
parent62b748c1ad5014fdbf9952b0fc2f64c1b4fdec7e (diff)
[PATCH] Fix missing padding in DMI table.
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. Signed-off-by: Dave Jones <davej@redhat.com> Signed-off-by: Linus Torvalds <torvalds@osdl.org>
-rw-r--r--arch/i386/kernel/dmi_scan.c1
1 files changed, 1 insertions, 0 deletions
diff --git a/arch/i386/kernel/dmi_scan.c b/arch/i386/kernel/dmi_scan.c
index 6c20ebe9934f..d9c97dae4a41 100644
--- a/arch/i386/kernel/dmi_scan.c
+++ b/arch/i386/kernel/dmi_scan.c
@@ -783,6 +783,7 @@ static __initdata struct dmi_blacklist dmi_blacklist[]={
{ 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 */