Flexible I/O Tester development
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: Jeff Furlong <jeff.furlong@hgst.com>,
	Sitsofe Wheeler <sitsofe@gmail.com>
Cc: "fio@vger.kernel.org" <fio@vger.kernel.org>, Jan Kara <jack@suse.cz>
Subject: Re: fio signal 11
Date: Mon, 13 Jun 2016 12:01:49 -0600	[thread overview]
Message-ID: <575EF50D.5010005@kernel.dk> (raw)
In-Reply-To: <BN3PR0401MB1457AD48DF8406D550343DC6F7530@BN3PR0401MB1457.namprd04.prod.outlook.com>

On 06/13/2016 11:58 AM, Jeff Furlong wrote:
> I'd like to use the latest git version so that I can pickup patch 356014ff351c6eb69339652650af5f6af72e5c22 to fix the ramp time issue.
>
> I tried the latest git version fio-2.11-21-g2b762, but got a new issue:
>
> [New LWP 120298]
> [New LWP 120281]
> [Thread debugging using libthread_db enabled]
> Using host libthread_db library "/lib64/libthread_db.so.1".
> Core was generated by `fio --name=test_job --ioengine=libaio --direct=1 --rw=write --iodepth=32'.
> Program terminated with signal 11, Segmentation fault.
> #0  __add_log_sample (iolog=iolog@entry=0x7f8376222c30, val=2230, ddir=ddir@entry=DDIR_WRITE, bs=bs@entry=0, t=t@entry=1056000,
>      offset=offset@entry=0) at stat.c:2015
> 2015			s->val = val;
> (gdb) bt
> #0  __add_log_sample (iolog=iolog@entry=0x7f8376222c30, val=2230, ddir=ddir@entry=DDIR_WRITE, bs=bs@entry=0, t=t@entry=1056000,
>      offset=offset@entry=0) at stat.c:2015
> #1  0x0000000000422411 in __add_log_sample (offset=0, t=1056000, bs=0, ddir=DDIR_WRITE, val=<optimized out>, iolog=0x7f8376222c30)
>      at stat.c:2004
> #2  __add_stat_to_log (log_max=<optimized out>, elapsed=1056000, ddir=DDIR_WRITE, iolog=0x7f8376222c30) at stat.c:2091
> #3  _add_stat_to_log (log_max=<optimized out>, elapsed=<optimized out>, iolog=0x7f8376222c30) at stat.c:2103
> #4  add_log_sample (td=td@entry=0x7f8361f3d000, iolog=0x7f8376222c30, val=2230, ddir=ddir@entry=DDIR_WRITE, bs=1048576,
>      offset=offset@entry=0) at stat.c:2139
> #5  0x000000000042f45f in add_log_sample (offset=0, bs=<optimized out>, ddir=DDIR_WRITE, val=<optimized out>, iolog=<optimized out>,
>      td=0x7f8361f3d000) at stat.c:2357
> #6  add_iops_samples (t=0x7f835a4bae50, td=0x7f8361f3d000) at stat.c:2362
> #7  calc_log_samples () at stat.c:2402
> #8  0x0000000000467508 in helper_thread_main (data=0x7f8376222d90) at helper_thread.c:125
> #9  0x00007f8377e7cdf5 in start_thread () from /lib64/libpthread.so.0
> #10 0x00007f83779a61ad in clone () from /lib64/libc.so.6
>
> Maybe I should try the ramp time patch only on 2.11 release?

What did you run to cause this crash? Looks like only some of the 
arguments got shown.

-- 
Jens Axboe



  reply	other threads:[~2016-06-13 18:01 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-09 21:58 fio signal 11 Jeff Furlong
2016-06-10  7:17 ` Sitsofe Wheeler
2016-06-10 18:42   ` Jeff Furlong
2016-06-12  2:56     ` Jens Axboe
2016-06-12  3:30       ` Jens Axboe
2016-06-13 17:58         ` Jeff Furlong
2016-06-13 18:01           ` Jens Axboe [this message]
2016-06-13 18:04             ` Jeff Furlong
2016-06-13 19:21               ` Jeff Furlong
2016-06-13 19:23                 ` Jens Axboe
2016-06-13 19:34                   ` Jens Axboe
2016-06-13 20:55                     ` Jeff Furlong
2016-06-13 21:23                       ` Jens Axboe
2016-06-15 14:45         ` Jan Kara
2016-06-16  7:06           ` Jens Axboe
2016-07-20  5:08             ` Jan Kara
2016-07-25 15:21               ` Jens Axboe
2016-07-26  8:43                 ` Jan Kara
2016-07-26 14:17                   ` Jens Axboe
2016-07-26 18:33                     ` Jeff Furlong
2016-07-26 18:35                       ` Jens Axboe
2016-08-01 22:57                         ` Jeff Furlong
2016-08-02 21:03                           ` Jens Axboe
2016-08-03 14:55                           ` Jens Axboe
2016-08-03 15:02                             ` Jeff Furlong
2016-08-03 15:03                               ` Jens Axboe
2016-08-03 15:14                                 ` Jens Axboe
2016-08-03 15:29                                   ` Jeff Furlong

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=575EF50D.5010005@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=fio@vger.kernel.org \
    --cc=jack@suse.cz \
    --cc=jeff.furlong@hgst.com \
    --cc=sitsofe@gmail.com \
    /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