"Barry K. Nathan" <[EMAIL PROTECTED]> wrote:
>
> Ok, I've narrowed the problem down to one patch. In 2.6.11-mm3, the
> problem goes away if I remove this patch:
> swsusp-enable-resume-from-initrd.patch

That really helps, thanks.

The patch looks fairly innocent.  I'll give up on this and cc the
developers.

> (Recap of the problem in case this gets forwarded: Resume is almost
> instant without the apparently-guilty patch. With the patch, resume
> takes almost half an hour.)
> 
> BTW, there's another strange thing that's introduced by 2.6.11-rc2-mm1:
> With that kernel, suspend is also ridiculously slow (speed is comparable
> to the slow resume with the aforementioned patch). 2.6.11-rc2 does not
> have that problem.

Does reverting swsusp-enable-resume-from-initrd.patch fix this also?

> Also, with 2.6.12-rc2-mm1, this computer happens to hit the bug where
> all the printk timestamps are 0000000.0000000 (don't take the # of
> digits too literally). Probably unrelated, but I may as well mention it.
> (System is an Athlon XP 2200+ with SiS chipset. I can't remember which
> model of SiS chipset.)

Yes, sorry.  Reverting
http://www.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.12-rc2/2.6.12-rc2-mm1/broken-out/sched-x86-sched_clock-to-use-tsc-on-config_hpet-or-config_numa-systems.patch
will fix that one.

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

Reply via email to