netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Auke Kok <auke-jan.h.kok@intel.com>
To: Sukadev Bhattiprolu <sukadev@us.ibm.com>
Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: Network problem with 2.6.18-mm1 ?
Date: Wed, 27 Sep 2006 19:02:17 -0700	[thread overview]
Message-ID: <451B2D29.9040306@intel.com> (raw)
In-Reply-To: <20060928013724.GA22898@us.ibm.com>

Sukadev Bhattiprolu wrote:
> 
> I am unable to get networking to work with 2.6.18-mm1 on my system.
> 
> But 2.6.18 kernel on same system works fine. Here is some info about
> the system/debug attempts. Attached are the lspci output and config.
> 
> Appreciate any help. Please let me know if you need more info. 
> 
> Suka
> 
> System info:
> 
> 	x326, 2 CPU (AMD Opteron Processor 250)
> 
> Kernel info:
> 
> 	$ uname -a
> 	Linux elm3b166 2.6.18-mm1 #4 SMP PREEMPT Tue Sep 26 18:11:58 PDT 2006
> 	x86_64 GNU/Linux
> 
> 	Config tokens differing between the 2.6.18 kernel that works and
> 	the 2.6.18-mm1 that does not are:
> 
> 	Tokens in 2.6.18 but not in 2.6.18-mm1 config
> 
> 		CONFIG_SCSI_FC_ATTRS=y
> 		CONFIG_SCSI_SATA_SIL=y
> 		CONFIG_SCSI_SATA=y
> 
> 	Tokens in 2.6.18-mm1 but not in 2.6.18 config
> 
> 		CONFIG_PROC_SYSCTL=y
> 		CONFIG_SATA_SIL=y 
> 		CONFIG_ATA=y 
> 		CONFIG_ARCH_POPULATES_NODE_MAP=y
> 		CONFIG_CRYPTO_ALGAPI=y
> 		CONFIG_MICROCODE_OLD_INTERFACE=y
> 		CONFIG_BLOCK=y
> 		CONFIG_VIDEO_V4L1_COMPAT=y
> 		CONFIG_ZONE_DMA=y
> 		CONFIG_FB_DDC=y
> 
> 	All drivers compiled into kernel in both cases.
> 
> Debug info:
> 
> 	Checked hardware connections :-) 
> 	(Rebooting on 2.6.18 kernel works - consistently)
> 	
> 	$ ethtool -i eth0
> 		driver: e1000
> 		version: 7.2.7-k2
> 		firmware-version: N/A
> 
> 	$ ip addr
> 		seems fine (up, broadcasting etc)
> 
> 	$ ip -s link
> 		shows no errors/drops/overruns
> 
> 	$ ip route
> 		shows the correct gw
> 
> 	$ ethtool -S eth0
> 
> 		shows non-zero tx/rx packets/bytes but *rx_missed_errors*
> 		quite large (~138K) and increasing over time
> 
> 	$ ping <own-ip-addr>
> 		works fine
> 
> 	$ ping <gateway>
> 		no response.
> 
> 	$ tcpdump -i eth0 host <broken-host>
> 	
> 		while pinging gateway, tcpdump shows messages like:
> 
> 		18:03:45.936161 arp who-has <gateway> tell <broken-host>
> 
> (Config file and lspci output are attached)

how about dmesg? Perhaps it shows some valuable information.

also, since this is a networking problem, please include `ifconfig eth0` and the full 
output of `ethtool eth0` and `ethtool -S eth0`

Cheers,

Auke

  reply	other threads:[~2006-09-28  2:04 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-28  1:37 Network problem with 2.6.18-mm1 ? Sukadev Bhattiprolu
2006-09-28  2:02 ` Auke Kok [this message]
2006-09-28 18:52   ` Sukadev Bhattiprolu
2006-09-28 21:10     ` Jesse Brandeburg
2006-09-29  0:52       ` Sukadev Bhattiprolu
2006-09-29 18:08         ` Jesse Brandeburg
2006-09-29 23:30           ` Eric W. Biederman
2006-10-02 23:17             ` Badari Pulavarty

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=451B2D29.9040306@intel.com \
    --to=auke-jan.h.kok@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=sukadev@us.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;
as well as URLs for NNTP newsgroup(s).