On 04/01/2026 21:07, Samuel Thibault wrote:
Hello,
Michael Kelly, le dim. 04 janv. 2026 20:28:42 +0000, a ecrit:
stress-ng: fail: [3947] vm: detected 141733920769 bit errors while
stressing memory
stress-ng: fail: [3984] vm: detected 2 bit errors while stressing memory
That's the good news. The bad news is that I suspect the cause is related to
the handling of the signals which are used to terminate the stress-ng worker
(oomable child).
That'd still be useful to fix :)
I'm seeing corruption issues with the haskell ghc compiler, see
https://buildd.debian.org/status/fetch.php?pkg=ghc&arch=hurd-amd64&ver=9.10.3-1&stamp=1767477002&raw=0
I have to disable preemption to get the x86_64 build going, while the
i386 build goes fine.
Has the 'pending signal handling' fix helped with the building of the
ghc package ?
I hadn't had any luck reproducing these memory/disk corruption issues
whilst specifically trying to find a test case. I did however see a
similar result whilst compiling gnumach locally one time since then
including the output:
./kern/mach.server.h:1:2: error: stray ‘@’ in program
1 | #ifndef _mach_server_
| ^
./kern/mach.server.h:1:3: warning: null character(s) ignored
1 | #ifndef _mach_server_
| ^
./kern/mach.server.h:1:5: error: stray ‘\1’ in program
1 | #ifndef _mach_server_
| ^
The compilation succeeded normally upon immediately resuming the build.
I'd like to start working on this again. Is it possible for someone like
myself to search all of the hurd build logs to look for instances of
similar compilation issues?
Mike.
