Re: console resume broken sinceba15ab0e8de0d4439a91342ad52d55ca9e313f3d

[Pavel Machek]

On Wed 2009-09-30 17:11:03, Sascha Hauer wrote:
> 
> This patch fixes setting the console speed if console suspend is disabled
> by breaking it if it is enabled, see below:
> 
> > commit ba15ab0e8de0d4439a91342ad52d55ca9e313f3d
> > Author: Deepak Saxena <dsaxena@xxxxxxxxxx>
> > Date:   Sat Sep 19 13:13:33 2009 -0700
...
> > 
> >     Set proper console speed on resume if console suspend is disabled
> >     
> >     Commit b5b82df6, from May 2007, breaks no_console_suspend on the OLPC
> >     XO laptop. Basically what happens is that upon returning from resume,
> >     serial8250_resume_port() will reconfigure the port for high speed
> >     mode and all console output will be garbled, making debug of the
> >     resume path painful. This patch modifies uart_resume_port() to
> >     reset the port to the state it was in before we suspended.
> >     
> >     Original patch by Marcelo Tosatti
> > -		struct ktermios termios;
> > -
> > -		/*
> > -		 * First try to use the console cflag setting.
> > -		 */
> > -		memset(&termios, 0, sizeof(struct ktermios));
> > -		termios.c_cflag = uport->cons->cflag;
> > -
> > -		/*
> > -		 * If that's unset, use the tty termios setting.
> > -		 */
> > -		if (port->tty && termios.c_cflag == 0)
> > -			termios = *port->tty->termios;
> > -
> >  		uart_change_pm(state, 0);
> >  		uport->ops->set_termios(uport, &termios, NULL);
> 
> 
> We call ->set_termios with an unitialized struct ktermios here.
> 
> Any ideas what to do?

Revert the patch for now and make Deepak fix it properly?

Or maybe it is enough to just 'do nothing' in the 'if that's unset'
branch?


								Pavel

-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/