mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
* Re: Promise SX6000 No handler for event (fwd)
  2003-05-20 14:11 Promise SX6000 No handler for event (fwd) kernel
@ 2003-05-20 14:03 ` Alan Cox
  0 siblings, 0 replies; 2+ messages in thread
From: Alan Cox @ 2003-05-20 14:03 UTC (permalink / raw)
  To: kernel; +Cc: Linux Kernel Mailing List

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


^ permalink raw reply	[flat|nested] 2+ messages in thread

* Promise SX6000 No handler for event (fwd)
@ 2003-05-20 14:11 kernel
  2003-05-20 14:03 ` Alan Cox
  0 siblings, 1 reply; 2+ messages in thread
From: kernel @ 2003-05-20 14:11 UTC (permalink / raw)
  To: linux-kernel

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. 

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2003-05-20 14:48 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2003-05-20 14:11 Promise SX6000 No handler for event (fwd) kernel
2003-05-20 14:03 ` Alan Cox

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®