public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
* 3ware driver broken with 2.4.22/23 ?
@ 2003-12-21 11:21 Lukas Hejtmanek
  2003-12-21 11:29 ` Martin Loschwitz
                   ` (2 more replies)
  0 siblings, 3 replies; 7+ messages in thread
From: Lukas Hejtmanek @ 2003-12-21 11:21 UTC (permalink / raw)
  To: linux-kernel; +Cc: linux

Hello,

I have 3ware Escalade 8500-8 card with 8 SATA WD 250GB drives. I set up HW RAID5
configuration over all drives.
I'm using kernel 2.4.23 vanilla with XFS patch. RAID5 partition is formated to
XFS.
System is single hyper threaded P4 Xeon 2.8GHz with 1GB of RAM. There is Intel
1000/PRO ethernet card. Motherboard is MSI E7501 Master-LS.

If I do:
iozone -Ra -g 20G -e -n 10485760 
on the XFS partition then it freezes after certain time (but always the same
amount if I run it again few times).

Server responds only to ping and sysrq. No process can be run and already
running process top freezes as well. After about 8 hours it is still freezed.
If I connect monitor to the server when it freezes then monitor indicates - no
signal.

I use configuration with SMP without HIGHMEM. However it happens without SMP as
well. (Driver: 1.02.00.036)

With kernel 2.6.0 it seems to be ok. (Driver: 1.02.00.037)

Here is lspci:
00:00.0 Host bridge: Intel Corp. E7501 Memory Controller Hub (rev 01)
00:00.1 Class ff00: Intel Corp. E7000 Series Host RASUM Controller (rev 01)
00:02.0 PCI bridge: Intel Corp. E7000 Series Hub Interface B PCI-to-PCI Bridge (rev 01)
00:02.1 Class ff00: Intel Corp. E7000 Series Hub Interface B RASUM Controller (rev 01)
00:1d.0 USB Controller: Intel Corp. 82801CA/CAM USB (Hub #1) (rev 02)
00:1d.1 USB Controller: Intel Corp. 82801CA/CAM USB (Hub #2) (rev 02)
00:1d.2 USB Controller: Intel Corp. 82801CA/CAM USB (Hub #3) (rev 02)
00:1e.0 PCI bridge: Intel Corp. 82801BA/CA/DB/EB PCI Bridge (rev 42)
00:1f.0 ISA bridge: Intel Corp. 82801CA LPC Interface Controller (rev 02)
00:1f.1 IDE interface: Intel Corp. 82801CA Ultra ATA Storage Controller (rev 02)
00:1f.3 SMBus: Intel Corp. 82801CA/CAM SMBus Controller (rev 02)
01:1c.0 PIC: Intel Corp. 82870P2 P64H2 I/OxAPIC (rev 04)
01:1d.0 PCI bridge: Intel Corp. 82870P2 P64H2 Hub PCI Bridge (rev 04)
01:1e.0 PIC: Intel Corp. 82870P2 P64H2 I/OxAPIC (rev 04)
01:1f.0 PCI bridge: Intel Corp. 82870P2 P64H2 Hub PCI Bridge (rev 04)
02:09.0 Ethernet controller: Intel Corp. 82545EM Gigabit Ethernet Controller (Copper) (rev 01)
02:0c.0 RAID bus controller: 3ware Inc 3ware 7000-series ATA-RAID (rev 01)
04:04.0 Ethernet controller: Intel Corp. 82540EM Gigabit Ethernet Controller (rev 02)
04:05.0 VGA compatible controller: ATI Technologies Inc Rage XL (rev 27)

Here is info from 3ware card:
Monitor version:	ME7X 1.01.00.035	
Firmware version:	FE7S 1.05.00.036	
BIOS version:		BE7X 1.08.00.044	
PCB version:		Rev3	
Achip version:		V3.20	
Pchip version:		V1.30	
Model:			8500-8

Can firmware upgrade help? Or there is an issue with something other not related
to 3ware card?

-- 
Lukáš Hejtmánek

^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: 3ware driver broken with 2.4.22/23 ?
  2003-12-21 11:21 3ware driver broken with 2.4.22/23 ? Lukas Hejtmanek
@ 2003-12-21 11:29 ` Martin Loschwitz
  2003-12-21 11:48 ` Andre Tomt
  2003-12-22  1:16 ` Samuel Flory
  2 siblings, 0 replies; 7+ messages in thread
From: Martin Loschwitz @ 2003-12-21 11:29 UTC (permalink / raw)
  To: Lukas Hejtmanek, linux-kernel

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

On Sun, Dec 21, 2003 at 12:21:13PM +0100, Lukas Hejtmanek wrote:
> Hello,
> 
> I have 3ware Escalade 8500-8 card with 8 SATA WD 250GB drives. I set up HW RAID5
> configuration over all drives.
> I'm using kernel 2.4.23 vanilla with XFS patch. RAID5 partition is formated to
> XFS.
> System is single hyper threaded P4 Xeon 2.8GHz with 1GB of RAM. There is Intel
> 1000/PRO ethernet card. Motherboard is MSI E7501 Master-LS.
> 
> If I do:
> iozone -Ra -g 20G -e -n 10485760 
> on the XFS partition then it freezes after certain time (but always the same
> amount if I run it again few times).
> 
> Server responds only to ping and sysrq. No process can be run and already
> running process top freezes as well. After about 8 hours it is still freezed.
> If I connect monitor to the server when it freezes then monitor indicates - no
> signal.
> 
> I use configuration with SMP without HIGHMEM. However it happens without SMP as
> well. (Driver: 1.02.00.036)
> 
> With kernel 2.6.0 it seems to be ok. (Driver: 1.02.00.037)
> 
> Can firmware upgrade help? Or there is an issue with something other not related
> to 3ware card?
> 
Well, it happens from time to time that the card refuses to work with an
actual driver as actual drivers sometimes make use of functions introduced
in firmware upgrades. Upgrading the firmware should be the first thing to
try. Chances are it works well even with 2.4 afterwards.

> -- 
> Luká? Hejtmánek
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/

-- 
  .''`.   Martin Loschwitz           Debian GNU/Linux developer
 : :'  :  madkiss@madkiss.org        madkiss@debian.org
 `. `'`   http://www.madkiss.org/    people.debian.org/~madkiss/
   `-     Use Debian GNU/Linux 3.0!  See http://www.debian.org/

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: 3ware driver broken with 2.4.22/23 ?
  2003-12-21 11:21 3ware driver broken with 2.4.22/23 ? Lukas Hejtmanek
  2003-12-21 11:29 ` Martin Loschwitz
@ 2003-12-21 11:48 ` Andre Tomt
  2003-12-22  1:16 ` Samuel Flory
  2 siblings, 0 replies; 7+ messages in thread
From: Andre Tomt @ 2003-12-21 11:48 UTC (permalink / raw)
  To: Lukas Hejtmanek; +Cc: linux-kernel

On Sun, 2003-12-21 at 12:21, Lukas Hejtmanek wrote:
> Hello,
> 
> I have 3ware Escalade 8500-8 card with 8 SATA WD 250GB drives. I set up HW RAID5
> configuration over all drives.
> I'm using kernel 2.4.23 vanilla with XFS patch. RAID5 partition is formated to
> XFS.

Reproducing with a different filesystem would probably be a useful
datapoint.



^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: 3ware driver broken with 2.4.22/23 ?
  2003-12-21 11:21 3ware driver broken with 2.4.22/23 ? Lukas Hejtmanek
  2003-12-21 11:29 ` Martin Loschwitz
  2003-12-21 11:48 ` Andre Tomt
@ 2003-12-22  1:16 ` Samuel Flory
  2003-12-27  5:45   ` Joshua Schmidlkofer
  2 siblings, 1 reply; 7+ messages in thread
From: Samuel Flory @ 2003-12-22  1:16 UTC (permalink / raw)
  To: Lukas Hejtmanek; +Cc: linux-kernel, linux

Lukas Hejtmanek wrote:
> 
> Can firmware upgrade help? Or there is an issue with something other not related
> to 3ware card?
> 

   Generally not with such a small rev difference.  You could try the 
latest driver, and firmware in the 7.7.  The driver source is on the Red 
Hat drivers disk.  You should be able to drop in the .c, and .h in 
drivers/scsi, and recompile.
http://3ware.com/support/download.asp?code=5&id=7.7.0&softtype=Driver&releasenotes=&os=Windows

PS- Personally I'd suspect an XFS bug.  Try reiserfs.  I've been running 
2.4.23pres, and 2.4.23 on hundreds of 3ware of numerous different types. 
  With no issue with the prior firmware release.
-- 
There is no such thing as obsolete hardware.
Merely hardware that other people don't want.
(The Second Rule of Hardware Acquisition)
Sam Flory  <sflory@rackable.com>


^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: 3ware driver broken with 2.4.22/23 ?
  2003-12-22  1:16 ` Samuel Flory
@ 2003-12-27  5:45   ` Joshua Schmidlkofer
  2003-12-29 23:49     ` Lukas Hejtmanek
  0 siblings, 1 reply; 7+ messages in thread
From: Joshua Schmidlkofer @ 2003-12-27  5:45 UTC (permalink / raw)
  To: Samuel Flory; +Cc: Lukas Hejtmanek, Linux Kernel Mailing List, linux


>    Generally not with such a small rev difference.  You could try the 
> latest driver, and firmware in the 7.7.  The driver source is on the Red 
> Hat drivers disk.  You should be able to drop in the .c, and .h in 
> drivers/scsi, and recompile.
> http://3ware.com/support/download.asp?code=5&id=7.7.0&softtype=Driver&releasenotes=&os=Windows
> 
> PS- Personally I'd suspect an XFS bug.  Try reiserfs.  I've been running 
> 2.4.23pres, and 2.4.23 on hundreds of 3ware of numerous different types. 
>   With no issue with the prior firmware release.

There are a lot of people, running RAID5 3ware's w/ Terrabyte arrays.  I
don't want to say it is not an XFS bug, but I find that highly suspect. 

js


-- 
VB programmers ask why no one takes them seriously, 
it's somewhat akin to a McDonalds manager asking employees 
why they don't take their 'career' seriously.


^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: 3ware driver broken with 2.4.22/23 ?
  2003-12-27  5:45   ` Joshua Schmidlkofer
@ 2003-12-29 23:49     ` Lukas Hejtmanek
  2003-12-29 23:59       ` Joshua Schmidlkofer
  0 siblings, 1 reply; 7+ messages in thread
From: Lukas Hejtmanek @ 2003-12-29 23:49 UTC (permalink / raw)
  To: Joshua Schmidlkofer; +Cc: Samuel Flory, Linux Kernel Mailing List, linux

On Fri, Dec 26, 2003 at 09:45:25PM -0800, Joshua Schmidlkofer wrote:
> 
> >    Generally not with such a small rev difference.  You could try the 
> > latest driver, and firmware in the 7.7.  The driver source is on the Red 
> > Hat drivers disk.  You should be able to drop in the .c, and .h in 
> > drivers/scsi, and recompile.
> > http://3ware.com/support/download.asp?code=5&id=7.7.0&softtype=Driver&releasenotes=&os=Windows
> > 
> > PS- Personally I'd suspect an XFS bug.  Try reiserfs.  I've been running 
> > 2.4.23pres, and 2.4.23 on hundreds of 3ware of numerous different types. 
> >   With no issue with the prior firmware release.
> 
> There are a lot of people, running RAID5 3ware's w/ Terrabyte arrays.  I
> don't want to say it is not an XFS bug, but I find that highly suspect. 

Well, with ext3 parition iozone program finishes OK. So it looks like some XFS
bug.

-- 
Lukáš Hejtmánek

^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: 3ware driver broken with 2.4.22/23 ?
  2003-12-29 23:49     ` Lukas Hejtmanek
@ 2003-12-29 23:59       ` Joshua Schmidlkofer
  0 siblings, 0 replies; 7+ messages in thread
From: Joshua Schmidlkofer @ 2003-12-29 23:59 UTC (permalink / raw)
  To: Lukas Hejtmanek; +Cc: Samuel Flory, Linux Kernel Mailing List, linux

On Mon, 2003-12-29 at 15:49, Lukas Hejtmanek wrote:
> On Fri, Dec 26, 2003 at 09:45:25PM -0800, Joshua Schmidlkofer wrote:
> > 
> > >    Generally not with such a small rev difference.  You could try the 
> > > latest driver, and firmware in the 7.7.  The driver source is on the Red 
> > > Hat drivers disk.  You should be able to drop in the .c, and .h in 
> > > drivers/scsi, and recompile.
> > > http://3ware.com/support/download.asp?code=5&id=7.7.0&softtype=Driver&releasenotes=&os=Windows
> > > 
> > > PS- Personally I'd suspect an XFS bug.  Try reiserfs.  I've been running 
> > > 2.4.23pres, and 2.4.23 on hundreds of 3ware of numerous different types. 
> > >   With no issue with the prior firmware release.
> > 
> > There are a lot of people, running RAID5 3ware's w/ Terrabyte arrays.  I
> > don't want to say it is not an XFS bug, but I find that highly suspect. 
> 
> Well, with ext3 parition iozone program finishes OK. So it looks like some XFS
> bug.

FWIW have you sent this on to the XFS list?

thanks,
  Joshua





^ permalink raw reply	[flat|nested] 7+ messages in thread

end of thread, other threads:[~2003-12-29 23:59 UTC | newest]

Thread overview: 7+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2003-12-21 11:21 3ware driver broken with 2.4.22/23 ? Lukas Hejtmanek
2003-12-21 11:29 ` Martin Loschwitz
2003-12-21 11:48 ` Andre Tomt
2003-12-22  1:16 ` Samuel Flory
2003-12-27  5:45   ` Joshua Schmidlkofer
2003-12-29 23:49     ` Lukas Hejtmanek
2003-12-29 23:59       ` Joshua Schmidlkofer

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox