Most recent kernel where this bug did not occur: 2.6.18 Distribution: FC5 Hardware Environment: Dell Inspiron E1705 Core 2 Duo Software Environment: nothing special Problem Description: Kernel panics within a few minutes of boot Steps to reproduce: seems to happen on its own soon after booting, but occurs every time
Created attachment 9227 [details] panic text
Fixed in this code: commit 994bd4f9f5a065ead4a92435fdd928ac7fd33809 tree 11e5b123bd5c5319a65ad4732ad3965b815dedbb parent c25d5180441e344a3368d100c57f0a481c6944f7 author Eric W. Biederman <ebiederm@xmission.com> 1160628286 -0600 committer Linus Torvalds <torvalds@g5.osdl.org> 1160663850 -0700 [PATCH] x86_64 irq: Properly update vector_irq This patch fixes my one line thinko where I was clearing the vector_irq entries on the wrong cpus. Signed-off-by: Eric W. Biederman <ebiederm@xmission.com> Signed-off-by: Linus Torvalds <torvalds@osdl.org> arch/x86_64/kernel/io_apic.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/arch/x86_64/kernel/io_apic.c b/arch/x86_64/kernel/io_apic.c index c3cdcab..44b55f8 100644 --- a/arch/x86_64/kernel/io_apic.c +++ b/arch/x86_64/kernel/io_apic.c @@ -660,7 +660,7 @@ next: } if (old_vector >= 0) { int old_cpu; - for_each_cpu_mask(old_cpu, domain) + for_each_cpu_mask(old_cpu, irq_domain[irq]) per_cpu(vector_irq, old_cpu)[old_vector] = -1; } for_each_cpu_mask(new_cpu, domain)