Re: sun4v+DMA related boot crash on 4.13-git

On 07/11/2017 09:02 PM, David Miller wrote: From: Tushar Dave Date: Tue, 11 Jul 2017 20:43:39 -0700 Yes, indeed the bug is in Linus's tree. However, 'sparc' tree doesn't have DMA API change (e.g. commit b02c2b0bfd7ae) yet that introduced the panic. You can simply

Re: sun4v+DMA related boot crash on 4.13-git

On 07/11/2017 09:02 PM, David Miller wrote: From: Tushar Dave Date: Tue, 11 Jul 2017 20:43:39 -0700 Yes, indeed the bug is in Linus's tree. However, 'sparc' tree doesn't have DMA API change (e.g. commit b02c2b0bfd7ae) yet that introduced the panic. You can simply make a note of this when

Re: sun4v+DMA related boot crash on 4.13-git

From: Tushar Dave Date: Tue, 11 Jul 2017 20:43:39 -0700 > Yes, indeed the bug is in Linus's tree. However, 'sparc' tree doesn't > have DMA API change (e.g. commit b02c2b0bfd7ae) yet that introduced > the panic. You can simply make a note of this when you send the bug

Re: sun4v+DMA related boot crash on 4.13-git

From: Tushar Dave Date: Tue, 11 Jul 2017 20:43:39 -0700 > Yes, indeed the bug is in Linus's tree. However, 'sparc' tree doesn't > have DMA API change (e.g. commit b02c2b0bfd7ae) yet that introduced > the panic. You can simply make a note of this when you send the bug fix to me.

Re: sun4v+DMA related boot crash on 4.13-git

On 07/11/2017 05:34 PM, David Miller wrote: 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,

Re: sun4v+DMA related boot crash on 4.13-git

On 07/11/2017 05:34 PM, David Miller wrote: 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

Re: sun4v+DMA related boot crash on 4.13-git

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

Re: sun4v+DMA related boot crash on 4.13-git

From: Meelis Roos Date: Wed, 12 Jul 2017 00:48:07 +0300 (EEST) > Why sparc-next - it should go into 4.13 since 4.13 would break all > niagara1 and niagara2 systems otherwise? Absoultely, positively, correct.

Re: sun4v+DMA related boot crash on 4.13-git

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

Re: sun4v+DMA related boot crash on 4.13-git

From: Meelis Roos Date: Wed, 12 Jul 2017 00:48:07 +0300 (EEST) > Why sparc-next - it should go into 4.13 since 4.13 would break all > niagara1 and niagara2 systems otherwise? Absoultely, positively, correct.

Re: sun4v+DMA related boot crash on 4.13-git

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

Re: sun4v+DMA related boot crash on 4.13-git

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

Re: sun4v+DMA related boot crash on 4.13-git

> > > > > 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

Re: sun4v+DMA related boot crash on 4.13-git

> > > > > 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

Re: sun4v+DMA related boot crash on 4.13-git

On 07/10/2017 10:05 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

Re: sun4v+DMA related boot crash on 4.13-git

On 07/10/2017 10:05 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

Re: sun4v+DMA related boot crash on 4.13-git

> > > 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

Re: sun4v+DMA related boot crash on 4.13-git

> > > 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

Re: sun4v+DMA related boot crash on 4.13-git

On 07/10/2017 11:47 AM, tndave wrote: On 07/10/2017 06:20 AM, 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

Re: sun4v+DMA related boot crash on 4.13-git

On 07/10/2017 11:47 AM, tndave wrote: On 07/10/2017 06:20 AM, 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

Re: sun4v+DMA related boot crash on 4.13-git

On 07/10/2017 06:20 AM, 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

Re: sun4v+DMA related boot crash on 4.13-git

On 07/10/2017 06:20 AM, 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

sun4v+DMA related boot crash on 4.13-git

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.

sun4v+DMA related boot crash on 4.13-git

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.