ASPM Could not configure common clock.

[Madhur Sharma]

I did a clean install of Debian 12 (32-bit) without any DE.
I've noticed that after grub menu, if it displays " pci (some numbers) ASPM Could not configure common clock", the system boots into cli properly.
But, if no such error is shown, a white underscore keeps blinking on the top left. Keyboard also does not work in this case, and I have to hard shut down the laptop with the power button.
The error is random so most of the time, I'm not able to boot into Debian.
What should I do to always boot into Debian/resolve the issue?

[fabien]

You can try setting the

Code: Select all

pcie_aspm=off

kernel parameter in GRUB. Use the temporary method first.

[Madhur Sharma]

You can try setting the

Code: Select all

pcie_aspm=off

kernel parameter in GRUB. Use the temporary method first.

Doing this will remove the error message "aspm could not...."?

[fabien]

I don't know, tell us. Mostly I hope this will prevent your boot failures.

[Madhur Sharma]

You can try setting the

Code: Select all

pcie_aspm=off

kernel parameter in GRUB. Use the temporary method first.

Doesn't work, booting is still a luck by chance. If the error "aspm could not...." is displayed, I'm able to boot. But, most of the time this error is not displayed so I've to hard shut down.
All of this is random, sometime it display the error but most of the time it doesn't.

[fabien]

Some information is needed that might give some clues.
Could you please post the output of

Code: Select all

#> inxi --slots -Fxxxaz

(inxi must be installed)
and

Code: Select all

#> lspci -vv >/tmp/sysPCIdata 2>&1; \
journalctl -b --no-hostname --no-pager -g "aspm|pci|error" >>/tmp/sysPCIdata; \
echo -e "\n\n" >>/tmp/sysPCIdata; \
journalctl -b --no-hostname --no-pager >>/tmp/sysPCIdata; \
gzip /tmp/sysPCIdata

Please post sysPCIdata.gz as attachment.

Are there any records of your last boot failure in the logs?
You can check if the previous boot corresponds to the boot failure with

Code: Select all

#> journalctl -b -1

If so, could you please post (as an attachment)

Code: Select all

#> journalctl -b -1 --no-hostname --no-pager | gzip >/tmp/PCIbootfailure.gz

[fabien]

Hello @Madhur Sharma, have you progressed?

[Madhur Sharma]

Hello @Madhur Sharma, have you progressed?

Sorry, couldn't reply had some exams.
Tried to install some other distro and I've wiped the disk. Installation wasn't successful.
I'll try once again with Debian this time but not anytime soon as I've more exams in upcoming months so I won't be able to tinker with the laptop.
Thank you for helping.

[fabien]

Hello, thanks for letting us know.
You mentioned that you installed a 32-bit version. Since you are going to reinstall, maybe test a 64-bit version if possible?
In the meantime, I wish you the best for your exams.

[Madhur Sharma]

Hello, thanks for letting us know.
You mentioned that you installed a 32-bit version. Since you are going to reinstall, maybe test a 64-bit version if possible?
In the meantime, I wish you the best for your exams.

Thank you.
But the laptop has a 32-bit processor (Intel T2400 @ 1.83ghz).

[Aki]

Hello,

[..] I've noticed that after grub menu, if it displays " pci (some numbers) ASPM Could not configure common clock", the system boots into cli properly. But, if no such error is shown, a white underscore keeps blinking on the top left. Keyboard also does not work in this case, and I have to hard shut down the laptop with the power button. The error is random so most of the time, I'm not able to boot into Debian. What should I do to always boot into Debian/resolve the issue?

The "ASPM Could not configure common clock" could not be in the root cause of the computer freeze. There's probably a hardware issue that shows up sometimes for some reason.

Are you dual booting (with windows) your computer ?

What is your computer (manufacturer and model) ? You can use the inxi command to give more information.

Can you please send a full log of you booting process when it works ? You can use the following command:

Code: Select all

script log.txt
su -l -c "journalctl -b --no-pager"
exit

You can report the file log.txt in one the following ways:

• paste them into the Debian Pastezone service (https://paste.debian.net) and report the URL/link of the paste in a follow-up message

• attaching the logs to a follow-up forum message as a compressed zip or gz file

• paste logs into the body of a follow-up message between code tags (if they fit the size of a forum message)

Note: see your other previous discussion, in which it is reported that you have probably an not properly configured video adapter:

• Debian 12 installation without any DE