linux-kernel - Re: Long delays and keystrokes required

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 28 Oct 2008 18:11:37 +0100
From:	"Carlos R. Mafra" <crmafra2@...il.com>
To:	Frans Pop <elendil@...net.nl>
Cc:	linux-kernel@...r.kernel.org, akpm@...ux-foundation.org
Subject: Re: Long delays and keystrokes required - related to disk
	encryption?

On Tue 28.Oct'08 at 17:44:51 +0100, Frans Pop wrote:
> I'm seeing some very strange behavior with 2.6.28-rc2-95-g49fdf67 on my
> HP 2510p notebook.

Me too on my Vaio FZ240E.

> 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.

I have to press some key during boot too. But it does not happen at every boot.
And I've never seen this behaviour before 2.6.28-rc

> 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.

I don't have any encrypted disks tough.

I think I remember one email by Andrew Morton about this keystroke to
continue to boot issue, so I Cc:-ed him.


> 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.
> 
> Any ideas?
> 
> Cheers,
> FJP
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/