Date: Mon, 12 Apr 2004 22:09:31 -0400 (EDT) From: Robert Watson <rwatson@freebsd.org> To: Randy Bush <randy@psg.com> Cc: FreeBSD Current <freebsd-current@freebsd.org> Subject: Re: very current won't mount /tmp Message-ID: <Pine.NEB.3.96L.1040412220557.19867C-100000@fledge.watson.org> In-Reply-To: <16507.18229.168158.735721@roam.psg.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 13 Apr 2004, Randy Bush wrote: > >> ok, so with just-now current, i get a trap 12 for a write into a freed > >> page > >> is there any way i can scrape the screen, or do i have to get a second > >> machine and type all that gibberish? > > Well, the three common options are: > > - serial console > > none > > > - dump, if you can get it > > can't > > > - camera or other capture device > > http://rip.psg.com/~randy/040413.crash-ddb/ :-( Something is walking on memory after freeing it, but it's not immediately clear what. If you boot single-user and don't mount file systems, etc, does running commands result in a panic? Assuming for a moment that it doesn't panic, it would be interesting to try mounting nfs, etc, incrementally until it does crash. If it does panic even from single-user mode, it sounds like some incremental backouts are called :-(. If you back out a week or so (is that possible?) does life get better? Robert N M Watson FreeBSD Core Team, TrustedBSD Projects robert@fledge.watson.org Senior Research Scientist, McAfee Research
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.NEB.3.96L.1040412220557.19867C-100000>