public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Thomas Renninger <trenn@suse.de>
To: Brian Schau <brian.schau@gmail.com>
Cc: Len Brown <lenb@kernel.org>, linux-acpi@vger.kernel.org
Subject: Re: Unexpected shutdown - perhaps ACPI related?
Date: Thu, 9 Oct 2008 15:03:51 +0200	[thread overview]
Message-ID: <200810091503.51617.trenn@suse.de> (raw)
In-Reply-To: <4b97db550810090440j5815793ar7e09b3fd7a0b141c@mail.gmail.com>

On Thursday 09 October 2008 13:40:36 Brian Schau wrote:
> Hi,
>
> > Thomas' guess is a good one.  See if this is thermal related.
> > load your cpu with a copy of "cat /dev/zero > /dev/null
> > for each core.  Listen for fans to speed up,
>
> I did so for 10 minutes and the temperatur never rose beyond 72 deg C.
> I also did some other work during that time.
> I couldn't get it to shutdown ...
>
> BTW, the system is a dual core 2GHz system.
>
> > grep . /proc/acpi/thermal*/*/* /proc/acpi/fan/*/*
>
> root@stacy:~# grep . /proc/acpi/thermal*/*/* /proc/acpi/fan/*/*
> /proc/acpi/thermal_zone/THRM/cooling_mode:<setting not supported>
> /proc/acpi/thermal_zone/THRM/polling_frequency:<polling disabled>
> /proc/acpi/thermal_zone/THRM/state:state:                   ok
> /proc/acpi/thermal_zone/THRM/temperature:temperature:             73 C
> /proc/acpi/thermal_zone/THRM/trip_points:critical (S5):           104 C
> grep: /proc/acpi/fan/*/*: No such file or directory
73 C is beyond 72 C :)
104 sounds as if the HW would switch off before, could still be a thermal 
issue. Hmm, but the fans seem to be controlled by HW...

> wrt.to the last line (grep error) - the 'fan' modules is loaded but
> there are not
> files present in the /proc/acpi/fan directory.
>
> Also, when I see the shutdowns it occurs as you described above - the
> hardware shutdown.
Means, the power just gets switched off?
You should try to reproduce this easier somehow. Heavy battery/thermal 
reading, switching cpufreq up and down or something?
How often does that happen?
If it happens often you could try to exclude/not load ACPI drivers, cpufreq 
drivers. Switch off C-states. These are good candidates.

Does this only happen with X?
Maybe using another X driver (vesa fb) solves it?

Did this machine ever worked fine with older kernels/distributions?

     Thomas

  reply	other threads:[~2008-10-09 13:03 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-08 10:02 Unexpected shutdown - perhaps ACPI related? Brian Schau
2008-10-08 10:23 ` Thomas Renninger
2008-10-08 19:14   ` Len Brown
2008-10-09 11:40     ` Brian Schau
2008-10-09 13:03       ` Thomas Renninger [this message]
2008-10-09 16:40         ` Len Brown
2008-10-10  7:58         ` Brian Schau
2008-10-10  5:40       ` Zhao Yakui

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=200810091503.51617.trenn@suse.de \
    --to=trenn@suse.de \
    --cc=brian.schau@gmail.com \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@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