From: GOTO Masanori <gotom@debian.or.jp>
To: Tobias Rittweiler <inkognito.anonym@uni.de>
Cc: linux-kernel@vger.kernel.org, linux-scsi@vger.opensource.gr.jp,
kernel.org@oris.opensource.gr.jp
Subject: Re: [2.5.50] odd SCSI messages on shutdown
Date: Sun, 08 Dec 2002 14:09:43 +0900 [thread overview]
Message-ID: <80isy5f65k.wl@oris.opensource.jp> (raw)
In-Reply-To: <17730135168.20021206223444@uni.de>
At Fri, 6 Dec 2002 22:34:44 +0100,
Tobias Rittweiler wrote:
> on shutdown the following lines are displayed, but _not_ logged to
> /var/log/messages:
>
> Going to halt the system ...
> Synchronizing SCSI caches: sda FAILED
> status = 1, message = 00, host = 0, driver = 08
> Current sd?: sense = 70 5
> ASC=20 ASCQ= 0
> Raw sense data:0x70 0x00 0x05 0x00 0x00 0x00 0x00 0x0e 0x00 0x00 0x00
> 0x00 0x20 0x00 0x00 0xc0 0x00 0x00 0x00 0x00 0x00
> Power off.
Your device cannot handle SYNCHRONIZED_CACHE command which flushes
Seagate ST52160N device cache during shutdown introduced in recent 2.5.
I think the below patch for 2.5.50 (and current BK) suppresses such
failure message.
--- drivers/scsi/sd.c 2002-11-23 06:40:54.000000000 +0900
+++ drivers/scsi/sd.c.new 2002-12-08 13:14:13.000000000 +0900
@@ -865,8 +865,10 @@
if(status_byte(the_result) == CHECK_CONDITION
&& (SRpnt->sr_sense_buffer[0] & 0x70) == 0x70
&& (SRpnt->sr_sense_buffer[2] & 0x0f) == ILLEGAL_REQUEST
- /* The next are ASC 0x24 ASCQ 0x00: Invalid field in CDB */
- && SRpnt->sr_sense_buffer[12] == 0x24
+ /* The next are ASC 0x24 ASCQ 0x00: Invalid field in CDB,
+ or ASC 0x20 ASCQ 0x00: Invalid command operation code. */
+ && (SRpnt->sr_sense_buffer[12] == 0x24 ||
+ SRpnt->sr_sense_buffer[12] == 0x20)
&& SRpnt->sr_sense_buffer[13] == 0x00) {
printk(KERN_NOTICE "SCSI device %s: cache data unavailable\n", diskname);
} else {
-- gotom
prev parent reply other threads:[~2002-12-08 5:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-06 21:34 [2.5.50] odd SCSI messages on shutdown Tobias Rittweiler
2002-12-08 5:09 ` GOTO Masanori [this message]
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=80isy5f65k.wl@oris.opensource.jp \
--to=gotom@debian.or.jp \
--cc=inkognito.anonym@uni.de \
--cc=kernel.org@oris.opensource.gr.jp \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.opensource.gr.jp \
/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.