From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: "Sami Pietikäinen" <Sami.Pietikainen@wapice.com>
Cc: Michael Langfinger <linux-rt-users@langfinger.org>,
"linux-rt-users@vger.kernel.org" <linux-rt-users@vger.kernel.org>
Subject: Re: 3.10.9-rt5 with Atmel AT91SAM9G25 SoC triggers "Trying to free already-free IRQ 1"
Date: Fri, 8 Nov 2013 23:17:21 +0100 [thread overview]
Message-ID: <20131108221721.GB13367@linutronix.de> (raw)
In-Reply-To: <EBD2DE4ADA47B94E831AED12A4B0CADA67ECF09C@edb1.wapice.localdomain>
* Sami Pietikäinen | 2013-10-28 13:59:53 [+0000]:
>It seems that there is an irq number mismatch in the "arm-at91-pit-remove-irq-handler-when-clock-is-unused.patch".
>The patch adds setup_irq() and remove_irq() calls which have different irq number than the base driver.
>
>If I'm correct, the irq number should be NR_IRQS_LEGACY + AT91_ID_SYS instead of only AT91_ID_SYS.
>
>I have attached a fixed patch for 3.6.9-rt21. I tested it with SAMA5D35, and it removed the
>"Trying to free already-free IRQ 1" boot warnings.
Michael, any feedback? Does this solve your problem, too?
>BR,
>Sami Pietikäinen
Sebastian
--
To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2013-11-08 22:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-30 11:18 3.10.9-rt5 with Atmel AT91SAM9G25 SoC triggers "Trying to free already-free IRQ 1" Sami Pietikäinen
2013-09-01 10:40 ` Michael Langfinger
2013-09-03 9:09 ` Sami Pietikäinen
2013-10-11 10:09 ` Sebastian Andrzej Siewior
2013-10-14 7:24 ` Sami Pietikäinen
2013-10-18 14:03 ` Sebastian Andrzej Siewior
2013-10-23 12:19 ` Sami Pietikäinen
2013-10-28 13:59 ` Sami Pietikäinen
2013-11-08 22:17 ` Sebastian Andrzej Siewior [this message]
2013-11-09 20:37 ` Michael Langfinger
-- strict thread matches above, loose matches on Subject: below --
2013-08-29 21:54 Michael Langfinger
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=20131108221721.GB13367@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=Sami.Pietikainen@wapice.com \
--cc=linux-rt-users@langfinger.org \
--cc=linux-rt-users@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).