From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S265366AbUBPERk (ORCPT ); Sun, 15 Feb 2004 23:17:40 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S265367AbUBPERk (ORCPT ); Sun, 15 Feb 2004 23:17:40 -0500 Received: from pool-141-155-128-183.ny5030.east.verizon.net ([141.155.128.183]:44493 "EHLO mail.blazebox.homeip.net") by vger.kernel.org with ESMTP id S265366AbUBPERi (ORCPT ); Sun, 15 Feb 2004 23:17:38 -0500 Subject: Re: e1000 problems in 2.6.x From: Paul Blazejowski To: steve@saturn5.com Cc: LKML Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-hnthi6zI88IlFwBlYeUw" Message-Id: <1076905069.4092.4.camel@blaze.homeip.net> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.5.4 (Slackware Linux) Date: Sun, 15 Feb 2004 23:17:49 -0500 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org --=-hnthi6zI88IlFwBlYeUw Content-Type: text/plain Content-Transfer-Encoding: quoted-printable Hi Steve, I am experiencing same problem with e1000 on 2.6.3-rc2-mm1 and all previous 2.6 kernels with getting the transmit timed out messages.I do not get the transmission errors though.The same setup works fine on 2.4 kernel just like yours. This happens on Slackware 9.1 on NFORCE2 based Gigabyte 7NNXP board with OEM Intel 1000MT builtin chip. Have you found any solutions yet?=20 Regards, Paul B. --=-hnthi6zI88IlFwBlYeUw Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (GNU/Linux) iD8DBQBAMERtv0+bfGBjm98RApPZAJ9bXwmtBif6uVvhwpdcdbk3nq1WqACfRXEQ 9wACVMi0fccSN5Sg1NS2v+s= =Z4wq -----END PGP SIGNATURE----- --=-hnthi6zI88IlFwBlYeUw--