Re: 2.8 crash

[Henning Brauer <lists@bsws.de>]

Am Sonntag,  7. Januar 2001 02:56 schrieb Jim Breton:
> i386, custom kernel, P133 with 32 MB RAM.  OpenBSD 2.8.
>
> The machine crashed last night, but in a strange way -- it was still
> forwarding packets (it is used for NAT, as well as a couple of shell
> logins and SMTP/POP3/SSH) and accepting connections on the listening
> ports, although -- when you would connect to one of these ports, you
> wouldn't get any greeting back from the daemon or anything, it would
> just sit there.

I've seen the same behaviour on a 2.7 nat box a few days before, there i had 
the disk accidently attached to the seconday ide port instead of the primary 
(what IMHO should make no trouble, but anyway). Thanks to a central syslog 
server i could see the last messages the box gave: write errors on the disk. 
I've seen a few corrected soft errors before on this machine. Maybe you have 
the same error here. My troubles went away when I attached the disk to the 
primary port, i think the second one is broken (hardware error, not obsds 
fault).

just for info the dmesg:

OpenBSD 2.7-stable (cr3.ham.bsws.de) #0: Fri Jun  7 03:42:13 CEST 1996
    brahe@cr3:/usr/src/sys/arch/i386/compile/cr3.ham.bsws.de
cpu0: F00F bug workaround installed
cpu0: Intel Pentium/MMX ("GenuineIntel" 586-class) 167 MHz
cpu0: FPU,V86,DE,PSE,TSC,MSR,MCE,CX8,MMX
real mem  = 66695168 (65132K)
avail mem = 59215872 (57828K)
using 839 buffers containing 3436544 bytes (3356K) of memory
mainbus0 (root)
bios0 at mainbus0: AT/286+(5e) BIOS, date 09/30/96
apm0 at bios0: Power Management spec V1.2
apm0: AC on, battery charge unknown
pci0 at mainbus0 bus 0: configuration mode 1 (bios)
pchb0 at pci0 dev 0 function 0 "Intel 82437VX System (TVX)" rev 0x02
pcib0 at pci0 dev 7 function 0 "Intel 82371SB (Triton II) PCI-ISA" rev 0x01
pciide0 at pci0 dev 7 function 1 "Intel 82371SB (Triton II) IDE" rev 0x00: 
DMA, channel 0 wired to compatibility, channel 1 wired to compatibility
wd0 at pciide0 channel 0 drive 0: <QUANTUM FIREBALL_TM1280A>
wd0: can use 32-bit, PIO mode 4, DMA mode 2
wd0: 16-sector PIO, LBA, 1222MB, 2484 cyl, 16 head, 63 sec, 2503872 sectors
pciide0: channel 0 interrupting at irq 14
wd0(pciide0:0:0): using PIO mode 4, DMA mode 2 (using DMA data transfers)
rl0 at pci0 dev 13 function 0 "Realtek 8139" rev 0x10: irq 11 address 
00:00:cb:54:18:64
rlphy0 at rl0 phy 0: RTL internal phy
rl1 at pci0 dev 14 function 0 "Realtek 8139" rev 0x10: irq 10 address 
00:00:e8:88:79:4e
rlphy1 at rl1 phy 0: RTL internal phy
rl2 at pci0 dev 15 function 0 "Realtek 8139" rev 0x10: irq 9 address 
00:00:e8:8d:18:3b
rlphy2 at rl2 phy 0: RTL internal phy
isa0 at pcib0
isadma0 at isa0
pcppi0 at isa0 port 0x61
sysbeep0 at pcppi0
lpt0 at isa0 port 0x378/4 irq 7
npx0 at isa0 port 0xf0/16: using exception 16
pccom0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo
pccom1 at isa0 port 0x2f8/8 irq 3: ns16550a, 16 byte fifo
pcvt: got KEYB_R_RESEND
pcvt: no kbd detected
vt0 at isa0 port 0x60/16 irq 1: ega, mono, 8 scr, unknown kbd
biomask 4000 netmask 4e00 ttymask 4e82
pctr: 586-class performance counters and user-level cycle counter enabled
dkcsum: wd0 matched BIOS disk 80
root on wd0a
rootdev=0x0 rrootdev=0x300 rawdev=0x302
arplookup: unable to enter address for 0.0.0.0
/: optimization changed from TIME to SPACE
/: optimization changed from SPACE to TIME
arplookup: unable to enter address for 0.0.0.0   


-- 

Henning Brauer         |  BS Web Services
Hostmaster BSWS        |  Roedingsmarkt 14
hostmaster@bsws.de     |  20459 Hamburg
www.bsws.de            |  Germany