From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Michael Langfinger <linux-rt-users@langfinger.org>
Cc: "Sami Pietikäinen" <Sami.Pietikainen@wapice.com>,
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, 11 Oct 2013 12:09:51 +0200 [thread overview]
Message-ID: <20131011100951.GC6983@linutronix.de> (raw)
In-Reply-To: <aa8bdc572d2b3fc1f5c1c92293990143-EhVcX1hHQARfWkQdAQYAWQoDGQlVS19cWF9EAVxEXEI3UlEWXV5/H1FTQ11bSSoDXF1RQFtXWAhY-webmailer2@server02.webmailer.hosteurope.de>
* Michael Langfinger | 2013-09-01 12:40:07 [+0200]:
>Hello Sami,
Hi Michael,
>I attached the output of the boot process (with your patch applied)
>below. The first one is from kernel 3.10.9-rt5 with
>CONFIG_PREEMPT_RT_FULL set, the second one is from kernel 3.10.9-rt5
>with CONFIG_PREEMPT_RTB.
>
>If you need any further information, please let me know!
The problem does not look -RT specific.
>
>Kind regards,
>Michael Langfinger
>
>
>Starting linux kernel ..., machid: 0x1035
>
>Uncompressing Linux... done, booting the kernel.
…
>NR_IRQS:16 nr_irqs:16 16
>------------[ cut here ]------------
>WARNING: at kernel/irq/manage.c:1268 __free_irq+0x90/0x1a8()
>Trying to free already-free IRQ 1
here someone calls free_irq() on IRQ1 but it was not requested.
>Modules linked in:
…
>------------[ cut here ]------------
>WARNING: at kernel/irq/manage.c:1268 __free_irq+0x90/0x1a8()
>Trying to free already-free IRQ 1
The same thing here
>Modules linked in:
…
>genirq: Flags mismatch irq 16. 00002080 (at91_rtc) vs. 000152a0
>(at91_tick)
The the RTC comes with IRF_ONESHOT but the tick does not want this.
>at91_rtc fffffeb0.rtc: IRQ 16 already in use.
>at91_rtc: probe of fffffeb0.rtc failed with error -16
…
>genirq: Flags mismatch irq 16. 00002080 (ttyS0) vs. 000152a0
>(at91_tick)
>atmel_serial: atmel_startup - Can't get irq
The same is true for your uart (ttyS0). Since it can't get the interrupt
it will unregister and your console will be soon gone.
>Waiting 1sec before mounting root device...
…
>genirq: Flags mismatch irq 16. 00002080 (ttyS0) vs. 000152a0
>(at91_tick)
>atmel_serial: atmel_startup - Can't get irq
>
>[ the last two lines are repeated several times, then the system
>hangs ]
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.
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-11 10:09 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 [this message]
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
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=20131011100951.GC6983@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).