Modify

Opened 7 years ago

Closed 7 years ago

#8584 closed defect (duplicate)

stuck trace on .../ath/ath9k/recv.c:535 on TP-LINK TL-WR741ND

Reported by: kofec Owned by: nbd
Priority: low Milestone: Backfire 10.03.1
Component: packages Version: Backfire 10.03.1 RC4
Keywords: Cc:

Description

Hi,
I had stuck trace. Maybe this will be helpful for someone.

Linux version 2.6.32.27 (cezary@eko.one.pl) (gcc version 4.3.3 (GCC) ) #1 Wed Dec 29 21:28:43 CET 2010
prom: fw_arg0=00000007, fw_arg1=a1f87fb0, fw_arg2=a1f88460, fw_arg3=00000004
MyLoader: sysp=00000000, boardp=00000000, parts=ffffffff
bootconsole [early0] enabled
CPU revision is: 00019374 (MIPS 24Kc)
Atheros AR7240 rev 2, CPU:350.000 MHz, AHB:175.000 MHz, DDR:350.000 MHz
Determined physical RAM map:
 memory: 02000000 @ 00000000 (usable)
Initrd not found or empty - disabling initrd
Zone PFN ranges:
  Normal   0x00000000 -> 0x00002000
Movable zone start PFN for each node
early_node_map[1] active PFN ranges
    0: 0x00000000 -> 0x00002000
On node 0 totalpages: 8192
free_area_init_node: node 0, pgdat 802c6000, node_mem_map 81000000
  Normal zone: 64 pages used for memmap
  Normal zone: 0 pages reserved
  Normal zone: 8128 pages, LIFO batch:0
Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 8128
Kernel command line: rootfstype=squashfs,yaffs,jffs2 noinitrd console=ttyS0,115200 board=TL-WR741ND
PID hash table entries: 128 (order: -3, 512 bytes)
Dentry cache hash table entries: 4096 (order: 2, 16384 bytes)
Inode-cache hash table entries: 2048 (order: 1, 8192 bytes)
Primary instruction cache 64kB, VIPT, 4-way, linesize 32 bytes.
Primary data cache 32kB, 4-way, VIPT, cache aliases, linesize 32 bytes
Writing ErrCtl register=00000000
Readback ErrCtl register=00000000
Memory: 29356k/32768k available (2068k kernel code, 3412k reserved, 389k data, 152k init, 0k highmem)
SLUB: Genslabs=7, HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
Hierarchical RCU implementation.
NR_IRQS:56
Calibrating delay loop... 232.65 BogoMIPS (lpj=1163264)
Mount-cache hash table entries: 512
NET: Registered protocol family 16
MIPS: machine is TP-LINK TL-WR741ND
registering PCI controller with io_map_base unset
bio: create slab <bio-0> at 0
PCI: fixup device 0000:00:00.0
pci 0000:00:00.0: reg 10 64bit mmio: [0x000000-0x00ffff]
pci 0000:00:00.0: supports D1
pci 0000:00:00.0: PME# supported from D0 D1 D3hot
pci 0000:00:00.0: PME# disabled
PCI: mapping irq 48 to pin1@0000:00:00.0
Switching to clocksource MIPS
NET: Registered protocol family 2
IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
TCP established hash table entries: 1024 (order: 1, 8192 bytes)
TCP bind hash table entries: 1024 (order: 0, 4096 bytes)
TCP: Hash tables configured (established 1024 bind 1024)
TCP reno registered
NET: Registered protocol family 1
squashfs: version 4.0 (2009/01/31) Phillip Lougher
Registering mini_fo version $Id$
JFFS2 version 2.2. (NAND) (SUMMARY)  © 2001-2006 Red Hat, Inc.
yaffs Dec 29 2010 21:25:19 Installing. 
msgmni has been set to 57
io scheduler noop registered
io scheduler deadline registered (default)
Serial: 8250/16550 driver, 1 ports, IRQ sharing disabled
serial8250.0: ttyS0 at MMIO 0x18020000 (irq = 11) is a 16550A
console [ttyS0] enabled, bootconsole disabled
Atheros AR71xx SPI Controller driver version 0.2.4
m25p80 spi0.0: s25sl032a (4096 Kbytes)
spi0.0: searching for MyLoader partition table at offset 0x10000
spi0.0: searching for MyLoader partition table at offset 0x20000
spi0.0: searching for MyLoader partition table at offset 0x30000
spi0.0: searching for MyLoader partition table at offset 0x40000
spi0.0: no MyLoader partition table found
Searching for RedBoot partition table in spi0.0 at offset 0x3e0000
Searching for RedBoot partition table in spi0.0 at offset 0x3f0000
No RedBoot partition table detected in spi0.0
spi0.0: no WRT160NL signature found
Creating 5 MTD partitions on "spi0.0":
0x000000000000-0x000000020000 : "u-boot"
0x000000020000-0x000000160000 : "kernel"
0x000000160000-0x0000003f0000 : "rootfs"
mtd: partition "rootfs" set to be root filesystem
mtd: partition "rootfs_data" created automatically, ofs=2D0000, len=120000 
0x0000002d0000-0x0000003f0000 : "rootfs_data"
0x0000003f0000-0x000000400000 : "art"
0x000000020000-0x0000003f0000 : "firmware"
ag71xx_mdio: probed
eth0: Atheros AG71xx at 0xba000000, irq 5
eth0: Found an AR7240 built-in switch
eth1: Atheros AG71xx at 0xb9000000, irq 4
eth1: using fixed link parameters
Atheros AR71xx hardware watchdog driver version 0.1.0
ar71xx-wdt: timeout=15 secs (max=24)
TCP westwood registered
NET: Registered protocol family 17
802.1Q VLAN Support v1.8 Ben Greear <greearb@candelatech.com>
All bugs added by David S. Miller <davem@redhat.com>
VFS: Mounted root (squashfs filesystem) readonly on device 31:2.
Freeing unused kernel memory: 152k freed
Please be patient, while OpenWrt loads ...
input: gpio-buttons as /devices/platform/gpio-buttons/input/input0
Button Hotplug driver version 0.3.1
eth0: link up (1000Mbps/Full duplex)
Registered led device: tl-wr741nd:green:system
Registered led device: tl-wr741nd:green:qss
mini_fo: using base directory: /
mini_fo: using storage directory: /overlay
eth0: link down
eth0: link up (1000Mbps/Full duplex)
device eth0 entered promiscuous mode
br-lan: port 1(eth0) entering forwarding state
eth1: link up (100Mbps/Full duplex)
eth1: link down
eth1: link up (100Mbps/Full duplex)
Compat-wireless backport release: compat-wireless-2010-12-10-3-g880bb0b
Backport based on wireless-testing.git master-2010-12-16
cfg80211: Calling CRDA to update world regulatory domain
cfg80211: World regulatory domain updated:
cfg80211:     (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
cfg80211:     (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
cfg80211:     (2457000 KHz - 2482000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
cfg80211:     (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
cfg80211:     (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
cfg80211:     (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
PCI: Setting latency timer of device 0000:00:00.0 to 64
ath: EEPROM regdomain: 0x0
ath: EEPROM indicates default country code should be used
ath: doing EEPROM country->regdmn map search
ath: country maps to regdmn code: 0x3a
ath: Country alpha2 being used: US
ath: Regpair used: 0x3a
ieee80211 phy0: Selected rate control algorithm 'minstrel_ht'
Registered led device: ath9k-phy0
ieee80211 phy0: Atheros AR9285 Rev:2 mem=0xb0000000, irq=48
cfg80211: Calling CRDA for country: US
cfg80211: Regulatory domain changed to country: US
cfg80211:     (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
cfg80211:     (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2700 mBm)
cfg80211:     (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 1700 mBm)
cfg80211:     (5250000 KHz - 5330000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
cfg80211:     (5490000 KHz - 5600000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
cfg80211:     (5650000 KHz - 5710000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
cfg80211:     (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 3000 mBm)
PPP generic driver version 2.4.2
ip_tables: (C) 2000-2006 Netfilter Core Team
NET: Registered protocol family 24
nf_conntrack version 0.5.0 (461 buckets, 1844 max)
CONFIG_NF_CT_ACCT is deprecated and will be removed soon. Please use
nf_conntrack.acct=1 kernel parameter, acct=1 nf_conntrack module option or
sysctl net.netfilter.nf_conntrack_acct=1 to enable it.
device wlan0 entered promiscuous mode
br-lan: port 2(wlan0) entering forwarding state
device wlan0 left promiscuous mode
br-lan: port 2(wlan0) entering disabled state
device wlan0 entered promiscuous mode
br-lan: port 2(wlan0) entering forwarding state
ar71xx-wdt: enabling watchdog timer
xt_time: kernel timezone is -0000
br-lan: port 2(wlan0) entering disabled state
br-lan: port 1(eth0) entering disabled state
eth0: link down
device wlan0 left promiscuous mode
br-lan: port 2(wlan0) entering disabled state
device eth0 left promiscuous mode
br-lan: port 1(eth0) entering disabled state
eth1: link down
eth0: link up (1000Mbps/Full duplex)
eth0: link down
eth0: link up (1000Mbps/Full duplex)
device eth0 entered promiscuous mode
br-lan: port 1(eth0) entering forwarding state
device wlan0 entered promiscuous mode
br-lan: port 2(wlan0) entering forwarding state
eth1: link up (100Mbps/Full duplex)
eth1: link down
eth1: link up (100Mbps/Full duplex)
eth1: link down
eth1: link up (100Mbps/Full duplex)
device wlan0 left promiscuous mode
br-lan: port 2(wlan0) entering disabled state
device wlan0 entered promiscuous mode
br-lan: port 2(wlan0) entering forwarding state
device wlan0 left promiscuous mode
br-lan: port 2(wlan0) entering disabled state
device wlan0 entered promiscuous mode
br-lan: port 2(wlan0) entering forwarding state
ath: Timeout while waiting for nf to load: AR_PHY_AGC_CONTROL=0x40d22
ath: Timeout while waiting for nf to load: AR_PHY_AGC_CONTROL=0x40d22
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x02000020
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
------------[ cut here ]------------
WARNING: at /opt/projekty/openwrt/ar71xx-backfire/build_dir/linux-ar71xx/compat-wireless-2010-12-16/drivers/net/wireless/ath/ath9k/recv.c:535 0x80c6791c()
Modules linked in: xt_HL xt_hl xt_MARK ipt_ECN xt_CLASSIFY xt_time xt_tcpmss xt_statistic xt_mark xt_length ipt_ecn xt_DSCP xt_dscp nf_nat_tftp nf_conntrack_tftp nf_nat_irc nf_conntrack_irc nf_nat_ftp nf_conntrack_ftp ipt_MASQUERADE iptable_nat nf_nat xt_NOTRACK iptable_raw xt_state nf_conntrack_ipv4 nf_defrag_ipv4 nf_conntrack pppoe pppox ipt_REJECT xt_TCPMSS ipt_LOG xt_comment xt_multiport xt_mac xt_limit iptable_mangle iptable_filter ip_tables xt_tcpudp x_tables ppp_async ppp_generic slhc ath9k ath9k_common ath9k_hw ath mac80211 crc16 crc_ccitt cfg80211 compat_firmware_class compat arc4 aes_generic deflate ecb cbc leds_gpio button_hotplug gpio_buttons input_polldev input_core
Call Trace:[<8007e010>] 0x8007e010
[<80068374>] 0x80068374
[<80068374>] 0x80068374
[<8007cf1c>] 0x8007cf1c
[<80c6791c>] 0x80c6791c
[<80c70000>] 0x80c70000
[<80c6791c>] 0x80c6791c
[<80c646fc>] 0x80c646fc
[<80c60524>] 0x80c60524
[<8009fa18>] 0x8009fa18
[<8009635c>] 0x8009635c
[<80d20754>] 0x80d20754
[<80c65398>] 0x80c65398
[<80082170>] 0x80082170
[<800a80bc>] 0x800a80bc
[<80082964>] 0x80082964
[<80082a44>] 0x80082a44
[<8006082c>] 0x8006082c
[<80060a00>] 0x80060a00
[<8006b2bc>] 0x8006b2bc
[<8006c75c>] 0x8006c75c
[<80060a20>] 0x80060a20
[<802c7a54>] 0x802c7a54
[<802c73a8>] 0x802c73a8

---[ end trace f7b857f73b45d527 ]---
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x02000020
ath: Timeout while waiting for nf to load: AR_PHY_AGC_CONTROL=0x40d22
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x02000020
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x02000020
ath: Timeout while waiting for nf to load: AR_PHY_AGC_CONTROL=0x40d22
ath: Failed to stop TX DMA in 100 msec after killing last frame
ath: Timeout while waiting for nf to load: AR_PHY_AGC_CONTROL=0x40d22
ath: Failed to stop TX DMA in 100 msec after killing last frame
ath: Failed to stop TX DMA in 100 msec after killing last frame
ath: Failed to stop TX DMA in 100 msec after killing last frame
ath: Timeout while waiting for nf to load: AR_PHY_AGC_CONTROL=0x40d22
ath: Failed to stop TX DMA in 100 msec after killing last frame
ath: Failed to stop TX DMA in 100 msec after killing last frame
ath: Failed to stop TX DMA!
ath: Timeout while waiting for nf to load: AR_PHY_AGC_CONTROL=0x40d22
ath: Timeout while waiting for nf to load: AR_PHY_AGC_CONTROL=0x40d22
ath: Failed to stop TX DMA in 100 msec after killing last frame
ath: Failed to stop TX DMA in 100 msec after killing last frame
ath: Failed to stop TX DMA in 100 msec after killing last frame
ath: Failed to stop TX DMA in 100 msec after killing last frame
ath: Failed to stop TX DMA in 100 msec after killing last frame
ath: Failed to stop TX DMA in 100 msec after killing last frame
ath: Failed to stop TX DMA in 100 msec after killing last frame
ath: Failed to stop TX DMA in 100 msec after killing last frame
ath: Failed to stop TX DMA in 100 msec after killing last frame
ath: Failed to stop TX DMA in 100 msec after killing last frame
ath: Failed to stop TX DMA in 100 msec after killing last frame
ath: Failed to stop TX DMA in 100 msec after killing last frame
ath: Failed to stop TX DMA in 100 msec after killing last frame
ath: Failed to stop TX DMA in 100 msec after killing last frame
ath: Failed to stop TX DMA in 100 msec after killing last frame
ath: Failed to stop TX DMA in 100 msec after killing last frame
ath: Failed to stop TX DMA in 100 msec after killing last frame
ath: Failed to stop TX DMA in 100 msec after killing last frame
ath: Failed to stop TX DMA in 100 msec after killing last frame
ath: Failed to stop TX DMA in 100 msec after killing last frame
ath: Failed to stop TX DMA in 100 msec after killing last frame
ath: Failed to stop TX DMA in 100 msec after killing last frame
ath: Failed to stop TX DMA in 100 msec after killing last frame
ath: Failed to stop TX DMA in 100 msec after killing last frame
ath: Failed to stop TX DMA in 100 msec after killing last frame
ath: Failed to stop TX DMA in 100 msec after killing last frame
ath: Failed to stop TX DMA in 100 msec after killing last frame
ath: Failed to stop TX DMA in 100 msec after killing last frame
ath: Timeout while waiting for nf to load: AR_PHY_AGC_CONTROL=0x40d22
ath: Timeout while waiting for nf to load: AR_PHY_AGC_CONTROL=0x40d22
ath: Failed to stop TX DMA in 100 msec after killing last frame
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x02000020
ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x02000020
ath: Timeout while waiting for nf to load: AR_PHY_AGC_CONTROL=0x40d22
ath: Timeout while waiting for nf to load: AR_PHY_AGC_CONTROL=0x40d22

Attachments (0)

Change History (5)

comment:1 Changed 7 years ago by jow

  • Owner changed from developers to nbd
  • Status changed from new to assigned

comment:2 Changed 7 years ago by lore20

does your router reboot itself after that stuck?
mine does with a TL-WN961N, but I was unable to get a trace

comment:3 Changed 7 years ago by anonymous

I have same issue with TL-WR1043ND and it doesn't reboot.

comment:4 Changed 7 years ago by magyarsz

Similar on my TP-LINK TL-WR741ND too. I would like to use it AP+Client configuration, but it doesn't working by reason of problems described above.
I used the recent revision of trunk.

comment:5 Changed 7 years ago by nbd

  • Resolution set to duplicate
  • Status changed from assigned to closed

Stability issues are tracked in #8830, please try the latest version

Add Comment

Modify Ticket

Action
as closed .
The resolution will be deleted. Next status will be 'reopened'.
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.