[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200729145656.GA1574246@rowland.harvard.edu>
Date: Wed, 29 Jul 2020 10:56:56 -0400
From: Alan Stern <stern@...land.harvard.edu>
To: "Martin K. Petersen" <martin.petersen@...cle.com>
Cc: Martin Kepplinger <martin.kepplinger@...i.sm>,
Bart Van Assche <bvanassche@....org>, jejb@...ux.ibm.com,
Can Guo <cang@...eaurora.org>, linux-scsi@...r.kernel.org,
linux-kernel@...r.kernel.org, kernel@...i.sm
Subject: Re: [PATCH] scsi: sd: add runtime pm to open / release
On Wed, Jul 29, 2020 at 10:44:26AM -0400, Martin K. Petersen wrote:
>
> Alan,
>
> >> [ 77.474632] sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result:
> >> hostbyte=0x00 driverbyte=0x08 cmd_age=0s
> >> [ 77.474647] sd 0:0:0:0: [sda] tag#0 Sense Key : 0x6 [current]
> >> [ 77.474655] sd 0:0:0:0: [sda] tag#0 ASC=0x28 ASCQ=0x0
> >> [ 77.474667] sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x28 28 00 00 00 60
> >> 40 00 00 01 00
> >
> > This error report comes from the SCSI layer, not the block layer.
>
> This the device telling us that the media (SD card?) has changed.
Ah yes, thank you. I knew that SK=6 ASC=0x28 meant "Not Ready to Ready
Transition", but I had forgotten the "(Media May Have Changed)" part.
This makes sense and is a reasonable thing to see, since many SD card
readers lose track of whether or not the card has been changed when they
go into suspend.
Alan Stern
Powered by blists - more mailing lists