public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@SteelEye.com>
To: Andrew Morton <akpm@osdl.org>
Cc: "Martin J. Bligh" <mbligh@mbligh.org>,
	Linux Kernel <linux-kernel@vger.kernel.org>,
	SCSI Mailing List <linux-scsi@vger.kernel.org>
Subject: Re: Symbios problems in recent -mm trees?
Date: Fri, 05 Aug 2005 09:24:52 -0500	[thread overview]
Message-ID: <1123251892.5003.6.camel@mulgrave> (raw)
In-Reply-To: <20050804233927.2d3abb16.akpm@osdl.org>

On Thu, 2005-08-04 at 23:39 -0700, Andrew Morton wrote:
> James, could some of the scsi core rework have caused this?

Well, I don't think so.  The error below:

> > sdc: Unit Not Ready, sense:
> > : Current: sense key=0x0
> >     ASC=0x0 ASCQ=0x0
> >  target0:0:10: FAST-40 WIDE SCSI 80.0 MB/s DT (25 ns, offset 31)
> > Device  not ready.
> >  target0:0:10: FAST-40 WIDE SCSI 80.0 MB/s DT (25 ns, offset 31)
> > Device  not ready.
> >  target0:0:10: FAST-40 WIDE SCSI 80.0 MB/s DT (25 ns, offset 31)
> > Device  not ready.
> > sdc : READ CAPACITY failed.
> > sdc : status=1, message=00, host=0, driver=08 
> > sd: Current: sense key=0x0
> >     ASC=0x0 ASCQ=0x0

Is coming from the disk not the symbios driver ... I think you have a
disk failure.

James



  reply	other threads:[~2005-08-05 14:25 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-05  4:33 Symbios problems in recent -mm trees? Martin J. Bligh
2005-08-05  6:39 ` Andrew Morton
2005-08-05 14:24   ` James Bottomley [this message]
2005-08-05 14:36     ` [Bugme-new] [Bug 5003] New: Problem with symbios driver on recent -mm trees Martin J. Bligh
2005-08-05 15:01       ` James Bottomley
2005-08-09  4:41         ` Martin J. Bligh
2005-08-09 14:26           ` James Bottomley
2005-08-09 14:59             ` Martin J. Bligh
2005-08-09 16:55               ` James Bottomley
2005-08-09 23:23                 ` Martin J. Bligh

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=1123251892.5003.6.camel@mulgrave \
    --to=james.bottomley@steeleye.com \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=mbligh@mbligh.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox