From: Jean Tourrilhes <jt@bougret.hpl.hp.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Linux kernel mailing list <linux-kernel@vger.kernel.org>,
David Gibson <hermes@gibson.dropbear.id.au>
Subject: Re: Orinoco Wireless driver bugs in 2.5.17
Date: Wed, 22 May 2002 11:17:51 -0700 [thread overview]
Message-ID: <20020522111751.A10992@bougret.hpl.hp.com> (raw)
In-Reply-To: <20020522103834.B10921@bougret.hpl.hp.com> <E17Aams-0002Ue-00@the-village.bc.nu>
On Wed, May 22, 2002 at 07:24:37PM +0100, Alan Cox wrote:
> > Alan,
> > Could you be more precise and point out which kernel start
> > failing ?
>
> Certainly in 2.4.18 (and I've seen a pile of other similar reports).
2.4.18 did upgrade the driver from 0.06f to 0.09b. The bug
with 0.09b is a race condition in Tx code. This was fixed in version
0.11.
Have you tried 2.4.19-pre8-acX (well, I mean the Orinoco
driver in 2.4.19-pre8 ;-). It contains the new version of the driver
(v11) that fixes the race condition (but introduce the potential COR
problem).
If 2.4.19-pre8-acX fails, that would be for an entirely
different reason (even if the failure might look similar).
> Any specific info/debug/traces that would help ?
I'll defer that to David.
> Alan
Good luck...
Jean
next prev parent reply other threads:[~2002-05-22 18:17 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-22 17:38 Orinoco Wireless driver bugs in 2.5.17 Jean Tourrilhes
2002-05-22 18:24 ` Alan Cox
2002-05-22 18:17 ` Jean Tourrilhes [this message]
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
[not found] <385229951@toto.iv>
2002-05-27 9:27 ` Peter Chubb
-- strict thread matches above, loose matches on Subject: below --
2002-05-23 3:21 Erik McKee
2002-05-22 0:06 Peter Chubb
2002-05-22 1:53 ` David Gibson
2002-05-22 13:16 ` Alan Cox
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=20020522111751.A10992@bougret.hpl.hp.com \
--to=jt@bougret.hpl.hp.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=hermes@gibson.dropbear.id.au \
--cc=jt@hpl.hp.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.