On 03/13/2014 11:33 PM, Sören Brinkmann wrote: > On Thu, 2014-03-13 at 03:16PM -0700, Sören Brinkmann wrote: >> Hi Nicolas, >> >> I did some testing on the current linux-next tree and ran iperf on Zynq. >> It seems that network and even the whole system can collapse when doing >> that. >> I don't really know what's going on, but once I saw the message: >> "inconsistent Rx descriptor chain" >> printed twice (system frozen afterwards). >> >> I don't know what exactly is going wrong, but suspect something around >> memory/DMA. I have no clue whether it makes any sense or not, but I >> tried using the macb_* functions instead of the gem_* ones (see diff below). >> That seems to result in a stable system and working Ethernet. > > That was a little too early. After roughly 25 minutest the system runs > into a deadlock: > BUG: spinlock lockup suspected on CPU#1, iperf/774 > lock: 0xeda0366c, .magic: dead4ead, .owner: swapper/0/0, .owner_cpu: 0 > CPU: 1 PID: 774 Comm: iperf Tainted: G W 3.14.0-rc6-next-20140312-xilinx-dirty #41 > [] (unwind_backtrace) from [] (show_stack+0x10/0x14) > [] (show_stack) from [] (dump_stack+0x80/0xcc) > [] (dump_stack) from [] (do_raw_spin_lock+0xd4/0x190) > [] (do_raw_spin_lock) from [] (_raw_spin_lock_irqsave+0x58/0x64) > [] (_raw_spin_lock_irqsave) from [] (macb_start_xmit+0x24/0x2d0) > [] (macb_start_xmit) from [] (dev_hard_start_xmit+0x334/0x470) > [] (dev_hard_start_xmit) from [] (sch_direct_xmit+0x78/0x2f8) > [] (sch_direct_xmit) from [] (__dev_queue_xmit+0x314/0x704) > [] (__dev_queue_xmit) from [] (ip_finish_output+0x6c4/0x894) > [] (ip_finish_output) from [] (ip_local_out+0x74/0x90) > [] (ip_local_out) from [] (ip_queue_xmit+0x400/0x5c4) > [] (ip_queue_xmit) from [] (tcp_transmit_skb+0xa18/0xab0) > [] (tcp_transmit_skb) from [] (tcp_recvmsg+0x92c/0xae4) > [] (tcp_recvmsg) from [] (inet_recvmsg+0x1c0/0x1fc) > [] (inet_recvmsg) from [] (sock_recvmsg+0x7c/0x98) > [] (sock_recvmsg) from [] (SyS_recvfrom+0x9c/0x108) > [] (SyS_recvfrom) from [] (sys_recv+0x14/0x18) > [] (sys_recv) from [] (ret_fast_syscall+0x0/0x48) Do you have this change in your tree? https://github.com/Xilinx/linux-xlnx/commit/1a85939af40acca2bf963407b497cc31c303ff3e I don't think we have sent this to mainline yet. Thanks, Michal -- Michal Simek, Ing. (M.Eng), OpenPGP -> KeyID: FE3D1F91 w: www.monstr.eu p: +42-0-721842854 Maintainer of Linux kernel - Microblaze cpu - http://www.monstr.eu/fdt/ Maintainer of Linux kernel - Xilinx Zynq ARM architecture Microblaze U-BOOT custodian and responsible for u-boot arm zynq platform