From: hong zhang <henryzhang62@yahoo.com>
To: Robert Hancock <hancockr@shaw.ca>, vatsa@linux.vnet.ibm.com
Cc: e1000-devel@lists.sourceforge.net, greg@kroah.com,
varunc@linux.vnet.ibm.com, linux-kernel@vger.kernel.org,
jbarnes@virtuousgeek.org
Subject: Re: [E1000-devel] Strange problem with e1000 driver - ping packet loss
Date: Wed, 25 Jun 2008 11:09:51 -0700 (PDT) [thread overview]
Message-ID: <375649.87756.qm@web57914.mail.re3.yahoo.com> (raw)
In-Reply-To: <20080625143234.GB3899@linux.vnet.ibm.com>
Vatsa,
This is not legacy mode that causes long ping time.
---henry
--- On Wed, 6/25/08, Srivatsa Vaddagiri <vatsa@linux.vnet.ibm.com> wrote:
> From: Srivatsa Vaddagiri <vatsa@linux.vnet.ibm.com>
> Subject: Re: [E1000-devel] Strange problem with e1000 driver - ping packet loss
> To: "Robert Hancock" <hancockr@shaw.ca>
> Cc: e1000-devel@lists.sourceforge.net, greg@kroah.com, varunc@linux.vnet.ibm.com, linux-kernel@vger.kernel.org, jbarnes@virtuousgeek.org
> Date: Wednesday, June 25, 2008, 9:32 AM
> On Fri, Jun 20, 2008 at 08:40:47AM -0600, Robert Hancock
> wrote:
> > Looks reasonable to me.. and what does
> /proc/interrupts show with this
> > setup?
>
> Sorry about the delay, but here's /proc/interrupts:
>
> CPU0
> 0: 1342021 IO-APIC-edge timer
> 1: 416 IO-APIC-edge i8042
> 6: 6 IO-APIC-edge floppy
> 8: 1 IO-APIC-edge rtc
> 12: 13367 IO-APIC-edge i8042
> 169: 1 IO-APIC-level acpi
> 177: 8882 IO-APIC-level libata, eth1
> 185: 75633 IO-APIC-level uhci_hcd:usb1,
> i915@pci:0000:00:02.0
> 193: 0 IO-APIC-level uhci_hcd:usb2
> NMI: 0
> LOC: 1341970
> ERR: 0
> MIS: 0
>
>
>
> --
> Regards,
> vatsa
>
> -------------------------------------------------------------------------
> Check out the new SourceForge.net Marketplace.
> It's the best place to buy or sell services for
> just about anything Open Source.
> http://sourceforge.net/services/buy/index.php
> _______________________________________________
> E1000-devel mailing list
> E1000-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/e1000-devel
next prev parent reply other threads:[~2008-06-25 18:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.QBOn2aWyqGnBJJticG4h09lpxD0@ifi.uio.no>
2008-06-19 17:25 ` Robert Hancock
2008-06-19 20:25 ` Vegard Nossum
2008-06-20 12:30 ` Srivatsa Vaddagiri
2008-06-20 14:40 ` Robert Hancock
2008-06-25 14:32 ` Srivatsa Vaddagiri
2008-06-25 18:09 ` hong zhang [this message]
[not found] ` <alpine.LFD.1.10.0806251455500.3014@localhost.localdomain>
2008-06-25 19:04 ` Len Brown
2008-06-26 13:37 ` Srivatsa Vaddagiri
2008-06-24 4:33 ` Varun Chandramohan
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=375649.87756.qm@web57914.mail.re3.yahoo.com \
--to=henryzhang62@yahoo.com \
--cc=e1000-devel@lists.sourceforge.net \
--cc=greg@kroah.com \
--cc=hancockr@shaw.ca \
--cc=jbarnes@virtuousgeek.org \
--cc=linux-kernel@vger.kernel.org \
--cc=varunc@linux.vnet.ibm.com \
--cc=vatsa@linux.vnet.ibm.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome