From owner-freebsd-sparc Mon Sep 2 16:43:12 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 0595237B400 for ; Mon, 2 Sep 2002 16:43:09 -0700 (PDT) Received: from k6.locore.ca (k6.locore.ca [198.96.117.170]) by mx1.FreeBSD.org (Postfix) with ESMTP id CA1DC43E65 for ; Mon, 2 Sep 2002 16:43:07 -0700 (PDT) (envelope-from jake@k6.locore.ca) Received: from k6.locore.ca (jake@localhost.locore.ca [127.0.0.1]) by k6.locore.ca (8.12.5/8.12.5) with ESMTP id g82Nmj8a090326; Mon, 2 Sep 2002 19:48:46 -0400 (EDT) (envelope-from jake@k6.locore.ca) Received: (from jake@localhost) by k6.locore.ca (8.12.5/8.12.5/Submit) id g82NmjUg090325; Mon, 2 Sep 2002 19:48:45 -0400 (EDT) Date: Mon, 2 Sep 2002 19:48:45 -0400 From: Jake Burkholder To: marius@alchemy.franken.de Cc: Sten , freebsd-sparc@FreeBSD.ORG Subject: Re: Instability Message-ID: <20020902194845.J67527@locore.ca> References: <20020902145424.I67527@locore.ca> <20020902215033.A16493@newtrinity.default-network.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20020902215033.A16493@newtrinity.default-network.net>; from marius@alchemy.franken.de on Mon, Sep 02, 2002 at 09:50:33PM +0200 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 Apparently, On Mon, Sep 02, 2002 at 09:50:33PM +0200, marius@alchemy.franken.de said words to the effect of; > 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. Did you install screen from a package? I thought that the latest package run (which was a while ago) was after I moved the signal trampoline into libc, but I guess not. I have a fix which restores binary compatibility, you can either wait for that and do a buildworld or rebuild all your installed packages from ports. Sorry about that :-/ Jake To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-sparc" in the body of the message