Date: Tue, 15 Jul 2008 20:16:40 -0700 From: "Kevin Oberman" <oberman@es.net> To: "John Sullivan" <john@basicnets.co.uk> Cc: freebsd-stable@freebsd.org Subject: Re: Fresh 7.0 Install: Fatal Trap 12 panic when put under load Message-ID: <20080716031640.7DC744500E@ptavv.es.net> In-Reply-To: Your message of "Tue, 15 Jul 2008 10:58:19 BST." <854CADB9D95147CAB10BC35887A8E5DC@emea.hubersuhner.net>
next in thread | previous in thread | raw e-mail | index | archive | help
--==_Exmh_1216178200_6274P Content-Type: text/plain; charset=us-ascii Content-Disposition: inline > From: "John Sullivan" <john@basicnets.co.uk> > Date: Tue, 15 Jul 2008 10:58:19 +0100 > Sender: owner-freebsd-stable@freebsd.org > > I am experiencing 'random' reboots interspersed with panics whenever I put a newly installed system under load (make index in > /usr/ports is enough). A sample panic is at the end of this email. > > I have updated to 7.0-RELEASE-p2 using the GENERIC amd64 kernel and it is still the same. The system is a Gigabyte GA-M56S-S3 > motherboard with 4GB of RAM, an Athlon X2 6400+ and 3 x Maxtor SATA 750GB HDD's (only the first is currently in use). The first > disk is all allocated to FreeBSD using UFS. There is also a Linksys 802.11a/b/g card installed. I have flashed the BIOS to the > latest revision (F4e). The onboard RAID is disabled. > > At the moment there is no exotic software installed. > > Although I have been using FreeBSD for a number of years this is the first time I have experienced regular panics and am at a > complete loss trying to work out what is wrong. I would be grateful for any advice anyone is willing to give to help me > troubleshoot this issue. > > Thanks in advance > > John > > Fatal trap 12: page fault while in kernel mode > cpuid = 0; apic id = 00 > fault virtual address = 0x800000b0 > fault code - supervisor write data, page not present > instruction pointer = 0x8:0xffffffff804db18c > stack pointer = 0x10:ffffffffb1e92450 > frame pointer = 0x10:ffffffec > code segment = base 0x0, limit 0xfffff, type 0x16, DPL 0, pres 1, long 1, def32 0, gran 1 > processor eflags = interupt enabled, resume, IOPL = 0 > current processkernel trap 12 with interrupts disabled > > #nm -n /boot/kernel/kernel | grep ffffffff804db > ffffffff804dbac0 t flushbufqueues Could be memory, but I'd also suggest looking at temperatures. I've had overheating systems produce lots of such errors. -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: oberman@es.net Phone: +1 510 486-8634 Key fingerprint:059B 2DDF 031C 9BA3 14A4 EADA 927D EBB3 987B 3751 --==_Exmh_1216178200_6274P Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (FreeBSD) Comment: Exmh version 2.5 06/03/2002 iD8DBQFIfWgYkn3rs5h7N1ERAjdFAJ9EYCA98hG/hQVrmEeFUI0RMdWk6wCcCCjT pye7omwRLJ9tTfX6SJKExC8= =Ae1P -----END PGP SIGNATURE----- --==_Exmh_1216178200_6274P--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20080716031640.7DC744500E>