From: "Thiago Galesi" <thiagogalesi@gmail.com>
To: "Alan Stern" <stern@rowland.harvard.edu>
Cc: "Alex Buell" <alex.buell@munted.org.uk>,
linux-kernel@vger.kernel.org, "Robert Hancock" <hancockr@shaw.ca>,
"Tomas Styblo" <tripie@cpan.org>,
linux-usb@vger.kernel.org, usb-storage@lists.one-eyed-alien.net
Subject: Re: [PATCH] JMicron JM20337 USB-SATA data corruption bugfix - device 152d:2338
Date: Tue, 2 Sep 2008 17:16:22 -0300 [thread overview]
Message-ID: <82ecf08e0809021316l68272103q9daff7b12ed90e8b@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0809021508480.5583-100000@iolanthe.rowland.org>
Hello
>
> I can't tell exactly what's happening, but your device is sending back
> a lot of error messages (Not Ready - Medium not present). Maybe it
> doesn't recognize the type of disc you have loaded. Also, there appears to be some program querying the state of your
> device 7 or 8 times every two seconds.
Ok, I suspect what this may be, and I'll disable it, hopefully
producing a cleaner log.
> However what finally caused the failure was a command (0xAC) which I
> don't recognize and apparently your drive doesn't recognize either.
Is this it? dfbb5d80 1845367929 C Bi:6:002:1 0 13 = 55534253 acc90100
00000000 00
Any idea who may be sending this? I mean, can this be send via a
simple IOCTL to /dev/sr0 or it is something else?
Maybe stracing the program would be a good idea.
If I were to place a trace inside a driver, were would it be better?
sr_mod, sd_mod, usb-storage, cdrom? or somewhere else?
Thank you
--
-
Thiago Galesi
next prev parent reply other threads:[~2008-09-02 20:16 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.eWQqoO1e4Mdhu8SK5jzMFAI/3NU@ifi.uio.no>
2008-07-21 19:37 ` Robert Hancock
2008-07-22 2:37 ` Alan Stern
2008-07-22 9:03 ` Tomas Styblo
2008-07-23 2:38 ` Alan Stern
2008-07-23 23:20 ` Robert Hancock
2008-07-24 3:42 ` Alan Stern
2008-07-30 19:55 ` Robert Hancock
2008-07-30 20:00 ` [usb-storage] " Matthew Dharm
2008-07-30 20:46 ` Robert Hancock
2008-07-30 21:18 ` Alan Stern
2008-07-30 21:07 ` Alan Stern
2008-08-01 21:15 ` Alex Buell
2008-08-01 22:22 ` Alex Buell
2008-08-02 2:32 ` Robert Hancock
2008-08-02 23:49 ` Alan Stern
2008-08-03 9:07 ` Alex Buell
2008-08-04 16:48 ` Alan Stern
2008-08-04 20:17 ` Alex Buell
2008-08-04 20:45 ` Alan Stern
2008-09-02 12:10 ` Thiago Galesi
2008-09-02 15:02 ` Alan Stern
2008-09-02 16:07 ` Thiago Galesi
2008-09-02 19:19 ` Alan Stern
2008-09-02 20:16 ` Thiago Galesi [this message]
2008-09-02 21:06 ` Alan Stern
2008-09-04 12:09 ` Thiago Galesi
2008-09-04 14:03 ` Alan Stern
2008-09-04 15:17 ` Thiago Galesi
2008-09-04 15:26 ` Alan Stern
2008-07-25 8:44 ` Tomas Styblo
2008-07-25 8:54 ` Robert Hancock
2008-07-22 5:11 ` Tomas Styblo
2008-07-22 5:31 ` Robert Hancock
2008-07-22 6:11 ` Tomas Styblo
2008-07-22 8:45 ` Robert Hancock
2008-07-24 6:15 ` Alex Buell
2008-07-29 21:09 ` Alex Buell
2008-07-29 22:33 ` [usb-storage] " Matthew Dharm
2008-07-20 5:13 Tomas Styblo
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=82ecf08e0809021316l68272103q9daff7b12ed90e8b@mail.gmail.com \
--to=thiagogalesi@gmail.com \
--cc=alex.buell@munted.org.uk \
--cc=hancockr@shaw.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=stern@rowland.harvard.edu \
--cc=tripie@cpan.org \
--cc=usb-storage@lists.one-eyed-alien.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
all inboxes | Powered by JetHome®