From: "Paweł Zuzelski" <pawelz@pld-linux.org>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: "Jeremy Fitzhardinge" <jeremy.fitzhardinge@citrix.com>,
"Paweł Zuzelski" <pawelz@pld-linux.org>,
"James Dingwall" <james.dingwall@amdocs.com>,
lkml <linux-kernel@vger.kernel.org>,
virtualization@lists.osdl.org, xen-devel@lists.xensource.com
Subject: Re: PROBLEM: [BISECTED] 2.6.35.5 xen domU panics just after the boot
Date: Fri, 24 Sep 2010 07:40:00 +0200 [thread overview]
Message-ID: <20100924054000.GA4689@pzz.touk.pl> (raw)
In-Reply-To: <4C9BEA8C.2030808@goop.org>
On Thu, 23 Sep 2010, Jeremy Fitzhardinge wrote:
> On 09/21/2010 12:05 PM, Paweł Zuzelski wrote:
> > Hello,
> >
> > kernels 2.6.35.5 and 2.6.32.22 xen domU panics at the very begining of the
> > boot process.
> >
> > I have bisected it to a single commit, and the first bad commit is:
> > [fb412a178502dc498430723b082a932f797e4763] xen: use percpu interrupts for IPIs and VIRQs
> >
> > kernel v2.6.35.5 with reverted this commit works for me.
>
> Thanks very much for doing that. I'll have to work out what's going on
> (obviously it doesn't do it for me).
Have you seen the message from James Dingwall?
He had found the typo in fb412a178502dc498430723b082a932f797e4763
commit and sent the patch to lkml that fixes it.
Please, see https://patchwork.kernel.org/patch/202282/ if you have
not received James' mail. That patch resolves the problem for me and
for James.
--
Regards,
Paweł Zuzelski
next prev parent reply other threads:[~2010-09-24 5:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-21 19:05 PROBLEM: [BISECTED] 2.6.35.5 xen domU panics just after the boot Paweł Zuzelski
2010-09-24 0:02 ` [Xen-devel] " Jeremy Fitzhardinge
2010-09-24 2:13 ` Dan Magenheimer
2010-09-24 19:04 ` [Xen-devel] " Jeremy Fitzhardinge
2010-09-24 5:40 ` Paweł Zuzelski [this message]
2010-09-24 18:00 ` Jeremy Fitzhardinge
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=20100924054000.GA4689@pzz.touk.pl \
--to=pawelz@pld-linux.org \
--cc=james.dingwall@amdocs.com \
--cc=jeremy.fitzhardinge@citrix.com \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=virtualization@lists.osdl.org \
--cc=xen-devel@lists.xensource.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).