diff options
| author | Eric W. Biederman <[email protected]> | 2008-08-10 00:35:50 -0700 |
|---|---|---|
| committer | Ingo Molnar <[email protected]> | 2008-08-11 10:39:04 +0200 |
| commit | 3c7569b284e1be55d086b61a70d9f545326f6d74 (patch) | |
| tree | 18b36c05d17bc92441d1f007084fa4b98b7e9f9b /net/unix/sysctl_net_unix.c | |
| parent | d388e5fdc461344d04307a3fa83862b9ed429647 (diff) | |
x86_64: restore the proper NR_IRQS define so larger systems work.
As pointed out and tracked by Yinghai Lu <[email protected]>:
Dhaval Giani got:
kernel BUG at arch/x86/kernel/io_apic_64.c:357!
invalid opcode: 0000 [1] SMP
CPU 24
...
his system (x3950) has 8 ioapic, irq > 256
This was caused by:
commit 9b7dc567d03d74a1fbae84e88949b6a60d922d82
Author: Thomas Gleixner <[email protected]>
Date: Fri May 2 20:10:09 2008 +0200
x86: unify interrupt vector defines
The interrupt vector defines are copied 4 times around with minimal
differences. Move them all into asm-x86/irq_vectors.h
It appears that Thomas did not notice that x86_64 does something
completely different when he merge irq_vectors.h
We can solve this for 2.6.27 by simply reintroducing the old heuristic
for setting NR_IRQS on x86_64 to a usable value, which trivially removes
the regression.
Long term it would be nice to harmonize the handling of ioapic interrupts
of x86_32 and x86_64 so we don't have this kind of confusion.
Dhaval Giani <[email protected]> tested an earlier version of
this patch by YH which confirms simply increasing NR_IRQS fixes the
problem.
Signed-off-by: Eric W. Biederman <[email protected]>
Acked-by: Yinghai Lu <[email protected]>
Cc: Dhaval Giani <[email protected]>
Cc: Mike Travis <[email protected]>
Cc: Andrew Morton <[email protected]>
Signed-off-by: Ingo Molnar <[email protected]>
Diffstat (limited to 'net/unix/sysctl_net_unix.c')
0 files changed, 0 insertions, 0 deletions