Date: Sun, 8 May 2016 15:09:52 +0500 From: shahzaib mushtaq <shahzaib.cb@gmail.com> To: "lokadamus@gmx.de" <lokadamus@gmx.de> Cc: freebsd-questions@freebsd.org, galtsev@kicp.uchicago.edu Subject: Re: FreeBSD Crashes Intermittently !! Message-ID: <CAD3xhrN8oLj=k4SrKSZm=s3GyXYrtc%2BGLgbzf2B1SosOospB%2BQ@mail.gmail.com> In-Reply-To: <571BA1E1.5020809@gmx.de> References: <CAD3xhrMfKO8hVdpzR1xNqV=vwTMedPeTHR7v2=5W6RwC3F4V7A@mail.gmail.com> <56E2E9AC.1040902@gmx.de> <33444.128.135.52.6.1457712900.squirrel@cosmo.uchicago.edu> <56E2F586.9000108@gmx.de> <CAD3xhrM_Q=OjZzbJO1jY5a8Qhqne50ziQjJKSQ3kLO73FnJ0ag@mail.gmail.com> <CAD3xhrP=KYjzOEusoOwnysTqp=ZgWgH1ofrnnmuqaK4Z=7r_pA@mail.gmail.com> <5715DF0F.4090808@gmx.de> <CAD3xhrMTv_tOXTWX7kCim-mptYkXRZ-n_Mx%2BFX80OQkd-WMsPw@mail.gmail.com> <5715EBDA.10907@gmx.de> <CAD3xhrMtmgguc_De9de7EgBJ3cNqHnRwWQxut4g_eYWG1adgYw@mail.gmail.com> <CAD3xhrMNAU9Unamcny8N86FGdTD38V1qDE_GpHz=r-qygP7ymw@mail.gmail.com> <57161B95.9020802@gmx.de> <CAD3xhrO%2BMbTr12SgcVU7-ftHF8c2Ge4nzxbzobvKOs1qXRLQEQ@mail.gmail.com> <571BA1E1.5020809@gmx.de>
next in thread | previous in thread | raw e-mail | index | archive | help
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 <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 <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 <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" > > > >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAD3xhrN8oLj=k4SrKSZm=s3GyXYrtc%2BGLgbzf2B1SosOospB%2BQ>