Re: problem with megaraid2 driver

Re: problem with megaraid2 driver

[Xose Vazquez Perez]

Gabor Burjan wrote:

> I've an LSI Logic MegaRAID SCSI 320-1 card.  The exact name from the
> /proc/pci is `RAID bus controller: LSI Logic / Symbios Logic PowerEdge
> Expandable RAID Controller 4 (rev 1)' the PCI ID of this device is
> 0x1960.  I ran into a problem with the new megaraid2 driver:

>  Vendor: MegaRAID  Model: LD0 RAID5 70006R  Rev: 1L19
                                                   ^^^^

latest release 1L26 fixed a lot of bugs.
For SCSI and RAID storage boards is *very important* to run with latest
firmware.

Re: problem with megaraid2 driver

[Gabor Burjan]

On Fri, Nov 28, 2003 at 04:27:40PM +0100, Xose Vazquez Perez wrote:

> latest release 1L26 fixed a lot of bugs.
> For SCSI and RAID storage boards is *very important* to run with latest
> firmware.

Thanks for the quick answer, I'll flash the new firmware ASAP.

Is that possible that only the new driver triggers the problem which is
"built-in" in the firmware, while using the old driver everything seems
to be OK?

Gabor

Re: problem with megaraid2 driver

[Xose Vazquez Perez]

Gabor Burjan wrote:

> Is that possible that only the new driver triggers the problem which is
> "built-in" in the firmware, while using the old driver everything seems
> to be OK?

1.18k and 2.00.9 are very different drivers.

It looks like the firmware of the board is unable to
complete some commands of the pending list.

megaraid: aborting-4027815 cmd=2a <c=0 t=0 l=0>
megarid: Waiting for 11 commands to flush: iter:0
megarid: Waiting for 11 commands to flush: iter:1000
megarid: Waiting for 11 commands to flush: iter:2000
megaraid: aborted cmd 3d75a7[76] complete.
megarid: Waiting for 8 commands to flush: iter:3000
[... 4000, 5000, 6000, ... 59000]
megarid: Waiting for 8 commands to flush: iter:60000
megaraid: critical hardware error!

If those command were completed you would see the message:
"megaraid: abort sequence successfully complete".

So, try latest firmware.

-- 
There are 10 kinds of people.
Those that know to count in binary and those that no.

Re: problem with megaraid2 driver

[Gabor Burjan]

On Sat, Nov 29, 2003 at 04:38:57PM +0100, Xose Vazquez Perez wrote:

> It looks like the firmware of the board is unable to
> complete some commands of the pending list. [...]
> 
> So, try latest firmware.

Thank you, that solved the problem.

for the archive, this combination is running now:

adapter: LSI MegaRAID SCSI 320-1
megaraid2 driver v2.00.9
firmware 1L26:G112.

Gabor

problem with megaraid2 driver

[Gabor Burjan]

Dear Developers,

I've an LSI Logic MegaRAID SCSI 320-1 card.  The exact name from the
/proc/pci is `RAID bus controller: LSI Logic / Symbios Logic PowerEdge
Expandable RAID Controller 4 (rev 1)' the PCI ID of this device is
0x1960.  I ran into a problem with the new megaraid2 driver:

the relevant information catched on serial console:

Linux version 2.4.23-rc4 (root@mailserver) (gcc version 2.95.4 20011002 (Debian prerelease)) #2 Tue Nov 25 11:42:37 CET 2003
BIOS-provided physical RAM map:
 BIOS-e820: 0000000000000000 - 000000000009fc00 (usable)
 BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved)
 BIOS-e820: 00000000000e8000 - 0000000000100000 (reserved)
 BIOS-e820: 0000000000100000 - 000000001ff30000 (usable)
 BIOS-e820: 000000001ff30000 - 000000001ff40000 (ACPI data)
 BIOS-e820: 000000001ff40000 - 000000001fff0000 (ACPI NVS)
 BIOS-e820: 000000001fff0000 - 0000000020000000 (reserved)
 BIOS-e820: 00000000ffb80000 - 0000000100000000 (reserved)
511MB LOWMEM available.
On node 0 totalpages: 130864
zone(0): 4096 pages.
zone(1): 126768 pages.
zone(2): 0 pages.
Kernel command line: root=/dev/sda3 console=ttyS0 console=tty0
Initializing CPU#0
[...]
SCSI subsystem driver Revision: 1.00
Loading Adaptec I2O RAID: Version 2.4 Build 5
Detecting Adaptec I2O RAID controllers...
megaraid: v2.00.9 (Release Date: Thu Sep  4 17:49:42 EDT 2003)
PCI: Found IRQ 10 for device 02:0c.0
megaraid: found 0x1000:0x1960:bus 2:slot 12:func 0
scsi0:Found MegaRAID controller at 0xe0807000, IRQ:10
megaraid: [1L19:1.04] detected 1 logical drives.
megaraid: supports extended CDBs.
megaraid: channel[0] is raid.
scsi0 : LSI Logic MegaRAID 1L19 254 commands 16 targs 4 chans 7 luns
scsi0: scanning scsi channel 0 for logical drives.
  Vendor: MegaRAID  Model: LD0 RAID5 70006R  Rev: 1L19
  Type:   Direct-Access                      ANSI SCSI revision: 02
scsi0: scanning scsi channel 1 for logical drives.
scsi0: scanning scsi channel 2 for logical drives.
scsi0: scanning scsi channel 4 [P0] for physical devices.
Attached scsi disk sda at scsi0, channel 0, id 0, lun 0
SCSI device sda: 143372288 512-byte hdwr sectors (73407 MB)
 sda: sda1 sda2 sda3 sda4 < sda5 sda6 sda7 >

[... after a few hours of uptime ...]

megaraid: aborting-4027815 cmd=2a <c=0 t=0 l=0>
megarid: Waiting for 11 commands to flush: iter:0
megarid: Waiting for 11 commands to flush: iter:1000
megarid: Waiting for 11 commands to flush: iter:2000
megaraid: aborted cmd 3d75a7[76] complete.
megarid: Waiting for 8 commands to flush: iter:3000
[... 4000, 5000, 6000, ... 59000]
megarid: Waiting for 8 commands to flush: iter:60000
megaraid: critical hardware error!
megaraid: aborting-4027818 cmd=28 <c=0 t=0 l=0>
megarid: Waiting for 8 commands to flush: iter:0
megarid: Waiting for 8 commands to flush: iter:1000
megarid: Waiting for 8 commands to flush: iter:2000
megarid: Waiting for 8 commands to flush: iter:3000
[... 4000, 5000, 6000, ... 59000]
megarid: Waiting for 3 commands to flush: iter:60000
megaraid: critical hardware error!
megaraid: aborting-4027820 cmd=2a <c=0 t=0 l=0>
megarid: Waiting for 3 commands to flush: iter:0
megarid: Waiting for 3 commands to flush: iter:1000
megarid: Waiting for 3 commands to flush: iter:2000
megarid: Waiting for 3 commands to flush: iter:3000
[... 4000, 5000, 6000, ... 59000]
megarid: Waiting for 3 commands to flush: iter:60000
megaraid: critical hardware error!
megaraid: aborting-4027821 cmd=2a <c=0 t=0 l=0>
megarid: Waiting for 3 commands to flush: iter:0
megarid: Waiting for 3 commands to flush: iter:1000
megarid: Waiting for 3 commands to flush: iter:2000
megarid: Waiting for 3 commands to flush: iter:3000
[... 4000, 5000, 6000, ... 59000]
megarid: Waiting for 3 commands to flush: iter:60000
megaraid: critical hardware error!
megaraid: aborting-4027822 cmd=2a <c=0 t=0 l=0>
megarid: Waiting for 3 commands to flush: iter:0
megarid: Waiting for 3 commands to flush: iter:1000
megarid: Waiting for 3 commands to flush: iter:2000
megarid: Waiting for 3 commands to flush: iter:3000
[... 4000, 5000, 6000, ... 59000]
megarid: Waiting for 3 commands to flush: iter:60000
megaraid: critical hardware error!
megaraid: aborting-4027803 cmd=2a <c=0 t=0 l=0>
megarid: Waiting for 3 commands to flush: iter:0
megarid: Waiting for 3 commands to flush: iter:1000
megarid: Waiting for 3 commands to flush: iter:2000
megarid: Waiting for 3 commands to flush: iter:3000
[... 4000, 5000, 6000, ... 59000]
megarid: Waiting for 3 commands to flush: iter:60000
megaraid: critical hardware error!
megaraid: aborting-4027804 cmd=2a <c=0 t=0 l=0>
megarid: Waiting for 3 commands to flush: iter:0
megarid: Waiting for 3 commands to flush: iter:1000
megarid: Waiting for 3 commands to flush: iter:2000
megarid: Waiting for 3 commands to flush: iter:3000
[... 4000, 5000, 6000, ... 57000]
megarid: Waiting for 3 commands to flush: iter:58000
megarid: Waiting for 3 commands to flush: iter:59000

[... no interaction -> pressing reset button]

Is it useful in this form?  Unfortunately this is a production server
and I don't have other machine with this kind of RAID card to test on.

Now we're running the old v1.18k driver without any problem.
However I don't see any 1.x driver in v2.6, so this can't be the
long-term solution.

TIA,

Gábor
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html