From owner-freebsd-questions@freebsd.org Fri Dec 16 15:54:38 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 545F4C80080 for ; Fri, 16 Dec 2016 15:54:38 +0000 (UTC) (envelope-from m.e.sanliturk@gmail.com) Received: from mail-yb0-x22e.google.com (mail-yb0-x22e.google.com [IPv6:2607:f8b0:4002:c09::22e]) (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 13F7291E; Fri, 16 Dec 2016 15:54:38 +0000 (UTC) (envelope-from m.e.sanliturk@gmail.com) Received: by mail-yb0-x22e.google.com with SMTP id v78so40142649ybe.3; Fri, 16 Dec 2016 07:54:38 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=a9zLl0J+qnKan3np0QLzybNkZtS2iaTkHApSnZc8UFY=; b=DYzp+BjpEtzJl2s6AdLiOv89dCVH93fa6TnrwnYrc+K7TENYe7RMHi+KlPajd8BXr/ FePwX2LM46cfILq7xzKcD/AIPib7g4vz2A8Pr16mbHz1OFhUl7rv6nF7ZDk5fpyUA6TV rmVRf+62AdgsVjyzWTciEi1KclkkwmaUFdjaJO7AihIUF06oXj5mWwy92D55OAsmE5Eu 8cgpyd0PNV5cNZZ7qznHuVNzziRa3BxM6qgZt5D4zGGjmwKw67z9dRcbB0Oh972HhZl/ BsRtQ0xWyMuH1wBVBZi5ULhE328R6992mcNjLzwlpucTNP/z3scbRtGHkm4BO7nB4QGr hPHg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=a9zLl0J+qnKan3np0QLzybNkZtS2iaTkHApSnZc8UFY=; b=fLqbdpclY4JGNhyRsrOT8qJ2AB+9tfwibTslrntO397pUXkE7o3Z8m0RoPiXZ7IWy8 d24VrHw52pq5vBrKjfQ2ZCTgo7Ce8OHwAX71H+vZt/U9ZCI1GHHKy0PX+p8FumN+zG6R /P5I001BdjBP7UUGyRgua7lMnvkSkzVUdnGQmE9g2M0cfzTVc4mHc4/UWbC/ztmhbTGB iASS48BPFuxrHtuMjulbf27dnYUidfbsR8cUPBro8kbasofvRLCeN71qi0q3qmJKsPUT hQ0hY+j9iIiKXO8RUAf/UoTivj9afNkRGqRX7xOOStDmt79mmjgoX04Md//bpOcVb+/+ mC2A== X-Gm-Message-State: AIkVDXLelsCubQcEuMjvN0aQ8Q+5ANSm1Ia5nqY8rNmSoovr+spv7A1hidTTL5Q0AlwVnfpBYhK8yeNgmsvAhw== X-Received: by 10.37.37.130 with SMTP id l124mr2771280ybl.103.1481903677027; Fri, 16 Dec 2016 07:54:37 -0800 (PST) MIME-Version: 1.0 Received: by 10.37.209.208 with HTTP; Fri, 16 Dec 2016 07:54:36 -0800 (PST) In-Reply-To: <7e56c2b4-f809-94b5-19f1-c521062a6488@FreeBSD.org> References: <20161216105453.7nxo2qrxfnwgrs2n@bsd.de> <7e56c2b4-f809-94b5-19f1-c521062a6488@FreeBSD.org> From: Mehmet Erol Sanliturk Date: Fri, 16 Dec 2016 07:54:36 -0800 Message-ID: Subject: Re: HW defect or system failure To: Matthew Seaman Cc: FreeBSD Questions Mailing List Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Dec 2016 15:54:38 -0000 On Fri, Dec 16, 2016 at 4:07 AM, Matthew Seaman wrote: > On 16/12/2016 10:54, J wrote: > > i got this weird problem of my notebook randomly rebooting. > > How would i find out if it is a kernel panic or a hardware failure? > > What changed? If the rebooting started spontaneously, and not in a way > obviously related to your upgrading the OS or packages, then it is > probably hardware. > > Have you tried cleaning out and de-fluffing any air intakes or fans? A > common cause of rebooting like this is due to overheating. Making sure > the cooling airflow is unobstructed helps a lot. > > You can try running diagnostic tools like memtest86 -- these will detect > many problems with RAM or CPU caches, which would confirm hardware as > the cause. If memtest86 doesn't find anything, that doesn't mean your > hardware is definitely OK -- there are ways that hardware can fail that > memtest86 can't detect. > > Cheers, > > Matthew > > > Additional to overheating , memory chip , BIOS setup , ... , caused reboots , the following may be considered after memory tests : Sometimes , an executable may be broken in HDD . When it is run , it may cause a reboot by accessing erroneously reboot code . Therefore , you may try another lively executable OS to understand reboots are deterministic or probabilistic before reinstalling the existing program(s) or OS . Mehmet Erol Sanliturk