From: David Hinds <dhinds@sonic.net>
To: Ian Morgan <imorgan@webcon.net>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
hermes@gibson.dropbear.id.au
Subject: Re: in-kernel pcmcia oopsing in SMP
Date: Sat, 1 Dec 2001 12:46:30 -0800 [thread overview]
Message-ID: <20011201124630.A30249@sonic.net> (raw)
In-Reply-To: <20011201120541.B28295@sonic.net> <Pine.LNX.4.40.0112011513041.2329-100000@light.webcon.net>
In-Reply-To: <Pine.LNX.4.40.0112011513041.2329-100000@light.webcon.net>
On Sat, Dec 01, 2001 at 03:27:24PM -0500, Ian Morgan wrote:
>
> > I don't know how to interpret your oops report; you should probably
> > also forward the bug to David Gibson, hermes@gibson.dropbear.id.au,
> > since he is the orinoco maintainer.
>
> Well, Gibson's the one who suggested the broblem was with the pcmcia system,
> and not the orinoco driver! Hmm.... can you say runaround?
It pretty much can't be a PCMCIA subsystem bug. The basic PCMCIA code
handles card identification and configuration of the socket; however,
for almost all cards, the PCMCIA subsystem is completely out of the
loop during normal card operation. No PCMCIA code outside of the
orinoco driver itself will ever be executed.
Your oops, in tasklet code, sounds to me like a locking bug in the
driver code for managing the transmit stack vs. interrupt handling.
Have there been reports of the driver working well on SMP boxes?
-- Dave
next prev parent reply other threads:[~2001-12-01 20:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-01 19:21 in-kernel pcmcia oopsing in SMP Ian Morgan
2001-12-01 20:05 ` David Hinds
2001-12-01 20:27 ` Ian Morgan
2001-12-01 20:46 ` David Hinds [this message]
2001-12-17 3:24 ` David Gibson
2001-12-17 4:59 ` David Hinds
2001-12-03 3:25 ` BUG() in spinlock.h loading ds.o Ian Morgan
2001-12-03 6:56 ` David Hinds
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=20011201124630.A30249@sonic.net \
--to=dhinds@sonic.net \
--cc=hermes@gibson.dropbear.id.au \
--cc=imorgan@webcon.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