From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: imammedo <imammedo@redhat.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: Re: [PATCH] blkfront: Move blkif_interrupt into a tasklet.
Date: Tue, 16 Aug 2011 22:38:27 -0400 [thread overview]
Message-ID: <20110817023827.GA21468@dumpdata.com> (raw)
In-Reply-To: <1313494014833-4704111.post@n5.nabble.com>
On Tue, Aug 16, 2011 at 04:26:55AM -0700, imammedo wrote:
>
> Jeremy Fitzhardinge wrote:
> >
> > Have you tried bisecting to see when this particular problem appeared?
> > It looks to me like something is accidentally re-enabling interrupts -
> > perhaps a stack overrun is corrupting the "flags" argument between a
> > spin_lock_irqsave()/restore pair.
> >
> > Is it only on 32-bit kernels?
> >
> ------------[ cut here ]------------
> [604001.659925] WARNING: at block/blk-core.c:239 blk_start_queue+0x70/0x80()
> [604001.659964] Modules linked in: nfs lockd fscache auth_rpcgss nfs_acl
> sunrpc ip6t_REJECT nf_conntrack_ipv6 nf_conntrack_ipv4 nf_defrag_ipv4
> nf_defrag_ipv6 xt_state nf_conntrack ip6table_filter ip6_tables xen_netfront
> pcspkr [last unloaded: scsi_wait_scan]
> [604001.660147] Pid: 336, comm: udevd Tainted: G W 3.0.0+ #50
> [604001.660181] Call Trace:
> [604001.660209] [<c045c512>] warn_slowpath_common+0x72/0xa0
> [604001.660243] [<c06643a0>] ? blk_start_queue+0x70/0x80
> [604001.660275] [<c06643a0>] ? blk_start_queue+0x70/0x80
> [604001.660310] [<c045c562>] warn_slowpath_null+0x22/0x30
> [604001.660343] [<c06643a0>] blk_start_queue+0x70/0x80
> [604001.660379] [<c075e231>] kick_pending_request_queues+0x21/0x30
> [604001.660417] [<c075e42f>] blkif_interrupt+0x19f/0x2b0
> ...
> ------------[ cut here ]------------
>
> I've debugged a bit blk-core warning and can say:
> - Yes, It is 32-bit PAE kernel and happens only with it so far.
> - Affects PV xen guest, bare-metal and kvm configs are not affected.
> - Upstream kernel is affected as well.
> - Reproduces on xen 4.1.1 and 3.1.2 hosts
And the dom0 is 2.6.18 right? This problem is not present
when you use a 3.0 dom0?
next prev parent reply other threads:[~2011-08-17 2:38 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-23 6:54 Fix the occasional xen-blkfront deadlock, when irqbalancing Daniel Stodden
2010-08-23 6:54 ` [PATCH] blkfront: Move blkif_interrupt into a tasklet Daniel Stodden
2010-08-23 7:01 ` Daniel Stodden
2010-09-02 22:46 ` Jeremy Fitzhardinge
2010-09-02 23:08 ` Daniel Stodden
2010-09-07 1:39 ` blktap lockdep hiccup Jeremy Fitzhardinge
2010-09-07 1:46 ` Daniel Stodden
2010-09-08 2:03 ` [PATCH] blkfront: Move blkif_interrupt into a tasklet Jeremy Fitzhardinge
2010-09-08 2:21 ` Daniel Stodden
2010-09-08 6:37 ` Jeremy Fitzhardinge
2010-09-23 16:08 ` Andrew Jones
2010-09-23 16:23 ` Jeremy Fitzhardinge
2010-09-23 16:38 ` Paolo Bonzini
2010-09-23 18:36 ` Jeremy Fitzhardinge
2010-09-24 7:14 ` Andrew Jones
2010-09-24 18:50 ` Jeremy Fitzhardinge
2010-09-27 7:41 ` Andrew Jones
2010-09-27 9:46 ` Daniel Stodden
2010-09-27 10:21 ` Andrew Jones
2011-08-16 11:26 ` imammedo
2011-08-16 14:57 ` Konrad Rzeszutek Wilk
2011-08-17 2:38 ` Konrad Rzeszutek Wilk [this message]
2011-08-17 7:30 ` Paolo Bonzini
2011-08-17 9:07 ` Igor Mammedov
2011-08-24 15:36 ` Konrad Rzeszutek Wilk
2011-08-24 16:36 ` Igor Mammedov
2011-08-29 19:46 ` Konrad Rzeszutek Wilk
2011-08-31 23:47 ` [PATCH] xen: x86_32: do not enable iterrupts when returning from exception in interrupt context Igor Mammedov
2011-08-31 22:37 ` Jeremy Fitzhardinge
2011-09-01 8:19 ` Igor Mammedov
2011-09-01 11:46 ` [PATCH v2] " Igor Mammedov
2011-09-01 15:45 ` Konrad Rzeszutek Wilk
2011-09-01 16:46 ` Jeremy Fitzhardinge
2011-09-02 8:18 ` Igor Mammedov
2011-09-02 13:40 ` Konrad Rzeszutek Wilk
2011-09-02 14:01 ` [Xen-devel] " Igor Mammedov
2011-09-02 14:47 ` Konrad Rzeszutek Wilk
2011-09-06 9:16 ` Igor Mammedov
2011-09-02 9:19 ` Igor Mammedov
2011-09-02 10:00 ` Keir Fraser
2010-08-23 21:09 ` Fix the occasional xen-blkfront deadlock, when irqbalancing Jeremy Fitzhardinge
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=20110817023827.GA21468@dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=imammedo@redhat.com \
--cc=xen-devel@lists.xensource.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;
as well as URLs for NNTP newsgroup(s).