Hi!
> Distro: SuSE Linux 9.2
> Kernel: 2.6.8 (kernel-default-2.6.8-24.11), also 2.6.11.5
> Hardware: Dell Inspiron 6000d, Intel Pentium-M, 915PM chipset,
> disc is Fujitsu MHT2040AH, SATA via ata_piix driver
> Kernel cmdline: root=/dev/sda3 vga=0x317 selinux=0 resume=/dev/sda5 \
> desktop elevator=as showopts
>
> I have the same symptoms as seen in numerous complaints on the web: I do
> "echo disk > /sys/power/state" or run /sbin/swsusp or powersave -U. The
> kernel suspends all the way, then immediately wakes up, having
> accomplished nothing. On 2.6.11.5 I can read an error message: "swsusp:
> FATAL: cannot find swap device, try swapon -a!" Yes, the swap device is
> recognized in /proc/swaps.
>
> I put some printk's into 2.6.11.5 and found out the reason for this
> behavior: in kernel/power/swsusp.c, static resume_device == 0. The
> reason it's 0 is that swsusp_read uses name_to_dev_t to interpret
> resume=/dev/sda5, a bogus block device name. The reason it's bogus
> is
...
> So I'm hoping someone has an idea how to make software_resume happen
> _after_ the initrd has been run and its modules are in place, which
> might make it into whatever kernel is being used in SuSE 9.3.
This is WONTFIX for 2.6.11, but you can be pretty sure it is going to
be fixed for SuSE 9.3, and patch is already in 2.6.12-rc1. Feel free
to betatest SuSE 9.3 ;-).
Pavel
--
People were complaining that M$ turns users into beta-testers...
...jr ghea gurz vagb qrirybcref, naq gurl frrz gb yvxr vg gung jnl!
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]