Score:0

Ubuntu server 22.04 fresh build locks up completely on HP prodesk 600 g4 mini

ci flag

I'm trying to install Ubuntu on my new to me HP prodesk 600 g4. It's second hand but from a refurb company so it should be in an ok state hardware wise.

The first time I noticed issues with the install was when the keyboard taps wouldn't respond during the install process from a live USB boot. I thought it was my keyboard's fault but I use this keyboard all the time and never had an issue. After forcing a hard reboot each time I did this the system would lock up at progressively sooner points in the process, often not even getting to the install wizard.

I managed to get it installed, but it locked up almost straight away on first boot.

I reflashed the install media just in case it was corrupt, tried again trying to tap through the wizard as fast as I could to avoid lockups, and it still did it.

I disabled secure boot and tried again, no change.

I reset the BIOS settings, re-disabled secure boot and tried again, no change.

I hypothesised that it was the CPU maybe locking up from inadequate cooling, but I managed to install sensors package and it's idling at 37-39 Celsius.

I've even tried Ubuntu 20.04 just in case it was a new problem, and the same thing happened after first boot.

The box came with windows installed, but I never gave that a go because I never had the intention of using it so I don't know if the issue was there too.

I have done a full memtest86 and it showed absolutely no errors at all.

I thought I had a breakthrough when I tried taking out one stick of ram and tying again, ignoring the memtest and it miraculously seemed to run fine for a few hours! Wow, it might be ram I thought. I swapped the stick and slot and it still worked fine. So I put both sticks back in and tried again and it ran for several hours overnight. Strange, maybe the ram just needed to be reseated?

This morning I went to check on it and nope, it's locked up again.

When it locks up there are no errors, no warnings, no oddness in the screen or SSH session. It literally just pauses and the cursor on screen stops blinking.

I checked the last logs with journalctl -b -1 -e and it showed one error: i915 0000:00:02.0: [drm] *error* cpu pipe a fifo underrun. I have no idea if this is related but searches online don't seem to show the same behaviour. People with this seem to experience graphical glitches but the computer keeps running.

When booting live OSes from ventoy it seems to run fine. I haven't tried many options but hirens bootcd seems to work with no issues and memtest86 ran all the way through without locking up so I think it's Ubuntu 22.04 or kernel specific but I don't know enough to be sure.

I've also seen some theories about NVIDIA drivers but to my knowledge this doesn't have an NVIDIA GPU in it so I don't think it should be that?

Please any help would be greatly appreciated.

After the most recent freeze I looked at journalctl again and that same error wasn't even there that time. I'm not sure it's related, I've only seen that once. I can't seen any other relevant warnings in journalctl. There is also absolutely nothing in /var/crash. It's like it just freezes in time.

I have verified the ISO is valid as per one suggestion also. It is valid.

The next thing I might try is unplugging the HDMI cable and letting it run headless. I only have HDMI on the HP FlexIO port and haven't used the other displayport ports.

Running headless didn't solve it

2fst4u avatar
ci flag
Which media specifically do you mean? The install media that it's being installed to? I've never seen a check like that, can you point me in the direction of how to check it?
2fst4u avatar
ci flag
Are you just saying to confirm the hash of the ISO is correct? The exact same thing happened with 20.04 so while I'm not ruling out doing this, it does seem like the symptoms point to something other than just a corrupted ISO download.
guiverc avatar
cn flag
No I wasn't ... a badly downloaded ISO can occur but in my experience that's extremely rare. USB *flash* media however is a *cheap consumable* however, and I find 5-8% of ISO writes fail using *sandisk* (*worse failure rate on other brands*) thus its the write of ISO to media that I was trying to get you to confirm. Some ISO write software also alters (re-formats the image) data as written to media, which can help some devices but hurt others; thus the validation of the checksum on booting I consider pretty essential if I want to trust the system, and critical if you have any problem.
2fst4u avatar
ci flag
Ok I'll try this when I can. I have tried two different forms of boot media though from different brands entirely. It does seem a bit farfetched but I'll try it.
guiverc avatar
cn flag
Do note: If you way of writing the ISO to media is faulty; and you use that method to write the same *valid* ISO to two different installation media I'd still expect two *invalid* media.. I prefer *clone* writes myself; whilst I realize there are reasons for other alternatives - they can create issues & thus validation is worth it (*unless you have the days/weeks needed to track down issues created*). It's just my opinion; but I write >250 ISOs to media per year for QA purposes.
2fst4u avatar
ci flag
My ISO has checked as OK according to that method. I have made the boot media with balena etcher and ventoy, on two different usb flash drives. I don't think this is the issue.
2fst4u avatar
ci flag
Also I note in a previous comment you mentioned "failure to install". The system doesn't fail to install, it installs fine but there is something wrong with it while it is running.
I sit in a Tesla and translated this thread with Ai:

mangohost

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.