The Latest Kernel Release.

elcore · 10-26-2022, 06:31 AM

5.15.75-x64 seems fine here, not much to report.
The usual output, which is what I normally get notified about on my desktop (in bold):

Code:

mtrr: your CPUs had inconsistent variable MTRR settings

Code:

acpi PNP0C14:01: duplicate WMI GUID 05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on PNP0C14:00)

Code:

ext2 filesystem being mounted at /home supports timestamps until 2038 (0x7fffffff)

That last one doesn't make much sense to me, I wonder if there's a way to silence it and get notifed again in 2037.

kjhambrick · 10-26-2022, 06:46 AM

all --

Generic Kernel Version 5.15.75.kjh is running fine on my Slackware64 15.0 + Multilib LapTop.

ChangeLog-5.15.75 references CVE-2022-1184.

-- kjh

Code:

uname -msrpn: Linux kjhlt7.kjh.home 5.15.75.kjh x86_64 11th Gen Intel(R) Core(TM) i9-11900K @ 3.50GHz
firmware ...: kernel-firmware-20221024_0cac82d-noarch-1                # upgraded
NVidia Blob : NVIDIA-Linux-x86_64-520.56.06.run
VMWare Blob : VMware-Workstation-Full-16.2.3-19376536.x86_64.bundle

kjhambrick · 10-26-2022, 07:03 AM

elcore --

I also see the acpi dupe but that's it ...( I am using ext4 file systems )

-- kjh

Code:

# dmesg |grep -i -e mtrr -e 2038 -e guid -e ext2

[    0.377983] MMIO Stale Data CPU bug present and SMT on, data leak possible. See https://www.kernel.org/doc/html/latest/admin-guide/hw-vuln/processor_mmio_stale_data.html for more details.
[    4.396736] acpi PNP0C14:01: duplicate WMI GUID 05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on PNP0C14:00)
[    4.398961] acpi PNP0C14:02: duplicate WMI GUID 05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on PNP0C14:00)

p.s. as for the dupe ... see comments #10 and #18 here https://bugzilla.kernel.org/show_bug.cgi?id=201885 ( fixed in linux 6.1 )

marav · 10-26-2022, 07:17 AM

Quote:

Originally Posted by kjhambrick

elcore --

I also see the acpi dupe but that's it ...( I am using ext4 file systems )

-- kjh

Code:

# dmesg |grep -i -e mtrr -e 2038 -e guid -e ext2

[    0.377983] MMIO Stale Data CPU bug present and SMT on, data leak possible. See https://www.kernel.org/doc/html/latest/admin-guide/hw-vuln/processor_mmio_stale_data.html for more details.
[    4.396736] acpi PNP0C14:01: duplicate WMI GUID 05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on PNP0C14:00)
[    4.398961] acpi PNP0C14:02: duplicate WMI GUID 05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on PNP0C14:00)

p.s. as for the dupe ... see comments #10 and #18 here https://bugzilla.kernel.org/show_bug.cgi?id=201885 ( fixed in linux 6.1 )

This is the way to edit/modify the DSDT table:
https://forums.linuxmint.com/viewtop...cd655#p2077184

elcore · 10-26-2022, 08:50 AM

I don't have MMIO Stale Data CPU bug on this one, maybe on a laptop but I'll have to check.

And to expand on mtrr message:

Code:

[    4.783180] mtrr: your CPUs had inconsistent variable MTRR settings
[    4.783180] mtrr: probably your BIOS does not setup all CPUs.
[    4.783180] mtrr: corrected configuration.

That's likely happened because I disabled virtual cores in BIOS.

Edit: There's no MMIO Stale Data CPU bug on my laptop either, but there is some other stuff:

Code:

[    1.428314] acpi PNP0A03:00: [Firmware Info]: MMCONFIG for domain 0000 [bus 00-01] only partially covers this bridge

Code:

[    1.432733] HPET not enabled in BIOS. You might try hpet=force boot option

Code:

[    1.438455] pci 0000:02:09.0: bridge configuration invalid ([bus 00-00]), reconfiguring
[    1.438514] pci_bus 0000:03: extended config space not accessible
[    1.438542] pci_bus 0000:03: busn_res: can not insert [bus 03-02] under [bus 02] (conflicts with (null) [bus 02])
[    1.438556] pci_bus 0000:03: busn_res: [bus 03-02] end is updated to 06
[    1.438563] pci_bus 0000:03: busn_res: can not insert [bus 03-06] under [bus 02] (conflicts with (null) [bus 02])
[    1.438575] pci 0000:02:09.0: devices behind bridge are unusable because [bus 03-06] cannot be assigned for them
[    1.438584] pci 0000:00:14.4: bridge has subordinate 02 but max busn 06

Code:

[    2.124382] AMD-Vi: AMD IOMMUv2 functionality not available on this system - This is not a bug.

Code:

[    6.802321] resource sanity check: requesting [mem 0x000c0000-0x000dffff], which spans more than PCI Bus 0000:00 [mem 0x000d0000-0x000d1fff window]

Seems to work fine considering its age, even though that laptop's just a html reader / mp3 player today.
Do you figure the MMIO Stale data CPU bug is related to config i.e. is that the result of SMT being enabled on AMD CPU?

kjhambrick · 10-26-2022, 11:35 AM

elcore --

The MMIO 'Spectacular Bug' is Intel's fault.

This is Intel's writeup: Processor MMIO Stale Data Vulnerabilities and this is from kernel.org: Processor MMIO Stale Data Vulnerabilities

It is CPU specific and I believe it can be mitigated via a kernel boot parameter but I ignore it

-- kjh

Code:

# ./do-get-spectre-meltdown.sh

Wed Oct 26 11:22:58 CDT 2022

  Linux kjhlt7.kjh.home 5.15.75.kjh #1 SMP PREEMPT Wed Oct 26 06:07:23 CDT 2022 x86_64 11th Gen Intel(R) Core(TM) i9-11900K @ 3.50GHz GenuineIntel GNU/Linux

  dmesg
    microcode: microcode updated early to revision 0x54, date = 2022-03-17
    Linux version 5.15.75.kjh (root@kjhlt7.kjh.home) (gcc (GCC) 11.2.0, GNU ld version 2.37-slack15) #1 SMP PREEMPT Wed Oct 26 06:07:23 CDT 2022
    Command line: BOOT_IMAGE=/boot/vmlinuz-generic-5.15.75.kjh root=UUID=6c71cd77-2463-408e-a992-ad6064b0651b ro nvidia-drm.modeset=1
    DMI: Notebook X170KM-G/X170KM-G, BIOS 1.07.06LS1 01/11/2020

  cpuinfo
    CPU Name:   11th Gen Intel(R) Core(TM) i9-11900K @ 3.50GHz
    Microcode:  0x54
    CPU FMS:    06-a7-01
    UCode Pkg:  intel-microcode-20220809-noarch-1_SBo_kjh  ( updated Aug 13 17:02 )
    UCode File: /lib/firmware/intel-ucode/06-a7-01         ( updated Aug 13 17:01 )
    UCode Info: 001/001: sig 0x000a0671, pf_mask 0x02, 2022-03-17, rev 0x0054, size 103424
    CPU bugs:   spectre_v1, spectre_v2, spec_store_bypass, swapgs, mmio_stale_data, retbleed, eibrs_pbrsb

  vulnerability and mitigation files in /sys/devices/system/cpu/vulnerabilities/
    itlb_multihit:       Not affected
    l1tf:                Not affected
    mds:                 Not affected
    meltdown:            Not affected
    mmio_stale_data:     Mitigation: Clear CPU buffers; SMT vulnerable
    retbleed:            Mitigation: Enhanced IBRS
    spec_store_bypass:   Mitigation: Speculative Store Bypass disabled via prctl and seccomp
    spectre_v1:          Mitigation: usercopy/swapgs barriers and __user pointer sanitization
    spectre_v2:          Mitigation: Enhanced IBRS, IBPB: conditional, RSB filling, PBRSB-eIBRS: SW sequence
    srbds:               Not affected
    tsx_async_abort:     Not affected

Didier Spaier · 10-26-2022, 12:08 PM

Built and running 6.0.5, will upgrade for Slint-15.0 released yesterday with 6.0.3, because of this:

Quote:

Revert "btrfs: call __btrfs_remove_free_space_cache_locked on cache load failure
...
It causes many reported btrfs issues, so revert it for now.

It's not the first time I ship a new kernel two days in a row, but I'd rather not have to do that too often.

Didier Spaier · 10-26-2022, 12:10 PM

deleted duplicate

elcore · 10-26-2022, 12:44 PM

Quote:

Originally Posted by kjhambrick

elcore --

The MMIO 'Spectacular Bug' is Intel's fault.

This is Intel's writeup: Processor MMIO Stale Data Vulnerabilities and this is from kernel.org: Processor MMIO Stale Data Vulnerabilities

It is CPU specific and I believe it can be mitigated via a kernel boot parameter but I ignore it

-- kjh

OK, that explains it, I've had no idea what that was since I don't ever test on anything intel.
Had a small ATOM at some point, 2x Athlon, 1x Phenom, but those are re-located now.
All I have available here at this time:

Code:

Model name:                      AMD Ryzen 5 5600X 6-Core Processor

CPU max MHz:                     3700.0000
CPU min MHz:                     2200.0000

Vulnerability Itlb multihit:     Not affected
Vulnerability L1tf:              Not affected
Vulnerability Mds:               Not affected
Vulnerability Meltdown:          Not affected
Vulnerability Mmio stale data:   Not affected
Vulnerability Retbleed:          Not affected
Vulnerability Spec store bypass: Mitigation; Speculative Store Bypass disabled via prctl and seccomp
Vulnerability Spectre v1:        Mitigation; usercopy/swapgs barriers and __user pointer sanitization
Vulnerability Spectre v2:        Mitigation; Retpolines, IBPB conditional, IBRS_FW, STIBP disabled, RSB filling, PBRSB-eIBRS Not affected
Vulnerability Srbds:             Not affected
Vulnerability Tsx async abort:   Not affected


Model name:                      AMD Turion(tm) 64 Mobile Technology ML-32

CPU max MHz:                     1800.0000
CPU min MHz:                     800.0000

Vulnerability Itlb multihit:     Not affected
Vulnerability L1tf:              Not affected
Vulnerability Mds:               Not affected
Vulnerability Meltdown:          Not affected
Vulnerability Mmio stale data:   Not affected
Vulnerability Retbleed:          Not affected
Vulnerability Spec store bypass: Not affected
Vulnerability Spectre v1:        Mitigation; usercopy/swapgs barriers and __user pointer sanitization
Vulnerability Spectre v2:        Mitigation; Retpolines, STIBP disabled, RSB filling, PBRSB-eIBRS Not affected
Vulnerability Srbds:             Not affected
Vulnerability Tsx async abort:   Not affected

I've enabled mitigations, but I think that stuff like chrome/firefox leaks way more data than those CPU bugs.
This firefox output for example:

Code:

Sandbox: Unexpected EOF, op 0 flags 00 path /proc/cpuinfo

Nobody asked permission to access /proc but w/e it's just accessing it for "reasons"..
So I guess having mitigations is fine, but often made useless by other stuff that's running on the modern system.

cwizardone · 10-27-2022, 06:03 AM

FWIW: Built and installed the 6.0.5 kernel and so far, so good with the Nvidia-Linux-x86_64-470.141.03 kernel and driver from Sbo.
VirtualBox-7.0.2-154219-Linux_amd64.run is also running as it should.

Edit in: The problem streaming video in Firefox remains and now also affects Pale Moon. No problem streaming video in Vivaldi.

teoberi · 10-27-2022, 07:11 AM

Will we have another period of time without kernel updates?
I'll still be patient, now I'm busy with other more urgent problems than compiling kernels.

marav · 10-27-2022, 08:04 AM

Old & Weird Laptops Risk Seeing Broken Backlight Controls With Linux 6.1

Code:

As a warning and call for testing, old and "weird" laptops may broken backlight controls 
when moving to the Linux 6.1 kernel currently under development. Thus if invested in using 
an old laptop with a modern kernel version, it may be useful trying out a Linux 6.1 release 
candidate to help spot any regressions early.

https://www.phoronix.com/news/Linux-...top-Backlights

Didier Spaier · 10-27-2022, 08:26 AM

I had built and installed 6.1-rc1 on my desktop some days ago, glad I didn't try it on my laptop

cwizardone · 10-27-2022, 12:18 PM

Year 2022, Round 64.

Another batch of updates has been scheduled for release on Saturday, 29 October 2022, at approximately 16:00, GMT. If no problems are found while testing the release candidates, they might be available sometime on Friday (depending on your time zone).

The details:

6.0.6-rc1, with 94 patches, https://lkml.iu.edu/hypermail/linux/...0.3/07125.html

5.15.76-rc1, with 79 patches, https://lkml.iu.edu/hypermail/linux/...0.3/07129.html

5.10.151-rc1, with 79 patches, https://lkml.iu.edu/hypermail/linux/...0.3/07132.html

5.4.221-rc1, with 53 patches, https://lkml.iu.edu/hypermail/linux/...0.3/07136.html

Quote:

Greg Kroah-Hartman
Date: Thu Oct 27 2022 - 13:12:04 EST
..............
A process change for those who care.

Previously, all of the -rc patches have been sent to
linux-kernel@xxxxxxxxxxxxxxx. That turns out to be a lovely way to
stress-test email servers both on the sending, and receiving side.

The vger postmasters have done a valiant job in fixing up all sorts of
crazy issues that this has caused over the years, moving jobs to
different machines, moving some reciever domains to separate queues or
machines, and trying to debug loony gmail server issues. They have, and
continue to, do a wonderful job at all of this.

But the stable patch bombs were causing problems, no matter what. To
help try to aliviate the overally mail load on the main linux-kernel
list, I am now NOT sending all of the patches to lkml, only the -rc
announcements.

If you want to see all of the patches, they will all be cc:ed to the
stable@xxxxxxxxxxxxxxx list, and they should all show up almost
instantly on lore.kernel.org as they are getting sent also to the
patches@lists address as well.

So this should provide a bit of breathing room on the main linux-kernel
mailqueue for a while. And if you do want to see the full set of
patches, either use lore and the assorted tools that can easily get
emails out of it, or subscribe to the stable@vger mailing list.

thanks,

greg "I had a spam assassin rule named after me" k-h

3rensho · 10-28-2022, 06:21 AM

5.10.151 just appeared