On Sun, Nov 5, 2017 at 6:50 AM, Tomasz Kłoczko <kloczko.tomasz@xxxxxxxxx> wrote: > On 28 October 2017 at 11:21, Peter Robinson <pbrobinson@xxxxxxxxx> wrote: > [..] >> >> I can rant on this for a long time.... > > > It was not my intention to start the rant. We both can continue such talks > .. > Sorry my fault. I should not mention this. > > Back to the subject of RPi3 and rawhide kernel I have another OOPS on latest > kernel: > > [ 52.448904] ------------[ cut here ]------------ > [ 52.453927] WARNING: CPU: 3 PID: 748 at lib/dma-debug.c:614 > debug_dma_assert_idle+0x148/0x1e0 > [ 52.463044] bcm2835-dma 3f007000.dma: DMA-API: cpu touching an active dma > mapped cacheline [cln=0x00c479c0] > [ 52.473433] Modules linked in: rc_cec vc4 snd_soc_core ac97_bus > snd_pcm_dmaengine cec rc_core snd_pcm snd_timer snd soundcore hci_uart > drm_kms_helper brcmfmac btbcm btqca drm btintel brcmutil bluetooth > fb_sys_fops cfg80211 syscopyarea sysfillrect sysimgblt ecdh_generic rfkill > bcm2835_wdt bcm2835_thermal bcm2835_rng leds_gpio xfs libcrc32c smsc95xx > usbnet mii mmc_block sdhci_iproc crc32_arm_ce sdhci_pltfm dwc2 udc_core > sdhci pwm_bcm2835 i2c_bcm2835 bcm2835 bcm2835_dma phy_generic > [ 52.518818] CPU: 3 PID: 748 Comm: bash Not tainted > 4.14.0-0.rc7.git2.1.fc28.armv7hl #1 > [ 52.527208] Hardware name: Generic DT based system > [ 52.532314] [<c0313154>] (unwind_backtrace) from [<c030d92c>] > (show_stack+0x18/0x1c) > [ 52.540530] [<c030d92c>] (show_stack) from [<c0b7d210>] > (dump_stack+0xa0/0xd8) > [ 52.548197] [<c0b7d210>] (dump_stack) from [<c0353ee8>] > (__warn+0xe4/0x104) > [ 52.555586] [<c0353ee8>] (__warn) from [<c0353f44>] > (warn_slowpath_fmt+0x3c/0x4c) > [ 52.563526] [<c0353f44>] (warn_slowpath_fmt) from [<c07101d4>] > (debug_dma_assert_idle+0x148/0x1e0) > [ 52.573030] [<c07101d4>] (debug_dma_assert_idle) from [<c04e4b98>] > (wp_page_copy+0xfc/0x640) > [ 52.581982] [<c04e4b98>] (wp_page_copy) from [<c04e6668>] > (do_wp_page+0x3a4/0x5ac) > [ 52.590009] [<c04e6668>] (do_wp_page) from [<c04e99c0>] > (handle_mm_fault+0xd28/0xde0) > [ 52.598319] [<c04e99c0>] (handle_mm_fault) from [<c0b99800>] > (do_page_fault+0x244/0x3b8) > [ 52.606901] [<c0b99800>] (do_page_fault) from [<c0301348>] > (do_DataAbort+0x40/0xc0) > [ 52.615025] [<c0301348>] (do_DataAbort) from [<c0b990e0>] > (__dabt_usr+0x40/0x60) > [ 52.622865] Exception stack(0xedee7fb0 to 0xedee7ff8) > [ 52.628227] 7fa0: 00fb1f88 00000000 > 00588464 01041420 > [ 52.636899] 7fc0: 00000000 00fae738 00000000 ffffffff 005833e8 00000001 > 00000000 01024238 > [ 52.645570] 7fe0: 00fb1f88 bebaf9c8 0050e1ec 004ac3c4 20030010 ffffffff > [ 52.652646] ---[ end trace 9babae82f6635701 ]--- > [ 52.657596] Mapped at: > [ 52.660173] bcm2835_dma_create_cb_chain+0xb0/0x1f0 [bcm2835_dma] > [ 52.666761] bcm2835_dma_prep_slave_sg+0xf0/0x25c [bcm2835_dma] > [ 52.673103] bcm2835_request+0x324/0x490 [bcm2835] > [ 52.678258] mmc_start_request+0x278/0x2bc > [ 52.682677] mmc_start_areq+0x248/0x34c > > I'm not asking to solve it asap but my posts are more only in context of > what should I do (?). > Should I ignore it because it is known issue and someone already working on > it? > Or should I open the Fedora ticket? > Or should I report this to someone specific or some exact place? I'm not seeing anything like this on any of my RPi devices (2, 3 32 and 64 bit), the one crash I did see on one of them is resolved with rc8 and it unrelated to the above. So to start with we'll need a lot more information. _______________________________________________ arm mailing list -- arm@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to arm-leave@xxxxxxxxxxxxxxxxxxxxxxx
