From owner-freebsd-arm@FreeBSD.ORG Mon Apr 20 06:08:33 2015 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 9D3F39B3 for ; Mon, 20 Apr 2015 06:08:33 +0000 (UTC) Received: from smtp.hs-karlsruhe.de (smtp.HS-Karlsruhe.DE [193.196.64.25]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 60C08A28 for ; Mon, 20 Apr 2015 06:08:33 +0000 (UTC) Received: from iz-wera01.hs-karlsruhe.de ([193.196.65.46]) by smtp.hs-karlsruhe.de with esmtp (Exim 4.80.1) (envelope-from ) id 1Yk4sg-00CDfC-6c; Mon, 20 Apr 2015 08:08:30 +0200 X-Mailer: exmh version 2.8.0 04/21/2012 with nmh-1.6 From: Ralf Wenk To: Luiz Otavio O Souza cc: "freebsd-arm@freebsd.org" Subject: Re: Raspberry Pi B+ freeze during booting (new: r281074 causing it) In-reply-to: References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 20 Apr 2015 08:08:30 +0200 Message-Id: X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Apr 2015 06:08:33 -0000 Hi, On 19 Apr 2015 at 16:31:45 -0300, Luiz Otavio O Souza wrote: > On 19 April 2015 at 15:43, Ralf Wenk wrote: > > Hello, > > > > I wrote at Wed, 15 Apr 2015 14:30:48 +0200: > >> with r281139 my RPi freeze while booting. The last two lines logged > >> are always the same and belong to the ethernet interface. > >> > >> ue0: on smsc0 > >> ue0: Ethernet address: b8:eb:71:8a:6d:0b > >> > >> [...] > > > > the last revision which kernel boots here successful is 281073. > > Release 281074 is the first one which shows the described problem. > > > > [...] > > Hi, > > This issue was fixed on r281200 > > Regards, > Luiz glad to hear that. It looks like I began my search in the release window where this issue existed. Thank you. Regards Ralf