From: Jiri Slaby <jirislaby@gmail.com>
To: Greg KH <greg@kroah.com>
Cc: Alan Stern <stern@rowland.harvard.edu>,
Andrew Morton <akpm@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux-pm mailing list <linux-pm@lists.linux-foundation.org>,
USB list <linux-usb@vger.kernel.org>
Subject: Re: suspend (uhci_hcd) defunct in mmotm 2008-09-13-03-09
Date: Wed, 24 Sep 2008 20:19:53 +0200 [thread overview]
Message-ID: <48DA84C9.3010707@gmail.com> (raw)
In-Reply-To: <20080924181403.GA6336@kroah.com>
On 09/24/2008 08:14 PM, Greg KH wrote:
> On Wed, Sep 24, 2008 at 12:38:45PM -0400, Alan Stern wrote:
>> On Wed, 24 Sep 2008, Jiri Slaby wrote:
>>
>>>> In fact neither of those logs includes USB debugging messages. Maybe
>>>> you omitted a mkinitrd step.
>>> I don't think so. I don't use neither vanilla nor initrd so this must be the
>>> kernel. Anyway I recompiled with .config linked in and did
>>> # dmesg >dmesg_config.hcd
>>> # zcat /proc/config.gz >>dmesg_config.hcd
>>> in the built kernel. The file is here:
>>> http://decibel.fi.muni.cz/~xslaby/dmesg_config.hcd
>> Still no debugging messages. It's because you have
>> CONFIG_DYNAMIC_PRINTK_DEBUG enabled.
>
> If you have that enabled, you can turn on debugging "on the fly" by
> writing to the debugfs file as described in the documentation for that
> option.
I see, I need to boot to that kernel anyway, with dynamic_printk param this time.
Thanks.
next prev parent reply other threads:[~2008-09-24 18:20 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-15 14:00 hda_intel (sigmatel) defunct in mmotm 2008-09-13-03-09 Jiri Slaby
2008-09-15 14:16 ` Matthew Ranostay
2008-09-16 14:43 ` Matthew Ranostay
2008-09-17 8:58 ` Jiri Slaby
2008-09-17 14:09 ` Matthew Ranostay
2008-09-24 9:42 ` Jiri Slaby
2008-09-17 16:46 ` suspend (uhci_hcd) " Jiri Slaby
2008-09-18 21:14 ` Alan Stern
2008-09-24 10:55 ` Jiri Slaby
2008-09-24 14:49 ` Alan Stern
2008-09-24 16:04 ` Jiri Slaby
2008-09-24 16:38 ` Alan Stern
2008-09-24 18:14 ` Greg KH
2008-09-24 18:19 ` Jiri Slaby [this message]
2008-09-24 18:54 ` Jiri Slaby
2008-09-24 21:29 ` Alan Stern
2008-09-25 20:51 ` Jiri Slaby
2008-09-25 21:07 ` [PATCH] PM: use pm_op methods for device types Alan Stern
2008-09-25 21:27 ` Rafael J. Wysocki
2008-09-25 22:06 ` Greg KH
2008-09-26 13:56 ` Alan Stern
2008-09-26 17:59 ` Greg KH
2008-10-06 15:11 ` Pavel Machek
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=48DA84C9.3010707@gmail.com \
--to=jirislaby@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=linux-usb@vger.kernel.org \
--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