--- On Sat, 8/29/09, Marat N.Afanasyev <ama...@ksu.ru> wrote: > From: Marat N.Afanasyev <ama...@ksu.ru> > Subject: Re: Fatal Trap 12 in various processes always at address 0x3030313a > To: mahle...@yahoo.com > Cc: "FreeBSD-Stable" <freebsd-stable@freebsd.org> > Date: Saturday, August 29, 2009, 6:59 PM > Richard Mahlerwein wrote: > > (Sorry, update to subject to be <something>) > > > > 3 weeks ago: > > I upgraded from 7.1-PRELEASE to -stable and all seemed > fine > > until I rebooted out of single user mode after doing > make > > installworld and mergemaster. At that point, > near the > > end of the boot sequence I got a core dump, > apparently > > triggered by devd. > > > > **** > > Fatal trap 12: page fault while in kernel mode. > > cpu id = 0; apic id = 00 > > fault virtual address = 0x3030313a > > fault code = supervisor write, page not present > > [snip] > > current process = 355 (devd) > > **** > > > > I redid the *whole* process in single user mode, yet > no > > difference. I was out of town for 2.5 weeks > after > > that, then busy for a few days, which brings me to > now: > > > > TODAY: > > I booted to my memtest86+ CD, let it run through which > it > > did with no issues noted. > > I blew away my /usr/src and resynced as of about noon > > today. After following through all steps to > rebuild, I > > now get a fatal trap 12... > > > > **** > > Fatal trap 12: page fault while in kernel mode. > > cpu id = 0; apic id = 00 > > fault virtual address = 0x3030313a > > fault code = supervisor write, page not present > > [snip] > > current process = 352 (sysctl) > > **** > > > > Same virtual address, different process. Umm. > Interesting. > > > > I'm at a loss. Google's been of little help, > and > > searching these lists hasn't turned up much either. > > Does anyone have a further recommendation on what to > do, > > try, test or change? > > > > BTW, I'm GENERIC. > > Rich Mahlerwein > > > > > > > > > _______________________________________________ > > freebsd-stable@freebsd.org > mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > > To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org" > > > such trap could be triggered by 'floating' memory/cache > error. and i think that you should try to suspect memory > first. memtest helps to diagnose most of memory problems, > but not all. > > -- SY, Marat >
How can I test that? If a buildworld will complete successfully several times (with mildly different source, even), and memtest86+ won't find it, how can I tell if that's the problem or not? _______________________________________________ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
