[Bug 1163582] New: alloc_contig_range: [17800, 179c7) PFNs busy
http://bugzilla.opensuse.org/show_bug.cgi?id=1163582 Bug ID: 1163582 Summary: alloc_contig_range: [17800, 179c7) PFNs busy Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.1 Hardware: aarch64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-maintainers@forge.provo.novell.com Reporter: axel.braun@gmx.de QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- After upgrading the Raspi today I got flooded with the above error messages coming from kernel. uname -r 4.12.14-lp151.28.36-default And I see as well Feb 13 13:15:30 gnuhealth-raspi kernel: ------------[ cut here ]------------ Feb 13 13:15:30 gnuhealth-raspi kernel: WARNING: CPU: 3 PID: 685 at ../drivers/gpu/drm/vc4/vc4_plane.c:795 vc4_plane_async_set_fb+0x80/0x88 [vc4] Feb 13 13:15:30 gnuhealth-raspi kernel: Modules linked in: fuse af_packet nls_iso8859_1 nls_cp437 vc4 vfat fat snd_soc_core ac97_bus snd_pcm_dmaengine snd_pcm snd_timer brcmfmac snd joydev brcmutil soundcore cfg80211 hid_generic cpufreq_dt drm_kms_helper hid_cherry smsc95xx usbhid rfkill usbnet drm mii drm_panel_orientation_quirks fb_sys_fops syscopyarea sysfillrect sysimgblt raspberrypi_hwmon vchiq(C) raspberrypi_cpufreq bcm2835_thermal bcm2835_wdt bcm2835_rng crc32_ce uio_pdrv_genirq uio leds_gpio mmc_block dwc2 gpio_raspberrypi_exp usbcore clk_raspberrypi sdhci_iproc sdhci_pltfm sdhci i2c_bcm2835 bcm2835 mmc_core bcm2835_dma phy_generic fixed sg dm_multipath dm_mod scsi_dh_rdac scsi_dh_emc scsi_dh_alua efivarfs Feb 13 13:15:30 gnuhealth-raspi kernel: CPU: 3 PID: 685 Comm: X Tainted: G C 4.12.14-lp151.28.36-default #1 openSUSE Leap 15.1 Feb 13 13:15:30 gnuhealth-raspi kernel: Hardware name: raspberrypi rpi/rpi, BIOS 2019.01 08/21/2019 Feb 13 13:15:30 gnuhealth-raspi kernel: task: ffffd2603aeec200 task.stack: ffffd2603adb4000 Feb 13 13:15:30 gnuhealth-raspi kernel: pstate: 80000005 (Nzcv daif -PAN -UAO) Feb 13 13:15:30 gnuhealth-raspi kernel: pc : vc4_plane_async_set_fb+0x80/0x88 [vc4] Feb 13 13:15:30 gnuhealth-raspi kernel: lr : vc4_plane_async_set_fb+0x30/0x88 [vc4] Feb 13 13:15:30 gnuhealth-raspi kernel: sp : ffffd2603adb7930 Feb 13 13:15:30 gnuhealth-raspi kernel: x29: ffffd2603adb7930 x28: ffffd2603907a900 Feb 13 13:15:30 gnuhealth-raspi kernel: x27: 00000000fffffffe x26: 000000000000008e Feb 13 13:15:30 gnuhealth-raspi kernel: x25: 0000000000000040 x24: ffffd2603907a900 Feb 13 13:15:30 gnuhealth-raspi kernel: x23: ffffd2603afccd00 x22: ffffd2603acbd400 Feb 13 13:15:30 gnuhealth-raspi kernel: x21: ffffd2603bf6e840 x20: ffffd2603907a900 Feb 13 13:15:30 gnuhealth-raspi kernel: x19: ffffd2603b259200 x18: 0000ffffe0317c24 Feb 13 13:15:30 gnuhealth-raspi kernel: x17: 0000000000000000 x16: 0000000000000001 Feb 13 13:15:30 gnuhealth-raspi kernel: x15: 0000ffffe0317c20 x14: ffffd2603afa5b40 Feb 13 13:15:30 gnuhealth-raspi kernel: x13: 0000000000000000 x12: 0000000000000000 Feb 13 13:15:30 gnuhealth-raspi kernel: x11: 0000000000000002 x10: 0000000000000000 Feb 13 13:15:30 gnuhealth-raspi kernel: x9 : 00000000fffffff5 x8 : 0000000000000044 Feb 13 13:15:30 gnuhealth-raspi kernel: x7 : 0000000000000044 x6 : ffffd2603b259200 Feb 13 13:15:30 gnuhealth-raspi kernel: x5 : 0000000000000001 x4 : ffffd260391401a4 Feb 13 13:15:30 gnuhealth-raspi kernel: x3 : ffffd2603b259200 x2 : 00000000fffffffe Feb 13 13:15:30 gnuhealth-raspi kernel: x1 : ffffd2603b259200 x0 : ffffd26039140000 Feb 13 13:15:30 gnuhealth-raspi kernel: Call trace: Feb 13 13:15:30 gnuhealth-raspi kernel: vc4_plane_async_set_fb+0x80/0x88 [vc4] Feb 13 13:15:30 gnuhealth-raspi kernel: vc4_plane_atomic_async_update+0x40/0xf8 [vc4] Feb 13 13:15:30 gnuhealth-raspi kernel: drm_atomic_helper_async_commit+0x70/0x158 [drm_kms_helper] Feb 13 13:15:30 gnuhealth-raspi kernel: vc4_atomic_commit+0x130/0x198 [vc4] Feb 13 13:15:30 gnuhealth-raspi kernel: drm_atomic_commit+0x54/0x60 [drm] Feb 13 13:15:30 gnuhealth-raspi kernel: drm_atomic_helper_update_plane+0x140/0x160 [drm_kms_helper] Feb 13 13:15:30 gnuhealth-raspi kernel: __setplane_atomic+0x12c/0x148 [drm] Feb 13 13:15:30 gnuhealth-raspi kernel: drm_mode_cursor_universal+0x110/0x228 [drm] Feb 13 13:15:30 gnuhealth-raspi kernel: drm_mode_cursor_common+0x18c/0x200 [drm] Feb 13 13:15:30 gnuhealth-raspi kernel: drm_mode_cursor2_ioctl+0x34/0x48 [drm] Feb 13 13:15:30 gnuhealth-raspi kernel: drm_ioctl_kernel+0x80/0xe8 [drm] Feb 13 13:15:30 gnuhealth-raspi kernel: drm_ioctl+0x1c4/0x428 [drm] Feb 13 13:15:30 gnuhealth-raspi kernel: do_vfs_ioctl+0xb0/0x848 Feb 13 13:15:30 gnuhealth-raspi kernel: SyS_ioctl+0x8c/0xa8 Feb 13 13:15:30 gnuhealth-raspi kernel: el0_svc_naked+0x44/0x48 Feb 13 13:15:30 gnuhealth-raspi kernel: ---[ end trace 92dac48133ced6e4 ]--- -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1163582
http://bugzilla.opensuse.org/show_bug.cgi?id=1163582#c1
Sid Boyce
http://bugzilla.opensuse.org/show_bug.cgi?id=1163582
Guillaume GARDET
http://bugzilla.opensuse.org/show_bug.cgi?id=1163582
Guillaume GARDET
http://bugzilla.opensuse.org/show_bug.cgi?id=1163582
Matthias Brugger
http://bugzilla.opensuse.org/show_bug.cgi?id=1163582
http://bugzilla.opensuse.org/show_bug.cgi?id=1163582#c2
--- Comment #2 from Matthias Brugger
After upgrading the Raspi today I got flooded with the above error messages coming from kernel.
RPi3 or RPi4? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1163582
http://bugzilla.opensuse.org/show_bug.cgi?id=1163582#c3
--- Comment #3 from Sid Boyce
http://bugzilla.opensuse.org/show_bug.cgi?id=1163582
Matthias Brugger
http://bugzilla.opensuse.org/show_bug.cgi?id=1163582
Matthias Brugger
http://bugzilla.opensuse.org/show_bug.cgi?id=1163582
Matthias Brugger
http://bugzilla.opensuse.org/show_bug.cgi?id=1163582
http://bugzilla.opensuse.org/show_bug.cgi?id=1163582#c4
--- Comment #4 from Nicolas Patricio Saenz Julienne
After the latest Tumbleweed aarch64 online upgrade. Pi3openSUSE:~ # uname -r 5.4.14-1-default [Sat Feb 22 07:56:55 2020] alloc_contig_range: 58 callbacks suppressed [Sat Feb 22 07:56:55 2020] alloc_contig_range: [18e00, 19000) PFNs busy [Sat Feb 22 07:56:55 2020] alloc_contig_range: [19200, 19400) PFNs busy
Hi Sid, this seems to be a separate issue, could you open another bug report. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1163582
http://bugzilla.opensuse.org/show_bug.cgi?id=1163582#c5
--- Comment #5 from Axel Braun
(In reply to Sid Boyce from comment #1)
After the latest Tumbleweed aarch64 online upgrade. Pi3openSUSE:~ # uname -r 5.4.14-1-default [Sat Feb 22 07:56:55 2020] alloc_contig_range: 58 callbacks suppressed [Sat Feb 22 07:56:55 2020] alloc_contig_range: [18e00, 19000) PFNs busy [Sat Feb 22 07:56:55 2020] alloc_contig_range: [19200, 19400) PFNs busy
Hi Sid, this seems to be a separate issue, could you open another bug report.
If I look at the description of the bug: [RPi3] alloc_contig_range: [17800, 179c7) PFNs busy it looks exactly the same. Can you explain? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1163582
http://bugzilla.opensuse.org/show_bug.cgi?id=1163582#c6
--- Comment #6 from Nicolas Patricio Saenz Julienne
(In reply to Nicolas Patricio Saenz Julienne from comment #4)
(In reply to Sid Boyce from comment #1)
After the latest Tumbleweed aarch64 online upgrade. Pi3openSUSE:~ # uname -r 5.4.14-1-default [Sat Feb 22 07:56:55 2020] alloc_contig_range: 58 callbacks suppressed [Sat Feb 22 07:56:55 2020] alloc_contig_range: [18e00, 19000) PFNs busy [Sat Feb 22 07:56:55 2020] alloc_contig_range: [19200, 19400) PFNs busy
Hi Sid, this seems to be a separate issue, could you open another bug report.
If I look at the description of the bug: [RPi3] alloc_contig_range: [17800, 179c7) PFNs busy it looks exactly the same. Can you explain?
Arrgh, yes sorry, I was focusing on the kernel warning you posted above and forgot about the actual topic. Nevermind what I said. Do you have a reliable way to reproduce the issue? I can't seem to do it. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1163582
http://bugzilla.opensuse.org/show_bug.cgi?id=1163582#c7
--- Comment #7 from Patrik Jakobsson
http://bugzilla.opensuse.org/show_bug.cgi?id=1163582
http://bugzilla.opensuse.org/show_bug.cgi?id=1163582#c8
--- Comment #8 from Sid Boyce
http://bugzilla.opensuse.org/show_bug.cgi?id=1163582
http://bugzilla.opensuse.org/show_bug.cgi?id=1163582#c9
--- Comment #9 from Sid Boyce
http://bugzilla.opensuse.org/show_bug.cgi?id=1163582
http://bugzilla.opensuse.org/show_bug.cgi?id=1163582#c10
--- Comment #10 from Patrik Jakobsson
http://bugzilla.opensuse.org/show_bug.cgi?id=1163582
http://bugzilla.opensuse.org/show_bug.cgi?id=1163582#c11
--- Comment #11 from Axel Braun
Perhaps you have enabled 3D acceleration with the Mesa-dri-vc4 package (not the xf86-video-fbturbo package)? Using the Mesa driver will allocate/deallocate much more memory and produce many more of these warnings.
Yes, the Mesa-dri-vc4 is enabled. So you recommend to disable the driver in order to get rid of the warnings? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1163582
http://bugzilla.opensuse.org/show_bug.cgi?id=1163582#c12
--- Comment #12 from Patrik Jakobsson
http://bugzilla.opensuse.org/show_bug.cgi?id=1163582
Matthias Brugger
http://bugzilla.opensuse.org/show_bug.cgi?id=1163582
http://bugzilla.opensuse.org/show_bug.cgi?id=1163582#c13
Matthias Brugger
http://bugzilla.opensuse.org/show_bug.cgi?id=1163582
http://bugzilla.opensuse.org/show_bug.cgi?id=1163582#c14
Matthias Brugger
http://bugzilla.opensuse.org/show_bug.cgi?id=1163582
http://bugzilla.opensuse.org/show_bug.cgi?id=1163582#c18
--- Comment #18 from Patrik Jakobsson
participants (1)
-
bugzilla_noreply@novell.com