From owner-freebsd-hackers@FreeBSD.ORG Mon Mar 16 09:18:05 2015 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id D983776F for ; Mon, 16 Mar 2015 09:18:05 +0000 (UTC) Received: from kib.kiev.ua (kib.kiev.ua [IPv6:2001:470:d5e7:1::1]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4396BCEE for ; Mon, 16 Mar 2015 09:18:05 +0000 (UTC) Received: from tom.home (kostik@localhost [127.0.0.1]) by kib.kiev.ua (8.14.9/8.14.9) with ESMTP id t2G9Hw29044162 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 16 Mar 2015 11:17:58 +0200 (EET) (envelope-from kostikbel@gmail.com) DKIM-Filter: OpenDKIM Filter v2.9.2 kib.kiev.ua t2G9Hw29044162 Received: (from kostik@localhost) by tom.home (8.14.9/8.14.9/Submit) id t2G9HwZx044161; Mon, 16 Mar 2015 11:17:58 +0200 (EET) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com using -f Date: Mon, 16 Mar 2015 11:17:58 +0200 From: Konstantin Belousov To: Michael Fuckner Subject: Re: Server with 3TB Crashing at boot Message-ID: <20150316091758.GY2379@kib.kiev.ua> References: <20150314134733.GI2379@kib.kiev.ua> <550448B3.7050100@fuckner.net> <20150314145607.GJ2379@kib.kiev.ua> <5504530F.5040508@fuckner.net> <20150314153941.GL2379@kib.kiev.ua> <5505160A.1020703@fuckner.net> <5505827D.6060404@fuckner.net> <5505982E.9060201@fuckner.net> <20150315193202.GS2379@kib.kiev.ua> <2138577776.537937.1426455964006.JavaMail.open-xchange@ptangptang.store> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <2138577776.537937.1426455964006.JavaMail.open-xchange@ptangptang.store> User-Agent: Mutt/1.5.23 (2014-03-12) X-Spam-Status: No, score=-2.0 required=5.0 tests=ALL_TRUSTED,BAYES_00, DKIM_ADSP_CUSTOM_MED,FREEMAIL_FROM,NML_ADSP_CUSTOM_MED autolearn=no autolearn_force=no version=3.4.0 X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on tom.home Cc: "freebsd-hackers@freebsd.org" , Ryan Stone , Steven Hartland X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 16 Mar 2015 09:18:05 -0000 On Sun, Mar 15, 2015 at 10:46:03PM +0100, Michael Fuckner wrote: > > > Send me two things: > > 1. output of acpidump -t > > 2. verbose dmesg of the boot with tunables set > > hw.dmar.enable=1 > > hw.dmar.match_verbose=1 > > > > http://dedi3.fuckner.net/~molli123/temp/head-dmar.log > http://dedi3.fuckner.net/~molli123/temp/acpidump.txt > > here are the logs you requested, Note that there are no fault logs from the DMAR blocking invalid DMA access. Look at the release 10.1 logs, where there are lines like DMAR0: :pci1:0:0 fault acc 0 adt 0x0 reason 0x5 addr 0 and which I cannot find in your CURRENT kernel dmesg. I would say that the machine is fine, at least WRT the boot sequence. Then, I looked back at the previous logs from you, and both logs I have say 10.1-RELEASE-p6 in the herald. You overwrite the logs, so I cannot recheck the history, but it seems that you did not tested stable/10 ? There is currently no difference in DMAR code between head and stable/10.