From: Arjan van de Ven <arjan@linux.intel.com>
To: Frans Pop <elendil@planet.nl>
Cc: linux-kernel@vger.kernel.org,
Yves-Alexis Perez <corsac@debian.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: Tue, 28 Oct 2008 20:32:39 -0700 [thread overview]
Message-ID: <4907D957.6040206@linux.intel.com> (raw)
In-Reply-To: <200810290153.23514.elendil@planet.nl>
Frans Pop wrote:
> On Tuesday 28 October 2008, Frans Pop wrote:
>> I'm seeing some very strange behavior with 2.6.28-rc2-95-g49fdf67 on my
>> HP 2510p notebook.
>>
>> During the boot there are several places where I need to hit a key for
>> the boot to continue. There are also some very long delays before the
>> next syslog message is displayed.
>> The boot does continue and regularly hitting a key helps (but does not
>> get rid of all delays), but it is a huge regression from 2.6.27.
>>
>> The delays seem to continue until file systems get mounted.
>>
>> As the delays start at the point my system asks for the passphrase to
>> unlock (LUKS) encrypted disks, I suspect it has to do with that.
>> Especially since hitting a key seems to "trigger" new disk activity.
>>
>> However, the delays happen _again_ during shutdown, which makes it
>> extra strange that the system does behave normally when logged in.
>>
>> During the first boot wireless networking failed. During the second
>> boot, wireless networking did come up (without any relevant changes).
>> This gave an interesting extra data point: with wireless the delays on
>> shutdown started later: after iwlagn gets disabled.
>
> I've bisected it to:
> 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
>
> The bisection was one of those annoying ones where you switch branches
> often and get a load of config changes. This means that I'm not 100% sure
> about it, especially as the behavior changed for the last few "bad"s:
> instead of endlessly repeated delays there would be only a few of them
> immediately after entering the LUKS passphrase.
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..
next prev parent reply other threads:[~2008-10-29 3:32 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 [this message]
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
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=4907D957.6040206@linux.intel.com \
--to=arjan@linux.intel.com \
--cc=corsac@debian.org \
--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.