Re: Bisects that are neither good nor bad

["Rafael J. Wysocki" <rjw@sisk.pl>]

Hi,

On Tuesday 30 May 2006 17:29, Pavel Machek wrote:
> >  > > I think I've seen the same problem on one of my (similar spec) laptops.
> >  > > Serial console was useless. On resume, there's a short spew of garbage
> >  > > (just like if the baud rate were misconfigured) over serial before it
> >  > > locks up completely.
> >  > 
> >  > <http://bugzilla.kernel.org/show_bug.cgi?id=4270> discusses a similar
> >  > problem on a couple of machines.  In my resume script (for a TP 600X),
> >  > I have to restore the serial console with
> >  > 
> >  >   setserial -a /dev/ttyS0
> >  > 
> >  > Until that magic executes, garbage characters (like modem noise)
> >  > appear across the serial console.
> > 
> > With the resume failure I'm seeing, we don't get back to userspace
> > to run anything like this. It goes bang long before that.
> > 
> > The SATA fix Mark proposed also didn't improve the situation for me :-/
> 
> If setserial -a is needed.. it means that someone really needs to fix
> suspend/resume support for serial... do it on working machine to
> enable debugging of broken ones...
> 
> (But x32 has no serials, so I'm unlikely to code it...)

There's been something wrong with the serial console on the resume front
on my box for quite some time now.  However, I don't use it very often and I
have a patch that disables suspending of the console's serial port, if anyone
is interested (no, I'm not going to post it to the list ;-) ).

I only observed that the serial console works just fine wrt suspend/resume
if I boot with init=/bin/bash.

Greetings,
Rafael