Messages in this thread | | | Date | Sun, 26 Sep 2010 23:13:36 -0700 | From | Greg KH <> | Subject | Re: [stable] PROBLEM: [BISECTED] 2.6.35.5 xen domU panics just after the boot |
| |
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
| |