From: "Rogério Brito" <rbrito@ime.usp.br>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Robert Hancock <hancockrwd@gmail.com>,
linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org
Subject: ioctl_internal_command messages (was: Re: [2.6.30-rc2] usb reset during big file transfer and ext3 error)
Date: Sun, 24 May 2009 12:32:30 -0300 [thread overview]
Message-ID: <20090524153230.GA6246@ime.usp.br> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0905241035380.7718-100000@netrider.rowland.org>
On May 24 2009, Alan Stern wrote:
> On Sun, 24 May 2009, [utf-8] Rogério Brito wrote:
> > In particular, those ioctl_internal_command return code messages seem
> > strange, regarding other USB devices that I have. Are they being shown
> > because I have some debugging information in my kernel or are they
> > abnormal?
>
> It is abnormal, but I can't tell what the reason is without more
> information. You should try using usbmon (see
> Documentation/usb/usbmon.txt) to trace these events.
Recompiling my kernel right now with usbmon support. Will send you logs
very soon.
Thanks,
--
Rogério Brito : rbrito@{mackenzie,ime.usp}.br : GPG key 1024D/7C2CAEB8
http://www.ime.usp.br/~rbrito : http://meusite.mackenzie.com.br/rbrito
Projects: algorithms.berlios.de : lame.sf.net : vrms.alioth.debian.org
next prev parent reply other threads:[~2009-05-24 15:32 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-21 11:10 [2.6.30-rc2] usb reset during big file transfer and ext3 error Rogério Brito
2009-04-22 0:34 ` Robert Hancock
2009-04-22 22:06 ` Rogério Brito
2009-04-23 2:53 ` Alan Stern
2009-05-01 9:15 ` Rogério Brito
2009-05-01 19:16 ` Alan Stern
2009-05-24 7:16 ` Rogério Brito
2009-05-24 14:40 ` Alan Stern
2009-05-24 15:32 ` Rogério Brito [this message]
2009-05-24 16:11 ` Rogério Brito
2009-05-25 2:34 ` Alan Stern
2009-05-25 15:13 ` [PATCH] usb-storage: include USB drive in unusual_devs list Rogério Brito
2009-05-25 21:03 ` Alan Stern
2009-05-25 21:41 ` Rogério Brito
2009-08-01 18:30 ` Rogério Brito
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=20090524153230.GA6246@ime.usp.br \
--to=rbrito@ime.usp.br \
--cc=hancockrwd@gmail.com \
--cc=linux-kernel@vger.kernel.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