Re: [PATCH v2] panic: Add options to print system info when panic happens

2018-11-27 Thread Feng Tang
Hi Steven, On Tue, Nov 27, 2018 at 01:23:18PM -0500, Steven Rostedt wrote: > On Tue, 27 Nov 2018 15:15:20 +0800 > Feng Tang wrote: > > > Kernel panic issues are always painful to debug, partially > > because it's not easy to get enough information of the > > context when panic happens. > > > >

Re: [PATCH v2] panic: Add options to print system info when panic happens

2018-11-27 Thread Steven Rostedt
On Tue, 27 Nov 2018 15:15:20 +0800 Feng Tang wrote: > Kernel panic issues are always painful to debug, partially > because 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 provide a easier way to

Re: [PATCH v2] panic: Add options to print system info when panic happens

2018-11-27 Thread Kees Cook
On Mon, Nov 26, 2018 at 11:15 PM, Feng Tang wrote: > Kernel panic issues are always painful to debug, partially > because 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 provide a easier way to sh

[PATCH v2] panic: Add options to print system info when panic happens

2018-11-26 Thread Feng Tang
Kernel panic issues are always painful to debug, partially because 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 provide a easier way to show the system info by adding a cmdline parameter, referring som