FreeBSD Crashes Intermittently !!

[shahzaib mushtaq]

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 at gmx.de <lokadamus at 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 at 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 at gmx.de <lokadamus at 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 at gmx.de <lokadamus at 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 at 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 at freebsd.org mailing list
> >>>> https://lists.freebsd.org/mailman/listinfo/freebsd-questions
> >>>> To unsubscribe, send any mail to "
> >>> freebsd-questions-unsubscribe at freebsd.org"
> >>>>
> >>>
> >>>
> >>
> >
>
>