From: Ingo Molnar <mingo@elte.hu>
To: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
Cc: Lee Schermerhorn <Lee.Schermerhorn@hp.com>,
linux-ia64 <linux-ia64@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Tony Luck <tony.luck@intel.com>, Ingo Molnar <mingo@redhat.com>,
Bob Picco <bob.picco@hp.com>, Eric Whitney <eric.whitney@hp.com>
Subject: Re: 2.6.25-rc2-mm1 - boot hangs on ia64
Date: Tue, 26 Feb 2008 11:31:38 +0000 [thread overview]
Message-ID: <20080226113138.GC10996@elte.hu> (raw)
In-Reply-To: <20080226202308.FF40.KOSAKI.MOTOHIRO@jp.fujitsu.com>
* KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com> wrote:
> Fujitsu machine can't boot too. my bisect indicate git-sched.patch
> cause regression too.
hm, that's a bit weird - nothing really should have broken it. Could you
try to do a specific bisection of sched-devel.git:
http://people.redhat.com/mingo/sched-devel.git/README
it's just a handful of commits so it should be relatively quick to
figure out. My only guess would be:
Subject: sched: make early bootup sched_clock() use safer
but i think this has been ruled out before ...
Ingo
WARNING: multiple messages have this Message-ID (diff)
From: Ingo Molnar <mingo@elte.hu>
To: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
Cc: Lee Schermerhorn <Lee.Schermerhorn@hp.com>,
linux-ia64 <linux-ia64@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Tony Luck <tony.luck@intel.com>, Ingo Molnar <mingo@redhat.com>,
Bob Picco <bob.picco@hp.com>, Eric Whitney <eric.whitney@hp.com>
Subject: Re: 2.6.25-rc2-mm1 - boot hangs on ia64
Date: Tue, 26 Feb 2008 12:31:38 +0100 [thread overview]
Message-ID: <20080226113138.GC10996@elte.hu> (raw)
In-Reply-To: <20080226202308.FF40.KOSAKI.MOTOHIRO@jp.fujitsu.com>
* KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com> wrote:
> Fujitsu machine can't boot too. my bisect indicate git-sched.patch
> cause regression too.
hm, that's a bit weird - nothing really should have broken it. Could you
try to do a specific bisection of sched-devel.git:
http://people.redhat.com/mingo/sched-devel.git/README
it's just a handful of commits so it should be relatively quick to
figure out. My only guess would be:
Subject: sched: make early bootup sched_clock() use safer
but i think this has been ruled out before ...
Ingo
next prev parent reply other threads:[~2008-02-26 11:31 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-25 15:56 2.6.25-rc2-mm1 - boot hangs on ia64 Lee Schermerhorn
2008-02-25 15:56 ` Lee Schermerhorn
2008-02-26 11:25 ` KOSAKI Motohiro
2008-02-26 11:25 ` KOSAKI Motohiro
2008-02-26 11:31 ` Ingo Molnar [this message]
2008-02-26 11:31 ` Ingo Molnar
2008-02-27 1:42 ` KOSAKI Motohiro
2008-02-27 1:42 ` KOSAKI Motohiro
2008-02-27 7:11 ` Ingo Molnar
2008-02-27 7:11 ` Ingo Molnar
2008-02-28 10:38 ` KOSAKI Motohiro
2008-02-28 10:38 ` KOSAKI Motohiro
2008-02-28 11:50 ` Ingo Molnar
2008-02-28 11:50 ` Ingo Molnar
2008-02-28 12:13 ` KOSAKI Motohiro
2008-02-28 12:13 ` KOSAKI Motohiro
2008-02-28 18:13 ` Andrew Morton
2008-02-28 18:13 ` Andrew Morton
2008-02-28 19:12 ` Ingo Molnar
2008-02-28 19:12 ` Ingo Molnar
2008-02-28 19:24 ` Andrew Morton
2008-02-28 19:24 ` Andrew Morton
2008-02-28 19:32 ` Ingo Molnar
2008-02-28 19:32 ` 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=20080226113138.GC10996@elte.hu \
--to=mingo@elte.hu \
--cc=Lee.Schermerhorn@hp.com \
--cc=akpm@linux-foundation.org \
--cc=bob.picco@hp.com \
--cc=eric.whitney@hp.com \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tony.luck@intel.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.