From: Ulrich Hahn <ulrich.hahn@web.de>
To: Charles Briscoe-Smith <charles@briscoe-smith.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: PCMCIA-related IDE problems - "hda: lost interrupt"
Date: Sun, 03 Mar 2002 22:16:11 +0100 [thread overview]
Message-ID: <3C82929B.48E5E77A@web.de> (raw)
In-Reply-To: <20020302122339.A31436@merry.bs.lan>
Hi there -
I was lucky today finding another solution that helped me out:
It seems the 2.4 kernel series produce the problem of messing with PCI
interrupts.
I had no problem with one and the same pcmcia_cs package with a 2.2.9 kernel
which locked up ALL of the 2.4 kernels I tried meanwile (I am on 2.4.18 now
using the kernel-owned pcmcia modules, yenta_socket, which does not seem to know
any parameters at all).
Today I found a hint on giving the kernel an irqmask on bootup in the lilo.conf
file:
append="pci=irqmask=0xafff"
This prevents the vital IRQs of ide or mouse from being taken by the PCI bridge
when the yenta_socket or i82365 module is loaded. (Unloading the module again
would not give back interrupt control - so a reboot was the final step)
Charles Briscoe-Smith wrote:
> > Personal question: did you find a solution?
>
> Yes, I did, and it has since been documented in the PCMCIA HOWTO,
> section 2.3, subsection "Card readers for desktop systems":
>
> For Chase CardPORT and Altec ISA card readers using the Cirrus PD6722
> ISA-to-PCMCIA bridge, the i82365 driver should be loaded with a
> ``has_ring=0'' parameter to prevent irq 15 conflicts.
>
> I had been trying the option "has_ring=1", which I didn't know was
> the default.
>
> [ CC'ed linux-kernel so that this gets into its archives. I am not on
> linux-kernel so, if replying, please CC me (and, I presume, Ulrich). ]
Thanks for your hint!
prev parent reply other threads:[~2002-03-03 21:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3C807EB5.24BAABC6@web.de>
2002-03-02 12:23 ` PCMCIA-related IDE problems on GA-7ZX motherboard Charles Briscoe-Smith
2002-03-03 21:16 ` Ulrich Hahn [this message]
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=3C82929B.48E5E77A@web.de \
--to=ulrich.hahn@web.de \
--cc=charles@briscoe-smith.org.uk \
--cc=linux-kernel@vger.kernel.org \
/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