#28 Traffic lockup on Tx error 0x20 (non-related to distance!)

closed-out-of-date
nobody
None
5
2005-02-25
2003-11-27
No

The card works allright, but suddenly it breaks down -
there is no more ping or traffic possible. After a
reload of the module, the card works allright for the
next 2 - 60 minutes. I could not recognize a pattern or
why it breaks down. The only error message I can see in
the logs is:

Tx error occurred (error 0x20)!! (maybe distance too high?)
And this message is repeated several times.

My guess is, that the driver can't recover after this
error to normal operation.

Thanks for any ideas.

Discussion

  • Anonymous - 2003-11-29

    last 400 lines of my syslog before breakdown

     
    Attachments
  • Anonymous - 2003-11-29

    Logged In: YES
    user_id=861416

    I read in the other thread, which could handle the same
    topic, that it is a good idea to debug with 0x109b - thus i did.
    And I am proud to present you the last 400 lines of output.
    If you need more debugging, I am happy to help.

    Now, there seems to be something interesting in the log -
    even before the tx error I mentioned. Any help (and fix :-))
    is appreciated.

    CU Steve

     
  • Andreas Mohr

    Andreas Mohr - 2003-12-02

    Logged In: YES
    user_id=132674

    Hmm, no, a 0x20 Tx error is not very critical. In almost all
    cases it simply means that you're out of reach.
    Communication SHOULD work again when you reenter the covered
    area.
    ...unless it really stops to attempt to send ANY packets
    whatsoever once you get some 0x20 errors, which would be
    very strange.
    Please provide longer logs about such a situation, right now
    I'm afraid I don't really know what's going on.
    You also tried iwconfig wlan0 txpower XXX, right?

     
  • Anonymous - 2003-12-02

    Logged In: YES
    user_id=861416

    Please tell me your desired type of debug and I will try to
    catch the log entries before collapse!! You want to have
    more lines or logs with another debug code?

    What about the messages before the tx error in the attached
    look, doesn't look normal (afaics). I mean that "Mode 2" and
    "cleaning up" stuff...
    The communication between my computer and the access point
    is about 5 meters through 2 walls - the windows system
    doesn't seem to have the same problem in this distance. I
    tried txpower 0dBm, 7dBm, 10 dBm and 20dBm and there's no
    difference between them.
    After the error occured, there's no way to get the
    connection back, even if I'm sitting in front of the access
    point.
    The attached log really shows the very last messages - after
    that, only a reload of the module could bring the PINGs and
    the log messages back to life.

     
  • Anonymous - 2003-12-08

    Logged In: YES
    user_id=861416

    One hot kernel minute.. attached in syslog2.tgz
    the last minute of the working driver. For me it's
    completely cryptic..
    I think 13:34:13 was the last ping sent.
    Hope, it is not a stupid configuration of MY system :-)

     
  • Anonymous - 2003-12-08

    last minute of messages

     
    Attachments
  • Stefan Heim

    Stefan Heim - 2003-12-08

    Logged In: YES
    user_id=901053

    > I think 13:34:13 was the last ping sent.

    No, that's the time the last packet (ICMP echo reply) was /received/.
    From that point on, you seem to be still successfully transmitting ICMP
    echo requests, but don't get replys anymore - at least your acx100
    does not signal the reception of a single packet beyond this point.

    What happened to the logfile around line 49? Looks eihter severely
    corrupted or hand edited.

    You seem to have your acx100-based card share an interrupt with
    some other hardware. What kind of hardware is this? What kind of
    interrupt intensive work is it doing? How does your /proc/interrupts look
    like? Can you please test with the other hardware part using the same
    IRQ temporarily disabled?

    Furthermore, what kind of radio part do you have
    (/proc/driver/acx100)?

    And, last but not least, is this on a SMP box?

     
  • Andreas Mohr

    Andreas Mohr - 2004-02-04
    • summary: No recover after error 0x20 --> Traffic lockup on Tx error 0x20 (non-related to distance!)
     
  • Andreas Mohr

    Andreas Mohr - 2004-02-04

    Logged In: YES
    user_id=132674

    Fortunately I'm able to experience the same issues (Tx error
    0x20 after a random amount of time, then NOTHING possible
    any more).
    However, it happens VERY irregularly, it seems (sometimes
    several days until it occurs!).
    Hopefully I'll be able to nail it down soon, it's too damn
    annoying...
    Any other information on this problem? Please post it!

     
  • Nobody/Anonymous

    Logged In: NO

    I have the same bug...
    i have a fedora core 3 kernel 2.6.9-1.667, wireless USR5416 pci.
    All my net works well, and after few minutes... my usr5416
    ping nothing...

    WARNING: Kernel Errors Present
    several excessive Tx retry errors occurred, attem...: 4
    Time(s)
    tx: error 0x20!...: 27 Time(s)
    tx: error 0x20! (excessive...: 9 Time(s)
    vesafb: probe of vesafb0 failed with error -6...: 5 Time(s)

    i had test sens to 3/3, power all, and retry 50...
    2 PCs are to 2 meters...

    please help me.

     
  • Nobody/Anonymous

    Logged In: NO

    I have the same problem,
    I have a USR5416 pci, on a Fedora core 3 kernel 2.6.9-1.667.
    i had test retry 50, sens 3/3, power all...
    nothing works more 60mn...
    please help.

     
  • Christian Kirbach

    • status: open --> closed-out-of-date
     
  • Christian Kirbach

    Logged In: YES
    user_id=889123

    Closing due to no activity within the last 6 months.

    If you want to reopen the bug please make sure you have checked
    that the problem persists even with the latest driver.
    You can get the driver from http://lisas.de/~andi/acx100/

     

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:





No, thanks