t;
> 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
>
Hi!
On 21:47 Sun 27 Jun , Harishkumar V wrote:
> hi,
>
> oh is it, can u explain, how to find out it.which portion of the code. i
> see only this,
The point is that even tough the stack trace usually contains the right trace,
this one does not. This is why I have suggested trfing to repr
Hi,
can u guide how to debug this and have an fix/workaround for this.
i see softlockup_tick and many funtions in the trace message. how to
pinpoint where it got struck.
On Sun, Jun 27, 2010 at 9:47 PM, Harishkumar V wrote:
> hi,
>
> oh is it, can u explain, how to find out it.which portion
hi,
oh is it, can u explain, how to find out it.which portion of the code. i
see only this,
handle_IRQ_event+0x28/0x74
LR is at handle_level_irq+0x94/0xec
pc : []lr : []psr: 48000113
sp : c7eede90 ip : c7eedeb0 fp : c7eedeac
r10: 001d r9 : c0638ba8 r8 :
r7 : 005c
Hi!
On 14:09 Sun 27 Jun , Harishkumar V wrote:
> MMU is available in ARM.
>
> if the same(cpu softlockup) exists on x86, how to handle this, u told in
> earlier mail,
>
> "This is only the stack trace of the softlockup check, not the code which
> got stuck", how to find out at which point, t
MMU is available in ARM.
if the same(cpu softlockup) exists on x86, how to handle this, u told in
earlier mail,
"This is only the stack trace of the softlockup check, not the code which
got stuck", how to find out at which point, the code got struck, in x86.
On Sun, Jun 27, 2010 at 11:47 AM, Mic
Hi!
Yes, please make sure that you have CONFIG_KALLSYM and CONFIG_FRAME_POINTER
enabled. However, I guess you already do have them enabled, because probably
you would not have seen any stacktrace otherwise. I do not know what else to
enable.
BTW: Is your system a nommu one?
-Michi
On 09
if i enable CONFIG_KALLSYMS, will it be useful
On Sun, Jun 27, 2010 at 9:00 AM, Harishkumar V wrote:
> Hi,
>
> is any kernel option to enable capture stack trace for code struck in x86.
> how to capture this on x86.
>
>
> i can cross verify the option with the ARM kernel configuration.
>
> On Sun
Hi,
is any kernel option to enable capture stack trace for code struck in x86.
how to capture this on x86.
i can cross verify the option with the ARM kernel configuration.
On Sun, Jun 27, 2010 at 8:52 AM, Harishkumar V wrote:
> Hi,
>
> is any kernel option to enable to capture stack trace in x8
Hi,
is any kernel option to enable to capture stack trace in x86. how to capture
this on x86.
i can cross verify the option with the ARM kernel configuration.
On Sat, Jun 26, 2010 at 9:40 PM, Michael Blizek <
mic...@michaelblizek.twilightparadox.com> wrote:
> Hi!
>
> On 17:15 Sat 26 Jun , H
Hi!
On 17:15 Sat 26 Jun , Harishkumar V wrote:
> Hi,
>
> this is the one, i am getting in the console,
...
This is only the stack trace of the softlockup check, not the code which got
stuck. I am not sure whether generating that stack trace on arm is possible.
Can you reproduce this on x86 o
Hi,
this is the one, i am getting in the console,
BUG: soft lockup - CPU#0 stuck for 61s! [linphone-3:764]
Modules linked in:
Pid: 764, comm: linphone-3
CPU: 0Not tainted (2.6.28-rc9 #14)
PC is at handle_IRQ_event+0x28/0x74
LR is at handle_level_irq+0x94/0xec
pc : []lr
Hi!
On 12:13 Sat 26 Jun , Harishkumar V 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 th
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
15 matches
Mail list logo
