From: Pavel Machek <pavel@ucw.cz>
To: Bj?rn Mork <bmork@dod.no>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>,
linux-kernel@vger.kernel.org,
Dmitry Torokhov <dtor_core@ameritech.net>
Subject: Re: Resume from swsusp stopped working with 2.6.14 and 2.6.15-rc1
Date: Wed, 23 Nov 2005 13:01:42 +0100 [thread overview]
Message-ID: <20051123120142.GA18403@elf.ucw.cz> (raw)
In-Reply-To: <87hda3d6b8.fsf@obelix.mork.no>
Hi!
> >> > 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?
Pavel
--
Thanks, Sharp!
next prev parent reply other threads:[~2005-11-23 12:02 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-12 13:39 Resume from swsusp stopped working with 2.6.14 and 2.6.15-rc1 Bjørn Mork
2005-11-12 15:23 ` Dmitry Torokhov
2005-11-12 20:01 ` Pavel Machek
2005-11-12 20:39 ` Pavel Machek
2005-11-13 1:53 ` Dmitry Torokhov
2005-11-13 10:09 ` Bjørn Mork
2005-11-17 21:57 ` Dmitry Torokhov
2005-11-18 9:37 ` Bjørn Mork
2005-11-18 11:40 ` Pavel Machek
2005-11-18 11:49 ` Bjørn Mork
2005-11-18 18:31 ` Pavel Machek
2005-11-18 23:32 ` Dmitry Torokhov
2005-11-19 23:48 ` Pavel Machek
2005-11-22 5:26 ` Dmitry Torokhov
2005-11-22 8:57 ` Bjørn Mork
2005-11-22 17:46 ` Pavel Machek
2005-11-22 18:41 ` Bjørn Mork
2005-11-22 18:53 ` Pavel Machek
2005-11-22 18:45 ` Dmitry Torokhov
2005-11-22 18:59 ` Pavel Machek
2005-11-22 19:08 ` Dmitry Torokhov
2005-11-22 20:37 ` Dmitry Torokhov
2005-11-22 18:47 ` Pavel Machek
2005-11-22 22:15 ` Rafael J. Wysocki
2005-11-22 22:51 ` Pavel Machek
2005-11-23 10:09 ` Bjørn Mork
2005-11-23 12:01 ` Pavel Machek [this message]
2005-11-23 13:14 ` Bjørn Mork
2005-11-23 13:25 ` Pavel Machek
2005-11-23 10:53 ` Rafael J. Wysocki
2005-11-18 13:46 ` Bernd Donner
-- strict thread matches above, loose matches on Subject: below --
2005-11-13 3:08 Bernd Donner
2005-11-13 12:13 ` Jacek Kawa
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20051123120142.GA18403@elf.ucw.cz \
--to=pavel@ucw.cz \
--cc=bmork@dod.no \
--cc=dtor_core@ameritech.net \
--cc=linux-kernel@vger.kernel.org \
--cc=rjw@sisk.pl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox