Messages in this thread | | | From | (Eric W. Biederman) | Subject | Re: [patch 00/21] 2.6.19-stable review | Date | Wed, 21 Feb 2007 13:13:16 -0700 |
| |
Andrew Morton <akpm@linux-foundation.org> writes:
> On Wed, 21 Feb 2007 14:31:41 -0500 > Chuck Ebbert <cebbert@redhat.com> wrote: >> What is the status of: >> >> > http://www.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.20/2.6.20-mm2/broken-out/x86_64-mm-simplfy-__assign_irq_vector.patch >> > http://www.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.20/2.6.20-mm2/broken-out/x86_64-mm-handle-irqs-pending-in-irr-during-irq-migration.patch > > That's mainly an Andi decision. Let's cc him. > >> They fix a serious bug that causes machines to freeze up >> or just run very slowly. >> >> I'd like to see these in -stable if possible. > > They're not even in mainline yet.
If you don't have it you at least want the patch below. It generally makes the bug non-fatal.
I'm still working my way through possible fixes... Although the patch in question is close, and normally fixes it in my utmost paranoia I can still find problems with it.
Eric
commit 2fb12a9bca5ad9aa6dcd2c639b4a7656a8843ef8 Author: Eric W. Biederman <ebiederm@xmission.com> Date: Tue Feb 13 13:26:25 2007 +0100
[PATCH] x86-64: survive having no irq mapping for a vector
Occasionally the kernel has bugs that result in no irq being found for a given cpu vector. If we acknowledge the irq the system has a good chance of continuing even though we dropped an irq message. If we continue to simply print a message and not acknowledge the irq the system is likely to become non-responsive shortly there after.
AK: Fixed compilation for UP kernels
Signed-off-by: Eric W. Biederman <ebiederm@xmission.com> Signed-off-by: Andi Kleen <ak@suse.de> Cc: "Luigi Genoni" <luigi.genoni@pirelli.com> Cc: Andi Kleen <ak@suse.de> Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |