All of lore.kernel.org
 help / color / mirror / Atom feed
From: Borislav Petkov <bp@amd64.org>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Matthew Garrett <mjg59@srcf.ucam.org>,
	Manoj Iyer <manoj.iyer@canonical.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"Rafael J. Wysocki" <rjw@sisk.pl>,
	"Herrmann3, Andreas" <Andreas.Herrmann3@amd.com>
Subject: Re: [PATCH] Quirk to fix suspend/resume on Lenovo Edge 11,13,14,15
Date: Thu, 13 Jan 2011 20:28:25 +0100	[thread overview]
Message-ID: <20110113192825.GC30866@kryptos.osrc.amd.com> (raw)
In-Reply-To: <alpine.LFD.2.00.1101132012140.2678@localhost6.localdomain6>

On Thu, Jan 13, 2011 at 08:13:42PM +0100, Thomas Gleixner wrote:
> > Well, Andreas did boot with 'hpet=verbose' on an affected machine here
> > and did a suspend/resume and the hpet config registers looked ok before
> > suspend and after resume. It might be that the HPET is temporarily
> > "insane" while resume lasts but we don't have any hard facts confirming
> 
> And you have no explanation at all why applying the irq pin routing
> quirk makes HPETs temporal insanity go away magically :)

But after the HPET counter wraps around, the machine is alive again.
Which means that the IRQ0 pin2 override is only temporarily needed after
resume... Strange.

-- 
Regards/Gruss,
Boris.

Advanced Micro Devices GmbH
Einsteinring 24, 85609 Dornach
General Managers: Alberto Bozzo, Andrew Bowd
Registration: Dornach, Gemeinde Aschheim, Landkreis Muenchen
Registergericht Muenchen, HRB Nr. 43632

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

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-13 16:02 [PATCH 0/1] Quirk to fix suspend/resume on Lenovo Edge 11,13,14,15 Manoj Iyer
2011-01-13 16:02 ` [PATCH] " Manoj Iyer
2011-01-13 16:46   ` Matthew Garrett
2011-01-13 17:10     ` Thomas Gleixner
2011-01-13 17:22       ` Borislav Petkov
2011-01-13 17:33         ` Manoj Iyer
2011-01-13 17:55           ` Borislav Petkov
2011-01-13 18:11             ` Manoj Iyer
2011-01-13 18:30               ` Borislav Petkov
2011-01-13 18:51                 ` Thomas Gleixner
2011-01-13 18:58                   ` Matthew Garrett
2011-01-13 19:07                     ` Borislav Petkov
2011-01-13 19:13                       ` Thomas Gleixner
2011-01-13 19:28                         ` Borislav Petkov [this message]
2011-01-13 19:41                           ` Thomas Gleixner
2011-01-13 20:33                             ` Manoj Iyer
2011-01-13 21:12                               ` Manoj Iyer
2011-01-13 21:40                                 ` Thomas Gleixner
2011-01-13 21:48                                   ` Manoj Iyer
2011-01-13 22:40                                     ` Thomas Gleixner
2011-01-13 21:09                             ` Borislav Petkov
2011-01-13 21:30                               ` Thomas Gleixner
2011-01-13 21:48                                 ` Borislav Petkov
2011-01-13 22:55                                   ` Thomas Gleixner
2011-01-14 19:55                                     ` Manoj Iyer
2011-01-14 21:41                                       ` Borislav Petkov
2011-01-28 17:59                                       ` Andreas Herrmann
2011-01-31 16:44                                         ` Manoj Iyer
2011-01-31 17:54                                           ` Manoj Iyer
2011-01-13 19:11                     ` Thomas Gleixner
2011-01-13 18:57                 ` Manoj Iyer
2011-01-13 17:39       ` Matthew Garrett
     [not found]         ` <AANLkTimk_Y4Q_cxg1SJxZiTT2gT9ywr5UGmsqPqwmeCy@mail.gmail.com>
2011-01-13 17:56           ` Matthew Garrett

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=20110113192825.GC30866@kryptos.osrc.amd.com \
    --to=bp@amd64.org \
    --cc=Andreas.Herrmann3@amd.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=manoj.iyer@canonical.com \
    --cc=mjg59@srcf.ucam.org \
    --cc=rjw@sisk.pl \
    --cc=tglx@linutronix.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.