linux-kernel - Re: x86 git tree broken

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <20080410205106.GB15440@elte.hu>
Date:	Thu, 10 Apr 2008 22:51:06 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	"Rafael J. Wysocki" <rjw@...k.pl>
Cc:	Andrew Morton <akpm@...ux-foundation.org>,
	LKML <linux-kernel@...r.kernel.org>, Pavel Machek <pavel@....cz>,
	Thomas Gleixner <tglx@...utronix.de>,
	"H. Anvin" <hpa@...or.com>
Subject: Re: x86 git tree broken

* Rafael J. Wysocki <rjw@...k.pl> wrote:

> Second, if I try to suspend the box to RAM, it enters a state it 
> cannot leave until power is physically cut from it (using the power 
> button to power off / power on the box doesn't help).

i used your config on an AMD system here and s2ram works just fine, both 
using CONFIG_PM_TEST_SUSPEND=y bootup suspend self-test [which x86.git 
QA uses all the time], and using a manual pm-suspend command at the 
console.

you can also try your luck and remove the last 20% of x86.git [which is 
always the newest stuff], by picking a commit 200 patches down the line, 
via:

 git-rev-list x86/base..x86/latest | head -200 | tail -1

and testing that. If that tree works, it's the last 200 commits that 
break stuff.

exactly what kind of system are you using? If you revert the trampoline 
changes, does it get any better - but i guess it might be better to do a 
bisection.

	Ingo
--
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/