crash on writing usbstick
Brett Wynkoop
freebsd-arm at wynn.com
Sun Mar 1 09:19:03 UTC 2015
Greeting-
So I plugged a 16G usb stick into my BeagleBone with the intent of
moving /usr/ports over to it. During the process KABOOM!
swi_handler() at swi_handler+0x2e4
pc = 0xc0613980 lr = 0xc06012a0 (swi_exit)
sp = 0xd4889e50 fp = 0xbffff500
r4 = 0x20c13200 r5 = 0x000001ed
r6 = 0x20c13364 r7 = 0x00000088
r8 = 0x00000001 r9 = 0xffffffe2
r10 = 0x20c13200
swi_exit() at swi_exit
pc = 0xc06012a0 lr = 0xc06012a0 (swi_exit)
sp = 0xd4889e50 fp = 0xbffff500
mode = 02, inum = 1284268, fs = /export
panic: ffs_valloc: dup alloc
KDB: enter: panic
[ thread pid 700 tid 100090 ]
Stopped at $d.7: ldrb r15, [r15, r15, ror r15]!
db>
The command doing the writing was
tar xpvf -
The entire pipeline was:
tar cpvf - . |( cd /export/ports ; tar xpvf -)
The only difference from the stock kernel for the BB was that I built
in the GPT stuff.
More datapoints:
# fsck -p
/dev/mmcsd0s2a: FILE SYSTEM CLEAN; SKIPPING CHECKS
/dev/mmcsd0s2a: clean, 551793 free (3025 frags, 68596 blocks, 0.2%
fragmentation) /dev/gpt/bbexport: PARTIALLY TRUNCATED INODE I=1284121
/dev/gpt/bbexport: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
#
[wynkoop at beaglebone ~]$ uname -a
FreeBSD beaglebone.wynn.com 11.0-CURRENT FreeBSD 11.0-CURRENT #2
r279219: Sun Mar 1 03:31:54 EST 2015
wynkoop at beaglebone.wynn.com:/usr/src/sys/arm/compile/BB-BEW arm
[wynkoop at beaglebone ~]$
World and my kernel are in sync, and both built native on the BB.
How is it that some of you are actually able to use USB mass storage?
-Brett
--
wynkoop at wynn.com http://prd4.wynn.com/wynkoop/pgp-keys.txt
917-642-6925
929-272-0000
If cowardly and dishonorable men sometimes shoot unarmed men with army
pistols or guns, the evil must be prevented by the penitentiary and
gallows, and not by a general deprivation of a constitutional privilege.
-Honorable J. A. Williams, Circuit Judge -
Wilson v. State, 33 Ark. 557, 34 Am. Rep. 52 (1878).
More information about the freebsd-arm
mailing list