From: "Jeremy T. Bouse" <Jeremy.Bouse@UnderGrid.net>
To: linux-kernel@vger.kernel.org
Subject: Re: [PCMCIA] Xircom nic hang on boot since cs.c race condition patch
Date: Thu, 18 Sep 2003 23:02:15 -0700 [thread overview]
Message-ID: <20030919060215.GB5952@UnderGrid.net> (raw)
In-Reply-To: <200309190247.h8J2lmhx005690@turing-police.cc.vt.edu>
[-- Attachment #1: Type: text/plain, Size: 2526 bytes --]
Not sure if it's related but I've had problems with PCMCIA support in
the test kernels myself... The Cisco Aironet 350 has problems and I've
been able to make any use of the Orinoco Gold wireless card...
Fortunately the ethernet card is built in on PCI bus and doesn't have
any problem but I had being corded down...
Regards,
Jeremy
On Thu, Sep 18, 2003 at 10:47:48PM -0400, Valdis.Kletnieks@vt.edu wrote:
> On Wed, 17 Sep 2003 22:33:36 BST, Russell King said:
> > On Wed, Sep 17, 2003 at 02:44:06PM -0400, Sean Estabrooks wrote:
> > > [PCMCIA] Fix race condition causing cards to be incorrectly recognised
> > >
> > > This patch that went into test5 causes my Toshiba laptop with Xircom
> > > pcmcia nic to freeze on boot at "Socket status: 30000020".
> >
> > Unfortunately this patch does two things:
> >
> > (a) it fixes the problem with PCMCIA cards not being recognised on boot.
> > (b) it introduces a deadlock between the PCMCIA layer and the driver
> > model.
>
> OK... so what's different about Sean's Toshiba and my Dell (or alternatively,
> the fact we both have Xircom cards) that the *old* code worked just fine?
>
> Is it the fact that it's a multi-function card?
>
> lspci -v says:
> 03:00.0 Ethernet controller: Xircom Cardbus Ethernet 10/100 (rev 03)
> Subsystem: Xircom Cardbus Ethernet 10/100
> Flags: bus master, medium devsel, latency 64, IRQ 9
> I/O ports at 1000 [size=128]
> Memory at 10800000 (32-bit, non-prefetchable) [size=2K]
> Memory at 10800800 (32-bit, non-prefetchable) [size=2K]
> Expansion ROM at 10400000 [disabled] [size=16K]
> Capabilities: [dc] Power Management version 1
>
> 03:00.1 Serial controller: Xircom Cardbus Ethernet + 56k Modem (rev 03) (prog-if 02 [16550])
> Subsystem: Xircom CBEM56G-100 Ethernet + 56k Modem
> Flags: medium devsel, IRQ 9
> I/O ports at 1080 [size=8]
> Memory at 10801000 (32-bit, non-prefetchable) [size=2K]
> Memory at 10801800 (32-bit, non-prefetchable) [size=2K]
> Expansion ROM at 10404000 [disabled] [size=16K]
> Capabilities: [dc] Power Management version 1
>
> I could see problems if the serial controller is being added while the ethernet
> controller is still getting its act together while holding locks, since it's one
> physical card.
>
> I admit not being hot on the programming model for cardbus, but I'm
> quite willing to test patches.. ;)
>
>
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2003-09-19 6:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-17 18:44 [PCMCIA] Xircom nic hang on boot since cs.c race condition patch Sean Estabrooks
2003-09-17 21:33 ` Russell King
2003-09-19 2:47 ` Valdis.Kletnieks
2003-09-19 6:02 ` Jeremy T. Bouse [this message]
2003-09-19 10:14 ` Klaus Kurzmann
2003-09-20 21:22 ` Russell King
2003-09-21 16:49 ` Sean Estabrooks
2003-09-21 17:31 ` Valdis.Kletnieks
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=20030919060215.GB5952@UnderGrid.net \
--to=jeremy.bouse@undergrid.net \
--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