From owner-freebsd-mips@FreeBSD.ORG Thu Aug 28 08:16:35 2014 Return-Path: Delivered-To: freebsd-mips@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id A712569E; Thu, 28 Aug 2014 08:16:35 +0000 (UTC) Received: from mail-vc0-x22e.google.com (mail-vc0-x22e.google.com [IPv6:2607:f8b0:400c:c03::22e]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 57C4F1037; Thu, 28 Aug 2014 08:16:35 +0000 (UTC) Received: by mail-vc0-f174.google.com with SMTP id hy4so425929vcb.33 for ; Thu, 28 Aug 2014 01:16:34 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:date:message-id:subject:from:to:content-type; bh=qbEqazbud8ayT637Rd2kvOK0MBty+dPcO4z+fg89TJM=; b=A+xSk5tJuug/+9ZOvZRT2bJnaX/BCKkUvjv5itHbUybjgsKotmQtaIrT3UnrlD6lkV GqLSQnCzrDn9WIg8b91gRlOVXyVcqQWoMj+/Nr/TO1oSmjH6CI0k5q34Ee8xafzR9omL z7uCZO5R9GLPYXopMn5/8bmjr5aXNT3kdifRvg2ec1LQnz4cARLBREY28Gi3IaWWhxzU hk0S9I1JoW3vWlSrx7nQG8JFCZbt1ebipCL9HmPLkqk4ziuPPbqgRiL2w1fzna9RDbjj mt6lxwnJj8EftM4z7Sf/hvOb7tu21iM+dw8Rs5/Oju/R5nb5CIB1OHZjG6+yRNY5At1X S7Mw== MIME-Version: 1.0 X-Received: by 10.52.135.133 with SMTP id ps5mr482172vdb.33.1409213794395; Thu, 28 Aug 2014 01:16:34 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.220.84.137 with HTTP; Thu, 28 Aug 2014 01:16:34 -0700 (PDT) Date: Thu, 28 Aug 2014 01:16:34 -0700 X-Google-Sender-Auth: W6U6igxtOC73l-COPEiecYokXSc Message-ID: Subject: August 25 HEAD on MIPS32 (routerstation pro) started throwing issues From: Adrian Chadd To: "freebsd-mips@freebsd.org" , Alan Cox Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-mips@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Porting FreeBSD to MIPS List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Aug 2014 08:16:35 -0000 Hi! I just updated a test AP at home to the latest -HEAD ,and here's what I was greeted with: Aug 28 08:07:57 init: login_getclass: unknown class 'daemon' BAD_PAGE_FAULT: pid 27 tid 100045 (mount), uid 0: pc 0x40514dd0 got a read fault (type 0x2) at 0x4040011c Trapframe Register Dump: zero: 0 at: 0x7fffffff v0: 0 v1: 0x404000fc a0: 0x54 a1: 0x40400000 a2: 0 a3: 0x1 t0: 0 t1: 0x40c0300c t2: 0x40800168 t3: 0x2f t4: 0x40c00030 t5: 0 t6: 0x748 t7: 0x402c70 t8: 0x13 t9: 0x40514d58 s0: 0x3 s1: 0x40418798 s2: 0 s3: 0x404ec4 s4: 0x40418798 s5: 0x40418798 s6: 0 s7: 0 k0: 0 k1: 0 gp: 0x405ec910 sp: 0x7ffee348 s8: 0 ra: 0x4051534c sr: 0xfc13 mullo: 0x6719 mulhi: 0xc badvaddr: 0x4040011c cause: 0x8 pc: 0x40514dd0 Page table info for pc address 0x40514dd0: pde = 0x813da000, pte = 0xa00569da Dumping 4 words starting at pc address 0x40514dd0: 8c700020 32030ff0 00032102 240300ff Page table info for bad address 0x4040011c: pde = 0x813da000, pte = 0 pid 27 (mount), uid 0: exited on signal 11 BAD_PAGE_FAULT: pid 32 tid 100045 (mount), uid 0: pc 0x40514dd0 got a read fault (type 0x2) at 0x4040011c Trapframe Register Dump: zero: 0 at: 0x7fffffff v0: 0 v1: 0x404000fc a0: 0x54 a1: 0x40400000 a2: 0 a3: 0x1 t0: 0 t1: 0x40c0300c t2: 0x40800168 t3: 0x2f t4: 0x40c00030 t5: 0 t6: 0x748 t7: 0x402c70 t8: 0x13 t9: 0x40514d58 s0: 0x3 s1: 0x40418798 s2: 0 s3: 0x404ec4 s4: 0x40418798 s5: 0x40418798 s6: 0 s7: 0 k0: 0 k1: 0 gp: 0x405ec910 sp: 0x7ffee348 s8: 0 ra: 0x4051534c sr: 0xfc13 mullo: 0x6719 mulhi: 0xc badvaddr: 0x4040011c cause: 0x8 pc: 0x40514dd0 Page table info for pc address 0x40514dd0: pde = 0x813d8000, pte = 0xa00569da Dumping 4 words starting at pc address 0x40514dd0: 8c700020 32030ff0 00032102 240300ff Page table info for bad address 0x4040011c: pde = 0x813d8000, pte = 0 If I run my startup script commands manually then there's a 50% chance it'll work and a 50% chance the above occurs. Does anyone have any ideas? Alan, is there anything recent in the pmap/VM code churn that may have caused this? -a