Yes that's right Mulyadi, As this was my first encounter with ksymoops
hence i didn't know much about it. Last night i was going through the
back trace for this oops and got lost while trying to figure the root cause
Keeping track of function calls in large project can be
very perplexing. Right now
Hi...
On Thu, Apr 23, 2009 at 2:29 PM, amit mehta wrote:
> Thanks for your replies, i just wanted to know how to debug
> such kernel OOPS, Forget about this particular OOPS, i just wanted to know
> how you proceed further when you get something similar. As Ramesh told,
> 'ksymoops' can be
> helpf
Thanks for your replies, i just wanted to know how to debug
such kernel OOPS, Forget about this particular OOPS, i just wanted to know
how you proceed further when you get something similar. As Ramesh told,
'ksymoops' can be
helpful.
__amit
On Thu, Apr 23, 2009 at 11:18 AM, Himanshu Chauhan wrote
> is that the whole message? please post the complete one so we all get
> the complete picture.
>
> However, briefly, i think the oops was started due to some bugs in one
> or more kernel threads (see kernel_thread_helper there?). BTW,
> scst...hmmm, SCSI module?
>
Hi Mulyadi,
Ya that is not c
On Wed, Apr 22, 2009 at 11:34 PM, amit mehta wrote:
> Hi,
>
> I'm getting following OOPS on one of my Linux box.
> Its related with one of a loadable module. To proceed further from here, I
> need generic
> suggestion/pointers for debugging kernel OOPS.
>
>
> [] apic_timer_interrupt+0x28/0x30
>
Hi Amit,
You didn't provide the full OOPs message.
On Wed, 2009-04-22 at 22:04 +0530, amit mehta wrote:
>
>
> [] apic_timer_interrupt+0x28/0x30
> [] scst_cmd_thread+0x9c/0xfc [scst]
> [] default_wake_function+0x0/0x8
> [] scst_cmd_thread+0x0/0xfc [scst]
> [] kthread+0x38/0x5d
> [] kthr
You could run a 'ksymoops' against the trace that that most of the
time gives you the point of crash.
On Wed, Apr 22, 2009 at 9:34 AM, amit mehta wrote:
> Hi,
>
> I'm getting following OOPS on one of my Linux box.
> Its related with one of a loadable module. To proceed further from here, I
> need
Hi,
I'm getting following OOPS on one of my Linux box.
Its related with one of a loadable module. To proceed further from here, I
need generic
suggestion/pointers for debugging kernel OOPS.
[] apic_timer_interrupt+0x28/0x30
[] scst_cmd_thread+0x9c/0xfc [scst]
[] default_wake_function+0x0/0x8
