From owner-freebsd-mips@freebsd.org Sun Oct 25 12:22:32 2015 Return-Path: Delivered-To: freebsd-mips@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0ED6F84C7 for ; Sun, 25 Oct 2015 12:22:32 +0000 (UTC) (envelope-from lists@opsec.eu) Received: from home.opsec.eu (home.opsec.eu [IPv6:2001:14f8:200::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id BF5B91A1A for ; Sun, 25 Oct 2015 12:22:31 +0000 (UTC) (envelope-from lists@opsec.eu) Received: from pi by home.opsec.eu with local (Exim 4.86 (FreeBSD)) (envelope-from ) id 1ZqKJh-000ICX-Kp for freebsd-mips@freebsd.org; Sun, 25 Oct 2015 13:22:29 +0100 Date: Sun, 25 Oct 2015 13:22:29 +0100 From: Kurt Jaeger To: freebsd-mips@freebsd.org Subject: Edge Router Lite, 11-current and vi dumping core ? Message-ID: <20151025122229.GS19913@home.opsec.eu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-BeenThere: freebsd-mips@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Porting FreeBSD to MIPS List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 25 Oct 2015 12:22:32 -0000 Hi! I built a very recent 11-current to run on the Ubiquity Edge Router Lite, using mkerlimage from http://rtfm.net/FreeBSD/ERL/. If I try to invoke vi via serial console or via remote ssh session, a crash is recorded on the serial console: root@erl:~ # uname -a FreeBSD erl 11.0-CURRENT FreeBSD 11.0-CURRENT #0 r289925M: Sun Oct 25 09:31:34 CET 2015 pi@fc.opsec.eu:/usr/obj/mips.mips64/usr/src/sys/ERL mips root@erl:~ # [invoking vi via SSH on other session] cpuid = 1 Oct 25 12:05:28 erl kernel: BAD_PAGE_FAULT: pid 1326 tid 100056 (vi), uid 0: pc 0x120013480 got a write fault (type 0x3) at 0x161616b98 Oct 25 12:05:28 erl kernel: Trapframe Register Dump: Oct 25 12:05:28 erl kernel: zero: 0 at: 0x7fffffffffffffff v0: 0x161616030 v1: 0xa Oct 25 12:05:28 erl kernel: a0: 0x120080eb8 a1: 0x15 a2: 0x16 a3: 0x120012068 Oct 25 12:05:28 erl kernel: a4: 0x1602ea270 a5: 0x1602ffa00 a6: 0xff a6: 0x16060d000 Oct 25 12:05:28 erl kernel: t0: 0 t1: 0 t2: 0x8 t3: 0x120013458 Oct 25 12:05:28 erl kernel: t8: 0x232 t9: 0x1 s0: 0x120011f10 s1: 0x160616000 Oct 25 12:05:28 erl kernel: s2: 0 s3: 0x16067a000 s4: 0 s5: 0x7fffffeb70 Oct 25 12:05:28 erl kernel: s6: 0x1 s7: 0 k0: 0 k1: 0 Oct 25 12:05:28 erl kernel: gp: 0x120089960 sp: 0x7fffffe838 s8: 0x160616010 ra: 0x120013458 Oct 25 12:05:28 erl kernel: sr: 0x808cb3 mullo: 0x30 mulhi: 0 badvaddr: 0x161616b98 Oct 25 12:05:28 erl kernel: cause: 0xc pc: 0x120013480 Oct 25 12:05:28 erl kernel: Page table info for pc address 0x120013480: pde = 0x9800000005f73000, pte = 0x28000000018fe5a Oct 25 12:05:28 erl kernel: Dumping 4 words starting at pc address 0x120013480: Oct 25 12:05:28 erl kernel: ac430b68 24a50001 14c5fff9 64840008 Oct 25 12:05:28 erl kernel: Page table info for bad address 0x161616b98: pde = 0x98000000050ad000, pte = 0 Any ideas on how I can debug this ? -- pi@opsec.eu +49 171 3101372 5 years to go !