From owner-freebsd-bugs Thu May 2 19:00:04 1996 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id TAA12591 for bugs-outgoing; Thu, 2 May 1996 19:00:04 -0700 (PDT) Received: (from gnats@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id TAA12570 Thu, 2 May 1996 19:00:02 -0700 (PDT) Date: Thu, 2 May 1996 19:00:02 -0700 (PDT) Message-Id: <199605030200.TAA12570@freefall.freebsd.org> To: freebsd-bugs Cc: From: David Greenman Subject: Re: kern/1171: panic: setrunnable Reply-To: David Greenman Sender: owner-bugs@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk The following reply was made to PR kern/1171; it has been noted by GNATS. From: David Greenman To: hsu@clinet.fi Cc: FreeBSD-gnats-submit@freebsd.org Subject: Re: kern/1171: panic: setrunnable Date: Thu, 02 May 1996 18:56:40 -0700 >#35 0xf01c527b in trap (frame={tf_es = 16, tf_ds = 16, tf_edi = -1073741824, > tf_esi = -1, tf_ebp = -266383540, tf_isp = -266383568, > tf_ebx = -240950016, tf_edx = -266065788, tf_ecx = -235599872, > tf_eax = 448, tf_trapno = 12, tf_err = 0, tf_eip = -267313518, > tf_cs = 8, tf_eflags = 66054, tf_esp = -240950016, tf_ss = -1}) > at ../../i386/i386/trap.c:320 >#36 0xf01bda31 in calltrap () >#37 0xf01121c6 in setrunnable (p=0xf1a36500) at ../../kern/kern_synch.c:648 >#38 0xf0111c87 in endtsleep (arg=0xf1a36500) at ../../kern/kern_synch.c:408 >#39 0xf01082cc in softclock () at ../../kern/kern_clock.c:664 >#40 0xf01bed87 in doreti_swi () >#41 0xf01c99c4 in vm_page_zero_idle () at ../../i386/i386/vm_machdep.c:855 >(kgdb) >(kgdb) frame 37 >#37 0xf01121c6 in setrunnable (p=0xf1a36500) at ../../kern/kern_synch.c:648 >648 case SRUN: >(kgdb) list >643 register int s; >644 >645 s = splhigh(); >646 switch (p->p_stat) { >647 case 0: >648 case SRUN: >649 case SZOMB: >650 default: >651 panic("setrunnable"); >652 case SSTOP: >(kgdb) print p >$1 = (struct proc *) 0xf1a36500 >(kgdb) print p->p_stat >$2 = 3 '\003' Given the supplied information, there is no way that a page fault could have occurred at that location unless the kernel text was either corrupted or had one or more memory bit errors. In other words, I think this is a hardware problem, not a software problem. -DG David Greenman Core-team/Principal Architect, The FreeBSD Project