Re: uvm_fault on Asus M2V-MX
Just for the record, I've been able to obtain a stable bios configuration. See the dmesg output below. I've realized that the problems I've been experiencing (uvm_fault previously, and strange unexpected reboots during boot-ups recently) are related with the audio configuration in bios settings. If I disable the audio (which is totally useless in my case), the system becomes unstable. So I left it enabled, and now everything seems fine and quite stable. Thanks for the replies, OpenBSD 4.1 (GENERIC.MP) #1152: Sat Mar 10 19:22:57 MST 2007 [EMAIL PROTECTED]:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 1039446016 (1015084K) avail mem = 878047232 (857468K) using 22937 buffers containing 104153088 bytes (101712K) of memory mainbus0 (root) bios0 at mainbus0: SMBIOS rev. 2.3 @ 0xf0740 (51 entries) bios0: ASUSTeK Computer INC. M2V-MX acpi at mainbus0 not configured mainbus0: Intel MP Specification (Version 1.1) cpu0 at mainbus0: apid 0 (boot processor) cpu0: AMD Athlon(tm) 64 X2 Dual Core Processor 4200+, 2200.29 MHz cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,CX16,NXE,MMXX,FFXSR,LONG,3DNOW2,3DNOW cpu0: 64KB 64b/line 2-way I-cache, 64KB 64b/line 2-way D-cache, 512KB 64b/line 16-way L2 cache cpu0: ITLB 32 4KB entries fully associative, 8 4MB entries fully associative cpu0: DTLB 32 4KB entries fully associative, 8 4MB entries fully associative cpu0: apic clock running at 199MHz cpu1 at mainbus0: apid 1 (application processor) cpu1: AMD Athlon(tm) 64 X2 Dual Core Processor 4200+, 2200.00 MHz cpu1: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,CX16,NXE,MMXX,FFXSR,LONG,3DNOW2,3DNOW cpu1: 64KB 64b/line 2-way I-cache, 64KB 64b/line 2-way D-cache, 512KB 64b/line 16-way L2 cache cpu1: ITLB 32 4KB entries fully associative, 8 4MB entries fully associative cpu1: DTLB 32 4KB entries fully associative, 8 4MB entries fully associative mpbios: bus 0 is type PCI mpbios: bus 1 is type PCI mpbios: bus 2 is type PCI mpbios: bus 3 is type PCI mpbios: bus 4 is type PCI mpbios: bus 5 is type PCI mpbios: bus 6 is type ISA ioapic0 at mainbus0 apid 2 pa 0xfec0, version 3, 24 pins ioapic1 at mainbus0 apid 3 pa 0xfecc, version 3, 24 pins pci0 at mainbus0 bus 0: configuration mode 1 pchb0 at pci0 dev 0 function 0 VIA K8M890 Host rev 0x00 pchb1 at pci0 dev 0 function 1 VIA K8M890 Host rev 0x00 pchb2 at pci0 dev 0 function 2 VIA K8M890 Host rev 0x00 pchb3 at pci0 dev 0 function 3 VIA K8M890 Host rev 0x00 pchb4 at pci0 dev 0 function 4 VIA K8M890 Host rev 0x00 VIA K8M890 IOAPIC rev 0x00 at pci0 dev 0 function 5 not configured pchb5 at pci0 dev 0 function 6 VIA K8M890 Host rev 0x00 pchb6 at pci0 dev 0 function 7 VIA K8M890 Host rev 0x00 ppb0 at pci0 dev 1 function 0 VIA K8HTB AGP rev 0x00 pci1 at ppb0 bus 1 vga1 at pci1 dev 0 function 0 VIA DeltaChrome Video rev 0x11 wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation) wsdisplay0: screen 1-5 added (80x25, vt100 emulation) ppb1 at pci0 dev 2 function 0 VIA K8T890 PCI-PCI rev 0x00 pci2 at ppb1 bus 2 ppb2 at pci0 dev 3 function 0 VIA K8T890 PCI-PCI rev 0x00 pci3 at ppb2 bus 3 pciide0 at pci0 dev 15 function 0 VIA VT8237A SATA rev 0x80: DMA pciide0: using apic 2 int 21 (irq 5) for native-PCI interrupt wd0 at pciide0 channel 0 drive 0: WDC WD2500JS-22NCB1 wd0: 16-sector PIO, LBA48, 238475MB, 488397168 sectors wd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 5 pciide1 at pci0 dev 15 function 1 VIA VT82C571 IDE rev 0x07: DMA, channel 0 configured to compatibility, channel 1 configured to compatibility pciide1: channel 0 disabled (no drives) pciide1: channel 1 disabled (no drives) pcib0 at pci0 dev 17 function 0 VIA VT8237A ISA rev 0x00 pchb7 at pci0 dev 17 function 7 VIA VT8251 VLINK rev 0x00 ppb3 at pci0 dev 19 function 0 VIA VT8237A PCI-PCI rev 0x00 pci4 at ppb3 bus 4 azalia0 at pci4 dev 1 function 0 VIA HD Audio rev 0x10: apic 2 int 17 (irq 5) azalia0: host: High Definition Audio rev. 1.0 azalia0: codec: 0x04x/0x10ec (rev. 0.2), HDA version 1.0 audio0 at azalia0 ppb4 at pci0 dev 19 function 1 VIA VT8237A PCI-PCI rev 0x00 pci5 at ppb4 bus 5 vr0 at pci5 dev 7 function 0 VIA VT6105 RhineIII rev 0x86: apic 2 int 17 (irq 5), address 00:08:54:3c:b4:00 ukphy0 at vr0 phy 1: Generic IEEE 802.3u media interface, rev. 4: OUI 0x004063, model 0x0034 rl0 at pci5 dev 9 function 0 Realtek 8139 rev 0x10: apic 2 int 20 (irq 3), address 00:1b:fc:1b:34:fe rlphy0 at rl0 phy 0: RTL internal PHY pchb8 at pci0 dev 24 function 0 AMD AMD64 HyperTransport rev 0x00 pchb9 at pci0 dev 24 function 1 AMD AMD64 Address Map rev 0x00 pchb10 at pci0 dev 24 function 2 AMD AMD64 DRAM Cfg rev 0x00 pchb11 at pci0 dev 24 function 3 AMD AMD64 Misc Cfg rev 0x00 isa0 at pcib0 isadma0 at isa0 com0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo pckbc0 at isa0 port 0x60/5 pckbd0 at pckbc0 (kbd slot) pckbc0: using irq 1 for kbd slot wskbd0 at pckbd0: console
Re: uvm_fault on Asus M2V-MX
Le 12 ao{t 07 ` 02:18, Soner Tari a icrit :
Today I was trying to install OpenBSD/amd64 4.1 GENERIC on a system
with
the following motherboard:
http://www.asus.com/products4.aspx?
modelmenu=2model=1418l1=3l2=101l3=324l4=0
But during installation I got the following blue lines (which I've
noted
on a piece of paper by hand):
uvm_fault (0xfe80 0a2de810, 0x7f8000267000, 0, 1) - e
fatal page fault in supervisor mode
trap type 6 code 0 rip 802540a7 cs 8 vflags 10216 cr2
7f8000267fb0 cpl1 0 rsp 800067015c80
syncing discs ...done
At which time system halts, or becomes unresponsive. (Actually, this
error occurs during my custom install script, in site41.tgz, after
usual
OpenBSD installation finishes.)
I was suspicious about pciide, but VIA 8237A is in the supported
hardware list.
So I've installed OpenBSD on the same HD, but now on another hardware,
then inserted the HD back into this system again, but after a
couple of
services start, I got another uvm_fault error (it's similar but not
the
same, if I recall correctly), and the system hangs.
Some of the other parts are: Athlon64 4200+ X2, Kingston 1GB RAM, WD
250GB SATA2 HD.
I've disabled many options in the bios, but nothing changed. If I
cannot
find a solution, the board will be returned.
Does anybody else use this motherboard too? Do you have any
problems? If
you had a similar issue, how did you fix it, any special bios
settings?
What could be the source of the uvm_fault error: motherboard, RAM, or
even the processor itself?
Otherwise I have installed OpenBSD with my custom script on other
amd64
hardware without major problems.
I would appreciate any help.
Maybe this is due to bad memory ? Test with memtest86+:
http://www.memtest.org
You should try the snapshots to see if the problem has been fixed and
will be
fixed for 4.2.
You could also try with acpi enabled and/or GENERIC.MP.
To enable acpi: at the boot prompt, type boot -c, then:
enable acpi
enable acpiec
quit
and the kernel will boot with acpi.
To boot the MULTIPROCESSOR kernel, boot bsd.mp (and you can enable acpi
on this one too).
Pierre Riteau
Re: uvm_fault on Asus M2V-MX
On Sun, Aug 12, 2007 at 03:18:41AM +0300, Soner Tari wrote: Today I was trying to install OpenBSD/amd64 4.1 GENERIC on a system with the following motherboard: http://www.asus.com/products4.aspx?modelmenu=2model=1418l1=3l2=101l3=324l4=0 But during installation I got the following blue lines (which I've noted on a piece of paper by hand): uvm_fault (0xfe80 0a2de810, 0x7f8000267000, 0, 1) - e fatal page fault in supervisor mode trap type 6 code 0 rip 802540a7 cs 8 vflags 10216 cr2 7f8000267fb0 cpl1 0 rsp 800067015c80 syncing discs ...done At which time system halts, or becomes unresponsive. (Actually, this error occurs during my custom install script, in site41.tgz, after usual OpenBSD installation finishes.) Where in the installation? Try running it with sh -x, or #!/bin/sh -x (I'd try what Pierre proposed first, unless your script does odd things - tweaking the write cache on the disks, or somesuch.) Joachim -- TFMotD: ym (4) - Yamaha OPL3-SAx audio device
Re: uvm_fault on Asus M2V-MX
I actually only add some packages in install.site script, during my 3-4 trials I got uvm_fault error in one of the following lines: pkg_add php5-mysql-5.1.6p1.tgz 21 | tee -a $LOG_FILE pkg_add php5-pear-5.1.6p0.tgz 21 | tee -a $LOG_FILE /usr/local/sbin/phpxs -s 21 | tee -a $LOG_FILE /usr/local/sbin/phpxs -a mysql 21 | tee -a $LOG_FILE I'll do what Pierre suggested first thing in the morning (the system is at workplace). Probably faulty RAM theory can explain the fact that I was getting this error almost exactly on the same lines above (i.e. shared memory usage reaches the same faulty RAM location around php5 install, a wild guess...). On Sun, 2007-08-12 at 21:35 +0200, Joachim Schipper wrote: Where in the installation? Try running it with sh -x, or #!/bin/sh -x (I'd try what Pierre proposed first, unless your script does odd things - tweaking the write cache on the disks, or somesuch.)
uvm_fault on Asus M2V-MX
Today I was trying to install OpenBSD/amd64 4.1 GENERIC on a system with the following motherboard: http://www.asus.com/products4.aspx?modelmenu=2model=1418l1=3l2=101l3=324l4=0 But during installation I got the following blue lines (which I've noted on a piece of paper by hand): uvm_fault (0xfe80 0a2de810, 0x7f8000267000, 0, 1) - e fatal page fault in supervisor mode trap type 6 code 0 rip 802540a7 cs 8 vflags 10216 cr2 7f8000267fb0 cpl1 0 rsp 800067015c80 syncing discs ...done At which time system halts, or becomes unresponsive. (Actually, this error occurs during my custom install script, in site41.tgz, after usual OpenBSD installation finishes.) I was suspicious about pciide, but VIA 8237A is in the supported hardware list. So I've installed OpenBSD on the same HD, but now on another hardware, then inserted the HD back into this system again, but after a couple of services start, I got another uvm_fault error (it's similar but not the same, if I recall correctly), and the system hangs. Some of the other parts are: Athlon64 4200+ X2, Kingston 1GB RAM, WD 250GB SATA2 HD. I've disabled many options in the bios, but nothing changed. If I cannot find a solution, the board will be returned. Does anybody else use this motherboard too? Do you have any problems? If you had a similar issue, how did you fix it, any special bios settings? What could be the source of the uvm_fault error: motherboard, RAM, or even the processor itself? Otherwise I have installed OpenBSD with my custom script on other amd64 hardware without major problems. I would appreciate any help.
