From owner-freebsd-stable@freebsd.org Wed Apr 19 02:45:44 2017 Return-Path: Delivered-To: freebsd-stable@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 DBB2AD44EE9 for ; Wed, 19 Apr 2017 02:45:44 +0000 (UTC) (envelope-from emz@norma.perm.ru) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id C4AA932B for ; Wed, 19 Apr 2017 02:45:44 +0000 (UTC) (envelope-from emz@norma.perm.ru) Received: by mailman.ysv.freebsd.org (Postfix) id C14D7D44EE7; Wed, 19 Apr 2017 02:45:44 +0000 (UTC) Delivered-To: stable@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 BF2CFD44EE6 for ; Wed, 19 Apr 2017 02:45:44 +0000 (UTC) (envelope-from emz@norma.perm.ru) Received: from elf.hq.norma.perm.ru (mail.norma.perm.ru [IPv6:2a00:7540:1::5]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.norma.perm.ru", Issuer "Vivat-Trade UNIX Root CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 181F732A for ; Wed, 19 Apr 2017 02:45:43 +0000 (UTC) (envelope-from emz@norma.perm.ru) Received: from [192.168.243.2] ([192.168.243.2]) (authenticated bits=0) by elf.hq.norma.perm.ru (8.15.2/8.15.2) with ESMTPSA id v3J2jcnE054159 (version=TLSv1.2 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO) for ; Wed, 19 Apr 2017 07:45:38 +0500 (YEKT) (envelope-from emz@norma.perm.ru) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=norma.perm.ru; s=key; t=1492569938; bh=rj7X9XNsM1vFGKXldJOCsudfBa32njleCwk8ZdHlrbk=; h=Subject:References:Cc:From:Date:In-Reply-To; b=NVFXrSY/wvzjbFMUgDLIcOCFSXMs9GpBqwkgYk6e3e1V17GuonGp2uATPauFG2wAc KIeMjAJpoK9TMvijW1iwM0U9Jg3WYA2hT/Ru+xJFoXKjMHAubVJeAgX6rHiZQFRQST j6u+kjEjd0PDI16DrFfTj+xKJbGiwXjcpgqJMDjE= Subject: Re: freebsd on Intel s5000pal - kernel reboots the system References: <4e16fe78-9a79-4cb6-8b49-9e74a807f358@norma.perm.ru> <20170418094422.GW1788@kib.kiev.ua> Cc: "stable@freebsd.org" From: "Eugene M. Zheganin" Message-ID: <0734423f-c05b-3f35-903e-56503b164306@norma.perm.ru> Date: Wed, 19 Apr 2017 07:45:40 +0500 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0 MIME-Version: 1.0 In-Reply-To: <20170418094422.GW1788@kib.kiev.ua> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Apr 2017 02:45:45 -0000 Hi. On 18.04.2017 14:44, Konstantin Belousov wrote: > You did not provide any information about your issue. It is not known > even whether the loader breaks for you, or a kernel starts booting and > failing. > > Ideally, you would use serial console and provide the log of everything > printed on it, before the reboot. > > What kind of boot do you use, legacy BIOS or EFI ? What version of > FreeBSD ? Oh, yeah, I'm sorry. Nah, loader is fine, the server reboots when the kernel itself is initializing the devices. It starts initializing various PCI stuff, then reboots. I'm aware about serial console, but, unfortunately, this server has some proprietary RS-232 jack, in the form-factor of 8P8C, and the only cable I have with these jacks is Cisco "blue" cable, but seems like they use different pin-out scheme. Thus, so far, no serial console, but I'm working on it. The FreeBSD version I've tried to use is the 11-RELEASE amd64. Thanks. Eugene.