Kernel OOPS analysis

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

 



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>


Apparently 'schedule' is throwing this message:

if (unlikely(in_atomic() && !current->exit_state)) {
      printk(KERN_ERR "BUG: scheduling while atomic: "
         "%s/0x%08x/%d\n",
         current->comm, preempt_count(), current->pid);
      debug_show_held_locks(current)
;
      if (irqs_disabled())
         print_irqtrace_events(current);
      dump_stack();
   }

__amit

--
"Everyone has a photographic memory. Some people just don't have film."

— Mel Brooks

[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