public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Elizabeth Morris-Baker <eamb@liu.fafner.com>
To: mdharm-kernel@one-eyed-alien.net (Matthew Dharm)
Cc: eamb@liu.fafner.com (Elizabeth Morris-Baker),
	chen_xiangping@emc.com (chen xiangping),
	linux-kernel@vger.kernel.org ('linux-kernel@vger.kernel.org')
Subject: Re: scsi init problem in 2.4.0-test10?
Date: Thu, 2 Nov 2000 16:45:25 -0600 (CST)	[thread overview]
Message-ID: <200011022245.QAA08323@liu.fafner.com> (raw)
In-Reply-To: <20001102145320.A27745@one-eyed-alien.net> from "Matthew Dharm" at Nov 02, 2000 02:53:20 PM

> 

	You need to send the TUR first, but yes, 
	START_STOP will guarantee that you are
	ready to rock and roll.
	The first fix I wrote did a TUR, then
	3 tries at a START_STOP, till it worked.
	
	cheers, 

	Elizabeth
	
> 
> --8t9RHnE3ZwKMSgU+
> Content-Type: text/plain; charset=us-ascii
> Content-Disposition: inline
> Content-Transfer-Encoding: quoted-printable
> 
> On Thu, Nov 02, 2000 at 03:58:24PM -0600, Elizabeth Morris-Baker wrote:
> > 	Basically the problem is in scan_scsis_single.
> > 	Some scsi devices are notoriously brain dead
> > 	about answering inquiries without having=20
> > 	recived a TUR and then spinning up.
> > 	The problem seems to be the disk, not the controller,
> > 	if this is the same problem.
> >=20
> > 	The problem appeared in the test kernels because
> > 	the TUR *used* to be there, now it is not.
> 
> Strictly speaking, shouldn't we send a START_STOP, not a TUR to get the
> disks (or other devices) to spin up?
> 
> Matt
> 
> --=20
> Matthew Dharm                              Home: mdharm-usb@one-eyed-alien.=
> net=20
> Maintainer, Linux USB Mass Storage Driver
> 
> S:  Another stupid question?
> G:  There's no such thing as a stupid question, only stupid people.
> 					-- Stef and Greg
> User Friendly, 7/15/1998
> 
> --8t9RHnE3ZwKMSgU+
> Content-Type: application/pgp-signature
> Content-Disposition: inline
> 
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.0.4 (GNU/Linux)
> Comment: For info see http://www.gnupg.org
> 
> iD8DBQE6AfBfz64nssGU+ykRAiG4AJ9d96tbBNs6zCwR8qIkGs5fJGs6EQCeLtO9
> khi+5UEoM5/apYkaEBBgnow=
> =/YMd
> -----END PGP SIGNATURE-----
> 
> --8t9RHnE3ZwKMSgU+--
> 

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

  reply	other threads:[~2000-11-02 23:05 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-11-02 21:49 scsi init problem in 2.4.0-test10? chen, xiangping
2000-11-02 21:58 ` Elizabeth Morris-Baker
2000-11-02 22:53   ` Matthew Dharm
2000-11-02 22:45     ` Elizabeth Morris-Baker [this message]
2000-11-02 23:50       ` Torben Mathiasen
2000-11-03  0:24         ` scsi init problem in 2.4.0-test10? [PATCH] Elizabeth Morris-Baker
2000-11-03  1:02           ` David Weinehall
2000-11-03  1:44             ` Elizabeth Morris-Baker
2000-11-03  1:37 ` scsi init problem in 2.4.0-test10? stefan mojschewitsch
  -- strict thread matches above, loose matches on Subject: below --
2000-11-02 23:24 chen, xiangping
2000-11-03  0:49 chen, xiangping

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=200011022245.QAA08323@liu.fafner.com \
    --to=eamb@liu.fafner.com \
    --cc=chen_xiangping@emc.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mdharm-kernel@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