Re: Missing interrupts?

no_spam_at_ntlworld.com
Date: 07/21/03

  • Next message: Kalle Kivimaa: "Unable to suspend (S4) with the latest 2.5/2.6 kernels"
    To: "Kathy Frazier" <kfrazier@mdc-dayton.com>, linux-kernel@vger.kernel.org
    Date:	Mon, 21 Jul 2003 21:00:54 +0100
    
    

    Kathy,

    How did you check that the driver was asserting the interrupt? (do you have an
    additional way of monitoring it?) I have yet to fully investigate my problem
    and an additional tool to check if my board is actually asserting the
    interrupt (and to find out how far it gets) would be very handy,

    Thanks for the suggestions - more notes below

    Thanks,

    SA

    > ">>"s truncated....
    > Futhermore, it appears that things on the motherboard are is such a bad
    > state, that no other interrupts are getting through (keyboard, mouse,
    > network, etc). This same board and driver works fine in a Pentium 3
    > system.
    >
    > >Machines test where everything worked: kernels 2.4.18-10 and 2.4.18-24.8.0
    > > on athlon based PCs
    > >
    > >Machine where interrupts failed to appear: kernel 2.4.18-3 on a pentium 4.
    >
    > Are you running these tests using the same board? You might try moving the
    > board for this device driver from the athlon PC to the pentium 4 PC just to
    > insure it is not a problem with the board.

    Same board each time

    >...
    >....
    > Is the value in pi_stage.interrupt assigned from the irq element of the
    > pci_dev structure (returned by pci_find_device routine)? This is the
    > preferred way to obtain your IRQ rather than look directly at your device's
    > config space.

    I am currently inspecting the board config space - I will modify and test - is
    it possible for the config space to be "wrong".

    > Even though you are indicating that you will share the IRQ, have you tried
    > adjusting BIOS settings or moving board to another slot to try to establish
    > a unique IRQ for yourself? That would at least prevent another device
    > driver from getting in your way.

    The card and driver share "nicely" with a random assortment of hardware on the
    "good" machines - I will try to get it a unique (or at least different
    interrupt) on the bad machine (it current shares with usb on int 9 which
    never seems to get any interrupts) and see how this pans out

    > Just curious: Are you receiving any interrupts at all in the pentium 4
    > system? Or is it running for awhile and then missing some? Does a missing
    > interrupt hang your system?

    The bad computer function fine in everyway except for the missing interrupts
    from my card - the card and driver are robust in the sense that they can live
    without the interrupts (performance can suffer though) so this problem is in
    the category annoying and anomolous rather than fatal.

    Ta SA.

    -
    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/


  • Next message: Kalle Kivimaa: "Unable to suspend (S4) with the latest 2.5/2.6 kernels"

    Relevant Pages

    • Re: wireless card driver problem about the "done" bit in the descriptor && the bail caused b
      ... the VxWorks, ... or a "rxdp bail", the whileloop break, while no interrupt to make ... it off and do a jobQueuePostto wake up tNet0. ... processing driver interrupt events in a timely manner. ...
      (comp.os.vxworks)
    • Re: 2.6.19 and up to 2.6.20-rc2 Ethernet problems x86_64
      ... If the system fails in ACPI mode, but works in non-ACPI mode, ... Using ACPI for SMP configuration information ... Using IOAPIC for interrupt routing ... Non-volatile memory driver v1.2 ...
      (Linux-Kernel)
    • Re: [PATCH] uio: User IRQ Mode
      ... This patch adds a "User IRQ Mode" to UIO. ... In this mode the user space driver ... is responsible for acknowledging and re-enabling the interrupt. ...
      (Linux-Kernel)
    • [PATCH 06/13] Char: cyclades, overall cleanup
      ... * Prevent users from opening non-existing Z ports. ... * Implemented full support for non-standard baud rates. ... * Driver now reports physical instead of virtual memory addresses. ... * Fixed SMP locking in Cyclom-Y interrupt handler. ...
      (Linux-Kernel)
    • [PATCH 13/79] cyclades: overall cleanup
      ... * Prevent users from opening non-existing Z ports. ... * Implemented full support for non-standard baud rates. ... * Driver now reports physical instead of virtual memory addresses. ... * Fixed SMP locking in Cyclom-Y interrupt handler. ...
      (Linux-Kernel)