Re: Resume from swsusp stopped working with 2.6.14 and 2.6.15-rc1

From: Pavel Machek
Date: Wed Nov 23 2005 - 07:01:45 EST


> >> > Well, I do not think this problem will surface again. It is first
> >> > failure in pretty long time. If it happens again, I'll take your
> >> > patch.
> >>
> >> If so, could you please make it printk() a message after the timeout has
> >> passed? This way the user will know what's going on at least.
> >
> > We do have messages there, they even tell you name of process that was
> > not stopped. That's enough to debug failure quickly.
> I don't think so. The example said
> "Strange, kseriod not stopped"
> This names a process that admittedly took a long time to stop, but not
> the real *cause* of the failure. There was nothing wrong with kseriod.
> FWIW, debugging this was way out of my league. I might have had a
> better chance if it mentioned a short, fixed timeout. I also noticed
> that it wasn't very obvious to you either at first. The first thought
> was a failing serio driver, although that admittedly might be because
> I mislead you in my attempt to pinpoint the failure.

Ok, can you suggest better wording?
Thanks, Sharp!
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at
Please read the FAQ at