Re: Kernel OOPS analysis

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Wed, Apr 22, 2009 at 11:34 PM, amit mehta <amit4g@xxxxxxxxx> 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.
>
>  <snip>
>  [<c0104878>] apic_timer_interrupt+0x28/0x30
>  [<f8e2d06f>] scst_cmd_thread+0x9c/0xfc [scst]
>  [<c011bbed>] default_wake_function+0x0/0x8
>  [<f8e2cfd3>] scst_cmd_thread+0x0/0xfc [scst]
>  [<c012f5fa>] kthread+0x38/0x5d
>  [<c012f5c2>] kthread+0x0/0x5d
>  [<c0104a37>] kernel_thread_helper+0x7/0x10
>  =======================
>  <snip>

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?

regards,

Mulyadi.

--
To unsubscribe from this list: send an email with
"unsubscribe kernelnewbies" to ecartis@xxxxxxxxxxxx
Please read the FAQ at http://kernelnewbies.org/FAQ



[Index of Archives]     [Newbies FAQ]     [Linux Kernel Mentors]     [Linux Kernel Development]     [IETF Annouce]     [Git]     [Networking]     [Security]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux RAID]     [Linux SCSI]     [Linux ACPI]
  Powered by Linux