From owner-freebsd-arm@FreeBSD.ORG Sun Dec 15 20:32:36 2013 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 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id B7CA163E for ; Sun, 15 Dec 2013 20:32:36 +0000 (UTC) Received: from feynman.konjz.org (feynman.konjz.org [64.147.119.39]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 756A81016 for ; Sun, 15 Dec 2013 20:32:35 +0000 (UTC) Received: from 127.0.0.1 (politkovskaja.torservers.net [77.247.181.165]) (authenticated bits=0) by feynman.konjz.org (8.14.7/8.14.4) with ESMTP id rBFK8rYs028618 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Sun, 15 Dec 2013 15:08:58 -0500 (EST) (envelope-from george@ceetonetechnology.com) Message-ID: <52AE0C45.4020406@ceetonetechnology.com> Date: Sun, 15 Dec 2013 15:08:37 -0500 From: George Rosamond MIME-Version: 1.0 To: Juergen.Dankoweit@T-Online.de, freebsd-arm@freebsd.org Subject: Re: FreeBSD on Raspberry Pi: sdhci_bcm0-slot0: timeout too large References: <52AD3C65.6040600@T-Online.de> In-Reply-To: <52AD3C65.6040600@T-Online.de> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 15 Dec 2013 20:32:36 -0000 Jürgen Dankoweit: > Hello to the list, > > for my Raspberry PI Model B with Micron-Chip I found an image which > boots FreeBSD. But on the monitor I see a lot of those messages: > > sdhci_bcm0-slot0: timeout too large > > What does this message mean and how to solve the problem which causes > this message? > > Usage: > FreeBSD 10-CURRENT #84 > compiled with CLang 3.3 > > Many thanks in advance Greetings Juergen. I see no one replied to this yet. I believe this came up previously on-list before, but I can't seem to find it in the archives. I'll take a look again and see if I can locate the solution, but I vividly remember there was something simple. I believe it had to do with the sdhci card being delayed in recognition, IIRC. In the meantime, maybe post your dmesg(8) and note the model/size of your SD card? g