potrace, po4a; guix bug, complete console output

  • Open
  • quality assurance status badge
Details
2 participants
  • Maxim Cournoyer
  • Olav Smorholm
Owner
unassigned
Submitted by
Olav Smorholm
Severity
normal
O
O
Olav Smorholm wrote on 18 Oct 2023 16:00
(address . bug-guix@gnu.org)
sabb6ltn7lrmoawa72nvv6hran3i7y23vay6zaexkomppuipye@ktvomcckxwcw
building /gnu/store/w63ra4pwqvk9ii5zf4piksf4kyddvz3p-potrace-1.16.drv...
\Backtrace:
In ice-9/eval.scm:
155:9 19 (_ _)
159:9 18 (_ #(#(#(#(#(#(#(#(#(#(#(#(#(#(#(#(#<directory (guile-u?> ?) ?) ?) ?) ?) ?) ?) ?) ?) ?) ?) ?) ?) ?) ?) ?))
In ice-9/boot-9.scm:
152:2 17 (with-fluid* _ _ _)
152:2 16 (with-fluid* _ _ _)
In ./guix/store.scm:
2168:24 15 (run-with-store #<store-connection 256.99 7f3c0bbc10a0> #<procedure 7f3bf66e6730 at ./guix/self.scm:13?> ?)
1996:8 14 (_ #<store-connection 256.99 7f3c0bbc10a0>)
In ./guix/gexp.scm:
299:22 13 (_ #<store-connection 256.99 7f3c0bbc10a0>)
1180:2 12 (_ #<store-connection 256.99 7f3c0bbc10a0>)
1046:2 11 (_ #<store-connection 256.99 7f3c0bbc10a0>)
892:4 10 (_ #<store-connection 256.99 7f3c0bbc10a0>)
In ./guix/store.scm:
2053:12 9 (_ #<store-connection 256.99 7f3c0bbc10a0>)
1405:13 8 (map/accumulate-builds #<store-connection 256.99 7f3c0bbc10a0> #<procedure 7f3becda5560 at ./guix/stor?> ?)
1405:13 7 (map/accumulate-builds #<store-connection 256.99 7f3c0bbc10a0> #<procedure 7f3bdcb89240 at ./guix/stor?> ?)
1405:13 6 (map/accumulate-builds #<store-connection 256.99 7f3c0bbc10a0> #<procedure 7f3bfb1fcfa0 at ./guix/stor?> ?)
1405:13 5 (map/accumulate-builds #<store-connection 256.99 7f3c0bbc10a0> #<procedure 7f3bdeace6a0 at ./guix/stor?> ?)
1405:13 4 (map/accumulate-builds #<store-connection 256.99 7f3c0bbc10a0> #<procedure 7f3bde19d440 at ./guix/stor?> ?)
1405:13 3 (map/accumulate-builds #<store-connection 256.99 7f3c0bbc10a0> #<procedure 7f3bfa7f3940 at ./guix/stor?> ?)
1401:5 2 (map/accumulate-builds #<store-connection 256.99 7f3c0bbc10a0> #<procedure 7f3bf49c2b00 at ./guix/stor?> ?)
1417:15 1 (_ #<store-connection 256.99 7f3c0bbc10a0> ("/gnu/store/y4cbrpv0dxsdjg8w2mb702p77xszp9p8-po4a-0.69.drv") ?)
1417:15 0 (loop #f)

./guix/store.scm:1417:15: In procedure loop:
ERROR:
1. &store-protocol-error:
message: "build of `/gnu/store/y4cbrpv0dxsdjg8w2mb702p77xszp9p8-po4a-0.69.drv' failed"
status: 100
guix pull: error: You found a bug: the program '/gnu/store/bir38i1c1nwbfkbhgprn3c9bp23q5i1w-compute-guix-derivation'
failed to compute the derivation for Guix (version: "7823c6504082a0cfbd98beb301e041fb8bc4e44e"; system: "x86_64-linux";
host version: "e80022ff3adde3184bed6758f604e3aa12942865"; pull-version: 1).
Please report the COMPLETE output above by email to <bug-guix@gnu.org>.
O
O
Olav Smorholm wrote on 18 Oct 2023 17:34
Re: bug#66610: Acknowledgement (potrace, po4a; guix bug, complete console output)
(address . 66610@debbugs.gnu.org)
akemfeg56xc45xra3675nqw24j3xoo5n6xdk727bxwnz3c3evl@j5hdl6rnzrr4
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
O
O
Olav Smorholm wrote on 18 Oct 2023 23:21
(address . 66610@debbugs.gnu.org)
py527tufoxzizzv4crjpiqukfgibrehlwo7jopgmvckoshmnwo@vat7el7mqldx
Attachment: file
O
O
Olav Smorholm wrote on 19 Oct 2023 15:04
(address . 66610@debbugs.gnu.org)
itxmp4fi4dljejugku6pgn3sjxq2vkcon4zjgy2aogczdsacvd@o3nrz6ckvjj5
On Wed, Oct 18, 2023 at 11:21:06PM +0200, Olav Smorholm wrote:
Toggle quote (9 lines)
> 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.

took much longer with --no-grafts and --no-substitutes, but this also
showed up again, but not the seed.

[Thu Oct 19 12:18:54 2023] xsltproc[5943]: segfault at 7fffff7fefe0 ip 00007ffff7b952ce sp 00007fffff7fefb0 error 6 in libc.so.6[7ffff7b2a000+167000]

still fairly sure its from guix building.

[Tue Oct 17 21:33:19 2023] process 'bootstrap-seeds/POSIX/x86/kaem-optional-seed' started with executable stack
O
O
Olav Smorholm wrote on 19 Oct 2023 18:29
(address . 66610@debbugs.gnu.org)
odsdcfwmdcwqsntogtkxmfbq5gydjxwjtpxx2ugsfzfubpu66p@xqsxirqmgbuq
On Thu, Oct 19, 2023 at 03:05:01PM +0200, Olav Smorholm wrote:
Toggle quote (19 lines)
> On Wed, Oct 18, 2023 at 11:21:06PM +0200, Olav Smorholm wrote:
> > 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.
>
> took much longer with --no-grafts and --no-substitutes, but this also
> showed up again, but not the seed.
>
> [Thu Oct 19 12:18:54 2023] xsltproc[5943]: segfault at 7fffff7fefe0 ip 00007ffff7b952ce sp 00007fffff7fefb0 error 6 in libc.so.6[7ffff7b2a000+167000]
>
> still fairly sure its from guix building.
>
> [Tue Oct 17 21:33:19 2023] process 'bootstrap-seeds/POSIX/x86/kaem-optional-seed' started with executable stack

Reboot, and by not checking, into rebuild kernel without the pattern
init unsafe hardening options. For an hour and half, the only thing I
see is this:
Thu Oct 19 16:57:16 2023] process 'store/5srp88m0d10qxnb49c3sa2a186kjy6xz-tcc-boot-0.9.27/bin/tcc' started with executable stack

Instead of the seed, and no mes segfaults, and will do this again.
It's a bit of a stretch to say I had a rodent i here segfaulted my way
out of, but I dont live in any of the relevant information structures
between compiler assembly, running code and debuggers. Nor familiarity
enough to say why tcc is said to be started with executable stack
instead of the seed as above. I am just fairly certain that something
isn't house clean in what is inherently complicated and bootstrap that
touches many fundamental things.
O
O
Olav Smorholm wrote on 20 Oct 2023 00:36
(address . 66610@debbugs.gnu.org)
tdehmnbnokgppooja26ye3amnzgc57azrn7oksj3utq7cqyrpb@45fstetoc2wb
On Thu, Oct 19, 2023 at 06:29:07PM +0200, Olav Smorholm wrote:
Toggle quote (35 lines)
> On Thu, Oct 19, 2023 at 03:05:01PM +0200, Olav Smorholm wrote:
> > On Wed, Oct 18, 2023 at 11:21:06PM +0200, Olav Smorholm wrote:
> > > 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.
> >
> > took much longer with --no-grafts and --no-substitutes, but this also
> > showed up again, but not the seed.
> >
> > [Thu Oct 19 12:18:54 2023] xsltproc[5943]: segfault at 7fffff7fefe0 ip 00007ffff7b952ce sp 00007fffff7fefb0 error 6 in libc.so.6[7ffff7b2a000+167000]
> >
> > still fairly sure its from guix building.
> >
> > [Tue Oct 17 21:33:19 2023] process 'bootstrap-seeds/POSIX/x86/kaem-optional-seed' started with executable stack
>
> Reboot, and by not checking, into rebuild kernel without the pattern
> init unsafe hardening options. For an hour and half, the only thing I
> see is this:
> Thu Oct 19 16:57:16 2023] process 'store/5srp88m0d10qxnb49c3sa2a186kjy6xz-tcc-boot-0.9.27/bin/tcc' started with executable stack
>
> Instead of the seed, and no mes segfaults, and will do this again.
> It's a bit of a stretch to say I had a rodent i here segfaulted my way
> out of, but I dont live in any of the relevant information structures
> between compiler assembly, running code and debuggers. Nor familiarity
> enough to say why tcc is said to be started with executable stack
> instead of the seed as above. I am just fairly certain that something
> isn't house clean in what is inherently complicated and bootstrap that
> touches many fundamental things.
>

Another reboot with more hardening things:
process 'store/9cfq2h8sa5f6cgrhdgadlxwkf00vmgf5-gcc-mesboot1-4.6.4/bin/gcc' started with executable stack

and absolutely no segfaults.
either bugs got more clever, or this isn't house clean.
O
O
Olav Smorholm wrote on 21 Oct 2023 16:57
(address . 66610@debbugs.gnu.org)
g7nmpswfys6pr6te3ln557jmz7wdllxnfr6zmqynf6icziydjz@yuqsrpm5nynu
On Fri, Oct 20, 2023 at 12:36:48AM +0200, Olav Smorholm wrote:
Toggle quote (7 lines)
> Another reboot with more hardening things:
> process 'store/9cfq2h8sa5f6cgrhdgadlxwkf00vmgf5-gcc-mesboot1-4.6.4/bin/gcc' started with executable stack
>
> and absolutely no segfaults.
> either bugs got more clever, or this isn't house clean.
>

Another --no-substitutes --no-grafts guix pull after garbage collection.

Not seeing any crashes or the same bugs, but whatever that xsltproc is, whether docbooks
perl script ot not. Whatever it is doing, or what it is, that trigger
PF_ALG; it doesnt look nice.

[Fri Oct 20 22:34:22 2023] elogind-daemon[2265]: New session 1...
[Fri Oct 20 22:34:31 2023] wezterm-gui[3001]: memfd_create() called without MFD_EXEC or MFD_NOEXEC_SEAL set
[Fri Oct 20 22:37:54 2023] process 'bootstrap-seeds/POSIX/x86/kaem-optional-seed' started with executable stack
[Fri Oct 20 22:51:30 2023] mes[13170]: segfault at 0 ip 0000000001016085 sp 00000000ffff5044 error 6 in mes[1000000+18000] likely on CPU 7 (core 13, socket 0)
[Fri Oct 20 22:51:30 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
[Sat Oct 21 04:07:49 2023] traps: conftest[7164] general protection fault ip:8048225 sp:ffffadb0 error:0 in conftest[8048000+57000]
[Sat Oct 21 15:22:01 2023] NET: Registered PF_ALG protocol family
[Sat Oct 21 15:33:47 2023] xsltproc[20127]: segfault at 7fffff7fefe0 ip 00007ffff7b952ce sp 00007fffff7fefb0 error 6 in libc.so.6[7ffff7b2a000+167000] likely on CPU 0 (core 0, socket 0)
[Sat Oct 21 15:33:47 2023] 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
[Sat Oct 21 15:42:15 2023] cmsysTestProces[17226]: segfault at 4 ip 0000000000402bfb sp 00007fffffffc770 error 6 in cmsysTestProcess[402000+6000] likely on CPU 10 (core 4, socket 0)
[Sat Oct 21 15:42:15 2023] 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
[Sat Oct 21 15:42:15 2023] cmsysTestProces[17242]: segfault at 4 ip 0000000000402bfb sp 00007fffffffc770 error 6 in cmsysTestProcess[402000+6000] likely on CPU 8 (core 0, socket 0)
[Sat Oct 21 15:42:15 2023] 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
[Sat Oct 21 15:42:55 2023] Crash[30912]: segfault at 0 ip 0000000000401116 sp 00007fffffffc9f0 error 6 in Crash[401000+1000] likely on CPU 12 (core 8, socket 0)
[Sat Oct 21 15:42:55 2023] 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
[Sat Oct 21 15:48:06 2023] cmsysTestProces[7756]: segfault at 4 ip 0000000000402bfb sp 00007fffffffcb70 error 6 in cmsysTestProcess[402000+6000] likely on CPU 14 (core 12, socket 0)
[Sat Oct 21 15:48:06 2023] 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
[Sat Oct 21 15:48:06 2023] cmsysTestProces[7766]: segfault at 4 ip 0000000000402bfb sp 00007fffffffcb70 error 6 in cmsysTestProcess[402000+6000] likely on CPU 14 (core 12, socket 0)
[Sat Oct 21 15:48:06 2023] 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
[Sat Oct 21 15:48:36 2023] Crash[12401]: segfault at 0 ip 0000000000401116 sp 00007fffffffcdf0 error 6 in Crash[401000+1000] likely on CPU 6 (core 12, socket 0)
[Sat Oct 21 15:48:36 2023] 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
O
O
Olav Smorholm wrote on 21 Oct 2023 19:12
(address . 66610@debbugs.gnu.org)
bdcxipdc4jtzttg5baedupfzqggrjxgr626tmcvaqpbzypr6dg@7jm3fmpuinj6
On Sat, Oct 21, 2023 at 04:57:52PM +0200, Olav Smorholm wrote:
Toggle quote (28 lines)
> Another --no-substitutes --no-grafts guix pull after garbage collection.
>
> Not seeing any crashes or the same bugs, but whatever that xsltproc is, whether docbooks
> perl script ot not. Whatever it is doing, or what it is, that trigger
> PF_ALG; it doesnt look nice.
>
> [Fri Oct 20 22:34:22 2023] elogind-daemon[2265]: New session 1...
> [Fri Oct 20 22:34:31 2023] wezterm-gui[3001]: memfd_create() called without MFD_EXEC or MFD_NOEXEC_SEAL set
> [Fri Oct 20 22:37:54 2023] process 'bootstrap-seeds/POSIX/x86/kaem-optional-seed' started with executable stack
> [Fri Oct 20 22:51:30 2023] mes[13170]: segfault at 0 ip 0000000001016085 sp 00000000ffff5044 error 6 in mes[1000000+18000] likely on CPU 7 (core 13, socket 0)
> [Fri Oct 20 22:51:30 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
> [Sat Oct 21 04:07:49 2023] traps: conftest[7164] general protection fault ip:8048225 sp:ffffadb0 error:0 in conftest[8048000+57000]
> [Sat Oct 21 15:22:01 2023] NET: Registered PF_ALG protocol family
> [Sat Oct 21 15:33:47 2023] xsltproc[20127]: segfault at 7fffff7fefe0 ip 00007ffff7b952ce sp 00007fffff7fefb0 error 6 in libc.so.6[7ffff7b2a000+167000] likely on CPU 0 (core 0, socket 0)
> [Sat Oct 21 15:33:47 2023] 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
> [Sat Oct 21 15:42:15 2023] cmsysTestProces[17226]: segfault at 4 ip 0000000000402bfb sp 00007fffffffc770 error 6 in cmsysTestProcess[402000+6000] likely on CPU 10 (core 4, socket 0)
> [Sat Oct 21 15:42:15 2023] 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
> [Sat Oct 21 15:42:15 2023] cmsysTestProces[17242]: segfault at 4 ip 0000000000402bfb sp 00007fffffffc770 error 6 in cmsysTestProcess[402000+6000] likely on CPU 8 (core 0, socket 0)
> [Sat Oct 21 15:42:15 2023] 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
> [Sat Oct 21 15:42:55 2023] Crash[30912]: segfault at 0 ip 0000000000401116 sp 00007fffffffc9f0 error 6 in Crash[401000+1000] likely on CPU 12 (core 8, socket 0)
> [Sat Oct 21 15:42:55 2023] 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
> [Sat Oct 21 15:48:06 2023] cmsysTestProces[7756]: segfault at 4 ip 0000000000402bfb sp 00007fffffffcb70 error 6 in cmsysTestProcess[402000+6000] likely on CPU 14 (core 12, socket 0)
> [Sat Oct 21 15:48:06 2023] 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
> [Sat Oct 21 15:48:06 2023] cmsysTestProces[7766]: segfault at 4 ip 0000000000402bfb sp 00007fffffffcb70 error 6 in cmsysTestProcess[402000+6000] likely on CPU 14 (core 12, socket 0)
> [Sat Oct 21 15:48:06 2023] 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
> [Sat Oct 21 15:48:36 2023] Crash[12401]: segfault at 0 ip 0000000000401116 sp 00007fffffffcdf0 error 6 in Crash[401000+1000] likely on CPU 6 (core 12, socket 0)
> [Sat Oct 21 15:48:36 2023] 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

Whatever the initial guix bug was or what bitrot and system quirks that
may be involved.

There is inherent room for a moral appeal around K&R(Ken Thompson and
Dennis Ritchie) legendary and classical systems security problems.

That accessibility, where interest is ensured, not really seeing
sufficiently amounts of assembly code and integrated circuits amateurs
in lack of professionals with hobbies.

Admitting to the existance of preferences of psychological nature that
influence social and ideological adherance from necessity between
natural and moral activity understood as practical vs cultural.
For GNU this line and differences is inherently strengthened.
O
O
Olav Smorholm wrote on 21 Oct 2023 20:29
(address . 66610@debbugs.gnu.org)
j5kmm34mxgdd4qvslwk4kr36ffy4uh4ljwiqxpwuugap75mwtz@jzbujq42tcbb
Attachment: file
O
O
Olav Smorholm wrote on 21 Oct 2023 20:52
(address . 66610@debbugs.gnu.org)
yc7ditmczudqllm4bbctymgm2vixl7k7266xzrwfp5yetgfwbh@yjs4siyoz34t
Attachment: file
O
O
Olav Smorholm wrote on 23 Oct 2023 18:48
(address . 66610@debbugs.gnu.org)
iu6hm7kknn7nyatjjjfjmt4nlyshed6cb2gqkipygt7xh6vwnd@e3ejh3ru23vb
On Sat, Oct 21, 2023 at 08:52:13PM +0200, Olav Smorholm wrote:
Toggle quote (2 lines)
>

And call it, or view is it as you may; no trivial task to determine if
the guix binary bug and crash was useful or not.

But in the process, while for other things after; starting to study
dmesg. Bluez and related things that awaken bluetooth kernel subsystems
is less of an aesthetic problem.

I react somewhat on PF_ALG especially, weird segfault that calls itself
xsltproc, and that there even exist segfaults and protection faults as
if checking for a kernel that is newer than minix era is
necessary. As false positives and negatives for intent to hide even the
oldest and most deprecated "hello world" crud.
O
O
Olav Smorholm wrote on 23 Oct 2023 19:03
(address . 66610@debbugs.gnu.org)
csrbbut4sdg2c5ajnbgv645begi55kkk2k3npbmmvctvvmrmli@knet3re473mw
On Mon, Oct 23, 2023 at 06:48:26PM +0200, Olav Smorholm wrote:
Toggle quote (16 lines)
> On Sat, Oct 21, 2023 at 08:52:13PM +0200, Olav Smorholm wrote:
> >
>
> And call it, or view is it as you may; no trivial task to determine if
> the guix binary bug and crash was useful or not.
>
> But in the process, while for other things after; starting to study
> dmesg. Bluez and related things that awaken bluetooth kernel subsystems
> is less of an aesthetic problem.
>
> I react somewhat on PF_ALG especially, weird segfault that calls itself
> xsltproc, and that there even exist segfaults and protection faults as
> if checking for a kernel that is newer than minix era is
> necessary. As false positives and negatives for intent to hide even the
> oldest and most deprecated "hello world" crud.

I'm sure interesting talks can be had:

[73428.629504] ptrace attach of "/tmp/guix-build-libinput-minimal-1.22.1.drv-0/build/libinput-test-suite --filter-group=touchpad --xml-output=junit-touchpad-XXXXXX.xml"[417] was attempted by "/tmp/guix-build-libinput-minimal-1.22.1.drv-0/build/libinput-test-suite --filter-group=touchpad --xml-output=junit-touchpad-XXXXXX.xml"[419]
[73428.640092] ptrace attach of "/tmp/guix-build-libinput-minimal-1.22.1.drv-0/build/libinput-test-suite --filter-group=touchpad-tap --xml-output=junit-touchpad-tap-XXXXXX.xml"[420] was attempted by "/tmp/guix-build-libinput-minimal-1.22.1.drv-0/build/libinput-test-suite --filter-group=touchpad-tap --xml-output=junit-touchpad-tap-XXXXXX.xml"[422]
[75861.720983] traps: bonobo-activati[4394] trap int3 ip:7ffff7bf39cf sp:7fffffffbd80 error:0 in libglib-2.0.so.0.7200.3[7ffff7bb7000+88000]
[77216.387681] Bluetooth: Core ver 2.22
[77216.387730] NET: Registered PF_BLUETOOTH protocol family
[77216.387732] Bluetooth: HCI device and connection manager initialized
[77216.387739] Bluetooth: HCI socket layer initialized
[77216.387742] Bluetooth: L2CAP socket layer initialized
[77216.387748] Bluetooth: SCO socket layer initialized
[77917.396492] python[11571]: segfault at 0 ip 00007ffff75198c0 sp 00007fffffffb2c8 error 4 in _testcapi.so[7ffff7519000+6000] likely on CPU 10 (core 4, socket 0)
[77917.396513] Code: 00 48 83 00 01 c3 0f 1f 40 00 48 89 d0 48 85 d2 74 08 48 83 00 01 c3 0f 1f 00 48 8b 05 11 a7 00 00 48 83 00 01 c3 0f 1f 40 00 <8b> 04 25 00 00 00 00 0f 0b 0f 1f 80 00 00 00 00 48 83 ec 08 48 8b
[77971.483788] python[19206]: segfault at 0 ip 00007ffff75198c0 sp 00007fffffffb2c8 error 4 in _testcapi.so[7ffff7519000+6000] likely on CPU 10 (core 4, socket 0)
O
O
Olav Smorholm wrote on 23 Oct 2023 19:42
(address . 66610@debbugs.gnu.org)
4fmrdo2tsij4fpudxvnwj2kbksvgtfzwezesreqwwy7zdhbh6a@dwur22m7u7rt
On Mon, Oct 23, 2023 at 07:03:40PM +0200, Olav Smorholm wrote:
Toggle quote (33 lines)
> On Mon, Oct 23, 2023 at 06:48:26PM +0200, Olav Smorholm wrote:
> > On Sat, Oct 21, 2023 at 08:52:13PM +0200, Olav Smorholm wrote:
> > >
> >
> > And call it, or view is it as you may; no trivial task to determine if
> > the guix binary bug and crash was useful or not.
> >
> > But in the process, while for other things after; starting to study
> > dmesg. Bluez and related things that awaken bluetooth kernel subsystems
> > is less of an aesthetic problem.
> >
> > I react somewhat on PF_ALG especially, weird segfault that calls itself
> > xsltproc, and that there even exist segfaults and protection faults as
> > if checking for a kernel that is newer than minix era is
> > necessary. As false positives and negatives for intent to hide even the
> > oldest and most deprecated "hello world" crud.
>
> I'm sure interesting talks can be had:
>
> [73428.629504] ptrace attach of "/tmp/guix-build-libinput-minimal-1.22.1.drv-0/build/libinput-test-suite --filter-group=touchpad --xml-output=junit-touchpad-XXXXXX.xml"[417] was attempted by "/tmp/guix-build-libinput-minimal-1.22.1.drv-0/build/libinput-test-suite --filter-group=touchpad --xml-output=junit-touchpad-XXXXXX.xml"[419]
> [73428.640092] ptrace attach of "/tmp/guix-build-libinput-minimal-1.22.1.drv-0/build/libinput-test-suite --filter-group=touchpad-tap --xml-output=junit-touchpad-tap-XXXXXX.xml"[420] was attempted by "/tmp/guix-build-libinput-minimal-1.22.1.drv-0/build/libinput-test-suite --filter-group=touchpad-tap --xml-output=junit-touchpad-tap-XXXXXX.xml"[422]
> [75861.720983] traps: bonobo-activati[4394] trap int3 ip:7ffff7bf39cf sp:7fffffffbd80 error:0 in libglib-2.0.so.0.7200.3[7ffff7bb7000+88000]
> [77216.387681] Bluetooth: Core ver 2.22
> [77216.387730] NET: Registered PF_BLUETOOTH protocol family
> [77216.387732] Bluetooth: HCI device and connection manager initialized
> [77216.387739] Bluetooth: HCI socket layer initialized
> [77216.387742] Bluetooth: L2CAP socket layer initialized
> [77216.387748] Bluetooth: SCO socket layer initialized
> [77917.396492] python[11571]: segfault at 0 ip 00007ffff75198c0 sp 00007fffffffb2c8 error 4 in _testcapi.so[7ffff7519000+6000] likely on CPU 10 (core 4, socket 0)
> [77917.396513] Code: 00 48 83 00 01 c3 0f 1f 40 00 48 89 d0 48 85 d2 74 08 48 83 00 01 c3 0f 1f 00 48 8b 05 11 a7 00 00 48 83 00 01 c3 0f 1f 40 00 <8b> 04 25 00 00 00 00 0f 0b 0f 1f 80 00 00 00 00 48 83 ec 08 48 8b
> [77971.483788] python[19206]: segfault at 0 ip 00007ffff75198c0 sp 00007fffffffb2c8 error 4 in _testcapi.so[7ffff7519000+6000] likely on CPU 10 (core 4, socket 0)
>

Not sure if I have point, it's an argument at least.
That the guix binary is a bit of target for the classical problems
involved. And who knowns, maybe one can find a K&R "hello world" string
in a binary as the best and worst of it.

But this is inherently ugly, to see the measures and crud involved, with
awareness of developers that it touch upon sensitive subsystems.
And may very well make it more accessible for study, publications and
discussions if just shafted and most likely fale positives with academic
print og preprint review.
O
O
Olav Smorholm wrote on 23 Oct 2023 20:13
(address . 66610@debbugs.gnu.org)
55ucted3sj7c7ovxq3hzev3dcudo6vznzxk6aniym7zowknizj@srwkkn6qp3wv
On Mon, Oct 23, 2023 at 07:42:02PM +0200, Olav Smorholm wrote:
Toggle quote (46 lines)
> On Mon, Oct 23, 2023 at 07:03:40PM +0200, Olav Smorholm wrote:
> > On Mon, Oct 23, 2023 at 06:48:26PM +0200, Olav Smorholm wrote:
> > > On Sat, Oct 21, 2023 at 08:52:13PM +0200, Olav Smorholm wrote:
> > > >
> > >
> > > And call it, or view is it as you may; no trivial task to determine if
> > > the guix binary bug and crash was useful or not.
> > >
> > > But in the process, while for other things after; starting to study
> > > dmesg. Bluez and related things that awaken bluetooth kernel subsystems
> > > is less of an aesthetic problem.
> > >
> > > I react somewhat on PF_ALG especially, weird segfault that calls itself
> > > xsltproc, and that there even exist segfaults and protection faults as
> > > if checking for a kernel that is newer than minix era is
> > > necessary. As false positives and negatives for intent to hide even the
> > > oldest and most deprecated "hello world" crud.
> >
> > I'm sure interesting talks can be had:
> >
> > [73428.629504] ptrace attach of "/tmp/guix-build-libinput-minimal-1.22.1.drv-0/build/libinput-test-suite --filter-group=touchpad --xml-output=junit-touchpad-XXXXXX.xml"[417] was attempted by "/tmp/guix-build-libinput-minimal-1.22.1.drv-0/build/libinput-test-suite --filter-group=touchpad --xml-output=junit-touchpad-XXXXXX.xml"[419]
> > [73428.640092] ptrace attach of "/tmp/guix-build-libinput-minimal-1.22.1.drv-0/build/libinput-test-suite --filter-group=touchpad-tap --xml-output=junit-touchpad-tap-XXXXXX.xml"[420] was attempted by "/tmp/guix-build-libinput-minimal-1.22.1.drv-0/build/libinput-test-suite --filter-group=touchpad-tap --xml-output=junit-touchpad-tap-XXXXXX.xml"[422]
> > [75861.720983] traps: bonobo-activati[4394] trap int3 ip:7ffff7bf39cf sp:7fffffffbd80 error:0 in libglib-2.0.so.0.7200.3[7ffff7bb7000+88000]
> > [77216.387681] Bluetooth: Core ver 2.22
> > [77216.387730] NET: Registered PF_BLUETOOTH protocol family
> > [77216.387732] Bluetooth: HCI device and connection manager initialized
> > [77216.387739] Bluetooth: HCI socket layer initialized
> > [77216.387742] Bluetooth: L2CAP socket layer initialized
> > [77216.387748] Bluetooth: SCO socket layer initialized
> > [77917.396492] python[11571]: segfault at 0 ip 00007ffff75198c0 sp 00007fffffffb2c8 error 4 in _testcapi.so[7ffff7519000+6000] likely on CPU 10 (core 4, socket 0)
> > [77917.396513] Code: 00 48 83 00 01 c3 0f 1f 40 00 48 89 d0 48 85 d2 74 08 48 83 00 01 c3 0f 1f 00 48 8b 05 11 a7 00 00 48 83 00 01 c3 0f 1f 40 00 <8b> 04 25 00 00 00 00 0f 0b 0f 1f 80 00 00 00 00 48 83 ec 08 48 8b
> > [77971.483788] python[19206]: segfault at 0 ip 00007ffff75198c0 sp 00007fffffffb2c8 error 4 in _testcapi.so[7ffff7519000+6000] likely on CPU 10 (core 4, socket 0)
> >
>
> Not sure if I have point, it's an argument at least.
> That the guix binary is a bit of target for the classical problems
> involved. And who knowns, maybe one can find a K&R "hello world" string
> in a binary as the best and worst of it.
>
> But this is inherently ugly, to see the measures and crud involved, with
> awareness of developers that it touch upon sensitive subsystems.
> And may very well make it more accessible for study, publications and
> discussions if just shafted and most likely fale positives with academic
> print og preprint review.
>

[148083.517777] Code: Unable to access opcode bytes at 0xffffffffffffffd6.
[148083.518475] test_regression[21751]: segfault at 0 ip 0000000000000000 sp 00007fffffffb998 error 14 in test_regression[400000+11000] likely on CPU 11 (core 5, socket 0)
[148083.518484] Code: Unable to access opcode bytes at 0xffffffffffffffd6.
[148083.519137] test_regression[21752]: segfault at 0 ip 0000000000000000 sp 00007fffffffb998 error 14 in test_regression[400000+11000] likely on CPU 11 (core 5, socket 0)

224051.720066] traps: recentmanager[889] trap int3 ip:7ffff7ee5787 sp:7fffffff5a40 error:0 in libglib-2.0.so.0.7200.3[7ffff7ea7000+88000]

[224450.718378] i915 0000:83:00.0: [drm] *ERROR* Atomic update failure on pipe B (start=174286 end=174287) time 130 us, min 1073, max 1079, scanline start 1071, end 1072
[243753.929744] i915 0000:83:00.0: [drm] *ERROR* Atomic update failure on pipe B (start=1332500 end=1332501) time 155 us, min 1073, max 1079, scanline start 1072, end 1073

The latter of which is icecat i believe.

I at the very least understanding things like CPU pipelines and vector
machines and how they differ. Which can be stated in short terms as
modern CPU's are vector machines inherently. You translate your
instructions into simpler operations that can run faster in the central
logic, or you a fast internal part with several units that translate
onto it and are willing to brute force a soltion if need be.
O
O
Olav Smorholm wrote on 17 Nov 2023 20:37
(address . 66610@debbugs.gnu.org)
3e3qyn7mae4vvthmn7gxc7x3qyam5gv26kk3hw5r37a26bvm4f@fzn2cf3efjon
Attachment: file
O
O
Olav Smorholm wrote on 17 Nov 2023 20:55
(address . 66610@debbugs.gnu.org)
di6qyzu6x46vt5dmoha37uth6eosruhlcsagtbrouvdcqjwynj@ohvddvjjnuqj
Attachment: file
O
O
Olav Smorholm wrote on 17 Nov 2023 21:16
(address . 66610@debbugs.gnu.org)
vbd3dounu2nyxv7jfrgr5hinwxjafzjtcsnb4gd2w2h7e6g56r@gpwbd5lbgben
On Fri, Nov 17, 2023 at 08:55:08PM +0100, Olav Smorholm wrote:
Toggle quote (5 lines)
> Binary or what not, I boldly take this as community confirmation of the
> bug report, and admittance of usage. With a huge what-if, and if-only-if
> where lines to do not cross internally in non-profit or for profit
> organisation with isolated soap boax requests and issues.

Now, Imagine you are me:

Working on AVX in 2012 for GEANT at CERN paid for by Intel after.
With no high school degree.
And while with on resolution to TBI in inferior parietal lobe.
I do whole genome sequencing and the west atlantic trade route from
Norway in early Viking age shows up at gedmatc.com, I'm 0.1% lebanese
jew, and closer to 3% moroccan in top 10 admixes, and it includes
Saami mtDNA in the Berber ancestral population. If it is like water,
some social borders and structures I may naturally sail it.
O
O
Olav Smorholm wrote on 17 Nov 2023 21:40
(address . 66610@debbugs.gnu.org)
dbwkkfg6gqm7sdeyzlcds2ne7ufam4tandhlx56s5qtzogzltf@tpmsofjp3y35
On Fri, Nov 17, 2023 at 09:16:33PM +0100, Olav Smorholm wrote:
Toggle quote (3 lines)
> Working on AVX in 2012 for GEANT at CERN paid for by Intel after.
> With no high school degree.

I will be captain obvious for something I'm not certain about, but I am
in a matter of ways in dialogue with Intel Liaoson to CERN.
That IT department of Intel, they also did and were interest in
frameworks I were interested in, during early interaction in OpenLab.
Something implicit may need to be said, there is a division in
semiconductor companies between researchers and services.
The latter cant ask, and the former cant request work that they just
can't do easily or quickly.

So iif I pretend to be RMS here, it's one thing over the other, and
provide commenty for open assembly code if need be.
O
O
Olav Smorholm wrote on 17 Nov 2023 22:24
(address . 66610@debbugs.gnu.org)
zfmwa22llg4tnnpqrukxd3etuybeqaz25doddntk35qkasy6dk@de4hzqejuoyw
On Fri, Nov 17, 2023 at 09:40:38PM +0100, Olav Smorholm wrote:
Toggle quote (16 lines)
> On Fri, Nov 17, 2023 at 09:16:33PM +0100, Olav Smorholm wrote:
> > Working on AVX in 2012 for GEANT at CERN paid for by Intel after.
> > With no high school degree.
>
> I will be captain obvious for something I'm not certain about, but I am
> in a matter of ways in dialogue with Intel Liaoson to CERN.
> That IT department of Intel, they also did and were interest in
> frameworks I were interested in, during early interaction in OpenLab.
> Something implicit may need to be said, there is a division in
> semiconductor companies between researchers and services.
> The latter cant ask, and the former cant request work that they just
> can't do easily or quickly.
>
> So iif I pretend to be RMS here, it's one thing over the other, and
> provide commenty for open assembly code if need be.
>
In other words, there is a definition of the number line that involves
integers, fractions and complex numbers with no negative numbers.
O
O
Olav Smorholm wrote on 17 Nov 2023 23:59
(address . 66610@debbugs.gnu.org)
apfjfkx3uzuxnisyigl2b7pdqhzzfvkvlnbgtl4oqjw45bzmr4@g7go6gtaux5b
On Fri, Nov 17, 2023 at 10:24:01PM +0100, Olav Smorholm wrote:
Toggle quote (21 lines)
> On Fri, Nov 17, 2023 at 09:40:38PM +0100, Olav Smorholm wrote:
> > On Fri, Nov 17, 2023 at 09:16:33PM +0100, Olav Smorholm wrote:
> > > Working on AVX in 2012 for GEANT at CERN paid for by Intel after.
> > > With no high school degree.
> >
> > I will be captain obvious for something I'm not certain about, but I am
> > in a matter of ways in dialogue with Intel Liaoson to CERN.
> > That IT department of Intel, they also did and were interest in
> > frameworks I were interested in, during early interaction in OpenLab.
> > Something implicit may need to be said, there is a division in
> > semiconductor companies between researchers and services.
> > The latter cant ask, and the former cant request work that they just
> > can't do easily or quickly.
> >
> > So iif I pretend to be RMS here, it's one thing over the other, and
> > provide commenty for open assembly code if need be.
> >
> In other words, there is a definition of the number line that involves
> integers, fractions and complex numbers with no negative numbers.



I struggled with this one, I am in some models more cloesly related to
CEU than the rest of Scandinavia. You are welcome, to this dsicprenacy
and divide. It does mean, native with ancestry.
O
O
Olav Smorholm wrote on 18 Nov 2023 00:16
(address . 66610@debbugs.gnu.org)
yesgvvgxv7ls22v3vceotuwloiiawaxa7b2b2523cozfgs7sve@jjmde5inveeo
On Fri, Nov 17, 2023 at 11:59:45PM +0100, Olav Smorholm wrote:
Toggle quote (28 lines)
> On Fri, Nov 17, 2023 at 10:24:01PM +0100, Olav Smorholm wrote:
> > On Fri, Nov 17, 2023 at 09:40:38PM +0100, Olav Smorholm wrote:
> > > On Fri, Nov 17, 2023 at 09:16:33PM +0100, Olav Smorholm wrote:
> > > > Working on AVX in 2012 for GEANT at CERN paid for by Intel after.
> > > > With no high school degree.
> > >
> > > I will be captain obvious for something I'm not certain about, but I am
> > > in a matter of ways in dialogue with Intel Liaoson to CERN.
> > > That IT department of Intel, they also did and were interest in
> > > frameworks I were interested in, during early interaction in OpenLab.
> > > Something implicit may need to be said, there is a division in
> > > semiconductor companies between researchers and services.
> > > The latter cant ask, and the former cant request work that they just
> > > can't do easily or quickly.
> > >
> > > So iif I pretend to be RMS here, it's one thing over the other, and
> > > provide commenty for open assembly code if need be.
> > >
> > In other words, there is a definition of the number line that involves
> > integers, fractions and complex numbers with no negative numbers.
>
>
> https://www.internationalgenome.org/faq/what-do-the-population-codes-mean/
>
> I struggled with this one, I am in some models more cloesly related to
> CEU than the rest of Scandinavia. You are welcome, to this dsicprenacy
> and divide. It does mean, native with ancestry.

And I am borderline, and ifit isn't enough comfort.
I have peggeed https://surfer.nmr.mgh.harvard.edu/as possibly the best
place to get a TBI diagnostics, but I am being blocked by the front desk
at MGH.

Suck on that.
O
O
Olav Smorholm wrote on 8 Dec 2023 01:17
(address . 66610@debbugs.gnu.org)
3qviawckqhsbt3ciomkcdrin5hcdtg7xihru6oewxwvppf4sdj@lafn42bl2va6
On Sat, Nov 18, 2023 at 12:16:54AM +0100, Olav Smorholm wrote:
Toggle quote (36 lines)
> On Fri, Nov 17, 2023 at 11:59:45PM +0100, Olav Smorholm wrote:
> > On Fri, Nov 17, 2023 at 10:24:01PM +0100, Olav Smorholm wrote:
> > > On Fri, Nov 17, 2023 at 09:40:38PM +0100, Olav Smorholm wrote:
> > > > On Fri, Nov 17, 2023 at 09:16:33PM +0100, Olav Smorholm wrote:
> > > > > Working on AVX in 2012 for GEANT at CERN paid for by Intel after.
> > > > > With no high school degree.
> > > >
> > > > I will be captain obvious for something I'm not certain about, but I am
> > > > in a matter of ways in dialogue with Intel Liaoson to CERN.
> > > > That IT department of Intel, they also did and were interest in
> > > > frameworks I were interested in, during early interaction in OpenLab.
> > > > Something implicit may need to be said, there is a division in
> > > > semiconductor companies between researchers and services.
> > > > The latter cant ask, and the former cant request work that they just
> > > > can't do easily or quickly.
> > > >
> > > > So iif I pretend to be RMS here, it's one thing over the other, and
> > > > provide commenty for open assembly code if need be.
> > > >
> > > In other words, there is a definition of the number line that involves
> > > integers, fractions and complex numbers with no negative numbers.
> >
> >
> > https://www.internationalgenome.org/faq/what-do-the-population-codes-mean/
> >
> > I struggled with this one, I am in some models more cloesly related to
> > CEU than the rest of Scandinavia. You are welcome, to this dsicprenacy
> > and divide. It does mean, native with ancestry.
>
> And I am borderline, and ifit isn't enough comfort.
> I have peggeed https://surfer.nmr.mgh.harvard.edu/ as possibly the best
> place to get a TBI diagnostics, but I am being blocked by the front desk
> at MGH.
>
> Suck on that.
>
And rantn and digression set aside.
I will have this screwed.
You don't win any wards with a piece of shit build systems from
disregard of giants and titans that made is possible.

Wnile publications like mine serve as insurance against medical
malpractice.
M
M
Maxim Cournoyer wrote on 19 Dec 2023 06:20
Re: bug#66610: potrace, po4a; guix bug, complete console output
(name . Olav Smorholm)(address . olavks@gmail.com)(address . 66610@debbugs.gnu.org)
87zfy66a59.fsf_-_@gmail.com
Hi Olav,

[...]

Thanks for the initial bug report about a po4a non reproducible segfault
(did I get this right?).

Please refrain from posting unrelated things to this report, as that's
lowering the signal to noise ratio and making it less likely that
someone is interested in reading your future replies.

--
Thanks,
Maxim
?