[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Pine.LNX.4.44L0.1005031536420.1651-100000@iolanthe.rowland.org>
Date: Mon, 3 May 2010 15:39:28 -0400 (EDT)
From: Alan Stern <stern@...land.harvard.edu>
To: Bruno Prémont <bonbons@...ux-vserver.org>
cc: "Rafael J. Wysocki" <rjw@...k.pl>,
Kernel development list <linux-kernel@...r.kernel.org>,
USB list <linux-usb@...r.kernel.org>
Subject: Re: s2ram slow (radeon) / failing (usb)
On Mon, 3 May 2010, Bruno [UTF-8] Prémont wrote:
> On Mon, 03 May 2010 Alan Stern <stern@...land.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?
With something like this: console=ttyS0,115200 console=tty0
> 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!'
The verbose debugging in driver.c should add some messages. If you
still don't see anything, try putting your own printk statements in
usb_suspend() and usb_resume() and the functions they call.
Alan Stern
--
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/
Powered by blists - more mailing lists