public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Matthew Wilcox <matthew@wil.cx>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-acpi@vger.kernel.org, "Brown, Len" <len.brown@intel.com>,
	linux-scsi@vger.kernel.org, Matthew Wilcox <willy@debian.org>
Subject: Re: git-acpi breakage, sym2
Date: Fri, 12 May 2006 05:23:45 -0600	[thread overview]
Message-ID: <20060512112345.GM12272@parisc-linux.org> (raw)
In-Reply-To: <20060511231005.0bce3384.akpm@osdl.org>

On Thu, May 11, 2006 at 11:10:05PM -0700, Andrew Morton wrote:
> The above bug appears to trigger a scsi or sym2 bug.  With git-acpi.patch
> present I get
> 
> sym0: <895> rev 0x2 at pci 0000:02:0c.0 irq 9
> sym0: Symbios NVRAM, ID 7, Fast-40, SE, parity checking
> sym0: SCSI BUS has been reset.
> scsi0 : sym-2.2.3
>  target0:0:0: Multiple LUNs disabled in NVRAM
>  0:0:0:0: ABORT operation started.
>  0:0:0:0: ABORT operation timed-out.
>  0:0:0:0: DEVICE RESET operation started.
>  0:0:0:0: DEVICE RESET operation timed-out.
>  0:0:0:0: BUS RESET operation started.
>  0:0:0:0: BUS RESET operation timed-out.
>  0:0:0:0: HOST RESET operation started.
> sym0: SCSI BUS has been reset.
>  0:0:0:0: HOST RESET operation timed-out.
>  0:0:0:0: scsi: Device offlined - not ready after error recovery
>  0:0:1:0: ABORT operation started.
>  0:0:1:0: ABORT operation timed-out.
>  0:0:1:0: DEVICE RESET operation started.
>  0:0:1:0: DEVICE RESET operation timed-out.
>  0:0:1:0: BUS RESET operation started.
>  0:0:1:0: BUS RESET operation timed-out.
>  0:0:1:0: HOST RESET operation started.
> sym0: SCSI BUS has been reset.
>  0:0:1:0: HOST RESET operation timed-out.
>  0:0:1:0: scsi: Device offlined - not ready after error recovery
>  0:0:2:0: ABORT operation started.
>  0:0:2:0: ABORT operation timed-out.
>  0:0:2:0: DEVICE RESET operation started.
>  0:0:2:0: DEVICE RESET operation timed-out.
>  0:0:2:0: BUS RESET operation started.
>  0:0:2:0: BUS RESET operation timed-out.
>  0:0:2:0: HOST RESET operation started.
> sym0: SCSI BUS has been reset.
> 
> ad infinitum.  How come?

Are you sure it's ad infinitum or just once for every device?
Anyway, this looks like a fairly classic "sym2 isn't getting any
interrupts" scenario.


  reply	other threads:[~2006-05-12 11:23 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-12  6:10 git-acpi breakage, sym2 Andrew Morton
2006-05-12 11:23 ` Matthew Wilcox [this message]
2006-05-12 11:25   ` Andrew Morton
2006-05-12 11:40     ` Matthew Wilcox
  -- strict thread matches above, loose matches on Subject: below --
2006-05-12  7:26 Brown, Len
2006-05-12  7:35 ` Andrew Morton

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=20060512112345.GM12272@parisc-linux.org \
    --to=matthew@wil.cx \
    --cc=akpm@osdl.org \
    --cc=len.brown@intel.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=willy@debian.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