linux-kernel - Re: 3.16-rcX crashes on resume from Suspend-To-RAM

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: <1405988531.2455.14.camel@rzhang1-toshiba>
Date:	Tue, 22 Jul 2014 08:22:11 +0800
From:	Zhang Rui <rui.zhang@...el.com>
To:	markus@...schke.com
Cc:	linux-kernel@...r.kernel.org,
	"Rafael J. Wysocki" <rafael.j.wysocki@...el.com>,
	Mika Westerberg <mika.westerberg@...ux.intel.com>
Subject: Re: 3.16-rcX crashes on resume from Suspend-To-RAM

On Thu, 2014-07-17 at 10:27 -0700, Markus Gutschke wrote:
> Please note the crash in "dmesg" right after booting. This looks relevant:
> 
I think the crash log also exists in 3.15 kernel, can you please verify
this?

> https://medusa.gutschke.com/markus/acpi/after-dmesg.txt
> https://medusa.gutschke.com/markus/acpi/acpidump.txt
> https://medusa.gutschke.com/markus/acpi/before-platform-devices-firmware-node.txt
> https://medusa.gutschke.com/markus/acpi/before-platform-devices.txt
> https://medusa.gutschke.com/markus/acpi/before-pnp-devices-firmware-node.txt
> https://medusa.gutschke.com/markus/acpi/before-pnp-devices.txt
> https://medusa.gutschke.com/markus/acpi/after-platform-devices-firmware-node.txt
> https://medusa.gutschke.com/markus/acpi/after-platform-devices.txt
> https://medusa.gutschke.com/markus/acpi/after-pnp-devices-firmware-node.txt
> https://medusa.gutschke.com/markus/acpi/after-pnp-devices.txt

are you building the kernel with last commit
eec15edbb0e14485998635ea7c62e30911b465f0?

If yes, please rebuild your 3.16 kernel with last commit
b04c58b1ed26317bfb4b33d3a2d16377fc6acd0f, and re-attach the after-*
logs.

And please also apply the debug patch attached on top of commit
b04c58b1ed26317bfb4b33d3a2d16377fc6acd0f, and see if the problem still
exists.

thanks,
rui

View attachment "0001-debug-patch.patch" of type "text/x-patch" (639 bytes)