[OpenWrt-Devel] wireless scan/add functioning wrong on my MTK7620n board

[张钊]

It seems that the weird reboot was caused by the power adapter I used, it cannot provide enough power output, after changing it the board went normal, but that warning is still there on UART Console when I add multiple SSID from Luci interface. Maybe next time the board reboot without any kernel panic output or other error messages we need to check the power source first, LOL~~

That warning was triggered like this on my board:
1, I flashed the firmware I built without saving settings.
2, The board booted normally, then I used UART console modified /etc/config/wireless then enable wifi.
3, The first ssid came out normally, then I connected my laptop to that SSID,  use Luci interface, add a secondary said,  the warning appeared just when I applied changes. 

It’s only a warning and both two ssid worked well, thanks to yousong’s patch. I’ll give a try on fixing this warning if I have some other spare time~




On Sep 26, 2014, at 1:54 AM, Sam Mei <smmei at foxmail.com> wrote:

> Could you detail the steps so I can make a test on my 7620n board?
> 
> I have build a wrtnode version for my 7620n router, and looks like everything runs well. 
> 
> sam
> 
>> 在 2014年9月25日，13:04，Yousong Zhou <yszhou4tech at gmail.com> 写道：
>> 
>>> On 25 September 2014 12:06, 张钊 <formywillcancer at gmail.com> wrote:
>>> I’ve built a firmware from git.openwrt.org/openwrt.git known as  CHAOS
>>> CALMER (Bleeding Edge, r42657) for my MTK7620n board, it works well except
>>> this weird problem.
>>> 
>>> When I enable wifi, then trying to use iw dev wlan0 scan or trying to add
>>> secondary AP from luci interface, my board will reboot without any signs at
>>> all, when it rebooted, secondary AP was added, can be joined normally but I
>>> also found a call trace about rt2800lib.c during the initialisation process,
>>> I wonder is this happened on your boards? I only have limited hardware
>>> driver debug skill and if I want to fix it by myself, where to go first?
>> 
>> I haven't seen this before.  Maybe it's caused by kernel panic and
>> reboot?  You may want to attach a serial console to it and see the
>> output.
>> 
>>> [   32.090000] ------------[ cut here ]------------
>>> [   32.100000] WARNING: CPU: 0 PID: 1050 at
>>> /home/zhangzhao/owrt/openwrt/build_dir/target-mipsel_24kec+dsp_uClibc-0.9.33.2/linux-ramips_mt7620n/compat-wireless-2014-05-22/drivers/net/wireless/rt2x00/rt2800lib.c:1092
>>> rt2800_conf_tx+0x3c8/0x494 [rt2800lib]()
>>> [   32.150000] Modules linked in: rt2800soc rt2800mmio rt2800lib pppoe
>>> ppp_async iptable_nat rt2x00soc rt2x00mmio rt2x00lib pppox ppp_generic
>>> nf_nat_ipv4 nf_conntrack_ipv6 nf_conntrack_ipv4 mac80211 ipt_MASQUERADE
>>> cfg80211 xt_time xt_tcpudp xt_state xt_nat xt_multiport xt_mark xt_mac
>>> xt_limit xt_id xt_conntrack xt_comment xt_TCPMSS xt_REDIRECT xt_LOG xt_CT
>>> slhc nf_nat_irc nf_nat_ftp nf_nat nf_defrag_ipv6 nf_defrag_ipv4
>>> nf_conntrack_irc nf_conntrack_ftp nf_conntrack iptable_raw iptable_mangle
>>> iptable_filter ipt_REJECT ip_tables crc_itu_t crc_ccitt compat
>>> ledtrig_usbdev ip6t_REJECT ip6table_raw ip6table_mangle ip6table_filter
>>> ip6_tables x_tables ipv6 eeprom_93cx6 arc4 crypto_blkcipher leds_gpio
>>> ohci_platform ohci_hcd ehci_platform ehci_hcd gpio_button_hotplug usbcore
>>> nls_base usb_common
>>> [   32.280000] CPU: 0 PID: 1050 Comm: mac80211.sh Not tainted 3.14.16 #1
>>> [   32.300000] Stack : 00000000 00000000 00000000 00000000 8031ad2e 00000039
>>> 83294b88 831c0540
>>>         8027b6d4 802be937 0000041a 8031399c 83294b88 831c0540 00000008
>>> 0000001c
>>>         00000001 80225228 00000003 80190aac 00000444 831c0540 8027e850
>>> 828999bc
>>>         00000000 00000000 00000000 00000000 00000000 00000000 00000000
>>> 00000000
>>>         00000000 00000000 00000000 00000000 00000000 00000000 00000000
>>> 82899948
>>>         ...
>>> [   32.310000] Call Trace:
>>> [   32.310000] [<801ccb78>] show_stack+0x48/0x70
>>> [   32.310000] [<80236550>] warn_slowpath_common+0x84/0xb4
>>> [   32.310000] [<80236608>] warn_slowpath_null+0x18/0x24
>>> [   32.310000] [<83164030>] rt2800_conf_tx+0x3c8/0x494 [rt2800lib]
>>> [   32.310000]
>>> [   32.310000] ---[ end trace 0ecb626de4f0471a ]---
>> 
>> 
>> This has been reported [1] before and I created a patch for this [2].
>> Wireless works fine even with this warning triggered.
>> 
>> [1] https://dev.openwrt.org/ticket/17032
>> [2] http://patchwork.openwrt.org/patch/6182/
>> 
>> Regards.
>> 
>>              yousong
>> _______________________________________________
>> openwrt-devel mailing list
>> openwrt-devel at lists.openwrt.org
>> https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
_______________________________________________
openwrt-devel mailing list
openwrt-devel at lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel