From: Marc Haber <mh+linux-kernel@zugschlus.de>
To: "Allan, Bruce W" <bruce.w.allan@intel.com>,
"Tantilov, Emil S" <emil.s.tantilov@intel.com>,
Linux Kernel Developers <linux-kernel@vger.kernel.org>,
Linux Kernel Network Developers <netdev@vger.kernel.org>,
"e1000-devel@lists.sf.net" <e1000-devel@lists.sf.net>
Subject: Re: e1000e crashes with 2.6.34.x and ThinkPad T60
Date: Fri, 13 Aug 2010 10:07:36 +0200 [thread overview]
Message-ID: <20100813080736.GA912@torres.zugschlus.de> (raw)
In-Reply-To: <20100813012551.GA25398@torres.zugschlus.de>
On Fri, Aug 13, 2010 at 03:25:51AM +0200, Marc Haber wrote:
> On Tue, Aug 10, 2010 at 09:34:52AM -0700, Allan, Bruce W wrote:
> > We have had other recent reports of issues with this part that are due to
> > ASPM L1 being enabled. Would you please try disabling L1 after the driver
> > is loaded as follows (assuming your adapter is still PCI bus/device/number
> > 02:00.0 as indicated in the lspci output you provided earlier):
> > 1) First check the hexadecimal value of the LnkCtl register -
> > # setpci -s 2:0.0 0xf0
> > 2) Disable ASPM (both L0s and L1) by zeroing out bits 0 and 1 in the value
> > returned by the previous step. For example, if it returned 42 (hex 42,
> > that is) -
> > # setpci -s 2:0.0 0xf0=0x40
> > 3) Confirm ASPM is disabled by checking the output from lspci again.
>
> It returned 42, and after setting 0x40, LnkCtl now says "ASPM Disabled".
>
> I'll dock the system now and will report after the weekend or after
> the first crash.
Didn't work, freeze within the first 60 minutes after starting serious
work. The system did sit idle for the night though without freezing.
Greetings
Marc
--
-----------------------------------------------------------------------------
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
next prev parent reply other threads:[~2010-08-13 8:07 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-24 9:26 Marc Haber
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 [this message]
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=20100813080736.GA912@torres.zugschlus.de \
--to=mh+linux-kernel@zugschlus.de \
--cc=bruce.w.allan@intel.com \
--cc=e1000-devel@lists.sf.net \
--cc=emil.s.tantilov@intel.com \
--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®