From: Felipe Balbi <balbi@ti.com>
To: Yegor Yefremov <yegorslists@googlemail.com>
Cc: netdev <netdev@vger.kernel.org>,
"N, Mugunthan V" <mugunthanvnm@ti.com>,
Felipe Balbi <balbi@ti.com>
Subject: Re: am335x: cpsw: interrupt failure
Date: Thu, 4 Dec 2014 10:56:09 -0600 [thread overview]
Message-ID: <20141204165609.GJ18045@saruman> (raw)
In-Reply-To: <CAGm1_ksPkFXV_S6541cK1TQb_eRTHbspZy4zWxY5GMrrjGD2tA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2112 bytes --]
Hi,
On Thu, Dec 04, 2014 at 05:41:38PM +0100, Yegor Yefremov wrote:
> I have following problem. My systems reboots at high network load
> after this commit (found via git bissect):
>
> commit 55601c9f24670ba926ebdd4d712ac3b177232330
> Author: Felipe Balbi <balbi@ti.com>
> Date: Mon Sep 8 17:54:58 2014 -0700
>
> arm: omap: intc: switch over to linear irq domain
>
> now that we don't need to support legacy board-files,
> we can completely switch over to a linear irq domain
> and make use of irq_alloc_domain_generic_chips() to
> allocate all generic irq chips for us.
>
> Signed-off-by: Felipe Balbi <balbi@ti.com>
> Signed-off-by: Tony Lindgren <tony@atomide.com>
>
> and I get following error messages:
>
> irq 0, desc: cf004000, depth: 1, count: 0, unhandled: 0
irq 0 ? Weird, that's not a valid IRQ.
> ->handle_irq(): c0087fc0, handle_bad_irq+0x0/0x258
> ->irq_data.chip(): c08e7174, no_irq_chip+0x0/0x68
> ->action(): (null)
> IRQ_NOPROBE set
> IRQ_NOREQUEST set
> irq 0, desc: cf004000, depth: 1, count: 0, unhandled: 0
> ->handle_irq(): c0087fc0, handle_bad_irq+0x0/0x258
> ->irq_data.chip(): c08e7174, no_irq_chip+0x0/0x68
> ->action(): (null)
> IRQ_NOPROBE set
> IRQ_NOREQUEST set
> irq 0, desc: cf004000, depth: 1, count: 0, unhandled: 0
> ->handle_irq(): c0087fc0, handle_bad_irq+0x0/0x258
> ->irq_data.chip(): c08e7174, no_irq_chip+0x0/0x68
> ->action(): (null)
> IRQ_NOPROBE set
> IRQ_NOREQUEST set
> irq 0, desc: cf004000, depth: 1, count: 0, unhandled: 0
> ->handle_irq(): c0087fc0, handle_bad_irq+0x0/0x258
> ->irq_data.chip(): c08e7174, no_irq_chip+0x0/0x68
> ->action(): (null)
>
> My system: am335x with fast ethernet on the first slave and gigabit
> Ethernet on second CPSW slave. This issue occurs, when I ran nuttcp
> with default settings.
>
> With commit above I can at least see these messages, but 3.18-rc7 for
> example reboots without any messages.
>
> Any idea?
if you take v3.18-rc7 and just revert that commit, does the problem go
away ?
--
balbi
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2014-12-04 16:56 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-04 16:41 am335x: cpsw: interrupt failure Yegor Yefremov
2014-12-04 16:56 ` Felipe Balbi [this message]
2014-12-05 10:03 ` Yegor Yefremov
2014-12-10 17:17 ` Felipe Balbi
2014-12-10 20:58 ` Yegor Yefremov
2014-12-10 21:02 ` Felipe Balbi
2014-12-10 22:56 ` Yegor Yefremov
2014-12-12 12:00 ` Yegor Yefremov
2014-12-12 17:32 ` Felipe Balbi
2014-12-12 19:19 ` Yegor Yefremov
2014-12-29 9:33 ` Yegor Yefremov
2014-12-29 13:46 ` Peter Hurley
2014-12-29 15:50 ` Felipe Balbi
2014-12-29 16:51 ` Tony Lindgren
2014-12-29 17:13 ` Felipe Balbi
2014-12-30 23:22 ` 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=20141204165609.GJ18045@saruman \
--to=balbi@ti.com \
--cc=mugunthanvnm@ti.com \
--cc=netdev@vger.kernel.org \
--cc=yegorslists@googlemail.com \
/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.