mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Marc Haber <mh+linux-kernel@zugschlus.de>
To: Linux Kernel Developers <linux-kernel@vger.kernel.org>,
	Linux Kernel Network Developers <netdev@vger.kernel.org>
Subject: e1000e crashes with 2.6.34.x and ThinkPad T60
Date: Sat, 24 Jul 2010 11:26:44 +0200	[thread overview]
Message-ID: <20100724092644.GA13353@torres.zugschlus.de> (raw)

Hi,

I have a new notebook, a Thinkpad T60, which is freezing in random
intervals (like 30 minutes to two days) as long as I am using the
on-board wired ethernet interface, which is an e1000e, [8086:109a]. As
long as I keep using the WLAN, the system runs for weeks despite
frequent suspend/resume cycles etc. The crashes seem really to be tied
to using the wired ethernet. This is a hard freeze, with nothing
happening on the system, only a long push on the power button helps.

Additionally, sometimes, probably after suspend/resume, the wired
ethernet does not come up properly again, ip addr claims "NO CARRIER"
even if the LEDs on the interface and on the switch claim that there
was a link. No packets are received by the interface when it's at this
stage.

Both issues appear with 2.6.34 and 2.6.34.1. I didn't try any of these
issues with an older kernel, 2.6.34 was already out when I started
using the T60.

To rule out defective hardware, I have tried with a second T60, with
the same results.

Full dmesg and lspci-nn attached, please say if you need more.

Greetings
Marc

P.S.: Please Cc: me on replies, both linux-kernel and netdev are too
big for me to timely follow. I am subscribed to both lists, but a Cc
helps in getting a faster reply.

-- 
-----------------------------------------------------------------------------
Marc Haber         | "I don't trust Computers. They | Mailadresse im Header
Mannheim, Germany  |  lose things."    Winona Ryder | Fon: *49 621 72739834
Nordisch by Nature |  How to make an American Quilt | Fax: *49 3221 2323190

             reply	other threads:[~2010-07-24 10:05 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-24  9:26 Marc Haber [this message]
2010-07-26 16:13 ` Allan, Bruce W
2010-07-30 12:56   ` Marc Haber
2010-07-30 17:42     ` Allan, Bruce W
2010-08-01 19:14       ` Marc Haber
2010-08-06  5:46     ` Chuck Ebbert
2010-08-10 12:02       ` Marc Haber
2010-07-28  0:33 ` Tantilov, Emil S
2010-07-30 12:54   ` Marc Haber
2010-08-04 18:23     ` Tantilov, Emil S
2010-08-10 12:04       ` Marc Haber
2010-08-10 16:34         ` Allan, Bruce W
2010-08-12 10:50           ` Marc Haber
2010-08-12 16:12             ` Allan, Bruce W
2010-08-13  1:25           ` Marc Haber
2010-08-13  8:07             ` Marc Haber
2010-08-24  9:45 ` No link on e1000e with 2.6.35.3 " Marc Haber
2010-08-25 18:01   ` Tantilov, Emil S
2010-08-26 11:27     ` Marc Haber
2010-08-26 17:14       ` Marc Haber
2010-08-26 21:31         ` Tantilov, Emil S
2010-09-04  6:33           ` Marc Haber
2010-09-07 19:05             ` Tantilov, Emil S
2010-09-12 21:04               ` Marc Haber
2010-08-26 17:22       ` Tantilov, Emil S
2010-08-26 18:51         ` Maciej W. Rozycki
2010-09-04  6:34         ` Marc Haber
2010-09-07 19:15           ` Tantilov, Emil S

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=20100724092644.GA13353@torres.zugschlus.de \
    --to=mh+linux-kernel@zugschlus.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@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

all inboxes | Powered by JetHome®