On Thu, Feb 25, 2021 at 09:54:06AM +0900, Punit Agrawal wrote: > From: Corinna Vinschen <vinschen@xxxxxxxxxx> > > commit 2643e6e90210e16c978919617170089b7c2164f7 upstream > > TSAUXC.DisableSystime is never set, so SYSTIM runs into a SYS WRAP > every 1100 secs on 80580/i350/i354 (40 bit SYSTIM) and every 35000 > secs on 80576 (45 bit SYSTIM). > > This wrap event sets the TSICR.SysWrap bit unconditionally. > > However, checking TSIM at interrupt time shows that this event does not > actually cause the interrupt. Rather, it's just bycatch while the > actual interrupt is caused by, for instance, TSICR.TXTS. > > The conclusion is that the SYS WRAP is actually expected, so the > "unexpected SYS WRAP" message is entirely bogus and just helps to > confuse users. Drop it. > > Signed-off-by: Corinna Vinschen <vinschen@xxxxxxxxxx> > Acked-by: Jacob Keller <jacob.e.keller@xxxxxxxxx> > Tested-by: Aaron Brown <aaron.f.brown@xxxxxxxxx> > Signed-off-by: Jeff Kirsher <jeffrey.t.kirsher@xxxxxxxxx> > --- > [ Due to confusion about stable rules for networking the request was > mistakenly sent to netdev only[0]. Apologies if you're seeing this > again. ] No signed-off-by: from you? :(
