[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <200804110027.06078.rjw@sisk.pl>
Date: Fri, 11 Apr 2008 00:27:05 +0200
From: "Rafael J. Wysocki" <rjw@...k.pl>
To: Ingo Molnar <mingo@...e.hu>
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
On Thursday, 10 of April 2008, Ingo Molnar wrote:
>
> * 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.
Yes, I'll probably do that, but don't have that much time today.
> exactly what kind of system are you using?
It's an Athlon 64 X2 on an ULi-based AsRock motherboard with Radeon X300SE
(PCIe).
> If you revert the trampoline changes, does it get any better - but i guess
> it might be better to do a bisection.
I'll try to figure out what is the last good commit.
Thanks,
Rafael
--
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