From mboxrd@z Thu Jan 1 00:00:00 1970 From: Carl-Daniel Hailfinger Subject: S3 suspend and serial console Date: Thu, 03 Feb 2005 15:09:07 +0100 Message-ID: <42023083.8030508@gmx.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Return-path: Sender: acpi-devel-admin-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org Errors-To: acpi-devel-admin-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , List-Archive: To: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org List-Id: linux-acpi@vger.kernel.org Hi, on resume from S3, my serial console prints garbage and stops working. I assume the BIOS resets the serial port on resume, but I have abolutely no idea how to find out what speed and parity the serial port has after resume. A quick try of 9600,57600,115200 didn't succeed and I now wonder if - the kernel could reset the serial ports on resume - the kernel could read the current parameters from the UART and print them out so I can adjust my serial console. Oh well... after some investigation, it seems the serial console goes back to normal after issuing the command echo foo >/dev/ttyS0 Could it be that the UART state is out-of-sync or something like that after resume and the serial console code doesn't notice? Regards, Carl-Daniel -- http://www.hailfinger.org/ ------------------------------------------------------- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag-&-drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl