public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: Len Brown <lenb@kernel.org>
Cc: Christoph Hellwig <hch@lst.de>, Zhang Rui <rui.zhang@intel.com>,
	linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: regression: 2.6.32-rc8 shuts down after reaching critical temperature
Date: Thu, 26 Nov 2009 11:35:32 +0100	[thread overview]
Message-ID: <20091126103532.GA26905@lst.de> (raw)
In-Reply-To: <alpine.LFD.2.00.0911251804230.9675@localhost.localdomain>

[-- Attachment #1: Type: text/plain, Size: 391 bytes --]

On Wed, Nov 25, 2009 at 06:07:51PM -0500, Len Brown wrote:
> I thought that rc8 boots, but overheats - can you capture
> the dmesg before it overheats?

Here's a dmesg from ~ 30 seconds before it overheated.  The workload
was:

 - boot
 - log into X
 - start a kernel compile using make -j4
 - ssh into another box to read mail in parallel
 - take dmesgs semi-regularly in yet another xterm

[-- Attachment #2: dmesg.bz2 --]
[-- Type: application/octet-stream, Size: 18073 bytes --]

  parent reply	other threads:[~2009-11-26 10:36 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-25 10:28 regression: 2.6.32-rc8 shuts down after reaching critical temperature Christoph Hellwig
2009-11-25 21:56 ` Len Brown
2009-11-25 22:13   ` Christoph Hellwig
2009-11-25 23:07     ` Len Brown
2009-11-26 10:17       ` Christoph Hellwig
2009-11-26 10:35       ` Christoph Hellwig [this message]
2009-12-02 15:14   ` Christoph Hellwig
2009-11-26  2:23 ` Henrique de Moraes Holschuh
2009-11-26  9:52   ` Christoph Hellwig
2009-12-02 11:56     ` Thomas Renninger
2009-12-02 13:30       ` Christoph Hellwig
2009-12-02 15:07         ` Thomas Renninger
2009-12-02 15:35           ` Christoph Hellwig
2009-12-11  6:49             ` Len Brown

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=20091126103532.GA26905@lst.de \
    --to=hch@lst.de \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rui.zhang@intel.com \
    /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