From: "Konold, Martin" <martin.konold@konsec.com>
To: Proxmox VE user list <pve-user@lists.proxmox.com>
Subject: [PVE-User] issues with 8.0.4 and Kernel 6.2.16-8-pve
Date: Tue, 22 Aug 2023 12:50:53 +0200 [thread overview]
Message-ID: <b6bd39e78d613b72c0b827626adb4624@konsec.com> (raw)
Hi,
in my test environment running on AMD hardware (Ryzen 9 3900 12-Core) I
can reproducibly produce errors messages about segfaults with the most
recent PVE kernels including 6.2.16-8-pve.
This PVE runs hyperconverged with ceph version 17.2.6 (quincy).
The problem is not experienced with kernel pinned to 5.15.108-1-pve.
For those interested: "proxmox-boot-tool kernel pin 5.15.108-1-pve"
[Mo Aug 21 16:36:06 2023] pverados[140842]: segfault at 5570961acb40 ip
000055709525cc36 sp 00007ffdb0a03360 error 7 in
perl[557095174000+195000] likely on CPU 19 (core 9, socket 0)
[Mo Aug 21 16:36:06 2023] Code: 01 08 49 89 c6 e8 8a b1 02 00 48 8b 85
e0 00 00 00 4c 8b 44 24 08 48 8b 40 18 48 85 c0 0f 84 e3 02 00 00 48 8b
15 a2 52 21 00 <c7> 40 20 ff ff ff ff 66 48 0f 6e c8 48 89 50 28 48 8b
10 48 8b 12
[Mo Aug 21 16:43:06 2023] pverados[145377]: segfault at 5570961acb40 ip
000055709525cc36 sp 00007ffdb0a03360 error 7 in
perl[557095174000+195000] likely on CPU 5 (core 6, socket 0)
[Mo Aug 21 16:43:06 2023] Code: 01 08 49 89 c6 e8 8a b1 02 00 48 8b 85
e0 00 00 00 4c 8b 44 24 08 48 8b 40 18 48 85 c0 0f 84 e3 02 00 00 48 8b
15 a2 52 21 00 <c7> 40 20 ff ff ff ff 66 48 0f 6e c8 48 89 50 28 48 8b
10 48 8b 12
[Mo Aug 21 17:39:05 2023] pverados[181472]: segfault at 557098a00140 ip
000055709524f09d sp 00007ffdb0a030f0 error 7 in
perl[557095174000+195000] likely on CPU 7 (core 9, socket 0)
[Mo Aug 21 17:39:05 2023] Code: 0f 95 c2 c1 e2 05 08 55 00 41 83 47 08
01 48 8b 53 08 22 42 23 0f b6 c0 66 89 45 02 49 8b 07 8b 78 60 48 8b 70
48 44 8d 6f 01 <44> 89 68 60 41 83 fd 01 0f 8f 4d 04 00 00 48 8b 56 08
49 63 c5 48
[Mo Aug 21 18:02:06 2023] pverados[196758]: segfault at 557095199ae0 ip
0000557095199ae0 sp 00007ffdb0a034f8 error 14 likely on CPU 20 (core 10,
socket 0)
[Mo Aug 21 18:02:06 2023] Code: Unable to access opcode bytes at
0x557095199ab6.
[Mo Aug 21 18:45:05 2023] pverados[224840]: segfault at 5570961acb40 ip
000055709525cc36 sp 00007ffdb0a03360 error 7 in
perl[557095174000+195000] likely on CPU 1 (core 1, socket 0)
[Mo Aug 21 18:45:05 2023] Code: 01 08 49 89 c6 e8 8a b1 02 00 48 8b 85
e0 00 00 00 4c 8b 44 24 08 48 8b 40 18 48 85 c0 0f 84 e3 02 00 00 48 8b
15 a2 52 21 00 <c7> 40 20 ff ff ff ff 66 48 0f 6e c8 48 89 50 28 48 8b
10 48 8b 12
[Mo Aug 21 19:23:35 2023] pverados[249788]: segfault at 5570961acb40 ip
000055709525cc36 sp 00007ffdb0a03360 error 7 in
perl[557095174000+195000] likely on CPU 0 (core 0, socket 0)
[Mo Aug 21 19:23:35 2023] Code: 01 08 49 89 c6 e8 8a b1 02 00 48 8b 85
e0 00 00 00 4c 8b 44 24 08 48 8b 40 18 48 85 c0 0f 84 e3 02 00 00 48 8b
15 a2 52 21 00 <c7> 40 20 ff ff ff ff 66 48 0f 6e c8 48 89 50 28 48 8b
10 48 8b 12
[Mo Aug 21 20:12:45 2023] pverados[281599]: segfault at 557095199ae0 ip
0000557095199ae0 sp 00007ffdb0a034f8 error 14 in
perl[557095174000+195000] likely on CPU 19 (core 9, socket 0)
[Mo Aug 21 20:12:45 2023] Code: Unable to access opcode bytes at
0x557095199ab6.
[Mo Aug 21 23:17:46 2023] pverados[401208]: segfault at 5570961acb40 ip
000055709525cc36 sp 00007ffdb0a03360 error 7 in
perl[557095174000+195000] likely on CPU 7 (core 9, socket 0)
[Mo Aug 21 23:17:46 2023] Code: 01 08 49 89 c6 e8 8a b1 02 00 48 8b 85
e0 00 00 00 4c 8b 44 24 08 48 8b 40 18 48 85 c0 0f 84 e3 02 00 00 48 8b
15 a2 52 21 00 <c7> 40 20 ff ff ff ff 66 48 0f 6e c8 48 89 50 28 48 8b
10 48 8b 12
[Di Aug 22 00:58:06 2023] pverados[465511]: segfault at 557095199ae0 ip
0000557095199ae0 sp 00007ffdb0a034f8 error 14 in
perl[557095174000+195000] likely on CPU 3 (core 4, socket 0)
[Di Aug 22 00:58:06 2023] Code: Unable to access opcode bytes at
0x557095199ab6.
[Di Aug 22 03:45:16 2023] pverados[572963]: segfault at 557095199ae0 ip
0000557095199ae0 sp 00007ffdb0a034f8 error 14 in
perl[557095174000+195000] likely on CPU 7 (core 9, socket 0)
[Di Aug 22 03:45:16 2023] Code: Unable to access opcode bytes at
0x557095199ab6.
[Di Aug 22 05:40:06 2023] pverados[647893]: segfault at 557095199ae0 ip
0000557095199ae0 sp 00007ffdb0a034f8 error 14 in
perl[557095174000+195000] likely on CPU 2 (core 2, socket 0)
[Di Aug 22 05:40:06 2023] Code: Unable to access opcode bytes at
0x557095199ab6.
[Di Aug 22 07:20:07 2023] pverados[713129]: segfault at 557095199ae0 ip
0000557095199ae0 sp 00007ffdb0a034f8 error 14 in
perl[557095174000+195000] likely on CPU 7 (core 9, socket 0)
[Di Aug 22 07:20:07 2023] Code: Unable to access opcode bytes at
0x557095199ab6.
[Di Aug 22 09:24:36 2023] pverados[793888]: segfault at 557095199ae0 ip
0000557095199ae0 sp 00007ffdb0a034f8 error 14 in
perl[557095174000+195000] likely on CPU 3 (core 4, socket 0)
[Di Aug 22 09:24:36 2023] Code: Unable to access opcode bytes at
0x557095199ab6.
[Di Aug 22 11:45:56 2023] pverados[887089]: segfault at 557098a00140 ip
000055709524f09d sp 00007ffdb0a030f0 error 7 in
perl[557095174000+195000] likely on CPU 4 (core 5, socket 0)
[Di Aug 22 11:45:56 2023] Code: 0f 95 c2 c1 e2 05 08 55 00 41 83 47 08
01 48 8b 53 08 22 42 23 0f b6 c0 66 89 45 02 49 8b 07 8b 78 60 48 8b 70
48 44 8d 6f 01 <44> 89 68 60 41 83 fd 01 0f 8f 4d 04 00 00 48 8b 56 08
49 63 c5 48
--
Kind Regards
ppa. Martin Konold
--
Martin Konold - Prokurist, CTO
KONSEC GmbH - make things real
Amtsgericht Stuttgart, HRB 23690
Geschäftsführer: Andreas Mack
Im Köller 3, 70794 Filderstadt, Germany
next reply other threads:[~2023-08-22 10:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-22 10:50 Konold, Martin [this message]
2023-08-22 11:11 ` David der Nederlanden | ITTY
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=b6bd39e78d613b72c0b827626adb4624@konsec.com \
--to=martin.konold@konsec.com \
--cc=pve-user@lists.proxmox.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.