From: David Gibson <hermes@gibson.dropbear.id.au>
To: Peter Chubb <peter@chubb.wattle.id.au>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Orinoco Wireless driver bugs in 2.5.17
Date: Wed, 22 May 2002 11:53:05 +1000 [thread overview]
Message-ID: <20020522015305.GJ4745@zax> (raw)
In-Reply-To: <15594.57612.421887.407469@wombat.chubb.wattle.id.au>
On Wed, May 22, 2002 at 10:06:36AM +1000, Peter Chubb wrote:
>
> Hi,
> I see two undesireable behaviours with the Orinoco drivers in
> 2.5.17.
>
> 1. With a compaq WL110 in a WL210 PCI<->PCMCIA bridge, I see many
>
> NETDEV WATCHDOG: eth1: transmit timed out
> Tx timeout! Resetting card. ALLOCFID=00c0, TXCOMPLFID=00bf, EVSTAT=808a
>
> messages, and see no activity on any other stations.
I've had one similar report, on a vaguely similar PCI<->PCMCIA
bridge. It looks very much as if we're not receiving any interrupts.
That would appear to be a low-level problem with routing of interrupts
through the bridge. It may well be a PCMCIA subsystem problem rather
than a driver problem.
> 2. With a Netgear MA401, every now and then the card goes into bozo
> mode, when iwconfig reports:
>
> eth0 IEEE 802.11-DS Nickname:"piggle"
> Mode:Managed Frequency:42.9497GHz Tx-Power=15 dBm
> RTS thr:off
> Link Quality:241 Signal level:136 Noise level:107
> Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
> Tx excessive retries:0 Invalid misc:0 Missed beacon:0
>
>
> Note the Frequency there. A `cardctl reset' fixes the problem.
Other than the bogus frequecy reported, does the card still work?
--
David Gibson | For every complex problem there is a
david@gibson.dropbear.id.au | solution which is simple, neat and
| wrong. -- H.L. Mencken
http://www.ozlabs.org/people/dgibson
next prev parent reply other threads:[~2002-05-22 2:03 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-22 0:06 Orinoco Wireless driver bugs in 2.5.17 Peter Chubb
2002-05-22 1:53 ` David Gibson [this message]
2002-05-22 13:16 ` Alan Cox
-- strict thread matches above, loose matches on Subject: below --
2002-05-22 17:38 Jean Tourrilhes
2002-05-22 18:24 ` Alan Cox
2002-05-22 18:17 ` Jean Tourrilhes
2002-05-23 1:27 ` David Gibson
2002-05-23 1:25 ` David Gibson
2002-05-29 18:40 ` Alan Cox
2002-05-29 17:42 ` Jean Tourrilhes
2002-06-02 23:38 ` David Gibson
2002-06-03 1:08 ` Alan Cox
2002-05-23 3:21 Erik McKee
[not found] <385229951@toto.iv>
2002-05-27 9:27 ` Peter Chubb
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=20020522015305.GJ4745@zax \
--to=hermes@gibson.dropbear.id.au \
--cc=linux-kernel@vger.kernel.org \
--cc=peter@chubb.wattle.id.au \
/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