Bug#1113996: linux-image-amd64: self-tests for sha256 using sha256-padlock-nano failed
Control: tags -1 + upstream moreinfo
Control: forwarded -1 https://lore.kernel.org/lkml/20250611101750.6839-1-AlanSong-oc@zhaoxin.com/
On Fri, Sep 05, 2025 at 01:09:29PM +0800, Larry Wei wrote:
> Package: linux-image-amd64
> Version: 6.16.3-1
> Severity: normal
> X-Debbugs-Cc: debian-amd64@lists.debian.org
> User: debian-amd64@lists.debian.org
> Usertags: amd64
>
> Dear Maintainer,
>
> When my laptop was turned on, some warning messages about `crypto/testmgr.c`
> appeared, and I remember these warning messages also appeared when I compiled
> the kernel myself. These pieces of information are roughly as follows:
> ......
> [ 6.898953] WARNING: CPU: 6 PID: 753 at crypto/testmgr.c:5816
> alg_test.cold+0x37/0xaa
> [ 6.898981] Modules linked in: padlock_sha btintel
> [ 6.898985] alg: self-tests for sha256 using sha256-padlock-nano failed
> (rc=-22)
> [ 6.898987] libarc4 padlock_aes
> [ 6.898990] ------------[ cut here ]------------
> [ 6.898991] btbcm
> [ 6.898992] alg: self-tests for sha256 using sha256-padlock-nano failed
> (rc=-22)
> [ 6.898993] btmtk via_cputemp hwmon_vid cfg80211 via_rng
> snd_hda_codec_realtek binfmt_misc bluetooth snd_hda_codec_generic uvcvideo
> snd_hda_scodec_component snd_hda_codec_hdmi kvm_intel
> [ 6.899009] WARNING: CPU: 4 PID: 754 at crypto/testmgr.c:5816
> alg_test.cold+0x37/0xaa
> [ 6.899015] hid_generic(+) videobuf2_vmalloc snd_hda_intel
> ......
> [ 6.899253] CR2: 00007f7512ee9de0 CR3: 000000011ada4005 CR4:
> 0000000000172ef0
> [ 6.899254] Call Trace:
> [ 6.899258] Call Trace:
> [ 6.899258] <TASK>
> [ 6.899261] <TASK>
> [ 6.899263] ? finish_task_switch.isra.0+0x97/0x2c0
> [ 6.899265] ? finish_task_switch.isra.0+0x97/0x2c0
> [ 6.899271] ? __schedule+0x4b8/0xd00
> [ 6.899272] ? __schedule+0x4b8/0xd00
> [ 6.899279] ? __pfx_cryptomgr_test+0x10/0x10
> [ 6.899280] ? __pfx_cryptomgr_test+0x10/0x10
> [ 6.899285] cryptomgr_test+0x24/0x40
> [ 6.899285] cryptomgr_test+0x24/0x40
> [ 6.899290] kthread+0xf9/0x240
> [ 6.899290] kthread+0xf9/0x240
> [ 6.899297] ? __pfx_kthread+0x10/0x10
> [ 6.899297] ? __pfx_kthread+0x10/0x10
> [ 6.899303] ret_from_fork+0x15c/0x190
> [ 6.899303] ret_from_fork+0x15c/0x190
> [ 6.899309] ? __pfx_kthread+0x10/0x10
> [ 6.899310] ? __pfx_kthread+0x10/0x10
> [ 6.899314] ret_from_fork_asm+0x1a/0x30
> [ 6.899315] ret_from_fork_asm+0x1a/0x30
> [ 6.899323] </TASK>
> [ 6.899323] </TASK>
> [ 6.899325] ---[ end trace 0000000000000000 ]---
> [ 6.899326] ---[ end trace 0000000000000000 ]---
> [ 6.901179] hid-generic 0003:248A:8367.0002: input,hidraw1: USB HID v1.11
> Keyboard [Telink Wireless Receiver] on usb-0000:01:00.0-3.2/input1
> ......
> The `dmesg` is uploaded to `https://linux-
> hardware.org/?probe=6f2705615c&log=dmesg` .
>
>
> I hope you can take some time to take a look and fix it as much as possible.
> Thanks!
My understanding is, that this is
https://lore.kernel.org/lkml/20250611101750.6839-1-AlanSong-oc@zhaoxin.com/
correct?
Can you followup on theat upstream upstream if you can test the
proposed approaches, and keep us as well in the loop?
Regards,
Salvatore
Reply to: