From: Andrew Morton <akpm@linux-foundation.org>
To: Frans Pop <elendil@planet.nl>
Cc: "Udo A. Steinberg" <us15@os.inf.tu-dresden.de>,
linux-kernel@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [2.6.23-rc8-mm2] System hangs (loops?) during boot
Date: Sun, 30 Sep 2007 19:24:19 -0700 [thread overview]
Message-ID: <20070930192419.c8b6e96b.akpm@linux-foundation.org> (raw)
In-Reply-To: <200710010207.34430.elendil@planet.nl>
On Mon, 1 Oct 2007 02:07:33 +0200 Frans Pop <elendil@planet.nl> wrote:
> > That excludes all the extra stuff in -mm and should give us a good hint
> > whether HPET is really at fault.
>
> The system does boot with rc8 + hrt1.
>
> Andrew: any suggestions on how to trace the "real" culprit for the hang?
Not really. Ordinarily one could move hpet-force-enable-on-ich34.patch to
start-of-series, then verify that mainline+hpet-force-enable-on-ich34.patch
works correctly, then just bisect all the other patches.
But tht doesn't work because hpet-force-enable-on-ich34.patch has a
dependency on other patches in the hrt-related patch series, and it could
be that the bug which you've exposed is already in mainline anyway.
If you had a minimal, standalone hpet-force-enable-on-ich34.patch against
mainline then you could test that against mainline. If that also failed
then you could git-bisect mainline, applying
hpet-force-enable-on-ich34.patch each time (I've done that before). But
this assumes that you're searching for a regression in minaline. It may
never have worked.
next prev parent reply other threads:[~2007-10-01 2:24 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-28 20:25 [2.6.23-rc8-mm2] System hangs (loops?) during boot Frans Pop
2007-09-29 0:32 ` Frans Pop
2007-09-29 8:37 ` Andrew Morton
[not found] ` <200709292140.23593.elendil@planet.nl>
2007-09-29 20:02 ` Andrew Morton
2007-09-30 13:44 ` Udo A. Steinberg
2007-09-30 21:50 ` Frans Pop
2007-09-30 22:00 ` Udo A. Steinberg
2007-10-01 0:07 ` Frans Pop
2007-10-01 0:44 ` Udo A. Steinberg
2007-10-01 1:12 ` Frans Pop
2007-10-01 2:24 ` Andrew Morton [this message]
2007-09-29 22:15 ` [2.6.23-rc8-mm2] kernel BUG at mm/slab.c:591! | invalid opcode: 0000 [#1] SMP Frans Pop
2007-09-30 10:45 ` Andrew Morton
2007-09-30 22:30 ` Miklos Szeredi
2007-09-30 22:59 ` [2.6.23-rc8-mm2] Fails to resume from s2mem (was:kernel BUG at mm/slab.c:591! ...) Frans Pop
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=20070930192419.c8b6e96b.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=elendil@planet.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=us15@os.inf.tu-dresden.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