Hi,
that Hardware of mine passed away recently, so I won't be able to track this
issue anymore. I suggest closing the bugreport, unless anybody else speaks up
about the same problem.
Regards
Carsten
Hi Ben,
On Friday 05 February 2016 16:54:59 Ben Hutchings wrote:
> On Fri, 2016-02-05 at 16:58 +0100, Carsten Wolff wrote:
> > At least, it does not fix the error
> > I'm seeing. The message stays the same, including the 32 byte it dumps.
>
> Then I'm out o
On Friday 05 February 2016 01:10:37 Ben Hutchings wrote:
> I found what seems to be a bug in the driver, but it was present in
> both 3.2 and 3.16. Please test whether the attached patch fixes this
> issue
Hum, the patch only fixes the decision, if and when the key is reset before an
operation,
Hi Ben,
thanks for the quick answer.
On Sunday 31 January 2016 23:37:56 Ben Hutchings wrote:
> That suggests a regression in the padlock-aes driver, although I don't
> see any functional changes there. As a workaround, you can blacklist
> it by adding "blacklist=padlock-aes" to the kernel comman
Package: src:linux
Version: 3.16.7-ckt20-1+deb8u3
Severity: normal
Hi,
I'm not at all sure I'm filing this against the right package. Maybe
cryptsetup, maybe linux, ...
After upgrading this system from wheezy to jessie, unlocking the cryptroot from
initrd with padlock-aes and padlock-sha loaded
:38:33 lb01 kernel: [71034.937051] [] ?
kernel_thread_helper+0x7/0x10
Aug 15 20:38:44 lb02 kernel: [73520.996050] IPVS: stopping backup sync thread
24426 ...
Aug 15 20:38:44 lb02 kernel: [73520.996806] IPVS: sync thread started: state =
MASTER, mcast_ifn = vlan0400, syncid = 22
--
Carsten Wol
6 matches
Mail list logo