From: Jes Sorensen <jes@sgi.com>
To: linux-ia64@vger.kernel.org
Subject: Re: panic from vector domain patch (was RE: Linus' tree broken?)
Date: Tue, 31 Jul 2007 14:34:41 +0000 [thread overview]
Message-ID: <46AF4881.504@sgi.com> (raw)
In-Reply-To: <1185239265.19353.6.camel@phobos>
Doug Chapman wrote:
> FYI, booting for me just fine on a RHEL5 installed base. What distro
> were you booting on?
Ok, I figured out which patch caused it, now to figure out whats wrong
and how to fix it :(
Jes
jes@eye:~/src/kernel/linus/lguest/linux-2.6-lguest> git bisect
bad0aa366f351d044703e25c8425e508170e80d83b1 is first bad commit
commit 0aa366f351d044703e25c8425e508170e80d83b1
Author: Tony Luck <tony.luck@intel.com>
Date: Fri Jul 20 11:22:30 2007 -0700
[IA64] Convert to generic timekeeping/clocksource
This is a merge of Peter Keilty's initial patch (which was
revived by Bob Picco) for this with Hidetoshi Seto's fixes
and scaling improvements.
Acked-by: Bob Picco <bob.picco@hp.com>
Signed-off-by: Tony Luck <tony.luck@intel.com>
prev parent reply other threads:[~2007-07-31 14:34 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-24 1:07 panic from vector domain patch (was RE: Linus' tree broken?) Doug Chapman
2007-07-24 2:06 ` Doug Chapman
2007-07-24 2:26 ` Yasuaki Ishimatsu
2007-07-24 13:09 ` Yasuaki Ishimatsu
2007-07-24 13:55 ` Doug Chapman
2007-07-24 14:28 ` Kenji Kaneshige
2007-07-25 0:19 ` Yasuaki Ishimatsu
2007-07-25 1:12 ` Doug Chapman
2007-07-25 2:55 ` Doug Chapman
2007-07-25 5:09 ` Doug Chapman
2007-07-25 8:59 ` Kenji Kaneshige
2007-07-25 13:03 ` Doug Chapman
2007-07-25 13:37 ` Horms
2007-07-25 15:26 ` Doug Chapman
2007-07-26 1:31 ` Horms
2007-07-26 2:55 ` Horms
2007-07-30 9:56 ` Jes Sorensen
2007-07-30 13:42 ` Doug Chapman
2007-07-30 13:53 ` Jes Sorensen
2007-07-31 14:34 ` Jes Sorensen [this message]
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=46AF4881.504@sgi.com \
--to=jes@sgi.com \
--cc=linux-ia64@vger.kernel.org \
/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.