All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Lord <liml@rtr.ca>
To: Matthew Wilcox <matthew@wil.cx>
Cc: linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: ata_ram driver
Date: Fri, 22 Feb 2008 16:27:48 -0500	[thread overview]
Message-ID: <47BF3E54.9050609@rtr.ca> (raw)
In-Reply-To: <20080222200951.GI16995@parisc-linux.org>

Matthew Wilcox wrote:
> I've ported the scsi_ram driver [1] to libata.  It could use a lot more
> work -- there's a lot of stuff in the identify page that I haven't
> filled in, and there's a lot of commands it doesn't even try to execute.
> 
> For example, when you unload the driver, you get the mildly disturbing
> messages:
> 
> sd 12:0:0:0: [sdb] Stopping disk
> sd 12:0:0:0: [sdb] START_STOP FAILED
> sd 12:0:0:0: [sdb] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
> 
..

I see messages like those with *established* libata drivers from time to time.
It could just be a bug in the shutdown sequence, somewhere between libata,
SCSI, block layer, and the device model in general.  Or not.

Cheers

  reply	other threads:[~2008-02-22 21:27 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-22 20:09 ata_ram driver Matthew Wilcox
2008-02-22 21:27 ` Mark Lord [this message]
2008-03-06  8:21   ` Tejun Heo
2008-03-06 15:28     ` James Bottomley
2008-03-06 23:55       ` Tejun Heo
2008-03-07  0:01         ` James Bottomley
2008-03-07  0:13           ` Tejun Heo
2008-03-07  0:22             ` James Bottomley
2008-03-07  0:28               ` Tejun Heo
2008-03-07  0:39                 ` James Bottomley
2008-03-07  0:43                   ` Tejun Heo
2008-03-07  3:08                     ` [PATCH 1/2] scsi: export scsi_forget_host() Tejun Heo
2008-03-07  3:08                       ` Tejun Heo
2008-03-07  3:11                       ` [PATCH 2/2] libata: kill SCSI devices before detaching ata_host Tejun Heo
2008-03-07  2:16                 ` ata_ram driver Jeff Garzik
2008-03-07  2:44                   ` James Bottomley

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=47BF3E54.9050609@rtr.ca \
    --to=liml@rtr.ca \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matthew@wil.cx \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.