Date: Wed, 6 Aug 2003 10:07:29 -0700 From: Marcel Moolenaar <marcel@xcllnt.net> To: Andrew Gallatin <gallatin@cs.duke.edu> Cc: freebsd-alpha@freebsd.org Subject: Re: last stable alpha kernel? Message-ID: <20030806170729.GC570@athlon.pn.xcllnt.net> In-Reply-To: <16177.7048.818230.53619@grasshopper.cs.duke.edu> References: <16174.57583.255147.337480@grasshopper.cs.duke.edu> <16175.62326.313499.299641@grasshopper.cs.duke.edu> <20030805192811.GB1198@dhcp01.pn.xcllnt.net> <16177.7048.818230.53619@grasshopper.cs.duke.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Aug 06, 2003 at 11:15:20AM -0400, Andrew Gallatin wrote: > > Marcel Moolenaar writes: > > On Tue, Aug 05, 2003 at 02:12:06PM -0400, Andrew Gallatin wrote: > > > > > > FWIW, here are the results I have for j16 buildworlds on UP alpha so far: > > > > *snip* > > > > > july22: fault on nofault entry panic > > > > We have the fault on nofault entry panic on ia64 as well. I don't > > know when I have time to look at ia64, but I keep an eye on alpha > > when I trace it down. I suspect the cause is roughly identical > > (ia64 pmap was derived from alpha pmap). > > Do you know when they started? My current results are as follows: > (all dates relative to GMT-0400) Unfortunately not. I asked kris to restart package builds on pluto1 two days ago. That's when we got the fault on nofault panics. I expect that the real bug was present for much longer. > > If you have any advice, please don't be shy ;) > Triaging when the problem first started is definitely what needs to be done first. I would probably start at the time the pipe changes came in. That is IIRC roughly two weeks ago. The July 22 datapoint should be fairly close. -- Marcel Moolenaar USPA: A-39004 marcel@xcllnt.net
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030806170729.GC570>