From owner-freebsd-sparc Mon Sep 2 12:51: 4 2002 Delivered-To: freebsd-sparc@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3BAFE37B400 for ; Mon, 2 Sep 2002 12:51:01 -0700 (PDT) Received: from newtrinity.default-network.net (newtrinity.default-network.net [62.159.128.162]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7D9A243E3B for ; Mon, 2 Sep 2002 12:50:46 -0700 (PDT) (envelope-from corex@newtrinity.default-network.net) Received: from newtrinity.default-network.net (markus@localhost [127.0.0.1]) by newtrinity.default-network.net (8.12.3/8.12.3/DEFAULT-NETWORK.NET) with ESMTP id g82Job4H075010; Mon, 2 Sep 2002 21:50:37 +0200 (CEST) (envelope-from corex@newtrinity.default-network.net) Received: (from corex@localhost) by newtrinity.default-network.net (8.12.3/8.12.3/Submit) id g82JoXiJ075009; Mon, 2 Sep 2002 21:50:33 +0200 (CEST) (envelope-from corex) Date: Mon, 2 Sep 2002 21:50:33 +0200 From: marius@alchemy.franken.de To: Jake Burkholder Cc: Sten , freebsd-sparc@FreeBSD.ORG Subject: Re: Instability Message-ID: <20020902215033.A16493@newtrinity.default-network.net> References: <20020902145424.I67527@locore.ca> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <20020902145424.I67527@locore.ca>; from jake@locore.ca on Mon, Sep 02, 2002 at 02:54:24PM -0400 Sender: owner-freebsd-sparc@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Mon, Sep 02, 2002 at 02:54:24PM -0400, Jake Burkholder wrote: > Apparently, On Mon, Sep 02, 2002 at 11:33:51AM +0200, > Sten said words to the effect of; > > > > > I have been having quite severe stability problems > > with kernels source starting about a week ago, > > I have replaced the hardware ( Ultra 60 ) with > > another which didn't help. > > > > The easiest way of reproducing it for me is rsyncing > > /usr/src from a remote machine. I'll try to get a > > trace. > > > > Just wondering if other ppl have been experiencing this. > > Hmm, I haven't noticed anything on my ultra 60, can you elaborate? > may be the same or another problem, since the recent "Removed support for in-kernel signal code"-changes i get the following panic (copied by hand; no serial console at the moment) on an u60: recursed on non-recursive lock (sleep mutex) process lock@/usr/src/sys/sparc64/sparc64/machdep.c:380 first aquired @/usr/src/sys/kern/subr_trap.c:232 panic:recurse Debugger("panic") Stopped at Debugger+0x1c: ta %xcc,1 may not be limited to u60 hardware, haven't upgraded other ultrasparc hardware to that source-level, yet. most easiest way for me to trigger the panic is to run something under screen, e.g. a `cd / && find .` will do. let me know if i can/shall provide further information. btw, there's a typo in the comment above line 380 in sparc64 machdep.c, "trampoline" is missing the 'p'. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-sparc" in the body of the message