Thanks for information, David. I'm closing this bugreport right now, please 
feel free to re-open it if you notice the same behaviour again (and of course 
feel free to add any additional information about it as well). Thanks!

regards,
-mika-

Strange, don't ask me why but it doesn't happen any more and I can't reproduce
it. Well, I keep my system up-to-date, maybe it has become fixed, no idea. So
sorry for all the trouble.

Any news here, azatoth?

thx && regards,
-mika-

could you please paste the kernel oops?
the kernel shouldn't oops just becase of a wrong pw.

a valied workaround would be to use pam-mount for home.

I use grml 1.0-1, so I also use the same versions as you.

Sorry, I really can't reproduce the problem here, though I'm using 2.6.22-grml. 
Can you please try upgrading the cryptsetup package and if that does not work 
yet try using linux-image-2.6.22-grml (available from grml-testing repository)?

% dpkg --list cryptsetup linux-image-2.6.22-grml
[...]
ii  cryptsetup                2:1.0.4+svn29-1+b1        configures encrypted 
block devices
ii  linux-image-2.6.22-grml   grml.01                   Linux kernel binary 
image for version 2.6.22-grml

I forgot to say that everything works fine when I enter the correct password.

After an installation of grml 1.0-1 I followed the instructions of the man page 
of grml2hd and made a crypted swap and a crypted home partition. Everything 
seems to work fine so far but when I get the instruction while booting to enter 
my passwort to unlock my home partition and I enter a wrong password the kernel 
gets panic. I even don't get the chance to enter it twice.

The man page also says that you have to edit /etc/runlevel.conf to adapt it but 
that's wrong, everything was already fine there.