linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Brownell <david-b@pacbell.net>
To: Nicolas Mailhot <Nicolas.Mailhot@laPoste.net>
Cc: greg@kroah.com, linux-usb-devel@lists.sourceforge.net,
	linux-kernel@vger.kernel.org
Subject: Re: [linux-usb-devel] 2.5.42-ac1, 2.5.42, 2.5.41 boot hang with CONFIG_USB_DEBUG=n
Date: Mon, 14 Oct 2002 09:53:19 -0700	[thread overview]
Message-ID: <3DAAF67F.1080504@pacbell.net> (raw)
In-Reply-To: 20021013172557.GA890@rousalka.noos.fr

> Now it turns out I didn't do such a piss-poor of configuring my 2.5 
> kernel, since the only option I could find that make a difference was 
> CONFIG_USB_DEBUG. When I accept flooding my system logs with obscure usb 
> incantations the system boots:(.   ...
> 
>     Can an helpful soul help me bring my system some relief  ? I'd 
> really like not to boot in debug mode.

That's a new failure mode!   Can you help narrow this down?

You're using the OHCI driver, so you can just tweak the lines at the
top of drivers/usb/host/ohci-hcd.c that can #define DEBUG.  If you
comment out that #define, and leave CONFIG_USB_DEBUG on (and then
rebuild and re-init with the new OHCI driver), does that work or not?

If that works, it'd be time to see which OHCI printk()s morph init (?)
timing enough to matter to your K7 box.   Looked to me like they were
all either before or after the timing-critical bits (chip init), so
disabling just the OHCI messages "should" not change your failure mode.

- Dave




  reply	other threads:[~2002-10-14 16:46 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-13 17:25 2.5.42-ac1, 2.5.42, 2.5.41 boot hang with CONFIG_USB_DEBUG=n Nicolas Mailhot
2002-10-14 16:53 ` David Brownell [this message]
2002-10-14 21:20   ` [linux-usb-devel] " Nicolas Mailhot
2002-10-15 17:10     ` David Brownell
2002-10-15 17:39       ` Nicolas Mailhot
2002-10-15 21:00         ` David Brownell
2002-10-18 17:45       ` Nicolas Mailhot
2002-10-21  2:44         ` David Brownell

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=3DAAF67F.1080504@pacbell.net \
    --to=david-b@pacbell.net \
    --cc=Nicolas.Mailhot@laPoste.net \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb-devel@lists.sourceforge.net \
    /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).