John Sullivan
2008-Jul-15 10:15 UTC
Fresh 7.0 Install: Fatal Trap 12 panic when put under load
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
Jeremy Chadwick
2008-Jul-15 10:21 UTC
Fresh 7.0 Install: Fatal Trap 12 panic when put under load
On Tue, Jul 15, 2008 at 10:58:19AM +0100, John Sullivan wrote:> 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.Can the system in question run memtest86+ successfully (no errors) for an hour? It would help diminish (but not entirely rule out) hardware (memory or chipset) issues. -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB |
John Sullivan
2008-Jul-15 10:28 UTC
Fresh 7.0 Install: Fatal Trap 12 panic when put under load
> Can the system in question run memtest86+ successfully (no > errors) for an hour? It would help diminish (but not > entirely rule out) hardware (memory or chipset) issues.Sorry, forgot to mention, I ran memtest over night without any problem reported. I ran Fedora 9 for a month without any issue - FreeBSD 7.0 crashes within an hour. John
Kostik Belousov
2008-Jul-15 19:51 UTC
Fresh 7.0 Install: Fatal Trap 12 panic when put under load
On Tue, Jul 15, 2008 at 08:47:03PM +0100, john@basicnets.co.uk wrote:> > > >> #9? 0xffffffff8067d3ee in uma_zalloc_arg (zone=0xffffff00bfed07e0, > >>udata=0x0, > >>flags=-256) at /usr/src/sys/vm/uma_core.c:1835 > >From the frame #9, please do > >p *zone > >I am esp. interested in the value of the uz_ctor member. > > > >It seems that it becomes corrupted, it value should be 0, as this seems > >to be ffs inode zone.? I suspect that gdb would show 0x6400000000 instead. > > I am afraid that you may need to spell out each step for me :-( > > (kgdb) p *zone > No symbol "zone" in current context.Do the "frame 9" before "p *zone".> (kgdb) list *0xffffffff8067d3ee > 0xffffffff8067d3ee is in uma_zalloc_arg (/usr/src/sys/vm/uma_core.c:1835). > 1830??????????????????????????????? ("uma_zalloc: Bucket pointer > mangled.")); > 1831??????????????????????????? cache->uc_allocs++; > 1832??????????????????????????? critical_exit(); > 1833??? #ifdef INVARIANTS > 1834??????????????????????????? ZONE_LOCK(zone); > 1835??????????????????????????? uma_dbg_alloc(zone, NULL, item); > 1836??????????????????????????? ZONE_UNLOCK(zone); > 1837??? #endif > 1838??????????????????????????? if (zone->uz_ctor != NULL) { > 1839??????????????????????????????????? if (zone->uz_ctor(item, > zone->uz_keg->uk_size, > > Is this that you were looking for?No, see above. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 195 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20080715/37c7f07d/attachment.pgp
Kris Kennaway
2008-Jul-15 20:07 UTC
Fresh 7.0 Install: Fatal Trap 12 panic when put under load
john@basicnets.co.uk wrote:> > > >> #9 0xffffffff8067d3ee in uma_zalloc_arg (zone=0xffffff00bfed07e0, >>> udata=0x0, >>> flags=-256) at /usr/src/sys/vm/uma_core.c:1835 >> From the frame #9, please do >> p *zone >> I am esp. interested in the value of the uz_ctor member. >> >> It seems that it becomes corrupted, it value should be 0, as this seems >> to be ffs inode zone. I suspect that gdb would show 0x6400000000 >> instead. > > I am afraid that you may need to spell out each step for me :-( > > (kgdb) p *zone > No symbol "zone" in current context. > (kgdb) list *0xffffffff8067d3ee > 0xffffffff8067d3ee is in uma_zalloc_arg (/usr/src/sys/vm/uma_core.c:1835). > 1830 ("uma_zalloc: Bucket pointer > mangled.")); > 1831 cache->uc_allocs++; > 1832 critical_exit(); > 1833 #ifdef INVARIANTS > 1834 ZONE_LOCK(zone); > 1835 uma_dbg_alloc(zone, NULL, item); > 1836 ZONE_UNLOCK(zone); > 1837 #endif > 1838 if (zone->uz_ctor != NULL) { > 1839 if (zone->uz_ctor(item, > zone->uz_keg->uk_size, > > Is this that you were looking for?Are you sure that is the same source tree you are running? The 7.0-RELEASE source has the zone->uz_ctor on line 1835, which is consistent with your backtrace. Kris
Kevin Oberman
2008-Jul-16 03:16 UTC
Fresh 7.0 Install: Fatal Trap 12 panic when put under load
> 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 flushbufqueuesCould 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 -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 224 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20080716/9fb539f5/attachment.pgp