Project

General

Profile

Actions

Bug #1181

open

ACX111 panic

Added by elekktretterr almost 16 years ago. Updated over 3 years ago.

Status:
In Progress
Priority:
Normal
Assignee:
-
Category:
Driver
Target version:
Start date:
Due date:
% Done:

0%

Estimated time:

Description

Sorry about the picture size!

I tried to switch from my Atheros(because of the dropouts ive been having)
card back to my ACX111 card. With AMRR enabled, the card is unable to stay
connected to my network(connects and disconnects and keeps retrying). But
when I removed AMRR from the kernel, I get this panic(picture attached).

Verbose dmesg coming soon.

Petr


Files

acx_onoe.JPG (316 KB) acx_onoe.JPG elekktretterr, 12/16/2008 11:39 AM
dump80211 (35.7 KB) dump80211 elekktretterr, 12/16/2008 11:43 AM
dumpradio (85.5 KB) dumpradio elekktretterr, 12/16/2008 11:43 AM
dmesg.txt (35.9 KB) dmesg.txt elekktretterr, 12/16/2008 11:43 AM
Actions #1

Updated by elekktretterr almost 16 years ago

verbose dmesg, and dumps attached.

Petr

Actions #2

Updated by swildner almost 16 years ago

Could you please put up such big pics and dumps on some external site
next time? It's really a pain in the ass.

Not to mention that embedded pics look like crap in nntp/mail archive
and are pretty much unusable because of that.

Sascha

Actions #4

Updated by sepherosa almost 16 years ago

Mmm, I think I have put MODULE_DEPEND(acx, wlan_ratectl_amrr ...) in
if_acx.c ... You should not remove AMRR from kernel config if you
have acx in the kernel config.
As about using different TX rate control algorithm, you could use:
ifconfig acx0 ratectl onoe

Best Regards,
sephe

Actions #5

Updated by sepherosa almost 16 years ago

On Tue, Dec 16, 2008 at 7:40 PM, Petr Janda
<> wrote:

verbose dmesg, and dumps attached.

Looks like acx0 never hears assoc-resp form AP. Try putting following
line in your /boot/loader.conf:
hw.acx.enable_pbcc="0"

Best Regards,
sephe

Actions #6

Updated by elekktretterr almost 16 years ago

Hi,
This makes no difference.

Petr

Actions #7

Updated by sepherosa over 15 years ago

grab

Actions #8

Updated by tuxillo over 9 years ago

  • Description updated (diff)
  • Category set to Driver
  • Status changed from New to In Progress
  • Target version set to 4.2

Hi Sephe,

Do you think this is still relevant?

Cheers,
Antonio Huete

Actions #9

Updated by swildner over 9 years ago

Before this gets relevant, someone needs to port the acx(4) to the current 802.11 framework and hook it back into the build.

Actions #10

Updated by tuxillo over 3 years ago

  • Target version changed from 4.2 to 6.0
Actions

Also available in: Atom PDF