From: pradeep4uiiita@gmail.com (Pradeep Kumar)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Regarding CPU softlockup issue
Date: Tue, 28 Dec 2010 15:55:58 +0530 [thread overview]
Message-ID: <AANLkTikhX6Rkjt6x-1SEKKz25c8ecMtvBLQEVLDnUELM@mail.gmail.com> (raw)
hi all,
I got the fallowing soft lockup error
"BUG: soft lockup - CPU#0 stuck for 16s! [Playback Thread:9266"]
is that 16s is the value of /proc/sys/kernel/softlockup_thresh ??
if yes, can I get rid of that message/panic by setting softlockup_thresh to
some value greater that 30 ???
--
Goudagunta Pradeep Kumar,
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20101228/6c54d6cc/attachment.html
next reply other threads:[~2010-12-28 10:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-28 10:25 Pradeep Kumar [this message]
2010-12-28 10:30 ` Fwd: Regarding CPU softlockup issue Pradeep Kumar
2010-12-28 11:37 ` Mulyadi Santosa
2010-12-28 19:35 ` Manish Katiyar
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=AANLkTikhX6Rkjt6x-1SEKKz25c8ecMtvBLQEVLDnUELM@mail.gmail.com \
--to=pradeep4uiiita@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).