public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David Hinds <dhinds@sonic.net>
To: Ian Morgan <imorgan@webcon.net>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	dhinds@zen.stanford.edu
Subject: Re: in-kernel pcmcia oopsing in SMP
Date: Sat, 1 Dec 2001 12:05:41 -0800	[thread overview]
Message-ID: <20011201120541.B28295@sonic.net> (raw)
In-Reply-To: <Pine.LNX.4.40.0112011406040.2329-100000@light.webcon.net>
In-Reply-To: <Pine.LNX.4.40.0112011406040.2329-100000@light.webcon.net>

On Sat, Dec 01, 2001 at 02:21:33PM -0500, Ian Morgan wrote:
> On a few SMP boxes here, with kernels from about 2.4.14 though 2.4.17-pre2,
> the system locks up hard during heavy wireless I/O.

The bug pretty much has to be in the orinoco driver; I'm not sure how
much stress testing it has had on SMP.

> (Some have said the kernel pcmcia stuff is still immature, but Hinds'
> pcmcia-cs package doesn't work at all for me. It's ds.o keeps oopsing when
> insmod'ed, so I can't even try it.)

I did fix one major SMP bug in the pcmcia-cs drivers just a couple
days ago; the beta at http://pcmcia-cs.sourceforge.net/ftp/NEW has the
fix.  I'm not sure if it is really the same bug you describe, though,
since no one else has reported the ds module causing an immediate
oops.

The standalone drivers are unlikely to help, though, because the
orinoco_cs driver in the standalone package is virtually identical to
the one in the current 2.4.* kernel.

Actually, though, you could try the (older) wvlan_cs driver in the
pcmcia-cs package.  You can do that with your current kernel drivers,
even.  Unpack the pcmcia-cs package, do "make config", then cd to the
wireless subdirectory and do a "make" there.  That should build a
wvlan_cs module that will mesh with your kernel PCMCIA subsystem.  It
will at least give you another data point.

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.

-- Dave

  reply	other threads:[~2001-12-01 20:06 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 [this message]
2001-12-01 20:27   ` Ian Morgan
2001-12-01 20:46     ` David Hinds
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=20011201120541.B28295@sonic.net \
    --to=dhinds@sonic.net \
    --cc=dhinds@zen.stanford.edu \
    --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