LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Yves-Alexis Perez <corsac@debian.org>
To: Pavel Machek <pavel@suse.cz>
Cc: Frans Pop <elendil@planet.nl>, linux-kernel@vger.kernel.org
Subject: Re: Long delays and keystrokes required - related to disk encryption?
Date: Fri, 31 Oct 2008 12:40:25 +0100 [thread overview]
Message-ID: <20081031114025.GB10383@corsac.net> (raw)
In-Reply-To: <20081031075705.GA32689@elf.ucw.cz>
On Fri, Oct 31, 2008 at 08:57:05AM +0100, Pavel Machek wrote:
> On Fri 2008-10-31 01:04:25, Frans Pop wrote:
> > On Thursday 30 October 2008, Pavel Machek wrote:
> > > Try "nohz=off highres=off"...
> >
> > Oh, I have no doubt that that could help. The point is though that I don't
> > think I should have to use such parameters.
> >
> > I think we've already established that disabling hires timers helps, so,
> > unless this will provide some additional tracing info to the developers,
> > I think I'll skip this suggestion.
> >
> > 2.6 28-rc2 is a regression against 2.6.27 because hires is broken. I don't
> > think I'll want to permanently add random boot parameters to work around
> > that regression.
>
> Well, you could probably narrow it down to "nohz=off", because I
> believe it is probably nohz and not highres that makes problems.
>
> Anyway, if this does not get fixed soon, you should cc rjw so this
> gets on the regression list.
It already is on the regression list, see:
http://bugzilla.kernel.org/show_bug.cgi?id=11826
http://bugzilla.kernel.org/show_bug.cgi?id=11893
>
> You can probably debug this with git bisect if no other ideas
> surface...
Bisect has already been done, the offending commit is:
commit dc4304f7deee29fcdf6a2b62f7146ea7f505fd42
Author: Arjan van de Ven <arjan@linux.intel.com>
Date: Mon Oct 13 10:32:15 2008 -0400
rangetimers: fix the bug reported by Ingo for real
And workarounding it with a return; early in the function worked.
But that's not really a solution.
Cheers,
--
Yves-Alexis
prev parent reply other threads:[~2008-10-31 11:40 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-28 16:44 Frans Pop
2008-10-28 17:11 ` Carlos R. Mafra
2008-10-28 21:52 ` Yves-Alexis Perez
2008-10-29 0:53 ` Frans Pop
2008-10-29 3:32 ` Arjan van de Ven
2008-10-29 6:54 ` Yves-Alexis Perez
2008-10-29 7:11 ` Yves-Alexis Perez
2008-11-03 7:23 ` Yves-Alexis Perez
2008-11-03 7:36 ` Yves-Alexis Perez
2008-11-05 2:03 ` Bernhard Schmidt
2008-11-05 15:13 ` Arjan van de Ven
2008-11-05 16:12 ` Bernhard Schmidt
2008-11-05 18:17 ` Yves-Alexis Perez
2008-11-05 20:41 ` Frans Pop
2008-11-06 15:41 ` Tony Vroon
2008-11-06 15:56 ` Yves-Alexis Perez
2008-10-29 10:43 ` Frans Pop
2008-10-30 19:50 ` Pavel Machek
2008-10-31 0:04 ` Frans Pop
2008-10-31 7:57 ` Pavel Machek
2008-10-31 11:40 ` Yves-Alexis Perez [this message]
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=20081031114025.GB10383@corsac.net \
--to=corsac@debian.org \
--cc=elendil@planet.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@suse.cz \
--subject='Re: Long delays and keystrokes required - related to disk encryption?' \
/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
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).