public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Artem Bityutskiy <dedekind1@gmail.com>
To: Norbert van Bolhuis <nvbolhuis@aimvalley.nl>
Cc: linux-mtd <linux-mtd@lists.infradead.org>
Subject: Re: a UBIFS image makes task pdflush blocked > 120 seconds
Date: Sun, 11 Oct 2009 17:04:12 +0300	[thread overview]
Message-ID: <1255269852.16942.105.camel@localhost> (raw)
In-Reply-To: <4ACF3478.1060503@aimvalley.nl>

On Fri, 2009-10-09 at 15:02 +0200, Norbert van Bolhuis wrote:
> We're using a 19MB UBIFS image (preprogrammed by manufacturing)
> for a 156 MB NOR flash partition.
> 
> As soon as some of our application processes start reading/writing
> to the UBIFS the below message occurs:
> 
> INFO: task pdflush:110 blocked for more than 120 seconds.
> "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
> pdflush       D 00000000     0   110      2
> 
> the below call trace belongs to the message:
> 
> [ceb6fc10] [c0008b24] 0xc0008b24
> [ceb6fc30] [c029b9a8] 0xc029b9a8 schedule
> [ceb6fc80] [c029c8c8] 0xc029c8c8 __mutex_lock_slowpath
> [ceb6fcb0] [c014211c] 0xc014211c make_reservation
> [ceb6fd20] [c014291c] 0xc014291c ubifs_jnl_write_inode
> [ceb6fd60] [c0149cc8] 0xc0149cc8 ubifs_write_inode
> [ceb6fd80] [c0145bbc] 0xc0145bbc ubifs_writepage
> [ceb6fdb0] [c005b0b8] 0xc005b0b8 __writepage
> [ceb6fdc0] [c005b8dc] 0xc005b8dc write_cache_pages
> [ceb6fe60] [c005ba50] 0xc005ba50 do_writepages
> [ceb6fe70] [c00a35cc] 0xc00a35cc __writeback_single_inode
> [ceb6fec0] [c00a3b90] 0xc00a3b90 generic_sync_sb_inodes
> [ceb6ff00] [c00a4330] 0xc00a4330 writeback_inodes
> [ceb6ff20] [c005c774] 0xc005c774 wb_kupdate
> [ceb6ff80] [c005cf70] 0xc005cf70 pdflush
> [ceb6ffd0] [c003bd30] 0xc003bd30
> [ceb6fff0] [c0011480] 0xc0011480

Does the stackdump always look like this?

Also, it is probably not commit_sem, because __mutex_lock_slowpath
is about mutexes, so this is about
mutex_lock_nested(&wbuf->io_mutex, wbuf->jhead);

-- 
Best Regards,
Artem Bityutskiy (Артём Битюцкий)

  parent reply	other threads:[~2009-10-11 14:04 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-09 13:02 a UBIFS image makes task pdflush blocked > 120 seconds Norbert van Bolhuis
2009-10-11 13:52 ` Artem Bityutskiy
2009-10-12 10:09   ` Norbert van Bolhuis
2009-10-14  8:56     ` Artem Bityutskiy
2009-11-11 15:54       ` Norbert van Bolhuis
2009-11-13  8:20         ` Artem Bityutskiy
2009-11-13 15:09           ` Norbert van Bolhuis
2009-11-13 15:52             ` Artem Bityutskiy
2009-11-13 15:56               ` Artem Bityutskiy
2009-11-13 16:28               ` Joakim Tjernlund
2009-10-11 14:04 ` Artem Bityutskiy [this message]
2009-10-11 14:09   ` Artem Bityutskiy
     [not found] <34637.10.10.0.184.1258202287.squirrel@intranet.aimsys.nl>
2009-11-16  8:13 ` Artem Bityutskiy
2009-11-16  8:53   ` Joakim Tjernlund
2009-11-16 23:22     ` Jamie Lokier
2009-11-17  8:31       ` Joakim Tjernlund
2009-11-17 10:45       ` Norbert van Bolhuis
     [not found] <4B012D0D.4080500@aimvalley.nl>
2009-11-16 12:12 ` Joakim Tjernlund
2009-11-17  8:25 ` Artem Bityutskiy
2009-11-17 16:25   ` Norbert van Bolhuis
2009-11-18  8:28     ` Artem Bityutskiy
2009-11-18  9:26       ` Norbert van Bolhuis
2009-11-18  9:40         ` Artem Bityutskiy
2009-11-18 10:38           ` Joakim Tjernlund
2009-11-18 10:54             ` Artem Bityutskiy
2009-11-18 10:59               ` Norbert van Bolhuis
2009-11-18 11:01               ` Joakim Tjernlund

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=1255269852.16942.105.camel@localhost \
    --to=dedekind1@gmail.com \
    --cc=linux-mtd@lists.infradead.org \
    --cc=nvbolhuis@aimvalley.nl \
    /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