On Tue, Nov 08, 2016 at 05:52:03PM +0800, 蒋雄伟(蒋冲) wrote:
> Hi,all
>
> We encountered the following panic in 2.6.32 and 3.10.0:
Can you reproduce using anything recent? I've really no idea what any of
those kernels looked like. That's ancient software.
Hi,all
We encountered the following panic in 2.6.32 and 3.10.0:
BUG: unable to handle kernel NULL pointer dereference at 0010
IP: [] rb_next+0x1/0x50
Call Trace:
? pick_next_task_fair+0x129/0x1d0
[] __schedule+0x12a/0x910
[] schedule+0x29/0x70
[] futex_wait_queue_me+0xc4/0x12
one more info as following before crash.
[83321.794602] c1 230 (DispSync) BUG: Bad rss-counter state
mm:ec376200 idx:0 val:2497
[83321.795281] c0 2084 (v.airplayserver) Unable to handle kernel NULL
pointer dereference at virtual address 0008
2014-12-29 9:56 GMT+08:00 Neil Zhang :
> Does anyone
Does anyone ever encountered it?
Please give your help if any.
Thanks in advanced!
Best Regards,
Neil Zhang
2014-12-26 17:37 GMT+08:00 Neil Zhang :
> Hi All,
> I encountered the following crash in 3.10.24.
>
> The panic log is as following.
> The strange thing is that the nr_running change to NU
Hi All,
I encountered the following crash in 3.10.24.
The panic log is as following.
The strange thing is that the nr_running change to NULL after pass the
check in the beginning of pick_next_task_fair.
So it seems there are race condition in the code.
Seems no related patch to fix it in the mainl
5 matches
Mail list logo