Mageia forum

share the magic
http://forums.mageia.org/en/

SOLVED block updates due to problems with kernel 6.6.28

http://forums.mageia.org/en/viewtopic.php?f=7&t=15343

Page 1 of 1

SOLVED block updates due to problems with kernel 6.6.28

PostPosted: Apr 26th, '24, 19:04
by ricard13
Hello everyone. Sorry if the Google translation is not what you wanted. Well, I have a problem with the installation of the kernel and cpupower. I get errors when starting atom in different programs or if I manage to go to the home screen it stays blocked after entering the password. I've tried a little of everything, including a fresh installation with a new user.
My question is how can I block the installation of kernel 2.2.28 in updates?

Re: How to block some updates due to problems with kernel 2.

PostPosted: Apr 26th, '24, 23:33
by benmc
can you post the output of
Code: Select all
uname -a


TIA

Re: How to block some updates due to problems with kernel 2.

PostPosted: Apr 27th, '24, 14:52
by ricard13
Code: Select all
[root@]# uname -a
Linux pc.trix 6.6.22-desktop-1.mga9 #1 SMP PREEMPT_DYNAMIC Sun Mar 17 18:04:51 UTC 2024 x86_64 GNU/Linux


This is the maximum version that I can install without errors.

Code: Select all
[root@]# dmidecode -t 2
# dmidecode 3.5
Getting SMBIOS data from sysfs.
SMBIOS 3.3.0 present.

Handle 0x0002, DMI type 2, 15 bytes
Base Board Information
        Manufacturer: ASUSTeK COMPUTER INC.
        Product Name: PRIME Z590M-PLUS
        Version: Rev 1.xx
        Serial Number: 210xxxxxxxxx
        Asset Tag: Default string
        Features:
                Board is a hosting board
                Board is replaceable
        Location In Chassis: Default string
        Chassis Handle: 0x0003
        Type: Motherboard
        Contained Object Handles: 0

Re: How to block some updates due to problems with kernel 2.

PostPosted: Apr 27th, '24, 18:21
by morgano
Could you try kernel-linus-6.6.28-1.mga9 ?
It is less patched by us than desktop and server flavours.

More info, please post output of
Code: Select all
inxi -SMCG
rpm -qa | grep kernel


Have you looked in system journal if you see interesting messages?
i.e you can enter
Code: Select all
journalctl -b-1
to see see the log from previous boot.

Re: How to block some updates due to problems with kernel 2.

PostPosted: Apr 27th, '24, 19:44
by ricard13
Code: Select all
[root@]# inxi -SMCG
System:
  Host: my.host Kernel: 6.6.22-desktop-1.mga9 arch: x86_64
    bits: 64 Desktop: MWM Distro: Mageia 9
Machine:
  Type: Desktop System: ASUS product: N/A v: N/A serial: N/A
  Mobo: ASUSTeK model: PRIME Z590M-PLUS v: Rev 1.xx serial: 210xxxxxxxxxxxx
    UEFI: American Megatrends v: 1601 date: 05/07/2022
CPU:
  Info: 8-core model: Intel Core i7-10700K bits: 64 type: MT MCP cache:
    L2: 2 MiB
  Speed (MHz): avg: 800 min/max: 800/5100 cores: 1: 800 2: 800 3: 800 4: 800
    5: 800 6: 800 7: 800 8: 800 9: 800 10: 800 11: 800 12: 800 13: 800 14: 800
    15: 800 16: 800
Graphics:
  Device-1: NVIDIA GM206 [GeForce GTX 960] driver: nouveau v: kernel
  Display: x11 server: X.org v: 1.21.1.8 with: Xwayland v: 22.1.9 driver: X:
    loaded: nouveau,v4l gpu: nouveau resolution: 1920x1080~60Hz
  API: OpenGL v: 4.5 Mesa 24.0.5 renderer: llvmpipe (LLVM 15.0.6 256 bits)


Code: Select all
[root@l]# rpm -qa | grep kernel
remove-old-kernels-0.99.21.7-1.mga9
kernel-desktop-6.4.9-4.mga9
kernel-desktop-devel-6.4.9-4.mga9
kernel-firmware-nonfree-20231111-1.mga9.nonfree
kernel-firmware-20231111-1.mga9
kernel-desktop-6.6.22-1.mga9
kernel-desktop-devel-6.6.22-1.mga9
kernel-desktop-6.6.28-1.mga9
kernel-desktop-latest-6.6.28-1.mga9
kernel-userspace-headers-6.6.28-1.mga9
kernel-desktop-devel-6.6.28-1.mga9

Re: How to block some updates due to problems with kernel 2.

PostPosted: Apr 27th, '24, 20:05
by ricard13
the result of the command is

Re: How to block some updates due to problems with kernel 2.

PostPosted: Apr 27th, '24, 21:42
by doktor5000
Maybe it would help if you would explain again what your actual issues are, the translation of the description is pretty vague.

ricard13 wrote:Well, I have a problem with the installation of the kernel and cpupower. I get errors when starting atom in different programs or if I manage to go to the home screen it stays blocked after entering the password.

What particular problem do you have with the installation of the kernel and cpupower?
What does "errors when starting atom in different programs" mean ?
Also, what home screen do you mean, the login manager before logging into your desktop environment ?

Re: How to block some updates due to problems with kernel 2.

PostPosted: Apr 27th, '24, 22:44
by morgano
In the provided "error.txt", journal of problematic run, there is at end
Code: Select all
abr 27 19:48:38 localhost kernel: watchdog: BUG: soft lockup - CPU#1 stuck for 26s! [kworker/1:2:752]
- and before it a call trace.
A screen of lines above that libvirtd reports internal error.

Re: How to block some updates due to problems with kernel 2.

PostPosted: Apr 27th, '24, 23:23
by ricard13
ok, I was just going to block the 2.2.28 kernel update. But I will explain the errors.
a) when I updated to kernel 2.2.28, during the reboot there were errors loading programs during startup. One of many, for example, was the network-up giving this error more or less "BUG: scheduling while atomic: kworker/1:2" having to shut down using the shutdown button

b) it logged in with the previous kernel and disabled the network-up loading and so on with various programs such as virtualbox, smart, etc.

c) I finally got to the main KDE login screen, I typed user and password and when I hit enter the system blocked, I was left with the login screen and I couldn't go to other tty (ctl-alt f12, etc.)

Re: How to block some updates due to problems with kernel 2.

PostPosted: Apr 27th, '24, 23:35
by ricard13
It crashes after entering the username and password to enter kde and I see no other errors

Another piece of information I will give you is that I have done an installation from scratch. With kde and gnome, with nouvo and nvidia drivers.

Re: How to block some updates due to problems with kernel 2.

PostPosted: Apr 28th, '24, 02:02
by Germ
I have a question...

Where are you coming up with "2.2.28 kernel update" ? There is no kernel 2.2.28 in mageia 9. The 2.2 kernel was released 25 years ago.

Re: How to block some updates due to problems with kernel 2.

PostPosted: Apr 28th, '24, 03:17
by doktor5000
He means 6.6.28, which is the more recent kernel that is installed.

Re: How to block some updates due to problems with kernel 2.

PostPosted: Apr 28th, '24, 12:25
by ricard13
sorry, it's 6.6.28, as you can read in the uname -a reports

Re: How to block updates due to problems with kernel 6.6.28

PostPosted: Apr 28th, '24, 17:05
by doktor5000
After the last message in your journalctl log, how long did you wait to let the login into the graphical desktop complete?

Also, does it boot normally if you unplug the network cable? Your intel e1000e network adapter seems to be the issue.
Might be slightly overloaded with all the stuff you start during boot (drbd, mysqld, libvirtd, ...)

Also the output of
Code: Select all
lspcidrake -v
might be helpful as the inxi output does not contain network devices

Re: How to block updates due to problems with kernel 6.6.28

PostPosted: Apr 28th, '24, 19:31
by ricard13
Regarding the start after inserting the username and password. I left it for a couple of hours and when I created an installation from scratch I left it overnight (9 hours). Regarding network overload and leaving the network without, I have not tried it but in a couple of minutes I will try it and comment.

Code: Select all
lspcidrake -v
i2c_i801        : Intel Corporation|Tiger Lake-H SMBus Controller [SERIAL_SMBUS] (vendor:8086 device:43a3 subv:1043 subd:8694) (rev: 11)
xhci_pci        : Intel Corporation|Tiger Lake-H USB 3.2 Gen 2x1 xHCI Host Controller [SERIAL_USB] (vendor:8086 device:43ed subv:1043 subd:8694) (rev: 11)
Card:NVIDIA GeForce 745 series and later: NVIDIA Corporation|GM206 [GeForce GTX 960] [DISPLAY_VGA] (vendor:10de device:1401 subv:1458 subd:36ac) (rev: a1)
unknown         : Intel Corporation|Tiger Lake-H PCI Express Root Port #5 [BRIDGE_PCI] (vendor:8086 device:43bc subv:0040 subd:0000) (rev: 11)
e1000e          : Intel Corporation|Ethernet Connection (14) I219-V [NETWORK_ETHERNET] (vendor:8086 device:15fa subv:1043 subd:8672) (rev: 11)
unknown         : Intel Corporation|Tiger Lake-H Shared SRAM [MEMORY_RAM] (vendor:8086 device:43ef subv:1043 subd:8694) (rev: 11)
unknown         : Intel Corporation|Tiger Lake-H PCI Express Root Port #9 [BRIDGE_PCI] (vendor:8086 device:43b0 subv:0040 subd:0000) (rev: 11)
intel_lpss_pci  : Intel Corporation|Tiger Lake-H Serial IO I2C Controller #0 (vendor:8086 device:43e8 subv:1043 subd:8694) (rev: 11)
unknown         : Intel Corporation|10th Gen Core Processor Host Bridge/DRAM Registers [BRIDGE_HOST] (vendor:8086 device:9b43 subv:1043 subd:8694) (rev: 05)
snd_hda_intel   : Intel Corporation|Device f0c8 [MULTIMEDIA_AUDIO_DEV] (vendor:8086 device:f0c8 subv:1043 subd:87fb) (rev: 11)
spi_intel_pci   : Intel Corporation|Tiger Lake-H SPI Controller (vendor:8086 device:43a4 subv:1043 subd:8694) (rev: 11)
unknown         : Intel Corporation|Tiger Lake-H PCIe Root Port #17 [BRIDGE_PCI] (vendor:8086 device:43c0) (rev: 11)
mei_me          : Intel Corporation|Tiger Lake-H Management Engine Interface [COMMUNICATION_OTHER] (vendor:8086 device:43e0 subv:1043 subd:8694) (rev: 11)
snd_hda_intel   : NVIDIA Corporation|GM206 High Definition Audio Controller [MULTIMEDIA_AUDIO_DEV] (vendor:10de device:0fba subv:1458 subd:36ac) (rev: a1)
unknown         : Kingston Technology Company, Inc.|KC2000/KC2500 NVMe SSD (vendor:2646 device:2262) (rev: 03)
unknown         : Intel Corporation|Device 43c4 [BRIDGE_PCI] (vendor:8086 device:43c4) (rev: 11)
unknown         : Intel Corporation|Z590 LPC/eSPI Controller [BRIDGE_ISA] (vendor:8086 device:4385 subv:1043 subd:8694) (rev: 11)
intel_lpss_pci  : Intel Corporation|Tiger Lake-H Serial IO I2C Controller #1 (vendor:8086 device:43e9 subv:1043 subd:8694) (rev: 11)
unknown         : Intel Corporation|Tiger Lake-H PCIe Root Port #1 [BRIDGE_PCI] (vendor:8086 device:43b8) (rev: 11)
unknown         : Intel Corporation|Device 43d2 [STORAGE_SATA] (vendor:8086 device:43d2 subv:1043 subd:8694) (rev: 11)
hub             : Linux 6.6.22-desktop-1.mga9 xhci-hcd|xHCI Host Controller [Hub|Unused|Full speed (or root) hub] (vendor:1d6b device:0002)
hub             : Genesys Logic, Inc.|USB2.0 Hub [Hub|Unused|Full speed (or root) hub] (vendor:05e3 device:0608)
usbhid          : Corsair Memory, Inc.|Integrated USB Bridge [Human Interface Device|No Subclass|None] (vendor:1b1c device:0c04)
usbhid          : Holtek|USB Gaming Mouse [Human Interface Device|Boot Interface Subclass|Keyboard] (vendor:04d9 device:a067)
usbhid          : Dell|Dell USB Entry Keyboard [Human Interface Device|Boot Interface Subclass|Keyboard] (vendor:413c device:2107)
hub             : VIA Labs, Inc.|USB2.0 Hub [Hub|Unused|Full speed (or root) hub] (vendor:2109 device:2813)
usb_storage     : Generic |MultiCard Device [Mass Storage|SCSI|Bulk-Only] (vendor:048d device:1366)
btusb           : Bluetooth v2.0|Bluetooth V2.0 Dongle [Wireless|Radio Frequency|Bluetooth] (vendor:0a12 device:0001)
usbhid          : AsusTek Computer Inc.|AURA LED Controller [Human Interface Device|No Subclass|None] (vendor:0b05 device:19af)
hub             : Linux 6.6.22-desktop-1.mga9 xhci-hcd|xHCI Host Controller [Hub|Unused|Full speed (or root) hub] (vendor:1d6b device:0003)
hub             : VIA Labs, Inc.|USB3.0 Hub [Hub|Unused|Full speed (or root) hub] (vendor:2109 device:0813)
hid_holtek_mouse: Holtek USB Gaming Mouse
hid_holtek_mouse: Holtek USB Gaming Mouse
hid_holtek_mouse: Holtek USB Gaming Mouse

Re: How to block updates due to problems with kernel 6.6.28

PostPosted: Apr 28th, '24, 21:16
by ricard13
Well, I have disconnected the network cable and the following has happened:

a) I turn off the computer
b) I unplug the mains cable and turn it on.
c) I can access my desktop without problems.
d) I connect network cable,
e) the device stays locked and I turn it off with the button.
f) I repeat the process from a to c
g) I delete networks from drakconf and repeat process a to c.
h) I connect the network and it blocks and appears in my open console.
Code: Select all
Message from syslogd@pcricardo at Apr 28 20:31:58 ...
     kernel:[ 356.155811] watchdog: BUG: soft lockup - CPU#11 stuck for 52s! [kworker/11:2:1005]

i) I repeat step a to c and enter tty12

j) I connect the cable and the following text appears


Code: Select all
br 28 20:49:35 pcricardo.grupmatrix kernel: e1000e 0000:00:1f.6 eno1: NIC Link is Up 10 Mbps Half Duplex, Flow Control: Rx/Tx
abr 28 20:49:35 pcricardo.grupmatrix kernel: BUG: scheduling while atomic: kworker/3:1/169/0x00000002
abr 28 20:49:35 pcricardo.grupmatrix kernel: Modules linked in: rfcomm ip6t_REJECT nf_reject_ipv6 xt_comment ip6table_raw xt_recent xt_MASQUERADE ipt_IFWLOG ipt_psd xt_set >
abr 28 20:49:35 pcricardo.grupmatrix kernel:  btbcm btmtk bluetooth uas usb_storage hid_holtek_mouse input_leds ecdh_generic ecc nvidia(PO) snd_hda_codec_realtek snd_hda_co>
abr 28 20:49:35 pcricardo.grupmatrix kernel:  xhci_pci_renesas video wmi
abr 28 20:49:35 pcricardo.grupmatrix kernel: CPU: 3 PID: 169 Comm: kworker/3:1 Tainted: P           O       6.6.28-desktop-1.mga9 #1
abr 28 20:49:35 pcricardo.grupmatrix kernel: Hardware name: ASUS System Product Name/PRIME Z590M-PLUS, BIOS 1601 05/07/2022
abr 28 20:49:35 pcricardo.grupmatrix kernel: Workqueue: events e1000_watchdog_task [e1000e]
abr 28 20:49:35 pcricardo.grupmatrix kernel: Call Trace:
abr 28 20:49:35 pcricardo.grupmatrix kernel:  <TASK>
abr 28 20:49:35 pcricardo.grupmatrix kernel:  dump_stack_lvl+0x43/0x60
abr 28 20:49:35 pcricardo.grupmatrix kernel:  __schedule_bug+0x56/0x70
abr 28 20:49:35 pcricardo.grupmatrix kernel:  __schedule+0xffa/0x13e0
abr 28 20:49:35 pcricardo.grupmatrix kernel:  ? ttwu_do_activate+0x6b/0x230
abr 28 20:49:35 pcricardo.grupmatrix kernel:  schedule+0x5a/0xd0
abr 28 20:49:35 pcricardo.grupmatrix kernel:  schedule_hrtimeout_range_clock+0xab/0x130
abr 28 20:49:35 pcricardo.grupmatrix kernel:  ? __pfx_hrtimer_wakeup+0x10/0x10
abr 28 20:49:35 pcricardo.grupmatrix kernel:  usleep_range_state+0x60/0x90
abr 28 20:49:35 pcricardo.grupmatrix kernel:  e1000e_read_phy_reg_mdic+0x83/0x270 [e1000e]
abr 28 20:49:35 pcricardo.grupmatrix kernel:  e1000e_update_stats+0x50c/0x730 [e1000e]
abr 28 20:49:35 pcricardo.grupmatrix kernel:  e1000_watchdog_task+0xdd/0xab0 [e1000e]
abr 28 20:49:35 pcricardo.grupmatrix kernel:  process_one_work+0x165/0x330
abr 28 20:49:35 pcricardo.grupmatrix kernel:  worker_thread+0x2f1/0x410
abr 28 20:49:35 pcricardo.grupmatrix kernel:  ? __pfx_worker_thread+0x10/0x10
abr 28 20:49:35 pcricardo.grupmatrix kernel:  kthread+0xe1/0x110
abr 28 20:49:35 pcricardo.grupmatrix kernel:  ? __pfx_kthread+0x10/0x10
abr 28 20:49:35 pcricardo.grupmatrix kernel:  ret_from_fork+0x2d/0x50
abr 28 20:49:35 pcricardo.grupmatrix kernel:  ? __pfx_kthread+0x10/0x10
abr 28 20:49:35 pcricardo.grupmatrix kernel:  ret_from_fork_asm+0x1b/0x30
abr 28 20:49:35 pcricardo.grupmatrix kernel:  </TASK>
abr 28 20:50:01 pcricardo.grupmatrix kernel: watchdog: BUG: soft lockup - CPU#3 stuck for 27s! [kworker/3:2:643]
abr 28 20:50:01 pcricardo.grupmatrix kernel: Modules linked in: rfcomm ip6t_REJECT nf_reject_ipv6 xt_comment ip6table_raw xt_recent xt_MASQUERADE ipt_IFWLOG ipt_psd xt_set >
abr 28 20:50:01 pcricardo.grupmatrix kernel:  btbcm btmtk bluetooth uas usb_storage hid_holtek_mouse input_leds ecdh_generic ecc nvidia(PO) snd_hda_codec_realtek snd_hda_co>
abr 28 20:50:01 pcricardo.grupmatrix kernel:  xhci_pci_renesas video wmi
abr 28 20:50:01 pcricardo.grupmatrix kernel: CPU: 3 PID: 643 Comm: kworker/3:2 Tainted: P        W  O       6.6.28-desktop-1.mga9 #1
abr 28 20:50:01 pcricardo.grupmatrix kernel: Hardware name: ASUS System Product Name/PRIME Z590M-PLUS, BIOS 1601 05/07/2022
abr 28 20:50:01 pcricardo.grupmatrix kernel: Workqueue: events linkwatch_event
abr 28 20:50:01 pcricardo.grupmatrix kernel: RIP: 0010:native_queued_spin_lock_slowpath+0x6a/0x2a0
abr 28 20:50:01 pcricardo.grupmatrix kernel: Code: 77 77 f0 0f ba 2b 08 0f 92 c2 8b 03 0f b6 d2 c1 e2 08 30 e4 09 d0 3d ff 00 00 00 77 53 85 c0 74 10 0f b6 03 84 c0 74 09 f>
abr 28 20:50:01 pcricardo.grupmatrix kernel: RSP: 0018:ffffc90000a8fbc0 EFLAGS: 00000202
abr 28 20:50:01 pcricardo.grupmatrix kernel: RAX: 0000000000000001 RBX: ffff88810851b428 RCX: 0000000000000000
abr 28 20:50:01 pcricardo.grupmatrix kernel: RDX: 0000000000000000 RSI: 0000000000000001 RDI: ffff88810851b428
abr 28 20:50:01 pcricardo.grupmatrix kernel: RBP: ffff8881a1fea134 R08: 0000000000000000 R09: 0000000000000004
abr 28 20:50:01 pcricardo.grupmatrix kernel: R10: ffff8881a1fea1fc R11: 0000000000000010 R12: ffff88810851b428
abr 28 20:50:01 pcricardo.grupmatrix kernel: R13: ffff8881a1fea000 R14: 0000000000000000 R15: 0000000000000000
abr 28 20:50:01 pcricardo.grupmatrix kernel: FS:  0000000000000000(0000) GS:ffff88883bac0000(0000) knlGS:0000000000000000
abr 28 20:50:01 pcricardo.grupmatrix kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
abr 28 20:50:01 pcricardo.grupmatrix kernel: CR2: 00007f463e241218 CR3: 00000001de81a002 CR4: 00000000007706e0
abr 28 20:50:01 pcricardo.grupmatrix kernel: PKRU: 55555554
abr 28 20:50:01 pcricardo.grupmatrix kernel: Call Trace:
abr 28 20:50:01 pcricardo.grupmatrix kernel:  <IRQ>
abr 28 20:50:01 pcricardo.grupmatrix kernel:  ? watchdog_timer_fn+0x1b4/0x220
abr 28 20:50:01 pcricardo.grupmatrix kernel:  ? __pfx_watchdog_timer_fn+0x10/0x10
abr 28 20:50:01 pcricardo.grupmatrix kernel:  ? __hrtimer_run_queues+0x10f/0x2b0
abr 28 20:50:01 pcricardo.grupmatrix kernel:  ? hrtimer_interrupt+0xf4/0x230
abr 28 20:50:01 pcricardo.grupmatrix kernel:  ? __sysvec_apic_timer_interrupt+0x49/0x140
abr 28 20:50:01 pcricardo.grupmatrix kernel:  ? sysvec_apic_timer_interrupt+0x69/0x90
abr 28 20:50:01 pcricardo.grupmatrix kernel:  </IRQ>
abr 28 20:50:01 pcricardo.grupmatrix kernel:  <TASK>
abr 28 20:50:01 pcricardo.grupmatrix kernel:  ? asm_sysvec_apic_timer_interrupt+0x16/0x20
abr 28 20:50:01 pcricardo.grupmatrix kernel:  ? native_queued_spin_lock_slowpath+0x6a/0x2a0
abr 28 20:50:01 pcricardo.grupmatrix kernel:  _raw_spin_lock+0x25/0x30
abr 28 20:50:01 pcricardo.grupmatrix kernel:  e1000e_get_stats64+0x1e/0x120 [e1000e]
abr 28 20:50:01 pcricardo.grupmatrix kernel:  dev_get_stats+0x5c/0x110
abr 28 20:50:01 pcricardo.grupmatrix kernel:  rtnl_fill_stats+0x3b/0x130
abr 28 20:50:01 pcricardo.grupmatrix kernel:  rtnl_fill_ifinfo+0x82f/0x14f0
abr 28 20:50:01 pcricardo.grupmatrix kernel:  ? kmalloc_reserve+0x62/0xf0
abr 28 20:50:01 pcricardo.grupmatrix kernel:  rtmsg_ifinfo_build_skb+0xaa/0x120
abr 28 20:50:01 pcricardo.grupmatrix kernel:  rtmsg_ifinfo+0x38/0x90
abr 28 20:50:01 pcricardo.grupmatrix kernel:  netdev_state_change+0x85/0x90
abr 28 20:50:01 pcricardo.grupmatrix kernel:  linkwatch_do_dev+0x49/0x60
abr 28 20:50:01 pcricardo.grupmatrix kernel:  __linkwatch_run_queue+0xd9/0x1f0
abr 28 20:50:01 pcricardo.grupmatrix kernel:  linkwatch_event+0x21/0x30
abr 28 20:50:01 pcricardo.grupmatrix kernel:  process_one_work+0x165/0x330
abr 28 20:50:01 pcricardo.grupmatrix kernel:  worker_thread+0x2f1/0x410
abr 28 20:50:01 pcricardo.grupmatrix kernel:  ? __pfx_worker_thread+0x10/0x10
abr 28 20:50:01 pcricardo.grupmatrix kernel:  kthread+0xe1/0x110
abr 28 20:50:01 pcricardo.grupmatrix kernel:  ? __pfx_kthread+0x10/0x10
abr 28 20:50:01 pcricardo.grupmatrix kernel:  ret_from_fork+0x2d/0x50
abr 28 20:50:01 pcricardo.grupmatrix kernel:  ? __pfx_kthread+0x10/0x10
abr 28 20:50:01 pcricardo.grupmatrix kernel:  ret_from_fork_asm+0x1b/0x30
abr 28 20:50:01 pcricardo.grupmatrix kernel:  </TASK>
lines 1938-1976/


added code tags ~Germ

Re: How to block updates due to problems with kernel 6.6.28

PostPosted: Apr 28th, '24, 22:13
by morgano
Feels like it is time to open a bug report and set to kernel and driver maintainers.

Re: How to block updates due to problems with kernel 6.6.28

PostPosted: Apr 29th, '24, 13:31
by ricard13
And how is it done from this point?

Re: How to block updates due to problems with kernel 6.6.28

PostPosted: Apr 29th, '24, 14:41
by Germ
See here: https://wiki.mageia.org/en/How_to_report_a_bug_properly

Re: How to block updates due to problems with kernel 6.6.28

PostPosted: Apr 29th, '24, 17:39
by doktor5000
I guess that might not be that helpful. It would probably be better to check your cables and the other devices along the cable for their settings.
Also definitely check beforehand if you have the latest BIOS upgrade for your mainboard installed.

Directly before the stack trace, link only negotiates to 10 Mbit:
abr 27 19:48:12 localhost kernel: e1000e 0000:00:1f.6 eno1: NIC Link is Up 10 Mbps Half Duplex, Flow Control: Rx/Tx


From other various reports on issues with the e1000e driver/chipset it is pretty flaky regarding autonegotiation and cable.
So check if you maybe only have a CAT5 cable, as normally autonegotiation should not end up below 1000Mbps or 10.000Mbps depending on your router/switches.

See e.g.
https://serverfault.com/questions/35407 ... -at-10mbps
https://bbs.archlinux.org/viewtopic.php?id=224183
https://patchwork.ozlabs.org/project/ne ... _plancton/
https://bugzilla.redhat.com/show_bug.cgi?id=1627816

Re: How to block updates due to problems with kernel 6.6.28

PostPosted: Apr 29th, '24, 21:49
by ricard13
This is not a fault, I have a bottleneck due to an old HUP that only works at 10. Tomorrow I will have a new device. I already tried borrowing.

Re: How to block updates due to problems with kernel 6.6.28

PostPosted: May 4th, '24, 07:19
by ricard13
problem solved. It was an update. Possibly from krb5.

https://bugs.mageia.org/show_bug.cgi?id=33157

Re: How to block updates due to problems with kernel 6.6.28

PostPosted: May 4th, '24, 13:53
by isadora
Would you be so kind, to mark the topic solved.
You can do so, by writing [SOLVED] leftwards of the topic-title in your first message.
Thanks ahead. ;)
All times are UTC + 1 hour [ DST ]
Page 1 of 1
Powered by phpBB® Forum Software © phpBB Group
https://www.phpbb.com/