That’s just what that specific user has. That commit has nothing to do with CPUs.
What do you mean by “hopefully”? That kernel is not booting, exactly like the others. I tried 3 times. 5.10.192-1 instead booted perfectly fine, as usual.
Eh, was joking. 
Then you have some other problems or some other commits should also be reverted.
I have a Xeon, but it does not seem it is relevant.
I admit it may be it, but it is difficult to say. I do not see anything peculiar. They seem to refer to the same commit we are talking about, but if @anon51566685 actually reverted it in the kernel he provided, I could still reproduce without it.
If you’d like you can test first two kernels I posted. One is 6.1.45 basically and the other is inbetween .46.
I see. If I’ll find the time, I’ll prepare some kernels to test, but testing a possibly broken/degraded SSD may be unacceptable once reported.
I’m sorry I created such long threads, but apparently I experienced two different unrelated sudden issues at the same time. This made it difficult to track down the causes.
Ouch! I missed those builds, sorry! I’ll test as soon as I can replace the SSD again.
I should probably actually read everything in those bug reports. Because that user actually said reverting that commit didn’t help, heh. No idea why is it even mentioned.
And then there is some other commit that is not even present in 6.1… oh well…
Btw, can you also post lspci?
This is the result of the bisection in that bugreport: LKML: Genes Lists: Re: Possible nvme regression in 6.4.11.
Also they mention the card reader. Didn’t try to blacklist it. I could try that to see if that is somehow my case.
00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers (rev 05)
00:01.0 PCI bridge: Intel Corporation 6th-10th Gen Core Processor PCIe Controller (x16) (rev 05)
00:02.0 VGA compatible controller: Intel Corporation HD Graphics P630 (rev 04)
00:04.0 Signal processing controller: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem (rev 05)
00:14.0 USB controller: Intel Corporation 100 Series/C230 Series Chipset Family USB 3.0 xHCI Controller (rev 31)
00:14.2 Signal processing controller: Intel Corporation 100 Series/C230 Series Chipset Family Thermal Subsystem (rev 31)
00:15.0 Signal processing controller: Intel Corporation 100 Series/C230 Series Chipset Family Serial IO I2C Controller #0 (rev 31)
00:15.1 Signal processing controller: Intel Corporation 100 Series/C230 Series Chipset Family Serial IO I2C Controller #1 (rev 31)
00:16.0 Communication controller: Intel Corporation 100 Series/C230 Series Chipset Family MEI Controller #1 (rev 31)
00:17.0 SATA controller: Intel Corporation Q170/Q150/B150/H170/H110/Z170/CM236 Chipset SATA Controller [AHCI Mode] (rev 31)
00:1c.0 PCI bridge: Intel Corporation 100 Series/C230 Series Chipset Family PCI Express Root Port #1 (rev f1)
00:1c.1 PCI bridge: Intel Corporation 100 Series/C230 Series Chipset Family PCI Express Root Port #2 (rev f1)
00:1d.0 PCI bridge: Intel Corporation 100 Series/C230 Series Chipset Family PCI Express Root Port #9 (rev f1)
00:1d.4 PCI bridge: Intel Corporation 100 Series/C230 Series Chipset Family PCI Express Root Port #13 (rev f1)
00:1d.6 PCI bridge: Intel Corporation 100 Series/C230 Series Chipset Family PCI Express Root Port #15 (rev f1)
00:1f.0 ISA bridge: Intel Corporation CM238 Chipset LPC/eSPI Controller (rev 31)
00:1f.2 Memory controller: Intel Corporation 100 Series/C230 Series Chipset Family Power Management Controller (rev 31)
00:1f.3 Audio device: Intel Corporation CM238 HD Audio Controller (rev 31)
00:1f.4 SMBus: Intel Corporation 100 Series/C230 Series Chipset Family SMBus (rev 31)
01:00.0 3D controller: NVIDIA Corporation GM107GLM [Quadro M1200 Mobile] (rev a2)
02:00.0 Network controller: Intel Corporation Wireless 8265 / 8275 (rev 78)
03:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS525A PCI Express Card Reader (rev 01)
04:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD Controller SM981/PM981/PM983
06:00.0 PCI bridge: Intel Corporation DSL6340 Thunderbolt 3 Bridge [Alpine Ridge 2C 2015]
07:00.0 PCI bridge: Intel Corporation DSL6340 Thunderbolt 3 Bridge [Alpine Ridge 2C 2015]
07:01.0 PCI bridge: Intel Corporation DSL6340 Thunderbolt 3 Bridge [Alpine Ridge 2C 2015]
07:02.0 PCI bridge: Intel Corporation DSL6340 Thunderbolt 3 Bridge [Alpine Ridge 2C 2015]
3e:00.0 USB controller: Intel Corporation DSL6340 USB 3.1 Controller [Alpine Ridge]
I guess if you really want to get a real answer, it is probably better if I simply bisect the kernel directly as I was doing before.
What would be the quickest way to do it? I was using this: AUR (en) - linux-git. Can I use it to build specific commits in the stable kernel git? Can I makepkg incrementally, without having to clean from one build to the following?
You should indeed try mentioned workarounds (blacklisting, adding kernel params).
Yes you can. You have to edit remote file - for commit put some tag, eg. v6.1.45. Build that. Then just cd src/linux-torvalds, bisect it and run makepkg -fers and repeat.
If you want to do it in clean chroot, you probably need to edit PKGBUILD itself. Was to lazy to do that myself.
Bisection completed: the offending commit is this: kernel/git/stable/linux.git - Linux kernel stable tree.
I guess this 217802 – regression NVME failure in 6.4.11 : 6.4.10 works fine. is exactly my problem. I’ll add this info but I guess it is not very useful. They already knew this weeks ago, but they are leaving it like it is for some reason. This is really a bad situation, I’m pretty disappointed.
Thank you for your help!
1 Like
This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.