From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Ingo Molnar <mingo@elte.hu>
Cc: Andrew Morton <akpm@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>, Pavel Machek <pavel@ucw.cz>,
Thomas Gleixner <tglx@linutronix.de>, "H. Anvin" <hpa@zytor.com>
Subject: Re: x86 git tree broken
Date: Fri, 11 Apr 2008 00:27:05 +0200 [thread overview]
Message-ID: <200804110027.06078.rjw@sisk.pl> (raw)
In-Reply-To: <20080410205106.GB15440@elte.hu>
On Thursday, 10 of April 2008, Ingo Molnar wrote:
>
> * Rafael J. Wysocki <rjw@sisk.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
next prev parent reply other threads:[~2008-04-10 22:27 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-10 19:59 x86 git tree broken Rafael J. Wysocki
2008-04-10 20:13 ` Ingo Molnar
2008-04-10 20:25 ` Rafael J. Wysocki
2008-04-10 20:29 ` Ingo Molnar
2008-04-10 20:38 ` Ingo Molnar
2008-04-10 22:28 ` Rafael J. Wysocki
2008-04-11 19:26 ` x86 git tree broken (bisected) Rafael J. Wysocki
2008-04-11 20:23 ` Rafael J. Wysocki
2008-04-11 20:29 ` Rafael J. Wysocki
2008-04-11 20:26 ` Yinghai Lu
2008-04-11 20:51 ` Rafael J. Wysocki
2008-04-11 21:11 ` Yinghai Lu
2008-04-11 21:21 ` Rafael J. Wysocki
2008-04-11 21:31 ` Yinghai Lu
2008-04-13 8:24 ` Yinghai Lu
2008-04-13 8:41 ` Yinghai Lu
2008-04-13 16:14 ` Rafael J. Wysocki
2008-04-14 9:02 ` Ingo Molnar
2008-04-13 16:12 ` Rafael J. Wysocki
2008-04-13 18:07 ` Yinghai Lu
2008-04-13 18:47 ` Rafael J. Wysocki
2008-04-13 18:53 ` Yinghai Lu
2008-04-13 18:54 ` Yinghai Lu
2008-04-13 22:00 ` Yinghai Lu
2008-04-13 22:10 ` Rafael J. Wysocki
2008-04-13 22:32 ` Yinghai Lu
2008-04-13 23:41 ` Rafael J. Wysocki
2008-04-13 23:45 ` H. Peter Anvin
2008-04-14 0:09 ` Rafael J. Wysocki
2008-04-14 0:12 ` H. Peter Anvin
2008-04-14 0:19 ` Rafael J. Wysocki
2008-04-14 1:42 ` Yinghai Lu
2008-04-14 9:16 ` Ingo Molnar
2008-04-14 18:08 ` Yinghai Lu
2008-04-14 20:21 ` Rafael J. Wysocki
2008-04-14 21:06 ` Yinghai Lu
2008-04-14 21:09 ` Rafael J. Wysocki
2008-04-14 21:36 ` Yinghai Lu
2008-04-13 7:51 ` Ingo Molnar
2008-04-13 7:59 ` Yinghai Lu
2008-04-13 7:58 ` [rfc] hw resource debugging checks (was: Re: x86 git tree broken (bisected)) Ingo Molnar
2008-04-13 8:18 ` Yinghai Lu
2008-04-13 9:19 ` Ingo Molnar
2008-04-13 9:39 ` [rfc] hw resource debugging checks Andi Kleen
2008-04-13 17:53 ` Arjan van de Ven
2008-04-13 18:19 ` Yinghai Lu
2008-04-13 18:29 ` Andi Kleen
2008-04-13 19:29 ` Yinghai Lu
2008-04-14 3:52 ` Arjan van de Ven
2008-04-14 5:01 ` Yinghai Lu
2008-04-14 14:12 ` Arjan van de Ven
2008-04-14 18:11 ` Yinghai Lu
2008-04-13 15:48 ` [rfc] hw resource debugging checks (was: Re: x86 git tree broken (bisected)) Arjan van de Ven
2008-04-10 20:51 ` x86 git tree broken Ingo Molnar
2008-04-10 22:27 ` Rafael J. Wysocki [this message]
2008-04-11 6:43 ` Ingo Molnar
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=200804110027.06078.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=akpm@linux-foundation.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=pavel@ucw.cz \
--cc=tglx@linutronix.de \
/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