From: MA <admin@sms13.de>
To: linux-kernel@vger.kernel.org
Subject: kernel problems, crc32c
Date: Fri, 30 Jul 2004 04:03:21 +0200 [thread overview]
Message-ID: <1623453663.20040730040321@sms13.de> (raw)
Hello
Not sure if this is the correct place to ask, I compiled my own
kernel, nothing fancy, mostly default stuff + some additional device
drivers but after trying to load the kernel I end up with the
following error
Failed to load transform for crc32c
Testing hmac_md5
Test 1:
9294727a3638bb1c13f48ef8158bfc9d
Pass
Test 2:
750c783e6ab0b503eaa86e310a5db738
Pass
Test 3:
56be34521d144c88dbb8c733f0e8b3f6
Pass
Test 4:
697eaf0aca3a3aea3a75164746ffaa79
Pass
Test 5:
56461ef2342edc00f9bab995690efd4c
Pass
Test 6:
6b1ab7fe4db7bf8f0b62ebce61b9d0cd
Pass
Test 7:
6f630fad67cda0ee1fb1f562db63aa53e
Pass
AT THIS POINT IT HANGS
This is redhat enterprise 3.0, I was trying a couple 2.6.X serie
kernels and the error was the same each time, I was also trying to
exlcude crc32 options from kernel but it didnt help, I was not able to
find the resolution on google, so here I am asking for help, thanks
--
Sincerely MA
next reply other threads:[~2004-07-30 2:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-30 2:03 MA [this message]
2004-07-30 5:08 ` kernel problems, crc32c James Morris
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=1623453663.20040730040321@sms13.de \
--to=admin@sms13.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox