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]

Message-Id: <200906141319.40536.rjw@sisk.pl>
Date:	Sun, 14 Jun 2009 13:19:40 +0200
From:	"Rafael J. Wysocki" <rjw@...k.pl>
To:	"Benjamin S." <sbenni@....de>
Cc:	linux-kernel@...r.kernel.org, js@...21.net
Subject: Re: 2.6.30 enabling cpu1 on resume fails after suspend to memory

On Sunday 14 June 2009, Benjamin S. wrote:
> 
> On Sun, 14 Jun 2009 12:35:24 +0200
> "Rafael J. Wysocki" <rjw@...k.pl> 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?

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/