From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754233AbaCMWdz (ORCPT ); Thu, 13 Mar 2014 18:33:55 -0400 Received: from ch1ehsobe001.messaging.microsoft.com ([216.32.181.181]:40563 "EHLO ch1outboundpool.messaging.microsoft.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753601AbaCMWdw convert rfc822-to-8bit (ORCPT ); Thu, 13 Mar 2014 18:33:52 -0400 X-Forefront-Antispam-Report: CIP:149.199.60.83;KIP:(null);UIP:(null);IPV:NLI;H:xsj-gw1;RD:unknown-60-83.xilinx.com;EFVD:NLI X-SpamScore: -2 X-BigFish: VPS-2(z569dhz98dIc89bh936eI1432Izz1f42h2148h208ch1ee6h1de0h1fdah2149h2073h2146h1202h1e76h2189h1d1ah1d2ah21bch1fc6hzzz2fh95h839h93fhc61hd24hf0ah119dh1288h12a5h12a9h12bdh137ah13b6h1441h14ddh1504h1537h153bh162dh1631h1758h18e1h1946h19b5h1b0ah224fh1d0ch1d2eh1d3fh1dfeh1dffh1e1dh1fe8h1ff5h209eh2216h2336h2438h2461h2487h24d7h2516h2545h255eh25f6h2605h906i1155h) Date: Thu, 13 Mar 2014 15:33:16 -0700 From: =?utf-8?B?U8O2cmVu?= Brinkmann To: Nicolas Ferre CC: Michal Simek , Anirudha Sarangi , Punnaiah Choudary Kalluri , , Subject: Re: Zynq macb References: MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) X-RCIS-Action: ALLOW Message-ID: <73734ba5-00d3-445d-8c6f-a1a868cdd537@CH1EHSMHS024.ehs.local> Content-Transfer-Encoding: 8BIT X-OriginatorOrg: xilinx.com X-FOPE-CONNECTOR: Id%0$Dn%*$RO%0$TLS%0$FQDN%$TlsDn% Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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) Sören