From: Matt Heler <lkml@lpbproductions.com>
To: Matt <odinson@warcloud.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Promise SX-6000 Pro on 2.6.8.1
Date: Tue, 31 Aug 2004 22:09:48 -0700 [thread overview]
Message-ID: <200408312209.49117.lkml@lpbproductions.com> (raw)
In-Reply-To: <Pine.LNX.4.21.0408312351250.13904-100000@www.warcloud.net>
This is a known issue. Consider using the 2.4 kernel for the time being until
the Promise SX-6000 GPL driver can be ported to the 2.6 kernel.
Matt H.
On Tuesday 31 August 2004 9:56 pm, Matt wrote:
> Hello
>
> I have recently attempted to upgrade my kernel from 2.4.20 with
> the cryptography patches to 2.6.8.1. My promise card as addressed by the
> i2o device does not seem to get set up correctly during boot or respond
> once initialized. This card was working fine before the upgrade.
>
> I use the following statement in my lilo.conf, as probing the resulting
> raid drive, removing it seems to have no effect on the 2.6 outcome.
>
> append="hde=noprobe hdf=noprobe hdg=noprobe hdh=noprobe hdi=noprobe
> hdj=noprobe hdc=ide-scsi"
>
> lspci and cat /proc/pci (I compiled that in too.) reveal nothing about the
> card.
>
> dmesg from boot says...
>
> input: AT Translated Set 2 keyboard on isa0060/serio0
> I2O Core - (C) Copyright 1999 Red Hat Software
> I2O: Event thread created as pid 299
> i2o: Checking for PCI I2O controllers...
> PCI: Found IRQ 12 for device 0000:00:0b.1
> PCI: Sharing IRQ 12 with 0000:00:02.1
> i2o: I2O controller on bus 0 at 89.
> I2O: Promise workarounds activated.
> i2o: PCI I2O controller at CD800000 size=4194304
> i2o/iop0: Installed at IRQ12
> i2o: 1 I2O controller found and installed.
> Activating I2O controllers...
> This may take a few minutes if there are many devices
> i2o/iop0: Reset rejected, trying to clear
> i2o/iop0: SysTab setup timed out.
> i2o/iop0: Get status timeout.
> i2o/iop0: Get status timeout.
> IOP reset timeout.
> I2O Block Storage OSM v0.9
> (c) Copyright 1999-2001 Red Hat Software.
> i2o_block: Checking for Boot device...
> i2o_block: Checking for I2O Block devices...
> i2o_scsi.c: Version 0.1.2
> chain_pool: 0 bytes @ d7dbd8a0
> (512 byte buffers X 4 can_queue X 0 i2o controllers)
> md: raid1 personality registered as nr 3
>
> I included the surrounding lines for context. The pertinant lines seem to
> be;
>
> i2o/iop0: Reset rejected, trying to clear
>
> about a three min pause here normally 1 sec.
>
> i2o/iop0: SysTab setup timed out.
> i2o/iop0: Get status timeout.
>
> about a 30-45 second pause here.
>
> i2o/iop0: Get status timeout.
>
>
> My relevant? kernel options are...
>
> # I2O device support
> #
> CONFIG_I2O=y
> # CONFIG_I2O_CONFIG is not set
> CONFIG_I2O_BLOCK=y
> CONFIG_I2O_SCSI=y
> CONFIG_I2O_PROC=y
>
> When it functions normally 2.4.20(crypt) it looks like this (with context)
>
> USB Mass Storage support registered.
> I2O Core - (C) Copyright 1999 Red Hat Software
> I2O: Event thread created as pid 9
> Linux I2O PCI support (c) 1999 Red Hat Software.
> i2o: Checking for PCI I2O controllers...
> PCI: Found IRQ 12 for device 00:0b.1
> i2o: I2O controller on bus 0 at 89.
> i2o: PCI I2O controller at 0xCD800000 size=4194304
> I2O: Promise workarounds activated.
> i2o/iop0: Installed at IRQ12
> i2o: 1 I2O controller found and installed.
> Activating I2O controllers...
> This may take a few minutes if there are many devices
> i2o/iop0: Reset rejected, trying to clear
> i2o/iop0: LCT has 7 entries.
> i2o/iop0: Configuration dialog desired.
> I2O configuration manager v 0.04.
> (C) Copyright 1999 Red Hat Software
> I2O Block Storage OSM v0.9
> (c) Copyright 1999-2001 Red Hat Software.
> i2o_block: Checking for Boot device...
> i2o_block: Checking for I2O Block devices...
> i2ob: Installing tid 11 device at unit 0
> i2o/hda: Max segments 12, queue depth 8, byte limit 49152.
> i2o/hda: Type 1: 152587MB, 512 byte sectors.
> i2o/hda: Maximum sectors/read set to 96.
> i2o/hda: i2o/hda1 i2o/hda2
> i2o_scsi.c: Version 0.0.1
> chain_pool: 2048 bytes @ c1466800
> (512 byte buffers X 4 can_queue X 1 i2o controllers)
> md: raid1 personality registered as nr 3
>
> during normal boot there are no delays more than a second.
> Also in 2.4.20, cat /proc/pci reveals the following.
>
> Bus 0, device 11, function 1:
> I2O: Intel Corp. 80960RM [i960RM Microprocessor] (rev 2).
> IRQ 12.
> Master Capable. Latency=64.
> Prefetchable 32 bit memory at 0xcd800000 [0xcdbfffff].
>
> My motherboard is a K7S5A running bios 3/25/2002S
>
> My card bios version is currently 1.10.0 but they are up to 1.20.0.27. I
> am going to hold off on upgrading for now because it didn't seem to solve
> the two other writers problems, and I'd be happy to test against this
> older version if you like.
>
> As I mentioned two other people have written to the list about this,
>
> Matt H. (lkml@lpbproductions.com)
> and Alex Murphy (murphy@sgtp.samara.ru)
>
> I couldn't seem to find a response upon googling.
>
> Please CC to odinson@warcloud.net. Thanks to anybody who can help with
> this. Thank you for your time.
>
> Matt
> ---------------------------------------------------------------------------
>---- Matthew Newhall
> President of LILUG
> Long Island Linux Users Group
> president@lilug.org
> http://lilug.org
>
> It is by the fortune of God that, in this country, we have three benefits:
> freedom of speech, freedom of thought, and the wisdom never to use either.
> -- Mark Twain
> ---------------------------------------------------------------------------
>----
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2004-09-01 5:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-01 4:56 Matt
2004-09-01 5:09 ` Matt Heler [this message]
2004-09-01 11:51 ` 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=200408312209.49117.lkml@lpbproductions.com \
--to=lkml@lpbproductions.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml@lpbproduction.scom \
--cc=odinson@warcloud.net \
/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®