From owner-freebsd-questions@freebsd.org Sun May 8 10:09:53 2016 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 31481B30D6B for ; Sun, 8 May 2016 10:09:53 +0000 (UTC) (envelope-from shahzaib.cb@gmail.com) Received: from mail-io0-x236.google.com (mail-io0-x236.google.com [IPv6:2607:f8b0:4001:c06::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id E9F27164A for ; Sun, 8 May 2016 10:09:52 +0000 (UTC) (envelope-from shahzaib.cb@gmail.com) Received: by mail-io0-x236.google.com with SMTP id d62so149736745iof.2 for ; Sun, 08 May 2016 03:09:52 -0700 (PDT) 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; bh=9h9SHphj41HzN+tCFzi8D4YKBZhXY6DkNXNwyqVFHrA=; b=Wr4AAoJ+iXymwq3d4oCxBrrB0ouXg/UC5HgdkJqh7YoWQnJ1tC0PHFW+VjNilwAHNA FkUYMsHgzBC5Ixv1NzQ6OkfMtzxks3ilWpggtN5rkYQdWG5nS00eDfZoUcRe8H7CfFTB OnNGJDWTXe2GaYHSseYPgiX5sMCU5UlI1Vdr0m1teAVojZsE6ACpFH36xeVgl6JPamXL Cg2tUdIsatBNtu139q+Jei3h6VkKULH5a8Bg2hyBwvKjTnfErFZpqQ9N9EFvbNfy5kPm 1DjthKcFrPPgjJLLMFRLa5n6P6rs9MYvsNayAcHT7ask1dFNqcKRtR7nxE/eNJ6nZVE3 gEzQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc; bh=9h9SHphj41HzN+tCFzi8D4YKBZhXY6DkNXNwyqVFHrA=; b=H+xk7DvMNBz/COkjXrN8qRC5jYwTywAHmRgL+zlR1SYd9kbcnO0cx5xlUFHddwWDXs FAoqvkv5x266xaGvcxuZgRjXKwuyhQnNu4YGu2SH5F6pI11ITM2BWQ2CHxsStYv4hn2f zNwdn43ho6OW6t7hNKq1ANHFWdn7l3/UoAdOmn0RYu4RwTm+/4lbnCSoO21X9I26vEKE F8WnjalzVmUeNpw+mLNF+0JbzvSE+YALUiVuddIjed6FKvnsLwG7hJ6c18uhpppaRUJB LGv7gZpTl9kJVcycIkIZAEJtQlKiXPQvJpt0HHLkE9fDpalV0Ye+VsAAS/GlTHp+MMDo wdiQ== X-Gm-Message-State: AOPr4FV1Pc2tQXEx1A722sbsMs2/q8yHH+AldJ+OC6zs87Xux3sPf0eIkFPqO0MtenQh68RuBGxd2NlqotHnPw== MIME-Version: 1.0 X-Received: by 10.107.53.204 with SMTP id k73mr31426024ioo.174.1462702192402; Sun, 08 May 2016 03:09:52 -0700 (PDT) Received: by 10.79.67.130 with HTTP; Sun, 8 May 2016 03:09:52 -0700 (PDT) In-Reply-To: <571BA1E1.5020809@gmx.de> References: <56E2E9AC.1040902@gmx.de> <33444.128.135.52.6.1457712900.squirrel@cosmo.uchicago.edu> <56E2F586.9000108@gmx.de> <5715DF0F.4090808@gmx.de> <5715EBDA.10907@gmx.de> <57161B95.9020802@gmx.de> <571BA1E1.5020809@gmx.de> Date: Sun, 8 May 2016 15:09:52 +0500 Message-ID: Subject: Re: FreeBSD Crashes Intermittently !! From: shahzaib mushtaq To: "lokadamus@gmx.de" Cc: freebsd-questions@freebsd.org, galtsev@kicp.uchicago.edu Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.22 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 08 May 2016 10:09:53 -0000 Hi, Well, after disabling logical cores on servers, situation got much stable. Though, there was a recent crash of FreeBSD-10.2 on DELL with different error panic: page fault . Following guide suggested to grab the value of "instruction pointer" but the value was not found even omitting the digits. : https://www.freebsd.org/doc/faq/advanced.html Here is the crash dump : http://prntscr.com/b1mgj3 On Sat, Apr 23, 2016 at 9:25 PM, lokadamus@gmx.de wrote: > Hi, > > Temp looks ok, but is the server working hard? > > I think about to disable core 22 and 23, but found your older mails and > see, that different cores makes this error. > http://pastebin.com/baShWuMP <-- from now > http://pastebin.com/042SJ11c <-- 9th march > > https://lists.freebsd.org/pipermail/freebsd-current/2016-January/059148.html > <-- januar > > I'm confused. > Regards > > > > On 04/19/16 13:56, shahzaib mushtaq wrote: > > Hi, > > > > Currently 2 x ffmpeg processes are running and the temp is : > > > > http://prntscr.com/au4wrm > > > > Well, it looks like restart is not necessary for microcode, you can > simply > > start microcode using command "service microcode_update start". > > > > Regards. > > > > On Tue, Apr 19, 2016 at 4:50 PM, lokadamus@gmx.de > wrote: > > > >> Yes, this is the port. I tested it on my old system. > >> After reboot it will start /usr/local/etc/rc.d/microcode-update and show > >> a little message. > >> My system is too old for an update. > >> > >> I'm wondering. i've never heard that lower 80w are protecting for > >> overheating. > >> Can you test this? > >> > >> > http://www.cyberciti.biz/faq/freebsd-determine-processor-cpu-temperature-command/ > >> > >> On 04/19/16 13:24, shahzaib mushtaq wrote: > >>> Hi, > >>> > >>> Can we use following freebsd guide to update microcode ? : > >>> > >>> Install sysutils/devcpu-data > >>> < > http://www.freebsd.org/cgi/url.cgi?ports/sysutils/devcpu-data/pkg-descr > >>> , > >>> then add: > >>> > >>> microcode_update_enable="YES" > >>> > >>> > >>> ===================================================== > >>> > >>> https://www.freebsd.org/doc/faq/compatibility-processors.html > >>> > >>> On Tue, Apr 19, 2016 at 1:40 PM, shahzaib mushtaq < > shahzaib.cb@gmail.com > >>> > >>> wrote: > >>> > >>>> Hi, > >>>> > >>>> We don't think its related to heat because L5640 only use 60W. Can we > >>>> update microcode on FreeBSD? Because intel has not stated this OS when > >>>> performing microcode update. > >>>> > >>>> Regards. > >>>> > >>>> On Tue, Apr 19, 2016 at 1:27 PM, lokadamus@gmx.de > >>>> wrote: > >>>> > >>>>> Hi, > >>>>> > >>>>> I think about the error lines: > >>>>> Hardware event. This is not a software error. > >>>>> CPU 23 BANK 5 > >>>>> MISC 0 ADDR 805613c60 > >>>>> MCG status:MCIP > >>>>> STATUS be00000000800400 MCGSTATUS 4 > >>>>> .... > >>>>> Hardware event. This is not a software error. > >>>>> CPU 22 BANK 5 > >>>>> > >>>>> https://en.wikipedia.org/wiki/Machine-check_exception > >>>>> > >>>>> Looks like a hardware problem from the second cpu. > >>>>> Thinks, what can be done: > >>>>> - Is it possible to read cpu heat infos from bios? > >>>>> - Disable HTT and look, if the error comes again > >>>>> - Remove the second cpu and look, if ... > >>>>> - Install microcode updates and hope, it will fix it > >>>>> > >>>>> Intel offers for many CPUs an microcode update. > >>>>> > >>>>> > >> > https://downloadcenter.intel.com/download/25512/Linux-Processor-Microcode-Data-File?v=t > >>>>> > >>>>> Can you test a cpu in another system? > >>>>> https://www.freebsd.org/cgi/ports.cgi?query=cpuburn&stype=all > >>>>> > >>>>> > >>>>> Regards > >>>>> > >>>>> On 04/19/16 09:35, shahzaib mushtaq wrote: > >>>>>> Hi, sorry for the mistake, cpus are : > >>>>>> > >>>>>> 2 x Intel(R) Xeon(R) CPU L5640 @ 2.27GHz5640 (12 cores, 24 threads) > >>>>>> > >>>>>> On Tue, Apr 19, 2016 at 12:32 PM, lokadamus@gmx.de < > lokadamus@gmx.de> > >>>>> wrote: > >>>>>> > >>>>>>> On 04/18/16 16:28, shahzaib mushtaq wrote: > >>>>>>>> Hi again, got back after a long time. So yes, we've move to new > Dell > >>>>> R510 > >>>>>>>> Hardware now. Here is the specs : > >>>>>>>> > >>>>>>>> DELL R510 > >>>>>>>> 2 x L5520 > >>>>>>>> 64GB RAM > >>>>>>>> 12x3TB Raid stripping+mirroring (HBA LSI-9211-fw version 19.00) > >>>>>>>> FreeBSD cw009.tunefiles.com 10.2-RELEASE-p14 FreeBSD > >> 10.2-RELEASE-p14 > >>>>>>> #0: > >>>>>>>> Wed Mar 16 20:46:12 UTC 2016 > >>>>>>>> root@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC > >>>>>>>> amd64 > >>>>>>>> > >>>>>>>> After 9days of uptime, server again got crashed with following > error > >>>>> in > >>>>>>>> crash log : > >>>>>>>> > >>>>>>>> http://pastebin.com/baShWuMP > >>>>>>>> > >>>>>>>> I am so much depressed now, there's much pressure on me from my > >>>>> company. > >>>>>>> Please > >>>>>>>> help us resolving this crash issue . :( > >>>>>>> Which CPU Model is installed? Is it one or more? > >>>>>>> > >>>>>>> There where some microcode updates for some models. > >>>>>>> > >>>>>>> Greeting > >>>>>>> > >>>>>> _______________________________________________ > >>>>>> freebsd-questions@freebsd.org mailing list > >>>>>> https://lists.freebsd.org/mailman/listinfo/freebsd-questions > >>>>>> To unsubscribe, send any mail to " > >>>>> freebsd-questions-unsubscribe@freebsd.org" > >>>>>> > >>>>> > >>>>> > >>>> > >>> > >> > >> > > _______________________________________________ > > freebsd-questions@freebsd.org mailing list > > https://lists.freebsd.org/mailman/listinfo/freebsd-questions > > To unsubscribe, send any mail to " > freebsd-questions-unsubscribe@freebsd.org" > > > >