Re: Meet the bugs for linux-3.19-rc4 on aarch64 board

2015-02-04 Thread Ding Tianhong
On 2015/2/5 1:09, Catalin Marinas wrote: > On Wed, Feb 04, 2015 at 03:17:25PM +, Ding Tianhong wrote: >> bad mode in Synchronous Abort handler detected, code 0x8605 >> CPU: 1 PID: 381 Comm: kworker/1:1 Tainted: G O 3.19.0-rc4+ #6 >> Hardware name: Hisilicon Board ESL (DT) >> Wor

Re: Meet the bugs for linux-3.19-rc4 on aarch64 board

2015-02-04 Thread Will Deacon
On Wed, Feb 04, 2015 at 05:09:51PM +, Catalin Marinas wrote: > On Wed, Feb 04, 2015 at 03:17:25PM +, Ding Tianhong wrote: > > bad mode in Synchronous Abort handler detected, code 0x8605 > > CPU: 1 PID: 381 Comm: kworker/1:1 Tainted: G O 3.19.0-rc4+ #6 > > Hardware name: Hisi

Re: Meet the bugs for linux-3.19-rc4 on aarch64 board

2015-02-04 Thread Catalin Marinas
On Wed, Feb 04, 2015 at 03:17:25PM +, Ding Tianhong wrote: > bad mode in Synchronous Abort handler detected, code 0x8605 > CPU: 1 PID: 381 Comm: kworker/1:1 Tainted: G O 3.19.0-rc4+ #6 > Hardware name: Hisilicon Board ESL (DT) > Workqueue: events (null) > task: ffc

Meet the bugs for linux-3.19-rc4 on aarch64 board

2015-02-04 Thread Ding Tianhong
Hi everyone: I run the linux-3.16 for aarch64 on my board, and it work fine, but when I try to update the kernel to linux-3.19-rc4, I met the problem just below: ad mode in Synchronous Abort handler detected, code 0x8605

Linux 3.19-rc4

2015-01-11 Thread Linus Torvalds
3): mm: propagate error from stack expansion even for guard page mm: Don't count the stack guard page towards RLIMIT_STACK linux 3.19-rc4 Luca Abeni (2): sched/deadline: Fix migration of SCHED_DEADLINE tasks sched/deadline: Avoid double-accounting in case of missed