From: Dave Chinner <david@fromorbit.com>
To: Stefan Priebe <s.priebe@profihost.ag>
Cc: Christoph Hellwig <hch@infradead.org>,
gregkh@linuxfoundation.org, stable@vger.kernel.org,
"xfs@oss.sgi.com" <xfs@oss.sgi.com>
Subject: Re: Kernel 3.0.30 hang in xfs_submit_ioend_bio
Date: Mon, 30 Apr 2012 20:32:59 +1000 [thread overview]
Message-ID: <20120430103259.GK7015@dastard> (raw)
In-Reply-To: <4F9E4874.8050505@profihost.ag>
On Mon, Apr 30, 2012 at 10:08:20AM +0200, Stefan Priebe wrote:
> Hi,
>
> while running several systems with 3.0.30 i'm seeing this call trace
> pretty often. Is this problem known?
>
> [925680.203973] Call Trace:
> [925680.204170] [<c0610ce0>] schedule+0x30/0x50
> [925680.204221] [<c0610d71>] io_schedule+0x71/0xb0
> [925680.204273] [<c0362420>] get_request_wait+0xa0/0x150
> [925680.204376] [<c03625c6>] __make_request+0xf6/0x280
> [925680.204427] [<c036143d>] generic_make_request+0x3fd/0x610
> [925680.204741] [<c03616ba>] submit_bio+0x6a/0x100
> [925680.204894] [<c03366a7>] xfs_submit_ioend_bio+0x47/0x70
> [925680.204946] [<c03367a4>] xfs_submit_ioend+0xd4/0xe0
> [925680.204998] [<c0337ba3>] xfs_vm_writepage+0x253/0x580
> [925680.205109] [<c01ae8ca>] shrink_page_list+0x55a/0x750
> [925680.205162] [<c01aed60>] shrink_inactive_list+0x1a0/0x350
> [925680.205214] [<c01af321>] shrink_zone+0x411/0x570
> [925680.205265] [<c01af9fe>] kswapd+0x57e/0x9c0
kswapd is blocking submitting IO - the request queue is full. I'd
say you've got memory pressure, lots of dirty pages and an IO
subsystem that can't keep up....
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2012-04-30 10:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-30 8:08 Kernel 3.0.30 hang in xfs_submit_ioend_bio Stefan Priebe
2012-04-30 10:32 ` Dave Chinner [this message]
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=20120430103259.GK7015@dastard \
--to=david@fromorbit.com \
--cc=gregkh@linuxfoundation.org \
--cc=hch@infradead.org \
--cc=s.priebe@profihost.ag \
--cc=stable@vger.kernel.org \
--cc=xfs@oss.sgi.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