[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Y7QYxAhcUa2JtjSy@unreal>
Date: Tue, 3 Jan 2023 14:00:04 +0200
From: Leon Romanovsky <leon@...nel.org>
To: Bjorn Helgaas <helgaas@...nel.org>
Cc: Paul Menzel <pmenzel@...gen.mpg.de>,
Rajat Khandelwal <rajat.khandelwal@...ux.intel.com>,
linux-pci@...r.kernel.org, netdev@...r.kernel.org,
rajat.khandelwal@...el.com, jesse.brandeburg@...el.com,
linux-kernel@...r.kernel.org, edumazet@...gle.com,
intel-wired-lan@...ts.osuosl.org, kuba@...nel.org,
Bjorn Helgaas <bhelgaas@...gle.com>,
anthony.l.nguyen@...el.com, pabeni@...hat.com, davem@...emloft.net
Subject: Re: [Intel-wired-lan] [PATCH] igc: Mask replay rollover/timeout
errors in I225_LMVP
On Tue, Jan 03, 2023 at 05:54:02AM -0600, Bjorn Helgaas wrote:
> On Tue, Jan 03, 2023 at 11:54:24AM +0200, Leon Romanovsky wrote:
> > On Sun, Jan 01, 2023 at 11:34:21AM +0100, Paul Menzel wrote:
> > > Am 01.01.23 um 09:32 schrieb Leon Romanovsky:
> > > > On Thu, Dec 29, 2022 at 05:56:40PM +0530, Rajat Khandelwal wrote:
> > > > > The CPU logs get flooded with replay rollover/timeout AER errors in
> > > > > the system with i225_lmvp connected, usually inside thunderbolt devices.
> > > > >
> > > > > One of the prominent TBT4 docks we use is HP G4 Hook2, which incorporates
> > > > > an Intel Foxville chipset, which uses the igc driver.
> > > > > On connecting ethernet, CPU logs get inundated with these errors. The point
> > > > > is we shouldn't be spamming the logs with such correctible errors as it
> > > > > confuses other kernel developers less familiar with PCI errors, support
> > > > > staff, and users who happen to look at the logs.
>
> > > > > --- a/drivers/net/ethernet/intel/igc/igc_main.c
> > > > > +++ b/drivers/net/ethernet/intel/igc/igc_main.c
>
> > > > > +static void igc_mask_aer_replay_correctible(struct igc_adapter *adapter)
>
> > > > Shouldn't this igc_mask_aer_replay_correctible function be implemented
> > > > in drivers/pci/quirks.c and not in igc_probe()?
> > >
> > > Probably. Though I think, the PCI quirk file, is getting too big.
> >
> > As long as that file is right location, we should use it.
> > One can refactor quirk file later.
>
> If a quirk like this is only needed when the driver is loaded,
This is always the case with PCI devices managed through kernel, isn't it?
Users don't care/aware about "broken" devices unless they start to use them.
Thanks
Powered by blists - more mailing lists