From owner-freebsd-questions@freebsd.org Thu Oct 22 12:18:16 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 0A61DA1C6B4 for ; Thu, 22 Oct 2015 12:18:16 +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 DE2A61375 for ; Thu, 22 Oct 2015 12:18:15 +0000 (UTC) (envelope-from m.e.sanliturk@gmail.com) Received: by mailman.ysv.freebsd.org (Postfix) id DBECAA1C6B3; Thu, 22 Oct 2015 12:18:15 +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 DB86CA1C6B2 for ; Thu, 22 Oct 2015 12:18:15 +0000 (UTC) (envelope-from m.e.sanliturk@gmail.com) Received: from mail-io0-x231.google.com (mail-io0-x231.google.com [IPv6:2607:f8b0:4001:c06::231]) (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 A56081374 for ; Thu, 22 Oct 2015 12:18:15 +0000 (UTC) (envelope-from m.e.sanliturk@gmail.com) Received: by iow1 with SMTP id 1so88904849iow.1 for ; Thu, 22 Oct 2015 05:18:15 -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=GKTtoLJE9WclUSUMGGOmbT3+JJqWe27HpVsbPqCyMtw=; b=RqB8zlb2i2380TjiID4nEvH6ahmTsPEMMsni/TzvV6tYlpPIPSlb6MdQR2qV+s6QzY MyKfj2hbh9ZjO9IphDAMhDmO7rIPCCjDS5JVZbIbZwWsUvn5rlZAJop2QeQylKvLSkKn qOh0kknYnPuFuOTrCypdGngvPxe13ZTeB5qWftJKd6Q6HePSmVkeUp2dEEyGbU2R8Yxc iNrCGcZiwshNgMQiA73ZWBteNEzZariuUWJv53X8hYYiTlbo8RMSwFRpuzFisbuB+hFH 5yrsxOQ08eb2pr+VXYxa8sU6FSKr9gqDysYr9m/ZTGS4f5EZniAxx8wfgPUYbS93TMRm Ay8Q== MIME-Version: 1.0 X-Received: by 10.107.30.207 with SMTP id e198mr1109839ioe.99.1445516295060; Thu, 22 Oct 2015 05:18:15 -0700 (PDT) Received: by 10.64.241.227 with HTTP; Thu, 22 Oct 2015 05:18:15 -0700 (PDT) In-Reply-To: <5628CFA7.6040704@netfence.it> References: <5627D8B8.7030901@netfence.it> <5628CD2B.2000902@gmail.com> <5628CFA7.6040704@netfence.it> Date: Thu, 22 Oct 2015 05:18:15 -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 12:18:16 -0000 On Thu, Oct 22, 2015 at 4:59 AM, Andrea Venturoli wrote: > On 10/22/15 13:48, Ernie Luzar wrote: > > Read the handbook section about splash. >> Your splash.bmp file has to be under 320x200 in size. For a bmp file >> over that size you need to also load the VESA module. >> >> vesa_load="YES" >> > > Hello Ernie and thanks for your time. > > I read that section (again), but found nothing new. > > My bitmap is 320x200x8, so it should be fine: it actually displays, so > that's not the problem; frequent reboots are. > > Besides, I'm using this on several boxes and all but this one works fine > (all without VESA). > > > bye & Thanks > av. > _______________________________________________ > > If you have two identical computers with the same programs running : One is working correctly , but other one is booting arbitrarily : Cause may be that an instruction address is broken and showing the boot starting code ( either 0 or maximum to showing BIOS boot start code address , sometimes ff...ff ) . Therefore , there is a necessity to check that - processor is working correctly - memories are working correctly - memory management chips are working correctly . 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 . Mehmet Erol Sanliturk