All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Dumazet <dada1@cosmosbay.com>
To: Mark Seger <Mark.Seger@hp.com>
Cc: Ben Greear <greearb@candelatech.com>,
	netdev@vger.kernel.org, mchan@broadcom.com
Subject: Re: occasionally corrupted network stats in /proc/net/dev
Date: Mon, 14 Jan 2008 20:12:59 +0100	[thread overview]
Message-ID: <478BB43B.8060905@cosmosbay.com> (raw)
In-Reply-To: <478BAF47.10607@hp.com>

Mark Seger a écrit :
> Ignore that last one as it was pointed out to me that we have both nic 
> installed on many of our systems and ethtool told me the one 
> associated with the nic is actually the broadcom one.
>
> version:        1.4.38 E1B1EC867DEEB8027B2DA0F
> license:        GPL
> description:    Broadcom NetXtreme II BCM5706/5708 Driver
>

I remember some tg3 chips actually have bugs when reporting stats.... 
once in a while

CCed to Michael Chan to get some details.


> -mark
>
> Mark Seger wrote:
>> I'll try to get data on the other systems reporting it and as I said 
>> it does not  happen all that often AND you have to be looking for 
>> it.  The system I've personally seen it happen on several times is 
>> running RHEL4/U4 which redhat numbers 2.6.9-42 and from modinfo I see:
>> version:        7.0.33-k2-NAPI 51E97FEE51D0772AFC89130
>> description:    Intel(R) PRO/1000 Network Driver
>>
>> -mark
>>
>> Ben Greear wrote:
>>> Mark Seger wrote:
>>>> I had posted the following on linux-net and haven't see any 
>>>> responses possibly because nobody had any or that list is 
>>>> obsolete.  I have been told this is the current list for everything 
>>>> networking on linux so I thought I'd try again...
>>> Do you see this with multiple network drivers, or just with one 
>>> particular driver.  If so, which one?
>>>
>>> Thanks,
>>> Ben
>>>
>
> -- 
> To unsubscribe from this list: send the line "unsubscribe netdev" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>
>





  parent reply	other threads:[~2008-01-14 19:13 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-14 17:20 occasionally corrupted network stats in /proc/net/dev Mark Seger
2008-01-14 17:38 ` Eric Dumazet
2008-01-14 18:08 ` Ben Greear
2008-01-14 18:24   ` Mark Seger
2008-01-14 18:51     ` Mark Seger
2008-01-14 19:01       ` Ben Greear
2008-01-14 19:12       ` Eric Dumazet [this message]
2008-01-14 20:41         ` Michael Chan
2008-01-14 20:05           ` Mark Seger

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=478BB43B.8060905@cosmosbay.com \
    --to=dada1@cosmosbay.com \
    --cc=Mark.Seger@hp.com \
    --cc=greearb@candelatech.com \
    --cc=mchan@broadcom.com \
    --cc=netdev@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.