public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Russell King <rmk@arm.linux.org.uk>
To: Sean Estabrooks <seanlkml@rogers.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.5.67 pcmcia - insmod ds.ko hangs
Date: Mon, 14 Apr 2003 12:36:45 +0100	[thread overview]
Message-ID: <20030414123645.B13664@flint.arm.linux.org.uk> (raw)
In-Reply-To: <1050319324.31740.13.camel@linux1.classroom.com>; from seanlkml@rogers.com on Mon, Apr 14, 2003 at 07:22:04AM -0400

On Mon, Apr 14, 2003 at 07:22:04AM -0400, Sean Estabrooks wrote:
> # insmod pcmcia_core.ko
> # insmod yenta_socket.ko
>     PCI: Found IRQ 11 for device 00:0b.0
>     PCI: Sharing IRQ 11 with 01:00.0
>     Yenta IRQ list 04b0, PCI irq11
>     Socket status: 30000020
>     PCI: Found IRQ 11 for device 00:0b.1
>     PCI: Sharing IRQ 11 with 00:0c.0
>     Yenta IRQ list 04b0, PCI irq11
>     Socket status: 30000007
> # insmod ds.ko  
>     PCI: Enabling device 02:00.0 (0000 -> 0003)
>     [hang]
> 
>   And hangs here permanently, and i should mention it hangs 
> the same way when compiled into the kernel.  Changing to
> another virtual console and bringing up the network works
> without a hitch, but the insmod above never returns.

Known problem - don't insert ds.ko with any cards in the sockets.
It's caused by a deadlock in the device model handling, caused by
the expectations of PCMCIA.

-- 
Russell King (rmk@arm.linux.org.uk)                The developer of ARM Linux
             http://www.arm.linux.org.uk/personal/aboutme.html


      reply	other threads:[~2003-04-14 11:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-14 11:22 2.5.67 pcmcia - insmod ds.ko hangs Sean Estabrooks
2003-04-14 11:36 ` Russell King [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=20030414123645.B13664@flint.arm.linux.org.uk \
    --to=rmk@arm.linux.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=seanlkml@rogers.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