Hi Andrew,
Thanks for the review.
On Mon, Nov 26, 2018 at 03:24:57PM -0800, Andrew Morton wrote:
> On Thu, 22 Nov 2018 15:10:31 +0800 Feng Tang wrote:
>
> > Kernel panic issues are always painful to debug, partially
> > because of it's not easy to get enough information of the
> > context when
Hi Andrew,
Thanks for the review.
On Mon, Nov 26, 2018 at 03:24:57PM -0800, Andrew Morton wrote:
> On Thu, 22 Nov 2018 15:10:31 +0800 Feng Tang wrote:
>
> > Kernel panic issues are always painful to debug, partially
> > because of it's not easy to get enough information of the
> > context when
On Thu, 22 Nov 2018 15:10:31 +0800 Feng Tang wrote:
> Kernel panic issues are always painful to debug, partially
> because of it's not easy to get enough information of the
> context when panic happens.
>
> And we have ramoops and kdump for that, while this commit
> tries to a easier way to
On Thu, 22 Nov 2018 15:10:31 +0800 Feng Tang wrote:
> Kernel panic issues are always painful to debug, partially
> because of it's not easy to get enough information of the
> context when panic happens.
>
> And we have ramoops and kdump for that, while this commit
> tries to a easier way to
Kernel panic issues are always painful to debug, partially
because of it's not easy to get enough information of the
context when panic happens.
And we have ramoops and kdump for that, while this commit
tries to a easier way to show the system info by adding a
cmdline parameter, referring some
Kernel panic issues are always painful to debug, partially
because of it's not easy to get enough information of the
context when panic happens.
And we have ramoops and kdump for that, while this commit
tries to a easier way to show the system info by adding a
cmdline parameter, referring some
6 matches
Mail list logo
