From owner-freebsd-smp@FreeBSD.ORG Wed Jun 20 23:52:06 2007 Return-Path: X-Original-To: freebsd-smp@freebsd.org Delivered-To: freebsd-smp@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 1A2BB16A468 for ; Wed, 20 Jun 2007 23:52:06 +0000 (UTC) (envelope-from yrao@force10networks.com) Received: from mx.force10networks.com (nat-eqx.force10networks.com [69.25.56.27]) by mx1.freebsd.org (Postfix) with ESMTP id 0165A13C447 for ; Wed, 20 Jun 2007 23:52:05 +0000 (UTC) (envelope-from yrao@force10networks.com) Received: from mx.force10networks.com ([10.11.0.222]) by mx.force10networks.com with Microsoft SMTPSVC(6.0.3790.0); Wed, 20 Jun 2007 16:52:51 -0700 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Wed, 20 Jun 2007 16:53:53 -0700 Message-ID: <1818EFE74C4A8A4292E05835D378EC661CE0D0@EXCH-CLUSTER-07.force10networks.com> In-Reply-To: <20070614190603.GA89528@rot13.obsecurity.org> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: kernel core dump hangs with the SMP kernel (FreeBSD 6.2) Thread-Index: AceutydeAlpDdK1bRxGRUR+iQqSZ0gE00eGg References: <1818EFE74C4A8A4292E05835D378EC66130055@EXCH-CLUSTER-07.force10networks.com> <20070614024333.GA70019@rot13.obsecurity.org> <1818EFE74C4A8A4292E05835D378EC66130074@EXCH-CLUSTER-07.force10networks.com> <20070614190603.GA89528@rot13.obsecurity.org> From: "Yong Rao" To: X-OriginalArrivalTime: 20 Jun 2007 23:52:51.0671 (UTC) FILETIME=[1D056E70:01C7B396] Cc: Jagjit Choudhary Subject: kernel core dump hangs with the SMP kernel (FreeBSD 6.2) X-BeenThere: freebsd-smp@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD SMP implementation group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 20 Jun 2007 23:52:06 -0000 Hello, I am able to isolate the problem to kernel configurations which have SMP enabled when used with 2 cpus. With ONE cpu the core dump works ok. I built the kernel with GENERIC, and deliberately crash the kernel (for testing purpose). The core dump works fine. Only added the "options SMP" and crashed the kernel, then prior to any pages being dumped out, it hangs there. Has someone successfully core dumped on a system using SMP kernel with multiple CPUs? I tried on two different boxes (different motherboards, CPUs and hard disks). Both got failed. I tried to enable the DDB, but don't know what to look for when it goes into ddb. Appreciate any pointers. a) The CPU information is=20 CPU: Dual Core AMD Opteron(tm) Processor 280 (2405.47-MHz 686-class CPU) Origin =3D "AuthenticAMD" Id =3D 0x20f12 Stepping =3D 2 =20 Features=3D0x178bfbff Features2=3D0x1 AMD Features=3D0xe2500800 AMD Features2=3D0x3 Cores per package: 2 b) We also tried on another mother board, which has 2 CPUs. The CPU information is below. CPU: Intel(R) Xeon(TM) CPU 2.80GHz (2800.11-MHz 686-class CPU) Origin =3D "GenuineIntel" Id =3D 0xf29 Stepping =3D 9 =20 Features=3D0xbfebfbff Features2=3D0x4400> real memory =3D 2147418112 (2047 MB) avail memory =3D 2096300032 (1999 MB) ACPI APIC Table: FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 6 c) The following are the prints when the dump hung. mem dump: start address =3D 0x4352, len=3D0x30 =20 =20 Fatal trap 12: page fault while in kernel mode cpuid =3D 1; apic id =3D 01 fault virtual address =3D 0x4352 fault code =3D supervisor read, page not present instruction pointer =3D 0x20:0xc9e9fc92 stack pointer =3D 0x28:0xebdbdbdc frame pointer =3D 0x28:0xebdbdbf8 code segment =3D base 0x0, limit 0xfffff, type 0x1b =3D DPL 0, pres 1, def32 1, gran 1 processor eflags =3D interrupt enabled, resume, IOPL =3D 0 current process =3D 74231 (pnicdbg) trap number =3D 12 panic: page fault cpuid =3D 1 Uptime: 1d18h27m42s Dumping 4030 MB (2 chunks) chunk 0: 1MB (154 pages) ... ok chunk 1: 4031MB (1031776 pages) (stopped and hung here) Thanks, Yong =20