From mboxrd@z Thu Jan 1 00:00:00 1970 From: erik quanstrom Date: Fri, 27 Feb 2009 13:48:31 -0500 To: 9fans@9fans.net Message-ID: <80203e548baaaca958ded36dcf2a66c3@coraid.com> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Subject: [9fans] interesting kernel panic Topicbox-Message-UUID: a9cd87b0-ead4-11e9-9d60-3106f5b1d025 maybe this is a hardware error. maybe it's an obscure bug. it's not immediately clear to me. we have not had any other panics in the last year. the only console message is: Thu Feb 26 15:02:18: panic: newpage Thu Feb 26 15:02:18: panic: newpage ktrace /kernel/path f0108f3d f3c71670 <pc, addr); 635 636 insyscall = up->insyscall; 637 up->insyscall = 1; 638 n = fault(addr, read); >639 if(n < 0){ 640 if(!user){ 641 dumpregs(ureg); 642 panic("fault: 0x%lux\n", addr); 643 } 644 checkpages(); acid: src(0xf019351b); // fixfault+0x121 /sys/src/9/port/fault.c:106 101 102 case SG_BSS: 103 case SG_SHARED: /* Zero fill on demand */ 104 case SG_STACK: 105 if(*pg == 0) { >106 new = newpage(1, &s, addr); 107 if(s == 0) 108 return -1; 109 110 *pg = new; 111 } acid: src(0xf01944cf); // newpage+0x91 /sys/src/9/port/page.c:195 190 191 lock(p); 192 if(p->ref != 0) 193 panic("newpage"); 194 >195 uncachepage(p); 196 p->ref++; 197 p->va = va; 198 p->modref = 0; 199 for(i = 0; i < MAXMACH; i++) 200 p->cachectl[i] = ct; - erik