From owner-freebsd-arm@FreeBSD.ORG Tue Jan 28 14:53:15 2014 Return-Path: Delivered-To: freebsd-arm@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 28A0D598 for ; Tue, 28 Jan 2014 14:53:15 +0000 (UTC) Received: from mho-02-ewr.mailhop.org (mho-02-ewr.mailhop.org [204.13.248.72]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id DD1E614F3 for ; Tue, 28 Jan 2014 14:53:14 +0000 (UTC) Received: from c-24-8-230-52.hsd1.co.comcast.net ([24.8.230.52] helo=damnhippie.dyndns.org) by mho-02-ewr.mailhop.org with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.72) (envelope-from ) id 1W8A2G-000LQm-5H; Tue, 28 Jan 2014 14:53:08 +0000 Received: from [172.22.42.240] (revolution.hippie.lan [172.22.42.240]) by damnhippie.dyndns.org (8.14.3/8.14.3) with ESMTP id s0SEr37R053787; Tue, 28 Jan 2014 07:53:03 -0700 (MST) (envelope-from ian@FreeBSD.org) X-Mail-Handler: Dyn Standard SMTP by Dyn X-Originating-IP: 24.8.230.52 X-Report-Abuse-To: abuse@dyndns.com (see http://www.dyndns.com/services/sendlabs/outbound_abuse.html for abuse reporting information) X-MHO-User: U2FsdGVkX19Haad73aQiM7F979vYFR9R Subject: Re: RaspberryPi panic with CURRENT r261183 (was: r260558) From: Ian Lepore To: Ralf Wenk In-Reply-To: References: <20140125113854.083d5f30@bender.Home> Content-Type: text/plain; charset="us-ascii" Date: Tue, 28 Jan 2014 07:53:03 -0700 Message-ID: <1390920783.1230.153.camel@revolution.hippie.lan> Mime-Version: 1.0 X-Mailer: Evolution 2.32.1 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit Cc: freebsd-arm@FreeBSD.org 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: Tue, 28 Jan 2014 14:53:15 -0000 On Tue, 2014-01-28 at 14:55 +0100, Ralf Wenk wrote: > Andrew Turner wrote: > > > > Can you try updating to at least r261137. There was a bug where > > backtrace may not work correctly when it passes through exception_exit. > > This won't fix your problem, but it may help track it down. > > I have updated world and system to r261183w ith activated INVARIANTS and > INVARIANTS_SUPPORT. Repeated the whole cycle of NFS-mount, rsync(1)-ing, > fetching the INDEX-file and calling portversion. > > Some ours later the system panics. I fsck(8)ed the filesystems without using > the journal, repeated it and and it panics again in the same process after > some hours. > > Rebooting, fsck(8)ing and updating ruby form source, which involves the same > local filesystems and devices does not lead to a panic. Until now, the system > survived more ours after this than with the rsync(1) update. > > This is what I get on the serial console: > > # mmcsd0: Error indicated: 1 Timeout > g_vfs_done():mmcsd0s2a[READ(offset=268386304, length=4096)]error = 5 > mmcsd0: Error indicated: 1 Timeout > g_vfs_done():mmcsd0s2a[READ(offset=292880384, length=4096)]error = 5 > mmcsd0: Error indicated: 1 Timeout > g_vfs_done():mmcsd0s2a[READ(offset=268402688, length=4096)]error = 5 > mmcsd0: Error indicated: 1 Timeout > g_vfs_done():mmcsd0s2a[READ(offset=268406784, length=4096)]error = 5 > mmcsd0: Error indicated: 1 Timeout > g_vfs_done():mmcsd0s2a[READ(offset=268414976, length=4096)]error = 5 > mmcsd0: Error indicated: 1 Timeout > g_vfs_done():mmcsd0s2a[WRITE(offset=284360704, length=8192)]error = 5 > mmcsd0: Error indicated: 1 Timeout > g_vfs_done():mmcsd0s2a[WRITE(offset=284360704, length=8192)]error = 5 > mmcsd0: Error indicated: 1 Timeout > g_vfs_done():mmcsd0s2a[WRITE(offset=284360704, length=8192)]error = 5 > mmcsd0: Error indicated: 1 Timeout > g_vfs_done():mmcsd0s2a[WRITE(offset=284360704, length=8192)]error = 5 > mmcsd0: Error indicated: 1 Timeout > g_vfs_done():mmcsd0s2a[WRITE(offset=284360704, length=8192)]error = 5 > mmcsd0: Error indicated: 1 Timeout > g_vfs_done():mmcsd0s2a[WRITE(offset=284360704, length=8192)]error = 5 > mmcsd0: Error indicated: 1 Timeout > g_vfs_done():mmcsd0s2a[WRITE(offset=284360704, length=8192)]error = 5 > mmcsd0: Error indicated: 1 Timeout > g_vfs_done():mmcsd0s2a[WRITE(offset=284360704, length=8192)]error = 5 > mmcsd0: Error indicated: 1 Timeout > g_vfs_done():mmcsd0s2a[WRITE(offset=284360704, length=8192)]error = 5 > mmcsd0: Error indicated: 1 Timeout > g_vfs_done():mmcsd0s2a[WRITE(offset=284360704, length=8192)]error = 5 > mmcsd0: Error indicated: 1 Timeout > g_vfs_done():mmcsd0s2a[WRITE(offset=284360704, length=8192)]error = 5 > mmcsd0: Error indicated: 1 Timeout > g_vfs_done():mmcsd0s2a[WRITE(offset=284360704, length=8192)]error = 5 > mmcsd0: Error indicated: 1 Timeout > g_vfs_done():mmcsd0s2a[WRITE(offset=8439296, length=512)]error = 5 > panic: brelse: inappropriate B_PAGING or B_CLUSTER bp 0xccab63f0 > KDB: enter: panic > [ thread pid 625 tid 100063 ] > Stopped at $d: ldrb r15, [r15, r15, ror r15]! > db> bt > Tracing pid 625 tid 100063 td 0xc26bbc80 > [trace snipped] The panic here is just a symptom. The actual problem appears to be that the sd controller or card locked up -- just stopped responding to commands so that everything after that point timed out. The filesystem code is not very forgiving about IO which does not complete, eventually you end up with a panic. -- Ian