All of lore.kernel.org
 help / color / mirror / Atom feed
From: Csillag Tamas <cstamas@digitus.itk.ppke.hu>
To: linux-scsi@vger.kernel.org
Subject: megaraid not working in 2.6.18
Date: Tue, 10 Oct 2006 11:07:29 +0200	[thread overview]
Message-ID: <20061010090729.GD905@digitus> (raw)

[-- Attachment #1: Type: text/plain, Size: 4596 bytes --]

hi,

I have two servers with AMI megaraid.
They both runnig 2.6.11.*

I want to upgrade to 2.6.18. The problem is: the driver does not work
anymore.

If I try the new driver, the kernel freezes after I see a stack trace
dump. It is OK, I read somewhere that I should not use this new one as
it does not support my old cards.

However the legacy megaraid drivers does not work either. I get
unknown-block-device error when the kernel tries to mount sdaX.
I do not even see the megaraid driver coming up! no detecting messages like
in 2.6.11

This page: http://linux.dell.com/storage.shtml#megaraid lead me to this
list.

# lspci -v
0000:00:00.0 Host bridge: ServerWorks CNB20LE Host Bridge (rev 06)
        Flags: bus master, medium devsel, latency 48

0000:00:00.1 Host bridge: ServerWorks CNB20LE Host Bridge (rev 06)
        Flags: bus master, medium devsel, latency 32

0000:00:02.0 Ethernet controller: Intel Corp. 82557/8/9 [Ethernet Pro 100] (rev 0d)
        Subsystem: Hewlett-Packard Company NetServer 10/100TX
        Flags: bus master, medium devsel, latency 64, IRQ 10
        Memory at fd020000 (32-bit, non-prefetchable) [size=4K]
        I/O ports at 1800 [size=64]
        Memory at fd000000 (32-bit, non-prefetchable) [size=128K]
        Capabilities: [dc] Power Management version 2

0000:00:04.0 Ethernet controller: Intel Corp. 82557/8/9 [Ethernet Pro 100] (rev 08)
        Subsystem: Hewlett-Packard Company NetServer 10/100TX
        Flags: bus master, medium devsel, latency 64, IRQ 5
        Memory at fd021000 (32-bit, non-prefetchable) [size=4K]
        I/O ports at 1840 [size=64]
        Memory at fd100000 (32-bit, non-prefetchable) [size=1M]
        Capabilities: [dc] Power Management version 2

0000:00:06.0 RAID bus controller: American Megatrends Inc. MegaRAID (rev 20)
        Subsystem: Hewlett-Packard Company: Unknown device 60e7
        Flags: bus master, medium devsel, latency 64, IRQ 11
        Memory at fd400000 (32-bit, prefetchable) [size=64K]
        Capabilities: [80] Power Management version 2

0000:00:07.0 VGA compatible controller: ATI Technologies Inc Rage XL (rev 27) (prog-if 00 [VGA])
        Subsystem: Hewlett-Packard Company: Unknown device 10e1
        Flags: bus master, stepping, medium devsel, latency 66, IRQ 11
        Memory at fc000000 (32-bit, non-prefetchable) [size=16M]
        I/O ports at 1400 [size=256]
        Memory at fd022000 (32-bit, non-prefetchable) [size=4K]
        Capabilities: [5c] Power Management version 2

0000:00:0f.0 Host bridge: ServerWorks CSB5 South Bridge (rev 93)
        Subsystem: Hewlett-Packard Company: Unknown device 129b
        Flags: bus master, medium devsel, latency 32

0000:00:0f.1 IDE interface: ServerWorks CSB5 IDE Controller (rev 93) (prog-if 8a [Master SecP PriP])
        Subsystem: Hewlett-Packard Company: Unknown device 129b
        Flags: bus master, medium devsel, latency 32
        I/O ports at <ignored>
        I/O ports at <ignored>
        I/O ports at <ignored>
        I/O ports at <ignored>
        I/O ports at 1880 [size=16]

0000:00:0f.2 USB Controller: ServerWorks OSB4/CSB5 OHCI USB Controller (rev 05) (prog-if 10 [OHCI])
        Subsystem: Hewlett-Packard Company: Unknown device 129b
        Flags: medium devsel, IRQ 11
        Memory at fd023000 (32-bit, non-prefetchable) [size=4K]

0000:00:0f.3 ISA bridge: ServerWorks CSB5 LPC bridge
        Subsystem: Hewlett-Packard Company: Unknown device 129b
        Flags: bus master, medium devsel, latency 0

0000:05:04.0 SCSI storage controller: LSI Logic / Symbios Logic 53c1010 66MHz  Ultra3 SCSI Adapter (rev 01)
        Subsystem: Hewlett-Packard Company: Unknown device 60a0
        Flags: bus master, 66MHz, medium devsel, latency 72, IRQ 9
        I/O ports at 1c00 [size=256]
        Memory at fd412000 (64-bit, non-prefetchable) [size=1K]
        Memory at fd410000 (64-bit, non-prefetchable) [size=8K]
        Capabilities: [40] Power Management version 2

0000:05:04.1 SCSI storage controller: LSI Logic / Symbios Logic 53c1010 66MHz  Ultra3 SCSI Adapter (rev 01)
        Subsystem: Hewlett-Packard Company: Unknown device 60a0
        Flags: bus master, 66MHz, medium devsel, latency 72, IRQ 11
        I/O ports at 2000 [size=256]
        Memory at fd412400 (64-bit, non-prefetchable) [size=1K]
        Memory at fd414000 (64-bit, non-prefetchable) [size=8K]
        Capabilities: [40] Power Management version 2

I attach my kernel config file too (for 2.6.18).

Thanks in advance. Ask for more info if needed.
please cc to me.
-- 

CSILLAG Tamas (cstamas) - http://digitus.itk.ppke.hu/~cstamas

[-- Attachment #2: config.gz --]
[-- Type: application/octet-stream, Size: 8931 bytes --]

             reply	other threads:[~2006-10-10  9:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-10  9:07 Csillag Tamas [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-10-10 13:03 megaraid not working in 2.6.18 Ju, Seokmann
2006-10-11  6:57 ` Csillag Tamas

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=20061010090729.GD905@digitus \
    --to=cstamas@digitus.itk.ppke.hu \
    --cc=linux-scsi@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.