From: David Brownell <david-b@pacbell.net>
To: Nicolas Mailhot <Nicolas.Mailhot@laPoste.net>
Cc: Patrick Mansfield <patmans@us.ibm.com>, linux-scsi@vger.kernel.org
Subject: Re: Usb storage mounting was broken
Date: Wed, 22 Oct 2003 11:44:30 -0700 [thread overview]
Message-ID: <3F96D00E.1080500@pacbell.net> (raw)
In-Reply-To: <1066845819.2806.11.camel@m70.net81-64-235.noos.fr>
> The only weird thing is some messages made it to /var/log/messages,
> /var/log/kernel and show up with dmesg, but didn't end up in
> /var/log/dmesg (which is what I used as attachement before, but the
> other messages were extracted from /var/log/kernel and put in the bug
> too). I suppose RedHat stops writing in /var/log/dmesg after the end of
> the boot.
As a rule, "dmesg output" means "output of dmesg command" ... :)
Boot messages (/var/log/dmesg) aren't a substitute.
OK, at this point what's needed is the more customary usb debug
information. Contents of /proc/bus/usb/devices for starters.
And since this resembles an enumeration failure, it'd be good
to have the Alt-Sysrq-t output for "khubd".
And does this happen if you try this with, say, OHCI not EHCI?
- Dave
next prev parent reply other threads:[~2003-10-22 18:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-21 22:33 Usb storage mounting was broken somewhere between 2.6.0-test5-bk10 and 2.6.0-test6-bk1 Nicolas Mailhot
2003-10-22 0:55 ` Patrick Mansfield
2003-10-22 2:25 ` David Brownell
2003-10-22 7:49 ` Nicolas Mailhot
2003-10-22 15:11 ` David Brownell
2003-10-22 15:45 ` Nicolas Mailhot
2003-10-22 16:20 ` David Brownell
2003-10-22 18:03 ` Nicolas Mailhot
2003-10-22 18:44 ` David Brownell [this message]
2003-10-22 20:33 ` Usb storage mounting was broken Nicolas Mailhot
2003-10-22 22:53 ` David Brownell
2003-10-23 19:59 ` Nicolas Mailhot
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=3F96D00E.1080500@pacbell.net \
--to=david-b@pacbell.net \
--cc=Nicolas.Mailhot@laPoste.net \
--cc=linux-scsi@vger.kernel.org \
--cc=patmans@us.ibm.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.