Re: TXEXC [RetryErr] in syslog

From: Rob French (
Date: 2002-07-26 06:50:45 UTC

Ok, I've built the new driver from source, I'll let you know how it goes as far as the lockup.

Who's "fault" is it likely to be as far as the excessive amount of errors I'm getting? They're showing up on the server's logs, but could it be the client's fault? (Not acknowledging the server's transmissions???) I admit I know next to nothing about wireless networks.

On Fri, 2002-07-26 at 02:32, Jouni Malinen wrote:
> On Fri, Jul 26, 2002 at 12:27:39AM -0400, Rob French wrote:
> > I tried
> >
> >
> > but I'm still getting the messages in /var/log/syslog, /var/log/debug,
> > and /var/log/kern.log. Not only that, but in about 30 minutes of heavy
> > traffic, I got about 60MB of log files (20MB in each of the above three
> > files), so obviously there's a more important issue somewhere here.
> You have probably too old version of the driver for PRISM2_NO_DEBUG..
> Either use newer version or edit the lines manually away from the driver
> code.
> However, that kind of amount of TXEXC errors does sound huge..
> On Fri, Jul 26, 2002 at 12:29:08AM -0400, Rob French wrote:
> > I should also add that I'm using the 05-02 driver. The 05-19 driver was
> > locking up my system periodically. The 05-02 driver just gives me 60MB
> > log files :-).
> I wrote "Latest CVS version".. Not even 2002-05-19 release is new
> enough.. Anyway, if the latest driver is locking up, I would really like
> to know whether the latest CVS version has fixed this. You can find the
> CVS snapshot from
> --
> Jouni Malinen PGP id EFC895FA

Soli Deo Gloria
-Rob French

This archive was generated by hypermail 2.1.4.