Re: [Swsusp-devel] Re: swsusp problems [was Re: Your opinion on the merge?]

[Dmitry Torokhov <dtor_core@ameritech.net>]

On Tuesday 23 March 2004 06:32 pm, Pavel Machek wrote:
> Hi!
> 
> > > Also, in your model, where do messages printk()-ed from drivers during
> > > suspend/resume end up? Corrupting screen? Lost from sight and only
> > > accessible from dmesg? I believe driver messages *are* important, and
> > > do not see how they could coexist with eye-candy.
> > > 
> > Well, unless these are error messages that prevent machine from suspending/
> > resuming they are really just another form of eye-candy, nothing more,
> > nothing less.
> 
> Well, I'd hate
> 
> Nov 10 00:37:51 amd kernel: Buffer I/O error on device sr0, logical block 842340
> Nov 10 00:37:53 amd kernel: end_request: I/O error, dev sr0, sector 6738472
> 
> to be obscured by progress bar.
> 
> 									Pavel

OK, so you have an error condition on your CD. Does it prevent suspend from
completing? If not then I probably would not care about it till later when
I see it in syslog... I remember that the one thing that Pat complained
most often is your love for "panic"ing instead of trying to recover. In that
case you understandably want as many preceding messages as possible left
intact on the screen to diagnose the problem. If error recovery is ever done
then some eye-candy probably won't hurt.

Also, if we leave swsusp and suspending alone for a second, I could have
'top' running on console overwriting the very same messages. Should we ban
top?

If error reporting is so important for a box it probably:
- has many more means to notify operator;
- has all eye-candy turned off;
- is not getting suspended anyway.
IOW it's most likely a server running 24/7.

-- 
Dmitry