linux-kernel - Re: [PATCH] serial-core: resume serial hardware with no_console

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20090924170503.37cbe4ed.akpm@linux-foundation.org>
Date:	Thu, 24 Sep 2009 17:05:03 -0700
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	Stanislav Brabec <utx@...guin.cz>
Cc:	linux-kernel@...r.kernel.org, gregkh@...e.de,
	linux@....linux.org.uk, Alan Cox <alan@...rguk.ukuu.org.uk>
Subject: Re: [PATCH] serial-core: resume serial hardware with
 no_console_suspend

On Tue, 15 Sep 2009 15:38:58 +0200
Stanislav Brabec <utx@...guin.cz> wrote:

> Hardware may need re-initialization to get serial port working after
> resume. It does not happen with no_console_suspend. Attached patch
> attempts to fix it.
> 
> The patch attempts to keep hardware running before suspend and run
> hardware re-initialization after resume. Maybe simpler approach is
> possible.

The patch doesn't apply any more and seems like a rather hacky thing to do.

It appears that you have specific serial hardware which doesn't resume
correctly?  If so, that's a bug, so how about we start with a bug
report/description?


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/