From owner-freebsd-current Sat Aug 24 8:38:57 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CB00F37B432; Sat, 24 Aug 2002 08:38:26 -0700 (PDT) Received: from vbook.express.ru (vbook.nc.express.ru [212.24.37.35]) by mx1.FreeBSD.org (Postfix) with ESMTP id AB4BC43E4A; Sat, 24 Aug 2002 08:38:16 -0700 (PDT) (envelope-from vova@express.ru) Received: from vova by vbook.express.ru with local (Exim 3.36 #1) id 17icyS-0000m0-00; Sat, 24 Aug 2002 19:37:16 +0400 Subject: Re: Memory corruption in CURRENT From: "Vladimir B. " Grebenschikov To: "Vladimir B. " Grebenschikov Cc: Terry Lambert , Mark Santcroos , Soeren Schmidt , Martin Blapp , Don Lewis , ktsin@acm.org, freebsd-current@FreeBSD.ORG, hackers@FreeBSD.ORG In-Reply-To: <1030100999.888.18.camel@vbook.express.ru> References: <200208220909.g7M99NcS077303@freebsd.dk> <3D64B005.6657A3B5@mindspring.com> <20020822100014.GA17143@ripe.net> <3D64BA1F.B3C8C8E0@mindspring.com> <20020822102553.GA17453@ripe.net> <3D64C9C2.30A37BF8@mindspring.com> <1030100999.888.18.camel@vbook.express.ru> Content-Type: text/plain; charset=KOI8-R Content-Transfer-Encoding: quoted-printable X-Mailer: Ximian Evolution 1.0.7 Date: 24 Aug 2002 19:37:16 +0400 Message-Id: <1030203436.908.27.camel@vbook.express.ru> Mime-Version: 1.0 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG =F7 Fri, 23.08.2002, =D7 15:09, Vladimir B. Grebenschikov =CE=C1=D0=C9=D3= =C1=CC: > =F7 Thu, 22.08.2002, =D7 15:23, Terry Lambert =CE=C1=D0=C9=D3=C1=CC: > > Mark Santcroos wrote: > > > On Thu, Aug 22, 2002 at 03:17:03AM -0700, Terry Lambert wrote: > > > > Mark Santcroos wrote: > > > > > On Thu, Aug 22, 2002 at 02:33:57AM -0700, Terry Lambert wrote: > > > > > > options DISABLE_PSE > > > > > > options DISABLE_PG_G > > > > > > > > > > Coming up next in this theater :-) > > > > > > > > > > btw, how does the report that using the other compiler fixed ever= ything > > > > > for KT fit in? > > >=20 > > > It looks indeed like it is a 'winner'. The buildworld is still runnin= g but > > > getting further already than the previous 10. > >=20 > > Ugh! Wait until it seems to work for a statistically significant > > sample size, and for more than one person before calling it "happy"! > >=20 > > Also, I'm not sure looking at the code whether or not the PG_G is > > truly significant, or just preterbs the workaround. The problem > > I've referred to in my "hunch" here is actually related solely to > > the PSE, but with the recent code reorganization in locore.s, etc., > > it could have become more significant. > >=20 > >=20 > > > > Coincidentally. It's hard to trigger the bug, so it's easy to > > > > work around it accidently. > > >=20 > > > Thats very true indeed. I can take that as a good 'explanation'. > > >=20 > > > I remember you talking about this PSE problems earlier and more often= . Is > > > it fixable? I assume we would like to turn these options back on as t= hey > > > improve performance don't they? > >=20 > > Yes and yes, but it could be pretty ugly. It would be better to > > get more data from people who are seeing the problem. It may be > > that it's just similar symptoms and more than one proot cause, > > etc., so I'm pretty loathe to make any assumptions.=20 >=20 > I have experience problem like this, after successful boot my notebook=20 > (SONY VAIO z505s) can panic in more or less random place under heavy > load, often while gdm login (gnome startup not easy task). >=20 > One of backtraces below, I have more or less stable panic (aprox. 2 of 3 > tries - panic). I don't run buildworld on netebook often. >=20 > I will try DISABLE_PSE and DISABLE_PG_G Yes, with these options, I have no "regular" panics. Just my two cents. > Vladimir B. Grebenschikov > vova@sw.ru, SWsoft, Inc. --=20 Vladimir B. Grebenschikov vova@sw.ru, SWsoft, Inc. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message