<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"> <head> <meta http-equiv="Content-Type" content="text/html; charset=us-ascii"> <meta name="Generator" content="Microsoft Word 15 (filtered medium)"> <style></style> </head> <body lang="EN-US" link="#0563C1" vlink="#954F72" style="word-wrap:break-word"> <div class="WordSection1"> Hello,<o:p></o:p> <o:p> </o:p> This issue was initially reported at <a href="https://www.linuxquestions.org/questions/linux-hardware-18/intermittent-black-screen-on-lvds-display-with-gma500_gfx-driver-on-atom-n2600-4175732670/"> https://www.linuxquestions.org/questions/linux-hardware-18/intermittent-black-screen-on-lvds-display-with-gma500_gfx-driver-on-atom-n2600-4175732670/</a>. mrmazda suggested to report this on <a href="mailto:intel-gfx@lists.freedesktop.org">intel-gfx@lists.freedesktop.org</a>. I also created a gitlab issue at <a href="https://gitlab.freedesktop.org/drm/misc/-/issues/35">https://gitlab.freedesktop.org/drm/misc/-/issues/35</a>, but based on the comment ‘Hi. No one reads this issue tracker.’ here <a href="https://gitlab.freedesktop.org/drm/misc/-/issues/33">https://gitlab.freedesktop.org/drm/misc/-/issues/33</a> I decided to post to this list instead. Problem description follows:<o:p></o:p> <o:p> </o:p> Our device containing the Atom N2600 processor sometimes boots to a black display just before displaying an xfce desktop. When this problem occurs, I see the BIOS screen and startup text for grub and initramfs, but the screen goes black at some point before displaying the desktop and remains black. The backlight seems to work. This occurs about once out of every 5 reboots of my device. I am running Ubuntu 22 with an xfce desktop, but this same problem occurs on Ubuntu 20 with an LXQt desktop.<o:p></o:p> <o:p> </o:p> Our display is connected via an LVDS interface. I've used an oscillisciope to probe the LVDS A clock and the 3 data pair signals (A0-A2) when this problem occurs, and it appears that the processor is setting every pixel to black on the display. I suspect this is the casebecause if I force the display to solid black (via the command 'dd if=/dev/zero of=/dev/fb0' after pressing Ctrl+Alt+F1 to get into a virtual console) when the device starts normally I see the same activity on the LVDS clock and data lines. When the display is showing black the LVDS clock is running at 25MHz, the A0 data line is very busy, and the A1 and A2 data lines are idle. When this problem occurs everything else works fine - I can connect to the device via SSH and VNC. VNC shows the XFCE desktop I normally see.<o:p></o:p> <o:p> </o:p> I believe this is an issue with the gma500_gfx driver because if I blacklist the gma500_gfx driver, only the i915 driver is used (with a non-optimal 800x600 resolution) and no matter how many times I reboot this device the LVDS display always works as expected. <o:p></o:p> <o:p> </o:p> I've tried to debug this issue by using drm.debug=6 as a kernel command line argument and recompiling the gma500_gfx driver to output additional register information, but nothing I've seen yet in dmesg or xrandr output is different between a normal and bad boot up of this device. I've just discovered the intel-gpu-tools package, but most of those tools fail with a message 'Couldn't map MMIO region' or 'No known gpu found for chipset flags 0x1 (intel)'. I suspect these tools don't support the gpu in the Atom N2600 processor.<o:p></o:p> <o:p> </o:p> Note that when the problem occurs, if I switch from TTY7 (default) to TTY1 the display remains blank (ie. no text login prompt). Also I don't even see a mouse cursor. Once the device boots up with this issue, I haven't yet found a way to get the display working again without another reboot.<o:p></o:p> <o:p> </o:p> I'd appreciate any other debugging advice. I'm new to gpu debugging and have already looked into this problem for days.<o:p></o:p> <o:p> </o:p> Output from 'uname -a' is below. Attached is output from the more verbose lspci, dmesg (when the problem occurs with original driver and drm.debug=6), xrandr, dmidecode and intel_bios_dumper commands.<o:p></o:p> <o:p> </o:p> volaris@Ubuntu-V8:~$ uname -a<o:p></o:p> Linux Ubuntu-V8 5.15.0-72-generic #79-Ubuntu SMP Wed Apr 19 08:22:18 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux<o:p></o:p> <o:p> </o:p> Thank you,<o:p></o:p> Jared<o:p></o:p> </div> </body> </html>