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: Mon, 14 Feb 2005 23:06:45 +0100	[thread overview]
Message-ID: <20050214230645.22eb3b3c@hebus> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0502141623440.1843-100000@ida.rowland.org>

The Mon, 14 Feb 2005 16:34:39 -0500 (EST)
Alan Stern <stern@rowland.harvard.edu> wrote:

> kernel:   Vendor: WDC WD25  Model: 00JB-00FUA0       Rev: 15.0
> kernel:   Type:   Direct-Access                      ANSI SCSI revision:
> 04
> 
> Since it claims to be SCSI revision 04, the command was sent.  But your 
> drive couldn't handle it and choked.
> 
> It's possible to prevent the SCSI driver from sending the REPORT_LUNS 
> command to your drive.  You can try this out by typing (as root):
> 
> 	echo 'WDC WD25:00JB-00FUA0:0x01' >/proc/scsi/device_info
> 
> before plugging in the drive.  If that solves the problem, it can be added
> permanently into the SCSI driver source code.
> 
OK, I just made the following tests :
- Plugged the disk and booted the openbrick
- Did the echo above
- Modprobed ehci-hcd and usb-storage
- Mounted the disk
- Made the copy of an iso image from /home (who is nfs mounted) to
/mnt/lacie1...

Absolutely no error, no odd display on the command line. Thus I guess we can
say the problem is solved so far.

You guys are wizards, you save my (geeky :-) life. I would hug you if I
could ! Also, realize that these openbricks can't have an IDE disk, and are
sometimes sold with lacie disks, so that might help other people.
What puzzles me is that a 2.6.8 kernel didn't exhibit this behaviour for the
same disk on another machine (and thus another usb2 chipset, but as that
wasn't the cause of the problem...)

In conclusion, I think that the patches from usb-devel I had applied solved
usb2 problems that had really happened (but now are solved), but some code
change introduced scsi errors (hence the working 2.6.8 kernel I tell about
above)... I don't really know, after all you're the experts.

USB devel and SCSI dev lists in Cc:

Many thanks,
Samuel Colin


  parent reply	other threads:[~2005-02-14 22:06 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 [this message]
2005-02-16 16:42         ` Alan Stern
2005-02-17 15:59           ` Samuel Colin
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=20050214230645.22eb3b3c@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