Date: Sun, 21 Aug 2011 21:45:38 +0300 From: Andriy Gapon <avg@FreeBSD.org> To: Derrick Edwards <dantavious313@gmail.com> Cc: "freebsd-current@freebsd.org" <freebsd-current@FreeBSD.org> Subject: Re: PANICS on 9.0-BETA1 Message-ID: <4E515252.4060706@FreeBSD.org> In-Reply-To: <1313948879.2448.3.camel@datdude> References: <1313705220.8034.2.camel@datdude> <4E4E717B.9090407@FreeBSD.org> <1313948879.2448.3.camel@datdude>
next in thread | previous in thread | raw e-mail | index | archive | help
on 21/08/2011 20:47 Derrick Edwards said the following: > On Fri, 2011-08-19 at 17:21 +0300, Andriy Gapon wrote: >> on 19/08/2011 01:07 Derrick Edwards said the following: >>> Fatal trap 12: page fault while in kernel mode >>> cpuid = 0; apic id = 00 >>> fault virtual address = 0xffffbe00a45b6798 >> >> This address looks suspiciously like a result of bit flips. >> >>> fault code = supervisor write data, page not present >>> instruction pointer = 0x20:0xffffffff814f444c >>> stack pointer = 0x28:0xffffff82267fbe90 >>> frame pointer = 0x28:0xffffff82267fbea0 >>> code segment = base 0x0, limit 0xfffff, type 0x1b >>> = DPL 0, pres 1, long 1, def32 0, gran 1 >>> processor eflags = interrupt enabled, resume, IOPL = 0 >>> current process = 5889 (csup) >>> trap number = 12 >>> panic: page fault >>> cpuid = 0 >>> Uptime: 10h9m0s >>> Dumping 1823 out of 7912 >> >> Do you always get the same stack trace? Or are they always different? >> I would double-check the hardware first. >> > Andriy, > Thanks for the reply. The stack trace are different. Attached is the > latest one. Machine is about 3 months old. Any recommendations on what > hardware to start looking at. Panic occurs with X and without X being > used. Start with the memory - try memtest86/memtest86+. But actually any bit could be under suspicion - CPU, PSU, etc. -- Andriy Gapon
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4E515252.4060706>