Bug#1006149: linux-image-5.16.0-1-686: Fails to boot on T41 Thinkpads
On 3/8/22 05:54, Axel Beckert wrote:
> Hi Damien,
>
> one of the affected users here.
>
> Damien Le Moal wrote:
>> In the bug report, I did not see a dmesg output for a failed boot. But I
>> guess it is because the user cannot capture it.
>
> Correct.
Could you try taking a video of the boot messages ?
Log page 0 is the log directory which indicates the log pages supported
by the device. This directory page is always supported, so failing to
access it means normally a buggy drive. However, since things are
working with 5.15, I would like to understand what is going on and which
part of the device scan is failing. For that, booting with
logging_level=7 (debug) and having the kernel messages would help.
>
>> Could you have a look at this bug report for Fedora:
>>
>> https://bugzilla.kernel.org/show_bug.cgi?id=215519
>>
>> This Debian case does sound similar. The problem is fixed with commit:
>>
>> fda17afc6166 ("ata: libata-core: Fix ata_dev_config_cpr()")
>>
>> which is included in kernel 5.16.9.
>
> Then it didn't help.
>
>> Could the users try that kernel version to see if that fixes the
>> issue ?
>
> Both affected users already tried 5.16.11 and the issue is still
> there.
>
> Nevertheless thanks for your prompt reply and all the details so far!
>
> Regards, Axel
--
Damien Le Moal
Western Digital Research
Reply to: