Date: Tue, 10 Apr 2001 12:09:33 -0400 From: "Andria Thomas" <andria@tovaris.com> To: hackers@freebsd.org Subject: problem with Aironet driver Message-ID: <3AD3303D.7E01528D@tovaris.com>
next in thread | raw e-mail | index | archive | help
Hi everyone. I'd like to report a problem we've been having with the Aironet driver on two of our machines. One machine is running FreeBSD 4.1.1-RELEASE, and the other is a very recent upgrade to 4.3-RC1. They both have Aironet PCI4800 cards and are connected directly to antennas (one on our roof, one on the roof of our ISP). Recently, we've seen messages like the following spewed to the consoles of each machine: Mar 26 14:25:57 gw /kernel: an0: id mismatch: expected 178, got 224 Mar 26 14:25:57 gw /kernel: an0: id mismatch: expected 17e, got 178 Mar 26 14:25:58 gw /kernel: an0: id mismatch: expected 9e, got 17e Mar 26 14:25:58 gw /kernel: an0: id mismatch: expected 224, got 9e Mar 26 14:25:59 gw /kernel: an0: id mismatch: expected 178, got 224 Mar 26 14:25:59 gw /kernel: an0: id mismatch: expected 17e, got 178 Mar 26 14:25:59 gw /kernel: an0: id mismatch: expected 9e, got 17e Mar 26 14:25:59 gw /kernel: an0: id mismatch: expected 224, got 9e Mar 26 14:26:00 gw /kernel: an0: id mismatch: expected 178, got 224 Mar 26 14:26:01 gw /kernel: an0: id mismatch: expected 17e, got 178 Mar 26 14:26:02 gw /kernel: an0: id mismatch: expected 9e, got 17e Mar 26 14:26:02 gw /kernel: an0: id mismatch: expected 224, got 9e Mar 26 14:26:03 gw /kernel: an0: id mismatch: expected 178, got 224 Mar 26 14:26:03 gw /kernel: an0: id mismatch: expected 17e, got 178 Mar 26 14:26:03 gw /kernel: an0: id mismatch: expected 9e, got 17e Mar 26 14:26:04 gw /kernel: an0: id mismatch: expected 224, got 9e Mar 26 14:26:04 gw /kernel: an0: id mismatch: expected 178, got 224 Mar 26 14:26:04 gw /kernel: an0: id mismatch: expected 17e, got 178 Mar 26 14:26:05 gw /kernel: an0: id mismatch: expected 9e, got 17e Mar 26 14:26:05 gw /kernel: an0: id mismatch: expected 224, got 9e When these messages begin, our network connection grinds to a near-halt (ping times of 1000-2000ms). The only way we've found to stop the messages is to disconnect the Aironet connection, and bring the network interface down and back up again. When it comes back up, everything is mysteriously back to normal. I've tried looking through the source code, but confess to not understanding what it is that prompts these messages to begin. Any help would be greatly appreciated. I've tried poring through mailing list archives, but no one else seems to have reported a similar problem. Thanks for any help you can offer! Andria Thomas To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3AD3303D.7E01528D>