Subject: port-i386/17749: machine faults when compiling with low memory
To: None <gnats-bugs@gnats.netbsd.org>
From: None <suga@netbsd.com.br>
List: netbsd-bugs
Date: 07/29/2002 01:02:57
>Number:         17749
>Category:       port-i386
>Synopsis:       Low memory machine locks when compiling
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    port-i386-maintainer
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Sun Jul 28 21:04:01 PDT 2002
>Closed-Date:
>Last-Modified:
>Originator:     
>Release:        NetBSD 1.6_BETA4 (200207240000 snapshot)
>Organization:
	
>Environment:
	
	
System: NetBSD servidor 1.6_BETA4 NetBSD 1.6_BETA4 (GENERIC) #0: Mon Jul 15 21:02:08 UTC 2002 autobuild@tgm.daemon.org:/autobuild/i386/OBJ/autobuild/src/sys/arch/i386/compile/GENERIC i386
Architecture: i386
Machine: i386

NetBSD 1.6_BETA4 (GENERIC) #0: Mon Jul 15 21:02:08 UTC 2002                                                           
    autobuild@tgm.daemon.org:/autobuild/i386/OBJ/autobuild/src/sys/arch/i386/compile/GENERIC
    cpu0: Intel 486DX4 (486-class)
    cpu0: features 3<FPU,VME>
    total memory = 13436 KB
    avail memory = 6012 KB
    using 193 buffers containing 772 KB of memory
    RTC BIOS diagnostic error 20<config_unit>
    BIOS32 rev. 0 found at 0xf6f20
    mainbus0 (root)
    Warning: broken PCI-Host bridge detected; disabling memory-mapped access
    pci0 at mainbus0 bus 0: configuration mode 1
    pci0: i/o space enabled
    ex0 at pci0 dev 3 function 0: 3Com 3c905C-TX 10/100 Ethernet with mngmt (rev. 0x

    78)
    ex0: interrupting at irq 9
    ex0: MAC address 00:01:03:d1:b9:af
    exphy0 at ex0 phy 24: 3Com internal media interface
    exphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
    pchb0 at pci0 dev 5 function 0
    pchb0: Silicon Integrated System 85C496 (rev. 0x31)
    ex1 at pci0 dev 13 function 0: 3Com 3c905-TX 10/100 Ethernet (rev. 0x0)
    ex1: interrupting at irq 10
    ex1: MAC address 00:60:08:b0:4c:e4
    nsphy0 at ex1 phy 24: DP83840 10/100 media interface, rev. 1
    nsphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
    isa0 at mainbus0
    com0 at isa0 port 0x3f8-0x3ff irq 4: ns16550a, working fifo
    com0: console
    pckbc0 at isa0 port 0x60-0x64
    wdc0 at isa0 port 0x1f0-0x1f7 irq 14
    wd0 at wdc0 channel 0 drive 0: <FUJITSU MPD3108AT>
    wd0: drive supports 16-sector PIO transfers, LBA addressing
    wd0: 10300 MB, 16383 cyl, 16 head, 63 sec, 512 bytes/sect x 21095424 sectors
    wd0: drive supports PIO mode 4, DMA mode 2, Ultra-DMA mode 4 (Ultra/66)
    wdc1 at isa0 port 0x170-0x177 irq 15
    pcppi0 at isa0 port 0x61
    midi0 at pcppi0: PC speaker
    sysbeep0 at pcppi0
    isapnp0 at isa0 port 0x279: ISA Plug 'n Play device support
    npx0 at isa0 port 0xf0-0xff: using exception 16
    fdc0 at isa0 port 0x3f0-0x3f7 irq 6 drq 2
    fd0 at fdc0 drive 0: 1.44MB, 80 cyl, 2 head, 18 sec
    isapnp0: no ISA Plug 'n Play devices found
    biomask f9ef netmask ffef ttymask ffef
    Kernelized RAIDframe activated
    boot device: wd0
    root on wd0a dumps on wd0b
    root file system type: ffs
    in6_ifattach: bridge0 is not multicast capable, IPv6 not enabled
    in6_ifattach: bridge0 is not multicast capable, IPv6 not enabled

>Description:

The machine is a 486 with 16mb running the generic kernel.
I was compiling a new, leaner kernel. The machine stopped and I got this
backtrace by using ddb on a serial console.

m_freem(100,c3151000,0,c07cb000,c07fd1c0) at m_freem+0x27
m_freem(c08a2d00,c082d000,c3c62c94,c0179910,c0646120) at m_freem+0x49
ex_intr(c07fc000) at ex_intr+0x193
Xintr10() at Xintr10+0x82
--- interrupt ---
idle(c3c493a0,c07baf88,c3c62d70,c02b5824) at idle+0x1b
bpendtsleep(c08a8680,11,c04ed7fa,0,0,c3c62f34,100000,c036293d) at bpendtsleep
biowait(c08a8680,2,3,c0691ba0,c07a6154) at biowait+0x34
uvm_swap_io(c3c62e08,6d6,1,100000,52b) at uvm_swap_io+0x16d
uvm_swap_get(c07a6154,6d6,2,c03562c2,c3bd4570) at uvm_swap_get+0x38
uvmfault_anonget(c3c62f34,c3c4584c,c3bd4570,8) at uvmfault_anonget+0x19f
uvm_fault(c3b72a48,84a7000,0,1,435) at uvm_fault+0x736
trap() at trap+0x4d4
--- trap (number 6) ---
 0x8053fa4:

>How-To-Repeat:
	Don't know. Does not seem to be a hardware problem.
>Fix:
	
>Release-Note:
>Audit-Trail:
>Unformatted:
 	<Please check tHat the above is correct for the bug being reported,>