public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Roman Rumisek <romrum@cbox.cz>
To: linux-acpi@vger.kernel.org
Subject: Re: Acpi suspend to ram on Acer Aspire 5672
Date: Mon, 05 Nov 2007 10:27:24 +0100	[thread overview]
Message-ID: <fgmnkg$9eu$1@ger.gmane.org> (raw)
In-Reply-To: 472E40DE.4090001@salfischberger.nl

Hi,

Tomas Salfischberger wrote:

> Hi,
> 
> Roman Rumisek wrote:
>> I have this problem on ACER Extensa 5220.
>> The "save to disk" is OK,but after "save to RAM" the notebook hangs
>> and seems (for example when i press CapsLock key - nothing) one is dead.
>>   
> 
> I also received an off-list reply from Peter Pregler about his Acer TM
> 3200 having the same issues.
> 
> What we need to debug this is some method of first finding out whether
> the kernel-code is actually reached during the resume process. If it is
> actually executing kernel-code, we need to debug at which point in
> hardware initialization it gets stuck.
> 
> Peter mentioned we need serial-port access (or a special firewire-cable)
> to debug. Do you have a docking-station?

No, only notebook.

> 
> An other approach would be to patch the kernel to use the system-speaker
> to output some debug beeps. I'll look into that the next moment I have a
> few spare hours, probably Thursday.
> 
> Just to get more details: Is the "Acer Extensa 5220" a dual core model?

May be, but I have notebook with D530 Celeron.

Roman


> 
> Thanks for your reply,
> 
> Tomas
> -
> To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html



      reply	other threads:[~2007-11-05  9:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-31  9:15 Acpi suspend to ram on Acer Aspire 5672 Tomas Salfischberger
2007-11-04 16:56 ` Roman Rumisek
2007-11-04 21:59   ` Tomas Salfischberger
2007-11-05  9:27     ` Roman Rumisek [this message]

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='fgmnkg$9eu$1@ger.gmane.org' \
    --to=romrum@cbox.cz \
    --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