public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Adam Pigg <piggz1@gmail.com>
To: linux-acpi@vger.kernel.org
Subject: Re: Problems with Toshiba Satellite L355
Date: Fri, 6 Feb 2009 18:06:49 +0000	[thread overview]
Message-ID: <200902061806.51475.adam@piggz.co.uk> (raw)
In-Reply-To: <1233883554.3625.8.camel@localhost.localdomain>

On Friday 06 February 2009 01:25:54 yakui_zhao wrote:
> On Fri, 2009-02-06 at 07:11 +0800, Adam Pigg wrote:
> > Hi
> >
> > i have 2 acpi related (i think) problems with my satellite l355 which i
> > hope someone can help with.
> >
> > 1. /proc/acpi/ac_adapter.../state always show the correct state, but
> > acpi_listen and lshal --monitor dont see any un/plug events.
>
> Will you please do the following test?
>    a. kill the process which is using /proc/acpi/event (Use the command
> of "lsof /proc/acpi/event" to get the process ID)
>    b. grep . /sys/firmware/acpi/interrupts/* >interrupts_before;
>    c. cat /proc/acpi/event . then you plug/unplug the AC adapter and see
> whether the ACPI event can be reported
>    d. after the test, grep . /sys/firmware/acpi/interrupts/* >
> interrupts_after
>
I did the above.  Nothing was reported in step c, and there was no differences 
between the two interrupt files.  I have created bug #12641 with all the info 
asked for.
Cheers
>    If no ACPI event is reported, will you please file a bug report at
> http://bugzilla.kernel.org/enter_bug.cgi?product=ACPI and attach the
> output of acpidump, lspci -vxxx ?
>    Thanks.
>
now to try this.......
> > 2. The machine will suspend to ram, resume, but after a second suspend,
> > wont resume.
>
>      Will you please add the boot option of "acpi_sleep=s3_beep" and do
> the following test?
>     a. kill the process which is using /proc/acpi/event
>     b. echo mem > /sys/power/state; dmesg >dmesg_after;
>     c. press the power button and see whether the box can be resumed.
>
>     If it can't be resumed, please reboot the system and check whether
> there exists the file of "dmesg_after".
>     Thanks.
>
> > I think i saw a similar sounding problem on an R500, but it was fixed.
> >
> > Ive attached the output of dmidecode, and am using 2.6.29rc3.
> >
> > Anything else that will  help let me know.
> >
> > Cheers
> >
> > Adam



  reply	other threads:[~2009-02-06 18:09 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-05 23:11 Problems with Toshiba Satellite L355 Adam Pigg
2009-02-06  1:25 ` yakui_zhao
2009-02-06 18:06   ` Adam Pigg [this message]
2009-02-06 18:47   ` Adam Pigg
2009-02-09  3:31     ` yakui_zhao
2009-02-09 20:03       ` Adam Pigg
2009-02-06 21:57   ` Adam Pigg
2009-02-08 19:09 ` Rafael J. Wysocki

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=200902061806.51475.adam@piggz.co.uk \
    --to=piggz1@gmail.com \
    --cc=adam@piggz.co.uk \
    --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