public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Russell King <rmk+lkml@arm.linux.org.uk>
To: Mike Cumings <mcumings@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Yenta CardBus IRQ storm disabling interrupt
Date: Sat, 29 Jan 2005 20:53:45 +0000	[thread overview]
Message-ID: <20050129205345.A14428@flint.arm.linux.org.uk> (raw)
In-Reply-To: <1295c7b005012912423352cd9d@mail.gmail.com>; from mcumings@gmail.com on Sat, Jan 29, 2005 at 12:42:17PM -0800

On Sat, Jan 29, 2005 at 12:42:17PM -0800, Mike Cumings wrote:
> In my Googling, I encountered a thread on January 10th of this year entitled
> "yenta_socket rapid fires interrupts" (between Dick Hollenbeck, Linus,
> and others)

Out of interest, is it the same cardbus card you're inserting into
the socket as the problem mentioned above?

I think what is suspected is that the Cardbus card is holding its
interrupt output active.  This normally shares the same interrupt
as the yenta socket status change interrupt, and, since we're
listening for interrupts from the card, it causes this problem.

A thought: can you reproduce this problem with 2.4?  Has this cardbus
card been used with other Linux kernels?  On other machines?

I suspect what you'll find is that any Linux kernel on any machine
with this card will exhibit this problem - which would prove my
theory.

-- 
Russell King
 Linux kernel    2.6 ARM Linux   - http://www.arm.linux.org.uk/
 maintainer of:  2.6 PCMCIA      - http://pcmcia.arm.linux.org.uk/
                 2.6 Serial core

  reply	other threads:[~2005-01-29 20:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-29 20:42 Yenta CardBus IRQ storm disabling interrupt Mike Cumings
2005-01-29 20:53 ` Russell King [this message]
2005-01-29 20:57   ` Mike Cumings
2005-01-29 22:04     ` Mike Cumings

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20050129205345.A14428@flint.arm.linux.org.uk \
    --to=rmk+lkml@arm.linux.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mcumings@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox