Michel, In your place, I would probably make an entire backup of the eMMC. Then reinstall to double check it's not something that accidentally got messed up by <whatever>. I've had this happen to me once, or twice, and I could not tell you what went wrong. Also, for the record, I'm usually very meticulous when it comes to taking notes - So I have exact steps to reproduce things I've already done. But I think in both cases, the problem cleared up. The difference for me is that I develop my images using an sdcard, and not the eMMC.
On Wed, Oct 14, 2015 at 9:56 AM, Michel Lavoie <[email protected]> wrote: > This thread seems to indicate that a physical problem within the eMMC is > quite unlikely and that badblocks should've been marked automatically: > https://groups.google.com/forum/embed/?place=forum/beagleboard&showsearch=true&showpopout=true&showtabs=true&hideforumtitle=true&parenturl=http%3A%2F%2Fbeagleboard.org%2FCommunity%2FForums#!searchin/beagleboard/emmc/beagleboard/6dJHbqgE7-c/uTSkbqCCJgAJ > > Should I format/reinstall? > > Thanks. > > > On Wednesday, October 14, 2015 at 12:51:37 PM UTC-4, Michel Lavoie wrote: > >> Hi, >> >> One of my BBB has been having problems with its filesystem for a while >> now and I think it originates from a physical problem on the eMMC but >> badblocks didn't find any error. It's running on Linux kernel 4.2.0-1-ARCH >> (Arch Linux) which is installed on the eMMC (no µSD card). >> >> The behavior is that after a while (generally a few days) the journal >> fails and the FS is remounted as read-only. The latest event's dmesg output >> is shown below. I starts with a "mmcqd/1: page allocation failure: order:3, >> mode:0xc020", follows with an aborted journal and the FS being remounted RO. >> >> I ran fsck.ext4 manually with the system unmounted (booted with a µSD >> card) and fixed several errors each time. As this event kept appearing >> afterwards I concluded that the must be something wrong with the eMMC. I >> then backed-up the partition (dd) and ran fsck with non-destructive >> badblocks ( >> https://wiki.archlinux.org/index.php/Badblocks#read-write_Test_.28non-destructive.29) >> but no error was found apart from filesystem issues which fsck fixed (no >> bad sector). >> >> Am I right in assuming that this is most likely a physical problem with >> the eMMC? Is there a more appropriate test I should run to test the eMMC? >> >> Thanks, >> >> [274268.642991] mmcqd/1: page allocation failure: order:3, mode:0xc020 >> [274268.649397] CPU: 0 PID: 92 Comm: mmcqd/1 Not tainted 4.2.0-1-ARCH #1 >> [274268.655895] Hardware name: Generic AM33XX (Flattened Device Tree) >> [274268.662150] [<c001704c>] (unwind_backtrace) from [<c0014224>] ( >> show_stack+0x20/0x24) >> [274268.670047] [<c0014224>] (show_stack) from [<c08b4f58>] (dump_stack+ >> 0x24/0x28) >> [274268.677415] [<c08b4f58>] (dump_stack) from [<c01221f8>] ( >> warn_alloc_failed+0xec/0x128) >> [274268.685478] [<c01221f8>] (warn_alloc_failed) from [<c0125304>] ( >> __alloc_pages_nodemask+0x778/0x8f4) >> [274268.694667] [<c0125304>] (__alloc_pages_nodemask) from [<c01256c4>] ( >> alloc_kmem_pages+0x40/0x110) >> [274268.703667] [<c01256c4>] (alloc_kmem_pages) from [<c013e4e0>] ( >> kmalloc_order+0x20/0x38) >> [274268.711809] [<c013e4e0>] (kmalloc_order) from [<c013e524>] ( >> kmalloc_order_trace+0x2c/0x94) >> [274268.720215] [<c013e524>] (kmalloc_order_trace) from [<c016454c>] ( >> __kmalloc+0x1e8/0x24c) >> [274268.728450] [<c016454c>] (__kmalloc) from [<c04febf0>] ( >> edma_prep_slave_sg+0xa4/0x2fc) >> [274268.736515] [<c04febf0>] (edma_prep_slave_sg) from [<c0717258>] ( >> omap_hsmmc_request+0x430/0x528) >> [274268.745448] [<c0717258>] (omap_hsmmc_request) from [<c06f9f4c>] ( >> __mmc_start_request+0x3c/0x58) >> [274268.754288] [<c06f9f4c>] (__mmc_start_request) from [<c06fa0c8>] ( >> mmc_start_request+0x160/0x298) >> [274268.763201] [<c06fa0c8>] (mmc_start_request) from [<c06fae3c>] ( >> mmc_start_req+0x2a4/0x3d8) >> [274268.771611] [<c06fae3c>] (mmc_start_req) from [<c070b568>] ( >> mmc_blk_issue_rw_rq+0xb8/0xaac) >> [274268.780100] [<c070b568>] (mmc_blk_issue_rw_rq) from [<c070c1b8>] ( >> mmc_blk_issue_rq+0x25c/0x4ec) >> [274268.788943] [<c070c1b8>] (mmc_blk_issue_rq) from [<c070cbf0>] ( >> mmc_queue_thread+0xa8/0x170) >> [274268.797470] [<c070cbf0>] (mmc_queue_thread) from [<c00659b8>] ( >> kthread+0xe4/0xfc) >> ... > > -- > For more options, visit http://beagleboard.org/discuss > --- > You received this message because you are subscribed to the Google Groups > "BeagleBoard" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
