From: Jens Axboe <axboe@kernel.dk>
To: Michael Mattsson <michael.mattsson@gmail.com>
Cc: fio@vger.kernel.org
Subject: Re: fio hangs with --status-interval
Date: Fri, 11 Jul 2014 13:48:50 +0200 [thread overview]
Message-ID: <53BFCF22.8020407@kernel.dk> (raw)
In-Reply-To: <CAE56cDv7UmeGN=1rwyhbv7v5LfUkv+ueOoi+6KhnaXZYNx_7Fg@mail.gmail.com>
On 2014-07-10 23:27, Michael Mattsson wrote:
> Hey,
> I don't get any kernel messages about stuck processes. echo t >
> /proc/sysrq-trigger gives the following related to fio:
>
> fio S 0000000000000004 0 4189 3638 0x00000080
> ffff8817a0fd5bf8 0000000000000086 0000000000000000 ffffffff8111f867
> ffff8817a0fd5d01 00007fa2f43b6000 ffff8817a0fd5bd8 ffffffff810aec10
> ffff88186b867ab8 ffff8817a0fd5fd8 000000000000fbc8 ffff88186b867ab8
> Call Trace:
> [<ffffffff8111f867>] ? unlock_page+0x27/0x30
> [<ffffffff810aec10>] ? get_futex_key+0x180/0x2b0
> [<ffffffff810ae559>] futex_wait_queue_me+0xb9/0xf0
> [<ffffffff810af668>] futex_wait+0x1f8/0x380
> [<ffffffff8100988e>] ? __switch_to+0x26e/0x320
> [<ffffffff810b0f31>] do_futex+0x121/0xb50
> [<ffffffff8109f491>] ? lock_hrtimer_base+0x31/0x60
> [<ffffffff810a010f>] ? hrtimer_try_to_cancel+0x3f/0xd0
> [<ffffffff810a01c2>] ? hrtimer_cancel+0x22/0x30
> [<ffffffff8152a413>] ? do_nanosleep+0x93/0xc0
> [<ffffffff810a0294>] ? hrtimer_nanosleep+0xc4/0x180
> [<ffffffff810b19db>] sys_futex+0x7b/0x170
> [<ffffffff810e1e87>] ? audit_syscall_entry+0x1d7/0x200
> [<ffffffff810e1c7e>] ? __audit_syscall_exit+0x25e/0x290
> [<ffffffff8100b072>] system_call_fastpath+0x16/0x1b
OK, so nothing unexpected there. But it's all still very weird. Could
you try and attach gdb to a fio process that is stuck like this, and
generate 'bt' backtraces?
--
Jens Axboe
next prev parent reply other threads:[~2014-07-11 11:48 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-09 22:56 fio hangs with --status-interval Michael Mattsson
2014-07-10 8:44 ` Jens Axboe
2014-07-10 14:55 ` Michael Mattsson
2014-07-10 20:07 ` Jens Axboe
2014-07-10 21:27 ` Michael Mattsson
2014-07-11 11:48 ` Jens Axboe [this message]
2014-07-11 16:19 ` Michael Mattsson
2014-07-12 8:42 ` Jens Axboe
2014-07-16 16:58 ` Vasily Tarasov
2014-07-21 8:08 ` Jens Axboe
2014-07-21 20:25 ` Vasily Tarasov
2014-07-21 20:54 ` Jens Axboe
2014-07-25 7:43 ` Jens Axboe
2014-07-25 7:56 ` Jens Axboe
2014-07-25 16:34 ` Vasily Tarasov
2014-07-28 8:56 ` Jens Axboe
2014-07-28 16:05 ` Vasily Tarasov
2014-07-28 19:49 ` Jens Axboe
2014-10-23 15:57 ` Michael Mattsson
2014-10-23 16:01 ` Jens Axboe
2014-10-23 21:58 ` Michael Mattsson
2014-10-24 5:17 ` Jens Axboe
2014-10-24 15:33 ` Michael Mattsson
2014-10-24 15:50 ` Jens Axboe
2014-11-04 15:46 ` Vasily Tarasov
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=53BFCF22.8020407@kernel.dk \
--to=axboe@kernel.dk \
--cc=fio@vger.kernel.org \
--cc=michael.mattsson@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.