Hammerhead screen freeze

I installed phosh on my hammeread and after a minute or two from boot the screen freezes. I can login using ssh and looking at dmesg i see is all made of "msm fd900000.mdss: pp done time out, lm=0" messages. I suspect there is something wrong with freedreno

Supposedly your suspicion is not totally wrong - https://patchwork.kernel.org/patch/11312579/

By Alexey Min on 2020-01-07T15:56:43

It is fixed in 5.5 branch https://github.com/masneyb/linux. We need upgrade hammerhead (postmarketos-qcom-msm8974) kernel package. I am unable to do it properly, there are some python errors.

By Daniel Kuťka on 2020-01-08T15:28:41

It has included first version of mentioned path https://lkml.org/lkml/2019/11/12/288 or https://github.com/masneyb/linux/commit/e6849409087363ef587d85a96c499f28fa551547

By Daniel Kuťka on 2020-01-08T14:55:42

I am unable to do it properly, there are some python errors.

Well, just upgrading the kernel should not be that hard.

What errors are you getting exactly?

Consider joining the chat to get realtime help and have it resolved fast:

https://wiki.postmarketos.org/wiki/Matrix_and_IRC

By Oliver Smith on 2020-01-11T22:42:31

added category::device type::bug labels

changed title from Hammerhead Phosh freeze to Hammerhead screen freeze

By Bart Ribbers on 2020-01-09T14:51:50

I just installed latest for hammerhead/default and the screen works about as well as it always has for me. My power key might be sticky though. My main problem is getting the screen to turn on reliably with the powerkey. I do see the 'msm fd9000000.mdss: pp done time out, lm=0' messages when I press the powerkey to turn the device back on, but the screen works fine for a while after that. (shelli UI). @MartijnBraam had experienced a screen freeze after 5 minutes or more, workaround for me is to powerkey a few times.

By Craig Comstock on 2020-03-31T04:32:07

I tested today an installation for hammerhead with phosh (mainline kernel 5.6.0-rc6).
I see the pmOS logo but phosh never shows up, and I get a lot of msm fd900000.mdss: pp done time out, lm=0 errors in dmesg.

I think this issue is not solved yet in the mainline MDP driver.

I see the same error messages in oneplus-bacon.

By Federico Amedeo Izzo on 2020-04-13T09:28:00

And the same are on samsung-klte

By Alexey Min on 2020-04-13T16:44:35

This issue that apparently affects most MSM8974 phones is related to the async mode of the Qualcomm MDP which is currently enabled in the mainline kernel.

As @dano.kutka pointed some months ago there is a kernel fork from masneyb which temporarily fixes this problem by reverting the commits enabling async mode.

In particular this is the revert commit.

Can we apply on linux-postmarketos this revert commit until the problem is fixed upstream?

By Federico Amedeo Izzo on 2020-04-14T19:49:30

I can try to test this revert. Maybe tonight if I'm lucky.

By Craig Comstock on 2020-04-14T20:35:05

I tested the revert patch by adding it to linux-postmarketos-qcom-msm8974.

Shortly after I found out that the said patch is already applied in linux-postmarketos here.

I will retest now the pmos on lg-hammerhead and see if the pp dome time out errors are still there

By Federico Amedeo Izzo on 2020-04-18T16:32:17

I still get the msm fd900000.mdss: pp done time out, lm=0 errors in dmesg on lg-hammerhead even if the revert patch is there.

Also I can confirm that the screen is black after pmOS splash screen. (phosh selected as UI)

Here is dmesg hammerhead_black_screen_dmesg.txt

By Federico Amedeo Izzo on 2020-04-18T16:44:32

If you press the power button two times after turning it on, phosh will come out.

In any case the screen dies some minutes later, usually preceded by

dmesg-hammerhead

This happens on 5.6.0-rc6. After happening, restarting lightdm does not unfreeze it.

In fact at first glance I confused it for #540 (closed).

EDIT: new dmesg.txt

By tallero on 2020-06-02T17:01:46

mentioned in issue #540 (closed)

By tallero on 2020-05-12T15:22:00

mentioned in issue #607 (closed)

By Alexey Min on 2020-06-07T12:26:49

I can somewhat reproduce this, here are the results of running a freshly built image with Phosh on hammerhead.

Photos:

• phosh-hammerhead
• phosh-hammerhead2
• phosh-pinephone-hammerhead

Booting:

• In about 1 of 5 tries, it gets stuck in console during boot, showing drm:adreno_request_fw: *ERROR* failed to load a330_pm4.fw (adreno_gpu.c). The firmware package is installed.
• The first two times it booted into Phosh, it crashed shortly afterwards.
• Then it did not crash anymore once Phosh was running, even if leaving it running for ten minutes or so and trying to run various applications.

Running applications:

• "simple" GTK+3 applications appear to be working fine (the welcome app, the calculator, text editor)
• Firefox always crashes directly after opening with an "Alignment trap" (dmesg)
• The keys on the virtual keyboard are smaller (#713 (closed))

Other observations (most of it is probably known already, but writing down just in case):

• Phosh can't power off the display, so it may look like it crashed when it should get powered off when it is idling
• Setting the brightness slider to 0% in the UI makes it go completely dark, which is not useful (you can't see the slider anymore to reverse it). On the PinePhone, at 0% the screen is still somewhat visible.
• Battery is always at 0%

CC: @masneyb, maybe there's something useful for you here.

All in all, when Phosh does boot up, I find very impressive how usable it is with a close-to mainline kernel on the Nexus 5. It would be great if the most annoying bugs could be worked out, and then we could add it to the "community" category of our devices.

By Oliver Smith on 2020-08-11T20:45:24

Not sure if following adds a useful data point, but for what it's worth:

• Just tried on Nexus 5 LG Hammerhead device.
• I am only interested in ssh access to my device, so after reading the issues people were having with Plasma and Phosh, I instead selected none for UI in pmbootstrap init step.
• Lack of UI did not help me ... Like Oliver and others above, I see the message drm:adreno_request_fw: *ERROR* failed to load a330_pm4.fw and then a continuous stream of msm fd900000.mdss: pp done time out, lm=0 on the screen

By Lane Merge on 2020-11-08T22:06:19

@LiftsAllShips : The pp done time out errors are fixed by this patch: https://github.com/msm8953-mainline/linux/commit/620fdb042751d5dfc143988778a5139f604ac886. I can't find an email address for the Junak user on GitHub to see if he/she would be willing to submit their fix upstream.

By Ghost User on 2020-11-18T05:07:42

@masneyb btw @notjunak already has some contributions accepted upstream - https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/drivers/pinctrl/qcom?id=0e74abf3a0a3a711145f11f3a782432a2df5f744

By Alexey Min on 2020-11-18T05:07:42

Do we have any patch for this issues in any postmarketos-linux branch?

I just got modem data connection working on hammerhead, but probably it broken something badly. Instead of screen freezes also ssh stopped working, so I think it crashes completely :<

EDIT: No, it's still just a screen.

By JuniorJPDJ on 2020-11-22T02:16:20

Any progress on this?

By AlexKurisu on 2021-01-10T15:34:03

So far none, and GPU/display state on msm8974 is getting only worse with each kernel upgrade.

But some work is ongoing in a direction to fix all unfixed issues on msm8974 platform, starting with iommu, gpu, ... maybe we'll get something working better than before eventually.

By Alexey Min on 2021-01-10T17:42:41

mentioned in commit a0b45427

By Luca Weiss on 2021-01-30T23:13:32

mentioned in merge request !1910 (closed)

By Luca Weiss on 2021-01-30T23:15:40

Fix for this was sent upstream: https://patchwork.kernel.org/project/linux-arm-msm/patch/20210127152442.533468-1-iskren.chernev@gmail.com/

By Alexey Min on 2021-01-31T06:10:19

added device-lg-hammerhead label

Much better with !2015 (merged) . General instabilities are still there but at least the screen is fluid in most situations.

By Luca Weiss on 2021-03-29T19:50:54

closed

Phosh still crashes for me after a while, and immediately when I try to open a QT application.

On the other side though, GNOME Shell on wayland never freezes; no freezes on all other X.Org sessions, too.

By tallero on 2021-07-28T12:39:13

Yea still borken for me

By Ecorous on 2021-11-20T14:42:48

mentioned in issue #1672 (closed)

By Zehkira on 2022-08-28T08:51:40