Hello all,
My server freezed periodically like a log.

I can't understand why. There are no any special software and non

standard core, only packages from the same release.
Server got router role and many people depend on it.
Just freeze.......
Please ask me additional information more than I send now-)
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
~->>dmesg

OpenBSD 4.0 (GENERIC) #1107: Sat Sep 16 19:15:58 MDT 2006

    deraadt@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC

cpu0: Intel(R) Core(TM)2 CPU 6320 @ 1.86GHz ("GenuineIntel" 686-class) 1.87 GHz

cpu0: FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,MWAIT,DS-CPL,VMX,EST,TM2,CX16

cpu0: unknown Core FSB_FREQ value 0 (0x41c80000)

cpu0: EST: unknown system bus clock

real mem  = 2128408576 (2078524K)

avail mem = 1933398016 (1888084K)

using 4256 buffers containing 106524672 bytes (104028K) of memory

mainbus0 (root)

bios0 at mainbus0: AT/286+(00) BIOS, date 07/16/06, SMBIOS rev. 2.4 @ 0xe4390 (35 entries)

bios0: Intel Corporation DG965WH

apm0 at bios0: Power Management spec V1.2

apm0: battery life expectancy 0%

apm0: AC off, battery charge unknown, estimated 0:00 hours

apm0: flags 30102 dobusy 0 doidle 1

pcibios at bios0 function 0x1a not configured

bios0: ROM list: 0xc0000/0xee00!

cpu0 at mainbus0

pci0 at mainbus0 bus 0: configuration mode 1 (no bios)

pchb0 at pci0 dev 0 function 0 vendor "Intel", unknown product 0x29a0 rev 0x02

ppb0 at pci0 dev 1 function 0 vendor "Intel", unknown product 0x29a1 rev 0x02

pci1 at ppb0 bus 1

vga1 at pci1 dev 0 function 0 "NVIDIA GeForce 6600" rev 0xa2

wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation)

wsdisplay0: screen 1-5 added (80x25, vt100 emulation)

vendor "Intel", unknown product 0x29a4 (class communications subclass miscellaneous, rev 0x02) at pci0 dev 3 function 0 not configured

uhci0 at pci0 dev 26 function 0 "Intel 82801H USB" rev 0x02: irq 11

usb0 at u...
[ message continues ]

It's probably totally unrelated, but I once managed to freeze an

OpenBSD box after attempting to make it automagically back up stuff to

a Windows Server 2003 box. In my case, I had installed sharity-light

(a package allowing you to access CIFS/SMB shares) and I had tried to

tell it to mount the CIFS/SMB share at some mountpoint -- this is when

it froze. It turned out that pf (which I had running on the OpenBSD

box) blocked some port that was needed for proper communication

between sharity-light and Windows Server 2003. I could only

troubleshoot by first ssh-ing into the OpenBSD box, then making the

mount attempt from the actual local keyboard/monitor of the OpenBSD

box (where things duly froze) and then using the preexisting ssh

session to troubleshoot and look at what was happening with tcpdump(8)

(cf. http://www.openbsd.org/faq/pf/logging.html ). If I didn't have a

preexisting ssh console open when making the mount attempt, then I

couldn't ssh into the box anymore from the moment of it freezing

(which meant there was no way to stop the madness, not even with a

local Ctrl+C; in that case I had to power cycle the machine). But with

a preexisting ssh session un-freezing the OpenBSD box was as simple as

punching a big hole into pf.conf (or disabling pf).
Again, you don't seem to be using sharity-light (at least it's not in

your below package list), but I thought I'd tell ya anyway; maybe

something along these lines might help you or a future reader of the

archives. For the record, my above problems happened with OpenBSD 3.9

-release/i386 and the appropriate sharity-light package.
cheerio,

[snip]
Hello Dmitry,
You just want to ask on misc@, not bugs@.
If this system worked and is now freezing, I think the first thing I'd

do is get the memory tester at memtest86.com and run that for 24

hours.
--STeve Andre'

Sounds similar to what can happen with amd64-on-i386 before the

changes for PAE were reverted just before 4.1.
Try 4.1 or newer.

Hi!
It's a very strange but i have same problem with my HP DL 140. running

i386 OS.

Once per week it just freezes and thats all, nothing in logs. It freezes

also when it's idling.

Strange is taht, i can ping it still, but nothing more, noone service is

responding.
DMESG follows
OpenBSD 4.1 (WWW) #0: Thu Mar 31 04:10:45 EEST 2005

    root@www.dtg.lv:/usr/sys/arch/i386/compile/WWW

cpu0: Intel(R) Xeon(R) CPU 5130 @ 2.00GHz ("GenuineIntel" 686-class) 2 GHz

cpu0:

FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,MWAIT,DS-CPL,VMX,TM2,CX16,xT

PR

real mem  = 2146054144 (2095756K)

avail mem = 1952407552 (1906648K)

using 4278 buffers containing 107425792 bytes (104908K) of memory

mainbus0 (root)

bios0 at mainbus0: AT/286+ BIOS, date 12/31/99, BIOS32 rev. 0 @ 0xfd361,

SMBIOS rev. 2.31 @ 0xdc010 (57 entries)

bios0: HP ProLiant DL140 G3

apm0 at bios0: Power Management spec V1.2

apm0: AC on, battery charge unknown

apm0: flags 30102 dobusy 0 doidle 1

pcibios0 at bios0: rev 2.1 @ 0xfd360/0xca0

pcibios0: PCI IRQ Routing Table rev 1.0 @ 0xfdde0/512 (30 entries)

pcibios0: PCI Interrupt Router at 000:31:0 ("Intel 82371FB ISA" rev 0x00)

pcibios0: PCI bus #16 is the last bus

bios0: ROM list: 0xc0000/0x8000 0xc8000/0x1000 0xc9000/0x1600

0xca800/0x1600 0xdc000/0x4000!

acpi at mainbus0 not configured

cpu0 at mainbus0

pci0 at mainbus0 bus 0: configuration mode 1 (no bios)

pchb0 at pci0 dev 0 function 0 "Intel 5000X Host" rev 0x31

ppb0 at pci0 dev 2 function 0 "Intel 5000 PCIE" rev 0x31

pci1 at ppb0 bus 1

ppb1 at pci1 dev 0 function 0 "Intel 6321ESB PCIE" rev 0x01

pci2 at ppb1 bus 2

ppb2 at pci2 dev 0 function 0 "Intel 6321ESB PCIE" rev 0x01

pci3 at ppb2 bus 3

ppb3 at pci1 dev 0 function 3 "Intel 6321ESB PCIE-PCIX" rev 0x01

pci4 at ppb3 bus 5

ppb4 at pci0 dev 3 function 0 "Intel 5000 PCIE" rev 0x31

pci5 at ppb4 bus 6

ppb5 at pci0 dev 4 function 0 vendor "Intel", unknown product 0x25fa rev

0x31

pci6 at ppb5 bu...
[ message continues ]

How idle is idling? Have you any processes which can explode in

RAM usage or massive forks? I saw once a system run out of mem,

with no swap space exhibiting the same beviour. I could imagine

(disclaimer: _didn't_ see that one) a system behave similiar after

not being aber to fork anymore.
--knitti

When it freezes, what's running? (ps aux/top will give you an idea).

When it freezes, who is it talking to? What do you run on this system?

Have you checked /var/logs for anything relevant? If it's a server, is

it maybe getting overloaded? Maybe your hardware is flakey (a dmesg

from just before the crash would be nice.. try rebooting and getting

the dmesg early on (single user?) before the previous one it gets

cleared and looking for errors.
-Nick