[lkml]   [2011]   [Aug]   [4]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [rfc] suppress excessive AER output
On Thu, Aug 04, 2011 at 02:45:01PM +0800, huang ying wrote:
> On Thu, Aug 4, 2011 at 6:34 AM, Dave Jones <> 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?

that would be better than the current situation probably, but my gut feeling is
that there's still going to be a lot of spew.


To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2011-08-05 03:53    [W:0.100 / U:0.128 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site