Hm, somehow that is the git commit I saw, but it probably was b/c it gotcherrypicked in my testing tree.> > Come on people...> > > Author: Suresh Siddha <suresh.b.siddha@intel.com>> > Date: Mon Mar 12 11:36:33 2012 -0700> > > > x86/ioapic: Add register level checks to detect bogus io-apic entries> > > > With out this commit, if the bios lists bogus io-apic's, then we will> > see some error messages ("Unable to reset IRR for apic")during linux> > boot which are benign. But as this patch breaks Xen, I am ok if these> > don't get applied to 'stable'. Also I think it is Ingo who added the> > 'stable' tag. Ingo, are you ok with this?> > What stable trees did this already go into in the releases today?

None. That is why I am sending this advance warning so you don'tput it in.

> > You need to tell me what I need to revert here, SPECIFICALLY, and in> what tree, if needed, otherwise I have no idea what is going on, sorry,> I can't read minds.> > > For the mainline, we have queued more patches to fix the Xen breakage.> > And what is that supposed to mean to me?> > Again, help me out here, this is making no sense at all.> > How am I supposed to "not apply" a patch that I have never heard of?> And how am I supposed to "not apply" a patch that I have already> applied?> > How about you all start over from the beginning and tell me EXACTLY what> you want me to do here, because I sure as heck don't know what is going> on...

Heh.

The patch titled "x86/ioapic: Add register level checks to detect bogus io-apic entries"(git commit 73d63d038ee9f769f5e5b46792d227fe20e442c5) that is in v3.4-rc1, eventhought it has cc: stable@kernel.org, should _NOT_ be applied to the stable tree.