From: Nathan Bryant <nbryant@optonline.net>
To: Burn Alting <burn@goldweb.com.au>
Cc: SCSI development list <linux-scsi@vger.kernel.org>
Subject: Re: sd_remove() called on a tape device - Linux 2.6.8.1 kernel
Date: Thu, 26 Aug 2004 05:42:33 -0400 [thread overview]
Message-ID: <412DB089.1090403@optonline.net> (raw)
In-Reply-To: <1093494731.3549.117.camel@swtf.comptex.com.au>
Burn Alting wrote:
>I'm running Fedora Core 2 with a ftp.kernel.org 2.6.8.1 kernel.
>
>I've noticed that for some reason, when I reboot the system, it sends a
>SCSI Synchronize Cache command to a tape device I have attached to the
>system. This occurs at the end of the shutdown process just before doing
>a reset into the BIOS (or whatever).
>
>The tape is at LUN 0 and a disk is at LUN 7, the only scsi devices on
>this system (hanging off an LSI Logic FC controller). The main disk is
>an IDE.
>
>Is there anything I can do to further track this down? I know that for
>
>
Add a call to WARN_ON to the locations that can send the SYNCHRONIZE
CACHE command. That will force a stack trace.
Disable PM poweroff before you halt the system so that you can see the
trace.
>some reason the sd_remove() routine is being called rather than
>st_remove() - but not sure why. The system recognises the tape quite
>happily and reads/writes to it, so it knows what's at that scsi bus
>location.
>
>Regards
>Burn Alting
>
>-
>To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
>the body of a message to majordomo@vger.kernel.org
>More majordomo info at http://vger.kernel.org/majordomo-info.html
>
>
>
next prev parent reply other threads:[~2004-08-26 9:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-26 4:32 sd_remove() called on a tape device - Linux 2.6.8.1 kernel Burn Alting
2004-08-26 9:42 ` Nathan Bryant [this message]
2004-08-26 11:24 ` 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=412DB089.1090403@optonline.net \
--to=nbryant@optonline.net \
--cc=burn@goldweb.com.au \
--cc=linux-scsi@vger.kernel.org \
/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.