stable

kernel-6.3.4-201.fc38, kernel-headers-6.3.3-200.fc38, & 1 more

FEDORA-2023-514965dd8a created by jforbes a year ago for Fedora 38

The 6.3.3 stable kernel rebase contains a several new features, additional hardware support, and a number of important fixes across the tree.

Reboot Required
After installing this update it is required that you reboot your system to ensure the changes supplied by this update are applied properly.

How to install

Updates may require up to 24 hours to propagate to mirrors. If the following command doesn't work, please retry later:

sudo dnf upgrade --refresh --advisory=FEDORA-2023-514965dd8a

This update has been submitted for testing by jforbes.

a year ago

This update's test gating status has been changed to 'waiting'.

a year ago

This update's test gating status has been changed to 'failed'.

a year ago
User Icon g6avk commented & provided feedback a year ago
karma

Works for me, I have been testing the 6.3.x kernels for the test week with no issues. The enabled Default and Performance tests pass OK.

Work Station > Ryzen5 5600g/AMDGPU 400 Series Chipset. (UEFI + Secure Boot). SSD's > RAID1 (ext4) , running Plasma DE from Zawertun's COPR.

This update has been pushed to testing.

a year ago
User Icon bojan commented & provided feedback a year ago
karma

Works.

This update's test gating status has been changed to 'waiting'.

a year ago

This update's test gating status has been changed to 'passed'.

a year ago

This update can be pushed to stable now if the maintainer wishes

a year ago
User Icon solopasha commented & provided feedback a year ago
karma

disabled CONFIG_FB_EFI results in a black screen in tty with prop. nvidia driver

User Icon bretth provided feedback a year ago
karma
User Icon besser82 commented & provided feedback a year ago
karma

Works great on Lenovo T480! LGTM! =)

User Icon markec provided feedback a year ago
karma
User Icon pjolt commented & provided feedback a year ago
karma

Default and performance pass. HP Prodesk 400 G6 Mini, i5-10400T, CometLake-S GT2 [UHD 630].

User Icon dm0 provided feedback a year ago
karma
karma
User Icon rai510 provided feedback a year ago
karma
User Icon mhayden commented & provided feedback a year ago
karma

No issues found

User Icon mershl commented & provided feedback a year ago
karma

works

User Icon johnh99 commented & provided feedback a year ago
karma

Works OK for daily use and Xonotic CTF. Ryzen 3700x, Rog Strix B550-F board, nvidia from rpmfusion. Am getting this in dmesg: simple-framebuffer.0: swiotlb buffer is full... If I fall back to 6.2.15, that message now showing up but was not earlier. Likely the nividia drivers are broken, probably from flatpak updates. My suspicion, anyway.

User Icon py0xc3 commented & provided feedback a year ago
karma

./runtests.sh PASS with 6.3.3-200.fc38.x86_64 within a kvm/qemu VM (KDE spin, up to date with all testing repos of F38 enabled) on a AMD Ryzen 6000 mobile series host. No third party modules (tainted = 0).

I tested the VM some minutes with average activities, works fine so far. No errors/issues when using it.

2x vulnerability status:
.../spec_store_bypass:Mitigation: Speculative Store Bypass disabled via prctl
.../spectre_v1: Mitigation: usercopy/swapgs barriers and __user pointer sanitization

BZ#2187931 and BZ#2187935 not verified

User Icon nixuser commented & provided feedback a year ago
karma

Seems to be working here, but I am not using special nvidia drivers on this box (using default nouveau).

Dell Precision T5610 2 x Intel(R) Xeon(R) CPU E5-2603 v2 @ 1.80GHz (8 cores total) NVIDIA Corporation GK104 [GeForce GTX 760] (rev a1)

User Icon filiperosset commented & provided feedback a year ago
karma

no regressions noted

User Icon rathann commented & provided feedback a year ago
karma

Seems to work fine and fixes #2191739 for me.

User Icon ibims commented & provided feedback a year ago
karma

Runs for a few days now. Works on baremetal (non UEFI mode) AMD Ryzen5 3600, Mainboard MSI B450M Mortar Max with prop. nvidia driver (530.41.03) from rpmfusion.org (GTX980 card). Works with Gnome-Desktop (Xorg).

User Icon imabug provided feedback a year ago
karma
User Icon maxifed commented & provided feedback a year ago
karma

Works with Ryzen 5 7600X + Radeon RX6600 XT

User Icon wayne6001 commented & provided feedback a year ago
karma

Intel NUC6i5SYK, Intel Core i5-6260U × 4, Mesa Intel Iris Graphics 540 (SKL GT3)

working fine. Passed both default and performance test suites.

User Icon tharadash commented & provided feedback a year ago
karma

Seems to work fine on bare-metal HP Z440, AMD RX570 with UEFI. No issues to report so far and kernel regression tests both PASS.

User Icon gtb provided feedback a year ago
karma
User Icon pampelmuse commented & provided feedback a year ago
karma

The bootsplash is now missing but it works for me.

User Icon benthaase commented & provided feedback a year ago
karma

Still unstable. Multiple daily system lockups for no particular reason when either doing nothing but opening a folder / gnome overview. Can be forcibly be triggered opening this 3D Model in Firefox and spinning it around / moving around in Google Maps / running 3D accelerated applications.

Related bugs:

https://gitlab.freedesktop.org/drm/amd/-/issues/2548#note_1918409 https://gitlab.freedesktop.org/drm/amd/-/issues/2447#note_1918408

System

  • Lenovo P14s AMD Gen1
  • AMD Ryzen 7 PRO 4750U
  • Linux fedora 6.3.3-200.fc38.x86_64
  • Fedora release 38
  • Mozilla Firefox 113.0.1

Crashlog

kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx_high timeout, signaled seq=4201, emitted seq=4203
kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process gnome-shell pid 2771 thread gnome-shel:cs0 pid 2804
kernel: amdgpu 0000:07:00.0: amdgpu: GPU reset begin!
kernel: [drm] Send DSC disable to synaptics
kernel: [drm] psp gfx command UNLOAD_TA(0x2) failed and response status is (0x117)
kernel: amdgpu 0000:07:00.0: amdgpu: MODE2 reset
kernel: amdgpu 0000:07:00.0: amdgpu: GPU reset succeeded, trying to resume
kernel: [drm] PCIE GART of 1024M enabled.
kernel: [drm] PTB located at 0x000000F47FC00000
kernel: [drm] PSP is resuming...
kernel: [drm] reserve 0x400000 from 0xf47f800000 for PSP TMR
kernel: amdgpu 0000:07:00.0: amdgpu: RAS: optional ras ta ucode is not available
kernel: amdgpu 0000:07:00.0: amdgpu: RAP: optional rap ta ucode is not available
kernel: [drm] psp gfx command LOAD_TA(0x1) failed and response status is (0x7)
kernel: [drm] psp gfx command INVOKE_CMD(0x3) failed and response status is (0x4)
kernel: amdgpu 0000:07:00.0: amdgpu: Secure display: Generic Failure.
kernel: amdgpu 0000:07:00.0: amdgpu: SECUREDISPLAY: query securedisplay TA failed. ret 0x0
kernel: amdgpu 0000:07:00.0: amdgpu: SMU is resuming...
kernel: amdgpu 0000:07:00.0: amdgpu: SMU is resumed successfully!
kernel: [drm] DMUB hardware initialized: version=0x01010026
kernel: [drm] Send DSC enable to synaptics
kernel: [drm] Send DSC enable to synaptics
kernel: [drm] kiq ring mec 2 pipe 1 q 0
kernel: amdgpu 0000:07:00.0: [drm:amdgpu_ring_test_helper [amdgpu]] *ERROR* ring kiq_2.1.0 test failed (-110)
kernel: [drm:amdgpu_gfx_enable_kcq [amdgpu]] *ERROR* KCQ enable failed
kernel: [drm:amdgpu_device_ip_resume_phase2 [amdgpu]] *ERROR* resume of IP block <gfx_v9_0> failed -110
kernel: amdgpu 0000:07:00.0: amdgpu: GPU reset(2) failed
kernel: amdgpu 0000:07:00.0: amdgpu: GPU reset end with ret = -110
kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* GPU Recovery Failed: -110
firefox.desktop[4504]: Crash Annotation GraphicsCriticalError: |[0][GFX1-]: GFX: RenderThread detected a device reset in PostUpdate (t=52.2062) [GFX1-]: GFX: RenderThread detected a device reset in PostUpdate
kernel: [drm] Skip scheduling IBs!
kernel: [drm] Skip scheduling IBs!
kernel: amdgpu_cs_ioctl: 46 callbacks suppressed
kernel: [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125!
gnome-shell[2771]: amdgpu: The CS has been rejected (-125), but the context isn't robust.
gnome-shell[2771]: amdgpu: The process will be terminated.
User Icon benthaase commented & provided feedback a year ago
karma

Sorry for duplicate message, negative Karma because unstable. Reasoning above.

User Icon generalprobe commented & provided feedback a year ago
karma

While booting Kernel 6.3.3 I get this error and the whole windowmanager and applications get choppy Mai 21 22:40:50 el-ryzerino kernel: amdgpu 0000:0d:00.0: amdgpu: GPU fault detected: 147 0x0a124802 for process skypeforlinux pid 7723 thread skypeforli:cs0 pid 7741 Mai 21 22:40:50 el-ryzerino kernel: amdgpu 0000:0d:00.0: amdgpu: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x00106D91 Mai 21 22:40:50 el-ryzerino kernel: amdgpu 0000:0d:00.0: amdgpu: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x0F090002 Mai 21 22:40:50 el-ryzerino kernel: amdgpu 0000:0d:00.0: amdgpu: VM fault (0x02, vmid 7, pasid 32776) at page 1076625, write from 'CB5' (0x43423500) (144)

User Icon generalprobe commented & provided feedback a year ago
karma

sorry for wrong karma:

Mai 21 22:40:50 el-ryzerino kernel: amdgpu 0000:0d:00.0: amdgpu: GPU fault detected: 147 0x0a124802 for process skypeforlinux pid 7723 thread skypeforli:cs0 pid 7741
Mai 21 22:40:50 el-ryzerino kernel: amdgpu 0000:0d:00.0: amdgpu:   VM_CONTEXT1_PROTECTION_FAULT_ADDR   0x00106D91
Mai 21 22:40:50 el-ryzerino kernel: amdgpu 0000:0d:00.0: amdgpu:   VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x0F090002
Mai 21 22:40:50 el-ryzerino kernel: amdgpu 0000:0d:00.0: amdgpu: VM fault (0x02, vmid 7, pasid 32776) at page 1076625, write from 'CB5' (0x43423500) (144)
User Icon agurenko commented & provided feedback a year ago
karma

Works well on Ryzen 5900X + 7900 XTX

User Icon runekl commented & provided feedback a year ago
karma

Hi

It seems this kernel corrupts XFS file systems quite frequently. It has happened three times for me on different servers. Repairing the file system didn't make the system boot.

My advice: Stay away from this if you use XFS!

User Icon py0xc3 commented & provided feedback a year ago

@benthaase @generalprobe -> please check if this bug maybe applies to you and provide some complementary data and reports if so: https://bugzilla.redhat.com/show_bug.cgi?id=2193110 (have you had such issues already before? In earlier kernels? What are the circumstances/behaviors?)

@generalprobe Do you have also AMD Ryzen 7 ?

@runekl -> I have several XFS deployed without issues. The changelog of the kernel does not contain changes to xfs except some relations to xfstests, but not sure that this can have such impacts (?). Do you have maybe introduced some other updates along with the kernel? If not, you might file a bug, just to ensure it can be investigated

User Icon jforbes commented & provided feedback a year ago

Honestly, the issue with firefox should be investigated, but it is not my primary concern, the XFS issue is the reason that I haven't pushed this to stable. If you can add anything regarding the XFS issues to https://bugzilla.redhat.com/show_bug.cgi?id=2208553 it would be appreciated. I run almost exclusively XFS with a bit of ext4 here, and I have not seen the issue locally on any machine.

User Icon jforbes commented & provided feedback a year ago

For those reliably hitting the xfs problem, mind giving https://koji.fedoraproject.org/koji/taskinfo?taskID=101466330 a try when it finishes? Should be an hour or so.

User Icon runekl commented & provided feedback a year ago

Hi!

This happened on two HPE DL360gen8 and HPE DL580 gen8. All use hardware raid and Intel CPUs. Two happened after a reboot, one of them was a hard reboot. On DL580 it happened during normal operation and the machine died.

I haven't seen any issues like this before for several years with 100 fedora servers. So it seems something bad happened.

User Icon jforbes commented & provided feedback a year ago

@runeki it could be entirely my fault, there was an XFS CVE, I backported a patch for it, and may have missed a dependency somewhere. Upstream stable hasn't picked it up yet. That is what the kernel I posted above is testing, I reverted that patch. Seems if this were in the upstream kernel, others would have noticed and complained as well.

User Icon runekl commented & provided feedback a year ago

That makes a lot of sense. Since it happened to me on more than half of the servers with this kernel, it's not likely it's out there. I will test again when it's pushed to testing.

User Icon petersen commented & provided feedback a year ago

I just want to point out that kernel-6.3+ affects ghc-9.2 badly causing frequent mmap segfaults.

See https://bugzilla.redhat.com/show_bug.cgi?id=2209162 (bug 2209162) and further for more details (I understand this is already fixed in ghc-9.4, but currently the default ghc in F38 is 9.2.)

(I am not going to set minus karma since I am also a Proven Tester.)

User Icon jforbes commented & provided feedback a year ago

@runekl I was hoping to not push this to testing until I can get confirmation that it seems to be the cause of the issue. It is a scratch build at the moment.

User Icon ibims commented & provided feedback a year ago

@jforbes is it a bad or non-good idea to push 6.2.16 as a last „good“ release?

User Icon runekl commented & provided feedback a year ago

@jforbes I have put the scratch build on four servers just now. Will let you know how they behave.

User Icon runekl commented & provided feedback a year ago

@jforbes The issue seems to still be there. I got data corruption soon after reboot and service start on two of three servers. This post refers to xfs changes in 6.3: https://www.spinics.net/lists/linux-xfs/msg71098.html.

User Icon jforbes commented & provided feedback a year ago

Thanks for letting me know. I was hoping it was my backport of the CVE fix, just because it would mean I could probably track it down easily. I am guessing this is limited to certain XFS filesystems as I run mostly XFS here, and have not seen it. Perhaps some defaults that xfsprogs used at a specific time, or filesystems created with certain kernels... We can try to track it down in bz 2208553. I will not push this rebase to stable.

User Icon runekl commented & provided feedback a year ago

@jforbes I should mention that the corrupted file systems were created with Fedora31, while ths server surviving was created with Fedora36.

User Icon johnh99 commented & provided feedback a year ago

@jforbes For what it is worth, my 3 depmod warnings when using dracut have vanished with your scratch kernel that I had a hunch to try although I am not using XFS.

User Icon jforbes commented & provided feedback a year ago

@runekl and anyone else hitting the xfs issue, please take a look at https://bugzilla.redhat.com/show_bug.cgi?id=2208553

User Icon runekl commented & provided feedback a year ago

@jforbes The crash is easily reproducible. We just needed to start the server, we didn't even have to start any services to make it happen. We are working on providing information based on the guidelines from the XFS maintainer. Hope it's ready in a couple of hours.

User Icon js314592 commented & provided feedback a year ago

@ibims 6.2.16 should be better than 6.2.15

User Icon markec commented & provided feedback a year ago

We have 6.3.4 as well now, not sure if it's worth giving that a go or has any relevant changes in.

User Icon robatino commented & provided feedback a year ago

6.3.4 for F37 and F38 are building now, I can't tell from the Changelog whether any XFS changes are included.

User Icon nadrolinux commented & provided feedback a year ago
karma

Works fine. Finally I can use amd_pstate=active with a kernel from default repo.

User Icon runekl commented & provided feedback a year ago

The XFS issue is still present in kernel 6.3.4. But it seems to be gone in the 6.4 series.

User Icon kparal commented & provided feedback a year ago
karma

works fine on my Thinkpad P1 gen3

User Icon robatino commented & provided feedback a year ago

Hopefully fixed version of 6.3.4 building now in koji.

User Icon markec commented & provided feedback a year ago

Cool, seems it's build

jforbes edited this update.

New build(s):

  • kernel-6.3.4-201.fc38

Removed build(s):

  • kernel-6.3.3-200.fc38

Karma has been reset.

a year ago

This update has been submitted for testing by jforbes.

a year ago

This update's test gating status has been changed to 'waiting'.

a year ago
User Icon gtb provided feedback a year ago
karma
User Icon rai510 provided feedback a year ago
karma
BZ#2208553 xfs metadata corruption after upgrade to 6.3.3 kernel
User Icon imabug provided feedback a year ago
karma

This update's test gating status has been changed to 'passed'.

a year ago
User Icon bojan commented & provided feedback a year ago
karma

Boots here on a couple of machines (no xfs).

User Icon nixuser commented & provided feedback a year ago
karma

Working fine, but I'm not using xfs.

Intel NUC i7 NUC11PAH 1 x 11th Gen Intel(R) Core(TM) i7-1165G7 @ 2.80GHz Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] (rev 01)

User Icon pjolt commented & provided feedback a year ago
karma

Default and performance pass. HP Prodesk 400 G6 Mini, i5-10400T, CometLake-S GT2 [UHD 630]

User Icon runekl commented & provided feedback a year ago
karma

Doesn't corrupt my XFS files systems the way 6.3.3 did.

User Icon py0xc3 commented & provided feedback a year ago
karma

./runtests.sh PASS with kernel-6.3.4-201.fc38.x86_64, kernel-headers-6.3.3-200.fc38.x86_64, kernel-tools-6.3.3-200.fc38.x86_64 builds within a KVM/QEMU VM (KDE spin, up to date) running on a AMD Ryzen 6850 PRO host. No third party modules (tainted = 0).

I tested the VM some minutes with average activities, works fine so far. No errors/issues when using it.

I have NOT yet tested if it works on my host (with "work" I mean if it can solve BZ#2193110; the freeze can appear on the host when any VM is running but has not yet occurred within VMs, including with cpu host-passthrough).

I will now test on the host and report in BZ#2193110 if 6.3.4 creates any changes in the behavior.

I have xfs file systems but they have not been affected by the 6.3.3 issue.

User Icon py0xc3 commented & provided feedback a year ago
karma

BZ#2193110 persists with 6.3.4 (tested natively on AMD Ryzen 6850 PRO host). I experienced it already twice.

Major log entries from the first freeze:

May 28 13:20:25 fedora.domain kernel: RIP: 0010:__kmem_cache_alloc_node+0x1ba/0x320
May 28 13:20:25 fedora.domain kernel: Hardware name: LENOVO 21CHCTO1WW/21CHCTO1WW, BIOS R23ET60W (1.30 ) 09/14/2022
May 28 13:20:25 fedora.domain kernel: CPU: 8 PID: 5056 Comm: kwin_wayla:cs0 Not tainted 6.3.4-201.fc38.x86_64 #1
May 28 13:20:25 fedora.domain kernel: general protection fault, probably for non-canonical address 0x49f8d7efd771dae6: 0000 [#1] PREEMPT SMP NOPTI

-> the desktop clock has frozen at 13:20:24

Full logs at https://bugzilla.redhat.com/show_bug.cgi?id=2193110

My host XFS file systems work fine (but I didn't experience the XFS issue on 6.3.3 as well).

User Icon py0xc3 commented & provided feedback a year ago

With regards to my previous comment, I had to return to 6.2.15 because 6.3.4 creates too many kernel errors/freezes so that the system is not usable with this kernel.

However, it causes a new phenomenon: Firefox *¹ freezes and crashes, it cannot be re-started, and pidof firefox does no longer work then (it just idles without any return until I do CTRL+C). However, the system does not freeze, although the kernel errors are logged in the same way, but it seems to not "spread" from one core/thread to others.

Again, there are massive amounts of kernel errors logged (see BZ#2193110 for the full logs). But some more indicative are maybe:

May 28 14:38:41 fedora.domain kernel: WARNING: CPU: 4 PID: 5523 at drivers/gpu/drm/ttm/ttm_bo.c:326 ttm_bo_release+0x289/0x2e0 [ttm]

...

May 28 14:38:41 fedora.domain kernel: WARNING: CPU: 4 PID: 5523 at drivers/gpu/drm/ttm/ttm_bo.c:327 ttm_bo_release+0x296/0x2e0 [ttm]

...

May 28 14:38:41 fedora.domain kernel: kernel BUG at drivers/gpu/drm/ttm/ttm_bo.c:193!

However, once I tried to shutdown, it became obvious that the running system was already in a corrupted state, and the shutdown culminated in ...

May 28 14:51:09 fedora.domain kernel: #PF: error_code(0x0000) - not-present page
May 28 14:51:09 fedora.domain kernel: #PF: supervisor read access in kernel mode
May 28 14:51:09 fedora.domain kernel: BUG: unable to handle page fault for address: 0000003000300010

*¹ I had freezes also without Firefox running, so it is not Firefox-specific; see BZ#2193110

User Icon dm0 provided feedback a year ago
karma

This update has been pushed to testing.

a year ago

This update can be pushed to stable now if the maintainer wishes

a year ago
User Icon bretth provided feedback a year ago
karma

petersen edited this update.

a year ago
User Icon pampelmuse commented & provided feedback a year ago
karma

The bootsplash is still missing but it works for me.

User Icon markec provided feedback a year ago
karma
User Icon ibims commented & provided feedback a year ago
karma

Works on baremetal (non UEFI mode) AMD Ryzen5 3600, Mainboard MSI B450M Mortar Max with prop. nvidia driver (530.41.03) from rpmfusion.org (GTX980 card). Works with Gnome-Desktop (Xorg). But no XFS in use here.

User Icon pbrobinson commented & provided feedback a year ago
karma

Seems fine on a bunch of arm devices.

User Icon maxifed commented & provided feedback a year ago
karma

Works, perf and normal tests pass (BTRFS, no XFS system tested). Could not reproduce ghci bug, even on ghci-9.2.6

BZ#2209162 ghci-9.2.6 segfaults with "mmap 4096 bytes at (nil): Cannot allocate memory"
User Icon boris2023 commented & provided feedback a year ago
karma

Tested with CPU Ryzen 7 3700 on F38 Server

[boris@ServerFedora38 ~]$ hostnamectl Static hostname: ServerFedora38 Icon name: computer-desktop Chassis: desktop 🖥️ Machine ID: b1655271bd574ee3a113398c69010646 Boot ID: 2e6ad1741cf744f88ab669ab731d8c8b Operating System: Fedora Linux 38 (Server Edition)
CPE OS Name: cpe:/o:fedoraproject:fedora:38 OS Support End: Tue 2024-05-14 OS Support Remaining: 11month 2w 1d Kernel: Linux 6.3.4-201.fc38.x86_64 Architecture: x86-64 Hardware Vendor: Micro-Star International Co., Ltd. Hardware Model: MS-7C37 Firmware Version: H.60 Firmware Date: Wed 2019-11-06 [boris@ServerFedora38 ~]$ df -Th Filesystem Type Size Used Avail Use% Mounted on devtmpfs devtmpfs 4.0M 0 4.0M 0% /dev tmpfs tmpfs 7.8G 0 7.8G 0% /dev/shm tmpfs tmpfs 3.2G 2.0M 3.2G 1% /run /dev/mapper/fedora-root xfs 464G 28G 437G 6% / /dev/loop0 squashfs 128K 128K 0 100% /var/lib/snapd/snap/bare/5 /dev/loop2 squashfs 92M 92M 0 100% /var/lib/snapd/snap/gtk-common-themes/1535 /dev/loop6 squashfs 141M 141M 0 100% /var/lib/snapd/snap/skype/277 /dev/loop4 squashfs 56M 56M 0 100% /var/lib/snapd/snap/core18/2745 /dev/loop5 squashfs 54M 54M 0 100% /var/lib/snapd/snap/snapd/19122 /dev/loop3 squashfs 141M 141M 0 100% /var/lib/snapd/snap/skype/274 /dev/loop1 squashfs 165M 165M 0 100% /var/lib/snapd/snap/gnome-3-28-1804/198 tmpfs tmpfs 7.8G 16K 7.8G 1% /tmp /dev/sda2 xfs 960M 394M 567M 41% /boot /dev/sda1 vfat 599M 7.1M 592M 2% /boot/efi tmpfs tmpfs 1.6G 124K 1.6G 1% /run/user/1000

[boris@ServerFedora38 ~]$ journalctl | grep xfs Mar 26 17:37:21 ServerFedora38 systemd-fsck[654]: /usr/sbin/fsck.xfs: XFS file system. Mar 26 17:38:30 ServerFedora38 systemd-fsck[663]: /usr/sbin/fsck.xfs: XFS file system. Mar 26 17:45:08 ServerFedora38 root[2662]: 05efi: debug: /dev/sda2 is xfs partition: exiting Mar 26 17:45:10 ServerFedora38 root[3425]: 40grub2: debug: parsing: insmod xfs Mar 26 17:45:10 ServerFedora38 root[3425]: 40grub2: debug: parsing: insmod xfs Mar 26 17:45:45 ServerFedora38 dracut[4454]: drwxr-xr-x 2 root root 0 Mar 14 03:00 usr/lib/modules/6.2.8-300.fc38.x86_64/kernel/fs/xfs Mar 26 17:45:45 ServerFedora38 dracut[4454]: -rw-r--r-- 1 root root 720148 Mar 14 03:00 usr/lib/modules/6.2.8-300.fc38.x86_64/kernel/fs/xfs/xfs.ko.xz Mar 26 17:45:45 ServerFedora38 dracut[4454]: -rwxr-xr-x 1 root root 2598 Feb 8 03:00 usr/sbin/fsck.xfs Mar 26 17:45:45 ServerFedora38 dracut[4454]: -rwxr-xr-x 1 root root 715368 Feb 8 03:00 usr/sbin/xfs_db Mar 26 17:45:45 ServerFedora38 dracut[4454]: -rwxr-xr-x 1 root root 786 Feb 8 03:00 usr/sbin/xfs_metadump Mar 26 17:45:45 ServerFedora38 dracut[4454]: -rwxr-xr-x 1 root root 701648 Feb 8 03:00 usr/sbin/xfs_repair Mar 26 17:47:24 ServerFedora38 root[15044]: 05efi: debug: /dev/sda2 is xfs partition: exiting Mar 26 17:47:26 ServerFedora38 root[15804]: 40grub2: debug: parsing: insmod xfs Mar 26 17:47:26 ServerFedora38 root[15804]: 40grub2: debug: parsing: insmod xfs Mar 26 17:50:42 ServerFedora38 systemd-fsck[657]: /usr/sbin/fsck.xfs: XFS file system. Mar 26 18:14:53 ServerFedora38 systemd-fsck[663]: /usr/sbin/fsck.xfs: XFS file system. Apr 08 18:18:33 ServerFedora38 systemd-fsck[664]: /usr/sbin/fsck.xfs: XFS file system. Apr 08 18:39:37 ServerFedora38 root[6806]: 05efi: debug: /dev/sda2 is xfs partition: exiting Apr 08 18:39:39 ServerFedora38 root[7565]: 40grub2: debug: parsing: insmod xfs Apr 08 18:39:39 ServerFedora38 root[7565]: 40grub2: debug: parsing: insmod xfs Apr 08 18:39:39 ServerFedora38 root[7565]: 40grub2: debug: parsing: insmod xfs Apr 08 18:40:17 ServerFedora38 dracut[8610]: drwxr-xr-x 2 root root 0 Mar 14 03:00 usr/lib/modules/6.2.10-300.fc38.x86_64/kernel/fs/xfs Apr 08 18:40:17 ServerFedora38 dracut[8610]: -rw-r--r-- 1 root root 723396 Mar 14 03:00 usr/lib/modules/6.2.10-300.fc38.x86_64/kernel/fs/xfs/xfs.ko.xz Apr 08 18:40:18 ServerFedora38 dracut[8610]: -rwxr-xr-x 1 root root 2598 Feb 8 03:00 usr/sbin/fsck.xfs Apr 08 18:40:18 ServerFedora38 dracut[8610]: -rwxr-xr-x 1 root root 715368 Feb 8 03:00 usr/sbin/xfs_db Apr 08 18:40:18 ServerFedora38 dracut[8610]: -rwxr-xr-x 1 root root 786 Feb 8 03:00 usr/sbin/xfs_metadump Apr 08 18:40:18 ServerFedora38 dracut[8610]: -rwxr-xr-x 1 root root 701648 Feb 8 03:00 usr/sbin/xfs_repair Apr 08 18:42:41 ServerFedora38 root[20386]: 05efi: debug: /dev/sda2 is xfs partition: exiting Apr 08 18:42:42 ServerFedora38 root[21146]: 40grub2: debug: parsing: insmod xfs Apr 08 18:42:42 ServerFedora38 root[21146]: 40grub2: debug: parsing: insmod xfs Apr 08 18:42:42 ServerFedora38 root[21146]: 40grub2: debug: parsing: insmod xfs Apr 08 18:47:14 ServerFedora38 systemd-fsck[662]: /usr/sbin/fsck.xfs: XFS file system. May 09 18:29:03 ServerFedora38 systemd-fsck[665]: /usr/sbin/fsck.xfs: XFS file system. May 09 18:41:30 ServerFedora38 root[7285]: 05efi: debug: /dev/sda2 is xfs partition: exiting May 09 18:41:31 ServerFedora38 root[8044]: 40grub2: debug: parsing: insmod xfs May 09 18:41:31 ServerFedora38 root[8044]: 40grub2: debug: parsing: insmod xfs May 09 18:41:31 ServerFedora38 root[8044]: 40grub2: debug: parsing: insmod xfs May 09 18:41:31 ServerFedora38 root[8044]: 40grub2: debug: parsing: insmod xfs May 09 18:42:06 ServerFedora38 dracut[9104]: drwxr-xr-x 2 root root 0 Apr 27 03:00 usr/lib/modules/6.2.14-300.fc38.x86_64/kernel/fs/xfs May 09 18:42:06 ServerFedora38 dracut[9104]: -rw-r--r-- 1 root root 719884 Apr 27 03:00 usr/lib/modules/6.2.14-300.fc38.x86_64/kernel/fs/xfs/xfs.ko.xz . . . . . [boris@ServerFedora38 ~]$ dmesg| grep "XFS" [ 5.222382] SGI XFS with ACLs, security attributes, realtime, scrub, quota, no debug enabled [ 5.224106] XFS (dm-0): Mounting V5 Filesystem 70c56ddb-b881-4296-a73b-0e385cbe364e [ 5.383157] XFS (dm-0): Ending clean mount [ 16.201900] XFS (sda2): Mounting V5 Filesystem bed3367d-4aa0-4afc-99d0-50edc440fbbe [ 18.136884] XFS (sda2): Ending clean mount

BZ#2208553 xfs metadata corruption after upgrade to 6.3.3 kernel
User Icon norbertj commented & provided feedback a year ago
karma

Works with my 3 x86_64 machines (ext4 only). Default and Performance regression tests passed.

User Icon boris2023 commented & provided feedback a year ago

I apologize for posting hardly readable testing results, but preview option didn't work for me. Possibly it happened due to bunch of rows in post.

User Icon mrunge commented & provided feedback a year ago
karma

works for me, no issues noted

User Icon tharadash commented & provided feedback a year ago
karma

6.3.4 seems to work fine on bare-metal HP EliteBook 840 G6 with UEFI and SecureBoot. No issues to report so far and kernel regression tests both PASS.

User Icon frantisekz provided feedback a year ago
karma

This update has been submitted for stable by jforbes.

a year ago
User Icon wayne6001 commented & provided feedback a year ago
karma

Intel NUC6i5SYK, Intel Core i5-6260U × 4, Mesa Intel Iris Graphics 540 (SKL GT3)

Passed both default and performance test suites.

This update's test gating status has been changed to 'failed'.

a year ago

FEDORA-2023-514965dd8a ejected from the push because 'Required tests did not pass on this update'

a year ago

This update's test gating status has been changed to 'passed'.

a year ago
User Icon robatino provided feedback a year ago
karma
User Icon robatino commented & provided feedback a year ago

If 6.3.5 gets into testing, what happens to 6.3.4, now that it's not going to stable? Is it kicked out of the repo?

User Icon markec commented & provided feedback a year ago
karma

Seems like testing failed and might need a manual push.

This update has been submitted for stable by kevin.

a year ago

This update has been pushed to stable.

a year ago
User Icon adonnen commented & provided feedback a year ago
karma

This kernel will not boot. After updating today, I selected the new kernel in Grub, and it stuck at "Loading Linux 6.3.4-201.fc38.x86_64" for over 30 minutes, necessitating a hard restart. It never reached the ramdisk. I used grub to rollback to the previous update, and it worked fine. I will try to update again after a backup, but I am worried this might brick someone if they don't have backups. I am running a Framework Laptop (intel 12th-gen i5), and I am dual-booted with Windows 11.

User Icon py0xc3 commented & provided feedback a year ago

Something comparable to what @adonnen posted was also posted by another user on Ask.Fedora:
https://discussion.fedoraproject.org/t/fedora-hangs-on-boot-after-upgrading-to-kernel-6-3-4/83605

User Icon nixuser commented & provided feedback a year ago

It may be worth mentioning that it appears kernel-6.3.x brings IBT Protection to Fedora, in that it is now turned on by default. For me this killed VirtualBox as a host, but I think some custom drivers can cause problems also. For me the symptom was complete freeze when I tried to launch a VM. Solution was to add "ibt=off" to the kernel boot line. This impacts Intel 11th gen (Tigerlake) and later CPUs I believe. If you guys experiencing boot hangs are running special drivers, may be worth giving "ibt=off" a try.

User Icon adonnen provided feedback a year ago
karma
User Icon boris2023 commented & provided feedback a year ago

Please, check with https://forums.virtualbox.org/viewtopic.php?t=108948 . Quoting mentioned thread "This has been the default config as of kernel 6.2.x."

User Icon nixuser commented & provided feedback a year ago

@boris2023 that is referring to vanilla kernels from kernel.org. IBT wasn't on in Fedora during 6.2.

User Icon mbrode commented & provided feedback a year ago
karma

getting error "CIFS: VFS: cifs_mount failed w/return code = -5" since the last two kernel updates. older kernels still work with this v1 share...


Please login to add feedback.

Metadata
Type
enhancement
Karma
18
Signed
Content Type
RPM
Test Gating
Settings
Unstable by Karma
-3
Stable by Karma
disabled
Stable by Time
disabled
Dates
submitted
a year ago
in testing
a year ago
in stable
a year ago
modified
a year ago
approved
a year ago
BZ#2187931 CVE-2023-2176 Kernel: Slab-out-of-bound read in compare_netdev_and_ip
0
0
BZ#2187935 CVE-2023-2176 kernel: Slab-out-of-bound read in compare_netdev_and_ip [fedora-all]
0
0
BZ#2208553 xfs metadata corruption after upgrade to 6.3.3 kernel
0
1
BZ#2209162 ghci-9.2.6 segfaults with "mmap 4096 bytes at (nil): Cannot allocate memory"
0
1

Automated Test Results

Test Cases

0 9 Test Case kernel regression