linux-kernel - 2.6.34-rc3 doesn't suspend to disk (-rc2 did)

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 2 Apr 2010 02:19:26 +0200 (CEST)
From:	Jiri Kosina <jkosina@...e.cz>
To:	Pavel Machek <pavel@....cz>, "Rafael J. Wysocki" <rjw@...k.pl>
Cc:	linux-pm@...ts.linux-foundation.org, linux-kernel@...r.kernel.org
Subject: 2.6.34-rc3 doesn't suspend to disk (-rc2 did)

Hi,

I have just hit this problem. Haven't bisected it yet, and going through 
shortlog doesn't ring any bell immediately, so I am sending this out in 
case it rings a bell for someone right away.

Calling 

	s2disk -r /dev/sdb4

suspends without any issues on 2.6.34-rc2, and resume is also fine. With 
2.6.34-rc3 I get

	s2disk: Could not use the resume device (try swapon -a). Reason: No such device

Relevant part of s2disk strace:

mount("none", "/proc/2449", "tmpfs", 0, NULL) = 0
stat64("/dev/sdb4", {st_mode=S_IFBLK|0660, st_rdev=makedev(259, 65536), ...}) = 0
chdir("/proc/2449")                     = 0
mknod("resume", S_IFBLK|0600, makedev(259, 65536)) = 0
open("resume", O_RDWR|O_LARGEFILE)      = 3
stat64("/dev/snapshot", {st_mode=S_IFCHR|0660, st_rdev=makedev(10, 231), ...}) = 0
open("/dev/snapshot", O_RDONLY|O_LARGEFILE) = 4
ioctl(4, 0x400c330d, 0xbfdbcb04)        = -1 ENODEV (No such device)
ioctl(4, 0x4004330a, 0x10010300)        = -1 ENODEV (No such device)
write(2, "s2disk: Could not use the resume"..., 80s2disk: Could not use the resume device (try swapon -a). Reason: No such device

Thanks,

-- 
Jiri Kosina
SUSE Labs, Novell Inc.
--
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/