From owner-freebsd-questions@freebsd.org Thu Oct 22 16:18:55 2015 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 7E1E1A1C826 for ; Thu, 22 Oct 2015 16:18:55 +0000 (UTC) (envelope-from m.e.sanliturk@gmail.com) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 5CC8C17D3 for ; Thu, 22 Oct 2015 16:18:55 +0000 (UTC) (envelope-from m.e.sanliturk@gmail.com) Received: by mailman.ysv.freebsd.org (Postfix) id 58FB6A1C825; Thu, 22 Oct 2015 16:18:55 +0000 (UTC) Delivered-To: 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 58844A1C824 for ; Thu, 22 Oct 2015 16:18:55 +0000 (UTC) (envelope-from m.e.sanliturk@gmail.com) Received: from mail-ig0-x234.google.com (mail-ig0-x234.google.com [IPv6:2607:f8b0:4001:c05::234]) (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 2372B17D2 for ; Thu, 22 Oct 2015 16:18:55 +0000 (UTC) (envelope-from m.e.sanliturk@gmail.com) Received: by igbhv6 with SMTP id hv6so63354560igb.0 for ; Thu, 22 Oct 2015 09:18:54 -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:content-type; bh=QaubFqJzer8X83psIfk4GLV0JYeucmerlR1pXWnjifg=; b=fHXXYVzPqPEd6xZzu4F7JczOabBiOxv8EA5+QlwYvUtRKfO5uGIZZJUh7OEYKOZ0pg 4deN4sBPVcKROAz8BBaGdH584sy2Asmu0wZjVsJU/QflA4JDpEdUcFG65k0IZcMax29L 51+NUQzIMslYqXWJo2o9N9sAGWZ6RpXigBEAFukySO21K/h7N6X75m/EAKQ3/0luFfUj UbKwGpTfgoKafhJwh2OnWmx1fRCWkGX6wMa0tL2FReh7v00Oculf2601Dw/YZWwCHfLT t0NSi616UpvXD7wau1dkDovhqXyT7USD5W66Ra9pkUHh69DWhumm4ltSngjkmh4rUtl2 GT+Q== MIME-Version: 1.0 X-Received: by 10.50.72.108 with SMTP id c12mr33279689igv.63.1445530734446; Thu, 22 Oct 2015 09:18:54 -0700 (PDT) Received: by 10.64.241.227 with HTTP; Thu, 22 Oct 2015 09:18:54 -0700 (PDT) In-Reply-To: <5628FD40.1030701@netfence.it> References: <5627D8B8.7030901@netfence.it> <5628CD2B.2000902@gmail.com> <5628CFA7.6040704@netfence.it> <5628FD40.1030701@netfence.it> Date: Thu, 22 Oct 2015 09:18:54 -0700 Message-ID: Subject: Re: Spontaneous reboots with splash From: Mehmet Erol Sanliturk To: Andrea Venturoli Cc: Ernie Luzar , "questions@freebsd.org" Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Oct 2015 16:18:55 -0000 On Thu, Oct 22, 2015 at 8:14 AM, Andrea Venturoli wrote: > On 10/22/15 14:18, Mehmet Erol Sanliturk wrote: > > If you have two identical computers with the same programs running : >> One is working correctly , but other one is booting arbitrarily : >> > > I've got another identical box; I'll restore a dump on this and see if the > behaviour is the same. > > > > > Therefore , there is a necessity to check that >> >> - processor is working correctly >> > > CPU Burn-in says yes. > > > > - memories are working correctly >> > > Memtest 86+ says so. > > > > - memory management chips are working correctly . >> > > I have no idea how to check. How do I do this? > > > If memory tests are showing memories are working correctly , it is possible to say that memory management chips are also working correctly . Otherwise , it is not possible to write into and read from chips correctly . If memory chips fail , by testing with correctly working chips known , the problem may be attributed to memory management chips . Another possibility is the Watt level of Power Supply : If the required watts is exceeding the existent power supply watts level , it may cause reboots when power use increases beyond its capacity . Another possibility is power supply is cutting power spontaneously or causing fluctuations . > > Another problem may be a program which is causing generation of an >> invalid address showing boot start code and jumping into it . This is >> very easy for a i386 real mode program . >> > > In that case this program would be FreeBSD! That's why I'm asking here. > > > > If you can isolate the program causing boots , it will be possible to check its sources and binary file . > > Another possibility is that a program is broken ( contains an invalid >> address ) >> > > in HDD . When it starts to working , it jumps to that broken address > and this > > may start the boot . > > Would a userland program be allowed to do this??? > > > Let's assume that CPU is not over-heated and is not rebooting the computer like motherboard is powered . Let's assume that there is no any malicious program part to cause rebooting . A broken network card may corrupt data and may cause serious problems . The remaining possibility is that instruction counter value is destroyed in a program and showing the BIOS boot code area . To reboot the computer , it is necessary to start BIOS boot code This may occur also during BIOS related calls . Instead of a proper interrupt code , boot part is invoked . Otherwise we will say that within FreeBSD OS parts , there is a point that , instead of a proper shut down , it is directly rebooting the computer by calling BIOS boot code . Checking panic points and searching OS sources for such a reboot code ( without any error message and request approval from the user ) existence may help . Here the most important part is to find the program part which is causing the reboots . Studying this program part will reveal the reason and , therefore the cure . I can not say any correct sentence here about FreeBSD internals due to ( not sufficient knowledge ) . Since that computer is not working properly , you can do the following : Reinstall OS into a spare disk and check with it . This will identify whether problem is caused by the presently installed OS or not . If it can execute 64-bits OS , testing with such an OS will identify effect of OS or hardware . > > bye & Thanks > av. > Mehmet Erol Sanliturk