Re: [ANNOUNCE] v4.4.4-rt11
On 2016-03-11 15:56:59 [-1000], Jean-Denis Girard wrote: > Hi, Hi, > Here are the interrupts, I hope this is what you want: > jdg@arietta:~$ cat /proc/interrupts >CPU0 > 16: 145825 atmel-aic 1 Level at91_rtc, ttyS0 Yes, thank you. This means that the IRQ can be re-used. Now we need to rid of the warning :) Sebastian
Re: [ANNOUNCE] v4.4.4-rt11
Hi, Le 11/03/2016 07:14, Sebastian Andrzej Siewior a écrit : > This looks promising. Can you check if IRQ 16 is used by another > peripherals? While we need get rid fo the warning I am curious if it > works on boards which chare the timer with UART or something. Here are the interrupts, I hope this is what you want: jdg@arietta:~$ cat /proc/interrupts CPU0 16: 145825 atmel-aic 1 Level at91_rtc, ttyS0 17: 45661872 atmel-aic 17 Level tc_clkevt 18: 72014 atmel-aic 20 Level at_hdmac 19: 0 atmel-aic 21 Level at_hdmac 23:2541144 atmel-aic 12 Level f0008000.mmc 26: 0 atmel-aic 10 Level f8014000.i2c 27: 0 atmel-aic 19 Level at91_adc 28: 0 atmel-aic 14 Level f0004000.spi 31: 1 atmel-aic 22 Level ehci_hcd:usb1, ohci_hcd:usb2 Err: 0 The Arietta has been working fine for a couple of days with this kernel: jdg@arietta:~$ uname -r 4.4.4-rt11 jdg@arietta:~$ uptime 14:30:06 up 2 days, 4:04, 1 user, load average: 0.00, 0.02, 0.05 Thanks, -- Jean-Denis Girard SysNuxSystèmes Linux en Polynésie française http://www.sysnux.pf/ Tél: +689 40.50.10.40 / GSM: +689 87.79.75.27
Re: [ANNOUNCE] v4.4.4-rt11
On 2016-03-09 10:31:06 [-1000], Jean-Denis Girard wrote: > Hi, Hi, please don't cut people from TO and CC. > 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: 0xfff max_cycles: 0xfff, 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 … > Nevertheless it does boot, and seems to work fine. This looks promising. Can you check if IRQ 16 is used by another peripherals? While we need get rid fo the warning I am curious if it works on boards which chare the timer with UART or something. > Thanks, Sebastian
Re: [ANNOUNCE] v4.4.4-rt11
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: 0xfff max_cycles: 0xfff, 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 [] (unwind_backtrace) from [] (show_stack+0x10/0x14) [] (show_stack) from [] (warn_slowpath_common+0x80/0xa8) [] (warn_slowpath_common) from [] (warn_slowpath_fmt+0x2c/0x3c) [] (warn_slowpath_fmt) from [] (__free_irq+0xb0/0x2b0) [] (__free_irq) from [] (free_irq+0x40/0x50) [] (free_irq) from [] (pit_clkevt_shutdown+0x24/0x2c) [] (pit_clkevt_shutdown) from [] (clockevents_switch_state+0xe8) [] (clockevents_switch_state) from [] (clockevents_shutdown+0x1) [] (clockevents_shutdown) from [] (tick_check_new_device+0x54/0) [] (tick_check_new_device) from [] (clockevents_register_device) [] (clockevents_register_device) from [] (clocksource_probe+0x4) [] (clocksource_probe) from [] (start_kernel+0x248/0x35c) [] (start_kernel) from [<20008048>] (0x20008048) ---[ end trace 0001 ]--- Nevertheless it does boot, and seems to work fine. Thanks, -- Jean-Denis Girard SysNuxSystèmes Linux en Polynésie française http://www.sysnux.pf/ Tél: +689 40.50.10.40 / GSM: +689 87.79.75.27