netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Yegor Yefremov <yegorslists@googlemail.com>
To: netdev <netdev@vger.kernel.org>
Cc: "N, Mugunthan V" <mugunthanvnm@ti.com>, Felipe Balbi <balbi@ti.com>
Subject: am335x: cpsw: interrupt failure
Date: Thu, 4 Dec 2014 17:41:38 +0100	[thread overview]
Message-ID: <CAGm1_ksPkFXV_S6541cK1TQb_eRTHbspZy4zWxY5GMrrjGD2tA@mail.gmail.com> (raw)

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
->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?

Yegor

             reply	other threads:[~2014-12-04 16:41 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-04 16:41 Yegor Yefremov [this message]
2014-12-04 16:56 ` am335x: cpsw: interrupt failure Felipe Balbi
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=CAGm1_ksPkFXV_S6541cK1TQb_eRTHbspZy4zWxY5GMrrjGD2tA@mail.gmail.com \
    --to=yegorslists@googlemail.com \
    --cc=balbi@ti.com \
    --cc=mugunthanvnm@ti.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).