http://bugzilla.opensuse.org/show_bug.cgi?id=1183825 Bug ID: 1183825 Summary: When in graphical environment on RPI3, system goes down at when screen goes into powersave Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: aarch64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: X.Org Assignee: gfx-bugs@suse.de Reporter: dillon.ang.h@gmail.com QA Contact: gfx-bugs@suse.de Found By: --- Blocker: --- On the Raspberry Pi 3, when running X, it appears that when the system tries to put the connected monitor into powersave mode, the system becomes completely unresponsive. Connected peripherals go dead, and they system goes offline on the network. It does not respond to either ctrl-alt-delete to restart or ctrl-alt-backspace to restart X. One also cannot use the ctrl-alt-f keys to switch. My monitor is the HP Z24n G2 1920x1200 connected via HDMI. I use this same monitor on a Raspberry Pi 4 running the same version of openSUSE Tumbleweed, and this issue only affects the Raspberry Pi 3. This problem first appeared several months back, and I regret not investigating further at that time. At latest, it appeared with kernel 5.10, but I suspect it appeared before that. This problem occurs both in the installer when installing from the ISO, and when booted. I tested a fresh install in addition to a system that was updated to the latest version using Zypper dup. My install settings are to install a graphical environment with XFCE. I did not install the xfce4-screensaver and xscreensaver packages, but those were the only modifications I made to the package selection. I also turned off the firewall and set sshd to start at boot for testing purposes. I have not been able to recover a backtrace when the system goes down. If anyone has any suggestions on how I may be able to do this, that would be appreciated. I am including some output from dmesg at boot up in case it may be helpful. [ 22.187413] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4 [ 22.190981] efifb: probing for efifb [ 22.191226] efifb: framebuffer at 0x3e330000, using 9000k, total 9000k [ 22.191239] efifb: mode is 1920x1200x32, linelength=7680, pages=1 [ 22.191252] efifb: scrolling: redraw [ 22.191257] efifb: Truecolor: size=8:8:8:8, shift=24:16:8:0 [ 22.192022] Console: switching to colour frame buffer device 240x75 [ 22.246074] fb0: EFI VGA frame buffer device [ 22.263472] Serial: 8250/16550 driver, 32 ports, IRQ sharing enabled [ 22.276585] bcm2835-aux-uart 3f215040.serial: there is not valid maps for state default [ 22.277325] 3f215040.serial: ttyS0 at MMIO 0x3f215040 (irq = 71, base_baud = 50000000) is a 16550 [ 22.278908] Serial: AMBA driver [ 22.279660] msm_serial: driver initialized Lines omitted here [ 35.357215] rc_core: IR keymap rc-cec not found [ 35.357467] Registered IR keymap rc-empty [ 35.357758] rc rc0: vc4 as /devices/platform/soc/3f902000.hdmi/rc/rc0 [ 35.358014] input: vc4 as /devices/platform/soc/3f902000.hdmi/rc/rc0/input3 [ 35.363626] debugfs: Directory '3f902000.hdmi' with parent 'vc4-hdmi' already present! [ 35.393628] vc4-drm soc:gpu: bound 3f902000.hdmi (ops vc4_hdmi_ops [vc4]) [ 35.394015] vc4-drm soc:gpu: bound 3f806000.vec (ops vc4_vec_ops [vc4]) [ 35.394255] vc4-drm soc:gpu: bound 3f400000.hvs (ops vc4_hvs_ops [vc4]) [ 35.394534] vc4-drm soc:gpu: bound 3f004000.txp (ops vc4_txp_ops [vc4]) [ 35.394782] vc4-drm soc:gpu: bound 3f206000.pixelvalve (ops vc4_crtc_ops [vc4]) [ 35.395029] vc4-drm soc:gpu: bound 3f207000.pixelvalve (ops vc4_crtc_ops [vc4]) [ 35.395266] vc4-drm soc:gpu: bound 3f807000.pixelvalve (ops vc4_crtc_ops [vc4]) [ 35.395466] vc4-drm soc:gpu: bound 3fc00000.v3d (ops vc4_v3d_ops [vc4]) [ 35.396273] checking generic (3e330000 8ca000) vs hw (0 ffffffffffffffff) [ 35.396287] fb0: switching to vc4drmfb from EFI VGA [ 35.413890] Console: switching to colour dummy device 80x25 [ 35.428230] [drm] Initialized vc4 0.0.0 20140616 for soc:gpu on minor 0 [ 35.520035] Console: switching to colour frame buffer device 240x75 [ 35.560649] vc4-drm soc:gpu: [drm] fb0: vc4drmfb frame buffer device Let me know what other information I may be able to provide -- You are receiving this mail because: You are on the CC list for the bug.