You are not logged in.
With the AsRock board, there seems to be issues with the clock source coming from the board.. Even the time on my computer before was screwed up, and in the past few days, I was noticing jumps/incorrect time stamps in the system log.
Wondering if there's a real issue with the board, I think I am going to RMA it.
Last edited by ricky (2020-06-23 14:31:03)
Offline
The TSC behaving bad is strange. I thought the TSC is a clock source that's inside the CPU, not on the board? Maybe the board was doing something that made the whole CPU unstable? If things were just bad in general, the TSC misbehaving was then perhaps just one of the symptoms.
Offline
I've had this problem recently:
kernel: pcieport 0000:02:00.0: can't change power state from D3cold to D0 (config space inaccessible)
I don't know if this problem is the same as yours, but the reason for my problem is the incompatibility of bbswitch.
When I delete it, the system returns to normal (using live usb and mount partition as installing and then arch-chroot to the system, execute pacman-Rs bbswitch)
Offline
I've had this problem recently:
kernel: pcieport 0000:02:00.0: can't change power state from D3cold to D0 (config space inaccessible)
I don't know if this problem is the same as yours, but the reason for my problem is the incompatibility of bbswitch.
When I delete it, the system returns to normal (using live usb and mount partition as installing and then arch-chroot to the system, execute pacman-Rs bbswitch)
A have the same problem since around 10th October.
pci 0000:01:00.0: can't change power state from D3cold to D0 (config space inaccessible)
Geforce 940MX + bbswitch, i didn't have to remove, just it can't switch to the discrete nvidia card.
Offline