Edward Shu wrote:
> Steven Stallion:
>> All,
>>
>> I am noticing that on occasion the RTL8029AS seems to fire an interrupt
>> which is not reflected in the interrupt status register which causes a
>> spurious interrupt warning by pcisch.
>>
>> Any ideas?
>>
>> (Yes, I am clearing the interrupt before returning DDI_INTR_CLAIMED)
>>
> Spurious interrupt is usually caused by the error handling of
> interrupts in device drivers.
> One possible scenario is, a certain driver doesn't claim the interrupt
> belong to its own properly.
> System will regard it as a spurious interrupt because no one claim it.
>
> Can you please provide more information? like "::interrupts" output in
> kmdb, the
> whole spurious interrupt message without shortcut.
Certainly:
[1]> ::interrupts
Device Shared Type MSG # State INO Mondo Pil CPU
re#0 no Fixed --- enbl 0xc 0x20c 6 0
se#0 no Fixed --- enbl 0x22 0x222 12 0
eri#0 no Fixed --- enbl 0x1d 0x21d 6 0
ecpp#0 no Fixed --- enbl 0x1c 0x21c 3 0
lombus#0 no Fixed --- enbl 0x2e 0x22e 12 0
glm#1 no Fixed --- enbl 0x19 0x219 4 0
glm#0 no Fixed --- enbl 0x18 0x218 4 1
ohci#0 no Fixed --- enbl 0x1f 0x21f 9 0
su#0 no Fixed --- enbl 0x2d 0x22d 12 0
pcf8584#1 yes Fixed --- enbl 0x23 0x223 4 0
pcf8584#0 yes Fixed --- enbl 0x23 0x223 4 0
todds1287#0 no Fixed --- enbl 0x24 0x224 15 0
ce#0 no Fixed --- enbl 0x0 0x200 6 1
qlc#0 no Fixed --- enbl 0x4 0x204 4 1
And the dmesg output:
Oct 10 19:21:51 devel pcisch: [ID 781074 kern.warning] WARNING: pcisch0:
spurious interrupt from ino 0xc
Oct 10 19:21:51 devel pcisch: [ID 548919 kern.info] re-0#0
Oct 10 19:21:51 devel pcisch: [ID 100033 kern.info]
--
Yet magic and hierarchy
arise from the same source,
and this source has a null pointer.
Reference the NULL within NULL,
it is the gateway to all wizardry.
_______________________________________________
driver-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/driver-discuss
