> > > #define FIRST_DEVICE_VECTOR 0x31
> > > +#define THERMAL_APIC_VECTOR 0x32 /* Thermal monitor local vector */
> > > #define FIRST_SYSTEM_VECTOR 0xef
> >
> > You certainly want to select a different vector.
>
> Whats wrong with that vector? I tried to follow the guidelines as
> specified in hw_irq.h and opted to go for the lower priority ones, or
> is the vector not serviceable due to its range?
You can't use a vector that is in the range assigned to I/O APIC
interrupts (i.e. 0x31 - 0xee). Otherwise you'll get an overlap when the
vector gets assigned to an ordinary IRQ line. Also you probably want a
high-priority interrupt as the condition is serious, if not critical --
system failures, such as bus exceptions, machine check faults, parity
errors, power failures, etc. demand a high priority service.
-- + Maciej W. Rozycki, Technical University of Gdansk, Poland + +--------------------------------------------------------------+ + e-mail: macro@ds2.pg.gda.pl, PGP key available +- 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/