From: Matthew Wilcox <matthew@wil.cx>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-acpi@vger.kernel.org, len.brown@intel.com,
linux-scsi@vger.kernel.org, willy@debian.org
Subject: Re: git-acpi breakage, sym2
Date: Fri, 12 May 2006 05:40:46 -0600 [thread overview]
Message-ID: <20060512114046.GO12272@parisc-linux.org> (raw)
In-Reply-To: <20060512042504.33b1ad20.akpm@osdl.org>
On Fri, May 12, 2006 at 04:25:04AM -0700, Andrew Morton wrote:
> Matthew Wilcox <matthew@wil.cx> wrote:
> > > scsi0 : sym-2.2.3
> > > 0:0:0:0: ABORT operation started.
> > > 0:0:1:0: ABORT operation started.
> > > 0:0:2:0: ABORT operation started.
> > >
> > > ad infinitum. How come?
> >
> > Are you sure it's ad infinitum or just once for every device?
>
> I have a single card talking to a single disk. I whacked it after a couple
> of minutes.
Sure, but it has to probe each device to find out it's not there. See
the target number increasing in the snippet I left above?
> > Anyway, this looks like a fairly classic "sym2 isn't getting any
> > interrupts" scenario.
>
> It is - Len found that one.
Cool. I'd love sym2 to behave more sanely in the 'no interrupts' case
because it means I get a lot of bug reports directed my way from people
with bad setups. I don't see a nice way to do it though ...
next prev parent reply other threads:[~2006-05-12 11:40 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
2006-05-12 11:25 ` Andrew Morton
2006-05-12 11:40 ` Matthew Wilcox [this message]
-- 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=20060512114046.GO12272@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.