linux-kernel - Re: s2ram slow (radeon) / failing (usb)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20100503164820.384a371f@pluto.restena.lu>
Date:	Mon, 3 May 2010 16:48:20 +0200
From:	Bruno Prémont <bonbons@...ux-vserver.org>
To:	Alan Stern <stern@...land.harvard.edu>
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 09:57:29 -0400 (EDT) Alan Stern wrote:
> On Mon, 3 May 2010, Bruno [UTF-8] Prémont wrote:
> 
> > 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.
> 
> Yes, that's equivalent to the other things.
> 
> > It looked like there was some more output during boot-up, but
> > nothing during suspend, at least up to the freezing point.
> 
> 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)

As noted in first e-mail, I disabled SERIAL_8250_PNP as that one
blocks/prevents serial output much too early during suspend.

> You might also want to #define VERBOSE_DEBUG at the start of 
> drivers/usb/core/driver.c, before the first #include.

Will do.

> 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/