From: Trevor-Hemsley@dial.pipex.com (Trevor Hemsley)
To: linux-kernel@vger.kernel.org
Subject: Re: pcmcia lockup inserting or removing cards in 2.4.5-ac{13,22}
Date: Thu, 05 Jul 2001 00:41:15 [thread overview]
Message-ID: <20010704235854Z266582-17721+8482@vger.kernel.org> (raw)
On Tue, 3 Jul 2001 00:30:10, "Trevor Hemsley"
<Trevor-Hemsley@dial.pipex.com> wrote:
> Somewhere between 2.4.2 and 2.4.5-ac13, PCMCIA card insertion and
> removal appears to have broken on my Toshiba Libretto. On 2.4.2 all was
> fine. On both 2.4.5-ac13 and ac22 it's broken. The whole machine freezes
> solid, no SAK-s, SAK-u, SAK-b, no Ctrl-Alt-Fn to switch VC's. No messages
> are issued. Problem occurs when inserting/removing any of YE-Data PCMCIA
> floppy, TDK Smartmedia adapter (ide_cs), or 3c589 ethernet card.
[large snip]
OK, I've done quite a lot more work on this. It isn't 2.4.5, I'd
compiled USB support in when I went to 2.4.5 and it's that that causes
the problems. I backed out all changes made between 2.4.2 and 2.4.5 in
drivers/pcmcia and that made no difference to the lockup so then I
went back to the .config file from 2.4.2 and that worked.
My best guess is that the USB support is using IRQ 11 and that the
PCMCIA card sockets are wired to use that as well. I have a bypass for
now - if I set the Toshiba BIOS up to use the slots in PCIC mode then
it assigns them IRQ 15. In cardbus mode they get assigned IRQ 11 in
Win9x but dmesg reports
Linux Kernel Card Services 3.1.22
options: [pci] [cardbus] [pm]
PCI: No IRQ known for interrupt pin A of device 00:06.0. Please try
using pci=biosirq.
PCI: No IRQ known for interrupt pin B of device 00:06.1. Please try
using pci=biosirq.
and
Yenta IRQ list 0eb8, PCI irq0
Socket status: 30000007
Yenta IRQ list 0eb8, PCI irq0
Socket status: 30000007
Using pci=biosirq makes no difference when in cardbus mode.
Ah, got it, flipping the PCMCIA setup in the BIOS from "Auto-detect"
to "Cardbus/16 bit" fixes it. lspci -vv now lists the cardbus ports as
having IRQ 11 assigned (instead of 0 before). Everything (famous last
words) appears to be working.
--
Trevor Hemsley, Brighton, UK.
Trevor-Hemsley@dial.pipex.com
next reply other threads:[~2001-07-04 23:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-05 0:41 Trevor Hemsley [this message]
2001-07-05 0:19 ` Erik Mouw
-- strict thread matches above, loose matches on Subject: below --
2001-07-05 21:42 Trevor Hemsley
2001-07-06 4:53 ` Jeff Garzik
2001-07-03 1:28 Trevor Hemsley
2001-07-03 1:14 mr sam jooky
2001-07-03 3:01 ` Byeong-ryeol Kim
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=20010704235854Z266582-17721+8482@vger.kernel.org \
--to=trevor-hemsley@dial.pipex.com \
--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
all inboxes | Powered by JetHome®