From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jason Andryuk Subject: Re: Missed Stable backport? maybe [PATCH v2 0/4] xen-blk: bug fixes Date: Mon, 23 Jun 2014 10:29:27 -0400 Message-ID: <53A839C7.5080409@aero.org> References: <53A445F1.9010204@aero.org> <53A44F57.3070507@citrix.com> <53A4627F.9080107@aero.org> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: <53A4627F.9080107@aero.org> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: =?ISO-8859-1?Q?Roger_Pau_Monn=E9?= , xen-devel@lists.xen.org Cc: david.vrabel@citrix.com List-Id: xen-devel@lists.xenproject.org On 6/20/2014 12:34 PM, Jason Andryuk wrote: > On 6/20/2014 11:12 AM, Roger Pau Monn=E9 wrote: >> On 20/06/14 16:32, Jason Andryuk wrote: >>> Hi Roger, >>> = >>> I'm seeing a crash on shutdown in xen_blkbk_unmap on 3.12.22. >>> kdb backtrace below. Could this be the shutdown race fixed by >>> "[PATCH v2 3/4] xen-blkback: fix shutdown race"? That email does >>> not provide the observed backtrace, so I cannot compare. >> = >> Could be related, but you didn't provide the reason for the crash, >> just the backtrace, have you tried applying those patches on top of >> your kernel? > = > The backtrace was seen rebooting my box. kdb is configured in the > hardware domain, so it broke into that. Not all guests were shutdown > prior to the restart. > = > It's intermittent. I just rebooted ready to capture the serial log, > but there was no crash. > = > I haven't tried the patches yet. They came up when googling for > related error messages. I hope to try them soon. Friday afternoon, I cherry picked the first three patches. I've rebooted a= handful of times without error, but it was not reproducible without the pa= tches. I'll report if I see the error again. Regards, Jason