linux-kernel - 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-next>] [day] [month] [year] [list]

Message-ID: <20090614120950.116536fa@pluto-lenny.milky.way>
Date:	Sun, 14 Jun 2009 12:09:50 +0200
From:	"Benjamin S." <sbenni@....de>
To:	"Rafael J. Wysocki" <rjw@...k.pl>
Cc:	linux-kernel@...r.kernel.org, js@...21.net
Subject: 2.6.30 enabling cpu1 on resume fails after suspend to memory


Hi,

I think I have the same problem Johannes has posted there:

http://marc.info/?l=linux-kernel&m=124475174614672&w=2

My motherboard is a Gigabyte GA-MA78G-DS3H rev. 1.0 (chipset SB700 - the 
same as Johannes' chipset) and my CPU is a AMD 4850e (also the same
as Johannes' CPU). Thus I see the same error on resume after suspend
to memory:

Initializing CPU#1
Stuck ??
Error taking CPU#1 up: -5


After bisecting all revisions between 2.6.29 and 2.6.30 the first bad 
revision seems to be:

commit 2ed8d2b3a81bdbb0418301628ccdb008ac9f40b7
Author: Rafael J. Wysocki <rjw@...k.pl>
Date:   Mon Mar 16 22:34:06 2009 +0100

    PM: Rework handling of interrupts during suspend-resume

    Use the functions introduced in by the previous patch,
    suspend_device_irqs(), resume_device_irqs() and check_wakeup_irqs(),
    to rework the handling of interrupts during suspend (hibernation) and
    resume.  Namely, interrupts will only be disabled on the CPU right
    before suspending sysdevs, while device drivers will be prevented
    from receiving interrupts, with the help of the new helper function,
    before their "late" suspend callbacks run (and analogously during
    resume).

    In addition, since the device interrups are now disabled before the
    CPU has turned all interrupts off and the CPU will ACK the interrupts
    setting the IRQ_PENDING bit for them, check in sysdev_suspend() if
    any wake-up interrupts are pending and abort suspend if that's the
    case.

    Signed-off-by: Rafael J. Wysocki <rjw@...k.pl>
    Acked-by: Ingo Molnar <mingo@...e.hu>



Best Regards, 

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