lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Message-ID: <924EFEDD5F540B4284297C4DC59F3DEE38C3C2@orsmsx423.amr.corp.intel.com> Date: Fri, 7 Dec 2007 15:12:54 -0800 From: "Pallipadi, Venkatesh" <venkatesh.pallipadi@...el.com> To: "Parag Warudkar" <parag.warudkar@...il.com>, "LKML" <linux-kernel@...r.kernel.org> Cc: "Andrew Morton" <akpm@...ux-foundation.org>, "Linus Torvalds" <torvalds@...ux-foundation.org>, "Thomas Gleixner" <tglx@...utronix.de>, "Ingo Molnar" <mingo@...e.hu> Subject: RE: soft lockup - CPU#1 stuck for 15s! [swapper:0] >-----Original Message----- >From: Parag Warudkar [mailto:parag.warudkar@...il.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? Thanks, Venki -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists