From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Message-ID: <53BFCF22.8020407@kernel.dk> Date: Fri, 11 Jul 2014 13:48:50 +0200 From: Jens Axboe MIME-Version: 1.0 Subject: Re: fio hangs with --status-interval References: <53BE5286.2060203@kernel.dk> <53BEF29E.3040500@kernel.dk> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit To: Michael Mattsson Cc: fio@vger.kernel.org List-ID: 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: > [] ? unlock_page+0x27/0x30 > [] ? get_futex_key+0x180/0x2b0 > [] futex_wait_queue_me+0xb9/0xf0 > [] futex_wait+0x1f8/0x380 > [] ? __switch_to+0x26e/0x320 > [] do_futex+0x121/0xb50 > [] ? lock_hrtimer_base+0x31/0x60 > [] ? hrtimer_try_to_cancel+0x3f/0xd0 > [] ? hrtimer_cancel+0x22/0x30 > [] ? do_nanosleep+0x93/0xc0 > [] ? hrtimer_nanosleep+0xc4/0x180 > [] sys_futex+0x7b/0x170 > [] ? audit_syscall_entry+0x1d7/0x200 > [] ? __audit_syscall_exit+0x25e/0x290 > [] 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