[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <DC09270D-6A7A-4FE3-A99C-CE84F1F64697@gmail.com>
Date: Wed, 21 Oct 2015 21:16:31 +0900
From: Jungseok Lee <jungseoklee85@...il.com>
To: AKASHI Takahiro <takahiro.akashi@...aro.org>
Cc: Catalin Marinas <catalin.marinas@....com>,
Will Deacon <will.deacon@....com>,
James Morse <james.morse@....com>,
Mark Rutland <mark.rutland@....com>, broonie@...nel.org,
david.griego@...aro.org, linux-arm-kernel@...ts.infradead.org,
"linux-kernel@...r.kernel.org List" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v2 1/2] arm64: revamp unwind_frame for interrupt stack
On Oct 21, 2015, at 9:14 PM, Jungseok Lee wrote:
Whoops!
> [Only Akashi and James]
>
> On Oct 21, 2015, at 3:38 PM, AKASHI Takahiro wrote:
>
> Hi Akashi and James,
>
> Am I the only person who have experienced kernel panic with this series?
> I have observed NULL pointer kernel panic with the following two ways.
>
> - $ sudo echo c > /proc/sysrq-trigger
> - perf record -e mem:[address of do_softirq]:x -ag -- sleep 2
>
> The kernel panic is triggered when the last stack frame of swapper is unwound.
> At that time, the value of fp, low, high is 0, 0, 0, respectively.
>
> My tree includes "Synchronise dump_backtrace() with perf call chain" patch
> which is queued into for-next/core.
>
> Best Regards
> Jungseok Lee
Really sorry for the noise.. It won't happen again..
Best Regards
Jungseok Lee--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists