Re: [OpenWrt-Devel] Wifi-related kernel-oops on mt7621 after 4.14 update
On Tue, Apr 17, 2018 at 2:56 PM, Felix Fietkauwrote: > On 2018-04-17 13:50, Kristian Evensen wrote: >> This is with the same image as last time (commit >> f6e6eadc99c6274207f8f2ebc739063549959a1f) and configuration (radios >> used as clients). I see that mt76 has been updated during the weekend >> so I will go ahead and compile a new image with the latest updates. > I'm about to push another update in a minute. Please wait for that and > test it. I fixed some more issues in the code. Thanks, great. I just started building a new image for my router, will test and let you know if I still see the issue. BR, Kristian ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Wifi-related kernel-oops on mt7621 after 4.14 update
On 2018-04-17 13:50, Kristian Evensen wrote: > This is with the same image as last time (commit > f6e6eadc99c6274207f8f2ebc739063549959a1f) and configuration (radios > used as clients). I see that mt76 has been updated during the weekend > so I will go ahead and compile a new image with the latest updates. I'm about to push another update in a minute. Please wait for that and test it. I fixed some more issues in the code. - Felix ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] Wifi-related kernel-oops on mt7621 after 4.14 update
Hi, On Thu, Apr 12, 2018 at 3:28 PM, Kristian Evensenwrote: > Thanks for the pointer. I compiled a new image KALLSYMS, but now I am > not able to reproduce the error. Perhaps there was something dirty in > my build directory. I will keep the image KALLSYMS on the routers and > keep checking for the error. The error came back after I updated my router again. Here are the oops'es with KALLMSYS enabled: [ 36.714334] CPU 1 Unable to handle kernel paging request at virtual address f32f0c10, epc == 8f391304, ra == 8f391304 [ 36.724966] Oops[#1]: [ 36.727246] CPU: 1 PID: 33 Comm: kworker/u8:2 Tainted: GW 4.14.32 #0 [ 36.734949] Workqueue: phy1 ieee80211_ibss_leave [mac80211] [ 36.740523] task: 8fd48000 task.stack: 8fd36000 [ 36.745037] $ 0 : 0001 000e 0001 [ 36.750270] $ 4 : 8f37957c [ 36.755506] $ 8 : 80452970 0001 00122121 [ 36.760726] $12 : 0010 77ec6230 [ 36.765946] $16 : 8f37957c 8fd37d58 f32f0c10 94573690 [ 36.771173] $20 : 0001 0040 00ff 8f378bc0 [ 36.776394] $24 : 10d9 8f391218 [ 36.781615] $28 : 8fd36000 8fd37d10 8f391304 [ 36.786837] Hi: 969d [ 36.789701] Lo: 0110 [ 36.792603] epc : 8f391304 mt76_get_survey+0xec/0x31c [mt76] [ 36.798417] ra: 8f391304 mt76_get_survey+0xec/0x31c [mt76] [ 36.804220] Status: 11007c03 KERNEL EXL IE [ 36.808399] Cause : 4088 (ExcCode 02) [ 36.812389] BadVA : f32f0c10 [ 36.815257] PrId : 0001992f (MIPS 1004Kc) [ 36.819331] Modules linked in: rt2800pci rt2800mmio rt2800lib qcserial ppp_async option usb_wwan rt2x00pci rt2x00mmio rt2x00lib rndis_host qmi_wwan ppp_generic nf_nat_pptp nf_conntrack_pptp nf_conntrack_ipv6p [ 36.890390] nf_nat_snmp_basic nf_nat_sip nf_nat_redirect nf_nat_proto_gre nf_nat_masquerade_ipv4 nf_nat_irc nf_conntrack_ipv4 nf_nat_ipv4 nf_nat_h323 nf_nat_ftp nf_nat_amanda nf_nat nf_log_ipv4 nf_flow_tablt [ 36.961381] ip_set_hash_netiface ip_set_hash_netport ip_set_hash_netnet ip_set_hash_net ip_set_hash_netportnet ip_set_hash_mac ip_set_hash_ipportnet ip_set_hash_ipportip ip_set_hash_ipport ip_set_hash_ipmarm [ 37.032821] ohci_hcd ehci_platform sd_mod scsi_mod ehci_hcd gpio_button_hotplug usbcore nls_base usb_common mii [ 37.043006] Process kworker/u8:2 (pid: 33, threadinfo=8fd36000, task=8fd48000, tls=) [ 37.051404] Stack : 0001 80051a40 81494dc0 0400 8f57c000 [ 37.059753] 8ec110dc 002f113b 8fc2a500 81494dc0 0001 [ 37.068100] 814a2dc0 8fc2a614 94573690 [ 37.076449] [ 37.084797] 000c 8ec113a0 0020 8149d2ec 814a2dc0 8fc2a500 [ 37.093147] ... [ 37.095597] Call Trace: [ 37.098045] [<8f391304>] mt76_get_survey+0xec/0x31c [mt76] [ 37.103671] [<8ec110dc>] ___ieee80211_start_rx_ba_session+0x15c/0x39c [mac80211] [ 37.27] [<8ec113a0>] __ieee80211_start_rx_ba_session+0x84/0xb8 [mac80211] [ 37.118315] [<8ec1144c>] ieee80211_process_addba_request+0x78/0x8c [mac80211] [ 37.125507] [<8ec152a0>] ieee80211_ibss_leave+0x44c/0x19c8 [mac80211] [ 37.132067] Code: 2610001c 0c116236 02002025 <8e44> 3c058d4f 34a5df3b 00850019 3012 3810 [ 37.141817] [ 37.143582] ---[ end trace 5af5293c693da408 ]--- [ 37.151753] Kernel panic - not syncing: Fatal exception in interrupt [ 37.160354] Rebooting in 3 seconds.. [ 30.252516] CPU 0 Unable to handle kernel paging request at virtual address eb44a0d5, epc == 8ed40ba4, ra == 8ec86fac [ 30.263189] Oops[#1]: [ 30.265506] CPU: 0 PID: 33 Comm: kworker/u8:2 Tainted: GW 4.14.32 #0 [ 30.273244] Workqueue: phy1 ieee80211_ibss_leave [mac80211] [ 30.278811] task: 8fd48000 task.stack: 8fd36000 [ 30.283321] $ 0 : 0001 7adc6e80 [ 30.288546] $ 4 : 8f3d8bc0 8fd27c20 eb449ae0 8e03a800 [ 30.293766] $ 8 : 80452970 0007 0006edf8 [ 30.298985] $12 : 8ee8d0c0 0007 1dcd6501 [ 30.304205] $16 : 8f3d9560 8f5b8800 8fd27480 8f3d8bc0 [ 30.309425] $20 : 8e03a800 8056 fffe [ 30.314645] $24 : [ 30.319865] $28 : 8fd36000 8fd37cf8 8056 8ec86fac [ 30.325085] Hi: 329d [ 30.327951] Lo: 010e [ 30.330849] epc : 8ed40ba4 mt76x2_dma_cleanup+0x478/0x1128 [mt76x2e] [ 30.337408] ra: 8ec86fac sta_set_sinfo+0xcc/0xbb0 [mac80211] [ 30.343386] Status: 11008403 KERNEL EXL IE [ 30.347565] Cause : c088 (ExcCode 02) [ 30.351553] BadVA : eb44a0d5 [ 30.354421] PrId : 0001992f (MIPS 1004Kc) [ 30.358494] Modules linked in: rt2800pci rt2800mmio rt2800lib qcserial ppp_async option usb_wwan rt2x00pci rt2x00mmio rt2x00lib rndis_host qmi_wwan ppp_generic nf_nat_pptp
Re: [OpenWrt-Devel] [PATCH 0/4] Gemini forward-port to kernel v4.14
On Tue, Apr 17, 2018 at 11:23 AM, Linus Walleijwrote: > On Tue, Apr 17, 2018 at 12:34 AM, Roman Yeryomin wrote: > >> I've found why it didn't work: >> [5.845199] Warning! fotg210_hcd should always be loaded before uhci_hcd >> and ohci_hcd, not after >> >> After fixing kernel config and applying your patch it works. >> So your patch works and is needed indeed. > > I always wondered about that thing, it looks a bit puzzleing, something is not > right... > > The SQ201 has a VIA Vectro VT6212LUSB 2.0 USB controller on PCI, > which is of course EHCI. EHCI req Damned google mail. EHCI requires UHCI to be activated in Kconfig. So to support all Geminis we are between a rock and a hard place here... if I can get the fotg210 working on some board I can maybe look into it. But just supporting fotg210 is fine for now, the SQ201 is not a regression, it's new stuff. Yours, Linus Walleij ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel