Date: Tue, 16 Aug 2005 11:37:25 -0700 From: Brooks Davis <brooks@one-eyed-alien.net> To: Iva Hesy <iva.cnhn@gmail.com> Cc: freebsd-stable@freebsd.org Subject: Re: Too short ethernet frame... Message-ID: <20050816183725.GC19325@odin.ac.hmc.edu> In-Reply-To: <148cabbc050813020177b5b97e@mail.gmail.com> References: <148cabbc05081202377c708c5b@mail.gmail.com> <20050812163645.GD13376@odin.ac.hmc.edu> <148cabbc05081222166ae7cdb6@mail.gmail.com> <148cabbc050813020177b5b97e@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--uh9ZiVrAOUUm9fzH Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Aug 13, 2005 at 02:01:26AM -0700, Iva Hesy wrote: > Just now, I add "date=3D2005.07.31.03.00.00" to my src cvsup sup-file > and make kernel, too short ethernet frames are still sniffered. But > when I add "date=3D2005.07.22.03.00.00" to sup-file and cvsup and make > kernel, the damn datagrams gone!!! Sounds like someone introduced a bug in the nic driver or the ethernet code, but I'm not seeing anything obvious between those dates. If you could narrow the date range further that would help. -- Brooks --=20 Any statement of the form "X is the one, true Y" is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 --uh9ZiVrAOUUm9fzH Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQFDAjJkXY6L6fI4GtQRAiX8AKCztKOz7cpl0nPBIu2OCDUoB7HwugCfWspS Gq22gIi8wp0JciO/o1fcA3U= =91LF -----END PGP SIGNATURE----- --uh9ZiVrAOUUm9fzH--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050816183725.GC19325>