public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Lukas Hejtmanek <xhejtman@ics.muni.cz>
To: Auke Kok <auke-jan.h.kok@intel.com>
Cc: linux-kernel@vger.kernel.org
Subject: e1000 driver problems
Date: Tue, 20 Nov 2007 15:38:04 +0100	[thread overview]
Message-ID: <20071120143803.GA5638@ics.muni.cz> (raw)
In-Reply-To: <45354850.6050900@intel.com>

Hello,

I have laptop thinkpad T61 with 82566MM Gigabit Network Connection (rev 03)
(8086:1049). I have kernel 2.6.24-rc3. E1000E driver does not work (the card
is not detected although it is PCI-E), with E1000 driver, it works mostly OK
unless I force speed to 100Mbits. (ethtool -s eth0 autoneg off speed 100)

I got message about device hang:
Nov 20 10:57:24 anubis kernel: [  212.307502] e1000: eth0: e1000_watchdog:
10/100 speed: disabling TSO
Nov 20 11:03:02 anubis kernel: [  242.811474]   Tx Queue             <0>
Nov 20 11:03:02 anubis kernel: [  242.811476]   TDH                  <80>
Nov 20 11:03:02 anubis kernel: [  242.811478]   TDT                  <81>
Nov 20 11:03:02 anubis kernel: [  242.811480]   next_to_use          <81>
Nov 20 11:03:02 anubis kernel: [  242.811482]   next_to_clean        <80>
Nov 20 11:03:02 anubis kernel: [  242.811484] buffer_info[next_to_clean]
Nov 20 11:03:02 anubis kernel: [  242.811486]   time_stamp <100079cdf>
Nov 20 11:03:02 anubis kernel: [  242.811488]   next_to_watch        <80>
Nov 20 11:03:02 anubis kernel: [  242.811489]   jiffies <100079e68>
Nov 20 11:03:02 anubis kernel: [  242.811491]   next_to_watch.status <0>
Nov 20 11:03:04 anubis kernel: [  243.000047]   Tx Queue             <0>
Nov 20 11:03:04 anubis kernel: [  243.000049]   TDH                  <80>
Nov 20 11:03:04 anubis kernel: [  243.000051]   TDT                  <81>
Nov 20 11:03:04 anubis kernel: [  243.000053]   next_to_use          <81>
and so on.

Is it known problem?


-- 
Lukáš Hejtmánek

  parent reply	other threads:[~2007-11-20 14:53 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-13 21:40 Machine restart doesn't work - Intel 965G, 2.6.19-rc2 Aleksey Gorelov
2006-10-13 21:42 ` Ryan Richter
2006-10-13 21:45   ` Lukas Hejtmanek
2006-10-13 21:46     ` Ryan Richter
2006-10-13 21:49       ` Lukas Hejtmanek
2006-10-13 21:51         ` Ryan Richter
2006-10-17 18:00         ` Ryan Richter
2006-10-17 20:53           ` Aleksey Gorelov
2006-10-17 21:17             ` Machine restart doesn't work - Intel 965G, 2.6.19-rc2 / e1000? Auke Kok
2006-10-17 22:14               ` dared1st
2007-11-20 14:38               ` Lukas Hejtmanek [this message]
2007-11-26 23:26                 ` e1000 driver problems Kok, Auke
2007-11-27 15:07                   ` Lukas Hejtmanek
2007-11-27 16:48                     ` Kok, Auke
2007-11-27 17:31                       ` Lukas Hejtmanek
2006-10-17 22:27             ` Machine restart doesn't work - Intel 965G, 2.6.19-rc2 Ryan Richter
2006-10-20 17:57               ` Auke Kok
2006-10-20 18:06                 ` Lukas Hejtmanek
2006-10-21 17:34                   ` Ryan Richter
2006-10-21 17:56                     ` Auke Kok
2006-10-20 18:07                 ` Ryan Richter
2006-10-20 18:17                   ` Auke Kok
2006-10-20 18:29                     ` Lukas Hejtmanek
2006-10-23 20:52                   ` Aleksey Gorelov
2006-10-13 21:50       ` Aleksey Gorelov

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=20071120143803.GA5638@ics.muni.cz \
    --to=xhejtman@ics.muni.cz \
    --cc=auke-jan.h.kok@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox