On Sunday 14 June 2009, Benjamin S. wrote: > On Sun, 14 Jun 2009 13:19:40 +0200 > "Rafael J. Wysocki" <rjw@xxxxxxx> wrote: > > > On Sunday 14 June 2009, Benjamin S. wrote: > > > > > > On Sun, 14 Jun 2009 12:35:24 +0200 > > > "Rafael J. Wysocki" <rjw@xxxxxxx> wrote: > > > > > > > Thanks for the report, the problem seems to be related to the chipset, because > > > > I'm unable to reproduce it with SB600 and a fairly new AMD CPU. > > > > > > > > Does the resume work if you comment out suspend_device_irqs() and > > > > resume_device_irqs() in drivers/base/power/main.c ? > > > > > > Yes, 2.6.30 without the two lines resumes without problems.\ > > > > Does it help (with the two lines present again) if the kernel is compiled with > > CONFIG_PCI_MSI unset? > > Yes, it works. OK, we need some help. Ingo, 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? Best, Rafael _______________________________________________ linux-pm mailing list linux-pm@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linux-foundation.org/mailman/listinfo/linux-pm
