public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Bernd Schubert <bernd-schubert@gmx.de>
To: "Moore, Eric" <Eric.Moore@lsi.com>
Cc: James Bottomley <James.Bottomley@steeleye.com>,
	linux-scsi@vger.kernel.org
Subject: Re: I/O errors on 6TB device
Date: Sun, 17 Dec 2006 00:00:52 +0100	[thread overview]
Message-ID: <200612170000.52606.bernd-schubert@gmx.de> (raw)
In-Reply-To: <664A4EBB07F29743873A87CF62C26D702A9967@NAMAIL4.ad.lsil.com>

[-- Attachment #1: Type: text/plain, Size: 2229 bytes --]

On Saturday 16 December 2006 22:03, Moore, Eric wrote:
> On Sat 12/16/2006 8:28 AM,  James Bottomley wrote:
> >> [17179724.816000] Fusion MPT base driver 3.03.07
> >> [17179724.816000] Copyright (c) 1999-2005 LSI Logic Corporation
> >> [17179724.832000] Fusion MPT SPI Host driver 3.03.07
>
> 3.03.07 driver is about a year old.  Which kernel and distro
> are you on?

Eric, thanks for your help. Its 2.6.16.36 on Debian Sarge, using most recent 
kernel version is not always a good idea on server systems - too many 
regressions. 
Attached is dmesg output from 2.6.19.1.

>
> >> [17179726.100000]  sda:<6>sd 0:0:1:0: SCSI error: return code = 0xb0000
> >> [17179726.132000] end_request: I/O error, dev sda, sector 12691101688
> >
> > This is definitely a fusion driver error: it's DID_SOFT_ERROR, which
> > that driver returns for a variety of firmware related conditions or
> > transfer underruns.
>
> Correct, DID_SOFT_ERROR is returned in many cases.
>
> Can you recompile the driver with some debug messages enabled
> in the driver Makefile so I can observe the return codes from firmware.
> You will need to uncomment MPT_DEBUG_REPLY in the Makefile.

Sure, its enabled now.

>
>
> FwRev=01030600h is version 1.03.06, which is quite old.  Try
> obtaining a newer one from the lsi download site.  I believe
> the newest fw internally is 1.03.34.

Until Monday I don't have physical access to the machine, so an update from 
DOS is not possible now. However, I see there is also a linux mptflash, I 
just can't get it compiled.

gcc -g -O -Wall -I..   -c -o mptflash.o mptflash.c
In file included from ../mptbase.h:58,
                 from mptflash.c:13:
../linux_compat.h:9:30: error: scsi/scsi_device.h: No such file or directory
../linux_compat.h:10:28: error: scsi/scsi_cmnd.h: No such file or directory

The kernel_headers in Debian don't have these files and including the header 
files directly from the kernel tree doesn't work. 
Do you have newer sources (the most recent version I could find are from 
mptlinux-3.02.60) or a working binary?


Thanks,
Bernd

-- 
Bernd Schubert
PCI / Theoretische Chemie
Universität Heidelberg
INF 229
69120 Heidelberg


[-- Attachment #2: dmesg.log.gz --]
[-- Type: application/x-gzip, Size: 9438 bytes --]

      parent reply	other threads:[~2006-12-16 23:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-16 12:12 I/O errors on 6TB device Bernd Schubert
2006-12-16 15:28 ` James Bottomley
2006-12-16 16:28   ` Bernd Schubert
     [not found]   ` <664A4EBB07F29743873A87CF62C26D702A9967@NAMAIL4.ad.lsil.com>
2006-12-16 23:00     ` Bernd Schubert [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=200612170000.52606.bernd-schubert@gmx.de \
    --to=bernd-schubert@gmx.de \
    --cc=Eric.Moore@lsi.com \
    --cc=James.Bottomley@steeleye.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox