Bug 1472579
| Summary: | VC4 driver related kernel oops on raspberry pi 3 | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Jussi Eloranta <eloranta> | ||||||||
| Component: | kernel | Assignee: | Kernel Maintainer List <kernel-maint> | ||||||||
| Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||
| Severity: | high | Docs Contact: | |||||||||
| Priority: | unspecified | ||||||||||
| Version: | 26 | CC: | eloranta, gansalmon, ichavero, itamar, jonathan, kernel-maint, madhu.chinakonda, mchehab | ||||||||
| Target Milestone: | --- | ||||||||||
| Target Release: | --- | ||||||||||
| Hardware: | armv7l | ||||||||||
| OS: | Linux | ||||||||||
| Whiteboard: | |||||||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||||||
| Doc Text: | Story Points: | --- | |||||||||
| Clone Of: | Environment: | ||||||||||
| Last Closed: | 2018-05-29 12:29:01 UTC | Type: | Bug | ||||||||
| Regression: | --- | Mount Type: | --- | ||||||||
| Documentation: | --- | CRM: | |||||||||
| Verified Versions: | Category: | --- | |||||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||
| Embargoed: | |||||||||||
| Attachments: |
|
||||||||||
|
Description
Jussi Eloranta
2017-07-19 03:37:52 UTC
Sorry, the kernel version above is incorrect. I meant 4.11.10. Still keeps happening with 4.11.11. After this the above messages are also followed by repeated: [ 352.839044] vc4_hdmi 3f902000.hdmi: ASoC: can't open interface 3f902000.hdmi: -19 At least for me vc4 is very unstable and had to revert to non-accelerated framebuffer driver (by blacklisting vc4). Actually, with the normal framebuffer driver the system is also faster (probably because of the repeated errors with vc4)! uname -a of this system is: Linux localhost 4.11.11-300.fc26.armv7hl #1 SMP Mon Jul 17 17:51:32 UTC 2017 armv7l armv7l armv7l GNU/Linux OK, I don't see this so much anymore but running mplayer on just about any mpeg file would crash the X server (logs attached & dmesg). This is on: Linux jussi 4.12.14-300.fc26.armv7hl #1 SMP Wed Sep 20 18:05:42 UTC 2017 armv7l armv7l armv7l GNU/Linux So, install mplayer from rpmfusion and try playing the attached mpeg file. Created attachment 1332941 [details]
Xorg log file
Created attachment 1332942 [details]
dmesg
Created attachment 1332943 [details]
Sample mpeg file that causes Xorg to crash with mplayer
This problem is still present with 4.13.4-200. In addition there is now also kernel crash (which appears just by starting X & logging in): [ 275.249480] ------------[ cut here ]------------ [ 275.249564] WARNING: CPU: 3 PID: 663 at drivers/gpu/drm/vc4/vc4_plane.c:746 vc4_plane_async_set_fb+0x68/0x9c [vc4] [ 275.249570] Modules linked in: fuse sunrpc vc4 snd_soc_core ac97_bus snd_pcm_dmaengine snd_seq snd_seq_device snd_pcm snd_timer joydev snd pl2303 soundcore brcmfmac drm_kms_helper brcmuti l drm cfg80211 fb_sys_fops rfkill syscopyarea sysfillrect sysimgblt bcm2835_thermal bcm2835_wdt bcm2835_rng phy_generic leds_gpio smsc95xx usbnet mii mmc_block crc32_arm_ce dwc2 sdhci_iproc udc_core sdhci_pltfm sdhci pwm_bcm2835 i2c_bcm2835 bcm2835 bcm2835_dma [ 275.249756] CPU: 3 PID: 663 Comm: Xorg Not tainted 4.13.4-200.fc26.armv7hl #1 [ 275.249761] Hardware name: Generic DT based system [ 275.249795] [<c0311a70>] (unwind_backtrace) from [<c030c6b4>] (show_stack+0x18/0x1c) [ 275.249811] [<c030c6b4>] (show_stack) from [<c0a64170>] (dump_stack+0x80/0xa0) [ 275.249825] [<c0a64170>] (dump_stack) from [<c034c0f4>] (__warn+0xe4/0x104) [ 275.249838] [<c034c0f4>] (__warn) from [<c034c1d0>] (warn_slowpath_null+0x24/0x2c) [ 275.249900] [<c034c1d0>] (warn_slowpath_null) from [<bf4cf2f8>] (vc4_plane_async_set_fb+0x68/0x9c [vc4]) [ 275.250013] [<bf4cf2f8>] (vc4_plane_async_set_fb [vc4]) from [<bf4cf3c8>] (vc4_update_plane+0x9c/0x14c [vc4]) [ 275.250259] [<bf4cf3c8>] (vc4_update_plane [vc4]) from [<bf2bf63c>] (__setplane_internal+0x1b4/0x1e0 [drm]) [ 275.250602] [<bf2bf63c>] (__setplane_internal [drm]) from [<bf2bf7bc>] (drm_mode_cursor_universal+0x154/0x1a4 [drm]) [ 275.250932] [<bf2bf7bc>] (drm_mode_cursor_universal [drm]) from [<bf2bf8e0>] (drm_mode_cursor_common+0xd4/0x1c4 [drm]) [ 275.251251] [<bf2bf8e0>] (drm_mode_cursor_common [drm]) from [<bf2a92e0>] (drm_ioctl+0x2b8/0x348 [drm]) [ 275.251432] [<bf2a92e0>] (drm_ioctl [drm]) from [<c04d2f48>] (vfs_ioctl+0x28/0x3c) [ 275.251449] [<c04d2f48>] (vfs_ioctl) from [<c04d30fc>] (do_vfs_ioctl+0x8c/0x850) [ 275.251463] [<c04d30fc>] (do_vfs_ioctl) from [<c04d3918>] (SyS_ioctl+0x58/0x74) [ 275.251481] [<c04d3918>] (SyS_ioctl) from [<c0307dc0>] (ret_fast_syscall+0x0/0x3c) [ 275.251515] ---[ end trace 17ddfe3f5c506095 ]--- We apologize for the inconvenience. There is a large number of bugs to go through and several of them have gone stale. The kernel moves very fast so bugs may get fixed as part of a kernel update. Due to this, we are doing a mass bug update across all of the Fedora 26 kernel bugs. Fedora 26 has now been rebased to 4.15.4-200.fc26. Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel. If you have moved on to Fedora 27, and are still experiencing this issue, please change the version to Fedora 27. If you experience different issues, please open a new bug report for those. This message is a reminder that Fedora 26 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 26. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '26'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 26 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. Fedora 26 changed to end-of-life (EOL) status on 2018-05-29. Fedora 26 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed. |