From: Borislav Petkov <bp@amd64.org>
To: Andrew Lutomirski <luto@mit.edu>
Cc: Clemens Ladisch <clemens@ladisch.de>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@elte.hu>, "H. Peter Anvin" <hpa@zytor.com>,
x86 <x86@kernel.org>
Subject: Re: HPET (?) related hangs and breakage in 2.6.35,36
Date: Tue, 9 Nov 2010 19:01:23 +0100 [thread overview]
Message-ID: <20101109180123.GB31121@aftab> (raw)
In-Reply-To: <AANLkTi=cUGGpkgWcbX=KMxzu+E=Toy_O+LeLoAFFUAsh@mail.gmail.com>
On Tue, Nov 09, 2010 at 12:44:48PM -0500, Andrew Lutomirski wrote:
> I may have just reproduced after a couple of days of uptime it in
> 2.6.36 with hpet=disable (in any case, the system hung and netconsole
> didn't work).
>
> I'm currently testing the hpet_min_tick stuff, backported to 2.6.36,
> with hpet on. Haven't had a problem yet, but I'll see what happens
> after a few hours. So far, it said:
>
> ACPI: HPET id: 0x8086a301 base: 0xfed00000 min tick: 128
This doesn't say what your BIOS has set it to originally. For that, do
hexdump -C /sys/firmware/acpi/tables/HPET
and check what does the u16 little endian value at offset 0x35 say.
--
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
next prev parent reply other threads:[~2010-11-09 18:02 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-09 13:46 Andrew Lutomirski
2010-11-09 15:20 ` Clemens Ladisch
2010-11-09 15:38 ` Borislav Petkov
2010-11-09 17:44 ` Andrew Lutomirski
2010-11-09 18:01 ` Borislav Petkov [this message]
2010-11-09 21:29 ` Andrew Lutomirski
2010-11-10 18:48 ` [FALSE ALARM] " Andrew Lutomirski
2010-11-10 18:50 ` Borislav Petkov
2010-11-10 19:02 ` Andrew Lutomirski
2010-11-10 20:52 ` Thomas Gleixner
2010-11-10 20:56 ` Andrew Lutomirski
2010-11-10 20:58 ` Thomas Gleixner
2010-11-11 11:06 ` Roedel, Joerg
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=20101109180123.GB31121@aftab \
--to=bp@amd64.org \
--cc=clemens@ladisch.de \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@mit.edu \
--cc=mingo@elte.hu \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=x86@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
Powered by JetHome