From: Ingo Molnar <mingo@elte.hu>
To: David Fries <david@fries.net>
Cc: linux-kernel@vger.kernel.org, "Rafael J. Wysocki" <rjw@sisk.pl>,
Pavel Machek <pavel@ucw.cz>, "H. Peter Anvin" <hpa@zytor.com>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [PATCH] i486 CR4 oops, no_console_suspend
Date: Tue, 19 Aug 2008 11:34:54 +0200 [thread overview]
Message-ID: <20080819093454.GG28713@elte.hu> (raw)
In-Reply-To: <20080819033710.GD17528@spacedout.fries.net>
* David Fries <david@fries.net> wrote:
> On Mon, Aug 18, 2008 at 08:41:20AM +0200, Ingo Molnar wrote:
> >
> > applied to tip/x86/urgent, thanks David. I've changed the conditions
> > to read_cr4_safe() instead - that's cleaner. Could you please check
> > whether the patch below works fine too on your box?
>
> Yes the 486 suspends and resumes with this patch.
good - it's now upstream and should show up in 2.6.27-rc4 as well.
> Is there any known problem with no_console_suspend and serial
> consoles? It worked to print the oops for me to track this down, and
> Documentation/kernel-parameters.txt says it is known to work with
> serial consoles, but on resume only kernel messages can output to the
> serial console. The getty on the serial port can't raed or write and
> processes trying to write to the port just hang without getting any
> data across. The serial port works fine across suspends without the
> no_console_suspend argument. Does anyone else see this?
i've had trouble no end with getting even kernel messages out to the
serial console during critical phases of suspend/resume. (especially in
combination with earlyprintk=ttyS0 - not surprisingly)
Especially during resume the UART is initialized back to something
really slow - 300 bauds or 9600 bauds. (depends on the chipset i guess)
So even though it works, it will only worked reliably when i
standardized all my baud settings to that very low setting.
Ingo
next prev parent reply other threads:[~2008-08-19 9:35 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-18 4:03 [PATCH] Fix i486 suspend to disk CR4 oops David Fries
2008-08-18 4:14 ` Maciej W. Rozycki
2008-08-18 4:35 ` H. Peter Anvin
2008-08-18 6:04 ` Andi Kleen
2008-08-18 6:34 ` H. Peter Anvin
2008-08-18 6:42 ` Andi Kleen
2008-08-18 6:41 ` Ingo Molnar
2008-08-18 6:45 ` H. Peter Anvin
2008-08-18 9:15 ` Pavel Machek
2008-08-18 10:16 ` Rafael J. Wysocki
2008-08-18 12:58 ` David Fries
2008-08-18 13:25 ` Ingo Molnar
2008-08-18 14:41 ` Maciej W. Rozycki
2008-08-18 14:38 ` Maciej W. Rozycki
2008-08-18 22:04 ` Pavel Machek
2008-08-18 22:10 ` H. Peter Anvin
2008-08-18 15:24 ` Dave Jones
2008-08-18 16:04 ` Lennart Sorensen
2008-08-18 17:17 ` Dave Jones
2008-08-18 17:32 ` H. Peter Anvin
2008-08-18 22:02 ` Pavel Machek
2008-08-19 3:37 ` [PATCH] i486 CR4 oops, no_console_suspend David Fries
2008-08-19 9:34 ` Ingo Molnar [this message]
2008-08-19 16:07 ` H. Peter Anvin
2008-08-21 4:17 ` David Fries
2008-08-21 5:37 ` H. Peter Anvin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080819093454.GG28713@elte.hu \
--to=mingo@elte.hu \
--cc=david@fries.net \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=rjw@sisk.pl \
--cc=tglx@linutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).