I was just feeling lucky and tried suspend-to-disk cycle
on my VIA C3 machine, which lacks PSE which is marked as
being required for swsusp to work. After commenting out
the PSE check in include/asm-i386/suspend.h and rebooting,
I tried the whole cycle, several times, with real load
(while running 3 kernel compile in parallel) and while
IDLE... And surprizingly, it all worked flawlessly for
me, without a single glitch...
So the question is: is PSE really needed nowadays?
Ok, "w/o a single glitch"... Actually there are several
of them so far, but I guess they're unrelated to PSE/C3:
o Suspend after clean boot is sloooow, it takes quite
alot of time to write all the stuff to the disk (the
percents are increasing by 1..2 in a sec). After
resume, if I suspend again the whole process takes
only several secs.
o There's a single 'failed' message, while *suspending*:
Stopping tasks: ===============================================|
Shrinking memory... done (0 pages freed)
pnp: Device 01:01.00 disabled.
pnp: Device 00:09 disabled.
pnp: Device 00:08 disabled.
ACPI: PCI interrupt for device 0000:00:07.5 disabled
ACPI: PCI interrupt for device 0000:00:07.3 disabled
ACPI: PCI interrupt for device 0000:00:07.2 disabled
swsusp: Need to copy 19322 pages
PCI: Setting latency timer of device 0000:00:01.0 to 64
PCI: VIA IRQ fixup for 0000:00:07.1, from 255 to 0
ACPI: PCI Interrupt 0000:00:07.2[D] -> Link [LNKD] -> GSI 11 (level, low) -> IRQ 11
PCI: VIA IRQ fixup for 0000:00:07.2, from 9 to 11
usb usb1: root hub lost power or was reset
ACPI: PCI Interrupt 0000:00:07.3[D] -> Link [LNKD] -> GSI 11 (level, low) -> IRQ 11
PCI: VIA IRQ fixup for 0000:00:07.3, from 9 to 11
usb usb2: root hub lost power or was reset
ACPI: PCI Interrupt 0000:00:07.5[C] -> Link [LNKC] -> GSI 12 (level, low) -> IRQ 12
ACPI: PCI Interrupt 0000:00:0a.0[A] -> Link [LNKC] -> GSI 12 (level, low) -> IRQ 12
eth0: link up, 100Mbps, full-duplex, lpa 0x45E1
pnp: Device 00:08 activated.
pnp: Device 00:09 activated.
pnp: Failed to activate device 00:0b. <========= this one
pnp: Device 01:01.00 activated.
This is all shown while *suspending*, so it looks like
the kernel is shutting down all the devices and brings
them up again for some reason. PNP device 00:0b is my
keyboard.
o There's the following sequence of messages in my dmesg:
Restarting tasks...<6>usb 1-1: USB disconnect, address 2
done
usb 1-1: new low speed USB device using uhci_hcd and address 3
It looks like either the formatting is wrong (missing \n in some
printk() or something), or USB device(s) aren't shutting down/
powered up at the appropriate time, or the connect/powerup
event interferes with the stuff happening during "Restarting
tasks...done" time. For the end-user this is just a cosmetic
glitch (improper formatting), but it as well may be some
more serious prob.
Note I never tried swsusp before, so I've no idea how it usually
looks like, or should look like. We've servers which never suspend,
we've X terminals (no need to suspend, and it will not work anyway
as the network connections will not be restored anyway), and this
my VIA-C3-based machine, which never worked due to the PSE check.
Thanks.
/mjt
-
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]
