Date: Wed, 6 Aug 2003 11:15:20 -0400 (EDT) From: Andrew Gallatin <gallatin@cs.duke.edu> To: Marcel Moolenaar <marcel@xcllnt.net> Cc: freebsd-alpha@freebsd.org Subject: Re: last stable alpha kernel? Message-ID: <16177.7048.818230.53619@grasshopper.cs.duke.edu> In-Reply-To: <20030805192811.GB1198@dhcp01.pn.xcllnt.net> References: <16174.57583.255147.337480@grasshopper.cs.duke.edu> <16175.62326.313499.299641@grasshopper.cs.duke.edu> <20030805192811.GB1198@dhcp01.pn.xcllnt.net>
next in thread | previous in thread | raw e-mail | index | archive | help
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) june1: OK june7: OK june10: OK june12: system lockup june14: system lockup june28: gcc ICE, system lockup july22: fault on nofault entry panic aug5: fault on nofault entry panic I have no idea if the lockup problem is orthogonal to the pmap problem or not. Unfortunately, obrien's FBSDID changes thrashed the src tree between june10 and june12 and make getting diffs very painful. For all I know, the lockup was fixed and the pmap problem is new. So I'm thinking about re-starting the search to see if I can find where the lockup changes to a fault on nofault panic. At least this makes things quicker, as the lockups and/or panics happen quickly. If you have any advice, please don't be shy ;) Drew
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?16177.7048.818230.53619>