From owner-freebsd-questions@freebsd.org Fri Oct 23 11:59:07 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 20ADEA1C006 for ; Fri, 23 Oct 2015 11:59:07 +0000 (UTC) (envelope-from luzar722@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 F14B915F5 for ; Fri, 23 Oct 2015 11:59:06 +0000 (UTC) (envelope-from luzar722@gmail.com) Received: by mailman.ysv.freebsd.org (Postfix) id EDC91A1C005; Fri, 23 Oct 2015 11:59:06 +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 ED5D7A1C004 for ; Fri, 23 Oct 2015 11:59:06 +0000 (UTC) (envelope-from luzar722@gmail.com) Received: from mail-io0-x244.google.com (mail-io0-x244.google.com [IPv6:2607:f8b0:4001:c06::244]) (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 B6EEE15F4 for ; Fri, 23 Oct 2015 11:59:06 +0000 (UTC) (envelope-from luzar722@gmail.com) Received: by iofz202 with SMTP id z202so11785930iof.2 for ; Fri, 23 Oct 2015 04:59:06 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=rd8xls8sm25AYfPrSoKMC05ixWj1nd87x3w+7/LsNt4=; b=VGyjifGpZPjOXgQz5erE7JwPO+QhjCTl0xK1K8p7Tcs6I7Vi3i4pYkaJkOFMhTSYB1 2HRykvVXS/XCgIAaa08mDJq4IA4J3NWQ0fBbfcZtR0HZphrK03Rrv1U3eskfVIxVVLzA mFlBweXt/xyK19zOnk38vZ3v/u5AnLim2FpA4GhKrE5Vq0F9vPxx0+T2YfiSzotb/qfQ BXDqm5oaEHG9I3AzuWopOvyyay/P+DyhFRzU5b1WJuNEJzdJ7gu0gMDQmKZheRHjNsR0 +O5UMRZgFYUUzcvkKmkolvI1io3zbiDnKCFOqn24Fk4DharfC3KnI7wOR+OCHxnLewiB +Hkg== X-Received: by 10.107.34.78 with SMTP id i75mr6555046ioi.155.1445601546206; Fri, 23 Oct 2015 04:59:06 -0700 (PDT) Received: from [10.0.10.3] (cpe-76-190-244-6.neo.res.rr.com. [76.190.244.6]) by smtp.googlemail.com with ESMTPSA id m29sm7740664iod.38.2015.10.23.04.59.05 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 23 Oct 2015 04:59:05 -0700 (PDT) Message-ID: <562A210A.50306@gmail.com> Date: Fri, 23 Oct 2015 07:59:06 -0400 From: Ernie Luzar User-Agent: Thunderbird 2.0.0.24 (Windows/20100228) MIME-Version: 1.0 To: Andrea Venturoli CC: questions@freebsd.org, freebsd-questions-local@be-well.ilk.org, galtsev@kicp.uchicago.edu, m.e.sanliturk@gmail.com Subject: Re: Spontaneous reboots with splash References: <5627D8B8.7030901@netfence.it> <5628CD2B.2000902@gmail.com> <5628CFA7.6040704@netfence.it> <5628FD40.1030701@netfence.it> <44eggme0ab.fsf@lowell-desk.lan> <562A06F7.7090806@netfence.it> In-Reply-To: <562A06F7.7090806@netfence.it> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit 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: Fri, 23 Oct 2015 11:59:07 -0000 > I just tried on the third box, so I guess hardware failure is out of the > picture. > > I installed a *fresh* 10.2/i386 with stock GENERIC kernel, no daemons > running, no ports installed, no fancy configs (just the above mentioned > lines to get the splash screen). > > "make kernel" reboots within minutes. > >> No, but splash(4) is part of the kernel, so it would be allowed to do >> that. > > That's what I meant: the problem must be in splash (or in the kernel > anyway), not in some other unspecified program. > > > > I'll just try and see if amd64 gives the same trouble and file a bug > report: I just wish I had some kernel message to include... > > > > bye & Thanks to all > av. > Just for laughs, add vesa_load="YES" to the 3rd box you just did a fresh install on and see what happens. What did you use for the install source? Was it the same source as what was used to build the box with the original splash problem? Did you run a checksum on that source? I run a boot splash screen on my 10.2 system without any problems.