Date: Tue, 28 Jan 2014 07:53:03 -0700 From: Ian Lepore <ian@FreeBSD.org> To: Ralf Wenk <iz-rpi03@hs-karlsruhe.de> Cc: freebsd-arm@FreeBSD.org Subject: Re: RaspberryPi panic with CURRENT r261183 (was: r260558) Message-ID: <1390920783.1230.153.camel@revolution.hippie.lan> In-Reply-To: <E1W898M-0065FQ-3w@smtp.hs-karlsruhe.de> References: <E1W6gx2-006Gys-Pp@smtp.hs-karlsruhe.de> <20140125113854.083d5f30@bender.Home> <E1W898M-0065FQ-3w@smtp.hs-karlsruhe.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 2014-01-28 at 14:55 +0100, Ralf Wenk wrote: > Andrew Turner <andrew@fubar.geek.nz> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1390920783.1230.153.camel>