Re: [PATCH 1/3] softlockup: add sched_clock_tick() to avoid kernel warning on kgdb resume

[Dongdong Deng <libfetion@gmail.com>]

On Mon, Feb 1, 2010 at 2:05 PM, Jason Wessel <jason.wessel@windriver.com> wrote:
> Dongdong Deng wrote:
>> On Fri, Jan 29, 2010 at 10:51 PM, Jason Wessel
>> <jason.wessel@windriver.com> wrote:
>>
>>> echo 3 > /proc/sys/kernel/softlockup_thresh
>>>
>>> And then some kernel code in a thread like:
>>>        local_irq_disable();
>>>        printk("Disable local irq for 11 seconds\n");
>>>        mdelay(11000);
>>>        local_irq_enable();
>>>
>>
>> Hi Jason,
>>
>> Maybe this problem was fixed by
>> commit baf48f6577e581a9adb8fe849dc80e24b21d171d - "softlock: fix false
>> panic which can occur if softlockup_thresh is reduced".
>>
>
>
> That is not the same problem.   The fix you referenced is a corner case
> where you end up with the stack trace at the point in time you reduce
> the threshold.  The only reason I reduce the threshold in the first
> place is just to shorten the amount of time it takes to observe the problem.

Thanks for your nice explanation. :)

Dongdong

> You can just change the numbers for the mdelay and use the default
> softlockup threshold values and still see the problem I reported.
>
> Jason.
>