From: Thomas Gleixner <tglx@linutronix.de>
To: Parag Warudkar <parag.warudkar@gmail.com>
Cc: Len Brown <lenb@kernel.org>,
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, 17 Dec 2007 23:05:55 +0100 (CET) [thread overview]
Message-ID: <alpine.LFD.0.99999.0712172208500.3670@localhost.localdomain> (raw)
In-Reply-To: <82e4877d0712170508r69189409l803c8f490e65925d@mail.gmail.com>
On Mon, 17 Dec 2007, Parag Warudkar wrote:
> On Dec 17, 2007 3:05 AM, Thomas Gleixner <tglx@linutronix.de> wrote:
> > Sigh. You did not have the debug patch applied anymore, which printks
> > the timer_list data ? Can you apply it again and provide the output
> > please ?
> >
>
> This keeps getting more and more weird - This time I was running with
> CONFIG_CPU_IDLE=N and I have ton of soft lockups after 14hr uptime.
It's more than weird.
> now at 39080147128907 nsecs
> .idle_entrytime : 39080384013047 nsecs
The time, when we entered idle on CPU#0 is in the future.
> .tick_stopped : 0
But the tick is not stopped, that means CPU#0 has work to do
On CPU#1 idle entry just happened:
> .idle_entrytime : 39079996603653 nsecs
> now at 40490254040892 nsecs
> .idle_entrytime : 40490492012833 nsecs
Again, idle_entry on CPU#0 is in the future.
On CPU#1 the idle entry was at:
> .idle_entrytime : 40489996578090 nsecs
which means: 0.257462802 sec. ago
> now at 40700144217096 nsecs
Aarg. On CPU#0 this is consistently in the future:
> .idle_entrytime : 40700372012887 nsecs
I'm really confused.
> .idle_entrytime : 40699996620694 nsecs
> .idle_sleeptime : 40540536046589 nsecs
> .last_jiffies : 10100000
> .next_jiffies : 10100467
> .idle_expires : 40701864000000 nsecs
> jiffies: 10100158
>
>
> Tick Device: mode: 1
> Clock Event Device: hpet
> max_delta_ns: 2147483647
> min_delta_ns: 3352
> mult: 61496110
> shift: 32
> mode: 3
> next_event: 40700692000000 nsecs
> set_next_event: hpet_legacy_next_event
> set_mode: hpet_legacy_set_mode
> event_handler: tick_handle_oneshot_broadcast
> tick_broadcast_mask: 00000003
Here is the next inconsistent data:
> tick_broadcast_oneshot_mask: 00000003
CPU#1 just woke up. That means the broadcast oneshot mask must be
cleared for CPU#1.
Some real strange thing is going on in your box.
I try to come up with some more debug patches tomorrow.
tglx
next prev parent reply other threads:[~2007-12-17 22:06 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-07 22:53 BUG: " 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
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 [this message]
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.0712172208500.3670@localhost.localdomain \
--to=tglx@linutronix.de \
--cc=akpm@linux-foundation.org \
--cc=arjan@infradead.org \
--cc=lenb@kernel.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
all inboxes | Powered by JetHome®