From owner-freebsd-hardware@FreeBSD.ORG Mon Feb 1 14:49:52 2010 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 451351065695 for ; Mon, 1 Feb 2010 14:49:52 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id 105898FC13 for ; Mon, 1 Feb 2010 14:49:52 +0000 (UTC) Received: from bigwig.baldwin.cx (66.111.2.69.static.nyinternet.net [66.111.2.69]) by cyrus.watson.org (Postfix) with ESMTPSA id BEA6046B23; Mon, 1 Feb 2010 09:49:51 -0500 (EST) Received: from jhbbsd.localnet (smtp.hudson-trading.com [209.249.190.9]) by bigwig.baldwin.cx (Postfix) with ESMTPA id BB8BB8A025; Mon, 1 Feb 2010 09:49:50 -0500 (EST) From: John Baldwin To: freebsd-hardware@freebsd.org Date: Mon, 1 Feb 2010 09:32:20 -0500 User-Agent: KMail/1.12.1 (FreeBSD/7.2-CBSD-20100120; KDE/4.3.1; amd64; ; ) References: <65BCAB515656D34AA48B0E713966CC83046A64@MBX021-E2-NJ-5.exch021.domain.local> In-Reply-To: <65BCAB515656D34AA48B0E713966CC83046A64@MBX021-E2-NJ-5.exch021.domain.local> MIME-Version: 1.0 Message-Id: <201002010932.20443.jhb@freebsd.org> Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0.1 (bigwig.baldwin.cx); Mon, 01 Feb 2010 09:49:50 -0500 (EST) X-Virus-Scanned: clamav-milter 0.95.1 at bigwig.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-1.3 required=4.2 tests=AWL,BAYES_00 autolearn=ham version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on bigwig.baldwin.cx Cc: "Hoang V.D. | Creative Solutions GmbH" Subject: Re: FreeBSD 8.0, Intel Xeon E5530, Dell R410, only 2 cores available X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 01 Feb 2010 14:49:52 -0000 On Friday 29 January 2010 6:28:17 pm Hoang V.D. | Creative Solutions GmbH wrote: > Hello, > > We just purchased a Dell PowerEdge R410 server with this CPU: Intel Xeon Processor E5530 > > http://ark.intel.com/Product.aspx?id=37103 > > According to specs the CPU has 4 cores, 8 Hyper-Threading threads, however after installing > FreeBSD 8.0 (amd64), only 2 cores (4 SMT threads) were recognized by the kernel. Here is the > relevant dmesg extract: > > ----------------- > Copyright (c) 1992-2009 The FreeBSD Project. > Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 > The Regents of the University of California. All rights reserved. > FreeBSD is a registered trademark of The FreeBSD Foundation. > FreeBSD 8.0-RELEASE-p2 #0: Tue Jan 5 21:11:58 UTC 2010 > root@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC > Timecounter "i8254" frequency 1193182 Hz quality 0 > CPU: Intel(R) Xeon(R) CPU E5530 @ 2.40GHz (2394.01-MHz K8-class CPU) > Origin = "GenuineIntel" Id = 0x106a5 Stepping = 5 > Features=0xbfebfbff > Features2=0x9ce3bd > AMD Features=0x28100800 > AMD Features2=0x1 > TSC: P-state invariant > real memory = 8589934592 (8192 MB) > avail memory = 8247111680 (7865 MB) > ACPI APIC Table: > FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs > FreeBSD/SMP: 1 package(s) x 2 core(s) x 2 SMT threads > cpu0 (BSP): APIC ID: 16 > cpu1 (AP): APIC ID: 17 > cpu2 (AP): APIC ID: 18 > cpu3 (AP): APIC ID: 19 > ioapic1: Changing APIC ID to 1 > ioapic0 irqs 0-23 on motherboard > ioapic1 irqs 32-55 on motherboard > ... > ----------------- > > We was expecting to see "1 package(s) x 4 core(s) x 2 SMT threads" and 8 usable "cpus" > Instead. According to sysctl: > > kern.smp.cpus: 4 > kern.smp.maxcpus: 32 > hw.ncpu: 4 > machdep.hlt_cpus: 0 > > We have made no change to the BIOS settings (all settings are set by default by Dell). > Could anyone help us with an explanation for this issue? Can you get the output of 'acpidump -t'? Also, the 'x 2 cores x 2 SMT threads' bit is based on registers read from the CPU. It is really claiming to be a 2x2 chip (2 cores with 2 threads each). Maybe see what /usr/ports/misc/cpuid claims? -- John Baldwin From owner-freebsd-hardware@FreeBSD.ORG Mon Feb 1 14:56:36 2010 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 17E141065676 for ; Mon, 1 Feb 2010 14:56:36 +0000 (UTC) (envelope-from freebsd-hardware@m.gmane.org) Received: from lo.gmane.org (lo.gmane.org [80.91.229.12]) by mx1.freebsd.org (Postfix) with ESMTP id C1BC88FC1D for ; Mon, 1 Feb 2010 14:56:35 +0000 (UTC) Received: from list by lo.gmane.org with local (Exim 4.69) (envelope-from ) id 1NbxSg-0001OK-IA for freebsd-hardware@freebsd.org; Mon, 01 Feb 2010 15:41:10 +0100 Received: from lara.cc.fer.hr ([161.53.72.113]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 01 Feb 2010 15:41:10 +0100 Received: from ivoras by lara.cc.fer.hr with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 01 Feb 2010 15:41:10 +0100 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-hardware@freebsd.org From: Ivan Voras Date: Mon, 01 Feb 2010 15:40:40 +0100 Lines: 26 Message-ID: References: <65BCAB515656D34AA48B0E713966CC83046A64@MBX021-E2-NJ-5.exch021.domain.local> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: lara.cc.fer.hr User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.1.5) Gecko/20100118 Thunderbird/3.0 In-Reply-To: <65BCAB515656D34AA48B0E713966CC83046A64@MBX021-E2-NJ-5.exch021.domain.local> Sender: news Subject: Re: FreeBSD 8.0, Intel Xeon E5530, Dell R410, only 2 cores available X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 01 Feb 2010 14:56:36 -0000 On 01/30/10 00:28, Hoang V.D. | Creative Solutions GmbH wrote: > FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs > FreeBSD/SMP: 1 package(s) x 2 core(s) x 2 SMT threads > We was expecting to see "1 package(s) x 4 core(s) x 2 SMT threads" and 8 usable "cpus" > Instead. According to sysctl: > > kern.smp.cpus: 4 > kern.smp.maxcpus: 32 > hw.ncpu: 4 > machdep.hlt_cpus: 0 > > We have made no change to the BIOS settings (all settings are set by default by Dell). > Could anyone help us with an explanation for this issue? Your CPU count is wrong. The topology might be wrong for Nehalems but it would be wrong in a different way. Before you can debug the FreeBSD side you should first make the hw.ncpu setting equal the "right" total number of logical CPUs available, e.g. by configuring your BIOS, upgrading your BIOS, etc. After you configure your BIOS to recognize all the CPUs, you can proceed, if necessary, to debug the CPU topology. From owner-freebsd-hardware@FreeBSD.ORG Mon Feb 1 16:14:33 2010 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7A5871065670 for ; Mon, 1 Feb 2010 16:14:33 +0000 (UTC) (envelope-from hoang.v.d@creativesolutions.at) Received: from west.smtp.exch021.serverdata.net (hub021-nj-2.exch021.serverdata.net [206.225.164.217]) by mx1.freebsd.org (Postfix) with ESMTP id 1866A8FC1D for ; Mon, 1 Feb 2010 16:14:32 +0000 (UTC) Received: from MBX021-E2-NJ-5.exch021.domain.local ([169.254.7.217]) by HUB021-NJ-2.exch021.domain.local ([10.240.4.33]) with mapi; Mon, 1 Feb 2010 08:14:32 -0800 From: "Hoang V.D. | Creative Solutions GmbH" To: "freebsd-hardware@freebsd.org" Thread-Topic: FreeBSD 8.0, Intel Xeon E5530, Dell R410, only 2 cores available Thread-Index: AcqhOrx/G8GKs9gGTfi/PH73nxAYOQCU63wAAA+3F5A= Date: Mon, 1 Feb 2010 16:14:28 +0000 Message-ID: <65BCAB515656D34AA48B0E713966CC8305F775@MBX021-E2-NJ-5.exch021.domain.local> References: <65BCAB515656D34AA48B0E713966CC83046A64@MBX021-E2-NJ-5.exch021.domain.local> <201002010932.20443.jhb@freebsd.org> In-Reply-To: <201002010932.20443.jhb@freebsd.org> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Cc: Subject: RE: FreeBSD 8.0, Intel Xeon E5530, Dell R410, only 2 cores available X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 01 Feb 2010 16:14:33 -0000 Hello > -----Original Message----- > From: John Baldwin [mailto:jhb@freebsd.org] > Sent: Monday, February 01, 2010 3:32 PM > To: freebsd-hardware@freebsd.org > Cc: Hoang V.D. | Creative Solutions GmbH > Subject: Re: FreeBSD 8.0, Intel Xeon E5530, Dell R410, only 2 cores avail= able > > Can you get the output of 'acpidump -t'? Also, the 'x 2 cores x 2 SMT > threads' bit is based on registers read from the CPU. It is really claim= ing > to be a 2x2 chip (2 cores with 2 threads each). Maybe see what > /usr/ports/misc/cpuid claims? > This is the output of 'acpidump -t': =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D /* RSD PTR: OEM=3DDELL, ACPI_Rev=3D2.0x (2) XSDT=3D0x000f0f34, length=3D36, cksum=3D138 */ /* XSDT: Length=3D156, Revision=3D1, Checksum=3D103, OEMID=3DDELL, OEM Table ID=3DPE_SC3, OEM Revision=3D0x1, Creator ID=3DDELL, Creator Revision=3D0x1 Entries=3D{ 0xcf6c3f9c, 0xcf6c3478, 0xcf6c35d8, 0xcf6c362c, 0xcf6c3= 668, 0xcf6c38c4, 0xcf6c3904, 0xcf6c3a3c, 0xcf6b2a18, 0xcf6b2c88, 0xcf6b2898= , 0xcf6b28c8, 0xcf6c3bc0, 0xcf6c3f34, 0xcf6c7000 } */ /* FACP: Length=3D244, Revision=3D3, Checksum=3D33, OEMID=3DDELL, OEM Table ID=3DPE_SC3, OEM Revision=3D0x1, Creator ID=3DDELL, Creator Revision=3D0x1 FACS=3D0xcf6c6000, DSDT=3D0xcf6af000 INT_MODEL=3DPIC Preferred_PM_Profile=3DEnterprise Server (4) SCI_INT=3D9 SMI_CMD=3D0xb2, ACPI_ENABLE=3D0x70, ACPI_DISABLE=3D0x71, S4BIOS_REQ= =3D0x0 PSTATE_CNT=3D0x90 PM1a_EVT_BLK=3D0x800-0x803 PM1a_CNT_BLK=3D0x804-0x805 PM2_CNT_BLK=3D0x850-0x850 PM_TMR_BLK=3D0x808-0x80b GPE0_BLK=3D0x820-0x82f CST_CNT=3D0x90 P_LVL2_LAT=3D500 us, P_LVL3_LAT=3D5000 us FLUSH_SIZE=3D0, FLUSH_STRIDE=3D0 DUTY_OFFSET=3D0, DUTY_WIDTH=3D0 DAY_ALRM=3D0, MON_ALRM=3D0, CENTURY=3D50 IAPC_BOOT_ARCH=3D{LEGACY_DEV,8042} Flags=3D{WBINVD,PROC_C1,SLP_BUTTON,RTC_S4} X_FACS=3D0xcf6c6000, X_DSDT=3D0xcf6af000 X_PM1a_EVT_BLK=3D0x800:0[32] (IO) X_PM1a_CNT_BLK=3D0x804:0[16] (IO) X_PM_TMR_BLK=3D0x808:0[32] (IO) X_GPE0_BLK=3D0x820:0[128] (IO) */ /* FACS: Length=3D64, HwSig=3D0x00000000, Firm_Wake_Vec=3D0x00000000 Global_Lock=3D Flags=3D Version=3D1 */ /* DSDT: Length=3D14488, Revision=3D1, Checksum=3D148, OEMID=3DDELL, OEM Table ID=3DPE_SC3, OEM Revision=3D0x1, Creator ID=3DINTL, Creator Revision=3D0x20050624 */ /* APIC: Length=3D350, Revision=3D1, Checksum=3D88, OEMID=3DDELL, OEM Table ID=3DPE_SC3, OEM Revision=3D0x1, Creator ID=3DDELL, Creator Revision=3D0x1 Local APIC ADDR=3D0xfee00000 Flags=3D{PC-AT} Type=3DLocal APIC ACPI CPU=3D1 Flags=3D{ENABLED} APIC ID=3D16 Type=3DLocal APIC ACPI CPU=3D2 Flags=3D{ENABLED} APIC ID=3D18 Type=3DLocal APIC ACPI CPU=3D3 Flags=3D{ENABLED} APIC ID=3D17 Type=3DLocal APIC ACPI CPU=3D4 Flags=3D{ENABLED} APIC ID=3D19 Type=3DLocal APIC ACPI CPU=3D5 Flags=3D{DISABLED} APIC ID=3D36 Type=3DLocal APIC ACPI CPU=3D6 Flags=3D{DISABLED} APIC ID=3D37 Type=3DLocal APIC ACPI CPU=3D7 Flags=3D{DISABLED} APIC ID=3D38 Type=3DLocal APIC ACPI CPU=3D8 Flags=3D{DISABLED} APIC ID=3D39 Type=3DLocal APIC ACPI CPU=3D9 Flags=3D{DISABLED} APIC ID=3D40 Type=3DLocal APIC ACPI CPU=3D10 Flags=3D{DISABLED} APIC ID=3D41 Type=3DLocal APIC ACPI CPU=3D11 Flags=3D{DISABLED} APIC ID=3D42 Type=3DLocal APIC ACPI CPU=3D12 Flags=3D{DISABLED} APIC ID=3D43 Type=3DLocal APIC ACPI CPU=3D13 Flags=3D{DISABLED} APIC ID=3D44 Type=3DLocal APIC ACPI CPU=3D14 Flags=3D{DISABLED} APIC ID=3D45 Type=3DLocal APIC ACPI CPU=3D15 Flags=3D{DISABLED} APIC ID=3D46 Type=3DLocal APIC ACPI CPU=3D16 Flags=3D{DISABLED} APIC ID=3D47 Type=3DLocal APIC ACPI CPU=3D17 Flags=3D{DISABLED} APIC ID=3D48 Type=3DLocal APIC ACPI CPU=3D18 Flags=3D{DISABLED} APIC ID=3D49 Type=3DLocal APIC ACPI CPU=3D19 Flags=3D{DISABLED} APIC ID=3D50 Type=3DLocal APIC ACPI CPU=3D20 Flags=3D{DISABLED} APIC ID=3D51 Type=3DLocal APIC ACPI CPU=3D21 Flags=3D{DISABLED} APIC ID=3D52 Type=3DLocal APIC ACPI CPU=3D22 Flags=3D{DISABLED} APIC ID=3D53 Type=3DLocal APIC ACPI CPU=3D23 Flags=3D{DISABLED} APIC ID=3D54 Type=3DLocal APIC ACPI CPU=3D24 Flags=3D{DISABLED} APIC ID=3D55 Type=3DLocal APIC ACPI CPU=3D25 Flags=3D{DISABLED} APIC ID=3D56 Type=3DLocal APIC ACPI CPU=3D26 Flags=3D{DISABLED} APIC ID=3D57 Type=3DLocal APIC ACPI CPU=3D27 Flags=3D{DISABLED} APIC ID=3D58 Type=3DLocal APIC ACPI CPU=3D28 Flags=3D{DISABLED} APIC ID=3D59 Type=3DLocal APIC ACPI CPU=3D29 Flags=3D{DISABLED} APIC ID=3D60 Type=3DLocal APIC ACPI CPU=3D30 Flags=3D{DISABLED} APIC ID=3D61 Type=3DLocal APIC ACPI CPU=3D31 Flags=3D{DISABLED} APIC ID=3D62 Type=3DLocal APIC ACPI CPU=3D32 Flags=3D{DISABLED} APIC ID=3D63 Type=3DLocal NMI ACPI CPU=3DALL LINT Pin=3D1 Flags=3D{Polarity=3Dactive-hi, Trigger=3Dedge} Type=3DINT Override BUS=3D0 IRQ=3D0 INTR=3D2 Flags=3D{Polarity=3Dconforming, Trigger=3Dconforming} Type=3DINT Override BUS=3D0 IRQ=3D9 INTR=3D9 Flags=3D{Polarity=3Dactive-hi, Trigger=3Dlevel} Type=3DIO APIC APIC ID=3D0 INT BASE=3D0 ADDR=3D0x00000000fec00000 Type=3DIO APIC APIC ID=3D1 INT BASE=3D32 ADDR=3D0x00000000fec80000 */ /* SPCR: Length=3D80, Revision=3D1, Checksum=3D235, OEMID=3DDELL, OEM Table ID=3DPE_SC3, OEM Revision=3D0x1, Creator ID=3DDELL, Creator Revision=3D0x1 */ /* HPET: Length=3D56, Revision=3D1, Checksum=3D178, OEMID=3DDELL, OEM Table ID=3DPE_SC3, OEM Revision=3D0x1, Creator ID=3DDELL, Creator Revision=3D0x1 HPET Number=3D0 ADDR=3D0xfed00000:0[0] (Memory) HW Rev=3D0x1 Comparitors=3D3 Counter Size=3D1 Legacy IRQ routing capable=3D{TRUE} PCI Vendor ID=3D0x8086 Minimal Tick=3D1000 */ /* DMAR: Length=3D432, Revision=3D1, Checksum=3D44, OEMID=3DDELL, OEM Table ID=3DPE_SC3, OEM Revision=3D0x1, Creator ID=3DDELL, Creator Revision=3D0x1 */ /* MCFG: Length=3D60, Revision=3D1, Checksum=3D70, OEMID=3DDELL, OEM Table ID=3DPE_SC3, OEM Revision=3D0x1, Creator ID=3DDELL, Creator Revision=3D0x1 Base Address=3D0x00000000e0000000 Segment Group=3D0x0000 Start Bus=3D0 End Bus=3D255 */ /* WD__: Length=3D308, Revision=3D1, Checksum=3D218, OEMID=3DDELL, OEM Table ID=3DPE_SC3, OEM Revision=3D0x1, Creator ID=3DDELL, Creator Revision=3D0x1 */ /* SLIC: Length=3D36, Revision=3D1, Checksum=3D47, OEMID=3DDELL, OEM Table ID=3DPE_SC3, OEM Revision=3D0x1, Creator ID=3DDELL, Creator Revision=3D0x1 */ /* ERST: Length=3D624, Revision=3D1, Checksum=3D114, OEMID=3DDELL, OEM Table ID=3DPE_SC3, OEM Revision=3D0x1, Creator ID=3DDELL, Creator Revision=3D0x1 */ /* HEST: Length=3D936, Revision=3D1, Checksum=3D148, OEMID=3DDELL, OEM Table ID=3DPE_SC3, OEM Revision=3D0x1, Creator ID=3DDELL, Creator Revision=3D0x1 */ /* BERT: Length=3D48, Revision=3D1, Checksum=3D136, OEMID=3DDELL, OEM Table ID=3DPE_SC3, OEM Revision=3D0x1, Creator ID=3DDELL, Creator Revision=3D0x1 */ /* EINJ: Length=3D336, Revision=3D1, Checksum=3D25, OEMID=3DDELL, OEM Table ID=3DPE_SC3, OEM Revision=3D0x1, Creator ID=3DDELL, Creator Revision=3D0x1 */ /* SRAT: Length=3D880, Revision=3D1, Checksum=3D202, OEMID=3DDELL, OEM Table ID=3DPE_SC3, OEM Revision=3D0x1, Creator ID=3DDELL, Creator Revision=3D0x1 Table Revision=3D1 Type=3DCPU Flags=3D{ENABLED} APIC ID=3D16 Proximity Domain=3D1 Type=3DCPU Flags=3D{ENABLED} APIC ID=3D18 Proximity Domain=3D1 Type=3DCPU Flags=3D{ENABLED} APIC ID=3D17 Proximity Domain=3D1 Type=3DCPU Flags=3D{ENABLED} APIC ID=3D19 Proximity Domain=3D1 Type=3DCPU Flags=3D{DISABLED} APIC ID=3D36 Proximity Domain=3D0 Type=3DCPU Flags=3D{DISABLED} APIC ID=3D37 Proximity Domain=3D0 Type=3DCPU Flags=3D{DISABLED} APIC ID=3D38 Proximity Domain=3D0 Type=3DCPU Flags=3D{DISABLED} APIC ID=3D39 Proximity Domain=3D0 Type=3DCPU Flags=3D{DISABLED} APIC ID=3D40 Proximity Domain=3D0 Type=3DCPU Flags=3D{DISABLED} APIC ID=3D41 Proximity Domain=3D0 Type=3DCPU Flags=3D{DISABLED} APIC ID=3D42 Proximity Domain=3D0 Type=3DCPU Flags=3D{DISABLED} APIC ID=3D43 Proximity Domain=3D0 Type=3DCPU Flags=3D{DISABLED} APIC ID=3D44 Proximity Domain=3D0 Type=3DCPU Flags=3D{DISABLED} APIC ID=3D45 Proximity Domain=3D0 Type=3DCPU Flags=3D{DISABLED} APIC ID=3D46 Proximity Domain=3D0 Type=3DCPU Flags=3D{DISABLED} APIC ID=3D47 Proximity Domain=3D0 Type=3DCPU Flags=3D{DISABLED} APIC ID=3D48 Proximity Domain=3D0 Type=3DCPU Flags=3D{DISABLED} APIC ID=3D49 Proximity Domain=3D0 Type=3DCPU Flags=3D{DISABLED} APIC ID=3D50 Proximity Domain=3D0 Type=3DCPU Flags=3D{DISABLED} APIC ID=3D51 Proximity Domain=3D0 Type=3DCPU Flags=3D{DISABLED} APIC ID=3D52 Proximity Domain=3D0 Type=3DCPU Flags=3D{DISABLED} APIC ID=3D53 Proximity Domain=3D0 Type=3DCPU Flags=3D{DISABLED} APIC ID=3D54 Proximity Domain=3D0 Type=3DCPU Flags=3D{DISABLED} APIC ID=3D55 Proximity Domain=3D0 Type=3DCPU Flags=3D{DISABLED} APIC ID=3D56 Proximity Domain=3D0 Type=3DCPU Flags=3D{DISABLED} APIC ID=3D57 Proximity Domain=3D0 Type=3DCPU Flags=3D{DISABLED} APIC ID=3D58 Proximity Domain=3D0 Type=3DCPU Flags=3D{DISABLED} APIC ID=3D59 Proximity Domain=3D0 Type=3DCPU Flags=3D{DISABLED} APIC ID=3D60 Proximity Domain=3D0 Type=3DCPU Flags=3D{DISABLED} APIC ID=3D61 Proximity Domain=3D0 Type=3DCPU Flags=3D{DISABLED} APIC ID=3D62 Proximity Domain=3D0 Type=3DCPU Flags=3D{DISABLED} APIC ID=3D63 Proximity Domain=3D0 Type=3DMemory Flags=3D{ENABLED} Base Address=3D0x0000000000000000 Length=3D0x00000000d0000000 Proximity Domain=3D1 Type=3DMemory Flags=3D{ENABLED} Base Address=3D0x0000000100000000 Length=3D0x0000000130000000 Proximity Domain=3D1 Type=3DMemory Flags=3D{DISABLED} Base Address=3D0x0000000000000000 Length=3D0x0000000000000000 Proximity Domain=3D0 Type=3DMemory Flags=3D{DISABLED} Base Address=3D0x0000000000000000 Length=3D0x0000000000000000 Proximity Domain=3D0 Type=3DMemory Flags=3D{DISABLED} Base Address=3D0x0000000000000000 Length=3D0x0000000000000000 Proximity Domain=3D0 Type=3DMemory Flags=3D{DISABLED} Base Address=3D0x0000000000000000 Length=3D0x0000000000000000 Proximity Domain=3D0 Type=3DMemory Flags=3D{DISABLED} Base Address=3D0x0000000000000000 Length=3D0x0000000000000000 Proximity Domain=3D0 Type=3DMemory Flags=3D{DISABLED} Base Address=3D0x0000000000000000 Length=3D0x0000000000000000 Proximity Domain=3D0 */ /* TCPA: Length=3D100, Revision=3D2, Checksum=3D176, OEMID=3DDELL, OEM Table ID=3DPE_SC3, OEM Revision=3D0x1, Creator ID=3DDELL, Creator Revision=3D0x1 */ /* SSDT: Length=3D4376, Revision=3D1, Checksum=3D43, OEMID=3DINTEL, OEM Table ID=3DPPM RCM, OEM Revision=3D0x80000001, Creator ID=3DINTL, Creator Revision=3D0x20061109 */ =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D It looks like all CPU above 4 are marked as "Disabled". Do "CPUs" here mean= real cores or SMT cores? Here is the output of cpuid: =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D eax in eax ebx ecx edx 00000000 0000000b 756e6547 6c65746e 49656e69 00000001 000106a5 12100800 009ce3bd bfebfbff 00000002 55035a01 00f0b2e4 00000000 09ca212c 00000003 00000000 00000000 00000000 00000000 00000004 1c004121 01c0003f 0000003f 00000000 00000005 00000040 00000040 00000003 00001120 00000006 00000003 00000002 00000001 00000000 00000007 00000000 00000000 00000000 00000000 00000008 00000000 00000000 00000000 00000000 00000009 00000000 00000000 00000000 00000000 0000000a 07300403 00000044 00000000 00000603 0000000b 00000001 00000002 00000100 00000010 80000000 80000008 00000000 00000000 00000000 80000001 00000000 00000000 00000001 28100800 80000002 65746e49 2952286c 6f655820 2952286e 80000003 55504320 20202020 20202020 45202020 80000004 30333535 20402020 30342e32 007a4847 80000005 00000000 00000000 00000000 00000000 80000006 00000000 00000000 01006040 00000000 80000007 00000000 00000000 00000000 00000100 80000008 00003028 00000000 00000000 00000000 Vendor ID: "GenuineIntel"; CPUID level 11 Intel-specific functions: Version 000106a5: Type 0 - Original OEM Family 6 - Pentium Pro Model 10 - Pentium III Xeon processor model A Stepping 5 Reserved 4 Extended brand string: "Intel(R) Xeon(R) CPU E5530 @ 2.40GHz" CLFLUSH instruction cache line size: 8 Initial APIC ID: 16 Hyper threading siblings: 16 Feature flags: bfebfbff: FPU Floating Point Unit VME Virtual 8086 Mode Enhancements DE Debugging Extensions PSE Page Size Extensions TSC Time Stamp Counter MSR Model Specific Registers PAE Physical Address Extension MCE Machine Check Exception CX8 COMPXCHG8B Instruction APIC On-chip Advanced Programmable Interrupt Controller present and enabl= ed SEP Fast System Call MTRR Memory Type Range Registers PGE PTE Global Flag MCA Machine Check Architecture CMOV Conditional Move and Compare Instructions FGPAT Page Attribute Table PSE-36 36-bit Page Size Extension CLFSH CFLUSH instruction DS Debug store ACPI Thermal Monitor and Clock Ctrl MMX MMX instruction set FXSR Fast FP/MMX Streaming SIMD Extensions save/restore SSE Streaming SIMD Extensions instruction set SSE2 SSE2 extensions SS Self Snoop HT Hyper Threading TM Thermal monitor 31 reserved Feature flags set 2: 009ce3bd: SSE3 SSE3 extensions DTES64 64-bit debug store MONITOR MONITOR/MWAIT instructions DS-CPL CPL Qualified Debug Store VMX Virtual Machine Extensions EST Enhanced Intel SpeedStep Technology TM2 Thermal Monitor 2 SSSE3 Supplemental Streaming SIMD Extension 3 CX16 CMPXCHG16B xTPR Send Task Priority messages PDCM Perfmon and debug capability DCA Direct Cache Access SSE4.1 Streaming SIMD Extension 4.1 SSE4.1 Streaming SIMD Extension 4.2 POPCNT POPCNT instruction Extended feature flags: 28100800: SYSCALL SYSCALL/SYSRET instructions XD-bit Execution Disable bit 27 - unknown feature EM64T Intel Extended Memory 64 Technology Extended feature flags set 2: 00000001: 0 - unknown feature TLB and cache info: 5a: Data TLB: 2MB or 4MB pages, 4-way set associative, 32 entries 03: Data TLB: 4KB pages, 4-way set assoc, 64 entries 55: Instruction TLB: 2MB or 4MB pages, fully assoc., 7 entries e4: 3rd-level cache: 8MB, 16-way set associative, 64-byte line size b2: Instruction TLB: 4-KB Pages, 4-way set associative, 64 entries f0: 64-byte prefetching 2c: 1st-level data cache: 32-KB, 8-way set associative, 64-byte line size 21: 256-KB L2 (MLC), 8-way set associative, 64 byte line size ca: Shared 2nd-level TLB: 4-KB Pages, 4-way set associative, 512 entries 09: 1st-level instruction cache: 32KB, 4-way set assoc, 64 byte line size Processor serial: 0001-06A5-0000-0000-0000-0000 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > -- > John Baldwin Thank you for your help! Best regards, Hoang From owner-freebsd-hardware@FreeBSD.ORG Mon Feb 1 16:37:41 2010 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8244B106566B for ; Mon, 1 Feb 2010 16:37:41 +0000 (UTC) (envelope-from hoang.v.d@creativesolutions.at) Received: from west.smtp.exch021.serverdata.net (hub021-nj-2.exch021.serverdata.net [206.225.164.217]) by mx1.freebsd.org (Postfix) with ESMTP id 31CF08FC15 for ; Mon, 1 Feb 2010 16:37:41 +0000 (UTC) Received: from MBX021-E2-NJ-5.exch021.domain.local ([169.254.7.217]) by HUB021-NJ-2.exch021.domain.local ([10.240.4.33]) with mapi; Mon, 1 Feb 2010 08:37:40 -0800 From: "Hoang V.D. | Creative Solutions GmbH" To: "freebsd-hardware@freebsd.org" Thread-Topic: FreeBSD 8.0, Intel Xeon E5530, Dell R410, only 2 cores available Thread-Index: AcqhOrx/G8GKs9gGTfi/PH73nxAYOQCVNf4AAA1G6fA= Date: Mon, 1 Feb 2010 16:37:37 +0000 Message-ID: <65BCAB515656D34AA48B0E713966CC8305F7A8@MBX021-E2-NJ-5.exch021.domain.local> References: <65BCAB515656D34AA48B0E713966CC83046A64@MBX021-E2-NJ-5.exch021.domain.local> In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 MIME-Version: 1.0 Cc: Ivan Voras Subject: RE: FreeBSD 8.0, Intel Xeon E5530, Dell R410, only 2 cores available X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 01 Feb 2010 16:37:41 -0000 VGhhbmsgeW91Lg0KDQo+IC0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQo+IEZyb206IG93bmVy LWZyZWVic2QtaGFyZHdhcmVAZnJlZWJzZC5vcmcgW21haWx0bzpvd25lci1mcmVlYnNkLQ0KPiBo YXJkd2FyZUBmcmVlYnNkLm9yZ10gT24gQmVoYWxmIE9mIEl2YW4gVm9yYXMNCj4gU2VudDogTW9u ZGF5LCBGZWJydWFyeSAwMSwgMjAxMCAzOjQxIFBNDQo+IFRvOiBmcmVlYnNkLWhhcmR3YXJlQGZy ZWVic2Qub3JnDQo+IFN1YmplY3Q6IFJlOiBGcmVlQlNEIDguMCwgSW50ZWwgWGVvbiBFNTUzMCwg RGVsbCBSNDEwLCBvbmx5IDIgY29yZXMgYXZhaWxhYmxlDQo+IA0KPiBZb3VyIENQVSBjb3VudCBp cyB3cm9uZy4gVGhlIHRvcG9sb2d5IG1pZ2h0IGJlIHdyb25nIGZvciBOZWhhbGVtcyBidXQgaXQN Cj4gd291bGQgYmUgd3JvbmcgaW4gYSBkaWZmZXJlbnQgd2F5Lg0KPiANCj4gQmVmb3JlIHlvdSBj YW4gZGVidWcgdGhlIEZyZWVCU0Qgc2lkZSB5b3Ugc2hvdWxkIGZpcnN0IG1ha2UgdGhlIGh3Lm5j cHUNCj4gc2V0dGluZyBlcXVhbCB0aGUgInJpZ2h0IiB0b3RhbCBudW1iZXIgb2YgbG9naWNhbCBD UFVzIGF2YWlsYWJsZSwgZS5nLg0KPiBieSBjb25maWd1cmluZyB5b3VyIEJJT1MsIHVwZ3JhZGlu ZyB5b3VyIEJJT1MsIGV0Yy4NCj4gDQo+IEFmdGVyIHlvdSBjb25maWd1cmUgeW91ciBCSU9TIHRv IHJlY29nbml6ZSBhbGwgdGhlIENQVXMsIHlvdSBjYW4gcHJvY2VlZCwgaWYNCj4gbmVjZXNzYXJ5 LCB0byBkZWJ1ZyB0aGUgQ1BVIHRvcG9sb2d5Lg0KDQpVbmZvcnR1bmF0ZWx5IHdlIGFyZSBvdXJz ZWx2ZXMgb3ZlciA5MDBrbSBhd2F5IGZyb20gdGhlIHNlcnZlci4gSXQgd2FzIHNoaXBwZWQNCnRv IHRoZSBkYXRhY2VudGVyIGFuZCB3ZSBoYWQgbm8gc2lnaHQgb2YgaXQuIFdlIGhhdmUgYXNrZWQg dGhlIGd1eXMgYXQgdGhlIA0KaG9zdGluZyBjb21wYW55IHRvIGxvb2sgYXQgdGhlIEJJT1MgbGFz dCB3ZWVrIHRvIHNlZSBpZiBIVCBpcyBkaXNhYmxlZCBhbmQgdGhleQ0Kc2FpZCB0aGVyZSBpcyBu byBzdWNoIG9wdGlvbiwgb25seSB0aGUgb3B0aW9uIHRvIHR1cm4gb24vb2ZmIFZULg0KDQpUaGVp ciBUZWNobmljYWwgR3VpZGVib29rIGZvciB0aGUgUjQxMCBkb2Vzbid0IHNheSBtdWNoLCBuZWl0 aGVyDQoNCmh0dHA6Ly93d3cuZGVsbC5jb20vZG93bmxvYWRzL2dsb2JhbC9wcm9kdWN0cy9wZWRn ZS9lbi9Qb3dlckVkZ2VfUjQxMF9UZWNobmljYWxfR3VpZGVib29rLnBkZg0KDQpKdXN0IGEgbWVu dGlvbiBhYm91dCAiU2ltdWx0YW5lb3VzIE11bHRpLVRocmVhZGluZyAoU01UKSBzdXBwb3J0IiBh cyBhIGZlYXR1cmUNCm9mIHRoZSBCSU9TLiBXZSBhbHNvIGZpbmQgdGhpcyBkb2MgYWJvdXQgaG93 IHRoZXkgZW51bWVyYXRlIHRoZSBjb3JlcyBhbmQgdGhyZWFkcw0KDQpodHRwOi8vd3d3LmRlbGwu Y29tL2Rvd25sb2Fkcy9nbG9iYWwvc2hhcmVkL2R1YWxfY29yZV9kZWxsX29zLnBkZg0KDQpidXQg dGhhdCB3YXMgcHJldHR5IG9sZCBhbmQgb25seSBhcHBsaWVzIHRvIGR1YWwtY29yZS4NCg0KV2Ug d2lsbCBhc2sgdGhlIGd1eXMgYXQgdGhlIGRhdGFjZW50ZXIgdG8gY2FyZWZ1bGx5IGNoZWNrIHRo ZSBCSU9TIGFnYWluLiBMaWtlDQpJIHdyb3RlLCB3ZSBkaWRuJ3QgdG91Y2ggdGhlIHNldHRpbmdz IHByZXNldCBieSBEZWxsLg0KDQpUaGFuayB5b3UgZm9yIHlvdXIgaGVscC4NCg0KQmVzdCByZWdh cmRzLA0KSG9hbmcNCg== From owner-freebsd-hardware@FreeBSD.ORG Mon Feb 1 16:52:55 2010 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2C75C106568B for ; Mon, 1 Feb 2010 16:52:55 +0000 (UTC) (envelope-from freebsd-hardware@m.gmane.org) Received: from lo.gmane.org (lo.gmane.org [80.91.229.12]) by mx1.freebsd.org (Postfix) with ESMTP id 9CDAB8FC17 for ; Mon, 1 Feb 2010 16:52:54 +0000 (UTC) Received: from list by lo.gmane.org with local (Exim 4.69) (envelope-from ) id 1NbzW8-0004VW-IC for freebsd-hardware@freebsd.org; Mon, 01 Feb 2010 17:52:52 +0100 Received: from lara.cc.fer.hr ([161.53.72.113]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 01 Feb 2010 17:52:52 +0100 Received: from ivoras by lara.cc.fer.hr with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 01 Feb 2010 17:52:52 +0100 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-hardware@freebsd.org From: Ivan Voras Date: Mon, 01 Feb 2010 17:52:29 +0100 Lines: 42 Message-ID: References: <65BCAB515656D34AA48B0E713966CC83046A64@MBX021-E2-NJ-5.exch021.domain.local> <65BCAB515656D34AA48B0E713966CC8305F7A8@MBX021-E2-NJ-5.exch021.domain.local> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: lara.cc.fer.hr User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.1.5) Gecko/20100118 Thunderbird/3.0 In-Reply-To: <65BCAB515656D34AA48B0E713966CC8305F7A8@MBX021-E2-NJ-5.exch021.domain.local> Sender: news Subject: Re: FreeBSD 8.0, Intel Xeon E5530, Dell R410, only 2 cores available X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 01 Feb 2010 16:52:55 -0000 On 02/01/10 17:37, Hoang V.D. | Creative Solutions GmbH wrote: > Thank you. > >> -----Original Message----- >> From: owner-freebsd-hardware@freebsd.org [mailto:owner-freebsd- >> hardware@freebsd.org] On Behalf Of Ivan Voras >> Sent: Monday, February 01, 2010 3:41 PM >> To: freebsd-hardware@freebsd.org >> Subject: Re: FreeBSD 8.0, Intel Xeon E5530, Dell R410, only 2 cores available >> >> Your CPU count is wrong. The topology might be wrong for Nehalems but it >> would be wrong in a different way. >> >> Before you can debug the FreeBSD side you should first make the hw.ncpu >> setting equal the "right" total number of logical CPUs available, e.g. >> by configuring your BIOS, upgrading your BIOS, etc. >> >> After you configure your BIOS to recognize all the CPUs, you can proceed, if >> necessary, to debug the CPU topology. > > Unfortunately we are ourselves over 900km away from the server. It was shipped > to the datacenter and we had no sight of it. We have asked the guys at the > hosting company to look at the BIOS last week to see if HT is disabled and they > said there is no such option, only the option to turn on/off VT. > > Their Technical Guidebook for the R410 doesn't say much, neither > > http://www.dell.com/downloads/global/products/pedge/en/PowerEdge_R410_Technical_Guidebook.pdf > > Just a mention about "Simultaneous Multi-Threading (SMT) support" as a feature > of the BIOS. We also find this doc about how they enumerate the cores and threads > > http://www.dell.com/downloads/global/shared/dual_core_dell_os.pdf > > but that was pretty old and only applies to dual-core. > > We will ask the guys at the datacenter to carefully check the BIOS again. Like > I wrote, we didn't touch the settings preset by Dell. > > Thank you for your help. While they are checking, tell them to try and upgrade the BIOS. From owner-freebsd-hardware@FreeBSD.ORG Mon Feb 1 16:55:07 2010 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B1C271065694 for ; Mon, 1 Feb 2010 16:55:07 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id 7F8248FC16 for ; Mon, 1 Feb 2010 16:55:07 +0000 (UTC) Received: from bigwig.baldwin.cx (66.111.2.69.static.nyinternet.net [66.111.2.69]) by cyrus.watson.org (Postfix) with ESMTPSA id 1530746B23; Mon, 1 Feb 2010 11:55:07 -0500 (EST) Received: from jhbbsd.localnet (smtp.hudson-trading.com [209.249.190.9]) by bigwig.baldwin.cx (Postfix) with ESMTPA id 3FC508A01F; Mon, 1 Feb 2010 11:55:06 -0500 (EST) From: John Baldwin To: "Hoang V.D. | Creative Solutions GmbH" Date: Mon, 1 Feb 2010 11:50:31 -0500 User-Agent: KMail/1.12.1 (FreeBSD/7.2-CBSD-20100120; KDE/4.3.1; amd64; ; ) References: <65BCAB515656D34AA48B0E713966CC83046A64@MBX021-E2-NJ-5.exch021.domain.local> <201002010932.20443.jhb@freebsd.org> <65BCAB515656D34AA48B0E713966CC8305F775@MBX021-E2-NJ-5.exch021.domain.local> In-Reply-To: <65BCAB515656D34AA48B0E713966CC8305F775@MBX021-E2-NJ-5.exch021.domain.local> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201002011150.31782.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0.1 (bigwig.baldwin.cx); Mon, 01 Feb 2010 11:55:06 -0500 (EST) X-Virus-Scanned: clamav-milter 0.95.1 at bigwig.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-1.3 required=4.2 tests=AWL,BAYES_00 autolearn=ham version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on bigwig.baldwin.cx Cc: "freebsd-hardware@freebsd.org" Subject: Re: FreeBSD 8.0, Intel Xeon E5530, Dell R410, only 2 cores available X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 01 Feb 2010 16:55:07 -0000 On Monday 01 February 2010 11:14:28 am Hoang V.D. | Creative Solutions GmbH wrote: > Hello > > > -----Original Message----- > > From: John Baldwin [mailto:jhb@freebsd.org] > > Sent: Monday, February 01, 2010 3:32 PM > > To: freebsd-hardware@freebsd.org > > Cc: Hoang V.D. | Creative Solutions GmbH > > Subject: Re: FreeBSD 8.0, Intel Xeon E5530, Dell R410, only 2 cores available > > > > Can you get the output of 'acpidump -t'? Also, the 'x 2 cores x 2 SMT > > threads' bit is based on registers read from the CPU. It is really claiming > > to be a 2x2 chip (2 cores with 2 threads each). Maybe see what > > /usr/ports/misc/cpuid claims? > > > > This is the output of 'acpidump -t': > > ========================= > > It looks like all CPU above 4 are marked as "Disabled". Do "CPUs" here > mean real cores or SMT cores? Yes, they are disabled in both the APIC and SRAT (NUMA info) tables. CPUs here mean SMT threads. Effectively each logical CPU that is visible to the OS should be listed in the ACPI APIC table. > Here is the output of cpuid: > > ========================= Grr, it looks like cpuid hasn't been updated to parse the cpuid bits that tell you how many threads and cores there are for a single package, but I suspect it would tell you the same thing that FreeBSD is claiming. What does your BIOS say about the number of cores in your CPU? -- John Baldwin From owner-freebsd-hardware@FreeBSD.ORG Mon Feb 1 17:25:50 2010 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 45AF11065672; Mon, 1 Feb 2010 17:25:50 +0000 (UTC) (envelope-from hoang.v.d@creativesolutions.at) Received: from west.smtp.exch021.serverdata.net (hub021-nj-3.exch021.serverdata.net [206.225.164.218]) by mx1.freebsd.org (Postfix) with ESMTP id 05F748FC1C; Mon, 1 Feb 2010 17:25:49 +0000 (UTC) Received: from MBX021-E2-NJ-5.exch021.domain.local ([169.254.7.217]) by HUB021-NJ-3.exch021.domain.local ([10.240.4.36]) with mapi; Mon, 1 Feb 2010 09:25:49 -0800 From: "Hoang V.D. | Creative Solutions GmbH" To: "freebsd-hardware@freebsd.org" Thread-Topic: FreeBSD 8.0, Intel Xeon E5530, Dell R410, only 2 cores available Thread-Index: AcqhOrx/G8GKs9gGTfi/PH73nxAYOQCU63wAAA+3F5D//6jigIAAfzjg Date: Mon, 1 Feb 2010 17:25:45 +0000 Message-ID: <65BCAB515656D34AA48B0E713966CC8305F832@MBX021-E2-NJ-5.exch021.domain.local> References: <65BCAB515656D34AA48B0E713966CC83046A64@MBX021-E2-NJ-5.exch021.domain.local> <201002010932.20443.jhb@freebsd.org> <65BCAB515656D34AA48B0E713966CC8305F775@MBX021-E2-NJ-5.exch021.domain.local> <201002011150.31782.jhb@freebsd.org> In-Reply-To: <201002011150.31782.jhb@freebsd.org> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Cc: Ivan Voras Subject: RE: FreeBSD 8.0, Intel Xeon E5530, Dell R410, only 2 cores available X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 01 Feb 2010 17:25:50 -0000 I would like to thanks both of you John and Ivan for your assistance. We th= ink=20 we have found out the cause of the problem now, this thread from Dell's "Li= nux=20 PowerEdge" list probably explained it: http://lists.us.dell.com/pipermail/linux-poweredge/2010-January/041159.html For some weird reason Dell decided to turn off two cores per CPU by default= (not HT but real cores) for those servers. We will ask the datacenter guys to lo= ok at that specific BIOS option tomorrow and fix it. Again, many thanks from happy FreeBSD users :-) Best regards, Hoang > -----Original Message----- > From: John Baldwin [mailto:jhb@freebsd.org] > Sent: Monday, February 01, 2010 5:51 PM > To: Hoang V.D. | Creative Solutions GmbH > Cc: freebsd-hardware@freebsd.org > Subject: Re: FreeBSD 8.0, Intel Xeon E5530, Dell R410, only 2 cores avail= able >=20 > Yes, they are disabled in both the APIC and SRAT (NUMA info) tables. CPU= s > here mean SMT threads. Effectively each logical CPU that is visible to t= he > OS should be listed in the ACPI APIC table. >=20 > Grr, it looks like cpuid hasn't been updated to parse the cpuid bits that > tell you how many threads and cores there are for a single package, but I > suspect it would tell you the same thing that FreeBSD is claiming. What = does > your BIOS say about the number of cores in your CPU? >=20 > -- > John Baldwin From owner-freebsd-hardware@FreeBSD.ORG Tue Feb 2 01:14:01 2010 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5D56A106566C for ; Tue, 2 Feb 2010 01:14:01 +0000 (UTC) (envelope-from dan@grillo.net) Received: from grillo.net (adsl-69-107-204-137.dsl.pltn13.pacbell.net [69.107.204.137]) by mx1.freebsd.org (Postfix) with ESMTP id 3A0CC8FC1B for ; Tue, 2 Feb 2010 01:14:00 +0000 (UTC) Received: from more.grillo.net (localhost.grillo.net [127.0.0.1]) by grillo.net (8.14.2/8.14.2) with ESMTP id o120YXcV070748 for ; Mon, 1 Feb 2010 16:34:33 -0800 (PST) (envelope-from grio@more-enet.grillo.net) Received: (from grio@localhost) by more.grillo.net (8.14.2/8.14.2/Submit) id o120YX5i070747; Mon, 1 Feb 2010 16:34:33 -0800 (PST) (envelope-from grio) From: Dan Grillo Message-Id: <201002020034.o120YX5i070747@more.grillo.net> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Organization: President, Grillo Networking, Inc. To: "freebsd-hardware@freebsd.org" References: <65BCAB515656D34AA48B0E713966CC83046A64@MBX021-E2-NJ-5.exch021.domain.local> <201002010932.20443.jhb@freebsd.org> <65BCAB515656D34AA48B0E713966CC8305F775@MBX021-E2-NJ-5.exch021.domain.local> <201002011150.31782.jhb@freebsd.org> <65BCAB515656D34AA48B0E713966CC8305F832@MBX021-E2-NJ-5.exch021.domain.local> Date: Mon, 1 Feb 2010 16:34:33 -0800 Versions: dmail (bsd44) 2.7/makemail 2.15 Subject: FreeBSD 8.0 driver for MCS9901 based 2-port RS232 PCI-E card X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 Feb 2010 01:14:01 -0000 FreeBSDers, Has anyone gotten an MCS9901 based 2-port RS232 PCI-E card working with FreeBSD 8? The actual card is a StarTech PEX2S552. pci id from pciconf -lv looks like: none5@pci0:4:0:0: class=0x070002 card=0x1000a000 chip=0x99019710 rev=0x00 hdr=0x00 vendor = 'MosChip Semiconductors (Was: Netmos Technology)' class = simple comms subclass = UART none6@pci0:4:0:1: class=0x070002 card=0x1000a000 chip=0x99019710 rev=0x00 hdr=0x00 vendor = 'MosChip Semiconductors (Was: Netmos Technology)' class = simple comms subclass = UART I tried just dropping this into dev/puc/pucdata.c --- pucdata.c.org 2010-02-01 13:46:09.000000000 -0800 +++ pucdata.c 2010-02-01 13:47:35.000000000 -0800 @@ -790,6 +790,12 @@ PUC_PORT_2S, 0x10, 4, 0, }, + { 0x9710, 0x9901, 0x1000, 2, + "MosChip (Awas Netmos) MCS9901 based 2-port serial", + DEFAULT_RCLK, + PUC_PORT_2S, 0x10, 4, 0, + }, + { 0x9710, 0x9835, 0xffff, 0, "NetMos NM9835 Dual UART and 1284 Printer port", DEFAULT_RCLK, but no luck. Any advice you can give is appreciated. --Dan -- Dan Grillo dan@grillo.net (650) 299-1470 From owner-freebsd-hardware@FreeBSD.ORG Tue Feb 2 13:32:40 2010 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5E7631065740 for ; Tue, 2 Feb 2010 13:32:40 +0000 (UTC) (envelope-from stephane.lapie@darkbsd.org) Received: from quasar.darkbsd.org (shinigami.darkbsd.org [82.227.96.182]) by mx1.freebsd.org (Postfix) with ESMTP id 1484B8FC1B for ; Tue, 2 Feb 2010 13:32:38 +0000 (UTC) Received: from quasar.darkbsd.org (localhost [127.0.0.1]) by quasar.darkbsd.org (Postfix) with ESMTP id B5E4E175F; Tue, 2 Feb 2010 14:32:31 +0100 (CET) Received: from quasar.darkbsd.org ([127.0.0.1]) by quasar.darkbsd.org (quasar.darkbsd.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4vOcPNwNtdnm; Tue, 2 Feb 2010 14:32:29 +0100 (CET) Received: from [192.168.3.42] (archer.yomi.darkbsd.org [192.168.3.42]) (Authenticated sender: darksoul) by quasar.darkbsd.org (Postfix) with ESMTPSA id 9310C1758; Tue, 2 Feb 2010 14:32:27 +0100 (CET) Message-ID: <4B682972.6030604@darkbsd.org> Date: Tue, 02 Feb 2010 22:32:34 +0900 From: Stephane LAPIE User-Agent: Thunderbird 2.0.0.23 (X11/20090817) MIME-Version: 1.0 To: freebsd-fs@freebsd.org, freebsd-hardware@freebsd.org X-Enigmail-Version: 0.95.6 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig30EC70D03E772944CD83A3F7" Cc: Subject: [zfs][hardware] Reproducible kernel panic in 8.0-STABLE X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 Feb 2010 13:32:40 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig30EC70D03E772944CD83A3F7 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: quoted-printable Hello lists, I have a case of kernel panic that can be consistently reproduced, and=20 which I guess is related to the hardware I'm using (Marvell controllers, = check my pciconf -lv output below). The kernel panic message is always, consistently, the following : Sleeping thread (tid 100021, pid 0) owns a non-sleepable lock in the following cases (both on Marvell PCI-X SATA controllers) : - Bad disk failing one too much DMA read/flush/write and getting=20 disconnected by the system (it has SMART indicators reporting at least=20 200 bad sectors, and still rising weekly); This is how I noticed it. - When I simply unplug one disk, to replace it. It should also be noted=20 my system freezes upon atacontrol reinit'ing the concerned ata channel. Unplugging for instance an USB drive that belongs to the pool doesn't=20 provoke this effect. Just sharing in case there is anyone here who could provide pointers or=20 insight. Thanks for your time, --> ZFS pool structure : NAME STATE READ WRITE CKSUM prana DEGRADED 0 0 0 raidz1 DEGRADED 0 0 0 spare DEGRADED 0 0 0 ad16 ONLINE 0 0 0 ad16 ONLINE 0 0 0 ad30 ONLINE 0 0 0 ad28 ONLINE 0 0 0 ad18 ONLINE 0 0 0 ad14 ONLINE 0 0 0 raidz1 ONLINE 0 0 0 ad26 ONLINE 0 0 0 ad4 ONLINE 0 0 0 ad6 ONLINE 0 0 0 ad8 ONLINE 0 0 0 ad10 ONLINE 0 0 0 raidz1 ONLINE 0 0 0 ad20 ONLINE 0 0 0 ad22 ONLINE 0 0 0 ad24 ONLINE 0 0 0 ad32 ONLINE 0 0 0 ad34 ONLINE 0 0 0 cache ad12 ONLINE 0 0 0 ad37 ONLINE 0 0 0 spares da0 AVAIL da1 AVAIL --> pciconf -lv output : hostb0@pci0:0:0:0: class=3D0x060000 card=3D0xd98015d9 chip=3D0x29e08086=20 rev=3D0x01 hdr=3D0x00 vendor =3D 'Intel Corporation' device =3D 'X38/X48 (Bearlake) Processor to I/O Controller' class =3D bridge subclass =3D HOST-PCI pcib1@pci0:0:6:0: class=3D0x060400 card=3D0xd98015d9 chip=3D0x29e98086=20 rev=3D0x01 hdr=3D0x01 vendor =3D 'Intel Corporation' device =3D 'X38/X48 (Bearlake) PCIe Root Port 2' class =3D bridge subclass =3D PCI-PCI em2@pci0:0:25:0: class=3D0x020000 card=3D0x10bd15d9 chip=3D0x10bd8086 rev= =3D0x02=20 hdr=3D0x00 vendor =3D 'Intel Corporation' device =3D 'Intel 82566DM Gigabit Ethernet Adapter (82566DM)' class =3D network subclass =3D ethernet uhci0@pci0:0:26:0: class=3D0x0c0300 card=3D0xd98015d9 chip=3D0x29378086=20 rev=3D0x02 hdr=3D0x00 vendor =3D 'Intel Corporation' device =3D '82801IB/IR/IH (ICH9 Family) USB Universal Host=20 Controller' class =3D serial bus subclass =3D USB uhci1@pci0:0:26:1: class=3D0x0c0300 card=3D0xd98015d9 chip=3D0x29388086=20 rev=3D0x02 hdr=3D0x00 vendor =3D 'Intel Corporation' device =3D '82801IB/IR/IH (ICH9 Family) USB Universal Host=20 Controller' class =3D serial bus subclass =3D USB uhci2@pci0:0:26:2: class=3D0x0c0300 card=3D0xd98015d9 chip=3D0x29398086=20 rev=3D0x02 hdr=3D0x00 vendor =3D 'Intel Corporation' device =3D '82801IB/IR/IH (ICH9 Family) USB Universal Host=20 Controller' class =3D serial bus subclass =3D USB ehci0@pci0:0:26:7: class=3D0x0c0320 card=3D0xd98015d9 chip=3D0x293c8086=20 rev=3D0x02 hdr=3D0x00 vendor =3D 'Intel Corporation' device =3D '82801IB/IR/IH (ICH9 Family) USB2 Enhanced Host=20 Controller' class =3D serial bus subclass =3D USB pcib4@pci0:0:28:0: class=3D0x060400 card=3D0xd98015d9 chip=3D0x29408086=20 rev=3D0x02 hdr=3D0x01 vendor =3D 'Intel Corporation' device =3D '82801IB/IR/IH (ICH9 Family) PCIe Root Port 1' class =3D bridge subclass =3D PCI-PCI uhci3@pci0:0:29:0: class=3D0x0c0300 card=3D0xd98015d9 chip=3D0x29348086=20 rev=3D0x02 hdr=3D0x00 vendor =3D 'Intel Corporation' device =3D '82801IB/IR/IH (ICH9 Family) USB Universal Host=20 Controller' class =3D serial bus subclass =3D USB uhci4@pci0:0:29:1: class=3D0x0c0300 card=3D0xd98015d9 chip=3D0x29358086=20 rev=3D0x02 hdr=3D0x00 vendor =3D 'Intel Corporation' device =3D '82801IB/IR/IH (ICH9 Family) USB Universal Host=20 Controller' class =3D serial bus subclass =3D USB uhci5@pci0:0:29:2: class=3D0x0c0300 card=3D0xd98015d9 chip=3D0x29368086=20 rev=3D0x02 hdr=3D0x00 vendor =3D 'Intel Corporation' device =3D '82801IB/IR/IH (ICH9 Family) USB Universal Host=20 Controller' class =3D serial bus subclass =3D USB ehci1@pci0:0:29:7: class=3D0x0c0320 card=3D0xd98015d9 chip=3D0x293a8086=20 rev=3D0x02 hdr=3D0x00 vendor =3D 'Intel Corporation' device =3D '82801IB/IR/IH (ICH9 Family) USB2 Enhanced Host=20 Controller' class =3D serial bus subclass =3D USB pcib6@pci0:0:30:0: class=3D0x060401 card=3D0xd98015d9 chip=3D0x244e8086=20 rev=3D0x92 hdr=3D0x01 vendor =3D 'Intel Corporation' device =3D '82801 Family (ICH2/3/4/5/6/7/8/9,63xxESB) Hub=20 Interface to PCI Bridge' class =3D bridge subclass =3D PCI-PCI isab0@pci0:0:31:0: class=3D0x060100 card=3D0xd98015d9 chip=3D0x29168086=20 rev=3D0x02 hdr=3D0x00 vendor =3D 'Intel Corporation' device =3D '82801IR (ICH9R) LPC Interface Controller' class =3D bridge subclass =3D PCI-ISA ahci0@pci0:0:31:2: class=3D0x010601 card=3D0xd98015d9 chip=3D0x29228086=20 rev=3D0x02 hdr=3D0x00 vendor =3D 'Intel Corporation' device =3D '82801IB/IR/IH (ICH9 Family) 6 port SATA AHCI Control= ler' class =3D mass storage subclass =3D SATA ichsmb0@pci0:0:31:3: class=3D0x0c0500 card=3D0xd98015d9 chip=3D0x29308086= =20 rev=3D0x02 hdr=3D0x00 vendor =3D 'Intel Corporation' device =3D '82801IB/IR/IH (ICH9 Family) SMBus Controller' class =3D serial bus subclass =3D SMBus none0@pci0:0:31:6: class=3D0x118000 card=3D0x000015d9 chip=3D0x29328086=20 rev=3D0x02 hdr=3D0x00 vendor =3D 'Intel Corporation' device =3D '82801IB/IR/IH (ICH9 Family) Thermal Subsystem' class =3D dasp pcib2@pci0:3:0:0: class=3D0x060400 card=3D0x00000000 chip=3D0x03408086=20 rev=3D0x09 hdr=3D0x01 vendor =3D 'Intel Corporation' device =3D '41210 [Lanai] Serial to Parallel PCI Bridge A-segmen= t=20 Bridge' class =3D bridge subclass =3D PCI-PCI pcib3@pci0:3:0:2: class=3D0x060400 card=3D0x00000000 chip=3D0x03418086=20 rev=3D0x09 hdr=3D0x01 vendor =3D 'Intel Corporation' device =3D '41210 [Lanai] Serial to Parallel PCI Bridge B-segmen= t=20 Bridge' class =3D bridge subclass =3D PCI-PCI em0@pci0:4:4:0: class=3D0x020000 card=3D0x108a8086 chip=3D0x108a8086 rev=3D= 0x03=20 hdr=3D0x00 vendor =3D 'Intel Corporation' device =3D 'PRO/1000 P' class =3D network subclass =3D ethernet em1@pci0:4:4:1: class=3D0x020000 card=3D0x108a8086 chip=3D0x108a8086 rev=3D= 0x03=20 hdr=3D0x00 vendor =3D 'Intel Corporation' device =3D 'PRO/1000 P' class =3D network subclass =3D ethernet pcib5@pci0:6:0:0: class=3D0x060400 card=3D0x00000000 chip=3D0x032c8086=20 rev=3D0x09 hdr=3D0x01 vendor =3D 'Intel Corporation' device =3D 'PCI Express-to-PCI Express Bridge (6702PXH)' class =3D bridge subclass =3D PCI-PCI ioapic0@pci0:6:0:1: class=3D0x080020 card=3D0xd98015d9 chip=3D0x03268086 = rev=3D0x09 hdr=3D0x00 vendor =3D 'Intel Corporation' device =3D '6700/6702PXH I/OxAPIC Interrupt Controller A' class =3D base peripheral subclass =3D interrupt controller atapci0@pci0:7:1:0: class=3D0x010000 card=3D0x11ab11ab chip=3D0x608111ab = rev=3D0x09 hdr=3D0x00 vendor =3D 'Marvell Semiconductor (Was: Galileo Technology Ltd)'= device =3D 'MV88SX6081 8-port SATA II PCI-X Controller' class =3D mass storage subclass =3D SCSI atapci1@pci0:7:7:0: class=3D0x010000 card=3D0x11ab11ab chip=3D0x608111ab = rev=3D0x09 hdr=3D0x00 vendor =3D 'Marvell Semiconductor (Was: Galileo Technology Ltd)'= device =3D 'MV88SX6081 8-port SATA II PCI-X Controller' class =3D mass storage subclass =3D SCSI em3@pci0:17:0:0: class=3D0x020000 card=3D0x10128086 chip=3D0x10128086 rev= =3D0x01=20 hdr=3D0x00 vendor =3D 'Intel Corporation' device =3D 'Dual Port Gigabit Ethernet Controller (Fiber) (82546= EB)' class =3D network subclass =3D ethernet em4@pci0:17:0:1: class=3D0x020000 card=3D0x10128086 chip=3D0x10128086 rev= =3D0x01=20 hdr=3D0x00 vendor =3D 'Intel Corporation' device =3D 'Dual Port Gigabit Ethernet Controller (Fiber) (82546= EB)' class =3D network subclass =3D ethernet vgapci0@pci0:17:1:0: class=3D0x030000 card=3D0x63261039 chip=3D0x63261039= =20 rev=3D0x0b hdr=3D0x00 vendor =3D 'Silicon Integrated Systems (SiS)' device =3D 'SiS6326 GUI Accelerator' class =3D display subclass =3D VGA fwohci0@pci0:17:3:0: class=3D0x0c0010 card=3D0xba8015d9 chip=3D0x8023104c= =20 rev=3D0x00 hdr=3D0x00 vendor =3D 'Texas Instruments (TI)' device =3D 'IEEE1394a-2000 OHCI PHY/Link-Layer Ctrlr (TSB43AB21/= A)' class =3D serial bus subclass =3D FireWire atapci2@pci0:17:4:0: class=3D0x010185 card=3D0x82131283 chip=3D0x82131283= =20 rev=3D0x00 hdr=3D0x00 vendor =3D 'Integrated Technology Express (ITE) Inc' device =3D 'IDE Controller (IT8213F)' class =3D mass storage subclass =3D ATA --> dmesg output : Copyright (c) 1992-2010 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 8.0-STABLE #11: Thu Jan 14 21:05:32 JST 2010 =20 darksoul@eirei-no-za.yomi.darkbsd.org:/usr/storage/tech/eirei-no-za.yomi.= darkbsd.org/usr/obj/usr/storage/tech/eirei-no-za.yomi.darkbsd.org/usr/src= /sys/DARK-2009KERN=20 amd64 Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Intel(R) Core(TM)2 Quad CPU Q9400 @ 2.66GHz (2666.68-MHz=20 K8-class CPU) Origin =3D "GenuineIntel" Id =3D 0x1067a Stepping =3D 10 =20 Features=3D0xbfebfbff =20 Features2=3D0x408e3fd AMD Features=3D0x20100800 AMD Features2=3D0x1 TSC: P-state invariant real memory =3D 8589934592 (8192 MB) avail memory =3D 8257941504 (7875 MB) ACPI APIC Table: FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs FreeBSD/SMP: 1 package(s) x 4 core(s) cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 cpu2 (AP): APIC ID: 2 cpu3 (AP): APIC ID: 3 ioapic0 irqs 0-23 on motherboard ioapic1 irqs 24-47 on motherboard kbd1 at kbdmux0 ichwd module loaded iscsi: version 2.1.0 acpi0: on motherboard acpi0: [ITHREAD] acpi0: Power Button (fixed) Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x1008-0x100b on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 pcib1: irq 16 at device 6.0 on pci0 pci3: on pcib1 pcib2: at device 0.0 on pci3 pci4: on pcib2 em0: port 0x2000-0x203f=20 mem 0xdfd80000-0xdfd9ffff,0xdfd00000-0xdfd3ffff irq 16 at device 4.0 on p= ci4 em0: [FILTER] em0: Ethernet address: 00:0e:0c:70:7d:1e em1: port 0x2040-0x207f=20 mem 0xdfda0000-0xdfdbffff,0xdfd40000-0xdfd7ffff irq 17 at device 4.1 on p= ci4 em1: [FILTER] em1: Ethernet address: 00:0e:0c:70:7d:1f pcib3: at device 0.2 on pci3 pci5: on pcib3 em2: port 0x1820-0x183f=20 mem 0xdff00000-0xdff1ffff,0xdff20000-0xdff20fff irq 16 at device 25.0 on = pci0 em2: Using MSI interrupt em2: [FILTER] em2: Ethernet address: 00:30:48:de:84:88 uhci0: port 0x1840-0x185f irq 16 at = device 26.0 on pci0 uhci0: [ITHREAD] usbus0: on uhci0 uhci1: port 0x1860-0x187f irq 17 at = device 26.1 on pci0 uhci1: [ITHREAD] usbus1: on uhci1 uhci2: port 0x1880-0x189f irq 18 at = device 26.2 on pci0 uhci2: [ITHREAD] usbus2: on uhci2 ehci0: mem=20 0xdff22800-0xdff22bff irq 18 at device 26.7 on pci0 ehci0: [ITHREAD] usbus3: EHCI version 1.0 usbus3: on ehci0 pcib4: irq 16 at device 28.0 on pci0 pci6: on pcib4 pcib5: at device 0.0 on pci6 pci7: on pcib5 atapci0: port 0x3000-0x30ff mem=20 0xdf200000-0xdf2fffff irq 24 at device 1.0 on pci7 atapci0: [ITHREAD] ata2: on atapci0 ata2: [ITHREAD] ata3: on atapci0 ata3: [ITHREAD] ata4: on atapci0 ata4: [ITHREAD] ata5: on atapci0 ata5: [ITHREAD] ata6: on atapci0 ata6: [ITHREAD] ata7: on atapci0 ata7: [ITHREAD] ata8: on atapci0 ata8: [ITHREAD] ata9: on atapci0 ata9: [ITHREAD] atapci1: port 0x3400-0x34ff mem=20 0xdf300000-0xdf3fffff irq 28 at device 7.0 on pci7 atapci1: [ITHREAD] ata10: on atapci1 ata10: [ITHREAD] ata11: on atapci1 ata11: [ITHREAD] ata12: on atapci1 ata12: [ITHREAD] ata13: on atapci1 ata13: [ITHREAD] ata14: on atapci1 ata14: [ITHREAD] ata15: on atapci1 ata15: [ITHREAD] ata16: on atapci1 ata16: [ITHREAD] ata17: on atapci1 ata17: [ITHREAD] uhci3: port 0x18a0-0x18bf irq 23 at = device 29.0 on pci0 uhci3: [ITHREAD] usbus4: on uhci3 uhci4: port 0x18c0-0x18df irq 22 at = device 29.1 on pci0 uhci4: [ITHREAD] usbus5: on uhci4 uhci5: port 0x18e0-0x18ff irq 18 at = device 29.2 on pci0 uhci5: [ITHREAD] usbus6: on uhci5 ehci1: mem=20 0xdff22c00-0xdff22fff irq 23 at device 29.7 on pci0 ehci1: [ITHREAD] usbus7: EHCI version 1.0 usbus7: on ehci1 pcib6: at device 30.0 on pci0 pci17: on pcib6 em3: port 0x4080-0x40bf=20 mem 0xdfe00000-0xdfe1ffff irq 20 at device 0.0 on pci17 em3: [FILTER] em3: Ethernet address: 00:07:e9:0f:a3:80 em4: port 0x40c0-0x40ff=20 mem 0xdfe20000-0xdfe3ffff irq 21 at device 0.1 on pci17 em4: [FILTER] em4: Ethernet address: 00:07:e9:0f:a3:81 vgapci0: port 0x4000-0x407f mem=20 0xde800000-0xdeffffff,0xdfe40000-0xdfe4ffff at device 1.0 on pci17 fwohci0: mem=20 0xdfe54000-0xdfe547ff,0xdfe50000-0xdfe53fff irq 22 at device 3.0 on pci17= fwohci0: [ITHREAD] fwohci0: OHCI version 1.10 (ROM=3D1) fwohci0: No. of Isochronous channels is 4. fwohci0: EUI64 00:30:48:00:00:20:42:f6 fwohci0: Phy 1394a available S400, 2 ports. fwohci0: Link S400, max_rec 2048 bytes. firewire0: on fwohci0 fwe0: on firewire0 if_fwe0: Fake Ethernet address: 02:30:48:20:42:f6 fwe0: Ethernet address: 02:30:48:20:42:f6 fwip0: on firewire0 fwip0: Firewire address: 00:30:48:00:00:20:42:f6 @ 0xfffe00000000, S400, = maxrec 2048 dcons_crom0: on firewire0 dcons_crom0: bus_addr 0x799820 fwohci0: Initiate bus reset fwohci0: fwohci_intr_core: BUS reset fwohci0: fwohci_intr_core: node_id=3D0x00000000, SelfID Count=3D1,=20 CYCLEMASTER mode atapci2: port=20 0x4420-0x4427,0x4414-0x4417,0x4418-0x441f,0x4410-0x4413,0x4400-0x440f=20 irq 23 at device 4.0 on pci17 atapci2: [ITHREAD] ata18: on atapci2 ata18: [ITHREAD] isab0: at device 31.0 on pci0 isa0: on isab0 ahci0: port=20 0x1c70-0x1c77,0x1c64-0x1c67,0x1c68-0x1c6f,0x1c60-0x1c63,0x1c00-0x1c1f=20 mem 0xdff22000-0xdff227ff irq 17 at device 31.2 on pci0 ahci0: [ITHREAD] ahci0: AHCI v1.20 with 6 3Gbps ports, Port Multiplier supported ahcich0: at channel 0 on ahci0 ahcich0: [ITHREAD] ahcich1: at channel 1 on ahci0 ahcich1: [ITHREAD] ahcich2: at channel 2 on ahci0 ahcich2: [ITHREAD] ahcich3: at channel 3 on ahci0 ahcich3: [ITHREAD] ahcich4: at channel 4 on ahci0 ahcich4: [ITHREAD] ahcich5: at channel 5 on ahci0 ahcich5: [ITHREAD] ichsmb0: port 0x1100-0x111f mem=20 0xdff23000-0xdff230ff irq 17 at device 31.3 on pci0 ichsmb0: [ITHREAD] smbus0: on ichsmb0 smb0: on smbus0 pci0: at device 31.6 (no driver attached) acpi_button0: on acpi0 atrtc0: port 0x70-0x71 irq 8 on acpi0 atkbdc0: port 0x60,0x64 irq 1 on acpi0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] atkbd0: [ITHREAD] uart0: <16550 or compatible> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 uart0: [FILTER] uart0: console (115200,n,8,1) uart1: <16550 or compatible> port 0x2f8-0x2ff irq 3 on acpi0 uart1: [FILTER] cpu0: on acpi0 coretemp0: on cpu0 est0: on cpu0 p4tcc0: on cpu0 cpu1: on acpi0 coretemp1: on cpu1 est1: on cpu1 p4tcc1: on cpu1 cpu2: on acpi0 coretemp2: on cpu2 est2: on cpu2 p4tcc2: on cpu2 cpu3: on acpi0 coretemp3: on cpu3 est3: on cpu3 p4tcc3: on cpu3 ichwd0: on isa0 ichwd0: Intel ICH9R watchdog timer (ICH9 or equivalent) orm0: at iomem=20 0xc0000-0xc7fff,0xc8000-0xc8fff,0xc9000-0xcf7ff,0xcf800-0xd5fff on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=3D0x300> vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0= ZFS filesystem version 14 ZFS storage pool version 14 Timecounters tick every 1.000 msec Waiting 5 seconds for SCSI devices to settle firewire0: 1 nodes, maxhop <=3D 0 cable IRM irm(0) (me) firewire0: bus manager 0 usbus0: 12Mbps Full Speed USB v1.0 usbus1: 12Mbps Full Speed USB v1.0 usbus2: 12Mbps Full Speed USB v1.0 usbus3: 480Mbps High Speed USB v2.0 usbus4: 12Mbps Full Speed USB v1.0 usbus5: 12Mbps Full Speed USB v1.0 usbus6: 12Mbps Full Speed USB v1.0 usbus7: 480Mbps High Speed USB v2.0 ugen0.1: at usbus0 uhub0: on usbus0 ugen1.1: at usbus1 uhub1: on usbus1 ugen2.1: at usbus2 uhub2: on usbus2 ugen3.1: at usbus3 uhub3: on usbus3 ugen4.1: at usbus4 uhub4: on usbus4 ugen5.1: at usbus5 uhub5: on usbus5 ugen6.1: at usbus6 uhub6: on usbus6 ugen7.1: at usbus7 uhub7: on usbus7 ad4: 1430799MB at ata2-master UDMA100 SATA 3G= b/s ad6: 1430799MB at ata3-master UDMA100 SATA 3G= b/s ad8: 1430799MB at ata4-master UDMA100 SATA 3G= b/s ad10: 1430799MB at ata5-master UDMA100 SATA=20 3Gb/s ad12: 61136MB at ata6-master UDMA100 SATA 3Gb/s uhub0: 2 ports with 2 removable, self powered uhub1: 2 ports with 2 removable, self powered uhub2: 2 ports with 2 removable, self powered uhub4: 2 ports with 2 removable, self powered uhub5: 2 ports with 2 removable, self powered uhub6: 2 ports with 2 removable, self powered ad14: 1430799MB at ata7-master UDMA100 SATA=20 3Gb/s ad16: 1430799MB at ata8-master UDMA100 SATA=20 3Gb/s ad18: 1430799MB at ata9-master UDMA100 SATA=20 3Gb/s ad20: 1430799MB at ata10-master UDMA100 SATA = 3Gb/s ad22: 1430799MB at ata11-master UDMA100 SATA = 3Gb/s ad24: 1430799MB at ata12-master UDMA100 SATA = 3Gb/s ad26: 1430799MB at ata13-master UDMA100 SATA = 3Gb/s ad28: 1430799MB at ata14-master UDMA100 SATA = 3Gb/s ad30: 1430799MB at ata15-master UDMA100 SATA = 3Gb/s ad32: 1430799MB at ata16-master UDMA100 SATA = 3Gb/s ad34: 1430799MB at ata17-master UDMA100 SATA = 3Gb/s ata18: DMA limited to UDMA33, controller found non-ATA66 cable ad36: 3823MB at ata18-master UDMA33 ad37: 61136MB at ata18-slave UDMA133 uhub3: 6 ports with 6 removable, self powered uhub7: 6 ports with 6 removable, self powered ugen0.2: at usbus0 uhub8: on usb= us0 SMP: AP CPU #1 Launched! SMP: AP CPU #2 Launched! SMP: AP CPU #3 Launched! Trying to mount root from zfs:prana uhub8: 3 ports with 2 removable, bus powered ugen0.3: at usbus0 ukbd0: =20 on usbus0 kbd2 at ukbd0 em1: link state changed to UP em0: link state changed to UP ad36: FAILURE - SMART status=3D51 error=3D4 ugen7.2: at usbus7 uhub9: on=20 usbus7 uhub9: 4 ports with 4 removable, self powered ugen7.3: at usbus7 uhub10: on=20 usbus7 uhub10: 4 ports with 4 removable, self powered ugen7.4: at usbus7 umass0: on usbus7 umass0: SCSI over Bulk-Only; quirks =3D 0x0000 umass0:6:0:-1: Attached to scbus6 da0 at umass-sim0 bus 0 scbus6 target 0 lun 0 da0: Fixed Direct Access SCSI-4 device da0: 40.000MB/s transfers da0: 1430799MB (2930277168 512 byte sectors: 255H 63S/T 182401C) --=20 Stephane LAPIE, EPITA SRS, Promo 2005 "Even when they have digital readouts, I can't understand them." --MegaTokyo --------------enig30EC70D03E772944CD83A3F7 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAktoKXYACgkQ24Ql8u6TF2MnggCg4yC6QL/HesQUk9VreOfbBd8g XXMAnivUDonClpkmbv1dxbWB8NAw674v =Jp8W -----END PGP SIGNATURE----- --------------enig30EC70D03E772944CD83A3F7-- From owner-freebsd-hardware@FreeBSD.ORG Tue Feb 2 13:57:02 2010 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AF4CB1065698; Tue, 2 Feb 2010 13:57:02 +0000 (UTC) (envelope-from avg@icyb.net.ua) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id A679D8FC13; Tue, 2 Feb 2010 13:57:01 +0000 (UTC) Received: from odyssey.starpoint.kiev.ua (alpha-e.starpoint.kiev.ua [212.40.38.101]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id PAA16976; Tue, 02 Feb 2010 15:56:57 +0200 (EET) (envelope-from avg@icyb.net.ua) Message-ID: <4B682F29.90505@icyb.net.ua> Date: Tue, 02 Feb 2010 15:56:57 +0200 From: Andriy Gapon User-Agent: Thunderbird 2.0.0.23 (X11/20091206) MIME-Version: 1.0 To: Stephane LAPIE References: <4B682972.6030604@darkbsd.org> In-Reply-To: <4B682972.6030604@darkbsd.org> X-Enigmail-Version: 0.95.7 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: freebsd-fs@freebsd.org, freebsd-hardware@freebsd.org Subject: Re: [zfs][hardware] Reproducible kernel panic in 8.0-STABLE X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 Feb 2010 13:57:02 -0000 on 02/02/2010 15:32 Stephane LAPIE said the following: > I have a case of kernel panic that can be consistently reproduced, and > which I guess is related to the hardware I'm using (Marvell controllers, > check my pciconf -lv output below). > > The kernel panic message is always, consistently, the following : > > Sleeping thread (tid 100021, pid 0) owns a non-sleepable lock I probably won't be able to help you, but to kickstart debugging could you please run 'procstat -t 0' and determine what kernel thread has tid 100021 on your system? -- Andriy Gapon From owner-freebsd-hardware@FreeBSD.ORG Tue Feb 2 14:04:08 2010 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 20B42106566B; Tue, 2 Feb 2010 14:04:08 +0000 (UTC) (envelope-from stephane.lapie@darkbsd.org) Received: from quasar.darkbsd.org (shinigami.darkbsd.org [82.227.96.182]) by mx1.freebsd.org (Postfix) with ESMTP id C7BDB8FC29; Tue, 2 Feb 2010 14:04:07 +0000 (UTC) Received: from quasar.darkbsd.org (localhost [127.0.0.1]) by quasar.darkbsd.org (Postfix) with ESMTP id 50C141797; Tue, 2 Feb 2010 15:04:01 +0100 (CET) Received: from quasar.darkbsd.org ([127.0.0.1]) by quasar.darkbsd.org (quasar.darkbsd.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1Y+82KTzNtJr; Tue, 2 Feb 2010 15:03:59 +0100 (CET) Received: from [192.168.3.42] (archer.yomi.darkbsd.org [192.168.3.42]) (Authenticated sender: darksoul) by quasar.darkbsd.org (Postfix) with ESMTPSA id E885F178F; Tue, 2 Feb 2010 15:03:57 +0100 (CET) Message-ID: <4B6830CF.9070102@darkbsd.org> Date: Tue, 02 Feb 2010 23:03:59 +0900 From: Stephane LAPIE User-Agent: Thunderbird 2.0.0.23 (X11/20090817) MIME-Version: 1.0 To: Andriy Gapon References: <4B682972.6030604@darkbsd.org> <4B682F29.90505@icyb.net.ua> In-Reply-To: <4B682F29.90505@icyb.net.ua> X-Enigmail-Version: 0.95.6 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enigB7914B7431170113956FAFAA" Cc: freebsd-fs@freebsd.org, freebsd-hardware@freebsd.org Subject: Re: [zfs][hardware] Reproducible kernel panic in 8.0-STABLE X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 Feb 2010 14:04:08 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigB7914B7431170113956FAFAA Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: quoted-printable Andriy Gapon wrote: > on 02/02/2010 15:32 Stephane LAPIE said the following: >> I have a case of kernel panic that can be consistently reproduced, and= >> which I guess is related to the hardware I'm using (Marvell controller= s, >> check my pciconf -lv output below). >> >> The kernel panic message is always, consistently, the following : >> >> Sleeping thread (tid 100021, pid 0) owns a non-sleepable lock >=20 > I probably won't be able to help you, but to kickstart debugging could = you please > run 'procstat -t 0' and determine what kernel thread has tid 100021 on = your system? Thanks for the tip. I will keep that one in mind, as I was wondering how = you looked up individual threads. # procstat -t 0 | grep 100021 0 100021 kernel thread taskq 1 92 sleep - Is that the "kernel task queue" handler ? --=20 Stephane LAPIE, EPITA SRS, Promo 2005 "Even when they have digital readouts, I can't understand them." --MegaTokyo --------------enigB7914B7431170113956FAFAA Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAktoMNgACgkQ24Ql8u6TF2PRWwCfW0dbLdl/RD5Jw1qMRZ6Ys064 Zd0AnjTX6k5k1XERp0WZuHJBYjDzKuiw =SCJh -----END PGP SIGNATURE----- --------------enigB7914B7431170113956FAFAA-- From owner-freebsd-hardware@FreeBSD.ORG Tue Feb 2 14:36:12 2010 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 24241106568F for ; Tue, 2 Feb 2010 14:36:12 +0000 (UTC) (envelope-from tanel.rebane@itassistans.se) Received: from server7.serverdrift.com (server7.serverdrift.com [91.201.60.40]) by mx1.freebsd.org (Postfix) with ESMTP id 8C8058FC2A for ; Tue, 2 Feb 2010 14:36:11 +0000 (UTC) Received: from [212.112.191.34] (helo=itassistans.se) by server7.serverdrift.com with esmtpsa (TLSv1:RC4-MD5:128) (Exim 4.69) (envelope-from ) id 1NcHZb-0007DG-4V for freebsd-hardware@freebsd.org; Tue, 02 Feb 2010 13:09:39 +0100 X-MDAV-Processed: itassistans.se, Tue, 02 Feb 2010 13:09:28 +0100 Received: from NCSE-A001-VM.ad.nc.com by itassistans.se (Cipher TLSv1:RC4-MD5:128) (MDaemon PRO v10.1.2) with ESMTP id md50000354334.msg for ; Tue, 02 Feb 2010 13:09:27 +0100 X-Spam-Processed: itassistans.se, Tue, 02 Feb 2010 13:09:27 +0100 (not processed: message from trusted or authenticated source) X-MDPtrLookup-Result: pass dns.ptr=212-181-5-100.customer.telia.com (ip=212.181.5.100) (itassistans.se) X-MDHeloLookup-Result: hardfail smtp.helo=NCSE-A001-VM.ad.nc.com (does not match 212.181.5.100) (itassistans.se) X-Authenticated-Sender: tanel.rebane@itassistans.se X-MDRemoteIP: 212.181.5.100 X-Return-Path: tanel.rebane@itassistans.se X-Envelope-From: tanel.rebane@itassistans.se X-MDaemon-Deliver-To: freebsd-hardware@freebsd.org Date: Tue, 02 Feb 2010 13:11:00 +0100 From: "Tanel Rebane" To: "'freebsd-hardware@freebsd.org'" Message-ID: X-Priority: 3 Organization: IT-Assistans Sverige AB X-Mailer: Outlook Connector for MDaemon 2.2.3 MIME-Version: 1.0 X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - server7.serverdrift.com X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - itassistans.se Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Status on LSI SAS2008? X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Tanel Rebane List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 Feb 2010 14:36:12 -0000 Hello, =20 Does anyone know the status of the LSI SAS2008 chipset in regards to FreeBS= D? If any, I suppose it=92s the mfi(4)-driver that should pick up support. = I know the LSI SAS2108 should work fine with mfi(4) but I have no idea how = big the differences between 2008 and 2108 are. =20 All feedback is valued, thanks in advance! =20 Best regards, Tanel Rebane =20 P.S: Please CC me as I=92m not subscribed to the list. From owner-freebsd-hardware@FreeBSD.ORG Tue Feb 2 15:23:36 2010 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 29B161065672 for ; Tue, 2 Feb 2010 15:23:36 +0000 (UTC) (envelope-from michael@fuckner.net) Received: from dedihh.fuckner.net (dedihh.fuckner.net [81.209.183.161]) by mx1.freebsd.org (Postfix) with ESMTP id AF2148FC16 for ; Tue, 2 Feb 2010 15:23:35 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by dedihh.fuckner.net (Postfix) with ESMTP id BF2E515AC5; Tue, 2 Feb 2010 16:06:51 +0100 (CET) X-Virus-Scanned: amavisd-new at example.com Received: from dedihh.fuckner.net ([127.0.0.1]) by localhost (dedihh.fuckner.net [127.0.0.1]) (amavisd-new, port 10024) with SMTP id 3CWJGonYtqBb; Tue, 2 Feb 2010 16:06:47 +0100 (CET) Received: from fuckner2.delnet (unknown [85.183.0.20]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by dedihh.fuckner.net (Postfix) with ESMTPSA id CE72915AB4; Tue, 2 Feb 2010 16:06:46 +0100 (CET) Message-ID: <4B683F37.4040807@fuckner.net> Date: Tue, 02 Feb 2010 16:05:27 +0100 From: Michael Fuckner User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.1.7) Gecko/20100122 Thunderbird/3.0.1 MIME-Version: 1.0 To: Tanel Rebane References: In-Reply-To: Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: quoted-printable Cc: "'freebsd-hardware@freebsd.org'" Subject: Re: Status on LSI SAS2008? X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 Feb 2010 15:23:36 -0000 On 02/02/10 13:11, Tanel Rebane wrote: > Does anyone know the status of the LSI SAS2008 chipset in regards to > FreeBSD? If any, I suppose it=92s the mfi(4)-driver that should pick u= p > support. I know the LSI SAS2108 should work fine with mfi(4) but I > have no idea how big the differences between 2008 and 2108 are. Hi all, I've been running those cards on Linux. The 2008-Chip is an HBA-Chip. Linux uses the mpt2sas Driver (the old=20 HBAs are using mptsas). The 2108 is the Raid-Chip using the megaraid_sas or 3w-sas driver=20 (depending on the firmware installed- LSI 9261-8i and 3ware 9750-8i seem=20 to have identical Hardware. Regards, Michael! From owner-freebsd-hardware@FreeBSD.ORG Tue Feb 2 15:50:55 2010 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7DBAE1065670; Tue, 2 Feb 2010 15:50:55 +0000 (UTC) (envelope-from avg@icyb.net.ua) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id 901278FC16; Tue, 2 Feb 2010 15:50:54 +0000 (UTC) Received: from odyssey.starpoint.kiev.ua (alpha-e.starpoint.kiev.ua [212.40.38.101]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id RAA19204; Tue, 02 Feb 2010 17:50:50 +0200 (EET) (envelope-from avg@icyb.net.ua) Message-ID: <4B6849DA.5080303@icyb.net.ua> Date: Tue, 02 Feb 2010 17:50:50 +0200 From: Andriy Gapon User-Agent: Thunderbird 2.0.0.23 (X11/20091206) MIME-Version: 1.0 To: Stephane LAPIE References: <4B682972.6030604@darkbsd.org> <4B682F29.90505@icyb.net.ua> <4B6830CF.9070102@darkbsd.org> In-Reply-To: <4B6830CF.9070102@darkbsd.org> X-Enigmail-Version: 0.95.7 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: freebsd-fs@freebsd.org, freebsd-hardware@freebsd.org Subject: Re: [zfs][hardware] Reproducible kernel panic in 8.0-STABLE X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 Feb 2010 15:50:55 -0000 on 02/02/2010 16:03 Stephane LAPIE said the following: > Andriy Gapon wrote: >> on 02/02/2010 15:32 Stephane LAPIE said the following: >>> I have a case of kernel panic that can be consistently reproduced, and >>> which I guess is related to the hardware I'm using (Marvell controllers, >>> check my pciconf -lv output below). >>> >>> The kernel panic message is always, consistently, the following : >>> >>> Sleeping thread (tid 100021, pid 0) owns a non-sleepable lock >> >> I probably won't be able to help you, but to kickstart debugging could >> you please >> run 'procstat -t 0' and determine what kernel thread has tid 100021 on >> your system? > > Thanks for the tip. I will keep that one in mind, as I was wondering how > you looked up individual threads. > > # procstat -t 0 | grep 100021 > 0 100021 kernel thread taskq 1 92 sleep - > > Is that the "kernel task queue" handler ? This taskqueue "taskqueue_thread" which is used to schedule tasks in many places. I would guess that one of those tasks leaked a lock. Probably it's best to configure system for crashdumps to a reliable storage and then try to examine a dump with kgdb to see what lock we have here. -- Andriy Gapon From owner-freebsd-hardware@FreeBSD.ORG Tue Feb 2 17:43:01 2010 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 178DB106566B; Tue, 2 Feb 2010 17:43:01 +0000 (UTC) (envelope-from avg@icyb.net.ua) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id 2801E8FC2A; Tue, 2 Feb 2010 17:42:59 +0000 (UTC) Received: from odyssey.starpoint.kiev.ua (alpha-e.starpoint.kiev.ua [212.40.38.101]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id TAA20962; Tue, 02 Feb 2010 19:42:54 +0200 (EET) (envelope-from avg@icyb.net.ua) Message-ID: <4B68641D.9000201@icyb.net.ua> Date: Tue, 02 Feb 2010 19:42:53 +0200 From: Andriy Gapon User-Agent: Thunderbird 2.0.0.23 (X11/20091206) MIME-Version: 1.0 To: Julian Elischer References: <4B682972.6030604@darkbsd.org> <4B682F29.90505@icyb.net.ua> <4B686324.2090308@elischer.org> In-Reply-To: <4B686324.2090308@elischer.org> X-Enigmail-Version: 0.95.7 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: freebsd-fs@freebsd.org, Stephane LAPIE , freebsd-hardware@freebsd.org Subject: Re: [zfs][hardware] Reproducible kernel panic in 8.0-STABLE X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 Feb 2010 17:43:01 -0000 on 02/02/2010 19:38 Julian Elischer said the following: > Andriy Gapon wrote: >> on 02/02/2010 15:32 Stephane LAPIE said the following: >>> I have a case of kernel panic that can be consistently reproduced, and >>> which I guess is related to the hardware I'm using (Marvell controllers, >>> check my pciconf -lv output below). >>> >>> The kernel panic message is always, consistently, the following : >>> >>> Sleeping thread (tid 100021, pid 0) owns a non-sleepable lock >> >> I probably won't be able to help you, but to kickstart debugging could >> you please >> run 'procstat -t 0' and determine what kernel thread has tid 100021 on >> your system? > > or in the kernel debugger after the panic, do: bt I think that in this case it may not help. I mean the stack trace. Because, I think that this panic happens after the taskqueue thread is done with its tasks and is parked waiting. > you DO have options kdb and ddb right? (I never leave home without them) > -- Andriy Gapon From owner-freebsd-hardware@FreeBSD.ORG Tue Feb 2 18:18:48 2010 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 15ACA1065670; Tue, 2 Feb 2010 18:18:48 +0000 (UTC) (envelope-from julian@elischer.org) Received: from utility-0.aerioconnect.net (outu.internet-mail-service.net [216.240.47.244]) by mx1.freebsd.org (Postfix) with ESMTP id C253B8FC0C; Tue, 2 Feb 2010 18:18:47 +0000 (UTC) Received: from idiom.com (mx0.idiom.com [216.240.32.160]) by utility-0.aerioconnect.net (8.13.1/8.13.1) with ESMTP id o12HcCdw019434; Tue, 2 Feb 2010 09:38:12 -0800 X-Client-Authorized: MaGic Cook1e X-Client-Authorized: MaGic Cook1e X-Client-Authorized: MaGic Cook1e X-Client-Authorized: MaGic Cook1e Received: from julian-mac.elischer.org (h-67-100-89-137.snfccasy.static.covad.net [67.100.89.137]) by idiom.com (Postfix) with ESMTP id C3A692D601B; Tue, 2 Feb 2010 09:38:11 -0800 (PST) Message-ID: <4B686324.2090308@elischer.org> Date: Tue, 02 Feb 2010 09:38:44 -0800 From: Julian Elischer User-Agent: Thunderbird 2.0.0.23 (Macintosh/20090812) MIME-Version: 1.0 To: Andriy Gapon References: <4B682972.6030604@darkbsd.org> <4B682F29.90505@icyb.net.ua> In-Reply-To: <4B682F29.90505@icyb.net.ua> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-fs@freebsd.org, Stephane LAPIE , freebsd-hardware@freebsd.org Subject: Re: [zfs][hardware] Reproducible kernel panic in 8.0-STABLE X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 Feb 2010 18:18:48 -0000 Andriy Gapon wrote: > on 02/02/2010 15:32 Stephane LAPIE said the following: >> I have a case of kernel panic that can be consistently reproduced, and >> which I guess is related to the hardware I'm using (Marvell controllers, >> check my pciconf -lv output below). >> >> The kernel panic message is always, consistently, the following : >> >> Sleeping thread (tid 100021, pid 0) owns a non-sleepable lock > > I probably won't be able to help you, but to kickstart debugging could you please > run 'procstat -t 0' and determine what kernel thread has tid 100021 on your system? or in the kernel debugger after the panic, do: bt you DO have options kdb and ddb right? (I never leave home without them) From owner-freebsd-hardware@FreeBSD.ORG Wed Feb 3 11:23:19 2010 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 098FA1065676; Wed, 3 Feb 2010 11:23:19 +0000 (UTC) (envelope-from stephane.lapie@darkbsd.org) Received: from quasar.darkbsd.org (shinigami.darkbsd.org [82.227.96.182]) by mx1.freebsd.org (Postfix) with ESMTP id 98F138FC1B; Wed, 3 Feb 2010 11:23:18 +0000 (UTC) Received: from quasar.darkbsd.org (localhost [127.0.0.1]) by quasar.darkbsd.org (Postfix) with ESMTP id 840151CFF; Wed, 3 Feb 2010 12:23:11 +0100 (CET) Received: from quasar.darkbsd.org ([127.0.0.1]) by quasar.darkbsd.org (quasar.darkbsd.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id n6qkRDKXiBJV; Wed, 3 Feb 2010 12:23:09 +0100 (CET) Received: from [192.168.3.42] (archer.yomi.darkbsd.org [192.168.3.42]) (Authenticated sender: darksoul) by quasar.darkbsd.org (Postfix) with ESMTPSA id 9E9211CF8; Wed, 3 Feb 2010 12:23:07 +0100 (CET) Message-ID: <4B695CA3.50008@darkbsd.org> Date: Wed, 03 Feb 2010 20:23:15 +0900 From: Stephane LAPIE User-Agent: Thunderbird 2.0.0.23 (X11/20090817) MIME-Version: 1.0 To: Andriy Gapon References: <4B682972.6030604@darkbsd.org> <4B682F29.90505@icyb.net.ua> <4B686324.2090308@elischer.org> <4B68641D.9000201@icyb.net.ua> In-Reply-To: <4B68641D.9000201@icyb.net.ua> X-Enigmail-Version: 0.95.6 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig9026C478EB31D9AA9953CE13" Cc: freebsd-fs@freebsd.org, Julian Elischer , freebsd-hardware@freebsd.org Subject: Re: [zfs][hardware] Reproducible kernel panic in 8.0-STABLE X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 Feb 2010 11:23:19 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig9026C478EB31D9AA9953CE13 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: quoted-printable Andriy Gapon wrote: > on 02/02/2010 19:38 Julian Elischer said the following: >> Andriy Gapon wrote: >>> on 02/02/2010 15:32 Stephane LAPIE said the following: >>>> I have a case of kernel panic that can be consistently reproduced, a= nd >>>> which I guess is related to the hardware I'm using (Marvell controll= ers, >>>> check my pciconf -lv output below). >>>> >>>> The kernel panic message is always, consistently, the following : >>>> >>>> Sleeping thread (tid 100021, pid 0) owns a non-sleepable lock >>> I probably won't be able to help you, but to kickstart debugging coul= d >>> you please >>> run 'procstat -t 0' and determine what kernel thread has tid 100021 o= n >>> your system? >> or in the kernel debugger after the panic, do: bt >=20 > I think that in this case it may not help. I mean the stack trace. > Because, I think that this panic happens after the taskqueue thread is = done with > its tasks and is parked waiting. >=20 >> you DO have options kdb and ddb right? (I never leave home without th= em) >> >=20 >=20 I just rebuilt a kernel with debugger options, and obtained the=20 following output upon pulling out one disk : Sleeping thread (tid 100024, pid 0) owns a non-sleepable lock sched_switch() at sched_switch+0xf8 mi_switch() at mi_switch+0x16f sleepq_timedwait() at sleepq_timedwait+0x42 _cv_timedwait() at _cv_timedwait+0x129 _sema_timedwait() at _sema_timedwait+0x55 ata_queue_request() at ata_queue_request+0x526 ata_controlcmd() at ata_controlcmd+0xa1 ata_setmode() at ata_setmode+0xdc ad_init() at ad_init+0x27 ad_reinit() at ad_reinit+0x48 ata_reinit() at ata_reinit+0x268 ata_conn_event() at ata_conn_event+0x49 taskqueue_run() at taskqueue_run+0x93 taskqueue_thread_loop() at taskqueue_thread_loop+0x46 fork_exit() at fork_exit+0x118 fork_trampoline() at fork_trampoline+0xe --- trap 0, rip =3D 0, rsp =3D 0xffffff80000aad30, rbp =3D 0 --- panic: sleeping thread cpuid =3D 2 KDB: enter: panic [thread pid 12 tid 100008 ] Stopped at kdb_enter+0x3d: movq $0,0x4943d0(%rip) I think the output below is not really relevant though. db> bt Tracing pid 12 tid 100008 td 0xffffff000187e000 kdb_enter() at kdb_enter+0x3d panic() at panic+0x17b turnstile_adjust() at turnstile_adjust turnstile_wait() at turnstile_wait+0x1aa _mtx_lock_sleep() at _mtx_lock_sleep+0xb0 softclock() at softclock+0x2a9 intr_event_execute_handlers() at intr_event_execute_handlers+0xfd ithread_loop() at ithread_loop+0x8e fork_exit() at fork_exit+0x118 fork_trampoline() at fork_trampoline+0xe --- trap 0, rip =3D 0, rsp =3D 0xffffff800005ad30, rbp =3D 0 --- If there is anything else I can run to obtain further information, all=20 hints are welcome, though this clearly seems to point to a problem with=20 my controller event handling as I initially thought. I am also very suspicious of that controller because it tends to drop=20 two disks at exactly the same time, which alas belong to the same raidz1 = block (BIOS level can't reset properly the port or redetect them after=20 this, I have to go through a cold boot; The disks themselves could be=20 damaged but I don't catch any weird readings via SMART and Reallocated=20 Sectors or such). I am seriously thinking of moving some of these disks=20 to the AHCI controller on my motherboard, and will resort to using my=20 spares at the very least in the meantime. Thanks for your time, --=20 Stephane LAPIE, EPITA SRS, Promo 2005 "Even when they have digital readouts, I can't understand them." --MegaTokyo --------------enig9026C478EB31D9AA9953CE13 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAktpXKkACgkQ24Ql8u6TF2PafgCg0KHN21iTsRKK5bicKqrVo4Rv E68AoKFECb7szXCvNUWvk7k40dKfMI5r =URPh -----END PGP SIGNATURE----- --------------enig9026C478EB31D9AA9953CE13-- From owner-freebsd-hardware@FreeBSD.ORG Thu Feb 4 22:46:12 2010 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 81B401065695; Thu, 4 Feb 2010 22:46:12 +0000 (UTC) (envelope-from avg@icyb.net.ua) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id 5919A8FC1E; Thu, 4 Feb 2010 22:46:11 +0000 (UTC) Received: from porto.topspin.kiev.ua (porto-e.starpoint.kiev.ua [212.40.38.100]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id AAA02408; Fri, 05 Feb 2010 00:46:07 +0200 (EET) (envelope-from avg@icyb.net.ua) Received: from localhost.topspin.kiev.ua ([127.0.0.1]) by porto.topspin.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1NdASd-0004N1-2x; Fri, 05 Feb 2010 00:46:07 +0200 Message-ID: <4B6B4E2E.2010902@icyb.net.ua> Date: Fri, 05 Feb 2010 00:46:06 +0200 From: Andriy Gapon User-Agent: Thunderbird 2.0.0.23 (X11/20091128) MIME-Version: 1.0 To: Stephane LAPIE References: <4B682972.6030604@darkbsd.org> <4B682F29.90505@icyb.net.ua> <4B686324.2090308@elischer.org> <4B68641D.9000201@icyb.net.ua> <4B695CA3.50008@darkbsd.org> In-Reply-To: <4B695CA3.50008@darkbsd.org> X-Enigmail-Version: 0.96.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: freebsd-fs@freebsd.org, freebsd-stable@freebsd.org, Julian Elischer , freebsd-hardware@freebsd.org Subject: Re: [zfs][hardware] Reproducible kernel panic in 8.0-STABLE X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 Feb 2010 22:46:12 -0000 on 03/02/2010 13:23 Stephane LAPIE said the following: > > I just rebuilt a kernel with debugger options, and obtained the > following output upon pulling out one disk : > > Sleeping thread (tid 100024, pid 0) owns a non-sleepable lock > sched_switch() at sched_switch+0xf8 > mi_switch() at mi_switch+0x16f > sleepq_timedwait() at sleepq_timedwait+0x42 > _cv_timedwait() at _cv_timedwait+0x129 > _sema_timedwait() at _sema_timedwait+0x55 > ata_queue_request() at ata_queue_request+0x526 > ata_controlcmd() at ata_controlcmd+0xa1 > ata_setmode() at ata_setmode+0xdc > ad_init() at ad_init+0x27 > ad_reinit() at ad_reinit+0x48 > ata_reinit() at ata_reinit+0x268 > ata_conn_event() at ata_conn_event+0x49 > taskqueue_run() at taskqueue_run+0x93 > taskqueue_thread_loop() at taskqueue_thread_loop+0x46 > fork_exit() at fork_exit+0x118 > fork_trampoline() at fork_trampoline+0xe > --- trap 0, rip = 0, rsp = 0xffffff80000aad30, rbp = 0 --- > panic: sleeping thread > cpuid = 2 > KDB: enter: panic > [thread pid 12 tid 100008 ] > Stopped at kdb_enter+0x3d: movq $0,0x4943d0(%rip) Not sure if I can derive anything useful from here. Someone with more expertise is needed. One thing I noticed is that ata_conn_event and ata_reinit and some other functions up the stack acquire state_mtx recursively, but the mutex is not initialized with MTX_RECURSE. Perhaps, indeed you would have a better luck with AHCI controller _and_ ahci(4) driver. It seems to handle dynamic coming and going of disks much better than ata(4). -- Andriy Gapon