Skip to contentSkip to conversation

New: MegaRAID Legacy doesn't work with LSI MegaRAID i4 since release 2.00.4

Bugme-new Andrew Morton 3 participants 5 messages Feb 13, 2007 – Feb 14, 2007 SCSI

lore
Share & tools
lore
#0 lore raw

Begin forwarded message:

Date: Tue, 13 Feb 2007 04:38:49 -0800
From: [email protected]
To: [email protected]
Subject: [Bugme-new] [Bug 7999] New: MegaRAID Legacy doesn't work with LSI MegaRAID i4 since release 2.00.4

http://bugzilla.kernel.org/show_bug.cgi?id=7999

           Summary: MegaRAID Legacy doesn't work with LSI MegaRAID i4 since
                    release 2.00.4
    Kernel Version: 2.6.20
            Status: NEW
          Severity: blocking
             Owner: [email protected]
         Submitter: [email protected]

Most recent kernel where this bug did *NOT* occur:2.6.14 ? Distribution:Debian Sarge
Hardware Environment: Asus A7V266 M/B, Adaptec AHA-2940UW, LSI MegaRAID 511 i4 Software Environment:
Problem Description: My MegaRAID i4 adapter, witch works well on linux 2.6.11.6 kernel, doesn't work anymore with newer kernels whereas I use the same config file (updated by 'make oldconfig') I compared megaraid.c from 2.6.11 and 2.6.20 and I noticed megaraid version goes from 2.00.3 to 2.00.4, so I guess the problem is here ?

Steps to reproduce: simply compile a kernel >= 2.6.15 with megaraid legacy support !

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.

#1 lore raw
Quoted 1 line · Andrew Morton

Subject: [Bugme-new] [Bug 7999] New: MegaRAID Legacy doesn't work with LSI MegaRAID i4 since release 2.00.4

This is by design ... the i4 is now supported by the new megaraid_mbox driver. Please retry with that driver.

James

#2 lore raw
Quoted 3 lines · James Bottomley

This is by design ... the i4 is now supported by the new megaraid_mbox driver. Please retry with that driver.

Damn ! I spent many hours trying many kernel version, but I never imagined the card support would be translated on megaraid NG !!!

By the way, I added megaraid NG modules on my 2.6.20 and my i4 card is now recognized... But I can't figure how it works :

hole:/home/rico# lsmod|grep megaraid
megaraid_mbox          35368  0
megaraid_mm            12068  1 megaraid_mbox
megaraid               41704  1
scsi_mod              151980  7 megaraid_mbox,sr_mod,sd_mod,megaraid,sg,aic7xxx,scsi_transport_spi
ho

So if I understand well, the module actively used with the LSI card is megaraid, the legacy one ! but the mbox and mm are loaded and seems to be necessary for the legacy driver ?

Never mind, sorry for the inconvenience... and the noise on the lkdml !

Regards,

Signature · 5 lines
Rico
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
#3 lore raw
Quoted 11 lines · Eric Belhomme
hole:/home/rico# lsmod|grep megaraid
megaraid_mbox          35368  0
megaraid_mm            12068  1 megaraid_mbox
megaraid               41704  1
scsi_mod              151980  7 
megaraid_mbox,sr_mod,sd_mod,megaraid,sg,aic7xxx,scsi_transport_spi
ho

So if I understand well, the module actively used with the LSI card is megaraid, the legacy one ! but the mbox and mm are loaded and seems to be necessary for the legacy driver ?

Actually, it shouldn't be. megaraid_mbox depends on megaraid_mm as your lsmod shows, which is correct. However, nothing's depending on legacy megaraid ... I'm not sure why it's showing as loaded and in use.

James

#4 lore raw
Quoted 6 lines · James Bottomley
Quoted 1 line

So if I understand well, the module actively used with the LSI card is megaraid, the legacy one ! but the mbox and mm are loaded and seems to be necessary for the legacy driver ?

Actually, it shouldn't be. megaraid_mbox depends on megaraid_mm as your lsmod shows, which is correct. However, nothing's depending on legacy megaraid ... I'm not sure why it's showing as loaded and in use.

but it is ! moreover I have a /proc/megaraid/hba1/ directory structure fully filled with my RAID card, drives, and RAID volumes informations, and I don't hav any entry in sysfs directory tree (witch is the right place for megaraid NG module)

I'd like to understand _why_ this module supposed to be independant from the "new generation" megaraid module needs megaraid NG to be compiled to work correctly ?

I looked over the sources but I didn't found any link between the legacy driver and the newgen one... quite strange !

Regards,

Signature · 6 lines
Rico

-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html