* linux-4.5-rc1 TI pandboard-es wifi wlcore locks and reset @ 2016-01-25 12:47 Ross Green 2016-02-01 12:38 ` Ross Green 0 siblings, 1 reply; 12+ messages in thread From: Ross Green @ 2016-01-25 12:47 UTC (permalink / raw) To: linux-kernel [-- Attachment #1: Type: text/plain, Size: 399 bytes --] Just tried the new kernel release on faithful pandaboard es with the new 4.5-rc1 release. There is a problem with the wifi modules once the modules are loaded. Looks like the wifi firmware gets loaded put no response after that causing recovery action. the kernel 4.4 works quite happily with this board. Here is a dmesg dump in the attachment. Anyone have any ideas here? Regards, Ross Green [-- Attachment #2: dmesg-panda-4.5-rc1 --] [-- Type: application/octet-stream, Size: 8715 bytes --] 266.330841] wlcore: firmware booted (Rev 6.3.10.0.133) [ 271.405578] wlcore: ERROR Tx stuck (in FW) for 5000 ms. Starting recovery [ 271.405639] ------------[ cut here ]------------ [ 271.417694] WARNING: CPU: 1 PID: 17 at drivers/net/wireless/ti/wlcore/main.c:787 wl1271_op_cancel_hw_scan+0x838/0x83c [wlc) [ 271.417694] Modules linked in: btwilink st_drv wl12xx wlcore_sdio wlcore mac80211 cfg80211 bluetooth [ 271.429931] CPU: 1 PID: 17 Comm: kworker/u4:1 Tainted: G W 4.5.0-rc1-panda #1 [ 271.448425] Hardware name: Generic OMAP4 (Flattened Device Tree) [ 271.454833] Workqueue: phy0 wl12xx_tx_watchdog_work [wlcore] [ 271.459899] Backtrace: [ 271.459899] [<c0013f80>] (dump_backtrace) from [<c001417c>] (show_stack+0x18/0x1c) [ 271.471496] r7:bf0e6bf0 r6:00000313 r5:c0947c74 r4:00000000 [ 271.471740] [<c0014164>] (show_stack) from [<c03a1988>] (dump_stack+0x98/0xd8) [ 271.485198] [<c03a18f0>] (dump_stack) from [<c0034c30>] (warn_slowpath_common+0x88/0xb8) [ 271.493804] r5:00000009 r4:00000000 [ 271.496337] [<c0034ba8>] (warn_slowpath_common) from [<c0034d04>] (warn_slowpath_null+0x24/0x2c) [ 271.506958] r8:00000000 r7:ee9b0d40 r6:ee9b0d7c r5:ee9b0d48 r4:ee9b0d40 [ 271.507141] [<c0034ce0>] (warn_slowpath_null) from [<bf0e6bf0>] (wl1271_op_cancel_hw_scan+0x838/0x83c [wlcore]) [ 271.524810] [<bf0e6b90>] (wl1271_op_cancel_hw_scan [wlcore]) from [<bf0e6d18>] (wl12xx_tx_watchdog_work+0x124/0x128 [wlcor) [ 271.536834] r5:ee9b0d48 r4:ee9b1b08 [ 271.536834] [<bf0e6bf4>] (wl12xx_tx_watchdog_work [wlcore]) from [<c004a54c>] (process_one_work+0x128/0x400) [ 271.551086] r7:eeb14b00 r6:ef00b000 r5:ef043f80 r4:ee9b1b08 [ 271.551269] [<c004a424>] (process_one_work) from [<c004a878>] (worker_thread+0x54/0x58c) [ 271.565704] r10:ef043f80 r9:ef14a020 r8:ef00b018 r7:c092a100 r6:00000088 r5:ef043f98 [ 271.574035] r4:ef00b000 [ 271.574188] [<c004a824>] (worker_thread) from [<c0050394>] (kthread+0xe4/0xfc) [ 271.584381] r10:00000000 r9:00000000 r8:00000000 r7:c004a824 r6:ef043f80 r5:ef140480 [ 271.590362] r4:00000000 [ 271.595062] [<c00502b0>] (kthread) from [<c000fb98>] (ret_from_fork+0x14/0x3c) [ 271.595062] r7:00000000 r6:00000000 r5:c00502b0 r4:ef140480 [ 271.609161] ---[ end trace 5ce4f982c0e8f8c9 ]--- [ 271.620056] wlcore: Hardware recovery in progress. FW ver: Rev 6.3.10.0.133 [ 271.627868] wlcore: pc: 0x0, hint_sts: 0x00000020 count: 34 [ 271.634094] wlcore: down [ 271.637969] ieee80211 phy0: Hardware restart was requested [ 272.137268] wlcore: firmware booted (Rev 6.3.10.0.133) [ 277.149902] wlcore: ERROR Tx stuck (in FW) for 5000 ms. Starting recovery [ 277.149902] ------------[ cut here ]------------ [ 277.162017] WARNING: CPU: 1 PID: 17 at drivers/net/wireless/ti/wlcore/main.c:787 wl1271_op_cancel_hw_scan+0x838/0x83c [wlc) [ 277.162017] Modules linked in: btwilink st_drv wl12xx wlcore_sdio wlcore mac80211 cfg80211 bluetooth [ 277.174255] CPU: 1 PID: 17 Comm: kworker/u4:1 Tainted: G W 4.5.0-rc1-panda #1 [ 277.192779] Hardware name: Generic OMAP4 (Flattened Device Tree) [ 277.193328] Workqueue: phy0 wl12xx_tx_watchdog_work [wlcore] [ 277.205017] Backtrace: [ 277.205017] [<c0013f80>] (dump_backtrace) from [<c001417c>] (show_stack+0x18/0x1c) [ 277.215850] r7:bf0e6bf0 r6:00000313 r5:c0947c74 r4:00000000 [ 277.221893] [<c0014164>] (show_stack) from [<c03a1988>] (dump_stack+0x98/0xd8) [ 277.229553] [<c03a18f0>] (dump_stack) from [<c0034c30>] (warn_slowpath_common+0x88/0xb8) [ 277.238159] r5:00000009 r4:00000000 [ 277.240722] [<c0034ba8>] (warn_slowpath_common) from [<c0034d04>] (warn_slowpath_null+0x24/0x2c) [ 277.251342] r8:00000000 r7:ee9b0d40 r6:ee9b0d7c r5:ee9b0d48 r4:ee9b0d40 [ 277.258483] [<c0034ce0>] (warn_slowpath_null) from [<bf0e6bf0>] (wl1271_op_cancel_hw_scan+0x838/0x83c [wlcore]) [ 277.269165] [<bf0e6b90>] (wl1271_op_cancel_hw_scan [wlcore]) from [<bf0e6d18>] (wl12xx_tx_watchdog_work+0x124/0x128 [wlcor) [ 277.281188] r5:ee9b0d48 r4:ee9b1b08 [ 277.283721] [<bf0e6bf4>] (wl12xx_tx_watchdog_work [wlcore]) from [<c004a54c>] (process_one_work+0x128/0x400) [ 277.295440] r7:eeb14b00 r6:ef00b000 r5:ef043f80 r4:ee9b1b08 [ 277.301452] [<c004a424>] (process_one_work) from [<c004a878>] (worker_thread+0x54/0x58c) [ 277.310058] r10:ef043f80 r9:ef14a020 r8:ef00b018 r7:c092a100 r6:00000088 r5:ef043f98 [ 277.310333] r4:ef00b000 [ 277.321075] [<c004a824>] (worker_thread) from [<c0050394>] (kthread+0xe4/0xfc) [ 277.328765] r10:00000000 r9:00000000 r8:00000000 r7:c004a824 r6:ef043f80 r5:ef140480 [ 277.332489] r4:00000000 [ 277.339813] [<c00502b0>] (kthread) from [<c000fb98>] (ret_from_fork+0x14/0x3c) [ 277.339813] r7:00000000 r6:00000000 r5:c00502b0 r4:ef140480 [ 277.352172] ---[ end trace 5ce4f982c0e8f8ca ]--- [ 277.364349] wlcore: Hardware recovery in progress. FW ver: Rev 6.3.10.0.133 [ 277.372161] wlcore: pc: 0x0, hint_sts: 0x00000020 count: 35 [ 277.378509] wlcore: down [ 277.381286] ieee80211 phy0: Hardware restart was requested [ 278.078155] wlcore: firmware booted (Rev 6.3.10.0.133) ^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: linux-4.5-rc1 TI pandboard-es wifi wlcore locks and reset 2016-01-25 12:47 linux-4.5-rc1 TI pandboard-es wifi wlcore locks and reset Ross Green @ 2016-02-01 12:38 ` Ross Green 2016-02-02 4:34 ` Sebastian Reichel 0 siblings, 1 reply; 12+ messages in thread From: Ross Green @ 2016-02-01 12:38 UTC (permalink / raw) To: linux-kernel; +Cc: robertcnelson [-- Attachment #1: Type: text/plain, Size: 956 bytes --] Just updated to the latest linux-4.5-rc2 and same result as rc1. The wireless module loads firmware and then stalls causing a reset of the device and then continues to go through a stall and reset cycle. please find enclosed a copy of the dmesg output. Is there anyone else testing a pandaboard with linux-4.5-rc2? Just for completeness also tested the latest linux-4.4.1 kernel and found no problems with the wireless modules. Regards, Ross Green On Mon, Jan 25, 2016 at 11:47 PM, Ross Green <rgkernel@gmail.com> wrote: > Just tried the new kernel release on faithful pandaboard es with the > new 4.5-rc1 release. > > There is a problem with the wifi modules once the modules are loaded. > Looks like the wifi firmware gets loaded put no response after that > causing recovery action. > > the kernel 4.4 works quite happily with this board. > > Here is a dmesg dump in the attachment. > > Anyone have any ideas here? > > Regards, > > Ross Green [-- Attachment #2: dmesg-4.5-rc2 --] [-- Type: application/octet-stream, Size: 33114 bytes --] # # # dmesg [ 0.000000] Booting Linux on physical CPU 0x0 [ 0.000000] Linux version 4.5.0-rc2-panda (rfg@red.dwarf) (gcc version 5.3.0 (Buildroot 2016.02-git-00183-g1682aee) ) #1 S6 [ 0.000000] CPU: ARMv7 Processor [412fc09a] revision 10 (ARMv7), cr=10c5387d [ 0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache [ 0.000000] Machine model: TI OMAP4 PandaBoard-ES [ 0.000000] Memory policy: Data cache writealloc [ 0.000000] OMAP4: Map 0xbfe00000 to fe600000 for dram barrier [ 0.000000] On node 0 totalpages: 261632 [ 0.000000] free_area_init_node: node 0, pgdat c0966200, node_mem_map ef7f9000 [ 0.000000] Normal zone: 1536 pages used for memmap [ 0.000000] Normal zone: 0 pages reserved [ 0.000000] Normal zone: 196608 pages, LIFO batch:31 [ 0.000000] HighMem zone: 65024 pages, LIFO batch:15 [ 0.000000] OMAP4460 ES1.1 [ 0.000000] PERCPU: Embedded 12 pages/cpu @ef7ab000 s17984 r8192 d22976 u49152 [ 0.000000] pcpu-alloc: s17984 r8192 d22976 u49152 alloc=12*4096 [ 0.000000] pcpu-alloc: [0] 0 [0] 1 [ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 260096 [ 0.000000] Kernel command line: root=/dev/mmcblk0p2 rootwait console=ttyO2,115200 [ 0.000000] PID hash table entries: 4096 (order: 2, 16384 bytes) [ 0.000000] Dentry cache hash table entries: 131072 (order: 7, 524288 bytes) [ 0.000000] Inode-cache hash table entries: 65536 (order: 6, 262144 bytes) [ 0.000000] Memory: 1027232K/1046528K available (6879K kernel code, 252K rwdata, 2156K rodata, 304K init, 297K bss, 19296K) [ 0.000000] Virtual kernel memory layout: vector : 0xffff0000 - 0xffff1000 ( 4 kB) fixmap : 0xffc00000 - 0xfff00000 (3072 kB) vmalloc : 0xf0800000 - 0xff800000 ( 240 MB) lowmem : 0xc0000000 - 0xf0000000 ( 768 MB) pkmap : 0xbfe00000 - 0xc0000000 ( 2 MB) modules : 0xbf000000 - 0xbfe00000 ( 14 MB) .text : 0xc0008000 - 0xc08db0d4 (9037 kB) .init : 0xc08dc000 - 0xc0928000 ( 304 kB) .data : 0xc0928000 - 0xc0967200 ( 253 kB) .bss : 0xc096a000 - 0xc09b47b8 ( 298 kB) [ 0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=2, Nodes=1 [ 0.000000] Preemptible hierarchical RCU implementation. [ 0.000000] [ 0.000000] NR_IRQS:16 nr_irqs:16 16 [ 0.000000] L2C: platform modifies aux control register: 0x0e070000 -> 0x3e470000 [ 0.000000] L2C: DT/platform modifies aux control register: 0x0e070000 -> 0x3e470000 [ 0.000000] L2C-310 enabling early BRESP for Cortex-A9 [ 0.000000] OMAP L2C310: ROM does not support power control setting [ 0.000000] L2C-310 dynamic clock gating disabled, standby mode disabled [ 0.000000] L2C-310 cache controller enabled, 16 ways, 1024 kB [ 0.000000] L2C-310: CACHE_ID 0x410000c7, AUX_CTRL 0x4e470000 [ 0.000000] ti_dt_clocks_register: failed to lookup clock node dss_fck [ 0.000000] ti_dt_clocks_register: failed to lookup clock node dss_fck [ 0.000000] ti_dt_clocks_register: failed to lookup clock node bandgap_fclk [ 0.000000] OMAP clockevent source: timer1 at 32768 Hz [ 0.000000] clocksource: 32k_counter: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 58327039986419 ns [ 0.000000] sched_clock: 32 bits at 32kHz, resolution 30517ns, wraps every 65535999984741ns [ 0.000000] OMAP clocksource: 32k_counter at 32768 Hz [ 0.000854] Console: colour dummy device 80x30 [ 0.000885] Calibrating delay loop... 1397.55 BogoMIPS (lpj=6987776) [ 0.089172] pid_max: default: 32768 minimum: 301 [ 0.089233] Security Framework initialized [ 0.089294] Mount-cache hash table entries: 2048 (order: 1, 8192 bytes) [ 0.089294] Mountpoint-cache hash table entries: 2048 (order: 1, 8192 bytes) [ 0.089935] CPU: Testing write buffer coherency: ok [ 0.090148] CPU0: thread -1, cpu 0, socket 0, mpidr 80000000 [ 0.090209] Setting up static identity map for 0x80008280 - 0x800082d8 [ 0.209167] CPU1: thread -1, cpu 1, socket 0, mpidr 80000001 [ 0.209228] Brought up 2 CPUs [ 0.209259] SMP: Total of 2 processors activated (2795.11 BogoMIPS). [ 0.209259] CPU: All CPU(s) started in SVC mode. [ 0.210052] devtmpfs: initialized [ 0.226684] VFP support v0.3: implementor 41 architecture 3 part 30 variant 9 rev 4 [ 0.227172] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns [ 0.227325] xor: measuring software checksum speed [ 0.319152] arm4regs : 1006.000 MB/sec [ 0.419128] 8regs : 804.000 MB/sec [ 0.519134] 32regs : 760.800 MB/sec [ 0.519165] xor: using function: arm4regs (1006.000 MB/sec) [ 0.519409] pinctrl core: initialized pinctrl subsystem [ 0.521301] NET: Registered protocol family 16 [ 0.522277] DMA: preallocated 256 KiB pool for atomic coherent allocations [ 0.524047] omap_hwmod: l3_main_3 using broken dt data from ocp [ 0.525634] omap_hwmod: l3_main_2 using broken dt data from ocp [ 0.632110] OMAP GPIO hardware version 0.1 [ 0.637390] omap-gpmc 50000000.gpmc: GPMC revision 6.0 [ 0.637420] gpmc_mem_init: disabling cs 0 mapped at 0x0-0x1000000 [ 0.637939] irq: no irq domain found for /ocp/l4@4a000000/scm@100000/pinmux@40 ! [ 0.638336] irq: no irq domain found for /ocp/l4@4a000000/scm@100000/pinmux@40 ! [ 0.638702] irq: no irq domain found for /ocp/l4@4a000000/scm@100000/pinmux@40 ! [ 0.650665] platform 4b501000.aes: Cannot lookup hwmod 'aes' [ 0.650970] platform 480a5000.des: Cannot lookup hwmod 'des' [ 0.657012] hw-breakpoint: found 5 (+1 reserved) breakpoint and 1 watchpoint registers. [ 0.657012] hw-breakpoint: maximum watchpoint size is 4 bytes. [ 0.657653] omap4_sram_init:Unable to get sram pool needed to handle errata I688 [ 0.657867] OMAP DMA hardware revision 0.0 [ 0.889739] raid6: int32x1 gen() 103 MB/s [ 1.059265] raid6: int32x1 xor() 84 MB/s [ 1.229583] raid6: int32x2 gen() 134 MB/s [ 1.399169] raid6: int32x2 xor() 98 MB/s [ 1.569244] raid6: int32x4 gen() 145 MB/s [ 1.739257] raid6: int32x4 xor() 97 MB/s [ 1.909240] raid6: int32x8 gen() 160 MB/s [ 2.079315] raid6: int32x8 xor() 94 MB/s [ 2.079315] raid6: using algorithm int32x8 gen() 160 MB/s [ 2.079345] raid6: .... xor() 94 MB/s, rmw enabled [ 2.079345] raid6: using intx1 recovery algorithm [ 2.085388] omap-dma-engine 4a056000.dma-controller: OMAP DMA engine driver [ 2.159301] reg-fixed-voltage wl12xx_vmmc: could not find pctldev for node /ocp/l4@4a000000/scm@100000/pinmux@40/pinmux_wle [ 2.163543] omap-iommu 4a066000.mmu: 4a066000.mmu registered [ 2.163665] omap-iommu 55082000.mmu: 55082000.mmu registered [ 2.165771] SCSI subsystem initialized [ 2.166046] usbcore: registered new interface driver usbfs [ 2.166168] usbcore: registered new interface driver hub [ 2.166320] usbcore: registered new device driver usb [ 2.167266] omap_i2c 48070000.i2c: could not find pctldev for node /ocp/l4@4a000000/scm@100000/pinmux@40/pinmux_i2c1_pins,e [ 2.167327] omap_i2c 48072000.i2c: could not find pctldev for node /ocp/l4@4a000000/scm@100000/pinmux@40/pinmux_i2c2_pins,e [ 2.167358] omap_i2c 48060000.i2c: could not find pctldev for node /ocp/l4@4a000000/scm@100000/pinmux@40/pinmux_i2c3_pins,e [ 2.167388] omap_i2c 48350000.i2c: could not find pctldev for node /ocp/l4@4a000000/scm@100000/pinmux@40/pinmux_i2c4_pins,e [ 2.167663] Linux video capture interface: v2.00 [ 2.168426] Advanced Linux Sound Architecture Driver Initialized. [ 2.169891] clocksource: Switched to clocksource 32k_counter [ 2.184112] NET: Registered protocol family 2 [ 2.184692] TCP established hash table entries: 8192 (order: 3, 32768 bytes) [ 2.184783] TCP bind hash table entries: 8192 (order: 4, 65536 bytes) [ 2.184906] TCP: Hash tables configured (established 8192 bind 8192) [ 2.184997] UDP hash table entries: 512 (order: 2, 16384 bytes) [ 2.185058] UDP-Lite hash table entries: 512 (order: 2, 16384 bytes) [ 2.185241] NET: Registered protocol family 1 [ 2.185638] RPC: Registered named UNIX socket transport module. [ 2.185638] RPC: Registered udp transport module. [ 2.185638] RPC: Registered tcp transport module. [ 2.185638] RPC: Registered tcp NFSv4.1 backchannel transport module. [ 2.187652] hw perfevents: enabled with armv7_cortex_a9 PMU driver, 7 counters available [ 2.189758] futex hash table entries: 512 (order: 3, 32768 bytes) [ 2.198547] NFS: Registering the id_resolver key type [ 2.198608] Key type id_resolver registered [ 2.198608] Key type id_legacy registered [ 2.198638] nfs4filelayout_init: NFSv4 File Layout Driver Registering... [ 2.198669] Installing knfsd (copyright (C) 1996 okir@monad.swb.de). [ 2.209930] ntfs: driver 2.1.32 [Flags: R/O]. [ 2.210205] fuse init (API version 7.24) [ 2.213684] jitterentropy: Initialization failed with host not compliant with requirements: 2 [ 2.213775] bounce: pool size: 64 pages [ 2.213775] io scheduler noop registered [ 2.213806] io scheduler deadline registered [ 2.213836] io scheduler cfq registered (default) [ 2.214721] pinctrl-single 4a100040.pinmux: 203 pins at pa fc100040 size 406 [ 2.214935] pinctrl-single 4a31e040.pinmux: 28 pins at pa fc31e040 size 56 [ 2.217926] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled [ 2.219543] omap_uart 4806a000.serial: no wakeirq for uart0 [ 2.219665] 4806a000.serial: ttyO0 at MMIO 0x4806a000 (irq = 226, base_baud = 3000000) is a OMAP UART0 [ 2.220245] 4806c000.serial: ttyO1 at MMIO 0x4806c000 (irq = 227, base_baud = 3000000) is a OMAP UART1 [ 2.220794] 48020000.serial: ttyO2 at MMIO 0x48020000 (irq = 228, base_baud = 3000000) is a OMAP UART2 [ 3.117523] console [ttyO2] enabled [ 3.121704] 4806e000.serial: ttyO3 at MMIO 0x4806e000 (irq = 229, base_baud = 3000000) is a OMAP UART3 [ 3.132415] [drm] Initialized drm 1.1.0 20060810 [ 3.138946] 58000000.dss supply vdda_video not found, using dummy regulator [ 3.146362] OMAP DSS rev 4.0 [ 3.149505] omapdss_dss 58000000.dss: bound 58001000.dispc (ops dispc_component_ops) [ 3.157836] omapdss_dss 58000000.dss: bound 58005000.encoder (ops dsi_component_ops) [ 3.166473] omapdss_dss 58000000.dss: bound 58006000.encoder (ops hdmi4_component_ops) [ 3.218261] loop: module loaded [ 3.224365] usbcore: registered new interface driver smsc95xx [ 3.230499] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver [ 3.237335] ehci-omap: OMAP-EHCI Host Controller driver [ 3.259918] ehci-omap 4a064c00.ehci: EHCI Host Controller [ 3.265594] ehci-omap 4a064c00.ehci: new USB bus registered, assigned bus number 1 [ 3.273681] ehci-omap 4a064c00.ehci: irq 336, io mem 0x4a064c00 [ 3.289916] ehci-omap 4a064c00.ehci: USB 2.0 started, EHCI 1.00 [ 3.296295] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002 [ 3.303405] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 3.310974] usb usb1: Product: EHCI Host Controller [ 3.316070] usb usb1: Manufacturer: Linux 4.5.0-rc2-panda ehci_hcd [ 3.322540] usb usb1: SerialNumber: 4a064c00.ehci [ 3.328155] hub 1-0:1.0: USB hub found [ 3.332122] hub 1-0:1.0: 3 ports detected [ 3.337036] usbcore: registered new interface driver cdc_wdm [ 3.343109] usbcore: registered new interface driver usb-storage [ 3.349822] i2c /dev entries driver [ 3.353637] usbcore: registered new interface driver uvcvideo [ 3.359619] USB Video Class driver (1.1.1) [ 3.365142] omap_wdt: OMAP Watchdog Timer Rev 0x01: initial timeout 60 sec [ 3.372711] device-mapper: uevent: version 1.0.3 [ 3.377868] device-mapper: ioctl: 4.34.0-ioctl (2015-10-28) initialised: dm-devel@redhat.com [ 3.441345] hidraw: raw HID events driver (C) Jiri Kosina [ 3.447418] usbcore: registered new interface driver usbhid [ 3.453277] usbhid: USB HID core driver [ 3.457824] emif 4c000000.emif: emif_probe: device configured with addr = f08a8000 and IRQ247 [ 3.467193] emif 4d000000.emif: emif_probe: device configured with addr = f08aa000 and IRQ248 [ 3.478698] omap-abe-twl6040 sound: ASoC: CODEC DAI twl6040-legacy not registered [ 3.486663] omap-abe-twl6040 sound: snd_soc_register_card() failed: -517 [ 3.494232] ip_tables: (C) 2000-2006 Netfilter Core Team [ 3.499938] Initializing XFRM netlink socket [ 3.504486] NET: Registered protocol family 17 [ 3.509490] Key type dns_resolver registered [ 3.514160] twl: not initialized [ 3.517578] twl6030_uv_to_vsel:OUT OF RANGE! non mapped vsel for 1375000 Vs max 1316660 [ 3.526092] twl6030_uv_to_vsel:OUT OF RANGE! non mapped vsel for 1375000 Vs max 1316660 [ 3.534576] twl6030_uv_to_vsel:OUT OF RANGE! non mapped vsel for 1375000 Vs max 1316660 [ 3.543090] twl6030_uv_to_vsel:OUT OF RANGE! non mapped vsel for 1375000 Vs max 1316660 [ 3.551574] twl6030_uv_to_vsel:OUT OF RANGE! non mapped vsel for 1375000 Vs max 1316660 [ 3.560058] twl6030_uv_to_vsel:OUT OF RANGE! non mapped vsel for 1375000 Vs max 1316660 [ 3.568542] twl6030_uv_to_vsel:OUT OF RANGE! non mapped vsel for 1410000 Vs max 1316660 [ 3.577056] omap2_set_init_voltage: unable to find boot up OPP for vdd_mpu [ 3.584350] omap2_set_init_voltage: unable to set vdd_mpu [ 3.590087] omap2_set_init_voltage: unable to find boot up OPP for vdd_core [ 3.597442] omap2_set_init_voltage: unable to set vdd_core [ 3.603271] omap2_set_init_voltage: unable to find boot up OPP for vdd_iva [ 3.610565] omap2_set_init_voltage: unable to set vdd_iva [ 3.617492] Power Management for TI OMAP4+ devices. [ 3.622680] OMAP4 PM: u-boot >= v2012.07 is required for full PM support [ 3.629913] ThumbEE CPU extension supported. [ 3.634490] Registering SWP/SWPB emulation handler [ 3.634490] SmartReflex Class3 initialized [ 3.665496] Btrfs loaded [ 3.666076] usb 1-1: new high-speed USB device number 2 using ehci-omap [ 3.677612] dmm 4e000000.dmm: initialized all PAT entries [ 3.685089] Skipping twl internal clock init and using bootloader value (unknown osc rate) [ 3.720397] twl 0-0048: PIH (irq 340) nested IRQs [ 3.726837] twl_rtc 48070000.i2c:twl@48:rtc: Enabling TWL-RTC [ 3.735961] twl_rtc 48070000.i2c:twl@48:rtc: rtc core: registered 48070000.i2c:twl@48 as rtc0 [ 3.756103] twl6040 0-004b: clk32k is not handled [ 3.763610] omap_i2c 48070000.i2c: bus 0 rev0.11 at 400 kHz [ 3.770507] omap_i2c 48072000.i2c: bus 1 rev0.11 at 400 kHz [ 3.777526] omap_i2c 48060000.i2c: bus 2 rev0.11 at 100 kHz [ 3.784545] omap_i2c 48350000.i2c: bus 3 rev0.11 at 400 kHz [ 3.791107] omap_hsmmc 4809c000.mmc: omap_device: omap_device_enable() called from invalid state 1 [ 3.839447] usb 1-1: New USB device found, idVendor=0424, idProduct=9514 [ 3.847137] omap_hsmmc 480d5000.mmc: omap_device: omap_device_enable() called from invalid state 1 [ 3.856994] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0 [ 3.865509] hub 1-1:1.0: USB hub found [ 3.872833] hub 1-1:1.0: 5 ports detected [ 3.985595] omap_hsmmc 480d5000.mmc: card claims to support voltages below defined range [ 3.999267] omap-abe-twl6040 sound: twl6040-legacy <-> 40132000.mcpdm mapping ok [ 4.011352] twl_rtc 48070000.i2c:twl@48:rtc: setting system clock to 2000-01-06 05:35:28 UTC (947136928) [ 4.015258] mmc1: new SDIO card at address 0001 [ 4.026184] sr_init: No PMIC hook to init smartreflex [ 4.031738] smartreflex smartreflex.0: omap_sr_probe: SmartReflex driver initialized [ 4.040222] smartreflex smartreflex.1: omap_sr_probe: SmartReflex driver initialized [ 4.048736] smartreflex smartreflex.2: omap_sr_probe: SmartReflex driver initialized [ 4.065917] vwl1271: disabling [ 4.069641] mmc0: host does not support reading read-only switch, assuming write-enable [ 4.079742] VDAC: disabling [ 4.081695] mmc0: new high speed SDHC card at address e624 [ 4.089050] VANA: disabling [ 4.092407] mmcblk0: mmc0:e624 SL32G 28.8 GiB [ 4.097106] VUSB: disabling [ 4.100494] ALSA device list: [ 4.100616] #0: PandaBoardES [ 4.129486] mmcblk0: p1 p2 p3 p4 [ 4.145416] EXT4-fs (mmcblk0p2): couldn't mount as ext3 due to feature incompatibilities [ 4.154663] EXT4-fs (mmcblk0p2): mounting ext2 file system using the ext4 subsystem [ 4.164916] usb 1-1.1: new high-speed USB device number 3 using ehci-omap [ 4.206359] EXT4-fs (mmcblk0p2): mounted filesystem without journal. Opts: (null) [ 4.217407] VFS: Mounted root (ext2 filesystem) readonly on device 179:2. [ 4.233825] devtmpfs: mounted [ 4.233825] Freeing unused kernel memory: 304K (c08dc000 - c0928000) [ 4.282165] usb 1-1.1: New USB device found, idVendor=0424, idProduct=ec00 [ 4.282165] usb 1-1.1: New USB device strings: Mfr=0, Product=0, SerialNumber=0 [ 4.300445] smsc95xx v1.0.4 [ 4.416534] smsc95xx 1-1.1:1.0 eth0: register 'smsc95xx' at usb-4a064c00.ehci-1.1, smsc95xx USB 2.0 Ethernet, 9e:72:45:9a:6 [ 4.589111] EXT4-fs (mmcblk0p2): warning: mounting unchecked fs, running e2fsck is recommended [ 4.652618] EXT4-fs (mmcblk0p2): re-mounted. Opts: (null) [ 4.784667] random: dd urandom read with 28 bits of entropy available [ 7.470184] smsc95xx 1-1.1:1.0 eth0: hardware isn't capable of remote wakeup [ 17.441986] Bluetooth: Core ver 2.21 [ 17.445983] NET: Registered protocol family 31 [ 17.450927] Bluetooth: HCI device and connection manager initialized [ 17.457733] Bluetooth: HCI socket layer initialized [ 17.463104] Bluetooth: L2CAP socket layer initialized [ 17.469055] Bluetooth: SCO socket layer initialized [ 25.057678] NFSD: the nfsdcld client tracking upcall will be removed in 3.10. Please transition to using nfsdcltrack. [ 25.069152] NFSD: starting 90-second grace period (net c0960740) [ 41.226531] random: nonblocking pool is initialized [ 41.642150] wlcore: loaded ... [ 180.659240] ------------[ cut here ]------------ [ 180.659240] WARNING: CPU: 1 PID: 6 at drivers/net/wireless/ti/wlcore/main.c:787 wl1271_op_cancel_hw_scan+0x838/0x83c [wlco) [ 180.676330] Modules linked in: btwilink st_drv wl12xx wlcore_sdio wlcore mac80211 cfg80211 bluetooth [ 180.685882] CPU: 1 PID: 6 Comm: kworker/u4:0 Tainted: G W 4.5.0-rc2-panda #1 [ 180.694793] Hardware name: Generic OMAP4 (Flattened Device Tree) [ 180.701171] Workqueue: phy0 wl12xx_tx_watchdog_work [wlcore] [ 180.707183] Backtrace: [ 180.707183] [<c0013f80>] (dump_backtrace) from [<c001417c>] (show_stack+0x18/0x1c) [ 180.717834] r7:bf0e6bf0 r6:00000313 r5:c0947cb4 r4:00000000 [ 180.723907] [<c0014164>] (show_stack) from [<c03a1908>] (dump_stack+0x98/0xd8) [ 180.723907] [<c03a1870>] (dump_stack) from [<c0034c30>] (warn_slowpath_common+0x88/0xb8) [ 180.740173] r5:00000009 r4:00000000 [ 180.740417] [<c0034ba8>] (warn_slowpath_common) from [<c0034d04>] (warn_slowpath_null+0x24/0x2c) [ 180.748077] r8:00000000 r7:ee8fcd40 r6:ee8fcd7c r5:ee8fcd48 r4:ee8fcd40 [ 180.760467] [<c0034ce0>] (warn_slowpath_null) from [<bf0e6bf0>] (wl1271_op_cancel_hw_scan+0x838/0x83c [wlcore]) [ 180.771148] [<bf0e6b90>] (wl1271_op_cancel_hw_scan [wlcore]) from [<bf0e6d18>] (wl12xx_tx_watchdog_work+0x124/0x128 [wlcor) [ 180.771423] r5:ee8fcd48 r4:ee8fdb08 [ 180.786987] [<bf0e6bf4>] (wl12xx_tx_watchdog_work [wlcore]) from [<c004a54c>] (process_one_work+0x128/0x400) [ 180.797393] r7:eeade700 r6:ef00b000 r5:ef02f900 r4:ee8fdb08 [ 180.803466] [<c004a424>] (process_one_work) from [<c004a878>] (worker_thread+0x54/0x58c) [ 180.803466] r10:ef02f900 r9:ef094020 r8:ef00b018 r7:c092a100 r6:00000088 r5:ef02f918 [ 180.820343] r4:ef00b000 [ 180.820343] [<c004a824>] (worker_thread) from [<c0050394>] (kthread+0xe4/0xfc) [ 180.830718] r10:00000000 r9:00000000 r8:00000000 r7:c004a824 r6:ef02f900 r5:ef0408c0 [ 180.831207] r4:00000000 [ 180.841735] [<c00502b0>] (kthread) from [<c000fb98>] (ret_from_fork+0x14/0x3c) [ 180.841766] r7:00000000 r6:00000000 r5:c00502b0 r4:ef0408c0 [ 180.851898] ---[ end trace 8afaed8976dc671c ]--- [ 180.866302] wlcore: Hardware recovery in progress. FW ver: Rev 6.3.10.0.133 [ 180.874114] wlcore: pc: 0x0, hint_sts: 0x00000020 count: 14 [ 180.880462] wlcore: down [ 180.883239] ieee80211 phy0: Hardware restart was requested [ 181.423950] wlcore: firmware booted (Rev 6.3.10.0.133) [ 186.439941] wlcore: ERROR Tx stuck (in FW) for 5000 ms. Starting recovery [ 186.439941] ------------[ cut here ]------------ [ 186.452056] WARNING: CPU: 1 PID: 6 at drivers/net/wireless/ti/wlcore/main.c:787 wl1271_op_cancel_hw_scan+0x838/0x83c [wlco) [ 186.464263] Modules linked in: btwilink st_drv wl12xx wlcore_sdio wlcore mac80211 cfg80211 bluetooth [ 186.470581] CPU: 1 PID: 6 Comm: kworker/u4:0 Tainted: G W 4.5.0-rc2-panda #1 [ 186.482727] Hardware name: Generic OMAP4 (Flattened Device Tree) [ 186.483062] Workqueue: phy0 wl12xx_tx_watchdog_work [wlcore] [ 186.494934] Backtrace: [ 186.495147] [<c0013f80>] (dump_backtrace) from [<c001417c>] (show_stack+0x18/0x1c) [ 186.505798] r7:bf0e6bf0 r6:00000313 r5:c0947cb4 r4:00000000 [ 186.510528] [<c0014164>] (show_stack) from [<c03a1908>] (dump_stack+0x98/0xd8) [ 186.519500] [<c03a1870>] (dump_stack) from [<c0034c30>] (warn_slowpath_common+0x88/0xb8) [ 186.528106] r5:00000009 r4:00000000 [ 186.530670] [<c0034ba8>] (warn_slowpath_common) from [<c0034d04>] (warn_slowpath_null+0x24/0x2c) [ 186.541259] r8:00000000 r7:ee8fcd40 r6:ee8fcd7c r5:ee8fcd48 r4:ee8fcd40 [ 186.541503] [<c0034ce0>] (warn_slowpath_null) from [<bf0e6bf0>] (wl1271_op_cancel_hw_scan+0x838/0x83c [wlcore]) [ 186.559143] [<bf0e6b90>] (wl1271_op_cancel_hw_scan [wlcore]) from [<bf0e6d18>] (wl12xx_tx_watchdog_work+0x124/0x128 [wlcor) [ 186.571136] r5:ee8fcd48 r4:ee8fdb08 [ 186.573669] [<bf0e6bf4>] (wl12xx_tx_watchdog_work [wlcore]) from [<c004a54c>] (process_one_work+0x128/0x400) [ 186.585388] r7:eeade700 r6:ef00b000 r5:ef02f900 r4:ee8fdb08 [ 186.585632] [<c004a424>] (process_one_work) from [<c004a878>] (worker_thread+0x54/0x58c) [ 186.597015] r10:ef02f900 r9:ef094020 r8:ef00b018 r7:c092a100 r6:00000088 r5:ef02f918 [ 186.603759] r4:ef00b000 [ 186.603759] [<c004a824>] (worker_thread) from [<c0050394>] (kthread+0xe4/0xfc) [ 186.618743] r10:00000000 r9:00000000 r8:00000000 r7:c004a824 r6:ef02f900 r5:ef0408c0 [ 186.627105] r4:00000000 [ 186.627105] [<c00502b0>] (kthread) from [<c000fb98>] (ret_from_fork+0x14/0x3c) [ 186.637451] r7:00000000 r6:00000000 r5:c00502b0 r4:ef0408c0 [ 186.643493] ---[ end trace 8afaed8976dc671d ]--- [ 186.654357] wlcore: Hardware recovery in progress. FW ver: Rev 6.3.10.0.133 [ 186.662170] wlcore: pc: 0x0, hint_sts: 0x00000020 count: 15 [ 186.668487] wlcore: down [ 186.671295] ieee80211 phy0: Hardware restart was requested [ 187.140624] wlcore: firmware booted (Rev 6.3.10.0.133) [ 192.150848] wlcore: ERROR Tx stuck (in FW) for 5000 ms. Starting recovery [ 192.150970] ------------[ cut here ]------------ [ 192.150970] WARNING: CPU: 1 PID: 6 at drivers/net/wireless/ti/wlcore/main.c:787 wl1271_op_cancel_hw_scan+0x838/0x83c [wlco) [ 192.150970] Modules linked in: btwilink st_drv wl12xx wlcore_sdio wlcore mac80211 cfg80211 bluetooth [ 192.150970] CPU: 1 PID: 6 Comm: kworker/u4:0 Tainted: G W 4.5.0-rc2-panda #1 [ 192.193511] Hardware name: Generic OMAP4 (Flattened Device Tree) [ 192.199920] Workqueue: phy0 wl12xx_tx_watchdog_work [wlcore] [ 192.201080] Backtrace: [ 192.205932] [<c0013f80>] (dump_backtrace) from [<c001417c>] (show_stack+0x18/0x1c) [ 192.216583] r7:bf0e6bf0 r6:00000313 r5:c0947cb4 r4:00000000 [ 192.219940] [<c0014164>] (show_stack) from [<c03a1908>] (dump_stack+0x98/0xd8) [ 192.230316] [<c03a1870>] (dump_stack) from [<c0034c30>] (warn_slowpath_common+0x88/0xb8) [ 192.238891] r5:00000009 r4:00000000 [ 192.241424] [<c0034ba8>] (warn_slowpath_common) from [<c0034d04>] (warn_slowpath_null+0x24/0x2c) [ 192.252044] r8:00000000 r7:ee8fcd40 r6:ee8fcd7c r5:ee8fcd48 r4:ee8fcd40 [ 192.259216] [<c0034ce0>] (warn_slowpath_null) from [<bf0e6bf0>] (wl1271_op_cancel_hw_scan+0x838/0x83c [wlcore]) [ 192.259216] [<bf0e6b90>] (wl1271_op_cancel_hw_scan [wlcore]) from [<bf0e6d18>] (wl12xx_tx_watchdog_work+0x124/0x128 [wlcor) [ 192.281890] r5:ee8fcd48 r4:ee8fdb08 [ 192.282226] [<bf0e6bf4>] (wl12xx_tx_watchdog_work [wlcore]) from [<c004a54c>] (process_one_work+0x128/0x400) [ 192.296173] r7:eeade700 r6:ef00b000 r5:ef02f900 r4:ee8fdb08 [ 192.296386] [<c004a424>] (process_one_work) from [<c004a878>] (worker_thread+0x54/0x58c) [ 192.310791] r10:ef02f900 r9:ef094020 r8:ef00b018 r7:c092a100 r6:00000088 r5:ef02f918 [ 192.319122] r4:ef00b000 [ 192.321838] [<c004a824>] (worker_thread) from [<c0050394>] (kthread+0xe4/0xfc) [ 192.321868] r10:00000000 r9:00000000 r8:00000000 r7:c004a824 r6:ef02f900 r5:ef0408c0 [ 192.321868] r4:00000000 [ 192.340545] [<c00502b0>] (kthread) from [<c000fb98>] (ret_from_fork+0x14/0x3c) [ 192.340728] r7:00000000 r6:00000000 r5:c00502b0 r4:ef0408c0 [ 192.352539] ---[ end trace 8afaed8976dc671e ]--- [ 192.365081] wlcore: Hardware recovery in progress. FW ver: Rev 6.3.10.0.133 [ 192.372924] wlcore: pc: 0x0, hint_sts: 0x00000020 count: 16 [ 192.379241] wlcore: down [ 192.382720] ieee80211 phy0: Hardware restart was requested [ 192.857391] wlcore: firmware booted (Rev 6.3.10.0.133) [ 197.907348] wlcore: ERROR Tx stuck (in FW) for 5000 ms. Starting recovery [ 197.914581] ------------[ cut here ]------------ [ 197.914581] WARNING: CPU: 1 PID: 6 at drivers/net/wireless/ti/wlcore/main.c:787 wl1271_op_cancel_hw_scan+0x838/0x83c [wlco) [ 197.914581] Modules linked in: btwilink st_drv wl12xx wlcore_sdio wlcore mac80211 cfg80211 bluetooth [ 197.914581] CPU: 1 PID: 6 Comm: kworker/u4:0 Tainted: G W 4.5.0-rc2-panda #1 [ 197.950073] Hardware name: Generic OMAP4 (Flattened Device Tree) [ 197.956451] Workqueue: phy0 wl12xx_tx_watchdog_work [wlcore] [ 197.962463] Backtrace: [ 197.965087] [<c0013f80>] (dump_backtrace) from [<c001417c>] (show_stack+0x18/0x1c) [ 197.973114] r7:bf0e6bf0 r6:00000313 r5:c0947cb4 r4:00000000 [ 197.979095] [<c0014164>] (show_stack) from [<c03a1908>] (dump_stack+0x98/0xd8) [ 197.986877] [<c03a1870>] (dump_stack) from [<c0034c30>] (warn_slowpath_common+0x88/0xb8) [ 197.995452] r5:00000009 r4:00000000 [ 197.996368] [<c0034ba8>] (warn_slowpath_common) from [<c0034d04>] (warn_slowpath_null+0x24/0x2c) [ 198.008605] r8:00000000 r7:ee8fcd40 r6:ee8fcd7c r5:ee8fcd48 r4:ee8fcd40 [ 198.012237] [<c0034ce0>] (warn_slowpath_null) from [<bf0e6bf0>] (wl1271_op_cancel_hw_scan+0x838/0x83c [wlcore]) [ 198.026458] [<bf0e6b90>] (wl1271_op_cancel_hw_scan [wlcore]) from [<bf0e6d18>] (wl12xx_tx_watchdog_work+0x124/0x128 [wlcor) [ 198.038482] r5:ee8fcd48 r4:ee8fdb08 [ 198.042327] [<bf0e6bf4>] (wl12xx_tx_watchdog_work [wlcore]) from [<c004a54c>] (process_one_work+0x128/0x400) [ 198.052764] r7:eeade700 r6:ef00b000 r5:ef02f900 r4:ee8fdb08 [ 198.052886] [<c004a424>] (process_one_work) from [<c004a878>] (worker_thread+0x54/0x58c) [ 198.067352] r10:ef02f900 r9:ef094020 r8:ef00b018 r7:c092a100 r6:00000088 r5:ef02f918 [ 198.074737] r4:ef00b000 [ 198.078338] [<c004a824>] (worker_thread) from [<c0050394>] (kthread+0xe4/0xfc) [ 198.086059] r10:00000000 r9:00000000 r8:00000000 r7:c004a824 r6:ef02f900 r5:ef0408c0 [ 198.086212] r4:00000000 [ 198.097106] [<c00502b0>] (kthread) from [<c000fb98>] (ret_from_fork+0x14/0x3c) [ 198.104766] r7:00000000 r6:00000000 r5:c00502b0 r4:ef0408c0 [ 198.110809] ---[ end trace 8afaed8976dc671f ]--- [ 198.121673] wlcore: Hardware recovery in progress. FW ver: Rev 6.3.10.0.133 [ 198.129486] wlcore: pc: 0x0, hint_sts: 0x00000020 count: 17 [ 198.135833] wlcore: down [ 198.138610] ieee80211 phy0: Hardware restart was requested [ 198.656066] wlcore: firmware booted (Rev 6.3.10.0.133) [ 203.767974] wlcore: ERROR Tx stuck (in FW) for 5000 ms. Starting recovery [ 203.768035] ------------[ cut here ]------------ [ 203.780090] WARNING: CPU: 1 PID: 6 at drivers/net/wireless/ti/wlcore/main.c:787 wl1271_op_cancel_hw_scan+0x838/0x83c [wlco) [ 203.792327] Modules linked in: btwilink st_drv wl12xx wlcore_sdio wlcore mac80211 cfg80211 bluetooth [ 203.802093] CPU: 1 PID: 6 Comm: kworker/u4:0 Tainted: G W 4.5.0-rc2-panda #1 [ 203.810760] Hardware name: Generic OMAP4 (Flattened Device Tree) [ 203.811096] Workqueue: phy0 wl12xx_tx_watchdog_work [wlcore] [ 203.822967] Backtrace: [ 203.822967] [<c0013f80>] (dump_backtrace) from [<c001417c>] (show_stack+0x18/0x1c) [ 203.833831] r7:bf0e6bf0 r6:00000313 r5:c0947cb4 r4:00000000 [ 203.834167] [<c0014164>] (show_stack) from [<c03a1908>] (dump_stack+0x98/0xd8) [ 203.847534] [<c03a1870>] (dump_stack) from [<c0034c30>] (warn_slowpath_common+0x88/0xb8) [ 203.856140] r5:00000009 r4:00000000 [ 203.858673] [<c0034ba8>] (warn_slowpath_common) from [<c0034d04>] (warn_slowpath_null+0x24/0x2c) [ 203.869293] r8:00000000 r7:ee8fcd40 r6:ee8fcd7c r5:ee8fcd48 r4:ee8fcd40 [ 203.876464] [<c0034ce0>] (warn_slowpath_null) from [<bf0e6bf0>] (wl1271_op_cancel_hw_scan+0x838/0x83c [wlcore]) [ 203.887176] [<bf0e6b90>] (wl1271_op_cancel_hw_scan [wlcore]) from [<bf0e6d18>] (wl12xx_tx_watchdog_work+0x124/0x128 [wlcor) [ 203.899169] r5:ee8fcd48 r4:ee8fdb08 [ 203.901702] [<bf0e6bf4>] (wl12xx_tx_watchdog_work [wlcore]) from [<c004a54c>] (process_one_work+0x128/0x400) [ 203.913452] r7:eeade700 r6:ef00b000 r5:ef02f900 r4:ee8fdb08 [ 203.913665] [<c004a424>] (process_one_work) from [<c004a878>] (worker_thread+0x54/0x58c) [ 203.928070] r10:ef02f900 r9:ef094020 r8:ef00b018 r7:c092a100 r6:00000088 r5:ef02f918 [ 203.930664] r4:ef00b000 [ 203.939117] [<c004a824>] (worker_thread) from [<c0050394>] (kthread+0xe4/0xfc) [ 203.939117] r10:00000000 r9:00000000 r8:00000000 r7:c004a824 r6:ef02f900 r5:ef0408c0 [ 203.955108] r4:00000000 [ 203.955108] [<c00502b0>] (kthread) from [<c000fb98>] (ret_from_fork+0x14/0x3c) [ 203.965454] r7:00000000 r6:00000000 r5:c00502b0 r4:ef0408c0 [ 203.970184] ---[ end trace 8afaed8976dc6720 ]--- [ 203.982360] wlcore: Hardware recovery in progress. FW ver: Rev 6.3.10.0.133 [ 203.990264] wlcore: pc: 0x0, hint_sts: 0x00000020 count: 18 [ 203.996490] wlcore: down [ 204.000335] ieee80211 phy0: Hardware restart was requested [ 204.494293] wlcore: firmware booted (Rev 6.3.10.0.133) [ 209.579589] wlcore: ERROR Tx stuck (in FW) for 5000 ms. Starting recovery [ 209.586791] ------------[ cut here ]------------ [ 209.591705] WARNING: CPU: 1 PID: 6 at drivers/net/wireless/ti/wlcore/main.c:787 wl1271_op_cancel_hw_scan+0x838/0x83c [wlco) [ 209.603912] Modules linked in: btwilink st_drv wl12xx wlcore_sdio wlcore mac80211 cfg80211 bluetooth [ 209.611694] CPU: 1 PID: 6 Comm: kworker/u4:0 Tainted: G W 4.5.0-rc2-panda #1 [ 209.622344] Hardware name: Generic OMAP4 (Flattened Device Tree) [ 209.622680] Workqueue: phy0 wl12xx_tx_watchdog_work [wlcore] [ 209.634552] Backtrace: [ 209.634552] [<c0013f80>] (dump_backtrace) from [<c001417c>] (show_stack+0x18/0x1c) [ 209.645385] r7:bf0e6bf0 r6:00000313 r5:c0947cb4 r4:00000000 [ 209.651214] [<c0014164>] (show_stack) from [<c03a1908>] (dump_stack+0x98/0xd8) [ 209.651214] [<c03a1870>] (dump_stack) from [<c0034c30>] (warn_slowpath_common+0x88/0xb8) [ 209.659118] r5:00000009 r4:00000000 [ 209.671508] [<c0034ba8>] (warn_slowpath_common) from [<c0034d04>] (warn_slowpath_null+0x24/0x2c) [ 209.680816] r8:00000000 r7:ee8fcd40 r6:ee8fcd7c r5:ee8fcd48 r4:ee8fcd40 [ 209.687957] [<c0034ce0>] (warn_slowpath_null) from [<bf0e6bf0>] (wl1271_op_cancel_hw_scan+0x838/0x83c [wlcore]) [ 209.698638] [<bf0e6b90>] (wl1271_op_cancel_hw_scan [wlcore]) from [<bf0e6d18>] (wl12xx_tx_watchdog_work+0x124/0x128 [wlcor) [ 209.699188] r5:ee8fcd48 r4:ee8fdb08 [ 209.713195] [<bf0e6bf4>] (wl12xx_tx_watchdog_work [wlcore]) from [<c004a54c>] (process_one_work+0x128/0x400) [ 209.724914] r7:eeade700 r6:ef00b000 r5:ef02f900 r4:ee8fdb08 [ 209.724914] [<c004a424>] (process_one_work) from [<c004a878>] (worker_thread+0x54/0x58c) [ 209.739532] r10:ef02f900 r9:ef094020 r8:ef00b018 r7:c092a100 r6:00000088 r5:ef02f918 [ 209.744873] r4:ef00b000 [ 209.750610] [<c004a824>] (worker_thread) from [<c0050394>] (kthread+0xe4/0xfc) [ 209.750640] r10:00000000 r9:00000000 r8:00000000 r7:c004a824 r6:ef02f900 r5:ef0408c0 [ 209.761596] r4:00000000 [ 209.761596] [<c00502b0>] (kthread) from [<c000fb98>] (ret_from_fork+0x14/0x3c) [ 209.776977] r7:00000000 r6:00000000 r5:c00502b0 r4:ef0408c0 [ 209.781951] ---[ end trace 8afaed8976dc6721 ]--- [ 209.793884] wlcore: Hardware recovery in progress. FW ver: Rev 6.3.10.0.133 [ 209.801727] wlcore: pc: 0x0, hint_sts: 0x00000020 count: 19 [ 209.807922] wlcore: down [ 209.810729] ieee80211 phy0: Hardware restart was requested [ 210.347412] wlcore: firmware booted (Rev 6.3.10.0.133) ^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: linux-4.5-rc1 TI pandboard-es wifi wlcore locks and reset @ 2016-02-02 4:34 ` Sebastian Reichel 0 siblings, 0 replies; 12+ messages in thread From: Sebastian Reichel @ 2016-02-02 4:34 UTC (permalink / raw) To: Ross Green; +Cc: linux-kernel, linux-omap, linux-wireless [-- Attachment #1: Type: text/plain, Size: 1385 bytes --] Hi, On Mon, Feb 01, 2016 at 11:38:38PM +1100, Ross Green wrote: > On Mon, Jan 25, 2016 at 11:47 PM, Ross Green <rgkernel@gmail.com> wrote: > > Just tried the new kernel release on faithful pandaboard es with the > > new 4.5-rc1 release. > > > > There is a problem with the wifi modules once the modules are loaded. > > Looks like the wifi firmware gets loaded put no response after that > > causing recovery action. > > > > the kernel 4.4 works quite happily with this board. > > > > Here is a dmesg dump in the attachment. > > > > Anyone have any ideas here? > > Just updated to the latest linux-4.5-rc2 and same result as rc1. > > The wireless module loads firmware and then stalls causing a reset of > the device and then continues to go through a stall and reset cycle. > > please find enclosed a copy of the dmesg output. > > Is there anyone else testing a pandaboard with linux-4.5-rc2? > > Just for completeness also tested the latest linux-4.4.1 kernel and > found no problems with the wireless modules. I can see the same problem with Nokia N950 (which uses spi connected wl1271). v4.4 + wl12xx spi DT patches from Uri Mashiach worked, v4.5 + the same patches does not work. I currently suspect 133b7326e960 or 3719c17e1816 to be the culprit. I have not yet verified it, though. Have you tried to bisect the problem? -- Sebastian [-- Attachment #2: signature.asc --] [-- Type: application/pgp-signature, Size: 819 bytes --] ^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: linux-4.5-rc1 TI pandboard-es wifi wlcore locks and reset @ 2016-02-02 4:34 ` Sebastian Reichel 0 siblings, 0 replies; 12+ messages in thread From: Sebastian Reichel @ 2016-02-02 4:34 UTC (permalink / raw) To: Ross Green Cc: linux-kernel-u79uwXL29TY76Z2rM5mHXA, linux-omap-u79uwXL29TY76Z2rM5mHXA, linux-wireless-u79uwXL29TY76Z2rM5mHXA [-- Attachment #1: Type: text/plain, Size: 1415 bytes --] Hi, On Mon, Feb 01, 2016 at 11:38:38PM +1100, Ross Green wrote: > On Mon, Jan 25, 2016 at 11:47 PM, Ross Green <rgkernel-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote: > > Just tried the new kernel release on faithful pandaboard es with the > > new 4.5-rc1 release. > > > > There is a problem with the wifi modules once the modules are loaded. > > Looks like the wifi firmware gets loaded put no response after that > > causing recovery action. > > > > the kernel 4.4 works quite happily with this board. > > > > Here is a dmesg dump in the attachment. > > > > Anyone have any ideas here? > > Just updated to the latest linux-4.5-rc2 and same result as rc1. > > The wireless module loads firmware and then stalls causing a reset of > the device and then continues to go through a stall and reset cycle. > > please find enclosed a copy of the dmesg output. > > Is there anyone else testing a pandaboard with linux-4.5-rc2? > > Just for completeness also tested the latest linux-4.4.1 kernel and > found no problems with the wireless modules. I can see the same problem with Nokia N950 (which uses spi connected wl1271). v4.4 + wl12xx spi DT patches from Uri Mashiach worked, v4.5 + the same patches does not work. I currently suspect 133b7326e960 or 3719c17e1816 to be the culprit. I have not yet verified it, though. Have you tried to bisect the problem? -- Sebastian [-- Attachment #2: signature.asc --] [-- Type: application/pgp-signature, Size: 819 bytes --] ^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: linux-4.5-rc1 TI pandboard-es wifi wlcore locks and reset 2016-02-02 4:34 ` Sebastian Reichel (?) @ 2016-02-02 5:41 ` Ross Green 2016-02-02 16:05 ` wl12xx regression on 4.5 (was: Re: linux-4.5-rc1 TI pandboard-es wifi wlcore locks and reset) Sebastian Reichel -1 siblings, 1 reply; 12+ messages in thread From: Ross Green @ 2016-02-02 5:41 UTC (permalink / raw) To: Sebastian Reichel; +Cc: linux-kernel, linux-omap, linux-wireless I have not tried a bisect yet, but I can confirm 4.4 and 4.4.1 work. 4.5-rc1 and 4.5-rc2 don't work. It appears the tx to device times out and then just goes into reset of the device to try and recover. A tx to device seems not to work. although somehow firmware has been loaded to the device. So some types of tx might work. Strange! There were quite a few omap and omap4 plus patches that have come along recently. so the culprit is in there somewhere. These machines have been rock solid for quite some time. If I get time, this evening, I'll see if I can give a bisect a try. Regards, Ross Green On Tue, Feb 2, 2016 at 3:34 PM, Sebastian Reichel <sre@kernel.org> wrote: > Hi, > > On Mon, Feb 01, 2016 at 11:38:38PM +1100, Ross Green wrote: >> On Mon, Jan 25, 2016 at 11:47 PM, Ross Green <rgkernel@gmail.com> wrote: >> > Just tried the new kernel release on faithful pandaboard es with the >> > new 4.5-rc1 release. >> > >> > There is a problem with the wifi modules once the modules are loaded. >> > Looks like the wifi firmware gets loaded put no response after that >> > causing recovery action. >> > >> > the kernel 4.4 works quite happily with this board. >> > >> > Here is a dmesg dump in the attachment. >> > >> > Anyone have any ideas here? >> >> Just updated to the latest linux-4.5-rc2 and same result as rc1. >> >> The wireless module loads firmware and then stalls causing a reset of >> the device and then continues to go through a stall and reset cycle. >> >> please find enclosed a copy of the dmesg output. >> >> Is there anyone else testing a pandaboard with linux-4.5-rc2? >> >> Just for completeness also tested the latest linux-4.4.1 kernel and >> found no problems with the wireless modules. > > I can see the same problem with Nokia N950 (which uses spi connected > wl1271). v4.4 + wl12xx spi DT patches from Uri Mashiach worked, v4.5 > + the same patches does not work. I currently suspect 133b7326e960 > or 3719c17e1816 to be the culprit. I have not yet verified it, though. > > Have you tried to bisect the problem? > > -- Sebastian ^ permalink raw reply [flat|nested] 12+ messages in thread
* wl12xx regression on 4.5 (was: Re: linux-4.5-rc1 TI pandboard-es wifi wlcore locks and reset) 2016-02-02 5:41 ` Ross Green @ 2016-02-02 16:05 ` Sebastian Reichel 2016-02-03 6:25 ` Ross Green 2016-02-07 22:05 ` Emil Goode 0 siblings, 2 replies; 12+ messages in thread From: Sebastian Reichel @ 2016-02-02 16:05 UTC (permalink / raw) To: Ross Green, Shahar Patury Cc: linux-kernel, linux-omap, linux-wireless, Guy Mishol, Kalle Valo [-- Attachment #1: Type: text/plain, Size: 1129 bytes --] Hi Ross, Please don't top-post on kernel mailinglists. Use either inline style or bottom posting. On Tue, Feb 02, 2016 at 04:41:13PM +1100, Ross Green wrote: > On Tue, Feb 2, 2016 at 3:34 PM, Sebastian Reichel <sre@kernel.org> wrote: > > On Mon, Feb 01, 2016 at 11:38:38PM +1100, Ross Green wrote: > >> On Mon, Jan 25, 2016 at 11:47 PM, Ross Green <rgkernel@gmail.com> wrote: > >> > Just tried the new kernel release on faithful pandaboard es with the > >> > new 4.5-rc1 release. > >> > > >> > There is a problem with the wifi modules once the modules are loaded. > >> > Looks like the wifi firmware gets loaded put no response after that > >> > causing recovery action. > >> > > >> > the kernel 4.4 works quite happily with this board. > >> > > >> > Here is a dmesg dump in the attachment. > >> > > >> > Anyone have any ideas here? > > [...] > > If I get time, this evening, I'll see if I can give a bisect a try. On N950 [wl1271 via SPI, using extra patches to init from DT] I get wifi working again on 4.5-rc1 with 3719c17e1816 ("wlcore/wl18xx: fw logger over sdio") reverted. -- Sebastian [-- Attachment #2: signature.asc --] [-- Type: application/pgp-signature, Size: 819 bytes --] ^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: wl12xx regression on 4.5 (was: Re: linux-4.5-rc1 TI pandboard-es wifi wlcore locks and reset) 2016-02-02 16:05 ` wl12xx regression on 4.5 (was: Re: linux-4.5-rc1 TI pandboard-es wifi wlcore locks and reset) Sebastian Reichel @ 2016-02-03 6:25 ` Ross Green 2016-02-07 22:05 ` Emil Goode 1 sibling, 0 replies; 12+ messages in thread From: Ross Green @ 2016-02-03 6:25 UTC (permalink / raw) To: Sebastian Reichel Cc: Shahar Patury, linux-kernel, linux-omap, linux-wireless, Guy Mishol, Kalle Valo On Wed, Feb 3, 2016 at 3:05 AM, Sebastian Reichel <sre@kernel.org> wrote: > Hi Ross, > > Please don't top-post on kernel mailinglists. Use either inline > style or bottom posting. > > On Tue, Feb 02, 2016 at 04:41:13PM +1100, Ross Green wrote: >> On Tue, Feb 2, 2016 at 3:34 PM, Sebastian Reichel <sre@kernel.org> wrote: >> > On Mon, Feb 01, 2016 at 11:38:38PM +1100, Ross Green wrote: >> >> On Mon, Jan 25, 2016 at 11:47 PM, Ross Green <rgkernel@gmail.com> wrote: >> >> > Just tried the new kernel release on faithful pandaboard es with the >> >> > new 4.5-rc1 release. >> >> > >> >> > There is a problem with the wifi modules once the modules are loaded. >> >> > Looks like the wifi firmware gets loaded put no response after that >> >> > causing recovery action. >> >> > >> >> > the kernel 4.4 works quite happily with this board. >> >> > >> >> > Here is a dmesg dump in the attachment. >> >> > >> >> > Anyone have any ideas here? >> >> [...] >> >> If I get time, this evening, I'll see if I can give a bisect a try. > > On N950 [wl1271 via SPI, using extra patches to init from DT] I get wifi > working again on 4.5-rc1 with 3719c17e1816 ("wlcore/wl18xx: fw logger > over sdio") reverted. > > -- Sebastian For the pandaboard using for 4.5 CONFIG_WLAN_VENDOR_TI=y CONFIG_WL12XX=m CONFIG_WLCORE=m CONFIG_WLCORE_SDIO=m CONFIG_WILINK_PLATFORM_DATA=y so I suspect it is something to do with modifications to wlcore, wlcore_sdio, or wl12xx that have been applied. Given there are similar problems with the SPI interface then it is more likely to be problems in the wlcore modifications. Shahar have these been tested on a pandaboard omap4 setup? Regards, Ross ^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: wl12xx regression on 4.5 (was: Re: linux-4.5-rc1 TI pandboard-es wifi wlcore locks and reset) 2016-02-02 16:05 ` wl12xx regression on 4.5 (was: Re: linux-4.5-rc1 TI pandboard-es wifi wlcore locks and reset) Sebastian Reichel @ 2016-02-07 22:05 ` Emil Goode 2016-02-07 22:05 ` Emil Goode 1 sibling, 0 replies; 12+ messages in thread From: Emil Goode @ 2016-02-07 22:05 UTC (permalink / raw) To: Sebastian Reichel Cc: Ross Green, Shahar Patury, linux-kernel, linux-omap, linux-wireless, Guy Mishol, Kalle Valo Hello, On Tue, Feb 02, 2016 at 05:05:38PM +0100, Sebastian Reichel wrote: > On Tue, Feb 02, 2016 at 04:41:13PM +1100, Ross Green wrote: > > On Tue, Feb 2, 2016 at 3:34 PM, Sebastian Reichel <sre@kernel.org> wrote: > > > On Mon, Feb 01, 2016 at 11:38:38PM +1100, Ross Green wrote: > > >> On Mon, Jan 25, 2016 at 11:47 PM, Ross Green <rgkernel@gmail.com> wrote: > > >> > Just tried the new kernel release on faithful pandaboard es with the > > >> > new 4.5-rc1 release. > > >> > > > >> > There is a problem with the wifi modules once the modules are loaded. > > >> > Looks like the wifi firmware gets loaded put no response after that > > >> > causing recovery action. > > >> > > > >> > the kernel 4.4 works quite happily with this board. > > >> > > > >> > Here is a dmesg dump in the attachment. > > >> > > > >> > Anyone have any ideas here? > > > > [...] > > > > If I get time, this evening, I'll see if I can give a bisect a try. > > On N950 [wl1271 via SPI, using extra patches to init from DT] I get wifi > working again on 4.5-rc1 with 3719c17e1816 ("wlcore/wl18xx: fw logger > over sdio") reverted. Reverting the changes in wlcore_set_partition() as below seem to help. Best regards, Emil Goode 8<-------- --- a/drivers/net/wireless/ti/wlcore/io.c +++ b/drivers/net/wireless/ti/wlcore/io.c @@ -175,14 +175,15 @@ int wlcore_set_partition(struct wl1271 *wl, if (ret < 0) goto out; + /* + * We don't need the size of the last partition, as it is + * automatically calculated based on the total memory size and + * the sizes of the previous partitions. + */ ret = wlcore_raw_write32(wl, HW_PART3_START_ADDR, p->mem3.start); if (ret < 0) goto out; - ret = wlcore_raw_write32(wl, HW_PART3_SIZE_ADDR, p->mem3.size); - if (ret < 0) - goto out; - out: return ret; } diff --git a/drivers/net/wireless/ti/wlcore/io.h b/drivers/net/wireless/ti/wlcore/io.h index 6c257b5..10cf374 100644 --- a/drivers/net/wireless/ti/wlcore/io.h +++ b/drivers/net/wireless/ti/wlcore/io.h @@ -36,8 +36,8 @@ #define HW_PART1_START_ADDR (HW_PARTITION_REGISTERS_ADDR + 12) #define HW_PART2_SIZE_ADDR (HW_PARTITION_REGISTERS_ADDR + 16) #define HW_PART2_START_ADDR (HW_PARTITION_REGISTERS_ADDR + 20) -#define HW_PART3_SIZE_ADDR (HW_PARTITION_REGISTERS_ADDR + 24) -#define HW_PART3_START_ADDR (HW_PARTITION_REGISTERS_ADDR + 28) +#define HW_PART3_START_ADDR (HW_PARTITION_REGISTERS_ADDR + 24) + #define HW_ACCESS_REGISTER_SIZE 4 #define HW_ACCESS_PRAM_MAX_RANGE 0x3c000 ^ permalink raw reply related [flat|nested] 12+ messages in thread
* Re: wl12xx regression on 4.5 (was: Re: linux-4.5-rc1 TI pandboard-es wifi wlcore locks and reset) @ 2016-02-07 22:05 ` Emil Goode 0 siblings, 0 replies; 12+ messages in thread From: Emil Goode @ 2016-02-07 22:05 UTC (permalink / raw) To: Sebastian Reichel Cc: Ross Green, Shahar Patury, linux-kernel-u79uwXL29TY76Z2rM5mHXA, linux-omap-u79uwXL29TY76Z2rM5mHXA, linux-wireless-u79uwXL29TY76Z2rM5mHXA, Guy Mishol, Kalle Valo Hello, On Tue, Feb 02, 2016 at 05:05:38PM +0100, Sebastian Reichel wrote: > On Tue, Feb 02, 2016 at 04:41:13PM +1100, Ross Green wrote: > > On Tue, Feb 2, 2016 at 3:34 PM, Sebastian Reichel <sre-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org> wrote: > > > On Mon, Feb 01, 2016 at 11:38:38PM +1100, Ross Green wrote: > > >> On Mon, Jan 25, 2016 at 11:47 PM, Ross Green <rgkernel-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote: > > >> > Just tried the new kernel release on faithful pandaboard es with the > > >> > new 4.5-rc1 release. > > >> > > > >> > There is a problem with the wifi modules once the modules are loaded. > > >> > Looks like the wifi firmware gets loaded put no response after that > > >> > causing recovery action. > > >> > > > >> > the kernel 4.4 works quite happily with this board. > > >> > > > >> > Here is a dmesg dump in the attachment. > > >> > > > >> > Anyone have any ideas here? > > > > [...] > > > > If I get time, this evening, I'll see if I can give a bisect a try. > > On N950 [wl1271 via SPI, using extra patches to init from DT] I get wifi > working again on 4.5-rc1 with 3719c17e1816 ("wlcore/wl18xx: fw logger > over sdio") reverted. Reverting the changes in wlcore_set_partition() as below seem to help. Best regards, Emil Goode 8<-------- --- a/drivers/net/wireless/ti/wlcore/io.c +++ b/drivers/net/wireless/ti/wlcore/io.c @@ -175,14 +175,15 @@ int wlcore_set_partition(struct wl1271 *wl, if (ret < 0) goto out; + /* + * We don't need the size of the last partition, as it is + * automatically calculated based on the total memory size and + * the sizes of the previous partitions. + */ ret = wlcore_raw_write32(wl, HW_PART3_START_ADDR, p->mem3.start); if (ret < 0) goto out; - ret = wlcore_raw_write32(wl, HW_PART3_SIZE_ADDR, p->mem3.size); - if (ret < 0) - goto out; ^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: wl12xx regression on 4.5 (was: Re: linux-4.5-rc1 TI pandboard-es wifi wlcore locks and reset) 2016-02-07 22:05 ` Emil Goode (?) @ 2016-02-08 8:26 ` Ross Green 2016-02-08 22:59 ` Emil Goode -1 siblings, 1 reply; 12+ messages in thread From: Ross Green @ 2016-02-08 8:26 UTC (permalink / raw) To: Emil Goode Cc: Sebastian Reichel, Shahar Patury, linux-kernel, linux-omap, linux-wireless, Guy Mishol, Kalle Valo On Mon, Feb 8, 2016 at 9:05 AM, Emil Goode <emil.fsw@goode.io> wrote: > Hello, > > On Tue, Feb 02, 2016 at 05:05:38PM +0100, Sebastian Reichel wrote: >> On Tue, Feb 02, 2016 at 04:41:13PM +1100, Ross Green wrote: >> > On Tue, Feb 2, 2016 at 3:34 PM, Sebastian Reichel <sre@kernel.org> wrote: >> > > On Mon, Feb 01, 2016 at 11:38:38PM +1100, Ross Green wrote: >> > >> On Mon, Jan 25, 2016 at 11:47 PM, Ross Green <rgkernel@gmail.com> wrote: >> > >> > Just tried the new kernel release on faithful pandaboard es with the >> > >> > new 4.5-rc1 release. >> > >> > >> > >> > There is a problem with the wifi modules once the modules are loaded. >> > >> > Looks like the wifi firmware gets loaded put no response after that >> > >> > causing recovery action. >> > >> > >> > >> > the kernel 4.4 works quite happily with this board. >> > >> > >> > >> > Here is a dmesg dump in the attachment. >> > >> > >> > >> > Anyone have any ideas here? >> > >> > [...] >> > >> > If I get time, this evening, I'll see if I can give a bisect a try. >> >> On N950 [wl1271 via SPI, using extra patches to init from DT] I get wifi >> working again on 4.5-rc1 with 3719c17e1816 ("wlcore/wl18xx: fw logger >> over sdio") reverted. > > Reverting the changes in wlcore_set_partition() as below seem to help. > > Best regards, > > Emil Goode > > 8<-------- > > --- a/drivers/net/wireless/ti/wlcore/io.c > +++ b/drivers/net/wireless/ti/wlcore/io.c > @@ -175,14 +175,15 @@ int wlcore_set_partition(struct wl1271 *wl, > if (ret < 0) > goto out; > > + /* > + * We don't need the size of the last partition, as it is > + * automatically calculated based on the total memory size and > + * the sizes of the previous partitions. > + */ > ret = wlcore_raw_write32(wl, HW_PART3_START_ADDR, p->mem3.start); > if (ret < 0) > goto out; > > - ret = wlcore_raw_write32(wl, HW_PART3_SIZE_ADDR, p->mem3.size); > - if (ret < 0) > - goto out; > - > out: > return ret; > } > diff --git a/drivers/net/wireless/ti/wlcore/io.h b/drivers/net/wireless/ti/wlcore/io.h > index 6c257b5..10cf374 100644 > --- a/drivers/net/wireless/ti/wlcore/io.h > +++ b/drivers/net/wireless/ti/wlcore/io.h > @@ -36,8 +36,8 @@ > #define HW_PART1_START_ADDR (HW_PARTITION_REGISTERS_ADDR + 12) > #define HW_PART2_SIZE_ADDR (HW_PARTITION_REGISTERS_ADDR + 16) > #define HW_PART2_START_ADDR (HW_PARTITION_REGISTERS_ADDR + 20) > -#define HW_PART3_SIZE_ADDR (HW_PARTITION_REGISTERS_ADDR + 24) > -#define HW_PART3_START_ADDR (HW_PARTITION_REGISTERS_ADDR + 28) > +#define HW_PART3_START_ADDR (HW_PARTITION_REGISTERS_ADDR + 24) > + > #define HW_ACCESS_REGISTER_SIZE 4 > > #define HW_ACCESS_PRAM_MAX_RANGE 0x3c000 > Thanks Emil, Just tested linux-4.5-rc3 with the above patch and confirm everything works as expected. So it would be good if this patch can find its way into linux-4.5-rc4. here is a portion of the dmesg: # dmesg [ 0.000000] Booting Linux on physical CPU 0x0 [ 0.000000] Linux version 4.5.0-rc3-panda (rfg@red.dwarf) (gcc version 5.3.0 (Buildroot 2016.02-git-00183-g1682aee) ) #1 S6 [ 0.000000] CPU: ARMv7 Processor [412fc09a] revision 10 (ARMv7), cr=10c5387d [ 0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache [ 0.000000] Machine model: TI OMAP4 PandaBoard-ES [ 0.000000] Memory policy: Data cache writealloc [ 0.000000] OMAP4: Map 0xbfe00000 to fe600000 for dram barrier [ 0.000000] On node 0 totalpages: 261632 ... ...[ 39.164764] wlcore: loaded [ 52.577209] wlcore: firmware booted (Rev 6.3.10.0.133) [ 56.101531] wlan0: authenticate with 90:f6:52:81:ee:70 [ 56.138732] wlan0: send auth to 90:f6:52:81:ee:70 (try 1/3) [ 56.146728] wlan0: authenticated [ 56.162078] wlan0: associate with 90:f6:52:81:ee:70 (try 1/3) [ 56.172821] wlan0: RX AssocResp from 90:f6:52:81:ee:70 (capab=0x431 status=0 aid=1) [ 56.188201] wlan0: associated [ 56.244812] wlcore: Association completed. So all is happy with the wlcore code with this patch. Now I can continue with the rest of the testing ;-) Regards, Ross Green ^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: wl12xx regression on 4.5 (was: Re: linux-4.5-rc1 TI pandboard-es wifi wlcore locks and reset) @ 2016-02-08 22:59 ` Emil Goode 0 siblings, 0 replies; 12+ messages in thread From: Emil Goode @ 2016-02-08 22:59 UTC (permalink / raw) To: Ross Green Cc: Sebastian Reichel, Shahar Patury, linux-kernel, linux-omap, linux-wireless, Guy Mishol, Kalle Valo Hello Ross, On Mon, Feb 08, 2016 at 07:26:34PM +1100, Ross Green wrote: > On Mon, Feb 8, 2016 at 9:05 AM, Emil Goode <emil.fsw@goode.io> wrote: > > Hello, > > > > On Tue, Feb 02, 2016 at 05:05:38PM +0100, Sebastian Reichel wrote: > >> On Tue, Feb 02, 2016 at 04:41:13PM +1100, Ross Green wrote: > >> > On Tue, Feb 2, 2016 at 3:34 PM, Sebastian Reichel <sre@kernel.org> wrote: > >> > > On Mon, Feb 01, 2016 at 11:38:38PM +1100, Ross Green wrote: > >> > >> On Mon, Jan 25, 2016 at 11:47 PM, Ross Green <rgkernel@gmail.com> wrote: > >> > >> > Just tried the new kernel release on faithful pandaboard es with the > >> > >> > new 4.5-rc1 release. > >> > >> > > >> > >> > There is a problem with the wifi modules once the modules are loaded. > >> > >> > Looks like the wifi firmware gets loaded put no response after that > >> > >> > causing recovery action. > >> > >> > > >> > >> > the kernel 4.4 works quite happily with this board. > >> > >> > > >> > >> > Here is a dmesg dump in the attachment. > >> > >> > > >> > >> > Anyone have any ideas here? > >> > > >> > [...] > >> > > >> > If I get time, this evening, I'll see if I can give a bisect a try. > >> > >> On N950 [wl1271 via SPI, using extra patches to init from DT] I get wifi > >> working again on 4.5-rc1 with 3719c17e1816 ("wlcore/wl18xx: fw logger > >> over sdio") reverted. > > > > Reverting the changes in wlcore_set_partition() as below seem to help. > > > > Best regards, > > > > Emil Goode > > > > 8<-------- > > > > --- a/drivers/net/wireless/ti/wlcore/io.c > > +++ b/drivers/net/wireless/ti/wlcore/io.c > > @@ -175,14 +175,15 @@ int wlcore_set_partition(struct wl1271 *wl, > > if (ret < 0) > > goto out; > > > > + /* > > + * We don't need the size of the last partition, as it is > > + * automatically calculated based on the total memory size and > > + * the sizes of the previous partitions. > > + */ > > ret = wlcore_raw_write32(wl, HW_PART3_START_ADDR, p->mem3.start); > > if (ret < 0) > > goto out; > > > > - ret = wlcore_raw_write32(wl, HW_PART3_SIZE_ADDR, p->mem3.size); > > - if (ret < 0) > > - goto out; > > - > > out: > > return ret; > > } > > diff --git a/drivers/net/wireless/ti/wlcore/io.h b/drivers/net/wireless/ti/wlcore/io.h > > index 6c257b5..10cf374 100644 > > --- a/drivers/net/wireless/ti/wlcore/io.h > > +++ b/drivers/net/wireless/ti/wlcore/io.h > > @@ -36,8 +36,8 @@ > > #define HW_PART1_START_ADDR (HW_PARTITION_REGISTERS_ADDR + 12) > > #define HW_PART2_SIZE_ADDR (HW_PARTITION_REGISTERS_ADDR + 16) > > #define HW_PART2_START_ADDR (HW_PARTITION_REGISTERS_ADDR + 20) > > -#define HW_PART3_SIZE_ADDR (HW_PARTITION_REGISTERS_ADDR + 24) > > -#define HW_PART3_START_ADDR (HW_PARTITION_REGISTERS_ADDR + 28) > > +#define HW_PART3_START_ADDR (HW_PARTITION_REGISTERS_ADDR + 24) > > + > > #define HW_ACCESS_REGISTER_SIZE 4 > > > > #define HW_ACCESS_PRAM_MAX_RANGE 0x3c000 > > > > Thanks Emil, > > Just tested linux-4.5-rc3 with the above patch and confirm everything > works as expected. So it would be good if this patch can find its way > into linux-4.5-rc4. > > So all is happy with the wlcore code with this patch. > Now I can continue with the rest of the testing ;-) Thank you for testing! I'm not familiar with this code so it would be good to get a comment from ti developers, if not I will send this fix. Best regards, Emil Goode ^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: wl12xx regression on 4.5 (was: Re: linux-4.5-rc1 TI pandboard-es wifi wlcore locks and reset) @ 2016-02-08 22:59 ` Emil Goode 0 siblings, 0 replies; 12+ messages in thread From: Emil Goode @ 2016-02-08 22:59 UTC (permalink / raw) To: Ross Green Cc: Sebastian Reichel, Shahar Patury, linux-kernel-u79uwXL29TY76Z2rM5mHXA, linux-omap-u79uwXL29TY76Z2rM5mHXA, linux-wireless-u79uwXL29TY76Z2rM5mHXA, Guy Mishol, Kalle Valo Hello Ross, On Mon, Feb 08, 2016 at 07:26:34PM +1100, Ross Green wrote: > On Mon, Feb 8, 2016 at 9:05 AM, Emil Goode <emil.fsw-k26UujxPaJg@public.gmane.org> wrote: > > Hello, > > > > On Tue, Feb 02, 2016 at 05:05:38PM +0100, Sebastian Reichel wrote: > >> On Tue, Feb 02, 2016 at 04:41:13PM +1100, Ross Green wrote: > >> > On Tue, Feb 2, 2016 at 3:34 PM, Sebastian Reichel <sre-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org> wrote: > >> > > On Mon, Feb 01, 2016 at 11:38:38PM +1100, Ross Green wrote: > >> > >> On Mon, Jan 25, 2016 at 11:47 PM, Ross Green <rgkernel-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote: > >> > >> > Just tried the new kernel release on faithful pandaboard es with the > >> > >> > new 4.5-rc1 release. > >> > >> > > >> > >> > There is a problem with the wifi modules once the modules are loaded. > >> > >> > Looks like the wifi firmware gets loaded put no response after that > >> > >> > causing recovery action. > >> > >> > > >> > >> > the kernel 4.4 works quite happily with this board. > >> > >> > > >> > >> > Here is a dmesg dump in the attachment. > >> > >> > > >> > >> > Anyone have any ideas here? > >> > > >> > [...] > >> > > >> > If I get time, this evening, I'll see if I can give a bisect a try. > >> > >> On N950 [wl1271 via SPI, using extra patches to init from DT] I get wifi > >> working again on 4.5-rc1 with 3719c17e1816 ("wlcore/wl18xx: fw logger > >> over sdio") reverted. > > > > Reverting the changes in wlcore_set_partition() as below seem to help. > > > > Best regards, > > > > Emil Goode > > > > 8<-------- > > > > --- a/drivers/net/wireless/ti/wlcore/io.c > > +++ b/drivers/net/wireless/ti/wlcore/io.c > > @@ -175,14 +175,15 @@ int wlcore_set_partition(struct wl1271 *wl, > > if (ret < 0) > > goto out; > > > > + /* > > + * We don't need the size of the last partition, as it is > > + * automatically calculated based on the total memory size and > > + * the sizes of the previous partitions. > > + */ > > ret = wlcore_raw_write32(wl, HW_PART3_START_ADDR, p->mem3.start); > > if (ret < 0) > > goto out; > > > > - ret = wlcore_raw_write32(wl, HW_PART3_SIZE_ADDR, p->mem3.size); > > - if (ret < 0) > > - goto out; > > - > > out: > > return ret; > > } > > diff --git a/drivers/net/wireless/ti/wlcore/io.h b/drivers/net/wireless/ti/wlcore/io.h > > index 6c257b5..10cf374 100644 > > --- a/drivers/net/wireless/ti/wlcore/io.h > > +++ b/drivers/net/wireless/ti/wlcore/io.h > > @@ -36,8 +36,8 @@ > > #define HW_PART1_START_ADDR (HW_PARTITION_REGISTERS_ADDR + 12) > > #define HW_PART2_SIZE_ADDR (HW_PARTITION_REGISTERS_ADDR + 16) > > #define HW_PART2_START_ADDR (HW_PARTITION_REGISTERS_ADDR + 20) > > -#define HW_PART3_SIZE_ADDR (HW_PARTITION_REGISTERS_ADDR + 24) > > -#define HW_PART3_START_ADDR (HW_PARTITION_REGISTERS_ADDR + 28) > > +#define HW_PART3_START_ADDR (HW_PARTITION_REGISTERS_ADDR + 24) > > + > > #define HW_ACCESS_REGISTER_SIZE 4 > > > > #define HW_ACCESS_PRAM_MAX_RANGE 0x3c000 > > > > Thanks Emil, > > Just tested linux-4.5-rc3 with the above patch and confirm everything > works as expected. So it would be good if this patch can find its way > into linux-4.5-rc4. > > So all is happy with the wlcore code with this patch. > Now I can continue with the rest of the testing ;-) Thank you for testing! I'm not familiar with this code so it would be good to get a comment from ti developers, if not I will send this fix. Best regards, Emil Goode -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org More majordomo info at http://vger.kernel.org/majordomo-info.html ^ permalink raw reply [flat|nested] 12+ messages in thread
end of thread, other threads:[~2016-02-08 22:59 UTC | newest] Thread overview: 12+ messages (download: mbox.gz / follow: Atom feed) -- links below jump to the message on this page -- 2016-01-25 12:47 linux-4.5-rc1 TI pandboard-es wifi wlcore locks and reset Ross Green 2016-02-01 12:38 ` Ross Green 2016-02-02 4:34 ` Sebastian Reichel 2016-02-02 4:34 ` Sebastian Reichel 2016-02-02 5:41 ` Ross Green 2016-02-02 16:05 ` wl12xx regression on 4.5 (was: Re: linux-4.5-rc1 TI pandboard-es wifi wlcore locks and reset) Sebastian Reichel 2016-02-03 6:25 ` Ross Green 2016-02-07 22:05 ` Emil Goode 2016-02-07 22:05 ` Emil Goode 2016-02-08 8:26 ` Ross Green 2016-02-08 22:59 ` Emil Goode 2016-02-08 22:59 ` Emil Goode
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.