On Tue, 22 May 2007, Romano Giannetti wrote:Ok, good to hear. It's not known, no, and yeah, that's scary (and 60 seconds is long enough that most people would have grown bored and pushed the power button for five seconds, having considered the resume a failure). Do you mean that doing "date" twice does not increase the seconds? If so, that's almost certainly related to the gaping delay. Which timer do you end up using (what does "dmesg | grep clocksource" say)? Does adding "clocksource=acpi_pm" to the kernel command line change things? Also, what does your lspci look like? Linus -
| Greg KH | [GIT PATCH] driver core patches against 2.6.24 |
| Tarkan Erimer | Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3 |
| Amit K. Arora | [RFC] Heads up on sys_fallocate() |
| Chuck Ebbert | Why do so many machines need "noapic"? |
git: | |
| Jarek Poplawski | [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| David Miller | [GIT]: Networking |
| Gerrit Renker | [PATCH 27/37] dccp: Integration of dynamic feature activation - part 2 (server side) |
| Natalie Protasevich | [BUG] New Kernel Bugs |
