From owner-freebsd-hardware@FreeBSD.ORG Mon Jan 27 11:06:47 2014 Return-Path: Delivered-To: freebsd-hardware@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 71FA1C49 for ; Mon, 27 Jan 2014 11:06:47 +0000 (UTC) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 3E2011A84 for ; Mon, 27 Jan 2014 11:06:47 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.7/8.14.7) with ESMTP id s0RB6l57013003 for ; Mon, 27 Jan 2014 11:06:47 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.7/8.14.7/Submit) id s0RB6khi013001 for freebsd-hardware@FreeBSD.org; Mon, 27 Jan 2014 11:06:46 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 27 Jan 2014 11:06:46 GMT Message-Id: <201401271106.s0RB6khi013001@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: gnats set sender to owner-bugmaster@FreeBSD.org using -f From: FreeBSD bugmaster To: freebsd-hardware@FreeBSD.org Subject: Current problem reports assigned to freebsd-hardware@FreeBSD.org X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Jan 2014 11:06:47 -0000 Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- f kern/156241 hardware [mfi] 'zfs send' does not prevents disks to suspend if 1 problem total. From owner-freebsd-hardware@FreeBSD.ORG Wed Jan 29 17:03:07 2014 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 1447C23C for ; Wed, 29 Jan 2014 17:03:07 +0000 (UTC) Received: from mail-qc0-x236.google.com (mail-qc0-x236.google.com [IPv6:2607:f8b0:400d:c01::236]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id CA20D1FCB for ; Wed, 29 Jan 2014 17:03:06 +0000 (UTC) Received: by mail-qc0-f182.google.com with SMTP id c9so3101942qcz.41 for ; Wed, 29 Jan 2014 09:03:05 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=aMfhqGqrkzG5V6VVGWMYyX/AJwIbptvdBfAet3A+T1k=; b=O+BupR2nse+tJOxgh+gQRCIMK24ylanuPmV4YfrafRaSy81enjyDZqgbS/goqqkqGg 896b1vE25U30aCt6GDI2JbooJ59l4+P5lBoTa5cxqhvQKknQMfVj5jDarB2abZbpXhT8 74Mp+GmoWAvaCviTTKLtULMK8VrFD2yUzGmY2NjpoI4bgCr+EoGUrY7wU/chKZS81LrW Kq2qCyGtkTR4/gbzgerzVe+r8QsIlKie+zWDKwBqBH0Tb2xZfiPePJZXmg/QcjgHY214 grnl5SOjckpyox5FcV5tZ9qnlxLA6yaJlHWYKVH6YRaQXiYzEN+NSt4BYuKt13Hvex6V E5xg== MIME-Version: 1.0 X-Received: by 10.224.46.130 with SMTP id j2mr13799956qaf.7.1391014985845; Wed, 29 Jan 2014 09:03:05 -0800 (PST) Received: by 10.96.143.5 with HTTP; Wed, 29 Jan 2014 09:03:05 -0800 (PST) In-Reply-To: References: Date: Wed, 29 Jan 2014 18:03:05 +0100 Message-ID: Subject: Fwd: Regarding ses in FreeBSD 9.2 From: Joar Jegleim To: freebsd-hardware@freebsd.org Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 Jan 2014 17:03:07 -0000 Forgive me for cross-listing, this one was initially sent to questions. Hardware seem to be more accurate . See bellow regarding my issue, I get those once every minute. The messages seem to be from ses0, which according to man ses is 'SCSI Environmental Services driver' . Does anybody know any utility I can use against the ses SCSI Environmental Services driver (?) ---------- Forwarded message ---------- From: Joar Jegleim Date: 27 January 2014 13:33 Subject: Regarding ses in FreeBSD 9.2 To: freebsd-questions Hi, I just upgraded a server from 9.1-RELEASE -> 9.2-RELEASE I noticed I get these about once every minute in /var/log/messages, as well as to the console: Jan 27 13:26:11 store01 kernel: ses0: pass25,ses0: SAS Device Slot Element: 1 Phys at Slot 23, Not All Phys Jan 27 13:26:11 store01 kernel: ses0: phy 0: SAS device type 0 id 0 Jan 27 13:26:11 store01 kernel: ses0: phy 0: protocols: Initiator( None ) Target( None ) Jan 27 13:26:11 store01 kernel: ses0: phy 0: parent 5001438017e2f4ff addr 0 Jan 27 13:26:11 store01 kernel: ses0: pass25,ses0: SAS Device Slot Element: 1 Phys at Slot 24, Not All Phys Jan 27 13:26:11 store01 kernel: ses0: phy 0: SAS device type 0 id 0 Jan 27 13:26:11 store01 kernel: ses0: phy 0: protocols: Initiator( None ) Target( None ) Jan 27 13:26:11 store01 kernel: ses0: phy 0: parent 5001438017e2f4ff addr 0 Jan 27 13:26:11 store01 kernel: ses0: pass25,ses0: Element descriptor: '900080050002' Jan 27 13:26:11 store01 kernel: ses0: pass25,ses0: SAS Expander: 36 Physses0: phy 0: connector 26 other 1 Jan 27 13:26:11 store01 kernel: ses0: phy 1: connector 27 other 2 Jan 27 13:26:11 store01 kernel: ses0: phy 2: connector 28 other 3 Jan 27 13:26:11 store01 kernel: ses0: phy 3: connector 29 other 4 Jan 27 13:26:11 store01 kernel: ses0: phy 4: connector 30 other 5 Jan 27 13:26:11 store01 kernel: ses0: phy 5: connector 31 other 6 Jan 27 13:26:11 store01 kernel: ses0: phy 6: connector 32 other 7 Jan 27 13:26:11 store01 kernel: ses0: phy 7: connector 33 other 8 Jan 27 13:26:11 store01 kernel: ses0: phy 8: connector 34 other 9 Jan 27 13:26:11 store01 kernel: ses0: phy 9: connector 35 other 10 Jan 27 13:26:11 store01 kernel: ses0: phy 10: connector 36 other 11 Jan 27 13:26:11 store01 kernel: ses0: phy 11: connector 37 other 12 Jan 27 13:26:11 store01 kernel: ses0: phy 12: connector 38 other 13 Jan 27 13:26:11 store01 kernel: ses0: phy 13: connector 39 other 14 Jan 27 13:26:11 store01 kernel: ses0: phy 14: connector 40 other 15 Jan 27 13:26:11 store01 kernel: ses0: phy 15: connector 41 other 16 Jan 27 13:26:11 store01 kernel: ses0: phy 16: connector 42 other 17 Jan 27 13:26:11 store01 kernel: ses0: phy 17: connector 43 other 18 Jan 27 13:26:11 store01 kernel: ses0: phy 18: connector 44 other 19 Jan 27 13:26:11 store01 kernel: ses0: phy 19: connector 45 other 20 Jan 27 13:26:11 store01 kernel: ses0: phy 20: connector 46 other 21 Jan 27 13:26:12 store01 kernel: ses0: phy 21: connector 47 other 22 Jan 27 13:26:12 store01 kernel: ses0: phy 22: connector 48 other 23 Jan 27 13:26:12 store01 kernel: ses0: phy 23: connector 49 other 24 Jan 27 13:26:12 store01 kernel: ses0: phy 24: connector 50 other 25 Jan 27 13:26:12 store01 kernel: ses0: phy 25: connector 59 other 255 Jan 27 13:26:12 store01 kernel: ses0: phy 26: connector 60 other 255 Jan 27 13:26:12 store01 kernel: ses0: phy 27: connector 61 other 255 Jan 27 13:26:12 store01 kernel: ses0: phy 28: connector 62 other 255 Jan 27 13:26:12 store01 kernel: ses0: phy 29: connector 63 other 255 Jan 27 13:26:12 store01 kernel: ses0: phy 30: connector 64 other 255 Jan 27 13:26:12 store01 kernel: ses0: phy 31: connector 65 other 255 Jan 27 13:26:12 store01 kernel: ses0: phy 32: connector 66 other 255 Jan 27 13:26:12 store01 kernel: ses0: phy 33: connector 255 other 255 Jan 27 13:26:12 store01 kernel: ses0: phy 34: connector 255 other 255 Jan 27 13:26:12 store01 kernel: ses0: phy 35: connector 255 other 255 I suspect it has something to to with an LSI HBA I've installed on that box, LSI SAS 9207-4i4e SGL The card was installed and ran on the 9.1-RELEASE install, and ses didn't post those messages then ... Does anyone know if these messages are to worry about ? and how I may stop them ? The LSI card is connected via external sas to an MSA storage shelf with 20 midline disks + 2 ssd disks + one sas disk. -- ---------------------- Joar Jegleim Homepage: http://cosmicb.no Linkedin: http://no.linkedin.com/in/joarjegleim fb: http://www.facebook.com/joar.jegleim AKA: CosmicB @Freenode ---------------------- -- ---------------------- Joar Jegleim Homepage: http://cosmicb.no Linkedin: http://no.linkedin.com/in/joarjegleim fb: http://www.facebook.com/joar.jegleim AKA: CosmicB @Freenode ---------------------- From owner-freebsd-hardware@FreeBSD.ORG Wed Jan 29 19:03:43 2014 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 482EF63B for ; Wed, 29 Jan 2014 19:03:43 +0000 (UTC) Received: from mo6-p00-ob.smtp.rzone.de (mo6-p00-ob.smtp.rzone.de [IPv6:2a01:238:20a:202:5300::11]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id CE8361A67 for ; Wed, 29 Jan 2014 19:03:42 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; t=1391022218; l=240; s=domk; d=fuckner.net; h=Content-Transfer-Encoding:Content-Type:In-Reply-To:References: Subject:To:MIME-Version:From:Date:X-RZG-CLASS-ID:X-RZG-AUTH; bh=2UCWJ3VaPNOCnP+V8xsHZpppGfo=; b=oA/rVQ8H5p3E3/BkvGloVqWTGXzHMVsOpG/q4SxPQRK7xDwY7feZRRIYwFsFw42A3cx /8gy4ZEBUVTSBvyxQfv01EdUZMR/hfU+xWM3f4R3UNHVzHepmGdk1yOHkrtLaS7x39ZLt e0ikuHOQJObCWmWhAK/X9Dnx5VE5L2VUSQc= X-RZG-AUTH: :IWUHfUGtd9+6EujMWHx57N4dWae4bmTL/JIGbzkGUoozgk+7q1hCDwOT55I33ZuV X-RZG-CLASS-ID: mo00 Received: from [10.1.2.128] (port-54838.pppoe.wtnet.de [46.59.214.229]) by smtp.strato.de (RZmta 32.22 DYNA|AUTH) with ESMTPSA id j07a1fq0TJ3SUBQ (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) for ; Wed, 29 Jan 2014 20:03:28 +0100 (CET) Message-ID: <52E95082.2070807@fuckner.net> Date: Wed, 29 Jan 2014 20:03:30 +0100 From: Michael Fuckner User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 MIME-Version: 1.0 To: freebsd-hardware@freebsd.org Subject: Re: Fwd: Regarding ses in FreeBSD 9.2 References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 Jan 2014 19:03:43 -0000 On 1/29/2014 6:03 PM, Joar Jegleim wrote: > Does anybody know any utility I can use against the ses SCSI > Environmental Services driver (?) > sysutils/sg3_utils should do, but long time since I last did. Kind regards, Michael! From owner-freebsd-hardware@FreeBSD.ORG Wed Jan 29 23:49:30 2014 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 103DFDFB; Wed, 29 Jan 2014 23:49:30 +0000 (UTC) Received: from ozzie.tundraware.com (ozzie.tundraware.com [75.145.138.73]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id BA9B1159B; Wed, 29 Jan 2014 23:49:29 +0000 (UTC) Received: from [192.168.0.2] (viper.tundraware.com [192.168.0.2]) (authenticated bits=0) by ozzie.tundraware.com (8.14.7/8.14.7) with ESMTP id s0TNnLfu024480 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Wed, 29 Jan 2014 17:49:21 -0600 (CST) (envelope-from tundra@tundraware.com) Message-ID: <52E99381.5050803@tundraware.com> Date: Wed, 29 Jan 2014 17:49:21 -0600 From: Tim Daneliuk User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 MIME-Version: 1.0 To: freebsd-stable@freebsd.org, FreeBSD Hardware Mailing List Subject: Need Help With MCA Code References: <52E73717.3000503@tundraware.com> In-Reply-To: <52E73717.3000503@tundraware.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.4.3 (ozzie.tundraware.com [75.145.138.73]); Wed, 29 Jan 2014 17:49:21 -0600 (CST) X-TundraWare-MailScanner-Information: Please contact the ISP for more information X-TundraWare-MailScanner-ID: s0TNnLfu024480 X-TundraWare-MailScanner: Found to be clean X-TundraWare-MailScanner-From: tundra@tundraware.com X-Spam-Status: No X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 Jan 2014 23:49:30 -0000 Resending in hopes that people on one of the other lists will have some insight here: On 01/27/2014 10:50 PM, Tim Daneliuk wrote: > I am running 9.2 stable i386 r261207. As noted earlier: > >> I just replaced mobo/CPU on FBSD server (Gigabyte Z-87-D3HP with >> an Intel i3-4130). I am not overclocking ... but I continue to see this sort of thing: > >> MCA: CPU 0 COR (1) internal parity error > > Dmesg shows: > >> MCA: Vendor "GenuineIntel", ID 0x306c3, APIC ID 0 >> MCA: CPU 0 COR (1) internal parity error >> MCA: Bank 0, Status 0x90000040000f0005 >> MCA: Global Cap 0x0000000000000c07, Status 0x0000000000000000_ > > I've swapped CPUs (i5). I've fiddled with an endless supply of > mobo settings. I've switched power supplies. I've moved mem > sticks around .... No joy. > > So, I dug through the sources and found this: > > > > mca_log(const struct mca_record *rec) > { > uint16_t mca_error; > > printf("MCA: Bank %d, Status 0x%016llx\n", rec->mr_bank, > (long long)rec->mr_status); > printf("MCA: Global Cap 0x%016llx, Status 0x%016llx\n", > (long long)rec->mr_mcg_cap, (long long)rec->mr_mcg_status); > printf("MCA: Vendor \"%s\", ID 0x%x, APIC ID %d\n", cpu_vendor, > rec->mr_cpu_id, rec->mr_apic_id); > printf("MCA: CPU %d ", rec->mr_cpu); > if (rec->mr_status & MC_STATUS_UC) > printf("UNCOR "); > else { > printf("COR "); > if (rec->mr_mcg_cap & MCG_CAP_CMCI_P) > printf("(%lld) ", ((long long)rec->mr_status & > MC_STATUS_COR_COUNT) >> 38); > } > > > It looks like the trailing else clause is kicking out the error but I am > unclear what the error means, beyond the fact that it appears to be a parity > error somewhere within the CPU's internal memory (cache?). Is this error > getting corrected? Is this benign, Should I get a different mobo? > > Um .... Haaaaalp :) I have now tried different motherboards, CPUs, memory, and power supplies and this error is still showing up now and then. This points strongly to either FreeBSD bogus reporting, or these errors being benign. It's hard to believe that the exact same error might occur with completely different hardware ... unless it's being caused by the case. -- ---------------------------------------------------------------------------- Tim Daneliuk tundra@tundraware.com PGP Key: http://www.tundraware.com/PGP/ From owner-freebsd-hardware@FreeBSD.ORG Thu Jan 30 18:32:42 2014 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id B9910A41 for ; Thu, 30 Jan 2014 18:32:42 +0000 (UTC) Received: from mail-qc0-x236.google.com (mail-qc0-x236.google.com [IPv6:2607:f8b0:400d:c01::236]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 77B091861 for ; Thu, 30 Jan 2014 18:32:42 +0000 (UTC) Received: by mail-qc0-f182.google.com with SMTP id c9so5583517qcz.27 for ; Thu, 30 Jan 2014 10:32:41 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=xFEHW/Ttny8a8nEYU1uaqRpwSWl7cwDiQBg+CLOfBH0=; b=R1OFxx/+hUr8JGtHlkw4YQMHxM9BRFIToqOPtSTHl/mbP/jQEerM0nbc7LgahmtyNa BoLRRV/ouUnfTpDVSPf5ZU6gRwoZUZ9AIjWV+5qkUAQdQiBvUHsYyVyYQyAtmQFItYt0 WwPxJ4G9P9SCRIDHiwasM8NdQlh3Tj+bDZyBTQyK50Mnvhbr62ud+Yks8va6KKd+vwNq wY3lUDtrcVqxBk/1J69XeJUMQqviOMKP+BAaXJceTGXAZfZDrgd0QjVo889wxIs1cjEV 8uqnsLrHH3Q5YjcGEyHZPhx0DkODJp5fLnZggT20ctyod/BXIGjcxhdBkTectsLH12ad gJPQ== MIME-Version: 1.0 X-Received: by 10.224.80.8 with SMTP id r8mr24707118qak.88.1391106761165; Thu, 30 Jan 2014 10:32:41 -0800 (PST) Received: by 10.96.143.5 with HTTP; Thu, 30 Jan 2014 10:32:41 -0800 (PST) In-Reply-To: <52E95082.2070807@fuckner.net> References: <52E95082.2070807@fuckner.net> Date: Thu, 30 Jan 2014 19:32:41 +0100 Message-ID: Subject: Re: Fwd: Regarding ses in FreeBSD 9.2 From: Joar Jegleim To: Michael Fuckner Content-Type: text/plain; charset=UTF-8 Cc: freebsd-hardware@freebsd.org X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Jan 2014 18:32:42 -0000 okay, thnx Michael, I'll check it out On 29 January 2014 20:03, Michael Fuckner wrote: > On 1/29/2014 6:03 PM, Joar Jegleim wrote: > >> Does anybody know any utility I can use against the ses SCSI >> Environmental Services driver (?) >> > sysutils/sg3_utils should do, but long time since I last did. > > Kind regards, > Michael! > _______________________________________________ > freebsd-hardware@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hardware > To unsubscribe, send any mail to "freebsd-hardware-unsubscribe@freebsd.org" -- ---------------------- Joar Jegleim Homepage: http://cosmicb.no Linkedin: http://no.linkedin.com/in/joarjegleim fb: http://www.facebook.com/joar.jegleim AKA: CosmicB @Freenode ---------------------- From owner-freebsd-hardware@FreeBSD.ORG Fri Jan 31 17:26:06 2014 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 5BA6CBE2; Fri, 31 Jan 2014 17:26:06 +0000 (UTC) Received: from bigwig.baldwin.cx (bigwig.baldwin.cx [IPv6:2001:470:1f11:75::1]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 325401615; Fri, 31 Jan 2014 17:26:06 +0000 (UTC) Received: from jhbbsd.localnet (unknown [209.249.190.124]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id 1E4DCB945; Fri, 31 Jan 2014 12:26:05 -0500 (EST) From: John Baldwin To: freebsd-stable@freebsd.org Subject: Re: Need Help With MCA Code Date: Fri, 31 Jan 2014 12:22:12 -0500 User-Agent: KMail/1.13.5 (FreeBSD/8.4-CBSD-20130906; KDE/4.5.5; amd64; ; ) References: <52E73717.3000503@tundraware.com> <52E99381.5050803@tundraware.com> In-Reply-To: <52E99381.5050803@tundraware.com> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201401311222.12136.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (bigwig.baldwin.cx); Fri, 31 Jan 2014 12:26:05 -0500 (EST) Cc: Tim Daneliuk , FreeBSD Hardware Mailing List X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 31 Jan 2014 17:26:06 -0000 On Wednesday, January 29, 2014 6:49:21 pm Tim Daneliuk wrote: > Resending in hopes that people on one of the other lists will have some insight here: > > On 01/27/2014 10:50 PM, Tim Daneliuk wrote: > > I am running 9.2 stable i386 r261207. As noted earlier: > > > >> I just replaced mobo/CPU on FBSD server (Gigabyte Z-87-D3HP with > >> an Intel i3-4130). I am not overclocking ... but I continue to see this sort of thing: > > > >> MCA: CPU 0 COR (1) internal parity error > > > > Dmesg shows: > > > >> MCA: Vendor "GenuineIntel", ID 0x306c3, APIC ID 0 > >> MCA: CPU 0 COR (1) internal parity error > >> MCA: Bank 0, Status 0x90000040000f0005 > >> MCA: Global Cap 0x0000000000000c07, Status 0x0000000000000000_ > > > > I've swapped CPUs (i5). I've fiddled with an endless supply of > > mobo settings. I've switched power supplies. I've moved mem > > sticks around .... No joy. > > > > So, I dug through the sources and found this: > > > > > > > > mca_log(const struct mca_record *rec) > > { > > uint16_t mca_error; > > > > printf("MCA: Bank %d, Status 0x%016llx\n", rec->mr_bank, > > (long long)rec->mr_status); > > printf("MCA: Global Cap 0x%016llx, Status 0x%016llx\n", > > (long long)rec->mr_mcg_cap, (long long)rec->mr_mcg_status); > > printf("MCA: Vendor \"%s\", ID 0x%x, APIC ID %d\n", cpu_vendor, > > rec->mr_cpu_id, rec->mr_apic_id); > > printf("MCA: CPU %d ", rec->mr_cpu); > > if (rec->mr_status & MC_STATUS_UC) > > printf("UNCOR "); > > else { > > printf("COR "); > > if (rec->mr_mcg_cap & MCG_CAP_CMCI_P) > > printf("(%lld) ", ((long long)rec->mr_status & > > MC_STATUS_COR_COUNT) >> 38); > > } > > > > > > It looks like the trailing else clause is kicking out the error but I am > > unclear what the error means, beyond the fact that it appears to be a parity > > error somewhere within the CPU's internal memory (cache?). Is this error > > getting corrected? Is this benign, Should I get a different mobo? > > > > Um .... Haaaaalp :) > > > I have now tried different motherboards, CPUs, memory, and power supplies and > this error is still showing up now and then. > > This points strongly to either FreeBSD bogus reporting, or these errors being > benign. It's hard to believe that the exact same error might occur with > completely different hardware ... unless it's being caused by the case. Are they all the same model CPU? Since it is a corrected error you can probably ignore it, but it is not bogus reporting. FreeBSD only reports these errors because they show up in registers on your CPU. -- John Baldwin From owner-freebsd-hardware@FreeBSD.ORG Fri Jan 31 17:49:06 2014 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 1C26AD6E; Fri, 31 Jan 2014 17:49:06 +0000 (UTC) Received: from ozzie.tundraware.com (ozzie.tundraware.com [75.145.138.73]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id E273F1871; Fri, 31 Jan 2014 17:49:05 +0000 (UTC) Received: from [192.168.0.2] (viper.tundraware.com [192.168.0.2]) (authenticated bits=0) by ozzie.tundraware.com (8.14.7/8.14.7) with ESMTP id s0VHmg1H024802 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Fri, 31 Jan 2014 11:48:42 -0600 (CST) (envelope-from tundra@tundraware.com) Message-ID: <52EBE1FA.2040603@tundraware.com> Date: Fri, 31 Jan 2014 11:48:42 -0600 From: Tim Daneliuk User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 MIME-Version: 1.0 To: John Baldwin , freebsd-stable@freebsd.org Subject: Re: Need Help With MCA Code References: <52E73717.3000503@tundraware.com> <52E99381.5050803@tundraware.com> <201401311222.12136.jhb@freebsd.org> In-Reply-To: <201401311222.12136.jhb@freebsd.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.4.3 (ozzie.tundraware.com [75.145.138.73]); Fri, 31 Jan 2014 11:48:42 -0600 (CST) X-TundraWare-MailScanner-Information: Please contact the ISP for more information X-TundraWare-MailScanner-ID: s0VHmg1H024802 X-TundraWare-MailScanner: Found to be clean X-TundraWare-MailScanner-From: tundra@tundraware.com X-Spam-Status: No Cc: FreeBSD Hardware Mailing List X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 31 Jan 2014 17:49:06 -0000 On 01/31/2014 11:22 AM, John Baldwin wrote: > On Wednesday, January 29, 2014 6:49:21 pm Tim Daneliuk wrote: >> Resending in hopes that people on one of the other lists will have some insight here: >> >> On 01/27/2014 10:50 PM, Tim Daneliuk wrote: >>> I am running 9.2 stable i386 r261207. As noted earlier: >>> >>>> I just replaced mobo/CPU on FBSD server (Gigabyte Z-87-D3HP with >>>> an Intel i3-4130). I am not overclocking ... but I continue to see this sort of thing: >>> >>>> MCA: CPU 0 COR (1) internal parity error >>> >>> Dmesg shows: >>> >>>> MCA: Vendor "GenuineIntel", ID 0x306c3, APIC ID 0 >>>> MCA: CPU 0 COR (1) internal parity error >>>> MCA: Bank 0, Status 0x90000040000f0005 >>>> MCA: Global Cap 0x0000000000000c07, Status 0x0000000000000000_ >>> >>> I've swapped CPUs (i5). I've fiddled with an endless supply of >>> mobo settings. I've switched power supplies. I've moved mem >>> sticks around .... No joy. >>> >>> So, I dug through the sources and found this: >>> >>> >>> >>> mca_log(const struct mca_record *rec) >>> { >>> uint16_t mca_error; >>> >>> printf("MCA: Bank %d, Status 0x%016llx\n", rec->mr_bank, >>> (long long)rec->mr_status); >>> printf("MCA: Global Cap 0x%016llx, Status 0x%016llx\n", >>> (long long)rec->mr_mcg_cap, (long long)rec->mr_mcg_status); >>> printf("MCA: Vendor \"%s\", ID 0x%x, APIC ID %d\n", cpu_vendor, >>> rec->mr_cpu_id, rec->mr_apic_id); >>> printf("MCA: CPU %d ", rec->mr_cpu); >>> if (rec->mr_status & MC_STATUS_UC) >>> printf("UNCOR "); >>> else { >>> printf("COR "); >>> if (rec->mr_mcg_cap & MCG_CAP_CMCI_P) >>> printf("(%lld) ", ((long long)rec->mr_status & >>> MC_STATUS_COR_COUNT) >> 38); >>> } >>> >>> >>> It looks like the trailing else clause is kicking out the error but I am >>> unclear what the error means, beyond the fact that it appears to be a parity >>> error somewhere within the CPU's internal memory (cache?). Is this error >>> getting corrected? Is this benign, Should I get a different mobo? >>> >>> Um .... Haaaaalp :) >> >> >> I have now tried different motherboards, CPUs, memory, and power supplies and >> this error is still showing up now and then. >> >> This points strongly to either FreeBSD bogus reporting, or these errors being >> benign. It's hard to believe that the exact same error might occur with >> completely different hardware ... unless it's being caused by the case. > > Are they all the same model CPU? Since it is a corrected error you can > probably ignore it, but it is not bogus reporting. FreeBSD only reports > these errors because they show up in registers on your CPU. > It's looking like this is an artifact of running 9.2-STABLE i386 on that hardware. I just installed 10-STABLE x64 and am beating the hardware to death and have yet to see an MCA check. It *is* possible the 9.2 install is boogered up (I went to grad school to learn how to say that), so I am pursuing a full rebuild of the server. While painful, this will also finally move this machine to x64 which is long overdue. -- ---------------------------------------------------------------------------- Tim Daneliuk tundra@tundraware.com PGP Key: http://www.tundraware.com/PGP/ From owner-freebsd-hardware@FreeBSD.ORG Fri Jan 31 22:25:21 2014 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 882BDB77 for ; Fri, 31 Jan 2014 22:25:21 +0000 (UTC) Received: from mail-ve0-x231.google.com (mail-ve0-x231.google.com [IPv6:2607:f8b0:400c:c01::231]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 498C41FAF for ; Fri, 31 Jan 2014 22:25:21 +0000 (UTC) Received: by mail-ve0-f177.google.com with SMTP id jz11so3464659veb.8 for ; Fri, 31 Jan 2014 14:25:20 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=H0vbPvOGdRY8lQnRkuOvXh6LLG/xKpApQJG51kilx/E=; b=D5nM4f8jrU8pxoAPiSTvjzLcj/PSpiK2SXA/aRprC/Qfjrb/jwj7k8B/4T64ZTmyYU sC0pHHX+/+BTWZsIOSd4YFmu6dnsjtWnA+u7FdZzsOzEn4GbxQLx9eHzRIrDULri5RKn pc6cOn8f7kfNUepefj3dQlsMo5amW7UEjd85+Ctlgy5TdbfpG2Q0Po97ok/Fh7Bt81v+ 7ys/DnPKryjPRdr4z0uy3sJeDQdc7zTlrtfEys3ivsAJewPzEnDPfGgzYkXpEEtUlnXu IexDj9fhrkATosFzQZ9mbSNal7fob0I/3MExbgrahE+VlBCJ/NtbQcPlutoSRm2Dedr7 pehg== MIME-Version: 1.0 X-Received: by 10.221.55.133 with SMTP id vy5mr9105549vcb.17.1391207120103; Fri, 31 Jan 2014 14:25:20 -0800 (PST) Received: by 10.58.172.131 with HTTP; Fri, 31 Jan 2014 14:25:20 -0800 (PST) Date: Sat, 1 Feb 2014 00:25:20 +0200 Message-ID: Subject: AR8161/8165 chipset (asus pu500ca) From: =?KOI8-R?B?4c7B1M/Mycog7sHXwdLP1w==?= To: freebsd-hardware@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 X-Mailman-Approved-At: Sat, 01 Feb 2014 00:02:47 +0000 X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 31 Jan 2014 22:25:21 -0000 Hi all. I really need driver for AR8161/8165 chipset class=0x20000 card=0x200f1043 chip=0x10911969 rev=0x10 hdr=0x00 vendor Atheros Communications class network subclass ethernet for my new notebook asus pu500ca Please say will be the support of this chipset? Asking very much!!! From owner-freebsd-hardware@FreeBSD.ORG Sat Feb 1 20:44:21 2014 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id D905385B; Sat, 1 Feb 2014 20:44:21 +0000 (UTC) Received: from ozzie.tundraware.com (ozzie.tundraware.com [75.145.138.73]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 746F01D13; Sat, 1 Feb 2014 20:44:21 +0000 (UTC) Received: from [192.168.0.2] (viper.tundraware.com [192.168.0.2]) (authenticated bits=0) by ozzie.tundraware.com (8.14.7/8.14.7) with ESMTP id s11Ki7K5011538 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Sat, 1 Feb 2014 14:44:07 -0600 (CST) (envelope-from tundra@tundraware.com) Message-ID: <52ED5C97.8030503@tundraware.com> Date: Sat, 01 Feb 2014 14:44:07 -0600 From: Tim Daneliuk User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 MIME-Version: 1.0 To: freebsd-stable@freebsd.org Subject: Followup On Recent MCA Madness. WAS: Need Help With MCA Code References: <52E73717.3000503@tundraware.com> <52E99381.5050803@tundraware.com> <201401311222.12136.jhb@freebsd.org> <52EBE1FA.2040603@tundraware.com> In-Reply-To: <52EBE1FA.2040603@tundraware.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.4.3 (ozzie.tundraware.com [75.145.138.73]); Sat, 01 Feb 2014 14:44:07 -0600 (CST) X-TundraWare-MailScanner-Information: Please contact the ISP for more information X-TundraWare-MailScanner-ID: s11Ki7K5011538 X-TundraWare-MailScanner: Found to be clean X-TundraWare-MailScanner-From: tundra@tundraware.com X-Spam-Status: No Cc: FreeBSD Hardware Mailing List X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 01 Feb 2014 20:44:21 -0000 On 01/31/2014 11:48 AM, Tim Daneliuk wrote: > On 01/31/2014 11:22 AM, John Baldwin wrote: >> On Wednesday, January 29, 2014 6:49:21 pm Tim Daneliuk wrote: >>> Resending in hopes that people on one of the other lists will have some insight here: >>> >>> On 01/27/2014 10:50 PM, Tim Daneliuk wrote: >>>> I am running 9.2 stable i386 r261207. As noted earlier: >>>> >>>>> I just replaced mobo/CPU on FBSD server (Gigabyte Z-87-D3HP with >>>>> an Intel i3-4130). I am not overclocking ... but I continue to see this sort of thing: >>>> >>>>> MCA: CPU 0 COR (1) internal parity error >>>> >>>> Dmesg shows: >>>> >>>>> MCA: Vendor "GenuineIntel", ID 0x306c3, APIC ID 0 >>>>> MCA: CPU 0 COR (1) internal parity error >>>>> MCA: Bank 0, Status 0x90000040000f0005 >>>>> MCA: Global Cap 0x0000000000000c07, Status 0x0000000000000000_ >>>> >>>> I've swapped CPUs (i5). I've fiddled with an endless supply of >>>> mobo settings. I've switched power supplies. I've moved mem >>>> sticks around .... No joy. >>>> This got resolved when I did a completely fresh install of FBSD 10 on the server. This made the MCAs go away. I therefore conclude that there were one of several possible root causes: - FreeBSD i386 doesn't play nice with Haswell parts - FreeBSD 9.2-STABLE i386 doesn't place nice with Haswell parts - My FreeBSD 9.2-STABLE i386 instance was corrupted somehow My belief is that it is mostly likely the last culprit, absent someone confirming that the first two are possibilities. The good thing that came out of this is that I finally upgraded this server in some important ways: - 64 bit - FreeBSD 10 - Latest bind 9 Now, if I could just figure out how to get stock X to run at 1920x1080 on HD4600 graphics. Apparently neither the intel of vesa drivers know how to do this, or at least I've had no luck with it. The intel driver doesn't even recognize the hardware as something it supports. "X on a server?" you say? Yes, for intermittent use of fluxbox to run a bunch of xterms. ---------------------------------------------------------------------------- Tim Daneliuk tundra@tundraware.com PGP Key: http://www.tundraware.com/PGP/