mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mikael Pettersson <mikpe@it.uu.se>
To: Udo van den Heuvel <udovdh@xs4all.nl>
Cc: linux-kernel@vger.kernel.org
Subject: Re: crypt issue with 2.6.30/gcc 4.4.0?
Date: Sun, 14 Jun 2009 17:16:16 +0200	[thread overview]
Message-ID: <18997.5184.484019.744195@pilspetsen.it.uu.se> (raw)
In-Reply-To: <4A34FD06.2020204@xs4all.nl>

Udo van den Heuvel writes:
 > 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?

Instead of changing two variables at once (kernel version AND gcc version)
you keep one constant and vary the other.

IOW, rebuild 2.6.29.4 with gcc-4.4 and test.
Then rebuild 2.6.30 with gcc-4.3 or older and test.

  reply	other threads:[~2009-06-14 15:16 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-14 13:37 Udo van den Heuvel
2009-06-14 15:16 ` Mikael Pettersson [this message]
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=18997.5184.484019.744195@pilspetsen.it.uu.se \
    --to=mikpe@it.uu.se \
    --cc=linux-kernel@vger.kernel.org \
    --cc=udovdh@xs4all.nl \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®