lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <d557139bacb2f079787b50f684b2aea8cd6988af@8b5064a13e22126c1b9329f0dc35b8915774b7c3.invalid>
Date:	Tue, 2 Sep 2008 12:20:00 +0100
From:	"Simon Arlott" <simon@...e.lp0.eu>
To:	"Pavel Machek" <pavel@...e.cz>
Cc:	linux-pm@...ts.linux-foundation.org,
	"Linux Kernel Mailing List" <linux-kernel@...r.kernel.org>
Subject: Re: [linux-pm] Tyan S2923-E suspend to ram fails to resume

On Tue, September 2, 2008 09:07, Pavel Machek wrote:
> On Sat 2008-08-23 17:47:10, Simon Arlott wrote:
>> On 12/08/08 11:31, Pavel Machek wrote:
>>> 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?

Tyan is going to look into it based them being able to use a common Linux
system (Knoppix 5.1.1) that fails to resume for me.

I've tried Windows XP 64-bit SP2C, that will only go to S1.
Vista Ultimate 64-bit will only go to S1 too.

I've yet to try a BSD, but it'll be a couple of weeks before I can do
that.

-- 
Simon Arlott
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ