Bug 85529

Summary: Error -110 writing Tx descriptor to BAP
Product: [Retired] Red Hat Linux Reporter: Tim Keitt <tkeitt>
Component: kernelAssignee: Arjan van de Ven <arjanv>
Status: CLOSED DUPLICATE QA Contact: Brian Brock <bbrock>
Severity: medium Docs Contact:
Priority: medium    
Version: 8.0   
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2006-02-21 18:52:05 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Tim Keitt 2003-03-03 22:39:15 UTC
Description of problem:

I get multiple "Error -110 writing Tx descriptor to BAP" messages in my logs
after which my wireless connection dies. The orinoco_pci module is the culprit.
If I do "ifdown eth1; modprobe -r ornico_pci; modprobe orinoco_pci; ifup eth1" I
usually, but not always, get my connection back.

Here's the relevant bits of 'lspci -v':

01:0d.0 Network controller: Harris Semiconductor Prism 2.5 Wavelan chipset (rev
        Subsystem: Citicorp TTI: Unknown device 1169
        Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV+ VGASnoop- ParErr-
Stepping- SERR- FastB2B-
        Status: Cap+ 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR-
        Interrupt: pin A routed to IRQ 11
        Region 0: Memory at e0300000 (32-bit, prefetchable) [size=4K]
        Capabilities: [dc] Power Management version 2
                Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA
                Status: D0 PME-Enable- DSel=0 DScale=0 PME-

Version-Release number of selected component (if applicable):

/* orinoco_pci.c 0.01
 * Driver for Prism II devices that have a direct PCI interface
 * (i.e., not in a Pcmcia or PLX bridge)
 * Specifically here we're talking about the Linksys WMP11
 * Some of this code is borrowed from orinoco_plx.c
 *      Copyright (C) 2001 Daniel Barlow <dan@telent.net>
 * Some of this code is "inspired" by linux-wlan-ng-0.1.10, but nothing
 * has been copied from it. linux-wlan-ng-0.1.10 is originally :
 *      Copyright (C) 1999 AbsoluteValue Systems, Inc.  All Rights Reserved.
 * The rest is :
 *      Copyright (C) 2001 Jean Tourrilhes <jt@hpl.hp.com>

How reproducible: always

Steps to Reproduce:
1. buy Fujitsu (Lifebook S) laptop
2. install redhat 8
3. buy linksys wireless router
4. setup wireless network
5. prepare to be frustrated
Actual results: It doesn't work

Expected results: It works

Additional info:

I think this is a known bug, but I would like to make sure its in the queue to
be fixed.

Comment 1 Tim Keitt 2003-03-17 03:22:21 UTC

*** This bug has been marked as a duplicate of 75237 ***

Comment 2 Red Hat Bugzilla 2006-02-21 18:52:05 UTC
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.