On Tue, Nov 19, 2013 at 1:15 AM, Ingo Molnar wrote:
>
> * Andrew Morton wrote:
>
>> On Mon, 18 Nov 2013 21:04:36 + (GMT) Jason Baron
>> wrote:
>>
>> > The panic_timeout value can be set via the command line option 'panic=x',
>> > or via
>> > /proc/sys/kernel/panic, however that is not suff
On Tue, Nov 19, 2013 at 05:04:14PM -0500, Jason Baron wrote:
> On 11/19/2013 02:09 AM, Ingo Molnar wrote:
> >
> > * Jason Baron wrote:
> >
> >> On 11/18/2013 05:30 PM, Andrew Morton wrote:
> >>> On Mon, 18 Nov 2013 21:04:36 + (GMT) Jason Baron
> >>> wrote:
> >>>
> The panic_timeout va
On Tue, Nov 19, 2013 at 10:02:11AM +0100, Ralf Baechle wrote:
> On Mon, Nov 18, 2013 at 09:04:36PM +, Jason Baron wrote:
>
> > The panic_timeout value can be set via the command line option 'panic=x',
> > or via
> > /proc/sys/kernel/panic, however that is not sufficient when the panic occurs
On Tue, Nov 19, 2013 at 12:11:29PM -0500, Jason Baron wrote:
> > I propose to kill these overrides for sanity unless somebody comes up
> > with a good argument. Patch below.
> >
>
> And so have the mips default be 0? IE drop the arch/mips/Kconfig bits from
> the patch I posted? (Which could of
On 11/19/2013 04:02 AM, Ralf Baechle wrote:
> On Mon, Nov 18, 2013 at 09:04:36PM +, Jason Baron wrote:
>
>> The panic_timeout value can be set via the command line option 'panic=x', or
>> via
>> /proc/sys/kernel/panic, however that is not sufficient when the panic occurs
>> before we are able
On Tue, Nov 19, 2013 at 11:51:27PM +0900, Shinya Kuribayashi wrote:
> IIRC we had set it to 180 seconds for some historical reasons, but
> I'm afraid nobody can recall the reason why it's set so in 2013...
> Anyway I was thinking it too long and reduced to a few seconds locally
> when debugging, s
On 11/19/13 6:02 PM, Ralf Baechle wrote:> On Mon, Nov 18, 2013 at 09:04:36PM
+, Jason Baron wrote:
It's more complicated - MIPS was using the global default with five MIPS
platforms overriding the default.
I propose to kill these overrides for sanity unless somebody comes up
with a good arg
On Mon, Nov 18, 2013 at 09:04:36PM +, Jason Baron wrote:
> The panic_timeout value can be set via the command line option 'panic=x', or
> via
> /proc/sys/kernel/panic, however that is not sufficient when the panic occurs
> before we are able to set up these values. Thus, add a CONFIG_PANIC_TI
On Mon, 18 Nov 2013 21:04:36 + (GMT) Jason Baron wrote:
> The panic_timeout value can be set via the command line option 'panic=x', or
> via
> /proc/sys/kernel/panic, however that is not sufficient when the panic occurs
> before we are able to set up these values. Thus, add a CONFIG_PANIC_TI
The panic_timeout value can be set via the command line option 'panic=x', or via
/proc/sys/kernel/panic, however that is not sufficient when the panic occurs
before we are able to set up these values. Thus, add a CONFIG_PANIC_TIMEOUT
so that we can set the desired value from the .config.
The defau
10 matches
Mail list logo