linux-kernel - HR timers soft lockup on resume from suspend to ram

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-Id: <1173025704.11244.22.camel@funkylaptop>
Date:	Sun, 04 Mar 2007 17:28:24 +0100
From:	Frédéric RISS <frederic.riss@...il.com>
To:	Thomas Gleixner <tglx@...utronix.de>
Cc:	Linux Kernel list <linux-kernel@...r.kernel.org>
Subject: HR timers soft lockup on resume from suspend to ram

Hi,

With recent git versions, my system won't resume from suspend to ram. At
resume time, the kernel hangs just after printing "Enabling non-boot
CPUs ...". This is on a Core Duo system (Mac Mini). Looking at the BUG,
it looks related to hrtimers.

When the system is hung, and I press on the power button, I get this
backtrace (copied from the screen, netconsole won't allow to capture
it): 

BUG: soft lockup detected on CPU#0!
  [<c0155c88>] softlockup_tick+0xa8/0x110
  [<c0130283>] update_process_times+0x33/0x80
  [<c014215b>] tick_sched_timer+0x5b/0xc0
  [<c013e3f3>] hrtimer_interrupt+0x143/0x1d0
  [<c01172e0>] smp_apic_timer_interrupt+0x50/0x80
  [<c0104e4c>] apic_timer_interrupt+0x28/0x30
  [<c0372926>] _spin_unlock_irq+0x6/0x30
  [<c0370488>] __sched_text_start+0x308/0x880
  [<c0372909>] _spin_unlock_irqrestore+0x19/0x30
  [<c01378ee>] worker_thread+0x12e/0x170
  [<c0120a50>] default_wake_function+0x0/0x10
  [<c01377c0>] worker_thread+0x0/0x170
  [<c013a88a>] kthread+0xba/0xf0
  [<c013a7d0>] kthread+0x0/0xf0
  [<c0104fb3>] kernel_thread_helper+0x7/0x14
  ======================

I get it every time I press on the power button.

Fred.

-
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/