Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756122AbdGLAel (ORCPT ); Tue, 11 Jul 2017 20:34:41 -0400 Received: from shards.monkeyblade.net ([184.105.139.130]:44870 "EHLO shards.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754585AbdGLAej (ORCPT ); Tue, 11 Jul 2017 20:34:39 -0400 Date: Tue, 11 Jul 2017 17:34:36 -0700 (PDT) Message-Id: <20170711.173436.720922946430226024.davem@davemloft.net> To: tushar.n.dave@oracle.com Cc: mroos@linux.ee, sparclinux@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: sun4v+DMA related boot crash on 4.13-git From: David Miller In-Reply-To: <60fa7a06-d319-9b6f-aba8-7b63014a1120@oracle.com> References: <60fa7a06-d319-9b6f-aba8-7b63014a1120@oracle.com> X-Mailer: Mew version 6.7 on Emacs 24.5 / Mule 6.0 (HANACHIRUSATO) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.5.12 (shards.monkeyblade.net [149.20.54.216]); Tue, 11 Jul 2017 17:34:38 -0700 (PDT) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1175 Lines: 30 From: Tushar Dave Date: Tue, 11 Jul 2017 15:38:21 -0700 > > > On 07/11/2017 02:48 PM, Meelis Roos wrote: >>>>>>> I tested yesterdayd 4.12+git on sparc64 to see if the sparc merge >>>>>>> works >>>>>>> fine, and on all of my sun4v machines (T1000, T2000, T5120) it crashed >>>>>>> on boot with DMA-related stacktrace (below). Allt he machines are >>>>>>> sun4v >>>>>>> physical machines, not VM-s. Older sun4 machines do not exhibit this >>>>>>> problem. >>>>>>> >>>>>>> Maybae DMA APi realted, maybe sparc64. Will try to bisect when I get >>>>>>> time. >>>>>> I see whats going on with panic. I will reproduce locally. Will get >>>>>> back >>>>>> soon. >>>>> This patch should fix panic. Please give it a try. >>>> >>>> Yes, this patch fixes it. Thank you for fixing it quickly! >>> Thanks for testing. Patch sent for sparc-next. >> Why sparc-next - it should go into 4.13 since 4.13 would break all >> niagara1 and niagara2 systems otherwise?This is sparc arch fix so I >> used sparc tree(in this case for sparc-next). > I am open to maintainers suggestions. Thanks. If the bug is in Linus's tree the fix must target 'sparc' not 'sparc-next'.