I was just wondering if how you resolved this issue? Did you apply a specific patch?
From a kernalnewbie perspective, this is a very generic error, and happens quite frequently(From my limited searches). So for us all to learn, what should we look for in the backtrace? The last calling function? Does this mean the last calling function is in some bad loop and that is where the issue is?
Just trying to learn and help other to learn :-)
Joe
On Tue, Jun 29, 2010 at 1:52 AM, sanjeev sharma <sanjeevsharmaengg@xxxxxxxxx> wrote:
I think this is an also specific to an Application also.Some patches has been introduce by Kernel guys to fix
This seems an issue with softlock ups in kernel.According to the kernel sources
(kernel/softlockup.c) the error "soft lockup detected" means a CPU in kernel
code didn't reschedule for 10 seconds or more (watchdog timeout). It may be
caused by driver code that processes hardware interrupts for more than 10
seconds without rescheduling other threads.
soft lockup in kernel.
Regards
sanjeev shrmaOn Sat, Jun 26, 2010 at 3:43 PM, Harishkumar V <harishpresent@xxxxxxxxx> wrote:
Hi,
I am facing "BUG: soft lockup - CPU#0 stuck for 61s!" problem. when i browsed through google, it appears to be general problem, but there is no workaround/solution exists. Any pointers how to trace this or fix this would be helpful.
--
Thanks and Regards,
Harish Kumar. V
