[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAC=cRTM_CZfstvbpdCRrLV-VH0VC=u6r10L+Ox2G4LWomXVauA@mail.gmail.com>
Date: Thu, 4 Aug 2011 14:45:01 +0800
From: huang ying <huang.ying.caritas@...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
On Thu, Aug 4, 2011 at 6:34 AM, 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 ?
Why not use __ratelimit to implement this feature?
Best Regards,
Huang Ying
--
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