Re: 3.18.1->3.19-rc2: In-band Error seen by MPU

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 





Am 02.01.2015 um 17:19 schrieb Tony Lindgren:
* Aaro Koskinen <aaro.koskinen@xxxxxx> [150101 10:23]:
Hi,

On Thu, Jan 01, 2015 at 07:12:51PM +0100, Peter Kümmel wrote:
When updating (custom DM3730 board) from 3.18.1 ro 3.19-rc2
I see a "In-band ERROR" warning which wasn't present in 3.18.1.
Could it be that I missed some DT updates?

[    0.366882] In-band Error seen by MPU  at address 0
[    0.366912] ------------[ cut here ]------------
[    0.366943] WARNING: CPU: 0 PID: 1 at drivers/bus/omap_l3_smx.c:166 omap3_l3_app_irq+0x100/0x134()

This appears also on N900/N950/N9...

Do you have CONFIG_PREEMPT enabled? It seems there's some
regression related to CONFIG_PREEMPT that started happening
with the merge window?

Indeed, when I disable CONFIG_PREEMPT the warning is gone.

Thanks,
Peter


Regards,

Tony
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html



[Index of Archives]     [Linux Arm (vger)]     [ARM Kernel]     [ARM MSM]     [Linux Tegra]     [Linux WPAN Networking]     [Linux Wireless Networking]     [Maemo Users]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite Trails]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux