From: Thomas Gleixner <tglx@linutronix.de>
To: Parag Warudkar <parag.warudkar@gmail.com>
Cc: Arjan van de Ven <arjan@infradead.org>,
Ingo Molnar <mingo@elte.hu>,
"Pallipadi, Venkatesh" <venkatesh.pallipadi@intel.com>,
LKML <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: soft lockup - CPU#1 stuck for 15s! [swapper:0]
Date: Mon, 10 Dec 2007 11:19:50 +0530 (IST) [thread overview]
Message-ID: <alpine.LFD.0.99999.0712101117300.11977@localhost.localdomain> (raw)
In-Reply-To: <82e4877d0712091357u41973a24v38c4ad18ad596de5@mail.gmail.com>
On Sun, 9 Dec 2007, Parag Warudkar wrote:
> On Dec 8, 2007 6:12 PM, Parag Warudkar <parag.warudkar@gmail.com> wrote:
> > No problems after disabling CONFIG_HIGHRES_TIMERS , CONFIG_CPU_IDLE
> > and CONFIG_NO_HZ.
> >
> > I will try enabling them one by one - HRT, NOHZ and CPU_IDLE last -
> > that way we can at least tell what is required to be hit with this
> > problem.
>
> Looks like CPU_IDLE=y is necessary for the problem to show up.
> With CPU_IDLE=n HRT+NO_HZ+TICK_ONESHOT does not give soft lockup problems.
> (Actually with HIGH_RES_TIMERS=NO_HZ=TICK_ONESHOT=y I do see short
> freezes on ssh - when I cannot type anything for may be a second even
> under 100% idle. But Soft Lock up doesnt show up in dmesg with this
> configuration.)
Can you please apply the patch below ? It prints out the internal
state of the clockevents/timer system when the softlockup is detected.
Thanks,
tglx
diff --git a/kernel/softlockup.c b/kernel/softlockup.c
index 11df812..82f1a05 100644
--- a/kernel/softlockup.c
+++ b/kernel/softlockup.c
@@ -118,6 +118,7 @@ void softlockup_tick(void)
show_regs(regs);
else
dump_stack();
+ sysrq_timer_list_show();
spin_unlock(&print_lock);
}
next prev parent reply other threads:[~2007-12-10 5:50 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-07 22:53 BUG: soft lockup - CPU#1 stuck for 15s! [swapper:0] Parag Warudkar
2007-12-07 23:12 ` Pallipadi, Venkatesh
2007-12-07 23:31 ` Parag Warudkar
2007-12-08 2:56 ` Thomas Gleixner
2007-12-08 15:10 ` Parag Warudkar
2007-12-08 15:36 ` Parag Warudkar
2007-12-08 15:47 ` Ingo Molnar
2007-12-08 16:00 ` Parag Warudkar
2007-12-08 19:13 ` Ingo Molnar
2007-12-08 19:33 ` Parag Warudkar
2007-12-08 19:42 ` Ingo Molnar
2007-12-08 20:08 ` Parag Warudkar
2007-12-08 20:11 ` Ingo Molnar
2007-12-08 20:46 ` Parag Warudkar
2007-12-08 20:51 ` Arjan van de Ven
2007-12-08 21:04 ` Parag Warudkar
2007-12-08 23:12 ` Parag Warudkar
2007-12-09 21:57 ` Parag Warudkar
2007-12-09 22:30 ` Arjan van de Ven
2007-12-10 5:49 ` Thomas Gleixner [this message]
2007-12-11 4:49 ` Parag Warudkar
2007-12-14 23:17 ` Len Brown
2007-12-15 0:51 ` Parag Warudkar
2007-12-15 8:10 ` Thomas Gleixner
2007-12-15 18:48 ` Parag Warudkar
2007-12-16 5:15 ` Parag Warudkar
2007-12-16 13:43 ` Parag Warudkar
2007-12-17 8:05 ` Thomas Gleixner
2007-12-17 13:08 ` Parag Warudkar
2007-12-17 22:05 ` Thomas Gleixner
2008-01-09 11:56 ` Thomas Gleixner
2008-01-11 0:31 ` Parag Warudkar
2008-01-11 9:50 ` Thomas Gleixner
2007-12-07 23:17 ` BUG: " Andrew Morton
2007-12-08 2:35 ` Rafael J. Wysocki
2007-12-09 22:42 parag.warudkar
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=alpine.LFD.0.99999.0712101117300.11977@localhost.localdomain \
--to=tglx@linutronix.de \
--cc=akpm@linux-foundation.org \
--cc=arjan@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=parag.warudkar@gmail.com \
--cc=torvalds@linux-foundation.org \
--cc=venkatesh.pallipadi@intel.com \
/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).