Bug 33157 - problems with startup in kernel 6.6.28 possible failure of i219 network card (e1000e)
Summary: problems with startup in kernel 6.6.28 possible failure of i219 network card ...
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 9
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Kernel and Drivers maintainers
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-04-29 21:52 CEST by Ricard Alfe
Modified: 2024-05-04 06:55 CEST (History)
2 users (show)

See Also:
Source RPM: kernel 6.6.28
CVE:
Status comment:


Attachments

Description Ricard Alfe 2024-04-29 21:52:03 CEST
Description of problem:

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.)


Version-Release number of selected component (if applicable): 
               kernel-desktop-6.6.28-1.mga9.x86_64


[root@pcricardo ~]# inxi -SMCGN
System:
  Host: pcr Kernel: 6.6.22-desktop-1.mga9 arch: x86_64
    bits: 64 Console: pty pts/0 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: 210xxxxxxxx
    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: 836 min/max: 800/5100 cores: 1: 1382 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 dri: nouveau gpu: nouveau resolution: 1920x1080~60Hz
  API: OpenGL v: 4.3 Mesa 24.0.5 renderer: NV126
Network:
  Device-1: Intel Ethernet I219-V driver: e1000e






How reproducible: Yes


Steps to Reproduce:


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.

      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


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/
Comment 1 Morgan Leijström 2024-04-30 17:44:39 CEST
Apparently from https://forums.mageia.org/en/viewtopic.php?t=15343

Thank you Richard for opening this issue.

I set it directly to kernel and driver team.

CC: (none) => fri
Component: Installer => RPM Packages

Morgan Leijström 2024-04-30 17:45:16 CEST

Assignee: bugsquad => kernel

Comment 2 w unruh 2024-05-03 00:41:47 CEST
So it looks like we should regress from 6.6.28 to an earlier kernel version.

CC: (none) => unruh

Comment 3 Morgan Leijström 2024-05-03 11:01:54 CEST
@w unruh, are you seeing the same?
Comment 4 w unruh 2024-05-03 17:27:48 CEST
(In reply to Morgan Leijström from comment #3)
> @w unruh, are you seeing the same?

No. mine was not as bad. the network-up worked and the D?M login screen came up quickly. The ony peoblem was with X not coming up.bot just freezing instead(with everything else seemingly working). The comment about Xorg maybe being involved makes sense on mine. Ie everything else working except X (including alt-ctl-Bsp-Bsp working, which says at least paet of X working. Under sddm, I got stuck with a curor arrow on the screen with the little dynamic dots circling the arrow, whick usually shows up for about 1/10th of a second before the plasma desktop background shows up. Here the Desktop background does not show up.The login box from sddm and for lightdm goes away, leavibg just the DM backgound.

I was also using the 6.6.28 kernel. I did not even think about the kernel being part of the problem, so did not think about trying an earlier kernel at booyup.

As I said I got around the problem by reinstalling Mga9 into a spare partition, and am using that. Unfortunately the computer needs to used for work, so further experimenting is hard.
Comment 5 w unruh 2024-05-03 17:33:15 CEST
Note as mentioned I do not have the problem with the mains cable. Mine did not wotk independently of the state of plugin. Ie his seems to be much worse than mine-- more disperate things don't work. On the otherhand I am using wireless mot ethernet and thus cannot plug in and remove the ethernet cable.
Comment 6 Morgan Leijström 2024-05-03 17:43:23 CEST
(In reply to w unruh from comment #4)
> > @w unruh, are you seeing the same?
> 
> I was also using the 6.6.28 kernel.
> I did not even think about the kernel being part of the problem
...
> I got around the problem by reinstalling Mga9

So after reinstallation it runs OK with kernel desktop 6.6.28?
 
If so, I believe the real problem is something else, but the kernel difference is one part of factors that trigs the problem.
Comment 7 w unruh 2024-05-03 18:01:28 CEST
Yes the reinstall  is working with kernel 6.6.28.

It was working fine before and the problem just suddenly appeared. It might have been just after an update, but someone else is using the machine, so I do not know the timeline.
Comment 8 Ricard Alfe 2024-05-03 19:36:20 CEST
I'm going to try installing it again. I've seen that there are other updates that are tied to the kernel and it may be their fault. Before, I only had the cpupower and lb64bpf1 kernel pending

  cpupower 6.6.28 1.mga9 x86_64
   freerdp 2.11.7 1.mga9 x86_64
   kernel-desktop 6.6.28 1.mga9 x86_64
   kernel-desktop-devel 6.6.28 1.mga9 x86_64
   kernel-desktop-latest 6.6.28 1.mga9 x86_64
   kernel-userspace-headers 6.6.28 1.mga9 x86_64
   krb5 1.20.1 1.1.mga9 x86_64
   lib64archive13 3.6.2 5.1.mga9 x86_64
   lib64bpf1 6.6.28 1.mga9 x86_64
   lib64freerdp2 2.11.7 1.mga9 x86_64
   lib64krb53 1.20.1 1.1.mga9 x86_64
   lib64krb53-devel 1.20.1 1.1.mga9 x86_64
Comment 9 Ricard Alfe 2024-05-03 19:58:47 CEST
Well this all works fine. It should be a topic for you to update some of the new ones. This topic can be closed. Thanks for everything.
Comment 10 Ricard Alfe 2024-05-04 06:55:16 CEST
Well this all works fine. It should be a topic for you to update some of the new ones. This topic can be closed. Thanks for everything.

Status: NEW => RESOLVED
Resolution: (none) => FIXED


Note You need to log in before you can comment on or make changes to this bug.