[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#291684: orinoco.c: Error -110 writing Tx descriptor to BAP



Package: kernel-source-2.6.10
Version: 2.6.10-4
Severity: important


Hi,

I'm seeing the "Error -110 writing Tx descriptor to BAP" bug as
described in FAQ at http://ozlabs.org/people/dgibson/dldwd/ about once
every other day. orinoco.c prints to the syslog at such a rate, that the
system becomes completely unresponsive and I have to reboot. The lspci
output for the chip is:

0000:02:0b.0 Network controller: Intersil Corporation Prism 2.5 Wavelan
chipset (rev 01)
        Subsystem: AMBIT Microsystem Corp.: Unknown device 0201
        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 9
	Region 0: Memory at e0500000 (32-bit, prefetchable) [size=4K]
        Capabilities: [dc] Power Management version 2
                Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA
PME(D0+,D1+,D2+,D3hot+,D3cold-)
                Status:	D0 PME-Enable- DSel=0 DScale=0 PME-
										
Updating to version 0.15rc2 of the driver (which the author considers
stable but doesn't have time to submit to mainline) fixes the problem.
Including the new driver in testing is probably too much hassle, but
maybe it's worthwhile for stable.

Regards,
   Georg

-- System Information:
Debian Release: 3.1
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.10-gw1
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)

Versions of packages kernel-source-2.6.10 depends on:
ii  binutils                      2.15-5     The GNU assembler, linker and bina
ii  bzip2                         1.0.2-1    A high-quality block-sorting file 
ii  coreutils [fileutils]         5.2.1-2    The GNU core utilities
ii  fileutils                     5.2.1-2    The GNU file management utilities 

-- no debconf information



Reply to: