Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 28 Nov 2006 12:44:02 -0800
From:      "Kevin Oberman" <oberman@es.net>
To:        markus@x-trader.de
Cc:        "=?iso-8859-1?Q?freebsd-stable@freebsd=2Eorg?=" <freebsd-stable@freebsd.org>
Subject:   Re: Panic in "thread taskq" on RELENG_6 
Message-ID:  <20061128204402.A8C5D45051@ptavv.es.net>
In-Reply-To: Your message of "Tue, 28 Nov 2006 20:01:06 %2B0100." <20061128190106.1D6B313283@qhmail2.colt1.inetserver.de> 

next in thread | previous in thread | raw e-mail | index | archive | help
--==_Exmh_1164746642_993P
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

> From: "=?iso-8859-1?Q?Markus_Oestreicher?=" <markus@x-trader.de>
> Date: Tue, 28 Nov 2006 20:01:06 +0100
> Sender: owner-freebsd-stable@freebsd.org
> 
> Good Day,
> 
> I get a panic on latest RELENG_6 every 6-12 hours. The server is a
> Dual Xeon FSB800 with 2 GB RAM and aac(4)-disks running postfix and
> amavisd-new for SPAM scanning.
> 
> 
> kernel trap 12 with interrupts disabled
> 
> Fatal trap 12: page fault while in kernel mode
> cpuid = 3; apic id = 07
> fault virtual address 	= 0x104
> fault code		= supervisor read, page not present
> instruction pointer	= 0x20:0xc06774e1
> stack pointer		= 0x28:0xe4f93c90
> frame pointer		= 0x28:0xe4f93c9c
> code segment		= base 0x0, limit 0xfffff, type 0x1b
> 				= DPL 0, pres 1, def32 1, gran 1
> processor eglags		= resume, IOPL = 0
> current process		= 5 (thread taskq)
> 
> The panic always in process "thread taskq".
> 
> db>trace
> _mit_lock_sleep(cb031e5c,c63f7180) at _mtx_lock_sleep+0x9d
> unp_gc(0,1) at uno_gc+0x222
> taskqueue_run(c6439d80) at taskqueue_run+0x13f
> taskqueue_thread_loop(c09f8988,e4f93d38) at taskqueue_thread_loop+0x> 92
> fork_exit(c06a1bc0,c09f8988,e4f93d38) at fork_exit+0x71
> fork_trampoline() at fork_trampoline+0x8
> --- trap 0x1, eip = 0, esp=0xe4f93d6c, ebp = 0
> 
> FreeBSD mx.local 6.2-PRERELEASE FreeBSD 6.2-PRERELEASE #1: 
>  Tue Nov 28 02:12:58 CET 2006     
>  root@mx.local:/usr/obj/usr/src/sys/SMP  i386
> 
> 
> Does that look like a hardware problem or a software issue?
> I will try to swap RAM in the next few days.

You are the third person to report this panic. (I am one of the other
two.

I am guessing from the name of your kernel that this is an SMP
system. So are the other two.

Are you running gnome-2.16 with hald? This is about all we found
in common on the first two systems.

Robert Watson would like some added data. Can you build a kernel with
the following options and connect something to the serial port to record
output?
options WITNESS 
options INVARIANT_SUPPORT 
options DDB 
options KDB 
options INVARIANTS

At the debugger prompt:
> show pcpu
> trace
> show allpcpu
> traceall
> show alllocks

At least my system has been totally uncooperative in crashing when I am
anywhere near it, so I have not yet collected any information other than
dumps.
-- 
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_1164746642_993P
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (FreeBSD)
Comment: Exmh version 2.5 06/03/2002

iD8DBQFFbJ+Skn3rs5h7N1ERAg6IAKCCuKmFNBPuPDVqndMZ+YjFjZxIdQCgt/H2
I2tgjLwXX9kij2tpgV6KtSk=
=WlW1
-----END PGP SIGNATURE-----

--==_Exmh_1164746642_993P--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20061128204402.A8C5D45051>