RE: megaraid 1.14e still broken
Title: RE: megaraid 1.14e still broken I've noticed that there is a module that appears to conflict with the megaraid driver. (I know this seems strange). I was having trouble getting the megaraid driver to work so... I winnowed down my kernel to an absolute bare minimum, added the megaraid driver, rebooted. It worked. So, I then basically did a binary search of the kernel features I'd disabled. This is very time consuming, I know. I rebuilt the kernel several times, adding a few features each time. I never figured out exactly which module was conflicting, if any, (because after rebuilding the kernel 10 times, it gets really, really old). But I believe it was the USB filesystem module, which I never reenabled, because I don't expect to ever use it. adam -Original Message- From: Heitzso [mailto:[EMAIL PROTECTED]] Sent: Thursday, January 25, 2001 9:30 AM To: 'Venkatesh Ramamurthy' Cc: '[EMAIL PROTECTED]' Subject: megaraid 1.14e still broken Venkatesh, megaraid version 1.14e breaks I rebooted to 2.4.0 and it's older megaraid v107 works fine the raid controller was oem'ed Dell-AMI so there's not an obvious upgrade I can burn into it from AMI page because the product isn't listed there when the box boots and before lilo takes over the message is: "PowerEdge Expandable RAID Controller BIOS 1.25" with an option to go into a configuration utility program the box is a Dell PowerEdge server 2300/450, 2 CPU, 1G RAM Venkatesh, I appreciate your adding debugging info to the driver to capture this, I didn't write the full register dump but did capture the first few debugging lines. megaraid: v1.14e (Release Date: Jan 23, 2001, 17:55) unable to handle kernel NULL pointer dereference at virtual addrss 02cc printing eip: c01e10bc *pde= Ooops: (followed by full register dump that I didn't copy) Let me know where to go next. Heitzso [EMAIL PROTECTED] -Original Message- From: Venkatesh Ramamurthy [mailto:[EMAIL PROTECTED]] Sent: Wednesday, January 24, 2001 2:12 PM To: 'Heitzso' Subject: RE: fyi megaraid problems Try this 1.14e version of the driver and i would be glad if you could let me know the result. Thanks Venkatesh <> > -Original Message- > From: Heitzso [SMTP:[EMAIL PROTECTED]] > Sent: Wednesday, January 24, 2001 1:09 PM > To: 'Venkatesh Ramamurthy' > Subject: RE: fyi megaraid problems > > > kernel, 2.4.1 pre 10, shipping with older > megaraid module, but one that works on our > box!> > > kernel 2.2.13 ships with v1.04, aug '99, WORKS > kernel 2.2.16 didn't ftp down kernel and check > kernel 2.2.18 ships with v1.11, BROKEN > kernel 2.4.1pre10 ships with v1.07b, WORKS > > > > -Original Message- > From: Venkatesh Ramamurthy [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, January 24, 2001 12:07 PM > To: 'Heitzso' > Subject: RE: fyi megaraid problems > > > Can i have the driver version number so that i can see whether we have > already fixed that problem? > Also you can send me the dmesg output from working system ( 2.2.13, > 2.4.1pre10). This could gave me some additional data points. > Thanks > Venkatesh > > > -Original Message- > > From: Heitzso [SMTP:[EMAIL PROTECTED]] > > Sent: Wednesday, January 24, 2001 12:07 PM > > To: 'Venkatesh Ramamurthy' > > Subject: RE: fyi megaraid problems > > > > can't ... > > > > because the hard drive is never accessed > > so the boot messages are never written out > > > > message was an oops, quick recap > > 2.2.13 works (RH6.1 env) > > 2.2.16 breaks (RH7 env) > > 2.2.18 breaks (RH7 env) > > 2.4.1pre10 works (RH7 env) > > > > I don't know if the bug's in megaraid or > > in the RH7 compiler environment, hence my > > stressing that component > > > > Heitzso > > > > -Original Message- > > From: Venkatesh Ramamurthy [mailto:[EMAIL PROTECTED]] > > Sent: Wednesday, January 24, 2001 11:59 AM > > To: '[EMAIL PROTECTED]' > > Subject: RE: fyi megaraid problems > > > > > > Hi, > > Can you send me the 'dmesg' output of the failing combination. I > > would look into the problem ASAP once i get it. > > Thanks > > Venkatesh > > > > > -Original Message- > > > From: Heitzso [mailto:[EMAIL PROTECTED]] > > > Sent: Wednesday, January 24, 2001 11:51 AM > > > To: '[EMAIL PROTECTED]' > > > Subject: fyi megaraid problems > > > > > > > > > don't know if this has been covered/studied > > > > > > datapoints I've run across re the megaraid > > > (scsi raid driver, american megatrends) > > > > > > box: Dell PowerEdge 2300, 2 cpus, 1G RAM > > > > > > hard drive setup as single drive via raid > > > controller > > > > > > RH6.1, compiled 2.2.13, megaraid works! > > > > > > RH7.0 install/upgrade breaks on megaraid > > > then, after forcing RH7.0 upgrade by hand > > > (completely snuffed up with all updates as of jan 23 am ...) > > > RH7.0 kernel (out of the rpm box 686 smp) breaks on megaraid > > > RH7.0 2.2.16 kernel source
RE: megaraid 1.14e still broken
Title: RE: megaraid 1.14e still broken I've noticed that there is a module that appears to conflict with the megaraid driver. (I know this seems strange). I was having trouble getting the megaraid driver to work so... I winnowed down my kernel to an absolute bare minimum, added the megaraid driver, rebooted. It worked. So, I then basically did a binary search of the kernel features I'd disabled. This is very time consuming, I know. I rebuilt the kernel several times, adding a few features each time. I never figured out exactly which module was conflicting, if any, (because after rebuilding the kernel 10 times, it gets really, really old). But I believe it was the USB filesystem module, which I never reenabled, because I don't expect to ever use it. adam -Original Message- From: Heitzso [mailto:[EMAIL PROTECTED]] Sent: Thursday, January 25, 2001 9:30 AM To: 'Venkatesh Ramamurthy' Cc: '[EMAIL PROTECTED]' Subject: megaraid 1.14e still broken Venkatesh, megaraid version 1.14e breaks I rebooted to 2.4.0 and it's older megaraid v107 works fine the raid controller was oem'ed Dell-AMI so there's not an obvious upgrade I can burn into it from AMI page because the product isn't listed there when the box boots and before lilo takes over the message is: PowerEdge Expandable RAID Controller BIOS 1.25 with an option to go into a configuration utility program the box is a Dell PowerEdge server 2300/450, 2 CPU, 1G RAM Venkatesh, I appreciate your adding debugging info to the driver to capture this, I didn't write the full register dump but did capture the first few debugging lines. megaraid: v1.14e (Release Date: Jan 23, 2001, 17:55) unable to handle kernel NULL pointer dereference at virtual addrss 02cc printing eip: c01e10bc *pde= Ooops: (followed by full register dump that I didn't copy) Let me know where to go next. Heitzso [EMAIL PROTECTED] -Original Message- From: Venkatesh Ramamurthy [mailto:[EMAIL PROTECTED]] Sent: Wednesday, January 24, 2001 2:12 PM To: 'Heitzso' Subject: RE: fyi megaraid problems Try this 1.14e version of the driver and i would be glad if you could let me know the result. Thanks Venkatesh m114e.tar.gz -Original Message- From: Heitzso [SMTP:[EMAIL PROTECTED]] Sent: Wednesday, January 24, 2001 1:09 PM To: 'Venkatesh Ramamurthy' Subject: RE: fyi megaraid problems flagging strangeness that latest greatest kernel, 2.4.1 pre 10, shipping with older megaraid module, but one that works on our box! kernel 2.2.13 ships with v1.04, aug '99, WORKS kernel 2.2.16 didn't ftp down kernel and check kernel 2.2.18 ships with v1.11, BROKEN kernel 2.4.1pre10 ships with v1.07b, WORKS -Original Message- From: Venkatesh Ramamurthy [mailto:[EMAIL PROTECTED]] Sent: Wednesday, January 24, 2001 12:07 PM To: 'Heitzso' Subject: RE: fyi megaraid problems Can i have the driver version number so that i can see whether we have already fixed that problem? Also you can send me the dmesg output from working system ( 2.2.13, 2.4.1pre10). This could gave me some additional data points. Thanks Venkatesh -Original Message- From: Heitzso [SMTP:[EMAIL PROTECTED]] Sent: Wednesday, January 24, 2001 12:07 PM To: 'Venkatesh Ramamurthy' Subject: RE: fyi megaraid problems can't ... because the hard drive is never accessed so the boot messages are never written out message was an oops, quick recap 2.2.13 works (RH6.1 env) 2.2.16 breaks (RH7 env) 2.2.18 breaks (RH7 env) 2.4.1pre10 works (RH7 env) I don't know if the bug's in megaraid or in the RH7 compiler environment, hence my stressing that component Heitzso -Original Message- From: Venkatesh Ramamurthy [mailto:[EMAIL PROTECTED]] Sent: Wednesday, January 24, 2001 11:59 AM To: '[EMAIL PROTECTED]' Subject: RE: fyi megaraid problems Hi, Can you send me the 'dmesg' output of the failing combination. I would look into the problem ASAP once i get it. Thanks Venkatesh -Original Message- From: Heitzso [mailto:[EMAIL PROTECTED]] Sent: Wednesday, January 24, 2001 11:51 AM To: '[EMAIL PROTECTED]' Subject: fyi megaraid problems don't know if this has been covered/studied datapoints I've run across re the megaraid (scsi raid driver, american megatrends) box: Dell PowerEdge 2300, 2 cpus, 1G RAM hard drive setup as single drive via raid controller RH6.1, compiled 2.2.13, megaraid works! RH7.0 install/upgrade breaks on megaraid then, after forcing RH7.0 upgrade by hand (completely snuffed up with all updates as of jan 23 am ...) RH7.0 kernel (out of the rpm box 686 smp) breaks on megaraid RH7.0 2.2.16 kernel source from rpm compiled using 2.2.13 .config file and make oldconfig generates kernel that breaks on megaraid (used RH provided scripts to compile with kgcc)
RE: fyi megaraid problems
Title: RE: fyi megaraid problems I've compiled the 2.2.18 and 2.4.0 kernels with the latest megaraid driver (1.14b) and they work well. You should also upgrade your firmware to L148 (bios 3.11). I think the firmware revision depends on which model card you have, I have the 1600 Elite. This is on a Penguin Relion 120, 2 CPUs, PIII, 1G RAM. Two 35G drives configured as one logical drive. I will say that I did float around for a while and found quite a few different versions of the driver (1.07b,1.13s,1b08b,1.13s0,1.14b, I have them all!) before Venkatesh Ramamurthy at AMI helped me figure this all out. (thanks Venkatesh!) Venkatesh posted the 1.14b driver to this list a week or two ago, and you can get the firmware upgrade from ami.com. -Original Message- From: Heitzso [mailto:[EMAIL PROTECTED]] Sent: Wednesday, January 24, 2001 11:51 AM To: '[EMAIL PROTECTED]' Subject: fyi megaraid problems don't know if this has been covered/studied datapoints I've run across re the megaraid (scsi raid driver, american megatrends) box: Dell PowerEdge 2300, 2 cpus, 1G RAM hard drive setup as single drive via raid controller RH6.1, compiled 2.2.13, megaraid works! RH7.0 install/upgrade breaks on megaraid then, after forcing RH7.0 upgrade by hand (completely snuffed up with all updates as of jan 23 am ...) RH7.0 kernel (out of the rpm box 686 smp) breaks on megaraid RH7.0 2.2.16 kernel source from rpm compiled using 2.2.13 .config file and make oldconfig generates kernel that breaks on megaraid (used RH provided scripts to compile with kgcc) 2.2.18 kernel (kernel.org) compiled with gcc on RH7.0 breaks on megaraid during boot BUT! 2.4.1pre10 (kernel.org), compiled with gcc on RH7.0 the megaraid driver works again! I was surprised that even 2.2.18 breaks then 2.4.1pre10 works, given RH's alliance with Dell. I compiled a 2.4.0 and set it up in lilo.conf but haven't tried booting to it. If it's useful to anyone, now that I have a good booting kernel I could recompile the old 2.2.13 setup and see whether the problem is due to a bad compiler env in RH7.0 or due to a bad megaraid module (i.e. if kernel that works fine now compiled under 6.1 breaks when recompiled under 7.0 then bug is in the RH7.0 compiler env; else bug is in megaraid shipped with 2.2.16, 2.2.18) Let me know if someone needs a datapoint. Heitzso [EMAIL PROTECTED] - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
RE: fyi megaraid problems
Title: RE: fyi megaraid problems I've compiled the 2.2.18 and 2.4.0 kernels with the latest megaraid driver (1.14b) and they work well. You should also upgrade your firmware to L148 (bios 3.11). I think the firmware revision depends on which model card you have, I have the 1600 Elite. This is on a Penguin Relion 120, 2 CPUs, PIII, 1G RAM. Two 35G drives configured as one logical drive. I will say that I did float around for a while and found quite a few different versions of the driver (1.07b,1.13s,1b08b,1.13s0,1.14b, I have them all!) before Venkatesh Ramamurthy at AMI helped me figure this all out. (thanks Venkatesh!) Venkatesh posted the 1.14b driver to this list a week or two ago, and you can get the firmware upgrade from ami.com. -Original Message- From: Heitzso [mailto:[EMAIL PROTECTED]] Sent: Wednesday, January 24, 2001 11:51 AM To: '[EMAIL PROTECTED]' Subject: fyi megaraid problems don't know if this has been covered/studied datapoints I've run across re the megaraid (scsi raid driver, american megatrends) box: Dell PowerEdge 2300, 2 cpus, 1G RAM hard drive setup as single drive via raid controller RH6.1, compiled 2.2.13, megaraid works! RH7.0 install/upgrade breaks on megaraid then, after forcing RH7.0 upgrade by hand (completely snuffed up with all updates as of jan 23 am ...) RH7.0 kernel (out of the rpm box 686 smp) breaks on megaraid RH7.0 2.2.16 kernel source from rpm compiled using 2.2.13 .config file and make oldconfig generates kernel that breaks on megaraid (used RH provided scripts to compile with kgcc) 2.2.18 kernel (kernel.org) compiled with gcc on RH7.0 breaks on megaraid during boot BUT! 2.4.1pre10 (kernel.org), compiled with gcc on RH7.0 the megaraid driver works again! I was surprised that even 2.2.18 breaks then 2.4.1pre10 works, given RH's alliance with Dell. I compiled a 2.4.0 and set it up in lilo.conf but haven't tried booting to it. If it's useful to anyone, now that I have a good booting kernel I could recompile the old 2.2.13 setup and see whether the problem is due to a bad compiler env in RH7.0 or due to a bad megaraid module (i.e. if kernel that works fine now compiled under 6.1 breaks when recompiled under 7.0 then bug is in the RH7.0 compiler env; else bug is in megaraid shipped with 2.2.16, 2.2.18) Let me know if someone needs a datapoint. Heitzso [EMAIL PROTECTED] - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
oracle 8.1.7 on 2.4.0?
Title: oracle 8.1.7 on 2.4.0? what is the status of oracle 8.1.7 on 2.4? Did the O_SYNC stuff ever get sorted out? Should I stick with 2.2.18?
oracle 8.1.7 on 2.4.0?
Title: oracle 8.1.7 on 2.4.0? what is the status of oracle 8.1.7 on 2.4? Did the O_SYNC stuff ever get sorted out? Should I stick with 2.2.18?
megaraid driver downrev in 2.4
Title: megaraid driver downrev in 2.4 anyone have a pointer to a working 1.09 or newer megaraid driver? 1.07b looks to have serious issues with 2.4.
megaraid driver downrev in 2.4
Title: megaraid driver downrev in 2.4 anyone have a pointer to a working 1.09 or newer megaraid driver? 1.07b looks to have serious issues with 2.4.
