From: Jeff Garzik <jgarzik@pobox.com>
To: Zwane Mwaikambo <zwane@linuxpower.ca>
Cc: Daniel Ritz <daniel.ritz@gmx.ch>,
linux-kernel <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@diego.com>
Subject: Re: [bug 2.5.69] xirc2ps_cs, irq 3: nobody cared, shutdown hangs
Date: Sun, 11 May 2003 13:24:56 -0400 [thread overview]
Message-ID: <3EBE8768.4000007@pobox.com> (raw)
In-Reply-To: <Pine.LNX.4.50.0305111202510.15337-100000@montezuma.mastecende.com>
Zwane Mwaikambo wrote:
> @@ -1312,7 +1312,7 @@ xirc2ps_interrupt(int irq, void *dev_id,
> */
>
> if (!netif_device_present(dev))
> - return IRQ_NONE;
> + goto out;
>
> ioaddr = dev->base_addr;
> if (lp->mohawk) { /* must disable the interrupt */
> @@ -1515,6 +1515,7 @@ xirc2ps_interrupt(int irq, void *dev_id,
> * force an interrupt with this command:
> * PutByte(XIRCREG_CR, EnableIntr|ForceIntr);
> */
> + out:
> return IRQ_RETVAL(handled);
> } /* xirc2ps_interrupt */
If this patch works, it's mainly a signal to dig deeper.
If netif_device_present() returns false, we think the hardware has
disappeared. So that implies a bug in calling netif_device_detach() no
a bug in the irq handler return value.
This is _especially_ true for pcmcia, even more than pci. PCI ejects
(including cardbus) are electrically safe, whereas pcmcia is different.
If pcmcia hardware disappears on you, you _really_ don't want to be
bitbanging its ports.
Jeff
next prev parent reply other threads:[~2003-05-11 17:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-11 14:47 [bug 2.5.69] xirc2ps_cs, irq 3: nobody cared, shutdown hangs Daniel Ritz
2003-05-11 16:13 ` Zwane Mwaikambo
2003-05-11 17:24 ` Jeff Garzik [this message]
2003-05-11 17:20 ` Alan Cox
2003-05-11 22:08 ` David Woodhouse
2003-05-11 21:40 ` Alan Cox
2003-05-11 22:55 ` David Woodhouse
2003-05-11 17:31 ` Zwane Mwaikambo
2003-05-12 19:59 ` Daniel Ritz
2003-05-13 7:43 ` Zwane Mwaikambo
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=3EBE8768.4000007@pobox.com \
--to=jgarzik@pobox.com \
--cc=akpm@diego.com \
--cc=daniel.ritz@gmx.ch \
--cc=linux-kernel@vger.kernel.org \
--cc=zwane@linuxpower.ca \
/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