RE: Megaraid does not work with 2.4.22

RE: Megaraid does not work with 2.4.22

[Marcelo Tosatti]

On Wed, 24 Sep 2003, Mukker, Atul wrote:

> Marcelo,
> 
> What are your plans to integrate the 1.18k as well as 2.00.9 megaraid
> drivers in the mainstream kernels.

Atul,

It depends on what they change and how extensively they have been tested.

Are they in 2.6 already? 

Re: Megaraid does not work with 2.4.22

[Marcelo Tosatti]

On Wed, 8 Oct 2003, Xose Vazquez Perez wrote:

> Marcelo Tosatti wrote:
> 
> >>Here go some trivial fixes(add menu entry, list all compatibles
> >>boards in help and put tab instead spaces) for megaraid2.
> > 
> > 
> > Those are already in the merged megaraid2
> 
> This is a patch against 2.4.22-bk30, and it's
> necessary to be able to compile megaraid2 and to
> get help text from menuconfig.

Oh indeed I missed it. 

Applied thanks 

Re: Megaraid does not work with 2.4.22

[Erik Andersen]

On Wed Oct 08, 2003 at 03:09:04AM +0200, Xose Vazquez Perez wrote:
> Marcelo Tosatti wrote:
> 
> >>Here go some trivial fixes(add menu entry, list all compatibles
> >>boards in help and put tab instead spaces) for megaraid2.
> > 
> > 
> > Those are already in the merged megaraid2
> 
> This is a patch against 2.4.22-bk30, and it's
> necessary to be able to compile megaraid2 and to
> get help text from menuconfig.

Xose is correct.  His patch should indeed be applied to the
latest bk tree so the megaraid2 driver can actually be compiled
into 2.4.x.  

 -Erik

--
Erik B. Andersen             http://codepoet-consulting.com/
--This message was written using 73% post-consumer electrons--

Re: Megaraid does not work with 2.4.22

[Xose Vazquez Perez]

Marcelo Tosatti wrote:

>>Here go some trivial fixes(add menu entry, list all compatibles
>>boards in help and put tab instead spaces) for megaraid2.
> 
> 
> Those are already in the merged megaraid2

This is a patch against 2.4.22-bk30, and it's
necessary to be able to compile megaraid2 and to
get help text from menuconfig.

-thanks-

Re: Megaraid does not work with 2.4.22

[Marcelo Tosatti]

On Tue, 7 Oct 2003, Xose Vazquez Perez wrote:

> Marcelo Tosatti wrote:
> 
> > Fine. I agree on adding in to mainline 2.4.x.
> 
> Here go some trivial fixes(add menu entry, list all compatibles
> boards in help and put tab instead spaces) for megaraid2.

Those are already in the merged megaraid2

thanks

Re: Megaraid does not work with 2.4.22

[Xose Vazquez Perez]

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

Marcelo Tosatti wrote:

> Fine. I agree on adding in to mainline 2.4.x.

Here go some trivial fixes(add menu entry, list all compatibles
boards in help and put tab instead spaces) for megaraid2.

-thanks-
-- 
If it wasn't for the presence of Lara Croft and Xena Warrior Princess,
techies around the world would have posters of Torvalds on their walls.


[-- Attachment #2: megaraid.patch --]
[-- Type: text/plain, Size: 2979 bytes --]

diff -Nuar old/Documentation/Configure.help new/Documentation/Configure.help
--- old/Documentation/Configure.help	Tue Oct  7 19:11:27 2003
+++ new/Documentation/Configure.help	Tue Oct  7 19:30:00 2003
@@ -9051,9 +9051,11 @@
 
 AMI MegaRAID support (old driver)
 CONFIG_SCSI_MEGARAID
-  This driver supports the AMI MegaRAID 418, 428, 438, 466, 762, 490
-  and 467 SCSI host adapters. This is the old and very heavily tested
-  driver but lacks features like clustering.
+  This driver supports the AMI MegaRAID 418, 428, 438, 466, 762, 490,
+  467, 471 and 493 SCSI host adapters. 
+
+  This is the old and very heavily tested driver but lacks features
+  like clustering.
 
   If you want to compile this driver as a module ( = code which can be
   inserted in and removed from the running kernel whenever you want),
@@ -9062,14 +9064,15 @@
 
 AMI MegaRAID support (new driver)
 CONFIG_SCSI_MEGARAID2
-This driver supports the AMI MegaRAID 418, 428, 438, 466, 762, 490
-and 467 SCSI host adapters. This is the newer less tested but more
-featureful driver.
-
-If you want to compile this driver as a module ( = code which can be
-inserted in and removed from the running kernel whenever you want),
-say M here and read <file:Documentation/modules.txt>.  The module
-will be called megaraid2.o.
+  This driver supports the AMI MegaRAID 418, 428, 438, 466, 762, 490,
+  467, 471, 493 and new Ultra320(518, 520, 531, 532) SCSI host adapters.
+
+  This is the newer less tested but more featureful driver.
+
+  If you want to compile this driver as a module ( = code which can be
+  inserted in and removed from the running kernel whenever you want),
+  say M here and read <file:Documentation/modules.txt>.  The module
+  will be called megaraid2.o.
 
 Intel/ICP (former GDT SCSI Disk Array) RAID Controller support
 CONFIG_SCSI_GDTH
diff -Nuar old/drivers/scsi/Config.in new/drivers/scsi/Config.in
--- old/drivers/scsi/Config.in	Tue Oct  7 19:10:54 2003
+++ new/drivers/scsi/Config.in	Tue Oct  7 19:21:28 2003
@@ -67,6 +67,7 @@
 dep_tristate 'Always IN2000 SCSI support' CONFIG_SCSI_IN2000 $CONFIG_SCSI
 dep_tristate 'AM53/79C974 PCI SCSI support' CONFIG_SCSI_AM53C974 $CONFIG_SCSI $CONFIG_PCI
 dep_tristate 'AMI MegaRAID support' CONFIG_SCSI_MEGARAID $CONFIG_SCSI
+dep_tristate 'AMI MegaRAID2 support' CONFIG_SCSI_MEGARAID2 $CONFIG_SCSI
 
 dep_tristate 'BusLogic SCSI support' CONFIG_SCSI_BUSLOGIC $CONFIG_SCSI
 if [ "$CONFIG_SCSI_BUSLOGIC" != "n" ]; then
diff -Nuar old/drivers/scsi/Makefile new/drivers/scsi/Makefile
--- old/drivers/scsi/Makefile	Tue Oct  7 19:10:49 2003
+++ new/drivers/scsi/Makefile	Tue Oct  7 19:21:41 2003
@@ -110,7 +110,7 @@
 obj-$(CONFIG_SCSI_DC390T)	+= tmscsim.o
 obj-$(CONFIG_SCSI_AM53C974)	+= AM53C974.o
 obj-$(CONFIG_SCSI_MEGARAID)	+= megaraid.o
-obj-$(CONFIG_SCSI_MEGARAID2)   += megaraid2.o
+obj-$(CONFIG_SCSI_MEGARAID2)	+= megaraid2.o
 obj-$(CONFIG_SCSI_ACARD)	+= atp870u.o
 obj-$(CONFIG_SCSI_SUNESP)	+= esp.o
 obj-$(CONFIG_SCSI_GDTH)		+= gdth.o

RE: Megaraid does not work with 2.4.22

[Tomita, Haruo]

Xose Vazquez Perez [xose@wanadoo.es]　wrote:

> megaraid 2.xx gets correct performance, it's stable and it 
> adds support
> for _present_ hardware, MegaRAID Ultra320 RAID boards(518, 
> 520, 531, 532).

Please remember what is also done for clean up of the source code.
it is very simple!!.
--
Haruo

Re: Megaraid does not work with 2.4.22

[syn uw]

>Fine. I agree on adding in to mainline 2.4.x.

Great, this is really good news for all of us here owning a LSI MegaRAID 
card ! Thank you very much!!

Now will this already go in kernel 2.4.23 ?

Regards

_________________________________________________________________
The new MSN 8: advanced junk mail protection and 2 months FREE* 
http://join.msn.com/?page=features/junkmail

Re: Megaraid does not work with 2.4.22

[Marcelo Tosatti]

On Wed, 1 Oct 2003, Xose Vazquez Perez wrote:

> Marcelo Tosatti wrote:
> 
> > Having two drivers for the same controller is not a good thing from a user
> 
> this doesn't is first time:
> e100/eepro100 aic7xxx/aic7xxx_old  sym53c8xx_2/sym53c8xx+ncr53c8xx ...

Yes its not but still, it sucks.

> > point of view. I just asked Atul privately but will do so again here: Why
> > do we need "megaraid2" ?
> 
> megaraid 1.xx gets *very bad* performance. But like 2.4 is stable serie, it
> shouldn't be deleted.
> 
> megaraid 2.xx gets correct performance, it's stable and it adds support
> for _present_ hardware, MegaRAID Ultra320 RAID boards(518, 520, 531, 532).

Fine. I agree on adding in to mainline 2.4.x. 

Re: Megaraid does not work with 2.4.22

[Xose Vazquez Perez]

Marcelo Tosatti wrote:

> Having two drivers for the same controller is not a good thing from a user

this doesn't is first time:
e100/eepro100 aic7xxx/aic7xxx_old  sym53c8xx_2/sym53c8xx+ncr53c8xx ...

> point of view. I just asked Atul privately but will do so again here: Why
> do we need "megaraid2" ?

megaraid 1.xx gets *very bad* performance. But like 2.4 is stable serie, it
shouldn't be deleted.

megaraid 2.xx gets correct performance, it's stable and it adds support
for _present_ hardware, MegaRAID Ultra320 RAID boards(518, 520, 531, 532).


-thanks-
-- 
:x

RE: Megaraid does not work with 2.4.22

[Marcelo Tosatti]

On Wed, 1 Oct 2003, syn uw wrote:

> >I don't know what is the opinion of other people :-?
> >Maybe linux-scsi members hold other opinion.
> 
> Well I for example would be more than pleased to see megaraid 2.x included 
> in the next stable 2.4.x Linux kernel !! I had a look at the current 
> changelogs of 2.4.23 and still no traces about a megaraid v2 inclusion :(( 
> Hopefully that will happen soon !

Having two drivers for the same controller is not a good thing from a user
point of view. I just asked Atul privately but will do so again here: Why 
do we need "megaraid2" ? 

RE: Megaraid does not work with 2.4.22

[syn uw]

>I don't know what is the opinion of other people :-?
>Maybe linux-scsi members hold other opinion.

Well I for example would be more than pleased to see megaraid 2.x included 
in the next stable 2.4.x Linux kernel !! I had a look at the current 
changelogs of 2.4.23 and still no traces about a megaraid v2 inclusion :(( 
Hopefully that will happen soon !

Regards

_________________________________________________________________
Get McAfee virus scanning and cleaning of incoming attachments.  Get Hotmail 
Extra Storage!   http://join.msn.com/?PAGE=features/es

RE: Megaraid does not work with 2.4.22

[Tomita, Haruo]

Hi Matt,

Matt wrote;

Matt> Atul should be submitting changelogs and patches to James 
Matt> Bottomley and linux-scsi for inclusion in both 2.4.x and 2.6.x,
Matt> unless Marcelo asks to receive them directly.

I think that it is better to also update the driver of 1.18x 
in the kernel tree of 2.4.x to the latest version(1.18k).
-- 
Haruo

RE: Megaraid does not work with 2.4.22

[Matt_Domsch]

> What are your plans to integrate the 1.18k as well as 2.00.9 megaraid
> drivers in the mainstream kernels.

I would be glad to see megaraid 1.18k and megaraid2 2.00.9 be included
in 2.4.x-stock.  These seem stable in our testing thus far.  Alan has
had megaraid2 2.00.(something - 5?) in his tree for a while now.

Alan didn't want to lightswitch the 1.18X series driver out during a
stable kernel series, preferring to have both a megaraid and a megaraid2
driver, and let people decide.


> Are they in 2.6 already? 

2.6.x has megaraid 2.00.3 in it right now - it needs to be brought up to
2.00.9.  There's no reason to have both megaraid and megaraid2 in 2.6.x,
only one 'megaraid' which is 2.00.x.


Atul should be submitting changelogs and patches to James Bottomley and
linux-scsi for inclusion in both 2.4.x and 2.6.x, unless Marcelo asks to
receive them directly.

Thanks,
Matt

-- 
Matt Domsch
Sr. Software Engineer, Lead Engineer
Dell Linux Solutions www.dell.com/linux
Linux on Dell mailing lists @ http://lists.us.dell.com

RE: Megaraid does not work with 2.4.22

[Xose Vazquez Perez]

Marcelo Tosatti wrote:

> On Wed, 24 Sep 2003, Mukker, Atul wrote:
> 
>> Marcelo,
>> 
>> What are your plans to integrate the 1.18k as well as 2.00.9 megaraid
>> drivers in the mainstream kernels.
> 
> Atul,
> 
> It depends on what they change and how extensively they have been tested.

kernel driver 1.xx is frozen since Dec-2002. Latest 1.xx _only_ fixes bugs
and adds support for ioctls on amd64. Not too much exciting.

2.xx driver adds support for latest hardware, MegaRAID Ultra320 RAID boards
(518, 520, 531, 532.). It was developed since Nov-2002 and it is included
in Red Hat Enterpise Linux 2.1 since May-2003.

Matt Domsch of Dell now is distribuyed both to their customers.
So they should be ready for official kernel inclusion.

I don't know what is the opinion of other people :-?
Maybe linux-scsi members hold other opinion.

> Are they in 2.6 already? 

no.

-thanks-

-- 
SCO before, Smoking Crack Often now.

Megaraid does not work with 2.4.22

[Krzysztof Olędzki]

Hello,

It seems that Megaraid does not work with 2.4.22 at least on
my machine. I don't know when it stopped working because I have never used
this SCSI adapter before. During kernel boot magararid's driver generates
nasty opps. This is the output from oops parsed by ksymoops:

ksymoops 2.4.9 on i686 2.4.22.  Options used
     -V (default)
     -k /proc/ksyms (default)
     -l /proc/modules (default)
     -o /lib/modules/2.4.22 (specified)
     -m /boot/System.map-2.4.22 (specified)

Error (regular_file): read_ksyms stat /proc/ksyms failed
No modules in ksyms, skipping objects
No ksyms, skipping lsmod
cpu: 0, clocks: 1333384, slice: 666692
PI_DEBUG for details.
3c59x: Donald Becker and others. www.scyld.com/network/vortex.html
Unable to handle kernel NULL pointer dereference at virtual address 0000000f
c0262330
*pde = 00000000
Oops: 0000
CPU:    0
EIP:    0010:[<c0262330>]    Not tainted
Using defaults from ksymoops -t elf32-i386 -a i386
EFLAGS: 00010286
eax: cfeb0078   ebx: 00000000   ecx: 00000005   edx: 00000018
esi: 00000000   edi: 00000000   ebp: cfeb0078   esp: c12ddd44
ds: 0018   es: 0018   ss: 0018
Process swapper (pid: 1, stackpage=c12dd000)
Stack: c12dc000 cfee9860 04000001 c026207b cfeb0078 00000000 00000001 00000000
       c12dddcc c12ddd68 c12ddd68 00000000 c0426b60 fffffffe 00000046 c011bf02
       c011be16 00000000 00000001 00000046 c0426b60 c0426900 00000000 00000001
Call Trace:    [<c026207b>] [<c011bf02>] [<c011be16>] [<c0108b8e>] [<c010b2ad>]
  [<c01089d5>] [<c0108b54>] [<c010b1f8>] [<c0108fa1>] [<c0262030>] [<c0108c35>]
  [<c02630c9>] [<c0262030>] [<c01172ff>] [<c01173f5>] [<c0105000>] [<c0263669>]
  [<c02303e6>] [<c023a4c3>] [<c015cac2>] [<c0105000>] [<c0230235>] [<c0105000>]
  [<c015c927>] [<c015cd33>] [<c0105000>] [<c0105053>] [<c0105000>] [<c010579e>]
  [<c0105040>]
Code: 80 7e 0f 00 74 1e c7 04 24 58 8d 06 00 43 e8 cd b8 0d 00 81


>>EIP; c0262330 <mega_busyWaitMbox+20/50>   <=====

Trace; c026207b <megaraid_isr+4b/2e0>
Trace; c011bf02 <bh_action+22/40>
Trace; c011be16 <tasklet_hi_action+46/70>
Trace; c0108b8e <do_IRQ+9e/a0>
Trace; c010b2ad <call_apic_timer_interrupt+5/10>
Trace; c01089d5 <handle_IRQ_event+45/70>
Trace; c0108b54 <do_IRQ+64/a0>
Trace; c010b1f8 <call_do_IRQ+5/d>
Trace; c0108fa1 <setup_irq+71/a0>
Trace; c0262030 <megaraid_isr+0/2e0>
Trace; c0108c35 <request_irq+a5/e0>
Trace; c02630c9 <mega_findCard+3b9/7d0>
Trace; c0262030 <megaraid_isr+0/2e0>
Trace; c01172ff <__call_console_drivers+5f/70>
Trace; c01173f5 <call_console_drivers+65/120>
Trace; c0105000 <_stext+0/0>
Trace; c0263669 <megaraid_detect+189/2b0>
Trace; c02303e6 <scsi_unregister_host+1a6/480>
Trace; c023a4c3 <ahc_linux_detect+23/60>
Trace; c015cac2 <proc_create+b2/100>
Trace; c0105000 <_stext+0/0>
Trace; c0230235 <scsi_register_host+2e5/2f0>
Trace; c0105000 <_stext+0/0>
Trace; c015c927 <proc_register+17/a0>
Trace; c015cd33 <create_proc_entry+83/d0>
Trace; c0105000 <_stext+0/0>
Trace; c0105053 <init+13/130>
Trace; c0105000 <_stext+0/0>
Trace; c010579e <arch_kernel_thread+2e/40>
Trace; c0105040 <init+0/130>

Code;  c0262330 <mega_busyWaitMbox+20/50>
00000000 <_EIP>:
Code;  c0262330 <mega_busyWaitMbox+20/50>   <=====
   0:   80 7e 0f 00               cmpb   $0x0,0xf(%esi)   <=====
Code;  c0262334 <mega_busyWaitMbox+24/50>
   4:   74 1e                     je     24 <_EIP+0x24>
Code;  c0262336 <mega_busyWaitMbox+26/50>
   6:   c7 04 24 58 8d 06 00      movl   $0x68d58,(%esp,1)
Code;  c026233d <mega_busyWaitMbox+2d/50>
   d:   43                        inc    %ebx
Code;  c026233e <mega_busyWaitMbox+2e/50>
   e:   e8 cd b8 0d 00            call   db8e0 <_EIP+0xdb8e0>
Code;  c0262343 <mega_busyWaitMbox+33/50>
  13:   81 00 00 00 00 00         addl   $0x0,(%eax)

 <0>Kernel panic: Aiee, killing interrupt handler!

1 error issued.  Results may not be reliable.


Best Ragards,

				Krzysztof Olędzki