All of lore.kernel.org
 help / color / mirror / Atom feed
From: fjohnber@zoho.com (Fredrick)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Softlock OOPS dump
Date: Mon, 06 Feb 2012 19:07:36 -0800	[thread overview]
Message-ID: <4F309578.2030600@zoho.com> (raw)
In-Reply-To: <CACsJYqrBtvLYM0dHLhM1WVyn_+W4t9DBBuk03kAw70+DpW4kyg@mail.gmail.com>

On 02/05/2012 11:13 PM, devendra rawat wrote:
>
> Hi All,
>
> I am having a PPC system running Windriver linux. System is restarting
> because of watchdog.
> System was restated because no scheduling took place for 15.7 seconds. I
> want to figure out which function/ISR/routine
> was the kernel executing when this softlockup happened and at what place
> was the execution going. The NIP (next instruction pointer) reg. is not
> giving the
> symbol name as the "switch" module that created the problem was
> dynamically loaded.
> Can anybody help in figuring out the exact routine that may be behind
> the lockup.
>
>   I am getting the following OOPS.
>
>
>
> cpu0: jiffies: 1903983223, hrtime: 16746998586843980, 15756 ms between
> scheduler_tick() calls
>   31/12/1969 EST 19:00:00, BUG: soft lockup detected on CPU#0!
> 31/12/1969 EST 19:00:00, NIP: C0041FAC LR: C0042320 SP: C71AFB10 REGS:
> c71afa60 TRAP: 0901    Tainted: P
>   31/12/1969 EST 19:00:00, MSR: 00009032 EE: 1 PR: 0 FP: 0 ME: 1 IR/DR: 11
>   31/12/1969 EST 19:00:00, TASK = cef2c880[1224] 'switch' THREAD: c71ae000
>   31/12/1969 EST 19:00:00, Last syscall: 54
>   31/12/1969 EST 19:00:00,
> 31/12/1969 EST 19:00:00, GPR00:
> 31/12/1969 EST 19:00:00, C017D5E4
> 31/12/1969 EST 19:00:00, C71AFB10
> 31/12/1969 EST 19:00:00, CEF2C880
> 31/12/1969 EST 19:00:00, 00000020
>   31/12/1969 EST 19:00:00, C71AFC20
> 31/12/1969 EST 19:00:00, D04C7F80
> 31/12/1969 EST 19:00:00, C036A774
>   31/12/1969 EST 19:00:00, 0000001C
> 31/12/1969 EST 19:00:00,
> 31/12/1969 EST 19:00:00, GPR08:
> 31/12/1969 EST 19:00:00, C036BF48
>   31/12/1969 EST 19:00:00, 00000000
> 31/12/1969 EST 19:00:00, 0000F10C
> 31/12/1969 EST 19:00:00, 00000000
> 31/12/1969 EST 19:00:00, 2410C042
> 31/12/1969 EST 19:00:00,
> 31/12/1969 EST 19:00:00, NIP [c0041fac]
> 31/12/1969 EST 19:00:00, handle_IRQ_event+0x254/0x4d4
>   31/12/1969 EST 19:00:00, LR [c0042320]
> 31/12/1969 EST 19:00:00, __do_IRQ+0xf4/0x164
> 31/12/1969 EST 19:00:00, Call trace
> 31/12/1969 EST 19:00:00,
> 31/12/1969 EST 19:00:00,  [c0042320]
> 31/12/1969 EST 19:00:00, __do_IRQ+0xf4/0x16
> 31/12/1969 EST 19:00:00,
>   31/12/1969 EST 19:00:00,  [c0006c64]
> 31/12/1969 EST 19:00:00, do_IRQ+0x54/0x10
> 31/12/1969 EST 19:00:00,
>   31/12/1969 EST 19:00:00,  [c0005214]
>   31/12/1969 EST 19:00:00, ret_from_except+0x0/0x1
> 31/12/1969 EST 19:00:00,
>   31/12/1969 EST 19:00:00,  [e10cbc7c]
> 31/12/1969 EST 19:00:00, bcm_bsa_request+0x189c/0x4140 [bcm5690
>   31/12/1969 EST 19:00:00,
> 31/12/1969 EST 19:00:00,  [e10d09a8]
> 31/12/1969 EST 19:00:00, bcm_ioctl+0x144/0x480 [bcm5690
> 31/12/1969 EST 19:00:00,
> 31/12/1969 EST 19:00:00,  [c0087764]
> 31/12/1969 EST 19:00:00, do_ioctl+0x68/0x9
>   31/12/1969 EST 19:00:00,
> 31/12/1969 EST 19:00:00,  [c0087850]
> 31/12/1969 EST 19:00:00, vfs_ioctl+0xb8/0x40
> 31/12/1969 EST 19:00:00,
> 31/12/1969 EST 19:00:00,  [c0087e00]
> 31/12/1969 EST 19:00:00, sys_ioctl+0x268/0x38
> 31/12/1969 EST 19:00:00,
> 31/12/1969 EST 19:00:00,  [c0004a1c]
> 31/12/1969 EST 19:00:00, DoSyscall_no_dpa_entry+0x74/0x9
>
> /*****************************/
>
> Thanks in advance.
> Devendra.
>
>



It could be getting stuck in the ioctl bcm_ioctl->bcm_bsa_request+0x189c

-Fredrick

>
>
> _______________________________________________
> Kernelnewbies mailing list
> Kernelnewbies at kernelnewbies.org
> http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

      parent reply	other threads:[~2012-02-07  3:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-06  7:13 Softlock OOPS dump devendra rawat
2012-02-06  7:45 ` Mulyadi Santosa
2012-02-07  3:07 ` Fredrick [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4F309578.2030600@zoho.com \
    --to=fjohnber@zoho.com \
    --cc=kernelnewbies@lists.kernelnewbies.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.