From owner-freebsd-current Tue Dec 3 08:33:41 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id IAA26949 for current-outgoing; Tue, 3 Dec 1996 08:33:41 -0800 (PST) Received: from viking.ucsalf.ac.uk (viking.ucsalf.ac.uk [192.195.1.1]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id IAA26941 for ; Tue, 3 Dec 1996 08:33:32 -0800 (PST) Received: by viking.ucsalf.ac.uk (Smail3.1.29.1 #4) id m0vUxmc-000371C; Tue, 3 Dec 96 16:33 GMT Message-Id: From: mark@plato.salford.ac.uk (Mark Powell) Subject: 2.2-current page fault panics To: freebsd-current@freebsd.org Date: 3 Dec 1996 16:33:16 -0000 X-Gated-To-News-By: news@ucsalf.ac.uk Xref: viking.ucsalf.ac.uk list.freebsd.hackers:10076 list.freebsd.current:6178 Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Been running 2.2-960801-SNAP since in came out with no problems. Wanted to get current so I pulled down the source and applied all the ctm updates as of yesterday. The new kernel now falls over under high disk activity/load. Going back to the 960801-SNAP returns me to a stable system. It's a PCI Pentium 166 with a AHA 7880 on board. Is this trace of the lastest vmcore useful? (kgdb) bt #0 0xf010e323 in boot () #1 0xf010e5e2 in panic () #2 0xf0187bda in trap_fatal () #3 0xf01876c8 in trap_pfault () #4 0xf01873af in trap () #5 0xf0185b97 in pmap_remove_pages () #6 0xf0108073 in exit1 () #7 0xf0107f34 in exit () #8 0xf0187e73 in syscall () #9 0x80a450d in ?? () Cannot access memory at address 0xefbfdcf0. (kgdb) Cheers. -- Mark Powell - Unix Information Officer - Clifford Whitworth Building A.I.S., University of Salford, Salford, Manchester, UK. Tel: +44 161 745 5936 Fax: +44 161 736 3596 Email: mark@salford.ac.uk finger mark@ucsalf.ac.uk (for PGP key) Home Page