From: Pavel Machek <pavel@ucw.cz>
To: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
Cc: lenb@kernel.org, linux-acpi@vger.kernel.org,
kernel list <linux-kernel@vger.kernel.org>,
ibm-acpi-devel@lists.sourceforge.net,
platform-driver-x86@vger.kernel.org
Subject: Re: thinkpad x60: critical thermal shutdown does not work (and ethernet overheats)
Date: Fri, 27 Sep 2013 12:22:54 +0200 [thread overview]
Message-ID: <20130927102254.GC18121@amd.pavel.ucw.cz> (raw)
In-Reply-To: <20130923120256.GB29847@khazad-dum.debian.net>
On Mon 2013-09-23 09:02:56, Henrique de Moraes Holschuh wrote:
> On Mon, 23 Sep 2013, Pavel Machek wrote:
> > > I have rather old thinkpad x60 here. Long time ago, I noticed that on
> > > high continuous ethernet load, it shuts itself down in regular
> > > way. I traced it down to overheat, followed by ACPI signaling system
> > > to go down.
> >
> > just to wrap the story up... after fixing pcie aspm problems,
> > ethernet apparently stopped overheating.
>
> And that means a new kernel with fixed ASPM handling, or disabling ASPM
> entirely, or what?
That means single-line forcing ASPM to be disabled, even through linux
is normally not able to disable ASPM when it is not supported by the
BIOS. Someone at Intel knows about the problem, hopefully they will
present some better solution...
> Good to know it can be handled by a software fix, though!
Yes :-). [I wonder if it happens on other X60 machines, too?]
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
prev parent reply other threads:[~2013-09-27 10:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-15 18:10 thinkpad x60: critical thermal shutdown does not work (and ethernet overheats) Pavel Machek
2013-09-23 10:42 ` Pavel Machek
2013-09-23 12:02 ` Henrique de Moraes Holschuh
2013-09-27 10:22 ` Pavel Machek [this message]
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=20130927102254.GC18121@amd.pavel.ucw.cz \
--to=pavel@ucw.cz \
--cc=hmh@hmh.eng.br \
--cc=ibm-acpi-devel@lists.sourceforge.net \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=platform-driver-x86@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;
as well as URLs for NNTP newsgroup(s).