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

From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Thomas Gleixner <tglx@linutronix.de>, "Benjamin S." <sbenni@gmx.de>
Cc: js@sig21.net, Matthew Wilcox <matthew@wil.cx>,
	Linux PCI <linux-pci@vger.kernel.org>,
	linux-kernel@vger.kernel.org,
	Jesse Barnes <jbarnes@virtuousgeek.org>,
	Ingo Molnar <mingo@elte.hu>,
	pm list <linux-pm@lists.linux-foundation.org>
Subject: Re: 2.6.30 enabling cpu1 on resume fails after suspend to memory
Date: Sun, 14 Jun 2009 14:15:16 +0200	[thread overview]
Message-ID: <200906141415.16949.rjw__24968.6577743434$1244981732$gmane$org@sisk.pl> (raw)
In-Reply-To: <alpine.LFD.2.00.0906141405450.2800@localhost.localdomain>

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