From: Thomas Gleixner <tglx@linutronix.de>
To: Borislav Petkov <bp@amd64.org>
Cc: Manoj Iyer <manoj.iyer@canonical.com>,
Matthew Garrett <mjg@redhat.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 19:51:49 +0100 (CET) [thread overview]
Message-ID: <alpine.LFD.2.00.1101131946560.2678@localhost6.localdomain6> (raw)
In-Reply-To: <20110113183025.GE2006@aftab>
On Thu, 13 Jan 2011, Borislav Petkov wrote:
> On Thu, Jan 13, 2011 at 01:11:48PM -0500, Manoj Iyer wrote:
> > Borislav,
> >
> > Please see attached lspci output.
>
> Thanks, that looks better. A stab in the dark:
>
> Can you boot your machine with "nohpet" and try a suspend/resume cycle
> to see whether that helps?
>
> If that works, can you then boot normally (i.e. no "nohpet" option on
> the command line) and wait ~5mins after resume to see whether your
> machine comes out of the hang after all (the idea here is to wait for
> the 32bit HPET counter to wrap around).
What's odd is that the machines actually boot. I would have expected
that they do not boot at all if the BIOS IRQ0 pin2 override is
ignored. But it seems that takes effect just when the machine does a
suspend/resume. Weird!
Can we please get a dmesg for a boot with an unpatched kernel and one
with the DMI quirks applied (or acpi_skip_timer_override on the kernel
command line) ?
Thanks,
tglx
next prev parent reply other threads:[~2011-01-13 18:52 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-13 16:02 [PATCH 0/1] " 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 [this message]
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
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=alpine.LFD.2.00.1101131946560.2678@localhost6.localdomain6 \
--to=tglx@linutronix.de \
--cc=Andreas.Herrmann3@amd.com \
--cc=bp@amd64.org \
--cc=linux-kernel@vger.kernel.org \
--cc=manoj.iyer@canonical.com \
--cc=mjg@redhat.com \
--cc=rjw@sisk.pl \
/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
all inboxes | Powered by JetHome®