[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4717C90A.4060208@garzik.org>
Date: Thu, 18 Oct 2007 16:58:50 -0400
From: Jeff Garzik <jeff@...zik.org>
To: Erez Zadok <ezk@...sunysb.edu>
CC: linux-kernel@...r.kernel.org, pcnet32@...izon.net,
netdev@...r.kernel.org
Subject: Re: broken PCNET32 in 2.6.24 requires experimental PCNET32_NAPI?
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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists