From: Pavel Machek <pavel@suse.cz>
To: Simon Arlott <simon@fire.lp0.eu>
Cc: linux-pm@lists.linux-foundation.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [linux-pm] Tyan S2923-E suspend to ram fails to resume
Date: Tue, 2 Sep 2008 10:07:28 +0200 [thread overview]
Message-ID: <20080902080728.GD15399@elf.ucw.cz> (raw)
In-Reply-To: <48B03F0E.9060605@simon.arlott.org.uk>
On Sat 2008-08-23 17:47:10, Simon Arlott wrote:
> On 12/08/08 11:31, Pavel Machek wrote:
>> On Sat 2008-08-09 15:42:22, Simon Arlott wrote:
>>> On 08/08/08 12:20, Simon Arlott wrote:
>>>> On Fri, August 8, 2008 08:14, Pavel Machek wrote:
>>>>> On Mon 2008-08-04 22:56:07, Simon Arlott wrote:
>>>>>> My system (Tyan S2923-E, dmesg attached) suspends ok in
>>>>>> all pm_test modes, but it won't resume with pm_test
>>>>>> "none".
>>>>>>
>>>>>> [ 6.423515] mem full: hash matches
>>>>>>
>>>>>> When I press the power button, the port 80 display shows:
>>>>>> FF D0 23 01 D0 ... DE
>>>>>> (and again each time I press it)
>>>>>>
>>>>>> If I force it to turn off, then on again:
>>>>>> FF D0 23 01 D0 ... FF D0 23 01 D0 ... (D2?) D3 00 01 D5
>>>>>> D6 <normal boot>
>>>>>>
>>>>>> Any ideas? (onboard SAS is disabled, watchdog is
>>>>>> disabled, everything else is enabled, PCI-E graphics
>>>>>> card)
>>>>>
>>>>> Try verifying if it reaches assembly code under realmode/ ...
>>>
>>> I've tried acpi_sleep=s3_beep, and this:
>>> diff --git a/arch/x86/kernel/acpi/realmode/wakeup.S b/arch/x86/kernel/acpi/realmode/wakeup.S
>>> Which doesn't work either.
>>
>> Yep, that should work. When it does not, it means BIOS is not
>> returning to our real mode code :-(. You may want to try disabling
>> APIC and similar stuff, in hope of working around BIOS bug you are
>> hitting, but ...
>
> I've tried the simplest possible 32-bit UP kernel I could come up with
> (.config attached) and it still doesn't work.
>
> (I modified post_init() to call pm_suspend(PM_SUSPEND_MEM).)
>
> Disassembly of the BIOS shows that DE is indeed part of 0xDEAD, but I
> haven't been able to tell what it's doing between D0 and there... not all
> of the port 80 codes that are displayed are easily visible.
>
> I've tried disabling all the CPU options in the BIOS, e.g. microcode
> update, VM, NMI but it doesn't help. I'm wondering if D0 is the right start
> point for the system - there's a DC code for S3 resume:
...you did a lot of work, but these issues are hard.
Do Windows suspend/resume on same hardware? BSD?
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next prev parent reply other threads:[~2008-09-02 9:23 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-04 21:56 Tyan S2923-E suspend to ram fails to resume Simon Arlott
2008-08-04 21:56 ` Simon Arlott
2008-08-08 7:14 ` Pavel Machek
2008-08-08 7:14 ` [linux-pm] " Pavel Machek
2008-08-08 11:20 ` Simon Arlott
2008-08-08 11:20 ` [linux-pm] " Simon Arlott
2008-08-09 14:42 ` Simon Arlott
2008-08-09 14:42 ` [linux-pm] " Simon Arlott
2008-08-12 10:31 ` Pavel Machek
2008-08-12 10:31 ` [linux-pm] " Pavel Machek
2008-08-23 16:47 ` Simon Arlott
2008-08-23 16:47 ` [linux-pm] " Simon Arlott
2008-09-02 8:07 ` Pavel Machek [this message]
2008-09-02 11:20 ` Simon Arlott
2008-09-02 11:20 ` Simon Arlott
2008-09-02 8:07 ` Pavel Machek
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=20080902080728.GD15399@elf.ucw.cz \
--to=pavel@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=simon@fire.lp0.eu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.