* sd_remove() called on a tape device - Linux 2.6.8.1 kernel
@ 2004-08-26 4:32 Burn Alting
2004-08-26 9:42 ` Nathan Bryant
0 siblings, 1 reply; 3+ messages in thread
From: Burn Alting @ 2004-08-26 4:32 UTC (permalink / raw)
To: SCSI development list
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
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
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: sd_remove() called on a tape device - Linux 2.6.8.1 kernel
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
2004-08-26 11:24 ` Douglas Gilbert
0 siblings, 1 reply; 3+ messages in thread
From: Nathan Bryant @ 2004-08-26 9:42 UTC (permalink / raw)
To: Burn Alting; +Cc: SCSI development list
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
>
>
>
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: sd_remove() called on a tape device - Linux 2.6.8.1 kernel
2004-08-26 9:42 ` Nathan Bryant
@ 2004-08-26 11:24 ` Douglas Gilbert
0 siblings, 0 replies; 3+ messages in thread
From: Douglas Gilbert @ 2004-08-26 11:24 UTC (permalink / raw)
To: Nathan Bryant; +Cc: Burn Alting, SCSI development list
Nathan Bryant wrote:
> 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.
Burn,
The scsi_debug driver can simulate tape drives (although the
streaming command set support is weak). For example:
# modprobe scsi_debug ptype=1 opts=1
will simulate one tape drive and log commands sent to it.
Doug Gilbert
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2004-08-26 11:25 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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
2004-08-26 11:24 ` Douglas Gilbert
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).