public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Samuel Colin <Samuel.Colin3@wanadoo.fr>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: USB development list <linux-usb-devel@lists.sourceforge.net>,
	SCSI development list <linux-scsi@vger.kernel.org>
Subject: Re: What is SCSI command 0xa0 ?
Date: Thu, 17 Feb 2005 16:59:40 +0100	[thread overview]
Message-ID: <20050217165940.23cd9521@hebus> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0502161133350.6418-100000@ida.rowland.org>

The Wed, 16 Feb 2005 11:42:18 -0500 (EST)
Alan Stern <stern@rowland.harvard.edu> wrote:

> Good.  The patch below ought to accomplish the same thing as that "echo" 
> command.  You can try patching your kernel and make sure that it really 
> works.  If it does, I'll submit the patch for official inclusion in the 
> kernel.
> 
I recompiled the kernel with the patch, and deactivated the debugging (to
avoid any possible slowing of the tests). After modprobing the needed
modules (ehci-hcd and usb-storage), I mounted the disks (no error, as
expected) and did the following :
- Copied about 12 Go of datas from lacie1 to lacieroot (at at least 20Mo/s,
so it didn't take long)
- Made an md5sum for all the copied files at the same time on lacie1 and
lacieroot. The resulting sums were exactly the same.
So if it doesn't look like a successful test, I don't know what does.

> I don't know why.  Do you want to turn on usb-storage verbose debugging in
> the 2.6.8 kernel, and run it on that other machine?
> [...]
> It's hard to say, since there are so many things being changed all the
> time.  But if the REPORT_LUNS command worked under 2.6.8 and failed under
> 2.6.11, it would be worthwhile to know why.
> 
OK, I will do and send the debug logs asap.

linux-usb-devel and linux-scsi (as they might be interested in the test
results for the 2.6.8 kernel) in Cc:

Regards,
Samuel Colin


  reply	other threads:[~2005-02-17 15:59 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20050214160210.6c7e7e52@hebus>
2005-02-14 21:07 ` What is SCSI command 0xa0 ? Alan Stern
2005-02-14 21:12   ` Doug Maxey
     [not found]     ` <Pine.LNX.4.44L0.0502141623440.1843-100000@ida.rowland.org>
2005-02-14 22:06       ` Samuel Colin
2005-02-16 16:42         ` Alan Stern
2005-02-17 15:59           ` Samuel Colin [this message]
2005-02-17 21:18             ` Magical ansi scsi revision (was Re: [linux-usb-devel] Re: What is SCSI command 0xa0 ?) Samuel Colin
2005-02-17 22:23               ` Alan Stern
2005-02-17 22:49                 ` Samuel Colin
2005-02-17 22:31               ` [PATCH as470] Add a NOREPORTLUN blacklist flag Alan Stern
2005-02-20 16:59                 ` Sergey Vlasov
2005-02-21  3:44                   ` Alan Stern
2005-02-21  6:47                     ` Matthew Dharm
2005-02-21 17:52                       ` Patrick Mansfield
2005-02-21 22:07                       ` Alan Stern
2005-02-28 17:26                     ` James Bottomley
2005-02-28 22:27                       ` Alan Stern
2005-02-14 21:27   ` What is SCSI command 0xa0 ? Matthias Andree
2005-02-14 21:53     ` Patrick Mansfield
2005-02-14 22:02     ` Douglas Gilbert

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=20050217165940.23cd9521@hebus \
    --to=samuel.colin3@wanadoo.fr \
    --cc=linux-scsi@vger.kernel.org \
    --cc=linux-usb-devel@lists.sourceforge.net \
    --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