All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jean-Denis Girard <jd.girard@sysnux.pf>
To: linux-kernel@vger.kernel.org
Cc: linux-rt-users@vger.kernel.org
Subject: Re: [ANNOUNCE] v4.4.4-rt11
Date: Wed, 9 Mar 2016 10:31:06 -1000	[thread overview]
Message-ID: <nbq16a$7li$1@ger.gmane.org> (raw)
In-Reply-To: <20160309135142.GF10517@linutronix.de>

Hi,

Le 09/03/2016 03:51, Sebastian Andrzej Siewior a écrit :
> - AT91 got a little better. A larger patch series by Boris Brezillon has
>   been merged. That means SAMA5 boots now. There is one warning left
>   about invoking free_irq() twice. I would be glad about some feedback
>   from pre-SAMA5 SoC. Those which share UART and timer interrupt. It
>   seems that that one I have here does not do this anymore.
> 
> - A patch on top the AT91 series to avoid two warning while switching
>   from period to oneshow mode.

I got this warning when booting my arietta G25:

clocksource: pit: mask: 0xfffffff max_cycles: 0xfffffff, max_idle_ns:
14334453866 ns
------------[ cut here ]------------
WARNING: CPU: 0 PID: 0 at kernel/irq/manage.c:1541 __free_irq+0xb0/0x2b0()
Trying to free already-free IRQ 16
Modules linked in:
CPU: 0 PID: 0 Comm: swapper Not tainted 4.4.4-rt11 #1
Hardware name: Atmel AT91SAM9
[<c000ecb8>] (unwind_backtrace) from [<c000cefc>] (show_stack+0x10/0x14)
[<c000cefc>] (show_stack) from [<c00165ac>] (warn_slowpath_common+0x80/0xa8)
[<c00165ac>] (warn_slowpath_common) from [<c0016600>]
(warn_slowpath_fmt+0x2c/0x3c)
[<c0016600>] (warn_slowpath_fmt) from [<c00409d4>] (__free_irq+0xb0/0x2b0)
[<c00409d4>] (__free_irq) from [<c0040c60>] (free_irq+0x40/0x50)
[<c0040c60>] (free_irq) from [<c03056fc>] (pit_clkevt_shutdown+0x24/0x2c)
[<c03056fc>] (pit_clkevt_shutdown) from [<c0058e94>]
(clockevents_switch_state+0xe8)
[<c0058e94>] (clockevents_switch_state) from [<c0058ee4>]
(clockevents_shutdown+0x1)
[<c0058ee4>] (clockevents_shutdown) from [<c00597dc>]
(tick_check_new_device+0x54/0)
[<c00597dc>] (tick_check_new_device) from [<c0058950>]
(clockevents_register_device)
[<c0058950>] (clockevents_register_device) from [<c051e22c>]
(clocksource_probe+0x4)
[<c051e22c>] (clocksource_probe) from [<c050aafc>]
(start_kernel+0x248/0x35c)
[<c050aafc>] (start_kernel) from [<20008048>] (0x20008048)
---[ end trace 0000000000000001 ]---

Nevertheless it does boot, and seems to work fine.


Thanks,
-- 
Jean-Denis Girard

SysNux                Systèmes   Linux   en   Polynésie   française
http://www.sysnux.pf/ Tél: +689 40.50.10.40 / GSM: +689 87.79.75.27

  reply	other threads:[~2016-03-09 20:31 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-09 13:51 [ANNOUNCE] v4.4.4-rt11 Sebastian Andrzej Siewior
2016-03-09 20:31 ` Jean-Denis Girard [this message]
2016-03-11 17:14   ` Sebastian Andrzej Siewior
2016-03-11 17:14     ` Sebastian Andrzej Siewior
2016-03-12  1:56     ` Jean-Denis Girard
2016-03-12  1:56       ` Jean-Denis Girard
2016-03-29 11:12       ` Sebastian Andrzej Siewior

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='nbq16a$7li$1@ger.gmane.org' \
    --to=jd.girard@sysnux.pf \
    --cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.