On Sun, Feb 05, 2017 at 07:41:45AM -0600, Steve Wise wrote: > > > commit b414fa01c31318383ae29d9d23cb9ca4184bbd86 > > > Author: Steve Wise <swise@xxxxxxxxxxxxxxxxxxxxx> > > > Date: Thu Dec 15 08:09:35 2016 -0800 > > > > > > iw_cxgb4: set correct FetchBurstMax for QPs > > > > > > The current QP FetchBurstMax value is 256B, which > > > is incorrect since a WR can exceed that value. The > > > result being a partial WR fetched by hardware, and > > > a fatal "bad WR" error posted by the SGE. > > > > > > So bump the FetchBurstMax to 512B. > > > > > > Signed-off-by: Steve Wise <swise@xxxxxxxxxxxxxxxxxxxxx> > > > Signed-off-by: Doug Ledford <dledford@xxxxxxxxxx> > > > > > > I'm not sure if this is the correct way to request this, but I think I'm > > > following _option_2 from Documentation/stable_kernel_rules.txt. > > > > Now queued up. Are you sure this isn't also needed in the 4.4-stable > > tree? > > > > Hey Greg, At first, I didn't think it is needed because, while the bug is > indeed present in that code, it is only exposed (and causes problems) with > the new T6 hardware. But now I think I'd like the fix pulled in 4.4-stable > to avoid any issues if T6 support is pulled into that base. How would I pull "T6" support into that kernel? I'm guessing that's a much larger issue and isn't something that would normally happen in a stable kernel release? thanks, greg k-h -- To unsubscribe from this list: send the line "unsubscribe stable" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html