all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Olav Smorholm <olavks@gmail.com>
To: 66610@debbugs.gnu.org
Subject: bug#66610: Acknowledgement (potrace, po4a; guix bug, complete console output)
Date: Wed, 18 Oct 2023 23:21:05 +0200	[thread overview]
Message-ID: <py527tufoxzizzv4crjpiqukfgibrehlwo7jopgmvckoshmnwo@vat7el7mqldx> (raw)
In-Reply-To: <akemfeg56xc45xra3675nqw24j3xoo5n6xdk727bxwnz3c3evl@j5hdl6rnzrr4>

Tried to reproduce, but with no substitutes and no grafts.
Wed Oct 18 18:48:34 2023] mes[19410]: segfault at 0 ip 0000000001016085 sp 00000000ffff5044 error 6 in mes[1000000+18000] likely on CPU 4 (core 8, socket 0)
[Wed Oct 18 18:48:34 2023] Code: 60 01 01 e8 71 ef ff ff 83 c4 04 85 c0 b8 00 00 00 00 89 45 fc b8 00 00 00 00 bb 00 00 00 00 50 89 d8 8b 5d fc 01 d8 89 c3 58 <88> 03 85 c0 c9 c3 3a 00 61 73 73 65 72 74 20 66 61 69 6c 3a 20 00

Which should be the first, and perhaps only one before conf and tests.
Reported as guix binary requested with caveats that while GNU, i tend to opt
for UNIX crashy. and could be hard to chase with coincidence mixed in;
hard to chase.

On Wed, Oct 18, 2023 at 05:34:50PM +0200, Olav Smorholm wrote:
> This may be relevant dmesg, where all should be from guix bootstrap on
> gentoo-musl hardened after garbage collecting, guix pull and update.
> I have enabled unsafe(rnd) kernel options security and hardening options.
> So the bug may have revealed itself here. A few of these lines are
> suspicious, and xsltproc may coincide, and tripped by kernel not safe
> for bugs.
> xsltproc[29510]: segfault at 7fffff7fefe0 ip 00007ffff7b952ce sp 00007fffff7fefb0 error 6 in libc.so.6
> Below this is a refresh of guix pull and update.
> 
> 
> 
> [16584.148847] ld.lld[15969]: segfault at 8 ip 00007ffff1cba4f4 sp 00007ffd747f77d8 error 4 in libLLVM-15.so[7ffff133f000+3c17000] likely on CPU 10 (core 4, socket 0)
> [16584.148867] Code: b6 50 08 80 fa 0d 0f 94 c0 c3 66 2e 0f 1f 84 00 00 00 00 00 66 90 48 8b 47 08 80 78 08 0d 0f 94 c0 c3 0f 1f 40 00 48 8b 47 08 <0f> b6 40 08 83 e8 12 83 f8 01 0f 96 c0 c3 66 2e 0f 1f 84 00 00 00
> [22073.399589] process 'bootstrap-seeds/POSIX/x86/kaem-optional-seed' started with executable stack
> [23083.553485] mes[21949]: segfault at 0 ip 0000000001016085 sp 00000000ffff5044 error 6 in mes[1000000+18000] likely on CPU 1 (core 1, socket 0)
> [23083.553504] Code: 60 01 01 e8 71 ef ff ff 83 c4 04 85 c0 b8 00 00 00 00 89 45 fc b8 00 00 00 00 bb 00 00 00 00 50 89 d8 8b 5d fc 01 d8 89 c3 58 <88> 03 85 c0 c9 c3 3a 00 61 73 73 65 72 74 20 66 61 69 6c 3a 20 00
> [44199.655173] traps: conftest[11508] general protection fault ip:8048225 sp:ffffadb0 error:0 in conftest[8048000+57000]
> [47929.916650] test-recvmsg[1981]: segfault at 0 ip 00007f6d870cc7d5 sp 00007ffcf61165e0 error 4 in libc.so[7f6d8709a000+62000] likely on CPU 12 (core 8, socket 0)
> [47929.916668] Code: 48 89 c7 e8 7d a5 fd ff 48 83 c4 18 c3 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 53 48 63 ca 48 89 f3 45 31 c9 45 31 c0 48 83 ec 40 <f3> 0f 6f 06 f3 0f 6f 4e 10 f3 0f 6f 56 20 48 8b 46 30 48 89 e2 48
> [47944.249962] test-recvmsg[4022]: segfault at 0 ip 00007fe08edc87d5 sp 00007fff60fed1e0 error 4 in libc.so[7fe08ed96000+62000] likely on CPU 8 (core 0, socket 0)
> [47944.249980] Code: 48 89 c7 e8 7d a5 fd ff 48 83 c4 18 c3 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 53 48 63 ca 48 89 f3 45 31 c9 45 31 c0 48 83 ec 40 <f3> 0f 6f 06 f3 0f 6f 4e 10 f3 0f 6f 56 20 48 8b 46 30 48 89 e2 48
> [86977.669680] NET: Registered PF_ALG protocol family
> [87794.000878] xsltproc[29510]: segfault at 7fffff7fefe0 ip 00007ffff7b952ce sp 00007fffff7fefb0 error 6 in libc.so.6[7ffff7b2a000+167000] likely on CPU 8 (core 0, socket 0)
> [87794.000896] Code: 00 48 89 c2 4c 8d 4a 10 48 8b 42 10 4c 89 ce 48 c1 ee 0c 49 89 f0 49 31 c0 48 39 c6 74 be eb ac 0f 1f 40 00 48 89 d8 48 89 d9 <44> 89 64 24 30 48 c1 e8 06 48 c1 e9 09 c7 44 24 78 6e 00 00 00 48
> [88930.006298] cmsysTestProces[556]: segfault at 4 ip 0000000000402bfb sp 00007fffffffc770 error 6 in cmsysTestProcess[402000+6000] likely on CPU 1 (core 1, socket 0)
> [88930.006316] Code: 83 40 00 e8 67 f7 ff ff 48 8b 3d 20 86 00 00 e8 db f6 ff ff 48 8b 3d 34 86 00 00 e8 cf f6 ff ff ba 2e 00 00 00 be 01 00 00 00 <c7> 04 25 04 00 00 00 00 00 00 00 48 8b 0d f3 85 00 00 bf 08 84 40
> [88930.013815] cmsysTestProces[563]: segfault at 4 ip 0000000000402bfb sp 00007fffffffc770 error 6 in cmsysTestProcess[402000+6000] likely on CPU 9 (core 1, socket 0)
> [88930.013830] Code: 83 40 00 e8 67 f7 ff ff 48 8b 3d 20 86 00 00 e8 db f6 ff ff 48 8b 3d 34 86 00 00 e8 cf f6 ff ff ba 2e 00 00 00 be 01 00 00 00 <c7> 04 25 04 00 00 00 00 00 00 00 48 8b 0d f3 85 00 00 bf 08 84 40
> [88963.001638] Crash[1983]: segfault at 0 ip 0000000000401116 sp 00007fffffffc9f0 error 6 in Crash[401000+1000] likely on CPU 12 (core 8, socket 0)
> [88963.001656] Code: 01 5d c3 90 c3 66 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 f3 0f 1e fa eb 8a 55 48 89 e5 48 c7 45 f8 00 00 00 00 48 8b 45 f8 <c7> 00 01 00 00 00 b8 00 00 00 00 5d c3 00 48 83 ec 08 48 83 c4 08
> [89271.158500] cmsysTestProces[18868]: segfault at 4 ip 0000000000402bfb sp 00007fffffffcb70 error 6 in cmsysTestProcess[402000+6000] likely on CPU 1 (core 1, socket 0)
> [89271.158518] Code: 83 40 00 e8 67 f7 ff ff 48 8b 3d 20 86 00 00 e8 db f6 ff ff 48 8b 3d 34 86 00 00 e8 cf f6 ff ff ba 2e 00 00 00 be 01 00 00 00 <c7> 04 25 04 00 00 00 00 00 00 00 48 8b 0d f3 85 00 00 bf 08 84 40
> [89271.162994] cmsysTestProces[18881]: segfault at 4 ip 0000000000402bfb sp 00007fffffffcb70 error 6 in cmsysTestProcess[402000+6000] likely on CPU 8 (core 0, socket 0)
> [89271.163010] Code: 83 40 00 e8 67 f7 ff ff 48 8b 3d 20 86 00 00 e8 db f6 ff ff 48 8b 3d 34 86 00 00 e8 cf f6 ff ff ba 2e 00 00 00 be 01 00 00 00 <c7> 04 25 04 00 00 00 00 00 00 00 48 8b 0d f3 85 00 00 bf 08 84 40
> [89298.998091] Crash[18308]: segfault at 0 ip 0000000000401116 sp 00007fffffffcdf0 error 6 in Crash[401000+1000] likely on CPU 3 (core 5, socket 0)
> [89298.998108] Code: 01 5d c3 90 c3 66 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 f3 0f 1e fa eb 8a 55 48 89 e5 48 c7 45 f8 00 00 00 00 48 8b 45 f8 <c7> 00 01 00 00 00 b8 00 00 00 00 5d c3 00 48 83 ec 08 48 83 c4 08
> 




  reply	other threads:[~2023-10-18 21:21 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-18 14:00 bug#66610: potrace, po4a; guix bug, complete console output Olav Smorholm
     [not found] ` <handler.66610.B.169764205314809.ack@debbugs.gnu.org>
2023-10-18 15:34   ` bug#66610: Acknowledgement (potrace, po4a; guix bug, complete console output) Olav Smorholm
2023-10-18 21:21     ` Olav Smorholm [this message]
2023-10-19 13:04       ` Olav Smorholm
2023-10-19 16:29         ` Olav Smorholm
2023-10-19 22:36           ` Olav Smorholm
2023-10-21 14:57             ` Olav Smorholm
2023-10-21 17:12               ` Olav Smorholm
2023-10-21 18:29                 ` Olav Smorholm
2023-10-21 18:52                   ` Olav Smorholm
2023-10-23 16:48                     ` Olav Smorholm
2023-10-23 17:03                       ` Olav Smorholm
2023-10-23 17:42                         ` Olav Smorholm
2023-10-23 18:13                           ` Olav Smorholm
2023-11-17 19:37                             ` Olav Smorholm
2023-11-17 19:55                               ` Olav Smorholm
2023-11-17 20:16                                 ` Olav Smorholm
2023-11-17 20:40                                   ` Olav Smorholm
2023-11-17 21:24                                     ` Olav Smorholm
2023-11-17 22:59                                       ` Olav Smorholm
2023-11-17 23:16                                         ` Olav Smorholm
2023-12-08  0:17                                           ` Olav Smorholm
2023-12-19  5:20                                             ` bug#66610: potrace, po4a; guix bug, complete console output Maxim Cournoyer

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=py527tufoxzizzv4crjpiqukfgibrehlwo7jopgmvckoshmnwo@vat7el7mqldx \
    --to=olavks@gmail.com \
    --cc=66610@debbugs.gnu.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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

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.