From: "kernel" <kernel@mousebusiness.com>
To: linux-kernel@vger.kernel.org
Subject: Promise SX6000 No handler for event (fwd)
Date: Tue, 20 May 2003 09:11:52 -0500 [thread overview]
Message-ID: <20030520141152.5916.qmail@srvr1.mousebusiness.com> (raw)
Alan Cox writes:
>> May 19 13:05:59 production kernel: i2o/iop0: No handler for event
>> (0x00000020)
>> May 19 13:05:59 production kernel: i2o/iop0: No handler for event
>> (0x00000020)
>
> 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?
>
>> 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.
Btw. I got those error messages while trying to copy data from an
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.
next reply other threads:[~2003-05-20 14:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-20 14:11 kernel [this message]
2003-05-20 14:03 ` Alan Cox
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=20030520141152.5916.qmail@srvr1.mousebusiness.com \
--to=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®