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]
Date:	Thu, 21 Aug 2008 21:54:23 +0200
From:	"Rafael J. Wysocki" <rjw@...k.pl>
To:	"Vegard Nossum" <vegard.nossum@...il.com>
Cc:	"Dmitry Adamushko" <dmitry.adamushko@...il.com>,
	"Max Krasnyanskiy" <maxk@...lcomm.com>,
	"Linux Kernel Mailing List" <linux-kernel@...r.kernel.org>,
	"Pavel Machek" <pavel@....cz>
Subject: Re: latest -git: hibernate: possible circular locking dependency detected

On Thursday, 21 of August 2008, Vegard Nossum wrote:
> On Thu, Aug 21, 2008 at 9:31 PM, Rafael J. Wysocki <rjw@...k.pl> wrote:
> > Now, what is the source of the "SysRq : Power Off" in the dmesg you posted?
> 
> The only suggestion I can make is that SysRq can be triggered remotely
> with serial console (COM1/ttyS0), because I know that the serial line
> is producing junk in the other direction (i.e. reading from /dev/ttyS0
> on the kernel which has been booted with console=ttyS0 reads junk,
> sometimes things that look like pieces of dmesg). Other than that, I
> have no idea. The SysRq thing seems to only happen after I've entered
> "echo disk > /sys/power/state" too.
> 
> (Also see my email at http://lkml.org/lkml/2008/8/21/409)
> 
> >
> > Also, have you tried to hibernate with the "platform" setting selected in
> > "cat /sys/power/disk" and if you have, does the lockdep warning appear in this
> > case?
> 
> Yes, I have tried it. In fact, I believe the lockdep warning in the
> boot-log comes with such a setting (ACPI was enabled; isn't platform
> the default in that case?). At least it looked to be selected when
> acpi is enabled:

Yes, it is the default in that case.

> > # cat /sys/power/disk
> > [platform] test testproc shutdown reboot

The problem is, in the case of the "platform" hibernation, kernel_power_off()
is not called at all (ACPI mechanism to enter the S4 sleep state is used
instead).  Apart from this, there should be lines like:

"ACPI: Preparing to enter system sleep state S4"

in the dmesg log in that case and they are not present in your dmesg.

Your dmesg looks like a mixture of hibernation in the "shutdown" mode with
"emergency" shutdown caused by "SysRq : Power Off".

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

Powered by blists - more mailing lists