Re: System Still Freezing

2006-03-16 Thread Chuck Swiger
Grant Peel wrote:
 As you may be aware, I have a PE 1850 that has started to intermitantly
 freeze (this all started Feb 23rd). SOmetimes, it will run for 2 days,
 then freeze, sometimes it can run as long as 5 days.
 
 All logs and everything turned up to near debug, show nothing. The
 system just stops dead, and again, a physical suyvey of the server
 reveals nothing. All lights still working and blinking, no excessive
 heat not beeps etc etc.

Maybe your power supply is going bad and delivering marginal voltages?
Do you have it in a redundant config, or could you try adding a second PSU?

 A week ago, I ran every 32 bit Dell diagnostic I could on it ... for 4
 hours straight and not 1 error found. I also ran memetst86 for 3 hours
 and no errors found.

That's interesting but not really conclusive.  If it's taking 2-5 days for
FreeBSD to die, you're probably going to have to run memtest or prime95 at least
overnight (12+ hours, and it would be better to run them for longer) to really
catch anything.

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


Re: System Still Freezing

2006-03-16 Thread Ken Stevenson

Grant Peel wrote:

Hi all,

Another chapter in the life (and death), of my Dell PE 1850.

As you may be aware, I have a PE 1850 that has started to intermitantly 
freeze (this all started Feb 23rd). SOmetimes, it will run for 2 days, 
then freeze, sometimes it can run as long as 5 days.


All logs and everything turned up to near debug, show nothing. The 
system just stops dead, and again, a physical suyvey of the server 
reveals nothing. All lights still working and blinking, no excessive 
heat not beeps etc etc.


A week ago, I ran every 32 bit Dell diagnostic I could on it ... for 4 
hours straight and not 1 error found. I also ran memetst86 for 3 hours 
and no errors found.




I don't have an answer for you, but I had a very similar problem. It's 
why I'm running FreeBSD now. I had RedHat 9 installed on a Dell 2650 
running Apache 2, Postfix, Postgresql, Bind ... My system has a DRAC, 
raid, and a single processor. Actually I have 2 identical servers. One 
server is only for backup and lightly used and it never had a problem.


The symptoms on my primary server were exactly the same. Sometimes it 
would seize up twice in one week. Sometimes it would run for weeks. 
The weird thing was that it would respond to pings. However no system 
services responded and the console was totally unresponsive.


In frustration after not being able to figure out what was causing the 
problem, I decided to try FreeBSD 6 Stable. End of problem. I never 
figured out if it was the operating system, or an application or what.


If you're desperate, you might want to try the opposite: load Linux. 
If you're looking for something that feels familiar to a FreeBSD'er, 
try Gentoo.



--
Ken Stevenson
Allen-Myland Inc.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


RE: System Still Freezing

2006-03-16 Thread fbsd_user
System freezes are all most always (94% of the time) hardware
problems.
Power supply overheating, power supply voltage output falling to
low,
dust on motherboard causing overheating, or first signs of hard
drive failure.
Running mfg diagnostic will not identify these types of problems
until
they become close to total failure.

If you want to eliminate 6.0 as cause install 4.11.
That's before all the current major changes were applied.

But my money is on hardware starting to fail.

If I was you, I would make an backup to different hard drive of any
data I did not want to lose.

The warning signs are staring you straight in the face.

I had this happen to me and was so frustrated over it. Once I
replaced the
hard drive FreeBSD was installed on the freeze ups stopped. I still
am using
that HD in the same box for backup storage with out any problems
since. Go figure.

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Grant Peel
Sent: Thursday, March 16, 2006 9:04 AM
To: freebsd-questions@freebsd.org
Subject: System Still Freezing


Hi all,

Another chapter in the life (and death), of my Dell PE 1850.

As you may be aware, I have a PE 1850 that has started to
intermitantly
freeze (this all started Feb 23rd). SOmetimes, it will run for 2
days, then
freeze, sometimes it can run as long as 5 days.

All logs and everything turned up to near debug, show nothing. The
system
just stops dead, and again, a physical suyvey of the server reveals
nothing.
All lights still working and blinking, no excessive heat not beeps
etc etc.

A week ago, I ran every 32 bit Dell diagnostic I could on it ... for
4 hours
straight and not 1 error found. I also ran memetst86 for 3 hours and
no
errors found.

Here are some particulars:

FreeBSD 6.0 RELEASE
Dell PowerEdge 1850
-Intel 3.0 GHz Duel Core.
-512 MB DDR RAn
-74 GB SCSI Seagate Cheetah 10k.
- 2 Onboard Intel Pro1000 (1 GB) NICS (Both connected to my switch,
1 LAN
and 1 WAN.).
- 1 Built in (Dedicated Riser) DRAC 4/I card.
- NO RAID, No Extra VIdeo or sound. No keyboard plugged in, no
monitor.

SHould I consider diableing APIC and Hyperthreading? Does anything
know if
these two would be causing all the issues I have in the kernel?

I have been reading alot about interupt storms lately. How can I
tell if
this is whats happeneing here?

Thanks again all,

-GRant


Kernel boot file (dmesg.boot):

root on s1# more dmesg.boot
dmesg.boot: No such file or directory
root on s1# pwd
/usr/src/sys/i386/conf
root on s1# cd /var/run
root on s1# more dmesg.boot
Copyright (c) 1992-2005 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993,
1994
The Regents of the University of California. All rights
reserved.
FreeBSD 6.0-RELEASE #2: Fri Mar 10 15:39:52 EST 2006
[EMAIL PROTECTED]:/usr/src/sys/i386/compile/DS9
MPTable: DELL PE 016C 
Timecounter i8254 frequency 1193182 Hz quality 0
CPU: Intel(R) Xeon(TM) CPU 3.00GHz (2992.71-MHz 686-class CPU)
  Origin = GenuineIntel  Id = 0xf43  Stepping = 3

Features=0xbfebfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR
,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SS
E2,SS,HTT,TM,PBE
  Features2=0x641dSSE3,RSVD2,MON,DS_CPL,CNTX-ID,CX16,b14
  AMD Features=0x2010NX,LM
  Hyperthreading: 2 logical CPUs
real memory  = 536608768 (511 MB)
avail memory = 515788800 (491 MB)
ioapic0: Changing APIC ID to 2
ioapic0: Assuming intbase of 0
ioapic1: Changing APIC ID to 3
ioapic1: Assuming intbase of 24
ioapic2: Changing APIC ID to 4
ioapic2: Assuming intbase of 48
ioapic0 Version 2.0 irqs 0-23 on motherboard
ioapic1 Version 2.0 irqs 24-47 on motherboard
ioapic2 Version 2.0 irqs 48-71 on motherboard
npx0: [FAST]
npx0: math processor on motherboard
npx0: INT 16 interface
cpu0 on motherboard
pcib0: MPTable Host-PCI bridge pcibus 0 on motherboard
pci0: PCI bus on pcib0
pcib1: PCI-PCI bridge at device 2.0 on pci0
pci1: PCI bus on pcib1
pcib2: MPTable PCI-PCI bridge at device 0.0 on pci1
pci2: PCI bus on pcib2
mpt0: LSILogic 1030 Ultra4 Adapter port 0xec00-0xecff mem
0xdfdf-0xdfdf,0xdfde-0xdfde irq 26 at device 5.0 o
n pci2
mpt0: [GIANT-LOCKED]
mpt0: MPI Version=1.2.12.0
mpt0: Unhandled Event Notify Frame. Event 0xa.
pcib3: MPTable PCI-PCI bridge at device 0.2 on pci1
pci3: PCI bus on pcib3
pcib4: PCI-PCI bridge at device 4.0 on pci0
pci4: PCI bus on pcib4
pcib5: PCI-PCI bridge at device 5.0 on pci0
pci5: PCI bus on pcib5
pcib6: MPTable PCI-PCI bridge at device 0.0 on pci5
pci6: PCI bus on pcib6
em0: Intel(R) PRO/1000 Network Connection, Version - 2.1.7 port
0xdcc0-0xdcff mem 0xdfae-0xdfaf irq 48 at device 7.0
 on pci6
em0: Ethernet address: 00:14:22:1c:d5:7e
em0:  Speed:N/A  Duplex:N/A
pcib7: MPTable PCI-PCI bridge at device 0.2 on pci5
pci7: PCI bus on pcib7
em1: Intel(R) PRO/1000 Network Connection, Version - 2.1.7 port
0xccc0-0xccff mem 0xdf8e-0xdf8f irq 49 at device 8.0
 on pci7
em1: Ethernet address: 00:14:22:1c:d5:7f
em1:  Speed:N/A