Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755145AbZLRWYA (ORCPT ); Fri, 18 Dec 2009 17:24:00 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1753786AbZLRWYA (ORCPT ); Fri, 18 Dec 2009 17:24:00 -0500 Received: from mga01.intel.com ([192.55.52.88]:32304 "EHLO mga01.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752618AbZLRWX7 (ORCPT ); Fri, 18 Dec 2009 17:23:59 -0500 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="4.47,420,1257148800"; d="scan'208";a="757557998" Subject: Re: kexec reboot broken with ioatdma? From: Dan Williams To: Roland Dreier Cc: Simon Horman , "linux-kernel@vger.kernel.org" , "kexec@lists.infradead.org" In-Reply-To: References: <20091216224912.GC16219@verge.net.au> <4B296930.9020704@intel.com> <1261174241.16958.6.camel@dwillia2-linux.ch.intel.com> Content-Type: text/plain; charset="UTF-8" Date: Fri, 18 Dec 2009 15:23:20 -0700 Message-Id: <1261175000.16958.8.camel@dwillia2-linux.ch.intel.com> Mime-Version: 1.0 X-Mailer: Evolution 2.28.0 (2.28.0-2.fc12) Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 738 Lines: 22 On Fri, 2009-12-18 at 15:20 -0700, 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 What was that, all of 8 minutes to turn that test around! :-) Nice. Thanks, Dan -- 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/