Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 8 Jan 2002 12:51:04 +0100
From:      Nils Holland <nils@tisys.org>
To:        freebsd-stable@freebsd.org
Subject:   4.5-PRERELEASE: VIA chases again...
Message-ID:  <20020108125104.A172@tisys.org>

next in thread | raw e-mail | index | archive | help
Hi folks,

I guess that this is slowly getting boring, but it seems as if I have found
one more crash. First of all, Matt and Soren will remember my "famous" NFs
crash. Since Soren's 686B fix has been in RELENG_4, this problem is gone,
as a long test proved. However, there's something new now. Here are the
details:

I just wanted to do a "make release". During that process, my machine
crashed. The first time, the crash occured while it was checking out the
sources from my local (i.e. I'm connected to it via Ethernet) CVS mirror.
When I tried again, it'd check out the sources fine, but crash duwing the
following "make buildworld" process. The *third* time, it crashed right
after the reboot when I tried to rm -R the directory in which I planned to
make the release.

I have tried to reproduce this problem on two other machines, one is KT266A
based and the other uses the MVP3. However, these machines don't seem to be
affected. In the end, it seems as if this is the KT133 / 686B bug again.
Note that I have already tried about *every* setting in the BIOS and
swapped about *every* component in the system. It all makes no difference.

I don't know how well others KT133 / 686B machines are working, but I have
the feeling that Chaintech, my mainboard's manufacturer, did a
really *bad* job in making this board and it's BIOS, and therefore it is
even possible (I guess) that this problem cannot be fixed easily, if at
all. Since my crappy Chaintech board seems to be the only thing that's
affected, I'm at least glad that it doesn't seem that there'ssomething
important broken in 4.5-PRERELEASE.

Anyway, I'd like to present you some information about my latest crash.
Unluckily, these information were not gathered with a debug kernel, but
something is already visible right now: It seems to be a *different* crash
than the one I had in conjunction with NFS:


Script started on Tue Jan  8 12:21:05 2002
root@jodie> gdb -k kernel.0 vmcore.0
This GDB was configured as "i386-unknown-freebsd"...
(no debugging symbols found)...
IdlePTD at phsyical address 0x00386000
initial pcb at physical address 0x002e85a0
panicstr: softdep_lock: locking against myself
panic messages:
---
Fatal trap 12: page fault while in kernel mode
fault virtual address	= 0x38
fault code		= supervisor read, page not present
instruction pointer	= 0x8:0xc01fc645
stack pointer	        = 0x10:0xe07c0bc8
frame pointer	        = 0x10:0xe07c0bd4
code segment		= base 0x0, limit 0xfffff, type 0x1b
			= DPL 0, pres 1, def32 1, gran 1
processor eflags	= interrupt enabled, resume, IOPL = 0
current process		= 35488 (mkdir)
interrupt mask		= bio 
trap number		= 12
panic: page fault

syncing disks... panic: softdep_lock: locking against myself
Uptime: 2h27m12s

dumping to dev #ad/0x20001, offset 1580448
dump ata0: resetting devices .. done
---
#0  0xc0143706 in dumpsys ()
(kgdb) where
#0  0xc0143706 in dumpsys ()
#1  0xc0143527 in boot ()
#2  0xc01438fc in poweroff_wait ()
#3  0xc01fbd6a in acquire_lock ()
#4  0xc01ffde8 in softdep_update_inodeblock ()
#5  0xc01faecd in ffs_update ()
#6  0xc0204801 in ffs_fsync ()
#7  0xc020310f in ffs_sync ()
#8  0xc0172e8f in sync ()
#9  0xc01432da in boot ()
#10 0xc01438fc in poweroff_wait ()
#11 0xc0270232 in trap_fatal ()
#12 0xc026ff05 in trap_pfault ()
#13 0xc026faef in trap ()
#14 0xc01fc645 in pagedep_lookup ()
#15 0xc01fcf29 in softdep_setup_allocdirect ()
#16 0xc01fa70f in ffs_balloc ()
#17 0xc0209a80 in ufs_mkdir ()
#18 0xc020aa19 in ufs_vnoperate ()
#19 0xc0175dbe in mkdir ()
#20 0xc02704dd in syscall2 ()
#21 0xc0264b55 in Xint0x80_syscall ()
#22 0x80482d2 in ?? ()
#23 0x8048135 in ?? ()
(kgdb) quit
root@jodie> exit
exit

As you can see, this time the crash doesn't seem to take place in some part
of the NFS code, but in the UFS/FFS code. Once again, I guess the code is
perfectly fine, but my board sucks. Oh, here's also another
/var/run/dmesg.boot:


Copyright (c) 1992-2002 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 4.5-PRERELEASE #0: Sat Jan  5 11:41:47 CET 2002
    root@poison.ncptiddische.net:/usr/obj/usr/src/sys/JODIE
Timecounter "i8254"  frequency 1193182 Hz
Timecounter "TSC"  frequency 996634421 Hz
CPU: AMD Athlon(tm) processor (996.63-MHz 686-class CPU)
  Origin = "AuthenticAMD"  Id = 0x642  Stepping = 2
  Features=0x183f9ff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR>
  AMD Features=0xc0440000<<b18>,AMIE,DSP,3DNow!>
real memory  = 805240832 (786368K bytes)
avail memory = 779370496 (761104K bytes)
Preloaded elf kernel "kernel" at 0xc0367000.
Pentium Pro MTRR support enabled
Using $PIR table, 8 entries at 0xc00fdba0
npx0: <math processor> on motherboard
npx0: INT 16 interface
pcib0: <Host to PCI bridge> on motherboard
pci0: <PCI bus> on pcib0
pcib1: <VIA 8363 (Apollo KT133) PCI-PCI (AGP) bridge> at device 1.0 on pci0
pci1: <PCI bus> on pcib1
pci1: <ATI Mach64-GM graphics accelerator> at 0.0 irq 11
isab0: <VIA 82C686 PCI-ISA bridge> at device 7.0 on pci0
isa0: <ISA bus> on isab0
atapci0: <VIA 82C686 ATA100 controller> port 0xd000-0xd00f at device 7.1 on pci0
atapci0: Correcting VIA config for southbridge data corruption bug
ata0: at 0x1f0 irq 14 on atapci0
ata1: at 0x170 irq 15 on atapci0
pci0: <VIA 83C572 USB controller> at 7.2 irq 10
pci0: <VIA 83C572 USB controller> at 7.3 irq 10
chip1: <VIA 82C686 ACPI interface> at device 7.4 on pci0
pcm0: <VIA VT82C686A> port 0xe400-0xe403,0xe000-0xe003,0xdc00-0xdcff irq 5 at device 7.5 on pci0
bktr0: <BrookTree 878> mem 0xdc001000-0xdc001fff irq 10 at device 16.0 on pci0
iicbb0: <I2C generic bit-banging driver> on bti2c0
iicbus0: <Philips I2C bus> on iicbb0 master-only
smbus0: <System Management Bus> on bti2c0
bktr0: Hauppauge Model 44354 C221
bktr0: Detected a MSP3415D-B3 at 0x80
bktr0: Hauppauge WinCast/TV, Philips FR1216 PAL FM tuner, msp3400c stereo, remote control.
pci0: <unknown card> (vendor=0x109e, dev=0x0878) at 16.1 irq 10
ed0: <NE2000 PCI Ethernet (RealTek 8029)> port 0xe800-0xe81f irq 11 at device 17.0 on pci0
ed0: address 00:20:18:2f:42:2d, type NE2000 (16 bit) 
orm0: <Option ROMs> at iomem 0xc0000-0xc7fff,0xc8000-0xcbfff on isa0
fdc0: <NEC 72065B or clone> at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0
fdc0: FIFO enabled, 8 bytes threshold
fd0: <1440-KB 3.5" drive> on fdc0 drive 0
atkbdc0: <Keyboard controller (i8042)> at port 0x60,0x64 on isa0
atkbd0: <AT Keyboard> flags 0x1 irq 1 on atkbdc0
kbd0 at atkbd0
psm0: <PS/2 Mouse> irq 12 on atkbdc0
psm0: model Generic PS/2 mouse, device ID 0
vga0: <Generic ISA VGA> at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0
sc0: <System console> at flags 0x100 on isa0
sc0: VGA <16 virtual consoles, flags=0x300>
ppc0: <Parallel port> at port 0x378-0x37f irq 7 on isa0
ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode
ppc0: FIFO with 16/16/8 bytes threshold
ppbus0: IEEE1284 device found /NIBBLE/ECP
Probing for PnP devices on ppbus0:
ppbus0: <HEWLETT-PACKARD DESKJET 930C> MLC,PCL,PML
lpt0: <Printer> on ppbus0
lpt0: Interrupt-driven port
ad0: 57241MB <WDC WD600AB-32CZA0> [116301/16/63] at ata0-master UDMA100
acd0: CDROM <CD-ROM 52X/AKH> at ata1-master using PIO4
acd1: CD-RW <LITE-ON LTR-12101B> at ata1-slave using PIO4
Mounting root from ufs:/dev/ad0s1a


Ok, that's it. I'd be thankful for any hints, but I guess I'm going to have
to wait and track Soren's 686B patch and see if a future update probably
makes my problems go away. I might also try flashing an older version of my
BIOS and see if that helps. Oh my, I guess I'm never going to buy Chaintech
again...

Greetings
Nils

-- 
Nils Holland
Ti Systems - FreeBSD in Tiddische, Germany
http://www.tisys.org * nils@tisys.org

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?20020108125104.A172>