Comment # 55
on bug 109206
from Ondrej Lang
(In reply to Joe Coutcher from comment #54) > Ondrej - I'm on a fresh install of Ubuntu 19.04 with no workarounds applied, > using a similar setup to yours (HP Envy x360 15m-bq121dx.) I installed > kernel 5.2 RC7 (since the AMD64 build of 5.2 final on kernel.ubuntu.com is > broken), and updated to the latest linux-firmware package available on the > disco feed (1.178.2). I should also note I'm on HP BIOS firmware version > 21. While the system boots to the desktop environment, there's tons of > garbage, and when using Firefox, screen writes are occuring on random parts > of the screen. Also, I attempted running Basemark Web 3.0 in Firefox, and > can consistently lock up the machine. For reference, the kernel version is > 5.2.0-050200rc7-lowlatency. Hi Joe, I'm quite sure your issue is not related to this ticket. The problem in this bug report is quite specific and is related to the raven_dmcu.bin firmware. It has a specific symptom where the screen is not initialized during boot (stays blank / black) so I think you need to report your problem somewhere else. Also, it would be good if you can check the kernel log after crash and see what error messages you have and then google for that specific message to find if someone else already created a bug report for it. I have been running kernel 5.2 since yesterday and had no issues whatsoever. I also just run the Basemark Web 3.0 benchmark and had no issues. As for your lockups, I know that the AMD APU had problems with random lockups in earlier kernels (if I remember correctly it was related to the C-state changes of the CPU), I myself had the problem and for me the fix was to add "idle=nomwait" to my kernel parameters. That fixed the random lockups for me. Now I don't know if this issue has already been addressed, last time I tried without the parameter was kernel 5.0 I think and still had lockups, so this might not be related to your specific problem, but as I said, best course of action for you is to inspect the kernel log after a crash, check the error message and then search for a bug report with that error and report your findings there.
You are receiving this mail because:
- You are the assignee for the bug.
_______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/dri-devel
