Aw: Re: [opensuse-arm] Raspi 3b / Leap 15.1 / reproducible Kernel Panic
Gesendet: Montag, 02. Dezember 2019 um 17:56 Uhr Von: "Richard (MQ)" <osl2008@gmail.com> An: "Axel Braun" <docb@opensuse.org>, opensuse-arm@opensuse.org Betreff: Re: [opensuse-arm] Raspi 3b / Leap 15.1 / reproducible Kernel Panic
On 01/12/2019 18:25, Axel Braun wrote:
Am Sonntag, 1. Dezember 2019, 17:39:03 CET schrieb Freek de Kruijf:
Had a similar problem with a RPi1B+, which worked fine for quite some time, but started to crash and rebooted several times a day.
After replacing the power device, it behaved like before.
In this case I was using the same power device for both...
Cheers Axel
Have you checked "journalctl -f" / dmesg / "/var/log/messages" or similar for warnings about under-voltage? I had this with a 1A PSU, fixed by usiang a 2A one.
I guess its more this what causes the problems: Dez 03 14:11:38 gnuhealth-raspi kernel: ------------[ cut here ]------------ Dez 03 14:11:38 gnuhealth-raspi kernel: WARNING: CPU: 3 PID: 659 at ../ drivers/gpu/drm/vc4/vc4_plane.c:795 vc4_plane_async_set_fb+0x80/0x88 [vc4] Dez 03 14:11:38 gnuhealth-raspi kernel: Modules linked in: fuse af_packet nls_iso8859_1 vc4 nls_cp437 snd_soc_core vfat fat ac97_bus snd_pcm_dmaengine snd_pcm snd_timer brcmfmac snd joydev soundcore brcmutil drm_kms_helper cfg80211 cpufreq_dt smsc95xx drm usbnet rfkill mii drm_panel_orientation_quirks fb_sys_fops hid_cherry syscopyarea sysfillrect sysimgblt raspberrypi_hwmon raspberrypi_cpufreq vchiq(C) bcm2835_thermal bcm2835_wdt bcm2835_rng crc32_ce uio_pdrv_genirq uio leds_gpio hid_generic usbhid mmc_block dwc2 sdhci_iproc sdhci_pltfm sdhci bcm2835 usbcore gpio_raspberrypi_exp clk_raspberrypi mmc_core i2c_bcm2835 bcm2835_dma phy_generic fixed sg dm_multipath dm_mod scsi_dh_rdac scsi_dh_emc scsi_dh_alua efivarfs Dez 03 14:11:38 gnuhealth-raspi kernel: CPU: 3 PID: 659 Comm: X Tainted: G C 4.12.14-lp151.28.32-default #1 openSUSE Leap 15.1 Dez 03 14:11:38 gnuhealth-raspi kernel: Hardware name: raspberrypi rpi/rpi, BIOS 2019.01 08/21/2019 Dez 03 14:11:38 gnuhealth-raspi kernel: task: ffffd661b93b0080 task.stack: ffffd661bac88000 Dez 03 14:11:38 gnuhealth-raspi kernel: pstate: 80000005 (Nzcv daif -PAN -UAO) Dez 03 14:11:38 gnuhealth-raspi kernel: pc : vc4_plane_async_set_fb+0x80/0x88 [vc4] Dez 03 14:11:38 gnuhealth-raspi kernel: lr : vc4_plane_async_set_fb+0x30/0x88 [vc4] Dez 03 14:11:38 gnuhealth-raspi kernel: sp : ffffd661bac8b930 Dez 03 14:11:38 gnuhealth-raspi kernel: x29: ffffd661bac8b930 x28: ffffd661baa9af00 Dez 03 14:11:38 gnuhealth-raspi kernel: x27: 00000000fffffffc x26: 000000000000005b Dez 03 14:11:38 gnuhealth-raspi kernel: x25: 0000000000000040 x24: ffffd661baa9af00 Dez 03 14:11:38 gnuhealth-raspi kernel: x23: ffffd661abfcbe00 x22: ffffd661abcd2d80 Dez 03 14:11:38 gnuhealth-raspi kernel: x21: ffffd661bb587840 x20: ffffd661baa9af00 Dez 03 14:11:38 gnuhealth-raspi kernel: x19: ffffd661abea3a00 x18: 0000ffffe6fe6494 Dez 03 14:11:38 gnuhealth-raspi kernel: x17: 0000000000000000 x16: 0000000000000001 Dez 03 14:11:38 gnuhealth-raspi kernel: x15: 0000ffffe6fe6490 x14: ffffd661bad0e600 Dez 03 14:11:38 gnuhealth-raspi kernel: x13: 0000000000000000 x12: 0000000000000000 Dez 03 14:11:38 gnuhealth-raspi kernel: x11: 0000000000000004 x10: 0000000000000000 Dez 03 14:11:38 gnuhealth-raspi kernel: x9 : 00000000fffffff8 x8 : 0000000000000054 Dez 03 14:11:38 gnuhealth-raspi kernel: x7 : 0000000000001000 x6 : ffffd661abea3a00 Dez 03 14:11:38 gnuhealth-raspi kernel: x5 : 0000000000000001 x4 : ffffd661ab838da4 Dez 03 14:11:38 gnuhealth-raspi kernel: x3 : ffffd661abea3a00 x2 : 00000000fffffffc Dez 03 14:11:38 gnuhealth-raspi kernel: x1 : ffffd661abea3a00 x0 : ffffd661ab838c00 Dez 03 14:11:38 gnuhealth-raspi kernel: Call trace: Dez 03 14:11:38 gnuhealth-raspi kernel: vc4_plane_async_set_fb+0x80/0x88 [vc4] Dez 03 14:11:38 gnuhealth-raspi kernel: vc4_plane_atomic_async_update+0x40/0xf8 [vc4] Dez 03 14:11:38 gnuhealth-raspi kernel: drm_atomic_helper_async_commit+0x70/0x158 [drm_kms_helper] Dez 03 14:11:38 gnuhealth-raspi kernel: vc4_atomic_commit+0x130/0x198 [vc4] Dez 03 14:11:38 gnuhealth-raspi kernel: drm_atomic_commit+0x54/0x60 [drm] Dez 03 14:11:38 gnuhealth-raspi kernel: drm_atomic_helper_update_plane+0x140/0x160 [drm_kms_helper] Dez 03 14:11:38 gnuhealth-raspi kernel: __setplane_atomic+0x12c/0x148 [drm] Dez 03 14:11:38 gnuhealth-raspi kernel: drm_mode_cursor_universal+0x110/0x228 [drm] Dez 03 14:11:38 gnuhealth-raspi kernel: drm_mode_cursor_common+0x18c/0x200 [drm] Dez 03 14:11:38 gnuhealth-raspi kernel: drm_mode_cursor2_ioctl+0x34/0x48 [drm] Dez 03 14:11:38 gnuhealth-raspi kernel: drm_ioctl_kernel+0x80/0xe8 [drm] Dez 03 14:11:38 gnuhealth-raspi kernel: drm_ioctl+0x1c4/0x428 [drm] Dez 03 14:11:38 gnuhealth-raspi kernel: do_vfs_ioctl+0xb0/0x848 Dez 03 14:11:38 gnuhealth-raspi kernel: SyS_ioctl+0x8c/0xa8 Dez 03 14:11:38 gnuhealth-raspi kernel: el0_svc_naked+0x44/0x48 Dez 03 14:11:38 gnuhealth-raspi kernel: ---[ end trace 7e37acd2a8fb1c49 ]--- For this I have found some old redhat bugs: https://bugzilla.redhat.com/show_bug.cgi?id=1633381 https://bugzilla.redhat.com/show_bug.cgi?id=1472579 ...unfortunately closed woth 'end of lifecycle' -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Am 03.12.19 um 14:34 schrieb Axel Braun:
Gesendet: Montag, 02. Dezember 2019 um 17:56 Uhr Von: "Richard (MQ)" <osl2008@gmail.com> An: "Axel Braun" <docb@opensuse.org>, opensuse-arm@opensuse.org Betreff: Re: [opensuse-arm] Raspi 3b / Leap 15.1 / reproducible Kernel Panic
On 01/12/2019 18:25, Axel Braun wrote:
Am Sonntag, 1. Dezember 2019, 17:39:03 CET schrieb Freek de Kruijf:
Had a similar problem with a RPi1B+, which worked fine for quite some time, but started to crash and rebooted several times a day.
After replacing the power device, it behaved like before.
In this case I was using the same power device for both...
Cheers Axel
Have you checked "journalctl -f" / dmesg / "/var/log/messages" or similar for warnings about under-voltage? I had this with a 1A PSU, fixed by usiang a 2A one.
I guess its more this what causes the problems:
Dez 03 14:11:38 gnuhealth-raspi kernel: ------------[ cut here ]------------ Dez 03 14:11:38 gnuhealth-raspi kernel: WARNING: CPU: 3 PID: 659 at ../ drivers/gpu/drm/vc4/vc4_plane.c:795 vc4_plane_async_set_fb+0x80/0x88 [vc4]
This is not a panic. 786 void vc4_plane_async_set_fb(struct drm_plane *plane, struct drm_framebuffer *fb) 787 { 788 struct vc4_plane_state *vc4_state = to_vc4_plane_state(plane->state); 789 struct drm_gem_cma_object *bo = drm_fb_cma_get_gem_obj(fb, 0); 790 uint32_t addr; 791 792 /* We're skipping the address adjustment for negative origin, 793 * because this is only called on the primary plane. 794 */ 795 WARN_ON_ONCE(plane->state->crtc_x < 0 || plane->state->crtc_y < 0); 796 addr = bo->paddr + fb->offsets[0]; Whatever it is, it should not be fatal. -- Stefan Seyfried "For a successful technology, reality must take precedence over public relations, for nature cannot be fooled." -- Richard Feynman -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
participants (2)
-
Axel Braun
-
Stefan Seyfried