lkml.org 
[lkml]   [1998]   [May]   [23]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    From
    SubjectRe: Possible cause of "spurious APIC interrupt"
    Andre M. Hedrick wrote:
    >
    > "spurious APIC interrupt, ayiee, should never happen."
    >
    > results of "lspci -vx" v1.03
    >
    > 00:07.2 USB Controller: Intel Corporation 82371SB PIIX3 USB [Natoma/Triton II]
    > (rev 01)
    > Flags: bus master, medium devsel, latency 64, IRQ ?
    > I/O ports at ef40
    > 00: 86 80 20 70 05 00 80 02 01 00 03 0c 00 40 00 00
    > 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
    > 20: 41 ef 00 00 00 00 00 00 00 00 00 00 00 00 00 00
    > 30: 00 00 00 00 00 00 00 00 00 00 00 00 ff 04 00 00
    >
    > I have noted that I only get this message if I enable the USB support
    > in the BIOS of my P6DNF. It seems that IO-APIC irq-translations
    > stick the USB irq at 0xff 255. Since the latest SMP code flags against
    > an interrupt of 0xff, this may be the need insight for catching
    > and handling that "spurious APIC interrupt".
    In my case (same MB, 2 PPro233) I *don't* have USB enabled (at least
    it's not in /proc/pci) and I *do* get spurious APIC interrupts. (see my
    message several hours ago). Let's check what other common hardware we
    have - maybe we'll be able to find the problem.

    here's my /proc/pci:
    PCI devices found:
    Bus 0, device 0, function 0:
    Host bridge: Intel 82441FX Natoma (rev 2).
    Medium devsel. Fast back-to-back capable. Master Capable.
    Latency=32.
    Bus 0, device 7, function 0:
    ISA bridge: Intel 82371SB PIIX3 ISA (rev 1).
    Medium devsel. Fast back-to-back capable. Master Capable. No
    bursts.
    Bus 0, device 7, function 1:
    IDE interface: Intel 82371SB PIIX3 IDE (rev 0).
    Medium devsel. Fast back-to-back capable. Master Capable.
    Latency=32.
    I/O at 0xffa0 [0xffa1].

    ^^^^ You probably have these 3 + USB ^^^^

    Bus 0, device 17, function 0:
    Display controller: Matrox Millennium (rev 1).
    Medium devsel. Fast back-to-back capable. IRQ 10.
    Non-prefetchable 32 bit memory at 0xfebf8000 [0xfebf8000].
    Prefetchable 32 bit memory at 0xf6000000 [0xf6000008].

    ^^^^ souldn't be a problem - especially in text mode, when it's not used
    at all.

    Bus 0, device 18, function 0:
    SCSI storage controller: NCR 53c825 (rev 2).
    Medium devsel. IRQ 11. Master Capable. Latency=32.
    I/O at 0xec00 [0xec01].
    Non-prefetchable 32 bit memory at 0xfebfff00 [0xfebfff00].

    ^^^^ can be problem. I get more interrupts when doing maxe -j bzImage.
    But I also get them even if I do some make on IDE disk.

    Bus 0, device 19, function 0:
    VGA compatible controller: S3 Inc. Trio32/Trio64 (rev 84).
    Medium devsel. IRQ 12.
    Non-prefetchable 32 bit memory at 0x80000000 [0x80000000].
    ^^^^ This is the one that is used when Im in text mode.

    Bus 0, device 20, function 0:
    Ethernet controller: 3Com 3C905 100bTX (rev 0).
    Medium devsel. IRQ 13. Master Capable. Latency=32. Min
    Gnt=3.Max Lat=8.
    I/O at 0xef00 [0xef01].
    ^^^^ Hmm... you got some tulip card - DEC or SMC I guess.

    /proc/interrupts:
    CPU0 CPU1
    0: 6573223 2207 XT-PIC timer
    1: 28565 25753 IO-APIC-edge keyboard
    2: 0 0 XT-PIC cascade
    4: 30387 29912 IO-APIC-edge serial
    5: 8106 10986 IO-APIC-edge Sound Blaster 16
    8: 1 0 IO-APIC-edge rtc
    13: 1 0 XT-PIC fpu
    14: 25525 27896 IO-APIC-edge ide0
    ^^^^ your IDEs are level!
    17: 2583 2581 IO-APIC-level ncr53c8xx
    19: 19070 19051 IO-APIC-level 3c905 Boomerang 100baseTx
    NMI: 0
    IPI: 0

    Character devices:
    1 mem
    2 pty
    3 ttyp
    4 ttyp
    5 cua
    6 lp
    ^^^^ you don't have that one
    7 vcs
    10 misc
    14 snd

    and I don't have netlink. BTW, Im on ALSA (+some changes I made)


    Block devices:
    2 fd
    3 ide0
    8 sd

    no loop & no ide[123]. BTW, your ide1 isn't in /proc/interrupts...

    Vadim

    -
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.rutgers.edu

    \
     
     \ /
      Last update: 2005-03-22 13:42    [W:0.032 / U:0.148 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site