public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Narayan Desai <desai@mcs.anl.gov>
To: linux-kernel@vger.kernel.org
Subject: Re: weird pcmcia problem
Date: Tue, 19 Aug 2003 09:19:38 -0500	[thread overview]
Message-ID: <87wud9ybk5.fsf@mcs.anl.gov> (raw)
In-Reply-To: <20030819124547.B18205@flint.arm.linux.org.uk> (Russell King's message of "Tue, 19 Aug 2003 12:45:47 +0100")

>>>>> "Russell" == Russell King <rmk@arm.linux.org.uk> writes:

  Russell> On Mon, Aug 18, 2003 at 07:34:59PM -0500, Narayan Desai
  Russell> wrote:
  >> Running 2.6.0-test3 (both with and without your recent yenta
  >> socket patches) pcmcia cards present during boot don't show up
  >> until they are removed and reinserted. Once reinserted, they work
  >> fine. This only seems to occur if yenta_socket is build into the
  >> kernel; if support is modular, cards appear to be recognized
  >> properly at boot time. I am running on a thinkpad t21.  Let me
  >> know if I can help with this problem in any way...  thanks

  Russell> As a general thing, when people report this problem (or any
  Russell> other problem), can they please include at least the
  Russell> following details please:

  Russell> - make/model of machine
  Russell> - type of cardbus bridge (from lspci)
  Russell> - type of card (pcmcia or cardbus)
  Russell> - make/model of card
  Russell> - full kernel dmesg (including yenta, card services
  Russell>   messages)
  Russell> - cardmgr messages from system log

This is an IBM thinkpad t21. the cardbus bridge is:
00:02.0 CardBus bridge: Texas Instruments PCI1450 (rev 03)
00:02.1 CardBus bridge: Texas Instruments PCI1450 (rev 03)

The problem is occurring with an orinoco gold pcmcia card.

the unable to map cs memory errors were the only odd thing in the
kernel messages, and it looks like your diagnosis was right on the
money. i these cardmgr messages:
Aug 18 20:38:06 topaz cardmgr[374]: watching 2 sockets
Aug 18 20:38:06 topaz cardmgr[375]: starting, version is 3.2.2
Aug 18 20:38:06 topaz cardmgr[375]: socket 0: Anonymous Memory
Aug 18 20:38:06 topaz cardmgr[375]: executing: 'modprobe memory_cs'
Aug 18 20:38:06 topaz cardmgr[375]: + FATAL: Module memory_cs not found.
Aug 18 20:38:06 topaz cardmgr[375]: modprobe exited with status 1
Aug 18 20:38:06 topaz cardmgr[375]: module /lib/modules/2.6.0-test3-p2/pcmcia/memory_cs.o not available
Aug 18 20:38:06 topaz cardmgr[375]: bind 'memory_cs' to socket 0 failed: Invalid argument

let me know if there is more info that would be useful.
 -nld


  parent reply	other threads:[~2003-08-19 15:56 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-19  0:34 weird pcmcia problem Narayan Desai
2003-08-19  1:11 ` Jamie Lokier
2003-08-19  4:47 ` Valdis.Kletnieks
     [not found]   ` <200308191816.h7JIGNBC002405@turing-police.cc.vt.edu>
2003-08-19 18:19     ` Russell King
2003-08-19 19:22       ` Valdis.Kletnieks
2003-08-19  8:34 ` Russell King
2003-08-19 19:12   ` Sven Dowideit
2003-08-19 11:45 ` Russell King
2003-08-19 13:46   ` Henrik Persson
2003-08-19 14:19   ` Narayan Desai [this message]
2003-08-19 23:35   ` Sven Dowideit
2003-08-19 23:46   ` Sven Dowideit

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=87wud9ybk5.fsf@mcs.anl.gov \
    --to=desai@mcs.anl.gov \
    --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