[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.LFD.2.00.1101132006190.2678@localhost6.localdomain6>
Date: Thu, 13 Jan 2011 20:11:41 +0100 (CET)
From: Thomas Gleixner <tglx@...utronix.de>
To: Matthew Garrett <mjg59@...f.ucam.org>
cc: Borislav Petkov <bp@...64.org>,
Manoj Iyer <manoj.iyer@...onical.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"Rafael J. Wysocki" <rjw@...k.pl>,
"Herrmann3, Andreas" <Andreas.Herrmann3@....com>
Subject: Re: [PATCH] Quirk to fix suspend/resume on Lenovo Edge 11,13,14,15
On Thu, 13 Jan 2011, Matthew Garrett wrote:
> On Thu, Jan 13, 2011 at 07:51:49PM +0100, Thomas Gleixner wrote:
>
> > 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!
>
> The only thing that springs to mind is some BIOS code making incorrect
> assumptions about timer setup when we trap into it. Is reprogramming the
> timer back to the boot state over suspend plausible? If so, that'd
> probably be a more general fix.
Well, it's even more odd that it comes back after 5 minutes with the
HPET enabled. How the hell is this related to the irq pin routing?
I'm really curious to see what differences we get for the irq pin
routing with and w/o the dmi quirk.
Thanks,
tglx
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists