[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CACqU3MXaHJ+AnUpkeBWg=aHp3iJBR=uXgr22pinAdu-wgeoCuQ@mail.gmail.com>
Date: Thu, 4 Aug 2011 22:24:07 -0400
From: Arnaud Lacombe <lacombar@...il.com>
To: Dave Jones <davej@...hat.com>,
Linux Kernel <linux-kernel@...r.kernel.org>,
tom.l.nguyen@...el.com, yanmin.zhang@...el.com
Subject: Re: [rfc] suppress excessive AER output
Hi,
On Wed, Aug 3, 2011 at 6:34 PM, Dave Jones <davej@...hat.com> wrote:
> I have a machine that has developed some kind of problem with
> its onboard ethernet. It still boots, but spewed almost 1.5G of text
> (2381585 instances of the warning below) before we realised what
> was going on, and blacklisted the igb driver.
>
> Is it worth logging every single error when we're flooding like this ?
> It seems unlikely that we'll find useful information in amongst that much data
> that wasn't already in the first 100 instances.
>
> I picked 100 in the (untested) example patch below arbitarily, but the exact
> value could be smaller, or slightly bigger..
>
> could we do something like this maybe ?
>
Please do not reinvent the wheel and use printk_ratelimited().
Thanks,
- Arnaud
> Dave
>
> diff --git a/drivers/pci/pcie/aer/aerdrv_errprint.c b/drivers/pci/pcie/aer/aerdrv_errprint.c
> index 3ea5173..4ec88c6 100644
> --- a/drivers/pci/pcie/aer/aerdrv_errprint.c
> +++ b/drivers/pci/pcie/aer/aerdrv_errprint.c
> @@ -153,6 +153,17 @@ void aer_print_error(struct pci_dev *dev, struct aer_err_info *info)
> {
> int id = ((dev->bus->number << 8) | dev->devfn);
> char prefix[44];
> + static unsigned long aer_printk_limit = 0;
> +
> + aer_printk_limit++;
> +
> + if (aer_printk_limit > 100)
> + return;
> +
> + if (aer_printk_limit == 100) {
> + printk(KERN_ERR "Reached limit of 100 AER errors. Further AER output suppressed.\n");
> + return;
> + }
>
> snprintf(prefix, sizeof(prefix), "%s%s %s: ",
> (info->severity == AER_CORRECTABLE) ? KERN_WARNING : KERN_ERR,
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@...r.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists