em driver regression
jfvogel at gmail.com
Thu Apr 8 17:23:34 UTC 2010
On Thu, Apr 8, 2010 at 10:18 AM, Brandon Gooch
<jamesbrandongooch at gmail.com>wrote:
> On Thu, Apr 8, 2010 at 12:06 PM, Jack Vogel <jfvogel at gmail.com> wrote:
> > On Thu, Apr 8, 2010 at 10:01 AM, Brandon Gooch <
> jamesbrandongooch at gmail.com>
> > wrote:
> >> On Thu, Apr 8, 2010 at 11:52 AM, Jack Vogel <jfvogel at gmail.com> wrote:
> >> > Mike, I noticed this connection is only 100Mb, that isn't accidental?
> >> > And,
> >> > is it possible for
> >> > you to check a connection at 1Gb and see if the watchdogs don't
> >> >
> >> > My test engineer is running this code, and we are having trouble
> >> > repro'ing
> >> > the issue, so any
> >> > clues might help. Is the kernel 64 or 32 bit?
> >> >
> >> > Jack
> >> >
> >> Not to butt in or anything...
> > Not butting in :) OK, so this all looks fine or am I missing something?
> > Jack
> This is the dmesg from the system exhibiting the "ip length 328
> disagrees with bytes received 332" while attempting to obtain a lease
> on the two DHCP-enabled VLANs, and also manifests in the VirtualBox
> bridged networking guests.
> I can honestly say that other than the output from dhclient and the
> VirtualBox issue, I might not have noticed problems otherwise.
> For instance, I have a VLAN interface configured to connect to an
> "outside" LAN segment and I'm running sshd on that interfaces IP
> address (using the new multiple routing table feature as well). I was
> able to connect to the sshd instance as usual, and I can make
> connections out as in:
> # setfib 4 ping google.com
> ...things seemed OK. Until VirtualBox. Then I started paying attention
> to messages scrolling by as my machine booted and saw the dhclient "ip
> length" thing (just as Mike Tancsa had) and thought, "It must be the
> new em(4) driver".
> That's my story :)
> I don't know what chip my em(4) device is, how can I check that? Also,
> would some type of traffic capture help in this case?
pciconf -l will show us. my tester is having trouble reproducing this,
but I dont think he is using vlans, that must be the missing ingredient.
The disagreement in size is 4 bytes, just the size of the CRC
coincidentally, but I dont have it set to strip, hmmmm. I may have
some code for you to try shortly, stay tuned.
More information about the freebsd-stable