From: Yves-Alexis Perez <corsac@debian.org>
To: Arjan van de Ven <arjan@linux.intel.com>
Cc: Frans Pop <elendil@planet.nl>,
linux-kernel@vger.kernel.org,
"Carlos R. Mafra" <crmafra2@gmail.com>,
Thomas Gleixner <tglx@linutronix.de>, Ingo Molnar <mingo@elte.hu>
Subject: Re: Long delays and keystrokes required - related to disk encryption?
Date: Wed, 29 Oct 2008 07:54:28 +0100 [thread overview]
Message-ID: <20081029065428.GA15581@corsac.net> (raw)
In-Reply-To: <4907D957.6040206@linux.intel.com>
On Tue, Oct 28, 2008 at 08:32:39PM -0700, Arjan van de Ven wrote:
> ok one easy thing to try, in the peek function (that this patch touches),
> just stick a "return" as first statement in.
> If that "fixes" it, we have a real issue with hrtimers, if not then something else is going on..
At first sight, it fixes it, yes. Tried on a recent git pull. I'll try
to rebuild it without the fix to see if the problem reappears or if it
was a side-effect from other change.
Cheers,
--
Yves-Alexis
next prev parent reply other threads:[~2008-10-29 6:56 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-28 16:44 Long delays and keystrokes required - related to disk encryption? 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 [this message]
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
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=20081029065428.GA15581@corsac.net \
--to=corsac@debian.org \
--cc=arjan@linux.intel.com \
--cc=crmafra2@gmail.com \
--cc=elendil@planet.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--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.