Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 04 Aug 2006 13:37:02 +0200
From:      Andras Got <andrej@antiszoc.hu>
To:        freebsd-stable@freebsd.org
Cc:        grs@salaisuus.fi
Subject:   Re: freebsd 6.x and 3ware 9500S-8 in 32bit pci slot
Message-ID:  <44D3315E.2050302@antiszoc.hu>
In-Reply-To: <61f46c042ed2d6199b32a367b9d3432c@salaisuus.fi>
References:  <61f46c042ed2d6199b32a367b9d3432c@salaisuus.fi>

next in thread | previous in thread | raw e-mail | index | archive | help
Hi,

How often is this crash? (daily, weekly, monthy...)

What's the freebsd version you're using?

Can you try your card in an other PCI slot and do you have other PCI devices?

Does this reset and/or crash could be related to high i/o or something else?

We have a similar, but a 4port (9500S-4) controller with 5.5 and in a PCI-X and works fine.

64bit support in freebsd differs from the PCI 64bit. In a PCI-X slot, the 64bit is the databus 
"width", instead of the normal 32bit. You can's enforce it, but it works automatically in PCI-X slots.

(A dmesg and a crash dump, if you can provide it, would be nice for the developer guys imho.)

Regards,
Andrej

Ville Sulin wrote:
> Hi,
> 
> I have a smallish problem, got a backup server with ASUS PC-DL motherboard that doesn't have a 64 bit pci slot
> and a 3ware 9500S-8 card. The machine resets the controller every now and then, but when there's enough disk
> io when it tries to do that the machine crashes.
> 
> console warnings:
> 
> twa0: INFO: (0x04: 0x000c): : unit=0
> twa0: ERROR: (0x05: 0x210b): Request timed out!: request = 0xc64fb1f0
> twa0: INFO: (0x16: 0x1108): Resetting controller...:
> twa0: INFO: (0x04: 0x0001): : SoftResetCount=1
> twa0: INFO: (0x16: 0x1107): Controller reset done!:
> twa0: INFO: (0x04: 0x000c): : unit=0
> 
> lspci -vv :
> 
> 03:0b.0 RAID bus controller: 3ware Inc 9xxx-series SATA-RAID
>         Subsystem: 3ware Inc 9xxx-series SATA-RAID
>         Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
>         Status: Cap+ 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
>         Latency: 32 (2250ns min), Cache Line Size 08
>         Interrupt: pin A routed to IRQ 23
>         Region 0: I/O ports at b000
>         Region 1: Memory at fb800000 (64-bit, non-prefetchable)
>         Region 3: Memory at fb000000 (64-bit, prefetchable)
>         Capabilities: [40] PCI-X non-bridge device
>                 Command: DPERE- ERO- RBC=512 OST=1
>                 Status: Dev=ff:1f.0 64bit+ 133MHz+ SCD- USC- DC=simple DMMRBC=512 DMOST=1 DMCRS=8 RSCEM- 266MHz- 533MHz-
>         Capabilities: [48] Power Management version 2
>                 Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0+,D1+,D2+,D3hot+,D3cold-)
>                 Status: D0 PME-Enable- DSel=0 DScale=0 PME-
> 
> And on the risk of sounding stupid, doesn't this "64bit+" mean that freebsd is using it "with 64 bit" support?
> And if it indeed does, is there any way to force it off?
> 
> If there isn't a simple solution, were just getting a motherboard with 64bit pci slot.
> 
> Thanks
> -Ville
> 
> _______________________________________________
> freebsd-stable@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org"
> 



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?44D3315E.2050302>