linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Bruno Prémont" <bonbons@linux-vserver.org>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>,
	Kernel development list <linux-kernel@vger.kernel.org>,
	USB list <linux-usb@vger.kernel.org>
Subject: Re: s2ram slow (radeon) / failing (usb)
Date: Mon, 3 May 2010 21:23:12 +0200	[thread overview]
Message-ID: <20100503212312.62b99fbb@neptune.home> (raw)
In-Reply-To: <Pine.LNX.4.44L0.1005031103180.1651-100000@iolanthe.rowland.org>

On Mon, 03 May 2010 Alan Stern <stern@rowland.harvard.edu> wrote:
> On Mon, 3 May 2010, Bruno [UTF-8] Prémont wrote:
> 
> > > Did you boot with "no_console_suspend"?  Are you using a VT console
> > > instead of X (a serial console may or may not work as well)?
> > 
> > Yes, I'm booting with no_console_suspend and console=ttyS0. On that
> > system there is no X. Multiple ttys are showing up on display with
> > KMS or VGA text mode (just the getty, all kernel and init output goes to
> > serial console as expected)
> 
> You're better off sending the console output to the display (or to
> both); I don't know how well serial consoles work with
> no_console_suspend.

How do I tell kernel to send to both?

At least when the keyboard is not plugged in I get about everything until
the very end, last message being 'SMP alternatives: switching to UP code'
(and the following line from dmesg after resume is 'Back to C!'

Thanks,
Bruno

  reply	other threads:[~2010-05-03 19:23 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-02 13:56 s2ram slow (radeon) / failing (usb) Bruno Prémont
2010-05-02 15:07 ` Alan Stern
2010-05-02 20:06   ` Bruno Prémont
2010-05-02 20:16     ` Rafael J. Wysocki
2010-05-02 20:56       ` Bruno Prémont
2010-05-02 22:04       ` Alan Stern
2010-05-02 21:59     ` Alan Stern
2010-05-03  6:34       ` Bruno Prémont
2010-05-03 13:57         ` Alan Stern
2010-05-03 14:48           ` Bruno Prémont
2010-05-03 15:04             ` Alan Stern
2010-05-03 19:23               ` Bruno Prémont [this message]
2010-05-03 19:39                 ` Alan Stern
2010-05-03 19:46           ` Bruno Prémont
2010-05-03 20:11             ` Alan Stern
2010-05-03 20:57               ` Bruno Prémont
2010-05-03 21:11                 ` Bruno Prémont
2010-05-04  6:42                   ` [linux-pm] " Oliver Neukum
2010-05-04  8:37                     ` Jiri Kosina
2010-05-04 21:04                       ` Bruno Prémont
2010-05-05 12:58                         ` Jiri Kosina
2010-05-05 19:17                           ` Bruno Prémont
2010-05-05 20:30                       ` Bruno Prémont
2010-05-05 20:53                         ` Bruno Prémont
2010-05-05 20:55                           ` Jiri Kosina
2010-05-05 21:35                             ` Alan Stern
2010-05-06 17:47                               ` Bruno Prémont
2010-05-06 18:40                                 ` Alan Stern
2010-05-06 20:59                                   ` Bruno Prémont
2010-05-07  8:29                                   ` Jiri Kosina
2010-05-07 21:18 ` s2ram slow resume - radeon versus no_console_suspend? Bruno Prémont

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=20100503212312.62b99fbb@neptune.home \
    --to=bonbons@linux-vserver.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=rjw@sisk.pl \
    --cc=stern@rowland.harvard.edu \
    /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).