Re: New hardware, old problem: stuck beacon when here is WiFi traffic
Hello, Adrian. You wrote 30 апреля 2013 г., 8:53:00: AC Any follow-up with the latest stuff in -HEAD? I'd like to see if the AC hardware queue is behaving how I think it is. Sorry, was busy yesterday. Sources: r250041, TDMA is enabled in kernel config. Warm-up: 120 seconds of TCP, throughput osculate between 50 and 100Mbit/, several BAR resets, no hangs. Test: 600 seconds of UDP. Throughput is 20Mbit/s. Hang on ~327s. traffic generator stopped, single forced bstuck helps. Log attached. Please, note: low throughput for UDP on these revisions. It was not so on older revisions, before all this additional debug stuff was added, latest good I tried was something like r249333, and I don't remember about r249767 (but I could try, firmware image is not removed, and I don't have images between r249333 and r249333). -- // Black Lion AKA Lev Serebryakov l...@freebsd.org___ freebsd-wireless@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-wireless To unsubscribe, send any mail to freebsd-wireless-unsubscr...@freebsd.org
Problem with new laptop's ral0 (Ralink 5390)
Hi, i have a problem with my new laptop Asus X55VD which has Ralink's RT5390 chip. I described the problem here: http://forums.freebsd.org/showthread.php?t=39259 Can someone help or suggest anything, i'd really like to run FreeBSD on this lappy and learn it from scratch. Thanks, p0 ___ freebsd-wireless@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-wireless To unsubscribe, send any mail to freebsd-wireless-unsubscr...@freebsd.org
Re: Problem with new laptop's ral0 (Ralink 5390)
Try doing 'up' instead of 'up scan'; does it still lock up? Adrian On 30 April 2013 07:26, Goran Tepshic purpleri...@gmail.com wrote: Hi, i have a problem with my new laptop Asus X55VD which has Ralink's RT5390 chip. I described the problem here: http://forums.freebsd.org/showthread.php?t=39259 Can someone help or suggest anything, i'd really like to run FreeBSD on this lappy and learn it from scratch. Thanks, p0 ___ freebsd-wireless@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-wireless To unsubscribe, send any mail to freebsd-wireless-unsubscr...@freebsd.org ___ freebsd-wireless@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-wireless To unsubscribe, send any mail to freebsd-wireless-unsubscr...@freebsd.org
Re: Problem with new laptop's ral0 (Ralink 5390)
Hi, I've no idea, unfortunately. You'd have to start adding kernel printfs in the driver to see when the driver locks up. I can't be much more help than that at the moment, sorry :( Adrian On 30 April 2013 08:29, Goran Tepshic purpleri...@gmail.com wrote: Adrian, yes, exactly. Not sure why. On Apr 30, 2013 5:28 PM, Adrian Chadd adr...@freebsd.org wrote: Try doing 'up' instead of 'up scan'; does it still lock up? Adrian On 30 April 2013 07:26, Goran Tepshic purpleri...@gmail.com wrote: Hi, i have a problem with my new laptop Asus X55VD which has Ralink's RT5390 chip. I described the problem here: http://forums.freebsd.org/showthread.php?t=39259 Can someone help or suggest anything, i'd really like to run FreeBSD on this lappy and learn it from scratch. Thanks, p0 ___ freebsd-wireless@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-wireless To unsubscribe, send any mail to freebsd-wireless-unsubscr...@freebsd.org ___ freebsd-wireless@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-wireless To unsubscribe, send any mail to freebsd-wireless-unsubscr...@freebsd.org
Re: State os VAP support
On Mon, Apr 29, 2013 at 09:16:09AM -0700, Adrian Chadd wrote: Multiple VAPs should be working. Doubly so on the AR5212 series hardware. adrian Thanks Adrian. When I start two separate hostapd daemons with the config files from my previous post (and separate pidfiles), only the first one works. Starting them in the opposite order, only the other one works so I am (almost) sure that the config files by themselves are correct. Please help! With kind regards, Paul Schenkeveld On 29 April 2013 03:14, Paul Schenkeveld free...@psconsult.nl wrote: Hi, I still cannot get VAP's to work, perhaps I'm doing something wrong, perhaps VAP support isn't ready yet. My hardware: Soekris net4826 with Atheros 5212 mini-pci card My FreeBSD: FreeBSD 10.0-CURRENT #0 r249745 My config: wlans_ath0=wlan63 wlan207 create_args_wlan63=wlanmode hostap mode 11g channel 7 country NL create_args_wlan207=wlanmode hostap mode 11g channel 7 country NL hostapd_config=/etc/hostapd.conf.testB /etc/hostapd.conf.testO hostapd.conf.testB: driver=bsd interface=wlan63 ctrl_interface=/var/run/hostapd.wlan63 ctrl_interface_group=wheel ssid=testB wpa=1 wpa_passphrase= wpa_key_mgmt=WPA-PSK wpa_pairwise=CCMP TKIP hostapd.conf.testO: driver=bsd interface=wlan207 ctrl_interface=/var/run/hostapd.wlan207 ctrl_interface_group=wheel ssid=testO wpa=1 wpa_passphrase= wpa_key_mgmt=WPA-PSK wpa_pairwise=CCMP TKIP I have tried running a single hostapd with two config files and running two separate hostapd daemons each with a config file. In both cases, I get one wlan working, the other does not work. Running hostapd with -d does not reveal the problem to me either (I see debug output when connecting to the working wlan but not when trying to connect to the other one). Hostapd debug output is below. My questions: Should VAP work at all? Does anyone know of VAP problems with the Atheros 5212? Should I run one hostapd with multiple config files or separate daemons? Anything else I'm doing wrong? Thanks for any help! Paul Schenkeveld hostapd -d output: ap1# hostapd -P /var/run/hostapd.pid -d /etc/hostapd.conf.testB /etc/hostapd.conf.testO Configuration file: /etc/hostapd.conf.testB ctrl_interface_group=0 (from group name 'wheel') BSS count 1, BSSID mask 00:00:00:00:00:00 (0 bits) Completing interface initialization Flushing old station entries Deauthenticate all stations bsd_set_privacy: enabled=0 bsd_set_key: alg=0 addr=0x0 key_idx=0 set_tx=1 seq_len=0 key_len=0 bsd_del_key: key_idx=0 bsd_set_key: alg=0 addr=0x0 key_idx=1 set_tx=0 seq_len=0 key_len=0 bsd_del_key: key_idx=1 bsd_set_key: alg=0 addr=0x0 key_idx=2 set_tx=0 seq_len=0 key_len=0 bsd_del_key: key_idx=2 bsd_set_key: alg=0 addr=0x0 key_idx=3 set_tx=0 seq_len=0 key_len=0 bsd_del_key: key_idx=3 Using interface wlan63 with hwaddr 00:0b:6b:dd:50:7b and ssid 'testB' Deriving WPA PSK based on passphrase SSID - hexdump_ascii(len=5): 74 65 73 74 42testB PSK (ASCII passphrase) - hexdump_ascii(len=8): [REMOVED] PSK (from passphrase) - hexdump(len=32): [REMOVED] bsd_set_ieee8021x: enabled=1 bsd_configure_wpa: enable WPA= 0x1 WPA: group state machine entering state GTK_INIT (VLAN-ID 0) GMK - hexdump(len=32): [REMOVED] GTK - hexdump(len=32): [REMOVED] WPA: group state machine entering state SETKEYSDONE (VLAN-ID 0) bsd_set_key: alg=2 addr=0x0 key_idx=1 set_tx=1 seq_len=0 key_len=32 bsd_set_privacy: enabled=1 bsd_set_opt_ie: set WPA+RSN ie (len 28) wlan63: Setup of interface done. Configuration file: /etc/hostapd.conf.testO ctrl_interface_group=0 (from group name 'wheel') BSS count 1, BSSID mask 00:00:00:00:00:00 (0 bits) Completing interface initialization Flushing old station entries Deauthenticate all stations bsd_set_privacy: enabled=0 bsd_set_key: alg=0 addr=0x0 key_idx=0 set_tx=1 seq_len=0 key_len=0 bsd_del_key: key_idx=0 bsd_set_key: alg=0 addr=0x0 key_idx=1 set_tx=0 seq_len=0 key_len=0 bsd_del_key: key_idx=1 bsd_set_key: alg=0 addr=0x0 key_idx=2 set_tx=0 seq_len=0 key_len=0 bsd_del_key: key_idx=2 bsd_set_key: alg=0 addr=0x0 key_idx=3 set_tx=0 seq_len=0 key_len=0 bsd_del_key: key_idx=3 Using interface wlan207 with hwaddr 00:0b:6b:dd:50:7b and ssid 'testO' Deriving WPA PSK based on passphrase SSID - hexdump_ascii(len=5): 74 65 73 74 4ftestO PSK (ASCII passphrase) - hexdump_ascii(len=8): [REMOVED] PSK (from passphrase) - hexdump(len=32): [REMOVED] bsd_set_ieee8021x: enabled=1 bsd_configure_wpa: enable WPA= 0x1 WPA: group state machine entering state GTK_INIT (VLAN-ID 0) GMK - hexdump(len=32):
Re: New hardware, old problem: stuck beacon when here is WiFi traffic
On 30 April 2013 01:24, Lev Serebryakov l...@freebsd.org wrote: Hello, Adrian. You wrote 30 апреля 2013 г., 8:53:00: AC Any follow-up with the latest stuff in -HEAD? I'd like to see if the AC hardware queue is behaving how I think it is. Sorry, was busy yesterday. Sources: r250041, TDMA is enabled in kernel config. Ok. Warm-up: 120 seconds of TCP, throughput osculate between 50 and 100Mbit/, several BAR resets, no hangs. Ok. But did it negotiate A-MPDU? Test: 600 seconds of UDP. Throughput is 20Mbit/s. Hang on ~327s. traffic generator stopped, single forced bstuck helps. Log attached. Please, note: low throughput for UDP on these revisions. It was not so on older revisions, before all this additional debug stuff was added, latest good I tried was something like r249333, and I don't remember about r249767 (but I could try, firmware image is not removed, and I don't have images between r249333 and r249333). It's fine. We'll worry about aggregation later. So here we go: Apr 30 12:21:26 gateway kernel: ath0: ath_stoptxdma: tx queue [9] 0xd8c3000, link 0 Apr 30 12:21:26 gateway kernel: ath0: ath_tx_stopdma: tx queue [0] 0, active=0, hwpending=0, flags 0x, link 0 Apr 30 12:21:26 gateway kernel: ath0: ath_tx_stopdma: tx queue [1] 0xc720ed00, active=0, hwpending=0, flags 0x, link 0 Apr 30 12:21:26 gateway kernel: ath0: ath_tx_stopdma: tx queue [2] 0, active=0, hwpending=0, flags 0x, link 0 Apr 30 12:21:26 gateway kernel: ath0: ath_tx_stopdma: tx queue [3] 0xd8bec00, active=0, hwpending=0, flags 0x, link 0 Apr 30 12:21:26 gateway kernel: ath0: ath_tx_stopdma: tx queue [8] 0xc720d2c0, active=0, hwpending=0, flags 0x, link 0 Notice how the hardware queue isn't active at all. There's frames in the TXQ and the hardware points to the next frame to transmit (but you didn't provide the whole list of frames that were in the TXQ, so I'm going on what it said before.) Hm.. Adrian ___ freebsd-wireless@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-wireless To unsubscribe, send any mail to freebsd-wireless-unsubscr...@freebsd.org
Re: New hardware, old problem: stuck beacon when here is WiFi traffic
Well, right now I'm trying to figure out whether there's a race condition in setting up / enabling the TX queue that I haven't yet seen before, or whether we've hit another one of those corner case bugs in the TX queue handling. I may add in a hack to the completion code that checks if the queue isn't active and if it isn't (but there's frames in the TX queue), it restarts TX. adrian ___ freebsd-wireless@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-wireless To unsubscribe, send any mail to freebsd-wireless-unsubscr...@freebsd.org
