From: "Rogério Brito" <rbrito@ime.usp.br>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-usb@vger.kernel.org, linux-scsi@vger.kernel.org,
linux-kernel@vger.kernel.org,
bugzilla-daemon@bugzilla.kernel.org
Subject: Re: [Bugme-new] [Bug 14020] New: Stack trace when running smartctl on an USB disk
Date: Sat, 22 Aug 2009 18:14:30 -0300 [thread overview]
Message-ID: <20090822211430.GA2547@ime.usp.br> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0908211003090.2912-100000@iolanthe.rowland.org>
[-- Attachment #1: Type: text/plain, Size: 494 bytes --]
Hi, Alan.
On Aug 21 2009, Alan Stern wrote:
> A usbmon trace showing what happens when you plug in the drive and
> when you run smartctl would help.
The requested trace is attached to this message. Please let me know if
you need more information.
Thanks, Rogério Brito.
--
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
[-- Attachment #2: usbmon-dump.txt.bz2 --]
[-- Type: application/octet-stream, Size: 13644 bytes --]
next prev parent reply other threads:[~2009-08-22 21:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20090820220740.GA767@ime.usp.br>
[not found] ` <Pine.LNX.4.44L0.0908211003090.2912-100000@iolanthe.rowland.org>
[not found] ` <20090822191420.GA5572@ime.usp.br>
2009-08-22 20:33 ` [PATCH] usb: fix paths in usbmon documentation Rogério Brito
2009-08-22 21:14 ` Rogério Brito [this message]
2009-08-23 0:17 ` [Bugme-new] [Bug 14020] New: Stack trace when running smartctl on an USB disk Alan Stern
2009-08-23 15:11 ` Rogério Brito
2009-08-23 16:24 ` Alan Stern
2009-08-23 18:22 ` Douglas Gilbert
[not found] ` <Pine.LNX.4.44L0.0909010942590.2816-100000@iolanthe.rowland.org>
2009-09-02 7:27 ` 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=20090822211430.GA2547@ime.usp.br \
--to=rbrito@ime.usp.br \
--cc=akpm@linux-foundation.org \
--cc=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@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