From: mikhail <mikhail.v.gavrilov@gmail.com>
To: "Darrick J. Wong" <darrick.wong@oracle.com>
Cc: linux-xfs@vger.kernel.org, "linux-mm@kvack.org" <linux-mm@kvack.org>
Subject: Re: Google Chrome cause locks held in system (kernel 4.15 rc2)
Date: Sat, 09 Dec 2017 17:31:26 +0500 [thread overview]
Message-ID: <1512822686.4168.4.camel@gmail.com> (raw)
In-Reply-To: <20171208040556.GG19219@magnolia>
On Thu, 2017-12-07 at 20:05 -0800, Darrick J. Wong wrote:
> > Hi, can anybody said what here happens? And which info needed for
> > fixing it? Thanks. [16712.376081] INFO: task tracker-store:27121
> > blocked for more than 120 seconds. [16712.376088] Not tainted
> > 4.15.0-rc2-amd-vega+ #10 [16712.376092] "echo 0 >
> > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
> > [16712.376095] tracker-store D13400 27121 1843 0x00000000
> > [16712.376102] Call Trace: [16712.376114] ? __schedule+0x2e3/0xb90
> > [16712.376123] ? wait_for_completion+0x146/0x1e0 [16712.376128]
> > schedule+0x2f/0x90 [16712.376132] schedule_timeout+0x236/0x540
> > [16712.376143] ? mark_held_locks+0x4e/0x80 [16712.376147] ?
> > _raw_spin_unlock_irq+0x29/0x40 [16712.376153] ?
> > wait_for_completion+0x146/0x1e0 [16712.376158]
> > wait_for_completion+0x16e/0x1e0 [16712.376162] ?
> > wake_up_q+0x70/0x70 [16712.376204] ? xfs_buf_read_map+0x134/0x2f0
> > [xfs] [16712.376234] xfs_buf_submit_wait+0xaf/0x520 [xfs]
>
>
Stuck waiting for a directory block to read.
> Slow disk?
Usual Seagate SATA3 HDD with 7200rpms
> Bad media?
No. If there were problems with the hard drive, we would see errors in
the logs.
Any way you can sure in this if look at smartctl output for HDD.
https://paste.fedoraproject.org/paste/EsELRXoiKzlkR5PYhVmJeg
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2017-12-09 12:31 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-08 3:50 mikhail
2017-12-08 4:05 ` Darrick J. Wong
2017-12-08 10:18 ` Tetsuo Handa
2017-12-09 13:17 ` mikhail
2017-12-09 14:14 ` Tetsuo Handa
2017-12-10 21:49 ` mikhail
2017-12-11 0:14 ` Tetsuo Handa
2017-12-11 3:34 ` mikhail
2017-12-11 3:48 ` Tetsuo Handa
2018-01-06 14:17 ` mikhail
2018-01-06 14:52 ` Tetsuo Handa
2018-01-06 15:28 ` mikhail
2018-01-06 15:48 ` Tetsuo Handa
2018-01-06 17:24 ` mikhail
2018-01-07 3:42 ` Tetsuo Handa
2017-12-09 12:31 ` mikhail [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-12-08 3:48 mikhail
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=1512822686.4168.4.camel@gmail.com \
--to=mikhail.v.gavrilov@gmail.com \
--cc=darrick.wong@oracle.com \
--cc=linux-mm@kvack.org \
--cc=linux-xfs@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