linux-kernel - Re: 2.6.30 enabling cpu1 on resume fails after suspend to memory

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-prev] [thread-next>] [day] [month] [year] [list]

Date:	Sun, 14 Jun 2009 14:15:16 +0200
From:	"Rafael J. Wysocki" <rjw@...k.pl>
To:	Thomas Gleixner <tglx@...utronix.de>, "Benjamin S." <sbenni@....de>
Cc:	Ingo Molnar <mingo@...e.hu>, linux-kernel@...r.kernel.org,
	js@...21.net, Jesse Barnes <jbarnes@...tuousgeek.org>,
	pm list <linux-pm@...ts.linux-foundation.org>,
	Linux PCI <linux-pci@...r.kernel.org>,
	Matthew Wilcox <matthew@....cx>
Subject: Re: 2.6.30 enabling cpu1 on resume fails after suspend to memory

On Sunday 14 June 2009, Thomas Gleixner wrote:
> On Sun, 14 Jun 2009, Rafael J. Wysocki wrote:
> > Evidently, the change of the interrupt handling during suspend-resume,
> > commit 2ed8d2b3a81bdbb0418301628ccdb008ac9f40b7 (PM: Rework handling of
> > interrupts during suspend-resume) broke resume (specifically, the enabling of
> > nonboot CPUs) on the Benjamin's machine, but only if MSI support is enabled.
> > Also, resume works if suspend_device_irqs() and resume_device_irqs() in
> > drivers/base/power/main.c are commented out.
> > 
> > Is there anything the MSI code does in __enable_irq() and/or __disable_irq()
> > that might cause this problem to appear?
> 
> Not that I'm aware of. Which of the devices is using MSI ? Have to
> tried to skip only the MSI ones in suspend/resume_device_irqs() ?

Good idea.

Benjamin, please send /proc/interrupts from your system.

Best,
Rafael
--
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/