From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: kernel <kernel@mousebusiness.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Promise SX6000 No handler for event (fwd)
Date: 20 May 2003 15:03:12 +0100 [thread overview]
Message-ID: <1053439391.30547.30.camel@dhcp22.swansea.linux.org.uk> (raw)
In-Reply-To: <20030520141152.5916.qmail@srvr1.mousebusiness.com>
On Maw, 2003-05-20 at 15:11, kernel wrote:
> > It sent us two event messages for events we've never head of (or asked
> > for)
> If we never asked for these messages, why did it send them?
Ask the vendor
> >
> >> May 19 13:06:04 production kernel: i2o/iop0: Hardware Failure: Unknown Error
> >
> > and then exploded
> >
> Yep. That's what's happening. Now, how do I defuse it? I *think* I'm setting
> this up just as suggested on this list and various other sources, yet still
> it is a no-go.
Ask the vendor. I've traced one of these with an end user and we didnt
send a single invalid I2O message to it
> NFS-mounted volume from an old, slow, busy server to my RAID. This tells me
> that probably the errors aren't caused by the SX6000 getting floodded by
> incoming data stream and not being able to keep up with it.
That would seem to be a bug in the controller firmware if so. You might
be able to reduce it or mitigate it by reducing the request queue size
we run.
Alan
prev parent reply other threads:[~2003-05-20 14:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-20 14:11 kernel
2003-05-20 14:03 ` Alan Cox [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=1053439391.30547.30.camel@dhcp22.swansea.linux.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=kernel@mousebusiness.com \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®