Brendan Gregg wrote: >>We've seen this occasionally on some laptops. There can be two reasons: >>1) The driver fails to register its interrupt correctly (The interrupt >>vector number could be wrongly translated) >> >> > >This looks like the case. I haven't found a workaround yet. Anyone know >what intr_vector[] is on x86? (I don't mind an "mdb -kw" hack :). > > > Do you mean autovect[] ? # mdb -k > autovect+8*n::print struct av_head Where n is the vector number.
We can also check the return value of apic_introp_xlate() while inserting the card. I guess the correct return value should be 0xb in your case. Vincent.
