Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754030Ab2E2Oyw (ORCPT ); Tue, 29 May 2012 10:54:52 -0400 Received: from rcsinet15.oracle.com ([148.87.113.117]:27021 "EHLO rcsinet15.oracle.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753477Ab2E2Oyt (ORCPT ); Tue, 29 May 2012 10:54:49 -0400 Date: Tue, 29 May 2012 10:47:43 -0400 From: Konrad Rzeszutek Wilk To: Hugh Dickins Cc: William Dauchy , shli@fusionio.com, stable@vger.kernel.org, Greg Kroah-Hartman , xen-devel@lists.xensource.com, Shaohua Li , linux-kernel@vger.kernel.org, Ben Hutchings Subject: Re: [Xen-devel] swap: don't do discard if no discard option added Message-ID: <20120529144743.GG3558@phenom.dumpdata.com> References: <20120521181558.GA7829@phenom.dumpdata.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) X-Source-IP: ucsinet22.oracle.com [156.151.31.94] Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 3427 Lines: 83 On Sat, May 26, 2012 at 11:29:37AM -0700, Hugh Dickins wrote: > On Mon, 21 May 2012, Konrad Rzeszutek Wilk wrote: > > On Mon, May 21, 2012 at 12:30:45AM +0200, William Dauchy wrote: > > > Hello, > > > > > > On Xen, when booting a guest with a system disk and an additional swap > > > disk I'm getting a calltrace. > > > xen hypervisor: 4.1.2; linux dom0: v3.3.6; linux guest: v3.2.17 > > > When booting without a swap disk, I don't have the issue. > > > I also tested a guest with v3.3.6: same problem. But from v3.4-rc2, > > > the issue is fixed. > > > I cherry-picked: > > > > > 052b198 swap: don't do discard if no discard option added > > > > So you are asking for 052b198 to be back-ported. > > > > I am OK with that but I think Shaohua needs to Ack that and > > ask Greg to put it on stable@kernel.org > > Since that commit did indeed go into v3.4, I won't quarrel with it > now going to stable. > > But the commit went in to work around the slow discard implementation > on OCZ Vertex II SSDs. > > Please, could someone explain to me the meaning of the stacktrace > below (which is missing a WARNING or BUG line?), and how disabling > swap discard fixes it? I think I know and just narrowed down the issue this Friday. William, could you please apply the patch outlined in https://bugzilla.redhat.com/show_bug.cgi?id=824641 to your dom0 and see if that (so do not have 052b198 in your branch) > > At present I see no connection (beyond the fact that the patch fixes > the symptom): in the absence of understanding, I have to beware that > the underlying issue may remain unfixed. > > Hugh > > > > > > > > > > Applied and tested on top of v3.2.17 and v3.3.6, it fixes the issue. > > > > > > Pid: 0, comm: swapper/0 Not tainted 3.2.17-x86_64 #12 > > > Call Trace: > > > > > > [] ? handle_irq_event_percpu+0x3a/0x140 > > > [] ? handle_irq_event+0x49/0x80 > > > [] ? handle_edge_irq+0x6d/0x120 > > > [] ? __xen_evtchn_do_upcall+0x1b8/0x280 > > > [] ? xen_evtchn_do_upcall+0x22/0x40 > > > [] ? xen_do_hypervisor_callback+0x1e/0x30 > > > > > > [] ? hypercall_page+0x3aa/0x1000 > > > [] ? hypercall_page+0x3aa/0x1000 > > > [] ? xen_safe_halt+0xc/0x20 > > > [] ? default_idle+0x23/0x40 > > > [] ? cpu_idle+0x63/0xb0 > > > [] ? start_kernel+0x362/0x36d > > > [] ? xen_start_kernel+0x558/0x55e > > > Code: 39 ed 0f 84 1c 02 00 00 44 8b 7b 48 4c 8b 73 50 41 83 ef 01 41 > > > 21 ef 49 6b c7 70 4d 8b 64 06 40 49 69 c4 d0 00 00 00 48 8d 14 03 <48> > > > 8b 8a 78 02 00 00 48 89 4c 24 10 80 ba 09 02 00 00 00 74 6d > > > RIP [] blkif_interrupt+0x66/0x320 > > > RSP > > > ---[ end trace dfd4e5623eb06620 ]--- > -- > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html > Please read the FAQ at http://www.tux.org/lkml/ -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/