linux-kernel - Re: [3/5] 2.6.21-rc4: known regressions (v2)

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: <46065FED.8030206@m3y3r.de>
Date:	Sun, 25 Mar 2007 13:41:33 +0200
From:	Thomas Meyer <thomas@...3r.de>
To:	"Eric W. Biederman" <ebiederm@...ssion.com>
CC:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	linux-pci@...ey.karlin.mff.cuni.cz,
	Greg Kroah-Hartman <gregkh@...e.de>,
	Tony Luck <tony.luck@...el.com>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Len Brown <lenb@...nel.org>
Subject: Re: [3/5] 2.6.21-rc4: known regressions (v2)

Eric W. Biederman schrieb:
>
> Thomas could you verify the patch below makes the problem go away
> for you.
>   

The patch solves the problem. I'm writing this after the third suspend
and resume cycle.
msi irq stays enabled for libata device:
cat /sys/devices/pci0000\:00/0000\:00\:1f.2/irq
218

cat /proc/interrupts
           CPU0       CPU1
  0:     274190          0   IO-APIC-edge      timer
  9:      13417          0   IO-APIC-fasteoi   acpi
 16:        166          0   IO-APIC-fasteoi   uhci_hcd:usb4
 17:      70908      88643   IO-APIC-fasteoi   wifi0
 18:       3060          0   IO-APIC-fasteoi   libata, uhci_hcd:usb3
 19:          8          0   IO-APIC-fasteoi   ohci1394, uhci_hcd:usb2
 20:      46252          0   IO-APIC-fasteoi   HDA Intel
 21:     168437          0   IO-APIC-fasteoi   uhci_hcd:usb1, ehci_hcd:usb5
218:      15896          0   PCI-MSI-edge      libata
219:          1          0   PCI-MSI-edge      eth0
NMI:          0          0
LOC:      87574     123338
ERR:          0
MIS:          0


BUT...


The first suspend to disk is ok. The second suspend to disk has a
strange behaviour:
1.) write pm image
2.) the system disable the non-boot cpus again (i guess this happens in
power_down())
3.) the system doesn't power down.
4.) pressing any key and the system powers down.

The same is true for the third suspend cycle. Maybe an acpi problem?


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