From: john stultz <johnstul@us.ibm.com>
To: Priit Laes <plaes@plaes.org>,
Alexey Fisher <bug-track@fisher-privat.net>
Cc: linux-kernel <linux-kernel@vger.kernel.org>, tglx@linutronix.de
Subject: Re: [BISECTED/2.6.35+] Regression: Machine runs really slowly after commit f12a15be
Date: Mon, 09 Aug 2010 12:01:38 -0700 [thread overview]
Message-ID: <1281380498.2444.2.camel@localhost.localdomain> (raw)
In-Reply-To: <1281186941.23274.5.camel@chi>
On Sat, 2010-08-07 at 16:15 +0300, Priit Laes wrote:
> Following commit makes my Dell Latitude D610 machine (x86_32) run really-really slow...
>
> f12a15be63d1de9a35971f35f06b73088fa25c3a is the first bad commit
> commit f12a15be63d1de9a35971f35f06b73088fa25c3a
> Author: John Stultz <johnstul@us.ibm.com>
On Sat, 2010-08-07 at 23:04 +0200, Alexey Fisher wrote:
> Hallo John,
> i have regression after commit f12a15be6.
> With this patch my netbook (Asus Eeepc 1005) starting really slow. It
> looks like printk comes 1/min.
Hi Priit, Alexey,
Thanks so much for the testing and bisecting the issue down!
Could you both please provide the output of:
cat /sys/devices/system/clocksource/clocksource0/current_clocksource
cat /sys/devices/system/clocksource/clocksource0/available_clocksource
thanks
-john
next prev parent reply other threads:[~2010-08-09 19:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-07 13:15 [BISECTED/2.6.35+] Regression: Machine runs really slowly after commit f12a15be Priit Laes
2010-08-09 19:01 ` john stultz [this message]
2010-08-09 19:38 ` Alexey Fisher
2010-08-09 19:51 ` john stultz
2010-08-09 20:19 ` Alexey Fisher
2010-08-09 19:43 ` Priit Laes
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=1281380498.2444.2.camel@localhost.localdomain \
--to=johnstul@us.ibm.com \
--cc=bug-track@fisher-privat.net \
--cc=linux-kernel@vger.kernel.org \
--cc=plaes@plaes.org \
--cc=tglx@linutronix.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.