All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Kyle McMartin <kyle@redhat.com>
Cc: James Dingwall <james.dingwall@amdocs.com>,
	Jeremy Fitzhardinge <jeremy.fitzhardinge@citrix.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	stable@kernel.org
Subject: Re: [stable] PROBLEM: [BISECTED] 2.6.35.5 xen domU panics just after the boot
Date: Sun, 26 Sep 2010 23:13:36 -0700	[thread overview]
Message-ID: <20100927061336.GA22721@kroah.com> (raw)
In-Reply-To: <20100927024044.GQ13116@bombadil.infradead.org>

On Sun, Sep 26, 2010 at 10:40:44PM -0400, Kyle McMartin wrote:
> On Thu, Sep 23, 2010 at 04:23:55PM +0100, James Dingwall wrote:
> > > I was experiencing the same immediate crash with a null pointer
> > > dereference (log below) on boot with 2.6.35.5.  Reverting
> > > fb412a178502dc498430723b082a932f797e4763 also resolved the problem for
> > > me.
> > 
> > Checking the diff from this commit it looks like there is a typo in the patch.  With the following (probably mangled by my client) I get 2.6.35.5 to boot.  Suggest it should be a candidate for .32 and .35 stable trees.
> > 
> 
> Greg, a spelling mistake cropped into this patch during 2.6.35.5 that
> James here points out. Adding you to CC since it seems to have missed
> stable 2.6.35.6...
> 
> Was in xen-use-percpu-interrupts-for-ipis-and-virqs.patch.

I don't understand, where did the error come from?  Was it in a patch I
applied, or did I mess up some patch?  Is the same problem upstream, and
if not, why not?

And finally, can you send this in a format that I can apply it?

thanks,

greg k-h

  reply	other threads:[~2010-09-27  6:13 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-23 15:23 Re: PROBLEM: [BISECTED] 2.6.35.5 xen domU panics just after the boot James Dingwall
2010-09-23 17:53 ` Paweł Zuzelski
2010-09-24 18:00 ` Jeremy Fitzhardinge
2010-09-27  2:40 ` Kyle McMartin
2010-09-27  6:13   ` Greg KH [this message]
2010-09-27  6:34     ` [stable] " Kyle McMartin
2010-09-27  8:37       ` [stable] PROBLEM: [BISECTED] 2.6.35.5 xen domU panics just after the boot [PATCH] James Dingwall
2010-09-28 18:29         ` Greg KH
2010-09-27 18:08     ` [stable] PROBLEM: [BISECTED] 2.6.35.5 xen domU panics just after the boot Jeremy Fitzhardinge
2010-09-28 18:29       ` Greg KH
2010-09-29 15:48         ` Jeremy Fitzhardinge
2010-09-30  0:06           ` Greg KH
2010-10-01 16:46             ` Jeremy Fitzhardinge
2010-10-01 18:26               ` Greg KH

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=20100927061336.GA22721@kroah.com \
    --to=greg@kroah.com \
    --cc=james.dingwall@amdocs.com \
    --cc=jeremy.fitzhardinge@citrix.com \
    --cc=kyle@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stable@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.