Your message dated Sun, 4 Feb 2024 09:18:47 +0100 with message-id <zb9izxtv30xms...@eldamar.lan> and subject line Re: Bug#1061262: ecdh-nist-p256: stack dump on boot has caused the Debian Bug report #1061262, regarding ecdh-nist-p256: stack dump on boot to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1061262: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061262 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Package: ecdh-nist-p256 Severity: normal X-Debbugs-Cc: kjell.myksv...@gmail.com Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? Reboot after package updates. * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? [ 3.334317] ------------[ cut here ]------------ [ 3.334319] alg: self-tests for ecdh-nist-p256 using ecdh-nist-p256-generic failed (rc=-14) [ 3.334325] WARNING: CPU: 27 PID: 461 at crypto/testmgr.c:5936 alg_test+0x516/0x630 [ 3.334331] Modules linked in: ecdh_generic(+) ecc crc16 amdgpu(+) i2c_algo_bit drm_ttm_helper ttm video drm_suballoc_helper amdxcp drm_buddy gpu_sched drm_display_helper drm_kms_helper xhci_pci nvme drm xhci_hcd nvme_core t10_pi crc32c_intel cec usbcore crc64_rocksoft crc64 rc_core crc_t10dif crct10dif_generic crct10dif_pclmul crct10dif_common usb_common gpio_amdpt wmi gpio_generic [ 3.334369] CPU: 27 PID: 461 Comm: cryptomgr_test Not tainted 6.5.0-5-amd64 #1 Debian 6.5.13-1 [ 3.334372] Hardware name: System manufacturer System Product Name/PRIME X399-A, BIOS 1601 04/14/2023 [ 3.334374] RIP: 0010:alg_test+0x516/0x630 [ 3.334377] Code: ff ff 4c 89 e6 4c 89 e7 41 89 c7 e8 e4 f4 fe ff e9 37 ff ff ff 44 89 f9 48 89 ea 4c 89 ee 48 c7 c7 38 08 0c 98 e8 1a 5d b5 ff <0f> 0b e9 7d fe ff ff 48 89 c2 48 89 ee 48 c7 c7 70 07 0c 98 45 89 [ 3.334379] RSP: 0018:ffffbd2844e97e10 EFLAGS: 00010286 [ 3.334381] RAX: 0000000000000000 RBX: 000000000000007e RCX: c0000000ffff7fff [ 3.334383] RDX: 0000000000000000 RSI: 00000000ffff7fff RDI: 0000000000000001 [ 3.334385] RBP: ffff987682aeee00 R08: 0000000000000000 R09: ffffbd2844e97ca0 [ 3.334386] R10: 0000000000000003 R11: ffff987deedfffe8 R12: 000000000000007f [ 3.334388] R13: ffff987682aeee80 R14: 00000000ffffffff R15: 00000000fffffff2 [ 3.334390] FS: 0000000000000000(0000) GS:ffff987def0c0000(0000) knlGS:0000000000000000 [ 3.334392] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 3.334393] CR2: 00007fe96d9ba840 CR3: 000000010c7ea000 CR4: 00000000003506e0 [ 3.334395] Call Trace: [ 3.334398] <TASK> [ 3.334399] ? alg_test+0x516/0x630 [ 3.334401] ? __warn+0x81/0x130 [ 3.334406] ? alg_test+0x516/0x630 [ 3.334409] ? report_bug+0x171/0x1a0 [ 3.334413] ? prb_read_valid+0x1b/0x30 [ 3.334417] ? srso_return_thunk+0x5/0x10 [ 3.334422] ? handle_bug+0x3c/0x80 [ 3.334426] ? exc_invalid_op+0x17/0x70 [ 3.334429] ? asm_exc_invalid_op+0x1a/0x20 [ 3.334435] ? alg_test+0x516/0x630 [ 3.334438] ? psi_memstall_leave+0xb0/0xb0 [ 3.334441] ? srso_return_thunk+0x5/0x10 [ 3.334444] ? finish_task_switch.isra.0+0x8f/0x2d0 [ 3.334449] ? srso_return_thunk+0x5/0x10 [ 3.334452] ? __schedule+0x3e2/0xb20 [ 3.334457] ? __pfx_cryptomgr_test+0x10/0x10 [ 3.334460] cryptomgr_test+0x24/0x40 [ 3.334464] kthread+0xe8/0x120 [ 3.334468] ? __pfx_kthread+0x10/0x10 [ 3.334471] ret_from_fork+0x34/0x50 [ 3.334475] ? __pfx_kthread+0x10/0x10 [ 3.334478] ret_from_fork_asm+0x1b/0x30 [ 3.334486] </TASK> [ 3.334487] ---[ end trace 0000000000000000 ]--- * What outcome did you expect instead? No stack dump. *** End of the template - remove these template lines *** -- System Information: Debian Release: trixie/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 6.5.0-5-amd64 (SMP w/32 CPU threads; PREEMPT) Kernel taint flags: TAINT_WARN Locale: LANG=nb_NO.UTF-8, LC_CTYPE=nb_NO.UTF-8 (charmap=UTF-8), LANGUAGE=nb_NO:nb:no_NO:no:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---Source: linux Source-Version: 6.6.13-1 Hi, On Sun, Feb 04, 2024 at 08:51:13AM +0100, kjell.myksv...@gmail.com wrote: > lør. 27. jan. 2024 kl. 14:00 skrev Salvatore Bonaccorso <car...@debian.org>: > > > Control: tags -1 + moreinfo > > > > On Sun, Jan 21, 2024 at 06:43:11PM +0100, Kjell M. Myksvoll wrote: > > > Package: ecdh-nist-p256 > > > Severity: normal > > > X-Debbugs-Cc: kjell.myksv...@gmail.com > > > > > > Dear Maintainer, > > > > > > *** Reporter, please consider answering these questions, where > > appropriate *** > > > > > > * What led up to the situation? > > > > > > Reboot after package updates. > > > > > > * What exactly did you do (or not do) that was effective (or > > > ineffective)? > > > * What was the outcome of this action? > > > > > > [ 3.334317] ------------[ cut here ]------------ > > > [ 3.334319] alg: self-tests for ecdh-nist-p256 using > > ecdh-nist-p256-generic failed (rc=-14) > > > [ 3.334325] WARNING: CPU: 27 PID: 461 at crypto/testmgr.c:5936 > > alg_test+0x516/0x630 > > > [ 3.334331] Modules linked in: ecdh_generic(+) ecc crc16 amdgpu(+) > > i2c_algo_bit drm_ttm_helper ttm video drm_suballoc_helper amdxcp drm_buddy > > gpu_sched drm_display_helper drm_kms_helper xhci_pci nvme drm xhci_hcd > > nvme_core t10_pi crc32c_intel cec usbcore crc64_rocksoft crc64 rc_core > > crc_t10dif crct10dif_generic crct10dif_pclmul crct10dif_common usb_common > > gpio_amdpt wmi gpio_generic > > > [ 3.334369] CPU: 27 PID: 461 Comm: cryptomgr_test Not tainted > > 6.5.0-5-amd64 #1 Debian 6.5.13-1 > > > [ 3.334372] Hardware name: System manufacturer System Product > > Name/PRIME X399-A, BIOS 1601 04/14/2023 > > > [ 3.334374] RIP: 0010:alg_test+0x516/0x630 > > > [ 3.334377] Code: ff ff 4c 89 e6 4c 89 e7 41 89 c7 e8 e4 f4 fe ff e9 > > 37 ff ff ff 44 89 f9 48 89 ea 4c 89 ee 48 c7 c7 38 08 0c 98 e8 1a 5d b5 ff > > <0f> 0b e9 7d fe ff ff 48 89 c2 48 89 ee 48 c7 c7 70 07 0c 98 45 89 > > > [ 3.334379] RSP: 0018:ffffbd2844e97e10 EFLAGS: 00010286 > > > [ 3.334381] RAX: 0000000000000000 RBX: 000000000000007e RCX: > > c0000000ffff7fff > > > [ 3.334383] RDX: 0000000000000000 RSI: 00000000ffff7fff RDI: > > 0000000000000001 > > > [ 3.334385] RBP: ffff987682aeee00 R08: 0000000000000000 R09: > > ffffbd2844e97ca0 > > > [ 3.334386] R10: 0000000000000003 R11: ffff987deedfffe8 R12: > > 000000000000007f > > > [ 3.334388] R13: ffff987682aeee80 R14: 00000000ffffffff R15: > > 00000000fffffff2 > > > [ 3.334390] FS: 0000000000000000(0000) GS:ffff987def0c0000(0000) > > knlGS:0000000000000000 > > > [ 3.334392] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 > > > [ 3.334393] CR2: 00007fe96d9ba840 CR3: 000000010c7ea000 CR4: > > 00000000003506e0 > > > [ 3.334395] Call Trace: > > > [ 3.334398] <TASK> > > > [ 3.334399] ? alg_test+0x516/0x630 > > > [ 3.334401] ? __warn+0x81/0x130 > > > [ 3.334406] ? alg_test+0x516/0x630 > > > [ 3.334409] ? report_bug+0x171/0x1a0 > > > [ 3.334413] ? prb_read_valid+0x1b/0x30 > > > [ 3.334417] ? srso_return_thunk+0x5/0x10 > > > [ 3.334422] ? handle_bug+0x3c/0x80 > > > [ 3.334426] ? exc_invalid_op+0x17/0x70 > > > [ 3.334429] ? asm_exc_invalid_op+0x1a/0x20 > > > [ 3.334435] ? alg_test+0x516/0x630 > > > [ 3.334438] ? psi_memstall_leave+0xb0/0xb0 > > > [ 3.334441] ? srso_return_thunk+0x5/0x10 > > > [ 3.334444] ? finish_task_switch.isra.0+0x8f/0x2d0 > > > [ 3.334449] ? srso_return_thunk+0x5/0x10 > > > [ 3.334452] ? __schedule+0x3e2/0xb20 > > > [ 3.334457] ? __pfx_cryptomgr_test+0x10/0x10 > > > [ 3.334460] cryptomgr_test+0x24/0x40 > > > [ 3.334464] kthread+0xe8/0x120 > > > [ 3.334468] ? __pfx_kthread+0x10/0x10 > > > [ 3.334471] ret_from_fork+0x34/0x50 > > > [ 3.334475] ? __pfx_kthread+0x10/0x10 > > > [ 3.334478] ret_from_fork_asm+0x1b/0x30 > > > [ 3.334486] </TASK> > > > [ 3.334487] ---[ end trace 0000000000000000 ]--- > > > > > > * What outcome did you expect instead? > > > > > > No stack dump. > > > > Please test 6.6.13-1 from unstable and 6.7.1-1~exp1 from experimental > > as the 6.5.y series won't get any more updates. Does the bug show up > > there as well? > > > > Hi! Have tested with 6.6.13-1 now, and the issue seems to be gone with that > version. No stack > dump during boot. Thanks for the report back! Regards, Salvatore
--- End Message ---
