public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Douglas Gilbert <dgilbert@interlog.com>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: linux-scsi@vger.kernel.org
Subject: Re: mptspi: Unexpected doorbell active!
Date: Thu, 09 Jul 2009 22:42:08 +0200	[thread overview]
Message-ID: <4A565620.5060007@interlog.com> (raw)
In-Reply-To: <1247067320.4159.162.camel@mulgrave.site>

James Bottomley wrote:
> On Wed, 2009-07-08 at 17:06 +0200, Douglas Gilbert wrote:
>> Cute error message but it appears just before my machine
>> locks solid. It looks like it is coming from a LSI 53c1030
>> SPI controller which lspci says is PCI-X but is actually
>> PCIe.
>>
>> I get that with 2 different tape drives (LTO-1 and LTO-3)
>> whose true identities are hidden behind badge engineering,
>> Tandberg data perhaps? Anyway both seem to have a major
>> problem with the LOG SENSE command and the Tape Alert
>> page in particular.
>>
>> The lockup occurs with both a Debian Lenny standard kernel
>> (lk 2.6.26-2-686) and a kernel.org lk 2.6.30 .
> 
> So the problem has been around for a while ...
> 
>> There is nothing other than the 53c1030 and a single tape
>> drive on the SCSI bus. So there is no good reason to lock
>> up the machine for any SCSI related error.
> 
> LSI just reworked the code that does this doorbell handling for the
> 2.6.31 merge window could you see if 2.6.31-rc2 is still exhibiting the
> problem?

Yes it is.

The controller is a LSI20320IE and the main chip appears
to be a LSI53C1020A A1.

Doug Gilbert



  reply	other threads:[~2009-07-09 20:42 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-08 15:06 mptspi: Unexpected doorbell active! Douglas Gilbert
2009-07-08 15:35 ` James Bottomley
2009-07-09 20:42   ` Douglas Gilbert [this message]
2009-07-21  9:59     ` Desai, Kashyap
2009-07-08 18:06 ` Grant Grundler
2009-07-08 18:16   ` Martin K. Petersen

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=4A565620.5060007@interlog.com \
    --to=dgilbert@interlog.com \
    --cc=James.Bottomley@HansenPartnership.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