Bug#1006149: linux-image-5.16.0-1-686: Fails to boot on T41 Thinkpads
On 3/9/22 23:45, Axel Beckert wrote:
> Hi Damien,
>
> Damien Le Moal wrote:
>>> Ok, did another one, this time with "debug loglevel=7" added on the
>>> kernel commandline by editing it in GRUB:
>>>
>>> https://noone.org/debian/Bug-Reports/1006149/DSCN5259.MOV
>>
>> Thanks for this. But unfortunately, it does not tell us much as to what
>> is going on...
>
> Ah, what a pity. Thanks for having a look anyways.
>
>> Could you send me dmesg output of a clean boot with 5.15
>> kernel ?
>
> Sure. I already posted this to the Debian bug report at
> https://bugs.debian.org/cgi-bin/bugreport.cgi?att=2;bug=1006149;filename=5.15.15-2.dmesg.xz;msg=96
> shortly before you got into the loop.
Nothing stands out here, all normal.
>
>> Also, once booted in 5.15, install sg3utils and run these commands:
>>
>> sudo sg_sat_read_gplog --log=0 --page=0 /dev/sdX
>> sudo sg_sat_read_gplog --log=0 --page=0 --dma /dev/sdX
>
> [I find it disturbing how often people just prepend "sudo" in
> instructions when they actually mean "as root". Not everyone has sudo
> installed — usually for good reasons.]
And some distros do not have a root user.. Not being a Debian user
myself, I do not know which one it is. Yes, I meant execute "as root".
>
> # sg_sat_read_gplog --log=0 --page=0 /dev/sda
> 00 0001 0000 0000 0002 0000 0000 0000 0000 .. .. .. .. .. .. .. ..
> 08 0000 0000 0000 0000 0000 0000 0000 0000 .. .. .. .. .. .. .. ..
> 10 0000 0000 0000 0000 0000 0000 0000 0000 .. .. .. .. .. .. .. ..
> 18 0000 0000 0000 0000 0000 0000 0000 0000 .. .. .. .. .. .. .. ..
> 20 0000 0000 0000 0000 0000 0000 0000 0000 .. .. .. .. .. .. .. ..
> 28 0000 0000 0000 0000 0000 0000 0000 0000 .. .. .. .. .. .. .. ..
> 30 0000 0000 0000 0000 0000 0000 0000 0000 .. .. .. .. .. .. .. ..
> 38 0000 0000 0000 0000 0000 0000 0000 0000 .. .. .. .. .. .. .. ..
> 40 0000 0000 0000 0000 0000 0000 0000 0000 .. .. .. .. .. .. .. ..
> 48 0000 0000 0000 0000 0000 0000 0000 0000 .. .. .. .. .. .. .. ..
> 50 0000 0000 0000 0000 0000 0000 0000 0000 .. .. .. .. .. .. .. ..
> 58 0000 0000 0000 0000 0000 0000 0000 0000 .. .. .. .. .. .. .. ..
> 60 0000 0000 0000 0000 0000 0000 0000 0000 .. .. .. .. .. .. .. ..
> 68 0000 0000 0000 0000 0000 0000 0000 0000 .. .. .. .. .. .. .. ..
> 70 0000 0000 0000 0000 0000 0000 0000 0000 .. .. .. .. .. .. .. ..
> 78 0000 0000 0000 0000 0000 0000 0000 0000 .. .. .. .. .. .. .. ..
> 80 0010 0000 0000 0000 0000 0000 0000 0000 .. .. .. .. .. .. .. ..
> 88 0000 0000 0000 0000 0000 0000 0000 0000 .. .. .. .. .. .. .. ..
> 90 0000 0000 0000 0000 0000 0000 0000 0000 .. .. .. .. .. .. .. ..
> 98 0000 0000 0000 0000 0000 0000 0000 0000 .. .. .. .. .. .. .. ..
> a0 0000 0000 0000 0000 0000 0000 0000 0000 .. .. .. .. .. .. .. ..
> a8 0000 0000 0000 0000 0000 0000 0000 0000 .. .. .. .. .. .. .. ..
> b0 0000 0000 0000 0000 0000 0000 0000 0000 .. .. .. .. .. .. .. ..
> b8 0000 0000 0000 0000 0000 0000 0000 0000 .. .. .. .. .. .. .. ..
> c0 0000 0000 0000 0000 0000 0000 0000 0000 .. .. .. .. .. .. .. ..
> c8 0000 0000 0000 0000 0000 0000 0000 0000 .. .. .. .. .. .. .. ..
> d0 0000 0000 0000 0000 0000 0000 0000 0000 .. .. .. .. .. .. .. ..
> d8 0000 0000 0000 0000 0000 0000 0000 0000 .. .. .. .. .. .. .. ..
> e0 0001 0001 0000 0000 0000 0000 0000 0000 .. .. .. .. .. .. .. ..
> e8 0000 0000 0000 0000 0000 0000 0000 0000 .. .. .. .. .. .. .. ..
> f0 0000 0000 0000 0000 0000 0000 0000 0000 .. .. .. .. .. .. .. ..
> f8 0000 0000 0000 0000 0000 0000 0000 0000 .. .. .. .. .. .. .. ..
So this drive does not support any log page, none. So the patch that is
referenced in the bug report, which increases the timeout value for read
log commands should really not matter since there should be no access to
any log page but the above, which seems OK. So something funky is going
on, and I fail to see how that patch referenced matters.
Unfortunately, I do not have any drive like the above, so hard to test
locally. The oldest drives I have all support some log pages...
Let me dig a little more.
> # sg_sat_read_gplog --log=0 --page=0 --dma /dev/sda
> ATA PASS-THROUGH (16), bad field in cdb
> sg_sat_read_gplog failed: Illegal request
> #
OK. No DMA read log for this drive. That's OK.
>
> Since the last output might be a hardware-specific issue, here some
> more information on /dev/sda:
>
> # fdisk -l /dev/sda
> Disk /dev/sda: 149.05 GiB, 160041885696 bytes, 312581808 sectors
> Disk model: SAMSUNG HM160HC
> Units: sectors of 1 * 512 = 512 bytes
> Sector size (logical/physical): 512 bytes / 512 bytes
> I/O size (minimum/optimal): 512 bytes / 512 bytes
> Disklabel type: dos
> Disk identifier: 0x000500cc
>
> Device Boot Start End Sectors Size Id Type
> /dev/sda1 * 63 993279 993217 485M 83 Linux
> /dev/sda3 996030 2988089 1992060 972.7M 82 Linux swap / Solaris
> /dev/sda4 2988090 312576704 309588615 147.6G 5 Extended
> /dev/sda5 2988153 86874232 83886080 40G 83 Linux
> # smartctl --info /dev/sda
> smartctl 7.2 2020-12-30 r5155 [i686-linux-5.15.0-3-686-pae] (local build)
> Copyright (C) 2002-20, Bruce Allen, Christian Franke, www.smartmontools.org
>
> === START OF INFORMATION SECTION ===
> Model Family: SAMSUNG SpinPoint M5
> Device Model: SAMSUNG HM160HC
> Serial Number: S12TJD0SA62821
> LU WWN Device Id: 5 0f0000 003162821
> Firmware Version: LQ100-10
> User Capacity: 160’041’885’696 bytes [160 GB]
> Sector Size: 512 bytes logical/physical
> Device is: In smartctl database [for details use: -P show]
> ATA Version is: ATA8-ACS, ATA/ATAPI-7 T13/1532D revision 0
Need to check that and what is expected with this version.
> Transport Type: Parallel, Unknown (0x00f)
> Local Time is: Wed Mar 9 15:25:44 2022 CET
> SMART support is: Available - device has SMART capability.
> SMART support is: Enabled
>
> HTH.
>
> Regards, Axel
--
Damien Le Moal
Western Digital Research
Reply to: