stress-ng --lockmix 1 crashes with *** fatal error - NtCreateEvent(lock): 0xC0000035

Cedric Blancher cedric.blancher@gmail.com
Tue Nov 12 18:52:00 GMT 2024


On Tue, 12 Nov 2024 at 15:29, Sebastian Feld via Cygwin
<cygwin@cygwin.com> wrote:
>
> stress-ng --lockmix 1 crashes on CYGWIN_NT-10.0-19045
> 3.6.0-0.229.g87cd4f3fbd06.x86_64
>
> $ stress-ng --lockmix 1
> stress-ng: info:  [174] defaulting to a 1 day run per stressor
> stress-ng: info:  [174] dispatching hogs: 1 lockmix
> stress-ng: info:  [175] lockmix: exercising file lock types: flock locka lockf
>       0 [main] stress-ng 175 C:\cygwin64\bin\stress-ng.exe: *** fatal
> error - NtCreateEvent(lock): 0xC0000035
>                              stress-ng: warn:  [174] metrics-check:
> all bogo-op counters are zero, data may be incorrect
> stress-ng: info:  [174] skipped: 0
> stress-ng: info:  [174] passed: 1: lockmix (1)
> stress-ng: info:  [174] failed: 0
> stress-ng: info:  [174] metrics untrustworthy: 0
> stress-ng: info:  [174] unsuccessful run completed in 1.28 sec
> $ stress-ng: fail:  [176] lockmix: fcntl F_SETLK failed, errno=14 (Bad address)
>
> Sebi

OUCH

I thought this was fixed with
https://cygwin.com/git/?p=newlib-cygwin.git;a=commit;h=ae181b0ff1226cf38be8a7f03ff19bf869c87f54

@Takashi Did you try to run stress-ng --lockmix 1 with your patches applied?

Ced

--
Cedric Blancher <cedric.blancher@gmail.com>
[https://plus.google.com/u/0/+CedricBlancher/]
Institute Pasteur


More information about the Cygwin mailing list