Date: Wed, 7 Apr 1999 12:06:31 +0400 From: butthead@icb.spb.su To: freebsd-stable@FreeBSD.ORG, dhesi@rahul.net Subject: RE: 3.1-STABLE + specific hardware crashes, 2.2.8 ok on same hard ware Message-ID: <49A0C11850D2D211AD3E00805FCBC53802508C@kovnt.icbank>
next in thread | raw e-mail | index | archive | help
I would like to report that my system crashes too
[uname -a]
FreeBSD cyber.spb.osi.ru 3.1-19990309-STABLE FreeBSD 3.1-19990309-STABLE #1:
Thu Mar 11 16:44:45 GMT 1999
butthead@cyber.spb.osi.ru:/export/src/sys/compile/RUX i386
its 486 box with IDE disk and 8Mb memory...
just crashes once per day or two days.
Also I have / and /usr FS corrupted in some way
fsck says that FILE SYSTEM STILL DIRTY and
asks to rerun dsck again. I did, but messages still the same.
I still can boot and operate this box in multiuser.
crash message is about page fault. Also my /var/log/wtmp and
/var/log/messages are corrupted. they contains garbage with
usual data...
my last dmesg follows
Copyright (c) 1992-1999 FreeBSD Inc.
Copyright (c) 1982, 1986, 1989, 1991, 1993
The Regents of the University of California. All rights reserved.
FreeBSD 3.1-19990309-STABLE #1: Thu Mar 11 16:44:45 GMT 1999
butthead@cyber.spb.osi.ru:/export/src/sys/compile/RUX
Timecounter "i8254" frequency 1193182 Hz
CPU: i486DX (486-class CPU)
real memory = 8388608 (8192K bytes)
avail memory = 6115328 (5972K bytes)
Preloaded elf kernel "kernel" at 0xf0261000.
Probing for devices on the ISA bus:
sc0 on isa
sc0: VGA color <16 virtual consoles, flags=0x0>
ed0 at 0x340-0x35f irq 11 on isa
ed0: address 00:00:b4:6f:d1:28, type NE2000 (16 bit)
atkbdc0 at 0x60-0x6f on motherboard
atkbd0 irq 1 on isa
psm0 not found
sio0 at 0x3f8-0x3ff irq 4 flags 0x10 on isa
sio0: type 16450
sio1 at 0x2f8-0x2ff irq 3 on isa
sio1: type 16450
ppc0 at 0x378 irq 7 on isa
ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode
nlpt0: <generic printer> on ppbus 0
nlpt0: Interrupt-driven port
ppi0: <generic parallel i/o> on ppbus 0
fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa
fd0: 1.2MB 5.25in
fd1: 1.44MB 3.5in
wdc0 at 0x1f0-0x1f7 irq 14 on isa
wdc0: unit 0 (wd0): <SAMSUNG SHD-3212A (APOLLO-4) AD>
wd0: 407MB (833664 sectors), 1002 cyls, 16 heads, 52 S/T, 512 B/S
wdc1 not found at 0x170
vga0 at 0x3b0-0x3df maddr 0xa0000 msize 131072 on isa
npx0 on motherboard
npx0: INT 16 interface
changing root device to wd0s1a
WARNING: / was not properly dismounted
####################
-Dima.
> I am encountering an odd situation. I am doing experiments with two
> machines and two OSs.
>
> Configuration I: ASUS P2B-S m/b, Pentium II 400 MHz, 256M ECC memory
> Configuration Ia: Using onboard SCSI.
> Configuration Ib: Onboard SCSI disabled, Symbios-based
> CSC wide SCSi card added.
>
> Configuration II: FIC PA-2013 m/b, AMD K6-2 380 MHz, 128M ECC memory,
> Symbios-based CSC wide SCSi card.
>
> Both have Netgear FA310TX (Tulip) network cards.
>
> The CSC SCSI card shows up at boot time as
> 'ncr 53c875 fast20 wide scsi'.
>
> The operating systems are:
> - FreeBSD 3.1-STABLE updated via cvsup on April 3rd. (Called 3.1 below.)
> I used the exact same OS disk in all experiments, i.e., moved the
> disk from machine to machine.
>
> - FreeBSD 2.2.8-19990120-SNAP. (Called 2.2.8 below.)
>
> The 'intensive processing' below involves doing the following
> concurrently:
> - using rsync to copy fileystem A to filesystem B, repeated in a loop
> - rm -rf on filesystem B, repeated in a loop
>
> Thus we have lots of file copies and directory creates going on,
> concurrently with rm -rf.
>
> Here is what I find.
>
> 1. Configuration Ia + 3.1: Repeatedly crashes every 1-2 hours
> under intensive processing. Crash dump backtrace is completely
> different each time.
>
> 2. Configuration Ib + 3.1: Crashes the same as above.
>
> 3. Configuration II + 3.1: No crashes under intensive processing.
>
> 4. Configuration Ib + 2.2.8: No crashes under intensive processing.
>
> Let's explore two theories.
>
> Theory A: Bad hardware in Configurations Ia and Ib. This is indicated
> by the fact that the crash dump is different each time.
> However, see item 4 above -- the identical hardware is rock
> solid with 2.2.8.
>
> Theory B: A bug in 3.1. However, the identical OS disk with 3.1 on it
> is rock solid with Configuration II, but shows repeated crashes
> with Configurations Ia and Ib. So, if there is an OS problem,
> it's dependent on the motherboard and CPU -- which seems a bit
> unusual to me.
>
> So, I am puzzled as to why 3.1 crashes with the PII motherboard but not
> with the K6, while 2.2.8 is solid with both motherboards. What sort of
> hardware problem could it be that would be triggered by 3.1?
>
> I didn't save any actual crash dumps, but I can probably regenerate them
> quite easily. I did save the backtraces, and they are all at this URL:
>
> http://www.rahul.net/dhesi/freebsd/crash3/
>
> I would welcome any suggestions as to what other tests to do.
> Regrettably, I do not have any other machine available at this time
> which is identical to Configuration Ia.
> --
> Rahul Dhesi <dhesi@spams.r.us.com>
>
>
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-stable" in the body of the message
>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?49A0C11850D2D211AD3E00805FCBC53802508C>