From: Jeff Garzik <jeff@garzik.org>
To: Erez Zadok <ezk@cs.sunysb.edu>
Cc: linux-kernel@vger.kernel.org, pcnet32@verizon.net,
netdev@vger.kernel.org
Subject: Re: broken PCNET32 in 2.6.24 requires experimental PCNET32_NAPI?
Date: Thu, 18 Oct 2007 16:58:50 -0400 [thread overview]
Message-ID: <4717C90A.4060208@garzik.org> (raw)
In-Reply-To: <200710182054.l9IKsiQJ007446@agora.fsl.cs.sunysb.edu>
Erez Zadok wrote:
> I'm using Linus's git tree as of commit
> d85714d81cc0408daddb68c10f7fd69eafe7c213. I built that kernel under vmware
> workstation 6.0.1 which emulates a pcnet32 nic. When I only turn on
> CONFIG_PCNET32, my network interface doesn't seem to come up fully: my dhcp
> server sees a request, offers an IP addr, but the VM running 2.6.24 doesn't
> pick up the response. Manually configuring the eth0 and pinging yields
> similar results: no replies come back. The same VM has lots of other
> kernels on it, all of which work fine (so it's not an iptables/selinux
> problem, or the like).
>
> If, however, I turn on the EXPERIMENTAL feature CONFIG_PCNET32_NAPI, then
> the driver works again. So, is this NAPI feature now a required one or did
> the base driver somehow got broken? I've not investigated this further.
Fixes were posted by the maintainer, and pushed to Linus, yesterday...
Jeff
next prev parent reply other threads:[~2007-10-18 20:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-18 20:54 broken PCNET32 in 2.6.24 requires experimental PCNET32_NAPI? Erez Zadok
2007-10-18 20:58 ` Jeff Garzik [this message]
2007-10-19 4:33 ` Erez Zadok
2007-10-19 4:41 ` David Miller
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=4717C90A.4060208@garzik.org \
--to=jeff@garzik.org \
--cc=ezk@cs.sunysb.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pcnet32@verizon.net \
/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.