Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 21 Feb 1995 17:27:41 -0400 (AST)
From:      Peter Howlett <phowlett@mailhub.ASG.unb.ca>
To:        hackers@FreeBSD.org
Subject:   PCNet32 VESA with EISA SCSI
Message-ID:  <Pine.A32.3.91.950221171236.22595A-100000@angus.ASG.unb.ca>

next in thread | raw e-mail | index | archive | help

Howdy,

Actually, I dont know if the subject says it or not. I have
been testing the new Lance PCNet ethernet driver with Paul
Richards. The driver seems to work now on VESA PCNet32 cards
(as well as regular ISA cards according to Paul). I just
tested it over the weekend on a VESA only machine:

486dx2/66 8megs ram
VESA IDE card  
VESA CL5428 video
VESA PCNet32 AM79C965 chipset

This machine works great. 

I also have an EISA/VESA combo board that causes
the machine to page fault whenever I ftp a large file (>50K). The
machine is:

486dx2/66 16megs ram
EISA Buslogic BT747c SCSI
EISA ATI Mach32 Video
and the VESA PCnet card (in the master slot)

The page fault looks like this:

ftp> get ....
Opening binary data connections.....
lnc0: Receive overflow error

Fatal trap 12: page fault while in kernel mode
fault virtual address        = 0xf0545364
fault code                   = supervisor read, page not present
instruction pointer          = 0x8: 0xf015d5ea
code segment                 = base 0x0, limit 0xfffff, type 0x1b
                             = DPL 0, pres 1, def32 1, gran 1
processor eflags             = interrupt enable, resume, IOPL=0
current process              = 124 (cron)
interrupt mask               = net tty bio
panic: page fault

Following is the nm|sort listing aroung the f015d5ea address:

f015ccb4 t common_microtime
f015ccd8 t pentium_microtime
f015cce0 F pmap.o
f015cce0 T _pmap_pte
f015cd64 T _pmap_extract
f015cdf8 T _pmap_pte_vm_page
f015ce30 T _pmap_use_pt
f015ce84 T _pmap_unuse_pt
f015cf14 T _pmap_activate
f015cf5c T _pmap_bootstrap
f015d094 T _pmap_init
f015d164 T _pmap_map
f015d1b4 T _pmap_create
f015d1e8 T _pmap_pinit
f015d290 T _pmap_growkernel
f015d43c T _pmap_destroy
f015d460 T _pmap_release
f015d47c T _pmap_reference
f015d4b4 t _pmap_alloc_pv_entry
f015d574 T _init_pv_entries
f015d5e4 t _get_pt_entry
f015d640 T _pmap_remove_entry
f015d6e8 T _pmap_remove
f015da90 T _pmap_remove_all
f015dc90 T _pmap_protect
f015de28 T _pmap_enter
f015e124 T _pmap_qenter
f015e180 T _pmap_qremove
f015e1b8 T _pmap_kenter
f015e1f4 T _pmap_kremove
f015e210 T _pmap_object_init_pt
f015e5e8 T _pmap_change_wiring
f015e6b0 T _pmap_copy
f015e6b8 T _pmap_kernel
f015e6dc T _pmap_zero_page
f015e744 T _pmap_copy_page
f015e7c4 T _pmap_pageable
f015e7cc T _pmap_page_exists
f015e8b0 T _pmap_testbit
f015eac0 T _pmap_changebit
f015ec44 T _pmap_page_protect
f015edc4 T _pmap_phys_address
f015edd0 T _pmap_is_referenced
f015ef64 T _pmap_is_modified
f015f12c T _pmap_clear_modify
f015f27c T _pmap_clear_reference
f015f3cc T _pmap_copy_on_write
f015f530 t _i386_protection_init
f015f5b4 T _pmap_mapdev
f015f640 F procfs_machdep.o
f015f640 T _procfs_read_regs
f015f660 T _procfs_write_regs
f015f680 T _procfs_read_fpregs
f015f6b0 T _procfs_write_fpregs
f015f6e0 T _procfs_sstep
f015f6fc T _procfs_fix_sstep

I guess this is the vm code. I really have no idea if this is
something that can be fixed or if its my hardware... Anyone have
any ideas?


--------------------------------------------------------------------
Peter Howlett				Atlantic Systems Group
Phone (Home): (506) 454-0479		Federicton, N.B. Canada
E-Mail: Peter@ASG.unb.ca		Phone: (506) 453-3505
http://www.ASG.unb.ca/~phowlett		Fax:   (506) 453-5004



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.A32.3.91.950221171236.22595A-100000>