linux-acpi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Angus Turnbull <angus@twinhelix.com>
To: linux-acpi@vger.kernel.org
Cc: lenb@kernel.org
Subject: [PATCH] Force acpi_skip_timer_override for Gigabyte GA-MA78GPM-UD2H
Date: Wed, 21 Dec 2011 18:34:14 +1300	[thread overview]
Message-ID: <1324445654.4784.8.camel@nirvana> (raw)

Some Gigabyte motherboards from the SB700 generation have an issue
where they will not boot or suspend/resume without
"acpi_skip_timer_override" on the kernel command line. I have a
GA-MA78GPM-UD2H (AM2+ socket) and the below patch allows it to boot
successfully by adding it to the quirks list (the AMD bug detection in
early_quirks.c isn't enabling acpi_skip_timer_override automatically).

https://lkml.org/lkml/2011/3/31/195 covered a similar issue.

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/658955 is a bug
report with my system information.

Also posted at https://lkml.org/lkml/2011/11/22/511

Reported-and-tested-by: <angus <at> twinhelix.com>
cc: Len Brown <lenb <at> kernel.org>



diff -upr a/arch/x86/kernel/acpi/boot.c b/arch/x86/kernel/acpi/boot.c
--- a/arch/x86/kernel/acpi/boot.c	
+++ b/arch/x86/kernel/acpi/boot.c
@@ -1466,6 +1466,20 @@ static struct dmi_system_id __initdata a
 		     DMI_MATCH(DMI_PRODUCT_NAME, "HP Compaq 6715b"),
 		     },
 	 },
+	/*
+	 * Buggy Gigabyte ACPI on SB700 boards, will not boot or resume
+	 * reliably without acpi_skip_timer_override (last stable BIOS).
+	 * Affects multiple boards of this generation.
+	 */
+	{
+	 .callback = dmi_ignore_irq0_timer_override,
+	 .ident = "Gigabyte GA-MA78GPM-UD2H",
+	 .matches = {
+		     DMI_MATCH(DMI_SYS_VENDOR,
+			"Gigabyte Technology Co., Ltd."),
+		     DMI_MATCH(DMI_PRODUCT_NAME, "GA-MA78GPM-UD2H"),
+		     },
+	 },
 	{}
 };


                 reply	other threads:[~2011-12-21  5:43 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1324445654.4784.8.camel@nirvana \
    --to=angus@twinhelix.com \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).