[Acx100-devel] [ acx100-Bugs-850351 ] No recover after error 0x20

[SourceForge.net <no...@so...>]

Bugs item #850351, was opened at 2003-11-27 18:13
Message generated for change (Comment added) made by beefsteve
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=543745&aid=850351&group_id=75380

Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Steffen Grunwald (beefsteve)
Assigned to: Nobody/Anonymous (nobody)
Summary: No recover after error 0x20

Initial Comment:
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.


----------------------------------------------------------------------

>Comment By: Steffen Grunwald (beefsteve)
Date: 2003-12-08 15:02

Message:
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 :-)

----------------------------------------------------------------------

Comment By: Steffen Grunwald (beefsteve)
Date: 2003-12-02 15:48

Message:
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.

----------------------------------------------------------------------

Comment By: Andreas Mohr (andim2)
Date: 2003-12-02 12:01

Message:
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?

----------------------------------------------------------------------

Comment By: Steffen Grunwald (beefsteve)
Date: 2003-11-29 21:10

Message:
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

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=543745&aid=850351&group_id=75380