From: Udo van den Heuvel <udovdh@xs4all.nl>
To: linux-kernel@vger.kernel.org
Subject: crypt issue with 2.6.30/gcc 4.4.0?
Date: Sun, 14 Jun 2009 15:37:10 +0200 [thread overview]
Message-ID: <4A34FD06.2020204@xs4all.nl> (raw)
Hello,
I am having trouble decrypting my dm-crypted disks with 2.6.30. 2.6.29.4
works fine with the same encrypted disks.
I've been upgrading to Fedora 11 in the past few days so now GCC 4.4.0
is the compiler, that may (also) be a factor.
On 2.6.92.4 I see the encryption password prompt being buried by a lot
of USB-messages from connected gear. I can 'blindly' type my password
and asterisks appear for each letter. At the end of the password I press
Enter; a complaint about the partition table for md1 is displayed and
booting continues.
With 2.6.30 I see the Password prompt being repeated, after all the USB
messages, as soon as I press the first letter of the password. Each time
the password is entered it is not accepted and a new Password: prompt is
printed up to a total of three tries.
For all of these boots into 2.6.29.4 or 2.6.30 the userland etc is the
same (Fedora 11), it is just that 2.6.29.4 was built while running
Fedora 10 and 2.6.30 is now built with the tools in 2.6.30.
I did boot into 2.6.30 (built while running Fedora 10) successfully
once, right after the upgrade to Fedora 11. Later I made small changes
to the kernel config and rebuilt the kernel and this made the encryption
password fail. A `make clean` and rebuild does not fix the issue
How can I find out what's the cause for the password issue?
Kind regards,
Udo
next reply other threads:[~2009-06-14 13:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-14 13:37 Udo van den Heuvel [this message]
2009-06-14 15:16 ` crypt issue with 2.6.30/gcc 4.4.0? Mikael Pettersson
2009-06-14 15:22 ` Udo van den Heuvel
2009-06-14 15:39 ` Mikael Pettersson
2009-06-14 15:36 ` Udo van den Heuvel
2009-06-14 15:54 ` Milan Broz
2009-06-14 16:10 ` Udo van den Heuvel
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=4A34FD06.2020204@xs4all.nl \
--to=udovdh@xs4all.nl \
--cc=linux-kernel@vger.kernel.org \
/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.