Understanding and Resolving Boot Log Errors and Warnings on the Beaglebone board

Why do we encounter boot log errors and warnings after logging into the Beaglebone board, what are their root causes, why do we see same boot logs with different boot IDs, and what steps are available to handle these errors and warnings?

– Boot 4d553fe4d80040f5816820f65e69f2ce –

Jun 18 14:55:57 beaglebone kernel: omap-mailbox 480c8000.mailbox: omap mailbox rev 0x400

Jun 18 14:55:57 beaglebone kernel: omap_i2c 4819c000.i2c: bus 2 rev0.11 at 100 kHz

Jun 18 14:55:57 beaglebone kernel: debugfs: Directory ‘49000000.dma’ with parent ‘dmaengine’ already present!

– Boot 5a6659e0ef714d8b90f7f123c0824aff –

Jun 18 14:55:57 beaglebone kernel: omap_i2c 4819c000.i2c: bus 2 rev0.11 at 100 kHz

Jun 18 14:55:57 beaglebone kernel: debugfs: Directory ‘49000000.dma’ with parent ‘dmaengine’ already present!

Jun 18 14:55:57 beaglebone kernel: edma 49000000.dma: TI EDMA DMA engine driver

– Boot bc3828916e5c4a57b0f69b88160e1b42 –

Jun 18 14:55:57 beaglebone kernel: omap-mailbox 480c8000.mailbox: omap mailbox rev 0x400

Jun 18 14:55:57 beaglebone kernel: omap_i2c 4819c000.i2c: bus 2 rev0.11 at 100 kHz

Jun 18 14:55:57 beaglebone kernel: debugfs: Directory ‘49000000.dma’ with parent ‘dmaengine’ already present!