[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20100526120236.4a849b5b.randy.dunlap@oracle.com>
Date: Wed, 26 May 2010 12:02:36 -0700
From: Randy Dunlap <randy.dunlap@...cle.com>
To: Udo van den Heuvel <udovdh@...all.nl>
Cc: linux-kernel@...r.kernel.org
Subject: Re: hpet timers gone?
On Mon, 24 May 2010 12:19:47 +0200 Udo van den Heuvel wrote:
> Hello,
>
> What has happened between 2.6.30.9 and 2.6.32.8 with regard to hpet timers?
>
> dmesg output from 2.6.30.9 does show activity but 2.6.32.8 and beyond don't.
> Also /proc/timer_list doesn't show hpet anymore. Also on 2.6.34 no hpet
> in timer_list.
>
> relevant .config:
> CONFIG_HPET_TIMER=y
> CONFIG_HPET_EMULATE_RTC=y
> CONFIG_HPET=y
> CONFIG_HPET_MMAP=y
Same here.
> And I have hpet=force on the kernel commandline for this VIA Epia
> LT10000 board.
>
> Any ideas?
On x86 peecee:
$ uname -a
Linux chimera.site 2.6.34 #2 SMP Tue May 18 10:52:27 PDT 2010 x86_64 x86_64 x86_64 GNU/Linux
$ grep hpet /proc/timer_list
Clock Event Device: hpet
set_next_event: hpet_legacy_next_event
set_mode: hpet_legacy_set_mode
$ dmesg | grep -i hpet
[ 0.000000] ACPI: HPET 00000000cf6f3000 00038 (v01 GATEWA SYSTEM 0000017E MSFT 01000013)
[ 0.000000] ACPI: HPET id: 0x8086a201 base: 0xfed00000
[ 0.000000] hpet clockevent registered
[ 0.000000] TSC: PIT calibration matches HPET. 1 loops
[ 0.771604] HPET: 3 timers in total, 0 timers will be used for per-cpu timer
[ 0.771604] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0
[ 0.771604] hpet0: 3 comparators, 64-bit 14.318180 MHz counter
What does dmesg show on your machine?
---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
--
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