SATA Problems - ATA_Identify timeout ERROR - using Tyan S5350 with FreeBSD 5.4

2005-07-01 Thread Alan Jay
 

I suppose the question is was there a problem with the Tyan S5350 motherboard
and its ATA controller - I know that two identical motherboards with different
hard disks exhibit the same problem.  And if so why is it that there has been
little on these lists about problems with the chipset which is on this
motherboard (a fairly common one I believe from Intel).

 

Although the problem went away the machines filesystem seems to have got
corrupted so maybe all was not fixed after all.

 

There have been a number of comments and queries about ATA problems and SATA
problems with 5.4 but no views as to if this is a real problem.

 

Any insights would be gratefully received.

 

One aside when trying to upgrade using CVSUP does the tag need to be RELENG_5
or RELENG_5_4?

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]


RE: SATA Problems - ATA_Identify timeout ERROR - using Tyan S5350 with FreeBSD 5.4 (Adaptec AIC-8110 Compatibility maybe?)

2005-07-01 Thread Alan Jay
Totally agree - I have 2 idential machines that have the same problem
And have tried alternate hard disks all of which exhibit the same 
Problem.  

I would agree with you that the ICH5 must be common and the Tyan S3530 
(http://www.tyan.com/products/html/tigeri7320r_spec.html ) with the Intel
6300SEB which I would have thought (as you say) was very common.

I did notice that Tyan offer the Adaptec AIC-8110 SATA I controller as an add
on module and I wondered if that might be supported but it doesn't seem by
that number to be on the release list (any thoughts).

 -Original Message-
 From: Tony Byrne [mailto:[EMAIL PROTECTED]
 Sent: Friday, July 01, 2005 11:29 AM
 To: Alan Jay
 Cc: freebsd-stable@freebsd.org
 Subject: Re: SATA Problems - ATA_Identify timeout ERROR - using Tyan S5350
 with FreeBSD 5.4
 
 Hello Alan,
 
 AJ There have been a number of comments and queries about ATA problems and
 SATA
 AJ problems with 5.4 but no views as to if this is a real problem.
 
 I have to agree. I've had nothing but trouble with various Intel
 boards with Intel ICH5 controllers and SATA hard disks under FreeBSD
 and yet the problem either doesn't seem to be widespread and isn't
 recognized by the community in general. I find that strange since the
 ICH5 must be common in the field along with SATA disks from Western
 Digital. I would have believed faulty hardware to be the cause, but I
 have *three* machines that are capable of generating DMA TIMEOUTs
 while reading or writing SATA disks.
 
 Regards,
 
 Tony.
 
 --
 Tony Byrne
 


___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]


RE: SATA Problems - ATA_Identify timeout ERROR - using Tyan S5350 with FreeBSD 5.4

2005-07-01 Thread Alan Jay
I thought that as well.  My machine is using a Tyan motherbaord with the Intel
6300SEB and I thought that was a reasnably conservative choice of motherboard.

I don't know if this is a hint not to use SATA/IDE controllers any more but
there are lots of occasions when it is more than enough power to be going on
with.

What is annoying is that there doesn't seem to be enough in the way of problem
reports to say this is not supported so we know we are on to a loosing streak
and need to find an alternate type of hardware.

Does anyone know if the Adaptec AIC-8110 SATA I controller, which Tyan
offer, as an add on module is supported.  The release notes which I have
checked do not mention this number.  But hten this is probably a part number
and not the chip number.

Thanks.



 -Original Message-
 From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Matthias
 Buelow
 Sent: Friday, July 01, 2005 12:49 PM
 To: Tony Byrne
 Cc: Alan Jay; freebsd-stable@freebsd.org
 Subject: Re: SATA Problems - ATA_Identify timeout ERROR - using Tyan S5350
 with FreeBSD 5.4
 
 Tony Byrne [EMAIL PROTECTED] writes:
 
 ICH5 must be common in the field along with SATA disks from Western
 Digital. I would have believed faulty hardware to be the cause, but I
 have *three* machines that are capable of generating DMA TIMEOUTs
 while reading or writing SATA disks.
 
 In my case here, it's ICH6 and Seagate. Normally this is a good
 combination that should work flawlessly... I mean, you can't get
 more conservative than an Intel chipset and a Seagate disk.
 
 mkb.

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]


SATA Problems - ATA_Identify timeout ERROR - using Tyan S5350

2005-07-01 Thread Alan Jay
Further to this the same ATA Timeout is seen in the latest SNAP binaries (1st
July).

 

 

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]


RE: SATA Problems - ATA_Identify timeout ERROR - using Tyan S5350

2005-07-01 Thread Alan Jay
Thanks for this - I haven't try but will do so - but I do need a little help.
I have downloaded the STABLE version and put it onto my machines.  Do I have
to compile the ATA driver into the system and if so how do I do so (sorry to
ask no instructions on the web site below).

Thanks.


 -Original Message-
 From: Dominic Marks [mailto:[EMAIL PROTECTED]
 Sent: Friday, July 01, 2005 5:00 PM
 To: freebsd-stable@freebsd.org; [EMAIL PROTECTED]
 Subject: Re: SATA Problems - ATA_Identify timeout ERROR - using Tyan S5350
 
 On Friday 01 July 2005 16:34, Alan Jay wrote:
  Further to this the same ATA Timeout is seen in the latest SNAP
  binaries (1st July).
 
 
 Do you see them with ATA mkIII as well?
 
  http://people.freebsd.org/~sos/ATA/
 
  ___
  freebsd-stable@freebsd.org mailing list
  http://lists.freebsd.org/mailman/listinfo/freebsd-stable
  To unsubscribe, send any mail to
  [EMAIL PROTECTED]
 
 HTH,
 --
 Dominic
 GoodforBusiness.co.uk
 I.T. Services for SMEs in the UK.

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]


RE: Re[2]: SATA Problems - ATA_Identify timeout ERROR - using Tyan S5350

2005-07-01 Thread Alan Jay
Tony,

Interesting that you have seen different disks producing different timeout
issues (or not) so far on my experiments with 4 different disks 2 SATA 2 IDE
(different dises) is that the timeout error has appears on all of them.

Regads
ALan

 -Original Message-
 From: Tony Byrne [mailto:[EMAIL PROTECTED]
 Sent: Friday, July 01, 2005 5:12 PM
 To: Dominic Marks
 Cc: freebsd-stable@freebsd.org; [EMAIL PROTECTED]
 Subject: Re[2]: SATA Problems - ATA_Identify timeout ERROR - using Tyan
 S5350
 
 Hello Dominic,
 
 DM Do you see them with ATA mkIII as well?
 
 I tried the ATA mkIII patches a few weeks ago on one of servers, which
 was suffering DMA TIMEOUTs, but they made no difference.
 
 This problem may only occur with certain combinations of controller
 and SATA hard drive. For example, I have a workstation with an ICH5
 controller which had been frequently emitting TIMEOUT messages when it
 had a 80Gb 7200k Seagate Barracuda SATA drive installed. As a test
 this afternoon, I swapped out the Seagate for a new 250Gb Western
 Digital SATA drive, and installed 5.4 RELEASE. The machine is now in
 the process of building world, and I've yet to see any TIMEOUTs.
 
 Regards,
 
 Tony.
 
 --
 Tony Byrne
 


___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]


RE: ATA_Identify timeout ERROR - using Tyan S5350 with FreeBSD 5.4 (problems booting - SATA hard disk not recognised) -

2005-06-30 Thread Alan Jay
Hi,

Thought I would report back what I discovered.

Following some suggestions on this list I booted into safe mode and installed
the operating system successfully.  I still couldn't get the machine to boot
except in safe mode.  

After updating the source to the latest stable incarnation via cvsup I did a
makeworld and rebuilt the kernel to take advantage of SMP support of our twin
processors.

At the end of that process the server boots fine.  Not sure what the error was
but it is still the case if you use the basic downloaded boot CD from the
archives and boot the server it complains as below. 

But with the recompiled kernel it is fine.

Does anyone have any insigts?

Regards
Alan

 -Original Message-
 From: Alan Jay [mailto:[EMAIL PROTECTED]
 Sent: Tuesday, June 14, 2005 8:25 PM
 To: 'freebsd-questions@freebsd.org'; 'freebsd-stable@freebsd.org'
 Subject: ATA_Identify timeout ERROR - using Tyan S5350 with FreeBSD 5.4
 (problems booting - SATA hard disk not recognised) -
 
 
 
 Hi,
 
 I just got a new Tyan S5350 using twin Xeon processors I am told this is now
 a
 very standard motherboard.
 
 Unfortunately when I try to boot FreeBSD 5.4 Release I get the following
 errors on the IDE/ATA/SATA connection.
 
 The errors I get during boot up are as follows:
 
 The hard disk is not recognised you get the error:
 
 Ata0_master: Failure ATAPI_IDENTITY timeout (x3) Then
 Ata1_master: Failure ATA_Identify timeout (x3)
 
 This is true if I use a standard IDE drive (160Gb) or a SATA drive (250Gb).
 The BIOS recognises the drives and is happy with them but the OS has this
 problem.
 
 The board appears to use the Intel 6300SEB chip set using for the
 IDE/ATA/SATA
 
 is it supported?  Or is there a problem with my motherboard?
 
 The board we have is:
 http://www.tyan.com/products/html/tigeri7320r_spec.html
 
 If anyone is using this motherboard successfully please let me know so I can
 organise a replacement.
 
 Any other help gratefully received.
 
 Alan Jay
 
 PS The rest of the machine specs are - twin Xeon processor; 4 Gb RAM; Intel
 Gigabit Network card in the PCI slot.  250Gb SATA drive.
 
 PPS Having looked around the lists there appear to be people who say this is
 related to the issues described 5.2.1 release errata
 (http://www.freebsd.org/releases/5.2.1R/errata.html)
 
 PPPS loading in safe mode does work but it isn't a viable way to run a
 server
 anyone got any ideas why this occurs and how to work around it the ideas in
 the errata for 5.2.1 don't seem to work assuming that I have the syntax
 correct in the /boot/loader.comf

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]


ATA_Identify timeout ERROR - using Tyan S5350 with FreeBSD 5.4 (problems booting - SATA hard disk not recognised) -

2005-06-14 Thread Alan Jay


Hi,

I just got a new Tyan S5350 using twin Xeon processors I am told this is now a
very standard motherboard.  

Unfortunately when I try to boot FreeBSD 5.4 Release I get the following
errors on the IDE/ATA/SATA connection.

The errors I get during boot up are as follows:

The hard disk is not recognised you get the error:

Ata0_master: Failure ATAPI_IDENTITY timeout (x3) Then
Ata1_master: Failure ATA_Identify timeout (x3)

This is true if I use a standard IDE drive (160Gb) or a SATA drive (250Gb).
The BIOS recognises the drives and is happy with them but the OS has this
problem. 

The board appears to use the Intel 6300SEB chip set using for the IDE/ATA/SATA

is it supported?  Or is there a problem with my motherboard?

The board we have is:
http://www.tyan.com/products/html/tigeri7320r_spec.html

If anyone is using this motherboard successfully please let me know so I can
organise a replacement.  

Any other help gratefully received.

Alan Jay 

PS The rest of the machine specs are - twin Xeon processor; 4 Gb RAM; Intel
Gigabit Network card in the PCI slot.  250Gb SATA drive. 

PPS Having looked around the lists there appear to be people who say this is
related to the issues described 5.2.1 release errata
(http://www.freebsd.org/releases/5.2.1R/errata.html) 

PPPS loading in safe mode does work but it isn't a viable way to run a server
anyone got any ideas why this occurs and how to work around it the ideas in
the errata for 5.2.1 don't seem to work assuming that I have the syntax
correct in the /boot/loader.comf 

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]


Problems with Serial ATA - Tyan Tiger i7320 motherboard

2005-06-10 Thread Alan Jay


I just got a machine Tyan Tiger i7320 motherboard with a 250Gb Serial ATA
Hitachi drive.
 
When I try to boot FreeBSD 5.4 Release it says:
 
ATA0 ATAPI IDENTITY_TIMEOUT several times
And
ATA1 IDENTIFY_TIMEOUT
 
Before the install starts - RedHat Liunx correctly sees the drive. :(

Does this mean FreeBSD does not support this or have I got the wrong BIOS
settings.  Any help gratefully received.

It is an Adaptec AIC-8110 SATA I controller I think.  In the startup of
FreeBSD it says Intel 6300ESB UDMA100 controller (atapci0 atapci1)

Thanks
ALan





___ 
Yahoo! Messenger - NEW crystal clear PC to PC calling worldwide with voicemail 
http://uk.messenger.yahoo.com
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]


RE: DELL PowerEdge 2850 and FreeBSD 5.4

2005-06-01 Thread Alan Jay
Hi,

I have a Tyan based 1U computer with twin Xeon and 6Gb RAM which we recently
installed 5.4 Release on.  When we recompiled the kernel with the SMP and PAE
options it would randomly reboot but so far (touch wood) using it with just
4Gb or RAM and removing the PAE kernel (just leaving the SMP one) it seems to
be stable.  We have yet to successfully get a PAE kernel to run consistently.
While running the ACPI/HTT and SMP seem to work ok have you tried this?

ALan

 -Original Message-
 Date: Tue, 31 May 2005 11:58:53 +0100
 From: Danny Cooper [EMAIL PROTECTED]
 
 I have installed FreeBSD 5.4 RELEASE and upgraded to -STABLE on a DELL
 PE2850.
 
 FreeBSD 5.4-STABLE #1: Wed May 25 23:43:12 BST 2005
 CPU: Intel(R) Xeon(TM) CPU 3.20GHz (3192.22-MHz 686-class CPU)
 real memory  = 5100273664 (4864 MB)
 avail memory = 4189892608 (3995 MB)
 MPTable: DELL PE 016D 
 FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs
 cpu0 (BSP): APIC ID:  0
 cpu1 (AP): APIC ID:  6
 amr0: LSILogic PERC 4e/Di Firmware 516A, BIOS H418, 256MB RAM
 
 I have disabled ACPI HTT and enabled PAE to make the whole system memory
 available.
 
 However the problem I have is the system can crash at any moment, and is not
 load related. As the crash info below is when the machine was in an 100%
 idle state.
 
 I have tried to install other versions of FreeBSD.
 
 4.11 Release (Doesn't see all available memory even with a kernel patch)
 5.4 Release (Crashes at random times, but mainly under load, running squid)
 
 
 Does anyone have similar problems or have found a work around?
 
 
 Danny C


___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]


problems with setting kern.maxdsiz in /boot/loader.conf

2005-05-06 Thread Alan Jay


I am running 5.4 RC4 and rebooted today after changing one of the boot-time
variables (maximum data size) in /boot/loader.conf.  I took it from 512MB to
2GB of RAM in order to improve the MySQL performance on the server.

However, upon reboot, the following error comes up:

Fatal trap 9: general protection fault while in kernel mode cpuid = 0; apic id
= 00
instruction pointer = 0x58:0x8bc
stack pointer   = 0x10:0xf80
frame pointer   = 0x10:0x0
code segment= base 0xc00f, limit 0x, type 0x1b
= DPL 0, pres 1, def32 0, gran 0
processor eflags= interrupt enabled, resume, IOPL = 0
current process = 0 (swapper)
trap number = 9
panic: general protection fault
cpuid = 0
Uptime: 1s

I tried resetting kern.maxdsiz backto 512MB by pressing 6 at the boot menu and
doing:
unset kern.maxdsiz
set kern.maxdsiz=536870912
show kern.maxdsiz
- this did not have any effect - exactly the same thing happened again.

Is the kern.maxdsiz now being reset or being reset by /boot/loader.conf after
changing things in the loader does anyone have any ideas.

Nothing else has changed on the server which is being prepared for use at the
moment and was updated to 5.4 RC4 just a few days ago but which has been
running fine and rebooting fine since then until this change.

Any ideas?

Thanks in advance

Alan

PS I assume the only way to remove /boot/loader.conf is to use the 2nd CD set
in fixit mode and remove / edit the file after mounting the root partition.

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Problems with AMD64 and 8 GB RAM?

2005-03-31 Thread Alan Jay
 Date: Thu, 31 Mar 2005 16:12:35 +0900
 From: Ganbold [EMAIL PROTECTED]
 Subject: Re: Problems with AMD64 and 8 GB RAM?
 
 Hi,
 
 Since we are discussing AMD64 with 8GB RAM, I also would like to point my
 problem.
 
 I'm still looking for possibility to run FreeBSD 5.3-STABLE with more than
 4GB RAM
 on Dual amd64 2.2GHz machine (IBM @server 325) with ServeRAID 6M (ips
 driver)).
 Right now I'm using only 4GB RAM and this server is in production.
 
 #uname -an
 FreeBSD publica.ub.mng.net 5.3-STABLE FreeBSD 5.3-STABLE #12: Mon Nov 22
 12:04:57 ULAT 2004 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/AMD
 amd64
 
 As Scott said a few months ago, problem is below:
 
 The ips driver looks like it will fail under heavy load when more than 4GB
 of RAM is present.  It tries to force busdma to not defer requests when the
 bounce page reserve is low, but that looks to be broken and
 will result in corrupted commands.

[Alan Jay] Since we are talking about FreeBSD on AMD64 on the AMD64 list I
have reported issues on that list.

I have a TyanThunder K8S pro S2882 twin Operteron with 8Gb of RAM and although
I can get the machine to run reasonably stably with 8Gb of RAM with limited
loading when pushed it falls over unpredictably.

We did some tests with the latest 5.3-STABLE / 5.4-PRERELEASE and still found
the same issues when using a mySQL database heavily hit over the Ethernet
controller.  Our final tests limited the memory on boot-up to 4Gb and the bug
is still there so we think it may well be some interaction with the Ethernet
controller.  The motherboard we have has a BroadcomBCM5704C 10/100/1000 based
card on board.  

Again this works fine initially but then we get a very dramatic failure with
no warning messages and the system falls over.  

There are still a few issues to be ironed out with the FreeBSD 5.x on AMD64
the latest STABLE/PRE-RELEASE is much improved but be aware there may be
issues.  We will be waiting a few more weeks before re-trying these tests to
see if the latest fixes that have been discussed have solved our problems.



___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]


UPDATE 5.3-STABLE was Re: Possible problems with Broadcom BCM5704C 10/100/1000 on TyanThunder K8S pro S2882 twin Operteron

2005-03-07 Thread Alan Jay
Hi,

Well after upgrading to the latest -STABLE via cvsup and makeworld makekernel
etc we have been doing some more tests over the weekend.

One of our databases ran fine all weekend so we took the plunge on Sunday to
try our big heavily accessed database.

It ran fine until 7.45 Monday morning - when I checked at 7.30am it was using
around 6 of the 8Gb of RAM the server then logged:

Mar  7 07:42:47 flappy kernel: bge1: discard frame w/o leading ethernet header
(len 4294967292 pkt len 4294967292)

Followed by:

Mar  7 07:42:47 flappy kernel: Fatal trap 12: pag
Mar  7 07:42:47 flappy kernel: e f
Mar  7 07:42:47 flappy kernel: ault
Mar  7 07:42:47 flappy kernel: wh
Mar  7 07:42:47 flappy kernel: ile in
Mar  7 07:42:47 flappy kernel: k
Mar  7 07:42:47 flappy kernel: er
Mar  7 07:42:47 flappy kernel: ne
Mar  7 07:42:47 flappy kernel: l mode
Mar  7 07:42:47 flappy kernel:
Mar  7 07:42:47 flappy kernel: cp
Mar  7 07:42:47 flappy kernel: ui
Mar  7 07:42:47 flappy kernel: d
Mar  7 07:42:47 flappy kernel: =
Mar  7 07:42:47 flappy kernel: 1;
Mar  7 07:42:47 flappy kernel: a
Mar  7 07:42:47 flappy kernel: pi
Mar  7 07:42:47 flappy kernel: c
Mar  7 07:42:47 flappy kernel: i
Mar  7 07:42:47 flappy kernel: d
Mar  7 07:42:47 flappy kernel: =
Mar  7 07:42:47 flappy kernel: 01
Mar  7 07:42:47 flappy kernel:
Mar  7 07:42:47 flappy kernel: fa
Mar  7 07:42:47 flappy kernel: ul
Mar  7 07:42:47 flappy kernel: t
Mar  7 07:42:47 flappy kernel: vi

Subsequently to that it has crashed a number of times and on a couple of
occasions has reported:

kernel: fxp0: can't map mbuf (error 12)

To my uninitiated eye it looks like this might have something to do with the
Network Performance Project which seems to be tinkering in this area but I
would appreciate any thoughts anyone might have regarding this.

By the way over the weekend the latest -STABLE which is marked 5.4-PRERELEASE
2 seemed much better than 5.3 had and the initial problems took much longer to
appear.  Though once the problems started to appear, they repeated themselves
rebooting every 1-2hrs until we removed the tests data.

Thanks for the guidance,
ALan

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Can FreeBSD 5.3R support the RAID card MegaRAID SCSI 320-2E

2005-03-05 Thread Alan Jay
 Subject: Re: Can FreeBSD 5.3R support the RAID card MegaRAID SCSI 320-2E
card?
  I have search amr on
 
 http://www.freebsd.org/cgi/man.cgi?query=amrsektion=4manpath=FreeBSD+5.3-
 RELEASE
 
  It said support the following:
   7   AMI MegaRAID 320-1
   7   AMI MegaRAID 320-2
   7   AMI MegaRAID 320-4X
   7   AMI MegaRAID Series 418
 
  Anyone knows amr supports MegaRAID SCSI 320-2E card?
  TKS.
 
 The amr(4) manpage in -CURRENT lists the 320 variants, the -2E
 specifically (is that a PCI Express version?).  We have a amr(4)  driver
 update coming in shortly to -CURRENT and then RELENG_5; keep an eye out
 for that and test it if you can.

We use these RAID controllers on our machines and have been running the 320-1
and 320-2 with 4.10 very happily and without incident.  We have also been
running the 320-1 on 5.3 -STABLE and although we have had problems with 5.3 it
hasn't had anything to do with the RAID controller :).

From the LSI Logic web site
(http://www.lsilogic.com/products/megaraid/index.html) the E does look like
the PCI Express version. 

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]


RE: Possible problems with Broadcom BCM5704C 10/100/1000 on TyanThunder K8S pro S2882 twin Operteron

2005-03-04 Thread Alan Jay
A couple of weeks ago we reported a potential problem with the Broadcom
BCM5704C 10/100/1000 onboard Ethernet (being used in Gigabit mode) controller
on the Tyan Thunder pro S2882 with twin Operteron and 8Gb of RAM.   

The system was running a three databases using mySQL - the first database ran
fine but the others when hit hard caused the server to crash in what appeared
to be a memory / Ethernet controller error.

We have now done the first phase of some tests and thought we would report
back. 

We switched off the broadcom Ethernet controller (via software) and routed all
traffic via the boards Intel 10/000 Ethernet connection.  One of the problem
databases has now been running for a few days and so far has been ok.

We will be doing some more tests over the next few days but this seems to be
pointing to some issues with the driver for the Broadcom Ethernet Chipset.  

Alan

 Having got 5.3 onto our new twin operteron Tyan Thunder K8S Pro S2882 with
8Gb
 of RAM and had a reasonabley stable operation for a few days we installed a
 couple of databases one worked fine but the other kept on causing the server
 to crash.  After some hunting around we found discussion about problems with
 the on board Broadcom BCM5704C 10/100/1000 Gigabit ethernet controller on
 Linux last year and wondered if there were similar issues with FreeBSD 5.3's
 broadcom driver?

 The problem only seems to happen when the controller is streched with lots
of
 data as the other mySQL database runs fine but switching to the more load
 intensive one causes issues.
  
 
 Thanks in advance for your advice.
 Alan Jay

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]


RE: Possible problems with Broadcom BCM5704C 10/100/1000 on Tyan Motherboard (2)

2005-02-16 Thread Alan Jay
 -Original Message-
 From: David O'Brien [mailto:[EMAIL PROTECTED]
 
 On Tue, Feb 15, 2005 at 04:53:24PM -, Alan Jay wrote:
  I had major problems installing with more than 4Gb but once I moved to
 stable
  we seemed to have a stable platform when doing basic stuff - we have two
  databases (mySQL) one is reasonably heavily used and one very extensively
  used.
 
 Just to be clear, you're stating you had stability problems with
 5.3-RELEASE and 4GB.  But with 5.3-STABLE and 4GB you have a stable
 system.  Correct?

[Alan Jay] Further to my comments yesterday - I would say that the system
appeared to be stable.  It is possible that when we ran a more extensive and
more often hit database that it used more memory and that is what caused the
problem.  BUT all the tests we did relating to memory didn't turn up any
issues - so we looked for other culprits.

One of the few errors we saw was relating to the Broadcom Gigabit link - I
will try to do some tests in the next week or so using the other onboard
Ethernet controller to see if that rules out the Broadcom or focuses the cause
of the problem.
 
  I think I agree wholeheartedly with your comments being a great supporter
 of
  FreeBSD it is a shame that the AMD release is not as super as the other
  versions we have used extensively.
 
 Of course one reason many are moving to the AMD64 platform is to have
 4GB RAM in the machine.  We believe this bug has been fixed in
 5.3-STABLE.  But too few people are testing 5.3-STABLE and are using
 5.3-RELEASE instead.  This isn't helping us QA the issue so that we know
 all the corner cases are fixed in upcoming 5.4 release.

[Alan Jay] Thanks for this and it was exactly the reason we moved to the AMD64
platform.
 
 A recent 5.3-STABLE snapshot can be found as
 ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/Feb_2005/5.3-STABLE-SNAP001-
 amd64-miniinst.iso
 and mirrors.
 
 --
 -- David  ([EMAIL PROTECTED])

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]


RE: Possible problems with Broadcom BCM5704C 10/100/1000 on Tyan Motherboard

2005-02-15 Thread Alan Jay
Thanks for this - the oddity is we have two identical machines and on one the
problem occurred we then moved the application over to the other machines that
had been working fine and it then exhibited the same symptoms - hence the
query about the broadcom controller.  I am hoping to so some further tests
using the other Ethernet controller on the board if I can get it plugged in
(unfortunately the machines are in a data center to which I don't have direct
access).

Thanks for the ideas.

ALan

 -Original Message-
 From: Doug White [mailto:[EMAIL PROTECTED]
 Sent: Monday, February 14, 2005 6:16 PM
 To: Alan Jay
 Cc: freebsd-stable@freebsd.org
 Subject: Re: Possible problems with Broadcom BCM5704C 10/100/1000 on Tyan
 Motherboard
 
 On Mon, 14 Feb 2005, Alan Jay wrote:
 
  I have FreeBSD 5.3 STABLE onto our new twin operteron Tyan Thunder K8S Pro
  S2882 with 8Gb of RAM and had a reasonably stable operation for a few days
 we
  installed a couple of databases one worked fine but the other kept on
 causing
  the server to crash.
 
 I'm about to gain access to an S2881, which is a similar board (different
 layout but same parts).
 
  I have searched the archive and there were issues last year but I couldn't
  work out if these have been totally resolved?
 
  The adapter does work fine in low levels of loading but when pushed (it is
  connected to a Gigabit switch) it seems to be the cause of the reboot - a
 what
  appeared to be stable server with moderate Ethernet activity was fine
 upping
  the activity with a new service caused regular reboots.
 
  There is no console message at the point of reboot to help that we have
  spotted.
 
 
 Hm, triple fault or other hardware reset. This usually indicates bad
 hardware.  Have you tried swapping the RAM between the systems and seeing
 if the problem follows?  An unrecoverable ECC fault can cause a reboot,
 along with strangeness caused  by temperature/power supply/etc.  Or the
 board could be Just Plain Bad.
 
 Considering you have one working machine, adn this is a very popular
 board, I don't think it s abasic problem with FreeBSD and this hardware.
 The worst thing reported is interrupt routing usually.
 
 --
 Doug White|  FreeBSD: The Power to Serve
 [EMAIL PROTECTED]  |  www.FreeBSD.org

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]


RE: Possible problems with Broadcom BCM5704C 10/100/1000 on Tyan Motherboard

2005-02-15 Thread Alan Jay
Thanks Jonathan for this, can I ask the unmentionalble (which Linux
implementation did you pick?).

I had major problems installing with more than 4Gb but once I moved to stable
we seemed to have a stable platform when doing basic stuff - we have two
databases (mySQL) one is reasonably heavily used and one very extensively
used.  They sit on different servers to maximise performance.  One worked
perfectly for a couple of weeks while the other more extensive one repeatedly
fell over.

I think I agree wholeheartedly with your comments being a great supporter of
FreeBSD it is a shame that the AMD release is not as super as the other
versions we have used extensively.

Thanks for your support.

Regards
ALan

 -Original Message-
 From: Jonathan A. Dama [mailto:[EMAIL PROTECTED]
 Sent: Tuesday, February 15, 2005 1:47 AM
 To: Doug White
 Cc: Alan Jay; freebsd-stable@freebsd.org; [EMAIL PROTECTED]
 Subject: Re: Possible problems with Broadcom BCM5704C 10/100/1000 on Tyan
 Motherboard
 
 We also have these boards, I've found them unusable under
 FreeBSD/5.3-STABLE with 8GB of RAM--other qualities appear to work okay.
 But I even saw some infrequent problems with 6GB.
 
 FreeBSD/amd64 is not in my opinion not actually a stable tier 1 quality
 release under these configurations, too many problems remain--especially
 in regards to ia32 emulation.
 
 Exigencies of the moment forced us to forgo further debugging and adopt
 linux/amd64.  (Sadly, some people actually have to get work done on their
 hardware...)
 
 To anyone who wants to peg these problems on hardware, running linux these
 machines have operated without fault while under a mix of high
 computational and i/o load.   moreover, the machines were tested
 extensively using memtest+ in a controlled ambient temperature range from
 60F to 80F.
 
 This is a really lamentable situation.  We've been a primarily FreeBSD
 shop for 10 years now and for the past 4 years or so a pure FreeBSD shop.
 Switching to linux on just these machines has been quite the headache but
 I'm holding on to the hope that FreeBSD/amd64 will shape up.
 
 FYI, most of the positive reports I've seen regarding FreeBSD and this
 motherboard are 2GB setups.  In my own testing that arrangement worked
 _very_ well.
 
 Addendum: The RAM timing is a bit marginal on the second processor.  i.e.,
   RAM that runs fine under extensive memtest+ ing has trouble
   doing 400MHz DDR on the Second Processor.  We ended up running
   it at 333MHz DDR
 
 -Jon
 
 
 
 On Mon, 14 Feb 2005, Doug White wrote:
 
  On Mon, 14 Feb 2005, Alan Jay wrote:
 
   I have FreeBSD 5.3 STABLE onto our new twin operteron Tyan Thunder K8S
 Pro
   S2882 with 8Gb of RAM and had a reasonably stable operation for a few
 days we
   installed a couple of databases one worked fine but the other kept on
 causing
   the server to crash.
 
  I'm about to gain access to an S2881, which is a similar board (different
  layout but same parts).
 
   I have searched the archive and there were issues last year but I
 couldn't
   work out if these have been totally resolved?
  
   The adapter does work fine in low levels of loading but when pushed (it
 is
   connected to a Gigabit switch) it seems to be the cause of the reboot -
 a what
   appeared to be stable server with moderate Ethernet activity was fine
 upping
   the activity with a new service caused regular reboots.
  
   There is no console message at the point of reboot to help that we have
   spotted.
 
 
  Hm, triple fault or other hardware reset. This usually indicates bad
  hardware.  Have you tried swapping the RAM between the systems and seeing
  if the problem follows?  An unrecoverable ECC fault can cause a reboot,
  along with strangeness caused  by temperature/power supply/etc.  Or the
  board could be Just Plain Bad.
 
  Considering you have one working machine, adn this is a very popular
  board, I don't think it s abasic problem with FreeBSD and this hardware.
  The worst thing reported is interrupt routing usually.
 
  --
  Doug White|  FreeBSD: The Power to Serve
  [EMAIL PROTECTED]  |  www.FreeBSD.org
  ___
  freebsd-stable@freebsd.org mailing list
  http://lists.freebsd.org/mailman/listinfo/freebsd-stable
  To unsubscribe, send any mail to [EMAIL PROTECTED]
 

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]


RE: Possible problems with Broadcom BCM5704C 10/100/1000 on Tyan Motherboard

2005-02-15 Thread Alan Jay
 
 The 4GB problems with 5.3-RELEASE are a well known problem and affect
 for i386 and amd64.  It's pretty much fixed in the 5.3-STABLE stream,
 but there are a few edge cases that I still need to fix which prevent me
 from feeling good about turning it into a 5.3-R errata fix.  It'll
 definitely be fixed and fully working for 5.4-RELEASE next month.
 
 Scott

Scott thanks for that update.

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]


RE: Possible problems with Broadcom BCM5704C 10/100/1000 on Tyan Motherboard

2005-02-15 Thread Alan Jay
 -Original Message-
 On Tue, Feb 15, 2005 at 04:53:24PM -, Alan Jay wrote:
  I had major problems installing with more than 4Gb but once I moved to
 stable
  we seemed to have a stable platform when doing basic stuff - we have two
  databases (mySQL) one is reasonably heavily used and one very extensively
  used.
 
 Just to be clear, you're stating you had stability problems with
 5.3-RELEASE and 4GB.  But with 5.3-STABLE and 4GB you have a stable
 system.  Correct?

[Alan Jay] I could not install with RELEASE but could with Stable.

Once installed and running we installed mySQL on the two machines one we
copied over a relatively simple database which ran fine without a problem.

The second machine then had another mySQL database moved to it and it started
to fall over.  After a number of tests we moved the first database off the
what had been working server and put the other database on it.  At which point
that server which had been stable fell over!
 
  I think I agree wholeheartedly with your comments being a great supporter
 of
  FreeBSD it is a shame that the AMD release is not as super as the other
  versions we have used extensively.
 
 The problem is a major bug that has existed since FreeBSD ?3.0? was
 exposed very close to the 5.3 release cycle.  This bug only causes a
 major problem with 4GB, thus few of us developers experienced it.
 [Most of us can't afford 4GB in our machines.  Donations of 1GB DIMMs
 for FreeBSD developers are accepted by [EMAIL PROTECTED]

[Alan Jay] I'll put them on my present list :)
 
 Of course one reason many are moving to the AMD64 platform is to have
 4GB RAM in the machine.  We believe this bug has been fixed in
 5.3-STABLE.  But too few people are testing 5.3-STABLE and are using
 5.3-RELEASE instead.  This isn't helping us QA the issue so that we know
 all the corner cases are fixed in upcoming 5.4 release.

[Alan Jay] Well the memory seemed to be stable on 5.3 STABLE with more than
4Gb in our case 8Gb there seems to be some other problem at work here.
 
 A recent 5.3-STABLE snapshot can be found as
 ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/Feb_2005/5.3-STABLE-SNAP001-
 amd64-miniinst.iso
 and mirrors.
 
 --
 -- David  ([EMAIL PROTECTED])

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]


Possible problems with Broadcom BCM5704C 10/100/1000 on Tyan Motherboard

2005-02-14 Thread Alan Jay

Hi,

I have FreeBSD 5.3 STABLE onto our new twin operteron Tyan Thunder K8S Pro
S2882 with 8Gb of RAM and had a reasonably stable operation for a few days we
installed a couple of databases one worked fine but the other kept on causing
the server to crash.  

I have searched the archive and there were issues last year but I couldn't
work out if these have been totally resolved?

The adapter does work fine in low levels of loading but when pushed (it is
connected to a Gigabit switch) it seems to be the cause of the reboot - a what
appeared to be stable server with moderate Ethernet activity was fine upping
the activity with a new service caused regular reboots.

There is no console message at the point of reboot to help that we have
spotted.

After some hunting around we found discussion about problems with this
motherboards on board Broadcom BCM5704C 10/100/1000 Gigabit Ethernet
controller on Linux last year and wondered if there were similar issues with
FreeBSD 5.3's Broadcom driver?

The problem only seems to happen when the controller is stretched with lots of
data as the other mySQL database runs fine but switching to the more load
intensive one causes issues.

Thanks in advance for your advice.






___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]