mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: "Pallipadi, Venkatesh" <venkatesh.pallipadi@intel.com>
Cc: Parag Warudkar <parag.warudkar@gmail.com>,
	LKML <linux-kernel@vger.kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Ingo Molnar <mingo@elte.hu>
Subject: RE: soft lockup - CPU#1 stuck for 15s! [swapper:0]
Date: Sat, 8 Dec 2007 08:26:11 +0530 (IST)	[thread overview]
Message-ID: <alpine.LFD.0.99999.0712080821220.3070@localhost.localdomain> (raw)
In-Reply-To: <924EFEDD5F540B4284297C4DC59F3DEE38C3C2@orsmsx423.amr.corp.intel.com>

On Fri, 7 Dec 2007, Pallipadi, Venkatesh wrote:
> >-----Original Message-----
> >From: Parag Warudkar [mailto:parag.warudkar@gmail.com] 
> >Sent: Friday, December 07, 2007 2:54 PM
> >To: LKML
> >Cc: Andrew Morton; Pallipadi, Venkatesh; Linus Torvalds
> >Subject: BUG: soft lockup - CPU#1 stuck for 15s! [swapper:0]
> >
> >Got this on today's git (2.6.24-rc4) while compiling  stuff - Looks
> >like it is related to CpuIdle stuff.
> >I chose CONFIG_CPU_IDLE for the first time so I don't know when this
> >was introduced.
> >
> >This is on x86_32, SMP.
> >
> >BUG: soft lockup - CPU#1 stuck for 15s! [swapper:0]
> >
> >Pid: 0, comm: swapper Not tainted (2.6.24-rc4 #3)
> >EIP: 0060:[<c0603e22>] EFLAGS: 00000202 CPU: 1
> >EIP is at _spin_lock_irqsave+0x16/0x27
> >EAX: c06b4110 EBX: 00000001 ECX: f7873808 EDX: 00000293
> >ESI: 00000005 EDI: f7873808 EBP: 00000000 ESP: f7829f10
> > DS: 007b ES: 007b FS: 00d8 GS: 0000 SS: 0068
> >CR0: 8005003b CR2: 004f5960 CR3: 372c5000 CR4: 000006d0
> >DR0: 00000000 DR1: 00000000 DR2: 00000000 DR3: 00000000
> >DR6: ffff0ff0 DR7: 00000400
> > [<c0438233>] tick_broadcast_oneshot_control+0x10/0xda
> > [<c0437c82>] tick_notify+0x1d4/0x2eb
> > [<c04281b4>] get_next_timer_interrupt+0x143/0x1b4
> > [<c0605819>] notifier_call_chain+0x2a/0x47
> > [<c04345a0>] raw_notifier_call_chain+0x17/0x1a
> > [<c04378b7>] clockevents_notify+0x19/0x4f
> > [<c0533cc3>] acpi_idle_enter_simple+0x183/0x1d0
> > [<c058cea3>] cpuidle_idle_call+0x53/0x78
> > [<c058ce50>] cpuidle_idle_call+0x0/0x78
> > [<c0402575>] cpu_idle+0x97/0xb8
> >
> 
> Looks like tick_broadcast_lock did not get freed in some path.
> You do not see this when you CPU_IDLE is not configured? 

This looks pretty much like the problem I was solving yesterday.

Parag, can you please try Linus latest and please check whether there
is a stack trace with clockevents_program_event on the top in your
dmesg.

Thanks,
	tglx

  parent reply	other threads:[~2007-12-08  2:56 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 [this message]
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
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.0712080821220.3070@localhost.localdomain \
    --to=tglx@linutronix.de \
    --cc=akpm@linux-foundation.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®