On Sun, May 14, 2006 at 11:04:26PM -0700, Joe Barnett wrote:
> My brand new installation of 3.9 (GENERIC, no patches applied as
> yet) is failing often with similar type messages:
>
> ----- start -----
> uvm_fault(0xd05c2f60, 0xd0dfb000, 0, 3) -> euvm_fault(0xd05c2f60,
> 0xd0dfb000, 0, 3) -> e
> kernel: page fault trap, code-0
> Stopped at uvm_fault+0x28c: incl uvmexp+0xf4
> ddb>
> ----- end -----
>
> "ddb> trace" output is:
>
> ----- start -----
> uvm_fault(d60b9294,1c013000,0,1,3) at uvm_fault+0x28c
> trap() at trap+0x259
> --- trap (number 6) ---
> 0x1c0138cc:
> ddb>
> ----- end -----
>
> "ddb> ps" output is:
>
> ----- start -----
> PID PPID PGRP UID S FLAGS WAIT COMMAND
> *5095 3924 3924 0 7 0x4006 mount
> 3924 1 3924 0 3 0x4086 pause sh
> 12 0 0 0 3 0x100204 crypto_wa crypto
> 11 0 0 0 3 0x100204 aiodoned aiodoned
> 10 0 0 0 3 0x100204 syncer update
> 9 0 0 0 3 0x100204 cleaner cleaner
> 8 0 0 0 3 0x100204 reaper reaper
> 7 0 0 0 3 0x100204 pgdaemon pagedaemon
> 6 0 0 0 3 0x100204 pftm pfpurge
> 5 0 0 0 3 0x100204 usbtsk usbtask
> 4 0 0 0 3 0x100204 usbevt usb0
> 3 0 0 0 3 0x100204 apmev apm0
> 2 0 0 0 3 0x100204 kmalloc kmthread
> 1 0 1 0 3 0x4084 wait init
> 0 -1 0 0 3 0x80204 scheduler swapper
> ddb>
> ----- end -----
>
> This particular output resulted from trace and ps following a crash
> during boot, around the time (various) daemons are loading. By
> various, sometimes the last loaded/attempted is httpd, another time
> it is ntpd, another time it is sshd, etc. This has been tried
> several times.
>
> If the machine does manage to boot, it will die/crash in similar
> fashion, the common element being uvm_fault. Often this will happen
> while trying to update the ports tree or trying to apply the
> sendmail patch, but it can happen at any time.
>
> I usually have vm.swapencrypt.enable=1 in /etc/sysctl.conf, but have
> tried it with default settings as well with the same result. I have
> tried mounting the drives with and without softupdates, again with
> the same results.
The default setting is 1.
>
> This machine was fine (running OpenBSD for several years, the latest
> being 3.8) until Friday when I did the upgrade. Since then I have
> basically swapped out all of the cards, motherboard, memory, power
> supply, even drives. Far as I can tell, the power supplied to the
> machine is OK, and (again, far as I can tell) the power supplies
> themselves are in good working order -- I have had power supplies
> fail before and I keep an extra or two on hand just in case.
>
> I have installed several times and this can happen as soon as the
> first reboot following installation or after some configuration and
> installation of packages has taken place. Currently I was able to
> install the packages I normally use, and the machine started acting
> up again during updating of the ports tree. At this point the
> machine will not fully boot. Following is the dmesg output grabbed
> while booting bsd.rd:
>
> OpenBSD 3.9 (RAMDISK_CD) #1025: Thu Mar 2 02:43:29 MST 2006
> [EMAIL PROTECTED]:/usr/src/sys/arch/i386/compile/RAMDISK_CD
> cpu0: AMD-K6(tm) 3D processor ("AuthenticAMD" 586-class) 401 MHz
> cpu0: FPU,V86,DE,PSE,TSC,MSR,MCE,CX8,PGE,MMX
> real mem = 267952128 (261672K)
> avail mem = 238661632 (233068K)
> using 3296 buffers containing 13500416 bytes (13184K) of memory
> mainbus0 (root)
> bios0 at mainbus0: AT/286+(67) BIOS, date 08/03/99, BIOS32 rev. 0 @
> 0xfb260
> apm0 at bios0: Power Management spec V1.2
> apm0: flags 70102 dobusy 1 doidle 1
> pcibios0 at bios0: rev 2.1 @ 0xf0000/0xb6e8
> pcibios0: PCI IRQ Routing Table rev 1.0 @ 0xfdcf0/144 (7 entries)
> pcibios0: PCI Exclusive IRQs: 10 11 12
> pcibios0: PCI Interrupt Router at 000:07:0 ("VIA VT82C586 ISA" rev 0x00)
> pcibios0: PCI bus #1 is the last bus
> bios0: ROM list: 0xc0000/0x8800
> cpu0 at mainbus0
> pci0 at mainbus0 bus 0: configuration mode 1 (no bios)
> pchb0 at pci0 dev 0 function 0 "VIA VT82C597 PCI" rev 0x04
> ppb0 at pci0 dev 1 function 0 "VIA VT82C598 AGP" rev 0x00
> pci1 at ppb0 bus 1
> vga1 at pci1 dev 0 function 0 "NVIDIA Riva TNT" rev 0x04
> wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation)
> pcib0 at pci0 dev 7 function 0 "VIA VT82C586 ISA" rev 0x47
> pciide0 at pci0 dev 7 function 1 "VIA VT82C571 IDE" rev 0x06: ATA33,
> channel 0 configured to compatibility, channel 1 configured to
> compatibility
> wd0 at pciide0 channel 0 drive 0: <WDC WD136AA>
> wd0: 16-sector PIO, LBA, 12971MB, 26564832 sectors
> atapiscsi0 at pciide0 channel 0 drive 1
> scsibus0 at atapiscsi0: 2 targets
> cd0 at scsibus0 targ 0 lun 0: <ATAPI, 50X CDROM, 3.1B> SCSI0 5/cdrom
> removable
> wd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 2
> cd0(pciide0:0:1): using PIO mode 4, Ultra-DMA mode 2
> wd1 at pciide0 channel 1 drive 0: <WDC WD1600JB-00REA0>
> wd1: 16-sector PIO, LBA48, 152627MB, 312581808 sectors
> wd2 at pciide0 channel 1 drive 1: <Maxtor 6Y080P0>
> wd2: 16-sector PIO, LBA, 78167MB, 160086528 sectors
> wd1(pciide0:1:0): using PIO mode 4, Ultra-DMA mode 2
> wd2(pciide0:1:1): using PIO mode 4, Ultra-DMA mode 2
> uhci0 at pci0 dev 7 function 2 "VIA VT83C572 USB" rev 0x02: irq 10
> usb0 at uhci0: USB revision 1.0
> uhub0 at usb0
> uhub0: VIA UHCI root hub, rev 1.00/1.00, addr 1
> uhub0: 2 ports with 2 removable, self powered
> "VIA VT82C586 Power" rev 0x10 at pci0 dev 7 function 3 not configured
> rl0 at pci0 dev 12 function 0 "Accton MPX 5030/5038" rev 0x10: irq
> 12, address 00:e0:29:54:b5:d4
> rlphy0 at rl0 phy 0: RTL internal PHY
> isa0 at pcib0
> isadma0 at isa0
> pckbc0 at isa0 port 0x60/5
> pckbd0 at pckbc0 (kbd slot)
> pckbc0: using irq 1 for kbd slot
> wskbd0 at pckbd0: console keyboard, using wsdisplay0
> 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
> fdc0 at isa0 port 0x3f0/6 irq 6 drq 2
> fd0 at fdc0 drive 0: 1.44MB 80 cyl, 2 head, 18 sec
> biomask efe5 netmask ffe5 ttymask ffe7
> rd0: fixed, 3800 blocks
> dkcsum: wd0 matches BIOS drive 0x80
> dkcsum: wd1 matches BIOS drive 0x81
> dkcsum: wd2 matches BIOS drive 0x82
> root on rd0a
> rootdev=0x1100 rrootdev=0x2f00 rawdev=0x2f02
>
> The normal processor in this machine is an AMD Athlon or Athlon XP
> (1.2 GHz or such) and 1GB of RAM. The dmesg above reflects a
> different board and memory (also different video card and power
> supply) -- again I have tried to isolate a hardware issue but this
> just keeps failing. There are other machines feeding from the same
> power and they are running well. What else? I have successfully
> installed 3.9 on two other machines and they are running (updated
> and patched) in perfect order.
>
> Has anyone seen this kind of behaviour recently? Possibly there is
> some piece of hardware I am overlooking? Any ideas/advice will be
> appreciated.
>
> Thanks,
>
> Joe
>
>
Just a stab in the dark, because your via chipset makes me suspicious...
[EMAIL PROTECTED]:~$ dmesg | grep VT82C586
pcibios0: PCI Interrupt Router at 000:07:0 ("VIA VT82C586 ISA" rev 0x00)
pcib0 at pci0 dev 7 function 0 "VIA VT82C586 ISA" rev 0x02
This caused lots of trouble to me, I thought memory was dying,
files got overwritten with random junk and the box often stoped with
uvm_fault randomly after minutes/hours/days/weeks.
The solution was to disable pciide.
Tobias
