[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87eid282pj.fsf@spindle.srvr.nix>
Date: Fri, 10 Sep 2010 08:42:00 +0100
From: Nix <nix@...eri.org.uk>
To: Artur Skawina <art.08.09@...il.com>
Cc: Thomas Gleixner <tglx@...utronix.de>,
Venkatesh Pallipadi <venki@...gle.com>,
Damien Wyart <damien.wyart@...e.fr>,
John Drescher <drescherjm@...il.com>,
linux-kernel@...r.kernel.org
Subject: Re: [BISECTED] 2.6.35.*: horrible (exponential? >linear) slowdown to unusability (HPET)
On 10 Sep 2010, Artur Skawina spake thusly:
> I'm seeing this too, except here it happens every couple of days of uptime,
> lasts for a few minutes, and then goes away. Which made bisecting a bit
> impractical... Thank you for doing it.
I just happened to be the lucky sod for whom it was consistently going
wrong. :)
> HW is similar; x64 and X58/82801JI/ICH10, tsc clocksrc.
> Did that printk trigger?
No.
(hm, odd.
spindle:~# cat /sys/devices/system/clocksource/clocksource0/current_clocksource
tsc
spindle:~# grep -i tsc /proc/timer_list
spindle:~# grep -i hpet /proc/timer_list
Clock Event Device: hpet
set_next_event: hpet_legacy_next_event
set_mode: hpet_legacy_set_mode
I suspect current_clocksource doesn't do what we think it does, or the
clocksource and 'clock event device' are not the same.)
--
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