Hi!
> > > 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...)
--
Thanks for all the (sleeping) penguins.
-
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/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
