From: Nico Erfurth <ne@erfurth.eu>
To: linux-crypto@vger.kernel.org
Subject: Padlock with VIA Nano still crashing
Date: Tue, 28 Jul 2009 10:26:54 +0200 [thread overview]
Message-ID: <4A6EB64E.3040209@erfurth.eu> (raw)
Hi,
I've tried to setup a fileserver with a Via Nano board (Jetway
NF77-N1G6) to use it's Padlock encryption engine. All works fine with
the software encryption, but when I try to use the Padlock driver I get
sporadic crashes while reading and writing on my encrypted device.
I can't provide the crashdump right now, because the machine itself is
not useable after the crash anymore. Whatever I try to do after the
kernel panic just results in another panic.
But I've compared the message with the sourcecode and it seems to point
to the "repz xcrypt-ecb" command used by aes_encrypt.
I've tried the latest cryptodev-2.6 and linux-2.6 (2.6.31-rc4) same
problem with both versions. (Which include fixes for the Via Nano)
Does anybody have an idea how I could get the crashdump so I can send it
to the list? If there is no other way I'll write it down next time.
Regards,
Nico
next reply other threads:[~2009-07-28 8:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-28 8:26 Nico Erfurth [this message]
2009-07-28 20:53 ` Padlock with VIA Nano still crashing Sebastian Andrzej Siewior
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=4A6EB64E.3040209@erfurth.eu \
--to=ne@erfurth.eu \
--cc=linux-crypto@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