public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Elisey Shemyakin <elisey@shemyakin.me>
To: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] x86: Aspire One Happy2 reboots only with the kbd method
Date: Tue, 1 Jan 2013 13:16:31 +0000 (UTC)	[thread overview]
Message-ID: <loom.20130101T120312-589@post.gmane.org> (raw)
In-Reply-To: 4FE39FC5.8060303@zytor.com

H. Peter Anvin <hpa <at> zytor.com> writes:

> 
> On 06/21/2012 03:22 PM, Uros Vampl wrote:
> > 
> > I advised the Arch user to join this discussion and provide the 
> > requested info. I immediately went for kbd as the solution because 
> > that's exactly what I need for my own Aspire One - that AOA110 quirk 
> > that's visible in the context of this patch. I figured it's a pattern, 
> > Aspire One machines quirky in the same way.
> > 
> 
> Probably, but we'd like to figure out what is going on.
> 
> 	-hpa
>
 
Hi. I got here from this forum https://bbs.archlinux.org/viewtopic.php?id=143716
 with the same issue on the same device.

Here is FACP table from acpidump output:

FACP @ 0x7f5fd000
  0000: 46 41 43 50 f4 00 00 00 04 4c 41 43 52 53 59 53  FACP.....LACRSYS
  0010: 41 43 52 50 52 44 43 54 01 00 00 00 31 30 32 35  ACRPRDCT....1025
  0020: 00 00 04 00 00 30 58 7f 00 10 5f 7f 00 02 09 00  .....0X..._.....
  0030: b2 00 00 00 a0 a1 00 80 00 04 00 00 00 00 00 00  ................
  0040: 04 04 00 00 00 00 00 00 20 04 00 00 08 04 00 00  ........ .......
  0050: 28 04 00 00 00 00 00 00 04 02 01 04 08 00 00 85  (...............
  0060: 65 00 e9 03 00 00 00 00 01 03 0d 00 00 03 00 00  e...............
  0070: a5 84 00 00 01 08 00 01 b2 00 00 00 00 00 00 00  ................
  0080: fb 00 00 00 00 30 58 7f 00 00 00 00 00 10 5f 7f  .....0X......._.
  0090: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
  00a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
  00b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
  00c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
  00d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
  00e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
  00f0: 00 00 00 00

I have tried to reboot with different kernel parameters.
Worked: kbd, efi, bios
Not worked: acpi, triple, pci

So, this patch works for me:

--- a/arch/x86/kernel/reboot.c
+++ b/arch/x86/kernel/reboot.c
@@ -447,6 +447,14 @@ 
 			DMI_MATCH(DMI_PRODUCT_NAME, "Precision M6600"),
 		},
 	},
+	{	/* Handle reboot issue on the Acer Aspire One Happy2. */
+		.callback = set_kbd_reboot,
+		.ident = "Acer Aspire One Happy2",
+		.matches = {
+			DMI_MATCH(DMI_SYS_VENDOR, "Acer"),
+			DMI_MATCH(DMI_PRODUCT_NAME, "AOHAPPY2"),
+		},
+	},
 	{ }
 };



      reply	other threads:[~2013-01-01 13:19 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-21 13:32 [PATCH] x86: Aspire One Happy2 reboots only with the kbd method Uros Vampl
2012-06-21 14:29 ` Don Zickus
2012-06-21 14:40   ` H. Peter Anvin
2012-06-21 22:22     ` Uros Vampl
2012-06-21 22:27       ` H. Peter Anvin
2013-01-01 13:16         ` Elisey Shemyakin [this message]

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=loom.20130101T120312-589@post.gmane.org \
    --to=elisey@shemyakin.me \
    --cc=linux-kernel@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