mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Stuffed Crust <pizza@shaftnet.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.19-rc3-ac2 I2O (Promise SX6000) funkiness
Date: 25 Jul 2002 11:35:48 +0100	[thread overview]
Message-ID: <1027593348.9488.16.camel@irongate.swansea.linux.org.uk> (raw)
In-Reply-To: <20020725034316.GA4501@shaftnet.org>

On Thu, 2002-07-25 at 04:43, Stuffed Crust wrote:
> It starts out fine, then the console starts spewing these messages after
> about 30/2664 inode tables.
> 
> 	i2o/iop0: No handler for event (0x00000020)
> 	i2o/iop0: No handler for event (0x00000020)
> 	i2o/iop0: No handler for event (0x00000020)
> 	i2o/iop0: No handler for event (0x00000020)
> 	i2o/iop0: No handler for event (0x00000020)

Its spewing events we didnt ask for then it dies

> 
> 	i2o/iop0: Hardware Failure: Unknown Error  
> 	i2o/iop0: Hardware Failure: Unknown Error  
> 	i2o/iop0: Hardware Failure: Unknown Error  

That says it all. Thats a message from the controller on the SX6000
saying "I broke".

> FWIW, this is a newer SX6000 with PDC20276 chips on it, and it's sharing
> IRQ10 with the usb controller.  Disabling it makes no difference.

You will need at list 2.4.19ac from a cold boot for this card to work.
Also check your boot logs to ensure it skipped over the PDC20276
controllers correctly. I think the code is right but I am not yet sure.

If we don't skip the 20276 chips properly then we reconfigure them and
the raid card has kittens (rightly so)

> Further details can be provided upon request...
> 
> I can move the controller to another machine this weekend for further
> testing.  But in the mean time, Just what is event 0x00000020?

Its an invalid I2O event code. Promise cards emit them before crashing
when you ask them to do anything they take offence too.

> I suppose I can call up Promise, but as their driver won't even compile,
> I don't have much faith in their ability to do anything but shave a
> couple of hours off of my life.

Actually the promise provided driver for the supertrak cards seems to
work fine. I actually used it to debug the generic i2o_block support for
their chips. It won't help if we are eating the ide controllers however


      reply	other threads:[~2002-07-25  9:18 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-25  3:43 Stuffed Crust
2002-07-25 10:35 ` 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=1027593348.9488.16.camel@irongate.swansea.linux.org.uk \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pizza@shaftnet.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®