public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Laszlo 'GCS' Boszormenyi <gcs-gKC9iF2I70U@public.gmane.org>
To: "Yu, Luming" <luming.yu-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: dev_zero <dev_xor-eZNTXLQAfP4@public.gmane.org>,
	acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: kacpid problems
Date: Mon, 8 Nov 2004 04:18:22 +0100	[thread overview]
Message-ID: <20041108031822.GA13253@pooh> (raw)
In-Reply-To: <20041108024859.GA12540@pooh>

* Laszlo 'GCS' Boszormenyi <gcs-gKC9iF2I70U@public.gmane.org> [2004-11-08 03:48:59 +0100]:

> > Could you verify if killing kacpid can make the thing better?
>  This just happened to me again. I did /etc/init.d/acpid stop, and it
> did, but issuing halt left me with the acpi_power_off called message.
> I think some memory corruption may happen in kernel space, or it is just
> ACPI failing for some reason.
 OK, just happened again, so update: I did /etc/init.d/acpid stop; but
as I saw CPU usage went to half kernel space, half user space. But(!)
now I can confirm that kacpid with pid 5 stuck in a D state, tried to do
something, but the box was so crawling that I chose to pull out the cord
instead.

HTH,
Laszlo



-------------------------------------------------------
This SF.Net email is sponsored by:
Sybase ASE Linux Express Edition - download now for FREE
LinuxWorld Reader's Choice Award Winner for best database on Linux.
http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click

  reply	other threads:[~2004-11-08  3:18 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-08  1:58 kacpid problems Yu, Luming
2004-11-08  2:48 ` Laszlo 'GCS' Boszormenyi
2004-11-08  3:18   ` Laszlo 'GCS' Boszormenyi [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-11-16  3:29 Yu, Luming
2004-11-11 16:51 Yu, Luming
2004-11-11 16:57 ` dev_zero
2004-11-11 15:32 Yu, Luming
2004-11-11 15:56 ` dev_zero
2004-11-11 16:01 ` dev_zero
2004-11-11 16:37 ` dev_zero
2004-11-11 14:37 Yu, Luming
     [not found] <3ACA40606221794F80A5670F0AF15F84041AC04B@pdsmsx403>
2004-11-10 16:14 ` dev_zero
     [not found] <3ACA40606221794F80A5670F0AF15F84041AC049@pdsmsx403>
2004-11-10 16:06 ` dev_zero
2004-11-10 16:11 ` dev_zero
     [not found] <3ACA40606221794F80A5670F0AF15F84041AC048@pdsmsx403>
2004-11-10 14:40 ` dev_zero
2004-11-10 14:50 ` dev_zero
2004-11-10 14:26 Yu, Luming
2004-11-10 14:35 ` dev_zero
2004-11-10  9:37 Yu, Luming
2004-11-10 13:33 ` dev_zero
     [not found]   ` <20041110133335.84968.qmail-dJK20/AG75nGRxTy+Q50vsz6deESKz/lQQ4Iyu8u01E@public.gmane.org>
2004-11-10 15:44     ` Wang, Zhenyu
     [not found]       ` <20041110154433.GA14613-/VnEId6AORcBH7GVJk7YB9h3ngVCH38I@public.gmane.org>
2004-11-10 15:54         ` Wang, Zhenyu
     [not found]           ` <20041110155455.GA14675-/VnEId6AORcBH7GVJk7YB9h3ngVCH38I@public.gmane.org>
2004-11-10 17:09             ` dev_zero
     [not found]               ` <20041110170945.38831.qmail-uk6eOWkoXtXGRxTy+Q50vsz6deESKz/lQQ4Iyu8u01E@public.gmane.org>
2004-11-11  1:22                 ` Wang, Zhenyu
     [not found]                   ` <20041111012228.GA18032-/VnEId6AORcBH7GVJk7YB9h3ngVCH38I@public.gmane.org>
2004-11-11 15:26                     ` dev_zero
     [not found] <3ACA40606221794F80A5670F0AF15F84041AC042@pdsmsx403>
2004-11-09 17:06 ` dev_zero
2004-11-09 15:50 Yu, Luming
2004-11-09 16:15 ` dev_zero
2004-11-09  8:23 Yu, Luming
2004-11-09 15:12 ` dev_zero
     [not found]   ` <20041109151244.94397.qmail-Njb8tMpsuHHGRxTy+Q50vsz6deESKz/lQQ4Iyu8u01E@public.gmane.org>
2004-11-09 15:45     ` Andrew Barr
2004-11-16  0:36 ` Laszlo 'GCS' Boszormenyi
2004-11-08  3:23 Yu, Luming
2004-11-08 20:41 ` dev_zero
2004-11-05 23:38 dev_zero
     [not found] ` <418C0EFA.6000001-eZNTXLQAfP4@public.gmane.org>
2004-11-06  2:02   ` Laszlo 'GCS' Boszormenyi
2004-11-06 12:58     ` dev_zero

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=20041108031822.GA13253@pooh \
    --to=gcs-gkc9if2i70u@public.gmane.org \
    --cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=dev_xor-eZNTXLQAfP4@public.gmane.org \
    --cc=luming.yu-ral2JQCrhuEAvxtiuMwx3w@public.gmane.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