On 2021-06-08 at 07:27, Greg Wooledge wrote:
> On Tue, Jun 08, 2021 at 12:05:21PM +0200, Thom Castermans wrote:
>
>> How can I debug this problem? My suspicion is that this has to do with the
>> kernel upgrade between stable and testing (4.19 to 5.10), but I'm not sure.
>>
>> Things I have tried so far:
>> - Ran smartctl test on the SSD: no issues reported.
>> - Ran memtest86: no issues reported [6].
>> (I am not suspecting hardware issues anyway, because buster is running fine
>> currently.)
>> - Chose different options for partitioning during install: tried encrypted
>> LVM, LVM and plain old ext4. Using full disk every time. This is because I
>> also saw error messages about LVM not being able to find the volume groups
>> a couple of times, but I did not take pictures unfortunately. It also
>> seemed to work anyway, because the partitions would be mounted correctly in
>> the few instances that booting succeeded.
>> - Installed non-free firmware (used the unofficial image [1]) during
>> installation and installed the intel-microcode package after installation
>> in an attempt to fix the error displayed in [4] ("[Firmware Bug]:
>> TSC_DEADLINE disabled due to Errata: please update microcode to
>> version: 0x22 (or later)").
>
> The first and most obvious thing you should try is booting the buster
> kernel, and seeing whether the problem still occurs. This will let
> you know whether the problem is in the kernel, or somewhere else.
Given that he's said that buster is running fine, I understand that he
did in fact already do this. Unless you specifically mean booting the
buster kernel with the testing userland?
> I'm also quite confused how you tested "chose different options...
> during install" to fix a problem that was introduced on a single
> machine after a dist-upgrade. Surely you don't mean you reinstalled
> buster and then dist-upgraded again... that would be dramatically
> masochistic, especially if you hadn't even tested using the previous
> kernel.
If you look back at part of the opening paragraph (snipped in your quote
above), he also said:
>> Thinking I may have done something wrong during upgrade, I created
>> a fresh testing installation image on a USB stick and installed
>> that. Installation finished without errors, but I got the same
>> problems on boot, even the first one after install.
So he doesn't just get the problem on dist-upgrade, but also on a clean
install of testing, and that latter is how he's been doing most of his
(er) testing of the problem.
It really does sound like he's been doing multiple reinstalls, and even
probably reinstalled buster after the latest failed install of testing,
since if I'm reading him right A: he's currently using the machine
involved, including to post this question, and B: he's currently running
buster on it, despite having done the experimentation above.
--
The Wanderer
The reasonable man adapts himself to the world; the unreasonable one
persists in trying to adapt the world to himself. Therefore all
progress depends on the unreasonable man. -- George Bernard Shaw
Attachment:
signature.asc
Description: OpenPGP digital signature