From mboxrd@z Thu Jan 1 00:00:00 1970 From: mugunthanvnm@ti.com (Mugunthan V N) Date: Mon, 6 Oct 2014 15:24:59 +0530 Subject: CPSW bug with AM437x SK In-Reply-To: <20141003010418.GA9612@saruman> References: <20141003010418.GA9612@saruman> Message-ID: <543266F3.4090200@ti.com> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.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