Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753059AbZLSHeM (ORCPT ); Sat, 19 Dec 2009 02:34:12 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752156AbZLSHeL (ORCPT ); Sat, 19 Dec 2009 02:34:11 -0500 Received: from kirsty.vergenet.net ([202.4.237.240]:58740 "EHLO kirsty.vergenet.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752060AbZLSHeK (ORCPT ); Sat, 19 Dec 2009 02:34:10 -0500 Date: Sat, 19 Dec 2009 18:34:06 +1100 From: Simon Horman To: Roland Dreier Cc: Dan Williams , "linux-kernel@vger.kernel.org" , "kexec@lists.infradead.org" Subject: Re: kexec reboot broken with ioatdma? Message-ID: <20091219073406.GG9764@verge.net.au> References: <20091216224912.GC16219@verge.net.au> <4B296930.9020704@intel.com> <1261174241.16958.6.camel@dwillia2-linux.ch.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.20 (2009-06-14) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 760 Lines: 20 On Fri, Dec 18, 2009 at 02:20:02PM -0800, Roland Dreier wrote: > > > Subject: ioat2,3: put channel hardware in known state at init > > > > Put the ioat2 and ioat3 state machines in the halted state with all > > errors cleared. > > Yes, with this applied I was able to kexec reboot from a kernel with > ioatdma loaded and have ioatdma work in the new kernel. So: > > Tested-by: Roland Dreier This seems fine to me from a kexec point of view Acked-by: Simon Horman -- 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/