netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marc D Ronell <mronell@alumni.upenn.edu>
To: netdev@vger.kernel.org
Subject: Re: Network access fails unless tcpdump is running?
Date: Fri, 02 Mar 2007 15:53:39 -0500	[thread overview]
Message-ID: <87abyv74fg.fsf@corps.glidepath.invalid> (raw)
In-Reply-To: 20070302202658.GA15151@core2.greyhouse.net

"Andy Gospodarek" <gospo@redhat.com> writes:

>
> Any chance you can boot back to the old kernel (the one where is was
> working) and run and ethtool -i eth0 on that one to see what version of
> the driver was used there?  It's hard to know what may have changed
> between the 2 versions of the driver since I don't know the starting
> point.
>
> It's also hard to know if this is fixed already since you aren't running
> the latest upstream kernel.  Downloading, building, and testing the
> latest from kernel.org would be a good way to know if this is already
> fixed.
>

I had already loaded,  compiled, and tested linux-2.6.20.1.  There was
no change with the newer kernel.  Network connections only worked when
tcpdump was running.

Similar for booting with an  older kernel 2.6.17.  I think the problem
is not with the kernel, but with other system software.  It could take
a while to debug, so I am just rebuilding.

Thanks for your help.

marc



      reply	other threads:[~2007-03-02 20:54 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-01 19:22 Network access fails unless tcpdump is running? Marc D Ronell
2007-03-01 20:13 ` Andy Gospodarek
2007-03-01 20:54   ` Marc D Ronell
2007-03-01 21:22     ` Andy Gospodarek
2007-03-01 23:27       ` Marc D Ronell
2007-03-02 20:26         ` Andy Gospodarek
2007-03-02 20:53           ` Marc D Ronell [this message]

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=87abyv74fg.fsf@corps.glidepath.invalid \
    --to=mronell@alumni.upenn.edu \
    --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 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).