From: Sitsofe Wheeler <sitsofe@yahoo.com>
To: "Elliott, Robert (Server Storage)" <Elliott@hp.com>
Cc: Bruce Cran <bruce@cran.org.uk>,
"fio@vger.kernel.org" <fio@vger.kernel.org>
Subject: Re: fio 2.1.4 intermittently crashes on windows
Date: Mon, 27 Jan 2014 20:46:31 +0000 [thread overview]
Message-ID: <20140127204630.GA1150@sucs.org> (raw)
In-Reply-To: <94D0CD8314A33A4D9D801C0FE68B402954874EEC@G4W3202.americas.hpqcorp.net>
On Fri, Jan 10, 2014 at 04:46:05PM +0000, Elliott, Robert (Server Storage) wrote:
> 3. The assert does not trigger, and the same crash occurs as before.
>
> C:\Users\Administrator\fio>c:\cygwin64\bin\gdb -args "c:/program files/fio/fio.exe" --filename=rob.tmp --size=128m --direct=1 --rw=randread --refill_buffers --norandommap --randrepeat=0 --bs=4k --iodepth=16 --numjobs=16 --runtime=60 --group_reporting --name=4ktest --time_based
> Jobs: 0 (f=0)
> Program received signal SIGSEGV, Segmentation fault.
> 0x0000000064943236 in pthread_mutex_unlock ()
> from /cygdrive/c/program files/fio/libwinpthread-1.dll
I've finally had time to reproduce this on a Windows 7 box. I use a
different command line:
./fio.exe --debug=all --filename=fiojob --thread --size=512 --rw=read --bs=512 --ioengine=sync --verify_pattern=0xdeadbeef --name=fiojobname
The problem appears to be that the mutex is being destroyed while it is
still being held by a different thread. Adding return; to the first line
of fio_mutex_remove in mutex.c papers over the problem...
--
Sitsofe | http://sucs.org/~sits/
next prev parent reply other threads:[~2014-01-27 20:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-28 1:42 fio 2.1.4 intermittently crashes on windows Todd Dworshak
2013-12-28 2:12 ` Bruce Cran
2014-01-08 22:02 ` Todd Dworshak
2014-01-09 1:07 ` Elliott, Robert (Server Storage)
2014-01-09 2:32 ` Todd Dworshak
2014-01-09 6:37 ` Sitsofe Wheeler
[not found] ` <94D0CD8314A33A4D9D801C0FE68B4029548744AD@G4W3202.americas.hpqcorp.net>
2014-01-10 5:21 ` Sitsofe Wheeler
2014-01-10 6:11 ` Bruce Cran
2014-01-10 16:46 ` Elliott, Robert (Server Storage)
2014-01-27 20:46 ` Sitsofe Wheeler [this message]
2014-01-28 21:08 ` Bruce Cran
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=20140127204630.GA1150@sucs.org \
--to=sitsofe@yahoo.com \
--cc=Elliott@hp.com \
--cc=bruce@cran.org.uk \
--cc=fio@vger.kernel.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox