From: Justin Piszcz <jpiszcz@lucidpixels.com>
To: "Pallipadi, Venkatesh" <venkatesh.pallipadi@intel.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
john stultz <johnstul@us.ibm.com>,
lkml <linux-kernel@vger.kernel.org>,
Arjan van de Ven <arjan@infradead.org>
Subject: RE: 2.6.31.4: WARNING: at arch/x86/kernel/hpet.c:390 hpet_next_event+0x70/0x80() [occurs when ACPI_PROCESSOR=y]
Date: Tue, 17 Nov 2009 06:45:31 -0500 (EST) [thread overview]
Message-ID: <alpine.DEB.2.00.0911170643430.25285@p34.internal.lan> (raw)
In-Reply-To: <alpine.DEB.2.00.0911140344430.29547@p34.internal.lan>
On Sat, 14 Nov 2009, Justin Piszcz wrote:
>
>
> On Fri, 13 Nov 2009, Pallipadi, Venkatesh wrote:
>
>> On Fri, 2009-11-13 at 10:43 -0800, Justin Piszcz wrote:
>>>
>>> On Fri, 13 Nov 2009, Pallipadi, Venkatesh wrote:
>>>
>>>> On Fri, 2009-11-13 at 01:38 -0800, Thomas Gleixner wrote:
>>>>> On Thu, 12 Nov 2009, Pallipadi, Venkatesh wrote:
>>>>>> Yes. Yes. This is a hardware errata. I have a patch to workaround this
>>>>>> and
>>>>>> waiting on the errata description to get published..
1. Do we have an ETA of when this will get published?
2. Is there a patch available for testing?
Another issue, have you tried rebooting any Linux kernel ~2.6.30+ on the
DP55KG? It hangs at reboot unless you specify reboot=a with various
distributions/live CDs.
Justin.
next prev parent reply other threads:[~2009-11-17 11:45 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-08 14:35 2.6.31.4: WARNING: at arch/x86/kernel/hpet.c:390 hpet_next_event+0x70/0x80() Justin Piszcz
2009-11-11 19:50 ` Dave Jones
2009-11-11 21:32 ` 2.6.31.4: WARNING: at arch/x86/kernel/hpet.c:390 hpet_next_event+0x70/0x80() [occurs when ACPI_PROCESSOR=y] Justin Piszcz
2009-11-12 16:26 ` Justin Piszcz
2009-11-12 16:33 ` Justin Piszcz
2009-11-12 23:39 ` Justin Piszcz
[not found] ` <1f1b08da0911121513l32d47b4x8b9722ad3440ceb6@mail.gmail.com>
[not found] ` <alpine.DEB.2.00.0911121824290.2852@p34.internal.lan>
2009-11-12 23:40 ` john stultz
2009-11-12 23:45 ` Justin Piszcz
2009-11-12 23:49 ` john stultz
2009-11-12 23:53 ` Justin Piszcz
2009-11-12 23:53 ` Thomas Gleixner
2009-11-12 23:56 ` Justin Piszcz
2009-11-13 0:18 ` Pallipadi, Venkatesh
2009-11-13 0:20 ` Justin Piszcz
2009-11-13 0:30 ` Pallipadi, Venkatesh
2009-11-13 9:38 ` Thomas Gleixner
2009-11-13 18:32 ` Pallipadi, Venkatesh
2009-11-13 18:43 ` Justin Piszcz
2009-11-14 1:12 ` Pallipadi, Venkatesh
2009-11-14 8:48 ` Justin Piszcz
2009-11-17 11:45 ` Justin Piszcz [this message]
2009-11-17 21:37 ` Pallipadi, Venkatesh
2009-11-17 22:53 ` Justin Piszcz
2009-11-19 22:08 ` Pallipadi, Venkatesh
2009-11-19 23:12 ` Justin Piszcz
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.DEB.2.00.0911170643430.25285@p34.internal.lan \
--to=jpiszcz@lucidpixels.com \
--cc=arjan@infradead.org \
--cc=johnstul@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=venkatesh.pallipadi@intel.com \
/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®