Ubuntu 20.04 freeze after few seconds on an hp 15-dw1069nl

[Marco Ciampa]

Some days ago I helped one of my friends who bough an HP laptop (15-dw1069nl ... Intel i7-10510U - nvidia GM108M(GeForce MX130)). I installed Ubuntu 20.04 on it without problems (not checked every details thought). He said that the problem happened after an update. After a few secs after it boots, it freezes. No way to do anything. I tried myself ... it happens even in the emergency console (i.e. without X...)! I tried reinstalling Ubuntu 20.04 myself. Yes, it fixes it...but true, until the next update! After the update... count 1 to 5 after the boot and it is completely frozen.

For the time being I resolved installing an oem kernel version (linux-image-oem-20.04d -> linux-image-5.14.0-1020-oem and fixed nvidia driver after install of package linux-oem-20.04d which installed the missing kernel headers files...
BTW:

    - the driver panel says that wifi does not work (RTL 8169) but actually it works flawlessly
    - the screen brightness keys do not work (but the sound keys do work). It's probably only the keys, since using the cursor, luckily, you can regulate the screen backlight. xev report no key press at all...

I am reporting this mainly for a heads up to the Ubuntu dev folks because I, somehow - but I do not know exactly how - resolved, and probably the same problems happen to the whole hp 15-sw10xx series...
Please note that I have not direct access to that machine. So I may can additional tests in the future but not easily/immediately.

lsb_release -d
Description: Ubuntu 20.04.3 LTS

[Ubuntu Foundations Team Bug Bot (crichton)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1959367/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

[Paul White (paulw2u)]

Marco, further to comment #1 this issue needs assigning to an Ubuntu package in order for it to be looked at by the "Ubuntu dev folks" who seldom subscribe to bug reports tasked to the Ubuntu project in general.

You seem to be saying that this issue was with a 'generally available' kernel but fixed with an 'oem' kernel so I'm assigning this to the 'linux' package.

Please execute the following command only once, as it will automatically gather debugging information, in a terminal:

  apport-collect 1953967

from the affected machine while the generally available kernel is active. If this is not possible then please add a comment to confirm this.

When reporting bugs in the future please use apport by using 'ubuntu-bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs.

[Marco Ciampa (ciampix)]

Sorry but it is nearly impossible to do anything with the system. When you update the kernel you have almost 5 seconds and then it freeze. It is impossible to do _any_ kind of log...

[Paul White (paulw2u)]

Yes, I understand that but which version of the kernel is affected? From which version did the upgrade take place and to which new version did the machine upgrade? Presumably the freeze happened when the machine rebooted to the new kernel?

Unsubscribing and leaving to the kernel to team to investigate.

[Marco Ciampa (ciampix)]

I tried a few, with the same results (5.4.0-96-generic and 5.13.0-27-generic signed and unsigned for sure). I started to think that it was because of something external of the kernel when I noticed that with the "oem" series of kernels the problem just vanished. I tried some of the "oem" series but it seems that all works right away. Hope this has some meaning for you...

[Marco Ciampa (ciampix)]

Also I am not sure of from which version the problem did show up since it was not me that did the upgrade that triggered the problem. If you can grab one of those hp laptops that seems that they are _very_ common (my friend bough it from Mediaworld) perhaps you can bisect and find the point when exactly this problem arose. I also thought that the wifi kernel module could be blamed of all this because of the strange behaviour of the drivers dialog that reports that it does not work but actually it seems to work fine... strange hu?

[Launchpad Janitor (janitor)]

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]