lkml.org 
[lkml]   [2010]   [Sep]   [14]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [BISECTED] 2.6.35.*: horrible (exponential? >linear) slowdown to unusability (HPET)
> On 14 Sep 2010, Thomas Gleixner said:
>> Another question. If you add hpet=verbose (or revert that commit) does
>> the printk_once in hpet_set_next_event() show up in dmesg ?
>>
>> "hpet: compare register read back failed."

Since adding back that extra read, the box here, which previously
was showing the symptoms every couple of days, has been ok; so i'm
now ~80% sure this change was indeed the cause. Nothing new in logs.

$ dmesg | grep -i hpet
ACPI: HPET 00000000bfee5dc0 00038 (v01 GBT GBTUACPI 42302E31 GBTU 00000098)
ACPI: HPET id: 0x8086a201 base: 0xfed00000
hpet clockevent registered
HPET: 4 timers in total, 0 timers will be used for per-cpu timer
hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0
hpet0: 4 comparators, 64-bit 14.318180 MHz counter
rtc0: alarms up to one month, 242 bytes nvram, hpet irqs
$

artur


\
 
 \ /
  Last update: 2010-09-15 00:25    [W:0.057 / U:0.048 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site