From owner-freebsd-current Tue Mar 13 17: 3: 5 2001 Delivered-To: freebsd-current@freebsd.org Received: from charger.oldcity.dca.net (charger.oldcity.dca.net [207.245.82.76]) by hub.freebsd.org (Postfix) with ESMTP id 4BBC537B718; Tue, 13 Mar 2001 17:02:59 -0800 (PST) (envelope-from tom@wact.net) Received: from wact.net (216-158-43-107.wlm.dca.net [216.158.43.107]) by charger.oldcity.dca.net (8.9.3/8.9.3/DCANET) with ESMTP id UAA10403; Tue, 13 Mar 2001 20:02:50 -0500 Message-ID: <3AAEC36C.5A7BF97A@wact.net> Date: Tue, 13 Mar 2001 20:03:40 -0500 From: Tom Uffner X-Mailer: Mozilla 4.76 [en] (X11; U; FreeBSD 5.0-CURRENT i386) X-Accept-Language: en, es, de MIME-Version: 1.0 To: John Baldwin Cc: current@FreeBSD.ORG Subject: Re: 5.0-20010304-CURRENT panics during boot on Sony Vaio References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG John Baldwin wrote: > On 05-Mar-01 Tom Uffner wrote: > > John Baldwin wrote: > >> On 04-Mar-01 Tom Uffner wrote: > >> > all of the snapshots since the 24th have exhibited this same or > >> > very similar behavior. > >> Does it happen for snapshots before the 24th? > > no, it does not, at least not for the 5.0-20010210-CURRENT snap. > Can you try cvsupping the src/sys tree one day at a time to see what day > the kernel starts breaking for you? ok, now i'm really confused. i built GENERIC kernels for every day from the 2/10 to 2/25 and none of them panic. the snaps for the 24th and 25th both during boot (only on my Vaio, not my other test systems) could something outside the kernel have changed that made a difference? or could it from building with different options? my /etc/make.conf has "COPTFLAGS= -O -pipe -march=i686". i presume that the snaps were built without any optimization, could this make a difference? -- Tom Uffner tom@wact.net Give a man a fish and you feed him for a day; teach him to use the Net and he won't bother you for weeks. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message