[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <a8dc0b1f-7f2a-db5b-87fa-37d61adcf03b@gmail.com>
Date: Fri, 14 Oct 2016 22:04:19 +1100
From: Balbir Singh <bsingharora@...il.com>
To: Abdul Haleem <abdhalee@...ux.vnet.ibm.com>,
linuxppc-dev@...ts.ozlabs.org, linux-kernel@...r.kernel.org,
mpe@...erman.id.au, ego@...ux.vnet.ibm.com,
aneesh.kumar@...ux.vnet.ibm.com
Subject: Re: [PowerPC] Kernel panic while running CPU toggle test on 4.8.0
kernel
On 14/10/16 17:24, Abdul Haleem wrote:
> Hi,
>
> Kernel Oops, followed by kernel panic seen while running rcutorture test on 4.8.0 kernel
> Machine Type : PowerPC Bare Metal
>
> RCU torture test steps:
> 1. modprobe rcutorture
> 2. start CPU offline and online while torture test is running
>
> dmesg start flooded with Oops messages following kernel panic resulted in machine reboot.
Good bug. The report looks good
Any chance you could add ftrace_dump_on_oops to command line and start this test
with tracing enabled? Otherwise, getting the line via addr2line of select_task_rq_fair+0xac8/0xca0
would be helpful.
It would also be nice to know the CFAR value (CFAR: c0000000000089e0) using
addr2line
Balbir Singh.
Powered by blists - more mailing lists