public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Nirmal Govind <nirmalg-8DAjSxpRXgY@public.gmane.org>
To: Micha Feigin <michf-+lLcF8/aw9x6auLlOhE+pQ@public.gmane.org>
Cc: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: problems with acpi (sleep states) on vaio notebook z1sp
Date: Wed, 24 Dec 2003 13:26:10 -0500	[thread overview]
Message-ID: <3FE9DA42.1050909@psu.edu> (raw)
In-Reply-To: <20031224153617.GI1632-4cxDFgrrBECgSpxsJD1C4w@public.gmane.org>


>>
>>I just can say "me too!". My Sony Vaio PCG-F403 (i44BX, P3-450, NeoMagic
>>Graphics) enters S3, but when I press a key, it shuts down completely
>>and can no longer be turned on. Only removing PSU and Battery for a few
>>seconds solves it.
>>
> 
> 
> Haven't checked with the last kernel, but last time I checked my vaio
> pcg-fxa53 also would wake up but would only show a blank screen and no
> other response. Pressing the power button for several seconds shut it
> down and then it would boot up normally (not to the suspended session
> though ;-)

Looks like there are a few of us who have the same problem.. what 
error messages do you get in syslog? If we're all getting similar 
error messages then that may narrow down the problem for the 
developers..

nirmal


-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills.  Sign up for IBM's
Free Linux Tutorials.  Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click

  parent reply	other threads:[~2003-12-24 18:26 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-23  6:34 problems with acpi (sleep states) on vaio notebook z1sp Yu, Luming
     [not found] ` <3ACA40606221794F80A5670F0AF15F8401720C50-SRlDPOYGfgogGBtAFL8yw7fspsVTdybXVpNB7YpNyf8@public.gmane.org>
2003-12-23  7:26   ` Carlo E. Prelz
2003-12-23 17:43   ` Martin Emrich
     [not found]     ` <1072201432.3134.10.camel-NZYYv2kObinUTSZfUHD3qA@public.gmane.org>
2003-12-24 15:36       ` Micha Feigin
     [not found]         ` <20031224153617.GI1632-4cxDFgrrBECgSpxsJD1C4w@public.gmane.org>
2003-12-24 18:26           ` Nirmal Govind [this message]
     [not found]             ` <3FE9DA42.1050909-8DAjSxpRXgY@public.gmane.org>
2003-12-24 22:42               ` Karol Kozimor
     [not found]                 ` <20031224224236.GA25026-DETuoxkZsSqrDJvtcaxF/A@public.gmane.org>
2003-12-25  1:11                   ` Nirmal Govind
     [not found]                     ` <3FEA392B.2020206-8DAjSxpRXgY@public.gmane.org>
2003-12-25  3:48                       ` Nils Spengler
  -- strict thread matches above, loose matches on Subject: below --
2003-12-29  8:20 Ow Mun Heng
2003-12-25  7:35 Yu, Luming
2003-12-24  1:47 Ow Mun Heng
2003-12-23  7:43 Ow Mun Heng
     [not found] ` <C386328088ED7F4E9F81AFBABDDF60DA03B3664F-Yw6hFe9C1vnHQcBQSaPqJq0fmWJ9l57d0E9HWUfgJXw@public.gmane.org>
2003-12-23 16:30   ` Micha Feigin
2003-12-22  2:17 Nils Spengler

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=3FE9DA42.1050909@psu.edu \
    --to=nirmalg-8dajsxprxgy@public.gmane.org \
    --cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=michf-+lLcF8/aw9x6auLlOhE+pQ@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