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, Michael Blizek <michi1@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
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:10 Sun 27 Jun , Harishkumar V wrote:
> if i enable CONFIG_KALLSYMS, will it be useful
>
> On Sun, Jun 27, 2010 at 9:00 AM, Harishkumar V <harishpresent@xxxxxxxxx>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, Jun 27, 2010 at 8:52 AM, Harishkumar V <harishpresent@xxxxxxxxx>wrote:
> >
> >> 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 <
> >> michi1@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
> >>
> >>> 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 or is it an arm-only error? If it is
> >>> related
> >>> to arm, not, check the kernel configuration whether there are any
> >>> relevant
> >>> options for generating stack traces or ask on linux-arm-kernel (see
> >>> http://kernelnewbies.org/ML ).
> >>>
> >>> -Michi
> >>> --
> >>> programing a layer 3+4 network protocol for mesh networks
> >>> see http://michaelblizek.twilightparadox.com
> >>>
> >>>
> >>
> >>
> >> --
> >> Thanks and Regards,
> >> Harish Kumar. V
> >>
> >
> >
> >
> > --
> > Thanks and Regards,
> > Harish Kumar. V
> >
>
>
>
> --
> Thanks and Regards,
> Harish Kumar. V
programing a layer 3+4 network protocol for mesh networks
see http://michaelblizek.twilightparadox.com
--
Thanks and Regards,
Harish Kumar. V
