Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752050AbaJFJza (ORCPT ); Mon, 6 Oct 2014 05:55:30 -0400 Received: from bear.ext.ti.com ([192.94.94.41]:39790 "EHLO bear.ext.ti.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751090AbaJFJz2 (ORCPT ); Mon, 6 Oct 2014 05:55:28 -0400 Message-ID: <543266F3.4090200@ti.com> Date: Mon, 6 Oct 2014 15:24:59 +0530 From: Mugunthan V N User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.1.2 MIME-Version: 1.0 To: CC: , , Linux OMAP Mailing List , Linux ARM Kernel Mailing List , Linux Kernel Mailing List Subject: Re: CPSW bug with AM437x SK References: <20141003010418.GA9612@saruman> In-Reply-To: <20141003010418.GA9612@saruman> Content-Type: text/plain; charset="windows-1252" Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Friday 03 October 2014 06:34 AM, Felipe Balbi wrote: > [ 261.177168] [] (skb_panic) from [] (skb_put+0x5c/0x60) > [ 261.184415] [] (skb_put) from [] (unix_stream_sendmsg+0x164/0x390) > [ 261.192712] [] (unix_stream_sendmsg) from [] (sock_aio_write+0xdc/0xfc) > [ 261.201475] [] (sock_aio_write) from [] (do_sync_write+0x8c/0xb4) > [ 261.209697] [] (do_sync_write) from [] (vfs_write+0x118/0x1c0) > [ 261.217652] [] (vfs_write) from [] (SyS_write+0x4c/0xa0) > [ 261.225054] [] (SyS_write) from [] (ret_fast_syscall+0x0/0x48) > [ 261.232988] Code: e58d4008 e58de00c e59f0008 ebfff48e (e7f001f2) > [ 261.239378] ---[ end trace d64258d586f40104 ]--- The BT shows that the warn came from a unix socket interface, so this cannot be a CPSW bug, its a bug in unix socket. Are you not seeing this issue with file system in any other media? I will try to reproduce this locally with my AM437x EVMsk. Regards Mugunthan V N -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/