All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arjan van de Ven <arjan@infradead.org>
To: Lukas Hejtmanek <xhejtman@ics.muni.cz>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>,
	Marcin Slusarz <marcin.slusarz@gmail.com>,
	linux-kernel@vger.kernel.org,
	Thomas Gleixner <tglx@linutronix.de>,
	torvalds@linux-foundation.org
Subject: Re: Bootup time regression from 2.6.27 to 2.6.28-rc3+
Date: Sun, 9 Nov 2008 12:28:35 -0800	[thread overview]
Message-ID: <20081109122835.10f410fa@infradead.org> (raw)
In-Reply-To: <20081109200918.GA4361@ics.muni.cz>

On Sun, 9 Nov 2008 21:09:18 +0100
Lukas Hejtmanek <xhejtman@ics.muni.cz> wrote:

> On Sun, Nov 09, 2008 at 02:24:10PM +0100, Rafael J. Wysocki wrote:
> > > > Do you have NO_HZ enabled?
> > > > (Cc'ing Thomas)
> > > 
> > > indeed, I have. Should I try it without NO_HZ?
> > 
> > Yes, please.
> 
> I tried it, it is not better. I/O operations on /dev/sda1 often
> require a key hit. It is AHCI driver.

just as a status on this guy:

1) we know what to remove to make it go away and go back to 2.6.27
status.
However we think it just papers over a bug elsewhere
2) Thomas did a lot of work and has a set of bugfixes to hrtimers and
related that fix a bunch of cases and MIGHT fix this one too (we
haven't been able to reproduce it but there's several reports out for
this "wait until hitting a key")

for me, the plan is that we need to get Thomas' fixes tested by someone
who can reproduce this very reliably. If they fix it, great.
If they don't, time is running out and we need to remove the feature
for 2.6.28 (that is 1 line of change), realizing that this just papers
over stuff and isn't a real fix, and get back to it for 2.6.29.



-- 
Arjan van de Ven 	Intel Open Source Technology Centre
For development, discussion and tips for power savings, 
visit http://www.lesswatts.org

  reply	other threads:[~2008-11-09 20:28 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-04 17:33 Bootup time regression from 2.6.27 to 2.6.28-rc3+ Lukas Hejtmanek
2008-11-09  0:06 ` Rafael J. Wysocki
2008-11-09  4:55   ` Arjan van de Ven
2008-11-09  8:56     ` Lukas Hejtmanek
2008-11-09 10:52       ` Marcin Slusarz
2008-11-09 11:33         ` Lukas Hejtmanek
2008-11-09 13:24           ` Rafael J. Wysocki
2008-11-09 20:09             ` Lukas Hejtmanek
2008-11-09 20:28               ` Arjan van de Ven [this message]
2008-11-09 20:34                 ` Lukas Hejtmanek
2008-11-09 21:24                   ` Arjan van de Ven
2008-11-09 21:38                     ` Lukas Hejtmanek
2008-11-09 21:43                     ` Lukas Hejtmanek
2008-11-09 21:57                       ` Thomas Gleixner
2008-11-10  8:12                         ` Lukas Hejtmanek
2008-11-10 12:16                         ` Lukas Hejtmanek
2008-11-09 21:56                     ` Thomas Gleixner
2008-11-09 22:46                       ` Bernhard Schmidt
2008-11-09 22:53                       ` Frans Pop
2008-11-14  1:45                       ` Frans Pop
2008-11-15 17:16                         ` Frans Pop
2008-11-15 18:04                           ` Arjan van de Ven
2008-11-16 19:27                         ` [2.6.28-rc5] TSC sync error and high hrtimer_start (was: Bootup time regression from 2.6.27 to 2.6.28-rc3+) Frans Pop
2008-11-17  2:18                           ` Frans Pop
2008-11-10 13:45                     ` Bootup time regression from 2.6.27 to 2.6.28-rc3+ Yves-Alexis Perez
2008-11-11 17:33                       ` Len Brown
2008-11-09 20:39                 ` Linus Torvalds
2008-11-09 20:48                   ` Arjan van de Ven
2008-11-09 14:20       ` Frans Pop
2008-11-09 15:14         ` Lukas Hejtmanek

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=20081109122835.10f410fa@infradead.org \
    --to=arjan@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcin.slusarz@gmail.com \
    --cc=rjw@sisk.pl \
    --cc=tglx@linutronix.de \
    --cc=torvalds@linux-foundation.org \
    --cc=xhejtman@ics.muni.cz \
    /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.