From: Mugunthan V N <mugunthanvnm@ti.com>
To: balbi@ti.com
Cc: davem@davemloft.net, netdev@vger.kernel.org,
Linux OMAP Mailing List <linux-omap@vger.kernel.org>,
Linux ARM Kernel Mailing List
<linux-arm-kernel@lists.infradead.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: CPSW bug with AM437x SK
Date: Mon, 6 Oct 2014 15:24:59 +0530 [thread overview]
Message-ID: <543266F3.4090200@ti.com> (raw)
In-Reply-To: <20141003010418.GA9612@saruman>
On Friday 03 October 2014 06:34 AM, Felipe Balbi wrote:
> [ 261.177168] [<c0648d48>] (skb_panic) from [<c0565edc>] (skb_put+0x5c/0x60)
> [ 261.184415] [<c0565edc>] (skb_put) from [<c0605aac>] (unix_stream_sendmsg+0x164/0x390)
> [ 261.192712] [<c0605aac>] (unix_stream_sendmsg) from [<c055b364>] (sock_aio_write+0xdc/0xfc)
> [ 261.201475] [<c055b364>] (sock_aio_write) from [<c014c42c>] (do_sync_write+0x8c/0xb4)
> [ 261.209697] [<c014c42c>] (do_sync_write) from [<c014cf70>] (vfs_write+0x118/0x1c0)
> [ 261.217652] [<c014cf70>] (vfs_write) from [<c014d564>] (SyS_write+0x4c/0xa0)
> [ 261.225054] [<c014d564>] (SyS_write) from [<c000ed40>] (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
WARNING: multiple messages have this Message-ID (diff)
From: mugunthanvnm@ti.com (Mugunthan V N)
To: linux-arm-kernel@lists.infradead.org
Subject: CPSW bug with AM437x SK
Date: Mon, 6 Oct 2014 15:24:59 +0530 [thread overview]
Message-ID: <543266F3.4090200@ti.com> (raw)
In-Reply-To: <20141003010418.GA9612@saruman>
On Friday 03 October 2014 06:34 AM, Felipe Balbi wrote:
> [ 261.177168] [<c0648d48>] (skb_panic) from [<c0565edc>] (skb_put+0x5c/0x60)
> [ 261.184415] [<c0565edc>] (skb_put) from [<c0605aac>] (unix_stream_sendmsg+0x164/0x390)
> [ 261.192712] [<c0605aac>] (unix_stream_sendmsg) from [<c055b364>] (sock_aio_write+0xdc/0xfc)
> [ 261.201475] [<c055b364>] (sock_aio_write) from [<c014c42c>] (do_sync_write+0x8c/0xb4)
> [ 261.209697] [<c014c42c>] (do_sync_write) from [<c014cf70>] (vfs_write+0x118/0x1c0)
> [ 261.217652] [<c014cf70>] (vfs_write) from [<c014d564>] (SyS_write+0x4c/0xa0)
> [ 261.225054] [<c014d564>] (SyS_write) from [<c000ed40>] (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
WARNING: multiple messages have this Message-ID (diff)
From: Mugunthan V N <mugunthanvnm@ti.com>
To: <balbi@ti.com>
Cc: <davem@davemloft.net>, <netdev@vger.kernel.org>,
Linux OMAP Mailing List <linux-omap@vger.kernel.org>,
Linux ARM Kernel Mailing List
<linux-arm-kernel@lists.infradead.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: CPSW bug with AM437x SK
Date: Mon, 6 Oct 2014 15:24:59 +0530 [thread overview]
Message-ID: <543266F3.4090200@ti.com> (raw)
In-Reply-To: <20141003010418.GA9612@saruman>
On Friday 03 October 2014 06:34 AM, Felipe Balbi wrote:
> [ 261.177168] [<c0648d48>] (skb_panic) from [<c0565edc>] (skb_put+0x5c/0x60)
> [ 261.184415] [<c0565edc>] (skb_put) from [<c0605aac>] (unix_stream_sendmsg+0x164/0x390)
> [ 261.192712] [<c0605aac>] (unix_stream_sendmsg) from [<c055b364>] (sock_aio_write+0xdc/0xfc)
> [ 261.201475] [<c055b364>] (sock_aio_write) from [<c014c42c>] (do_sync_write+0x8c/0xb4)
> [ 261.209697] [<c014c42c>] (do_sync_write) from [<c014cf70>] (vfs_write+0x118/0x1c0)
> [ 261.217652] [<c014cf70>] (vfs_write) from [<c014d564>] (SyS_write+0x4c/0xa0)
> [ 261.225054] [<c014d564>] (SyS_write) from [<c000ed40>] (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
next prev parent reply other threads:[~2014-10-06 9:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-03 1:04 CPSW bug with AM437x SK Felipe Balbi
2014-10-03 1:04 ` Felipe Balbi
2014-10-03 1:04 ` Felipe Balbi
2014-10-06 9:54 ` Mugunthan V N [this message]
2014-10-06 9:54 ` Mugunthan V N
2014-10-06 9:54 ` Mugunthan V N
2014-10-06 14:33 ` Felipe Balbi
2014-10-06 14:33 ` Felipe Balbi
2014-10-06 14:33 ` Felipe Balbi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=543266F3.4090200@ti.com \
--to=mugunthanvnm@ti.com \
--cc=balbi@ti.com \
--cc=davem@davemloft.net \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.