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, 18 Oct 2013 16:03:47 +0200 [thread overview]
Message-ID: <20131018140346.GA14569@linutronix.de> (raw)
In-Reply-To: <EBD2DE4ADA47B94E831AED12A4B0CADA67EBD1B2@edb0.wapice.localdomain>
* Sami Pietikäinen | 2013-10-14 07:24:20 [+0000]:
>Hello Sebastian
Hello Sami,
>>The problem does not look -RT specific.
>
>I would say that at least the "Trying to free already-free IRQ 1" warning is somehow -RT specific. When I tested the 3.6.9 kernel without the RT patch there were no warnings (using SAMA5D35). The same warning Michael is having appeared only after applying the patch. However, the other problems Michael is having might also be something else.
>
>>I don't understand why uart tries over and over to request that interrupt but it simply doesn't work.
>>I am a little confused why at91 is having everything (or more than one
>>device) is on irq 16. It should have only one device on each interrupt since they have usually dedicated irq lines.
>
>arm-at91-tclib-default-to-tclib-timer-for-rt.patch has the following comment:
>"RT is not too happy about the shared timer interrupt in AT91
>devices. Default to tclib timer for RT."
>
>Snippet from SAMA5D35 datasheet:
>"Usually, the Debug Unit interrupt line connects to the interrupt source 1 of the AIC, which may be shared with the real-time clock, the system timer interrupt lines and other system peripheral interrupts"
>
>The debug unit also has UART which is probably Michael's ttyS0.
Argh. I missed that detail. So that explains why UART and the timer
share the same interrupt number. Is that timer really disabled in your
config?
>
>BR,
>Sami
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-10-18 14:03 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 [this message]
2013-10-23 12:19 ` Sami Pietikäinen
2013-10-28 13:59 ` Sami Pietikäinen
2013-11-08 22:17 ` Sebastian Andrzej Siewior
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=20131018140346.GA14569@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).