From: "Bruno Prémont" <bonbons@linux-vserver.org>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: dri-devel@lists.freedesktop.org,
"Rafael J. Wysocki" <rjw@sisk.pl>, <linux-kernel@vger.kernel.org>,
<linux-usb@vger.kernel.org>
Subject: Re: s2ram slow (radeon) / failing (usb)
Date: Mon, 3 May 2010 08:34:49 +0200 [thread overview]
Message-ID: <20100503083449.7355b457@pluto.restena.lu> (raw)
In-Reply-To: <Pine.LNX.4.44L0.1005021756570.30701-100000@netrider.rowland.org>
On Sun, 2 May 2010 17:59:17 -0400 (EDT) Alan Stern wrote:
> On Sun, 2 May 2010, Bruno [UTF-8] Prémont wrote:
>
> > > There's no way to fix the USB problem without knowing what goes
> > > wrong. Let's see how far you get before the system freezes on a
> > > kernel with CONFIG_USB_DEBUG enabled.
> >
> > Am I missing something?
> >
> > I've enabled CONFIG_USB_DEBUG but don't see any additional module
> > parameter nor anything extra to toggle and I don't get more output
> > than without it.
>
> Depends what you mean by "output". The kernel generates more log
> messages, but they may not get sent to your console. You need to
> make sure the console's log level is set high enough to see debugging
> messages. For example:
>
> echo 9 >/proc/sys/kernel/printk
>
> or type Alt-SysRq-9.
I've been doing `dmesg -n 8` (9 is rejected as invalid) so it should
send out everything.
It looked like there was some more output during boot-up, but nothing
during suspend, at least up to the freezing point.
Bruno
next prev parent reply other threads:[~2010-05-03 6:34 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 [this message]
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
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=20100503083449.7355b457@pluto.restena.lu \
--to=bonbons@linux-vserver.org \
--cc=dri-devel@lists.freedesktop.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).