Messages in this thread | | On Mon, Feb 1, 2010 at 2:05 PM, Jason Wessel <jason.wessel@windriver.co= m> 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: >>> =C2=A0 =C2=A0 =C2=A0 =C2=A0local_irq_disable(); >>> =C2=A0 =C2=A0 =C2=A0 =C2=A0printk("Disable local irq for 11 seconds= \n"); >>> =C2=A0 =C2=A0 =C2=A0 =C2=A0mdelay(11000); >>> =C2=A0 =C2=A0 =C2=A0 =C2=A0local_irq_enable(); >>> >> >> Hi Jason, >> >> Maybe this problem was fixed by >> commit baf48f6577e581a9adb8fe849dc80e24b21d171d - "softlock: fix fal= se >> panic which can occur if softlockup_thresh is reduced". >> > > > That is not the same problem. =C2=A0 The fix you referenced is a corn= er case > where you end up with the stack trace at the point in time you reduce > the threshold. =C2=A0The only reason I reduce the threshold in the fi= rst > place is just to shorten the amount of time it takes to observe the p= roblem.
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. > -- To unsubscribe from this list: send the line "unsubscribe linux-kernel"= in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |