From: Paul Mundt <lethal@linux-sh.org>
To: linux-sh@vger.kernel.org
Subject: Re: kzm9g boot fail (was Re: irqdomain breaks ap4 boot)
Date: Mon, 20 Aug 2012 04:38:53 +0000 [thread overview]
Message-ID: <20120820043853.GD25767@linux-sh.org> (raw)
In-Reply-To: <502DDC97.5080501@kmckk.co.jp>
On Sun, Aug 19, 2012 at 09:19:34PM -0700, Kuninori Morimoto wrote:
>
> Hi Paul
>
> > Can you post a boot log with the pr_debug() output in the irqdomain code
> > enabled? You may need to add ignore_loglevel to your kernel command line.
> >
> > If that doesn't produce any further clues I'll have to find one of these
> > boards to see what's going on.
>
> This is my log
>
> NR_IRQS:16 nr_irqs:16 16
> irq: Allocated domain of type 0 @0xde802800
> intc: Registered controller 'sh73a0-intcs' with 77 IRQs
> irq: Allocated domain of type 3 @0xde802940
..
> irq: irq_domain_associate_many(<no-node>, irqbaseU2, hwbaseU2, count=1)
..
> intc: Registered controller 'sh73a0-intca-irq-pins' with 32 IRQs
> irq: Allocated domain of type 3 @0xde8029c0
> irq: irq_domain_associate_many(<no-node>, irqbaseT4, hwbaseT4, count=1)
> irq: irq_domain_associate_many(<no-node>, irqbaseT5, hwbaseT5, count=1)
> irq: irq_domain_associate_many(<no-node>, irqbaseT6, hwbaseT6, count=1)
> irq: irq_domain_associate_many(<no-node>, irqbaseT7, hwbaseT7, count=1)
> irq: irq_domain_associate_many(<no-node>, irqbaseT8, hwbaseT8, count=1)
> irq: irq_domain_associate_many(<no-node>, irqbaseT9, hwbaseT9, count=1)
> irq: irq_domain_associate_many(<no-node>, irqbaseU0, hwbaseU0, count=1)
> irq: irq_domain_associate_many(<no-node>, irqbaseU1, hwbaseU1, count=1)
> irq: irq_domain_associate_many(<no-node>, irqbaseU2, hwbaseU2, count=1)
> ------------[ cut here ]------------
> WARNING: at /opt/usr/src/WORK/morimoto/gitlinux/linux-2.6/kernel/irq/irqdomain.)
> error: irq_desc already associated; irqU2 hwirq=0x228
Well, that's certainly a valid bug. hwirq 552 is already bound to the
previous controller, and the vector in question is being registered a
second time under another controller. This looks to be RTDMAC_2_DEI6 (0x1300),
but the rest descends in to macro hell, so it's not obvious why the same
vector is being registered in multiple places.
next prev parent reply other threads:[~2012-08-20 4:38 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-02 9:50 irqdomain breaks ap4 boot kuninori.morimoto.gx
2012-08-03 5:00 ` Paul Mundt
2012-08-09 4:28 ` Paul Mundt
2012-08-09 4:53 ` Kuninori Morimoto
2012-08-10 6:10 ` Kuninori Morimoto
2012-08-10 12:38 ` Paul Mundt
2012-08-17 5:54 ` kzm9g boot fail (was Re: irqdomain breaks ap4 boot) Tetsuyuki Kobayashi
2012-08-20 1:14 ` Kuninori Morimoto
2012-08-20 3:13 ` Paul Mundt
2012-08-20 4:19 ` Kuninori Morimoto
2012-08-20 4:19 ` Tetsuyuki Kobayashi
2012-08-20 4:38 ` Paul Mundt [this message]
2012-08-20 4:45 ` Kuninori Morimoto
2012-08-20 5:24 ` Paul Mundt
2012-08-20 5:33 ` Tetsuyuki Kobayashi
2012-08-20 6:13 ` Kuninori Morimoto
2012-08-20 6:24 ` Kuninori Morimoto
2012-08-20 6:30 ` Paul Mundt
2012-08-20 6:32 ` Tetsuyuki Kobayashi
2012-08-22 6:49 ` [PATCH] mmc: sh-mmcif: avoid Oops on spurious interrupts Guennadi Liakhovetski
2012-08-22 12:16 ` Tetsuyuki Kobayashi
2012-08-23 7:11 ` Guennadi Liakhovetski
2012-09-04 7:40 ` Tetsuyuki Kobayashi
2012-08-31 3:05 ` Tetsuyuki Kobayashi
2012-09-18 6:13 ` Tetsuyuki Kobayashi
2012-09-18 6:42 ` Guennadi Liakhovetski
2012-09-18 8:02 ` Tetsuyuki Kobayashi
2012-09-18 8:44 ` Tetsuyuki Kobayashi
2012-09-18 8:56 ` Guennadi Liakhovetski
2012-09-19 2:50 ` Tetsuyuki Kobayashi
2012-09-26 1:47 ` Tetsuyuki Kobayashi
2012-09-26 10:04 ` Chris Ball
2012-09-19 6:24 ` Chris Ball
2012-09-21 2:35 ` Tetsuyuki Kobayashi
2012-08-20 7:18 ` kzm9g boot fail (was Re: irqdomain breaks ap4 boot) Magnus Damm
2012-08-20 7:40 ` Paul Mundt
2012-08-20 7:41 ` Kuninori Morimoto
2012-08-20 7:54 ` Paul Mundt
2012-08-20 8:12 ` Kuninori Morimoto
2012-08-20 8:35 ` Kuninori Morimoto
2012-08-21 2:31 ` Kuninori Morimoto
2012-08-21 4:22 ` Tetsuyuki Kobayashi
2012-08-31 6:55 ` irqdomain breaks ap4 boot Tetsuyuki Kobayashi
2012-08-31 7:17 ` Simon Horman
2012-08-31 10:36 ` Paul Mundt
2012-09-18 2:15 ` Tetsuyuki Kobayashi
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=20120820043853.GD25767@linux-sh.org \
--to=lethal@linux-sh.org \
--cc=linux-sh@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).