From: Russell King <rmk@arm.linux.org.uk>
To: Felipe Alfaro Solana <felipe_alfaro@linuxmail.org>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: 2.5.66-mm2-1 freezes solid after init PCMCIA
Date: Tue, 1 Apr 2003 20:46:45 +0100 [thread overview]
Message-ID: <20030401204645.B7936@flint.arm.linux.org.uk> (raw)
In-Reply-To: <1049202135.612.4.camel@teapot>; from felipe_alfaro@linuxmail.org on Tue, Apr 01, 2003 at 03:02:16PM +0200
On Tue, Apr 01, 2003 at 03:02:16PM +0200, Felipe Alfaro Solana wrote:
> OK, here we go...
I was thinking that it could be due to the pci changes - that's one of
the areas I've been working in recently which could have caused this.
However, I believe it is to do with the recent PCMCIA changes to use
the device model, and deadlock within the device model itself.
What basically seems to be happening is this:
- the ds module is inserted
- ds registers a driver model interface for pcmcia socket drivers,
which takes the global devclass_sem.
- ds causes the pcmcia core to evaluate the status of the sockets, and
perform "card insertion" processing if cards are present.
- this processing detects a cardbus card, and calls the cardbus code to
scan pci devices, and add them to the device tree.
- each device gets passed to the device model's class layer, which tries
to take devclass_sem. But wait! We've locked it while initialising
the ds module -> deadlock.
I'm currently working on the card insertion/removal code which hopefully
should fix this. However, it's not going to be immediately available,
so please be patient.
--
Russell King (rmk@arm.linux.org.uk) The developer of ARM Linux
http://www.arm.linux.org.uk/personal/aboutme.html
next prev parent reply other threads:[~2003-04-01 19:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-01 11:20 2.5.66-mm2-1 freezes solid after init PCMCIA Felipe Alfaro Solana
2003-04-01 11:53 ` Russell King
2003-04-01 13:02 ` Felipe Alfaro Solana
2003-04-01 19:46 ` Russell King [this message]
2003-04-01 21:01 ` Felipe Alfaro Solana
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=20030401204645.B7936@flint.arm.linux.org.uk \
--to=rmk@arm.linux.org.uk \
--cc=felipe_alfaro@linuxmail.org \
--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