On Tue, Sep 1, 2015 at 9:40 AM, Or Gerlitz <[email protected]> wrote: > On Tue, Sep 1, 2015 at 1:13 AM, Doug Ledford <[email protected]> wrote: >> On 08/31/2015 04:21 PM, Or Gerlitz wrote: >>> On Mon, Aug 31, 2015 at 4:02 PM, Doug Ledford <[email protected]> wrote: >>>> On 08/31/2015 03:09 AM, Matan Barak wrote: >>> >>>>> Actually, it looks like the dump stack we've got before [1] was fixed. >>>>> This happens when the mlx4 driver is used in setups where number of >>>>> cores >= 32. >>> >>>>> Doug, is that the case? >>> >>>> Indeed, 48 cores on this machine. >>> >>> so do we have bingo here? the patch is in the net-next tree (and we >>> can't put it in 4.2 only through -stable since 4.2 is released by >>> now), does it solves the problem? >> >> Yes, it solved the problem. I pulled the patch into my testing branch >> to confirm. > > Good. Something is still strange w.r.t your environment... you said that > when you were submitting the 4.2-rc changes this machine worked, however > the problematic code in mlx4_enable_msi_x existed there by the time you > made that testing, Matan - agree? > > Or.
If I recall, this code was sent through linux-net mailing list. So it's possible the different branches weren't rebased, isn't it? > -- > To unsubscribe from this list: send the line "unsubscribe linux-rdma" in > the body of a message to [email protected] > More majordomo info at http://vger.kernel.org/majordomo-info.html -- To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
