The latest version in jammy-updates is now 5.15.0-105.115 and 5.15.0-106.116 in 
proposed.
Paul, could you give them a try?

** Changed in: linux (Ubuntu)
       Status: New => Incomplete

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2058109

Title:
  Kernel 5.15.0-100 breaks Intel NIC

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  From syslog:
  Mar 15 12:11:18 kvmMini systemd[1]: Starting Refresh fwupd metadata and 
update motd...
  Mar 15 12:11:18 kvmMini fwupdmgr[284042]: Updating lvfs
  Mar 15 12:11:18 kvmMini fwupdmgr[284042]: Downloading…: 0%
  Mar 15 12:11:19 kvmMini fwupdmgr[284042]: Idle…: 100%
  Mar 15 12:11:19 kvmMini fwupdmgr[284042]: Idle…: 100%
  Mar 15 12:11:19 kvmMini fwupdmgr[284042]: Downloading…: 100%
  Mar 15 12:11:19 kvmMini fwupdmgr[284042]: Downloading…: 0%
  Mar 15 12:11:19 kvmMini fwupdmgr[284042]: Downloading…: 1%
  Mar 15 12:11:19 kvmMini fwupdmgr[284042]: Downloading…: 2%
  Mar 15 12:11:19 kvmMini fwupdmgr[284042]: Downloading…: 3%
  ...trimmed content
  Mar 15 12:11:19 kvmMini fwupdmgr[284042]: Downloading…: 97%
  Mar 15 12:11:19 kvmMini fwupdmgr[284042]: Downloading…: 98%
  Mar 15 12:11:19 kvmMini fwupdmgr[284042]: Idle…: 100%
  Mar 15 12:11:19 kvmMini fwupdmgr[284042]: Idle…: 100%
  Mar 15 12:11:20 kvmMini fwupdmgr[284042]: Successfully downloaded new 
metadata: 0 local devices supported
  Mar 15 12:11:20 kvmMini systemd[1]: fwupd-refresh.service: Deactivated 
successfully.
  Mar 15 12:11:20 kvmMini systemd[1]: Finished Refresh fwupd metadata and 
update motd.
  Mar 15 12:17:01 kvmMini CRON[284549]: (root) CMD (   cd / && run-parts 
--report /etc/cron.hourly)
  Mar 15 12:23:59 kvmMini kernel: [3519186.337746] x86/split lock detection: 
#AC: CPU 0/KVM/2230725 took a split_lock trap at address: 0xfffff80746442fb3
  Mar 15 12:26:49 kvmMini kernel: [3519356.515727] x86/split lock detection: 
#AC: CPU 0/KVM/2230725 took a split_lock trap at address: 0xfffff80746442fb3
  Mar 15 13:05:00 kvmMini systemd[1]: 
run-docker-runtime\x2drunc-moby-5ac73dacfde5bc72437e376d9f1d536f9da1ec70ebdb172d498c0f14b2a79bc4-runc.5pHMXa.mount:
 Deactivated successfully.
  Mar 15 13:07:48 kvmMini kernel: [3521815.001961] x86/split lock detection: 
#AC: CPU 0/KVM/279304 took a split_lock trap at address: 0xfffff80521c42fb3
  Mar 15 13:17:01 kvmMini CRON[289583]: (root) CMD (   cd / && run-parts 
--report /etc/cron.hourly)
  Mar 15 13:20:49 kvmMini kernel: [3522596.527060] x86/split lock detection: 
#AC: CPU 0/KVM/2230725 took a split_lock trap at address: 0xfffff80746442fb3
  Mar 15 13:30:01 kvmMini systemd[1]: 
run-docker-runtime\x2drunc-moby-5ac73dacfde5bc72437e376d9f1d536f9da1ec70ebdb172d498c0f14b2a79bc4-runc.I79KlX.mount:
 Deactivated successfully.
  Mar 15 13:43:22 kvmMini kernel: [3523948.983970] x86/split lock detection: 
#AC: CPU 0/KVM/279304 took a split_lock trap at address: 0xfffff80521c42fb3
  Mar 15 13:53:22 kvmMini kernel: [3524549.046156] x86/split lock detection: 
#AC: CPU 0/KVM/1774 took a split_lock trap at address: 0xfffff8041de42fb3
  Mar 15 14:07:33 kvmMini systemd[1]: 
run-docker-runtime\x2drunc-moby-5ac73dacfde5bc72437e376d9f1d536f9da1ec70ebdb172d498c0f14b2a79bc4-runc.K8Zq9M.mount:
 Deactivated successfully.
  Mar 15 14:17:01 kvmMini CRON[294744]: (root) CMD (   cd / && run-parts 
--report /etc/cron.hourly)
  Mar 15 14:20:03 kvmMini kernel: [3526150.403065] e1000e 0000:00:1f.6 eno2: 
Detected Hardware Unit Hang:
  Mar 15 14:20:03 kvmMini kernel: [3526150.403065]   TDH                  <9f>
  Mar 15 14:20:03 kvmMini kernel: [3526150.403065]   TDT                  <9>
  Mar 15 14:20:03 kvmMini kernel: [3526150.403065]   next_to_use          <9>
  Mar 15 14:20:03 kvmMini kernel: [3526150.403065]   next_to_clean        <9e>
  Mar 15 14:20:03 kvmMini kernel: [3526150.403065] buffer_info[next_to_clean]:
  Mar 15 14:20:03 kvmMini kernel: [3526150.403065]   time_stamp           
<1348a0aab>
  Mar 15 14:20:03 kvmMini kernel: [3526150.403065]   next_to_watch        <9f>
  Mar 15 14:20:03 kvmMini kernel: [3526150.403065]   jiffies              
<1348a0bb0>
  Mar 15 14:20:03 kvmMini kernel: [3526150.403065]   next_to_watch.status <0>
  Mar 15 14:20:03 kvmMini kernel: [3526150.403065] MAC Status             
<40080083>
  Mar 15 14:20:03 kvmMini kernel: [3526150.403065] PHY Status             <796d>
  Mar 15 14:20:03 kvmMini kernel: [3526150.403065] PHY 1000BASE-T Status  <3800>
  Mar 15 14:20:03 kvmMini kernel: [3526150.403065] PHY Extended Status    <3000>
  Mar 15 14:20:03 kvmMini kernel: [3526150.403065] PCI Status             <10>
  Mar 15 14:20:05 kvmMini kernel: [3526152.391042] e1000e 0000:00:1f.6 eno2: 
Detected Hardware Unit Hang:
  Mar 15 14:20:05 kvmMini kernel: [3526152.391042]   TDH                  <9f>
  Mar 15 14:20:05 kvmMini kernel: [3526152.391042]   TDT                  <9>
  Mar 15 14:20:05 kvmMini kernel: [3526152.391042]   next_to_use          <9>
  Mar 15 14:20:05 kvmMini kernel: [3526152.391042]   next_to_clean        <9e>
  Mar 15 14:20:05 kvmMini kernel: [3526152.391042] buffer_info[next_to_clean]:
  Mar 15 14:20:05 kvmMini kernel: [3526152.391042]   time_stamp           
<1348a0aab>
  Mar 15 14:20:05 kvmMini kernel: [3526152.391042]   next_to_watch        <9f>
  Mar 15 14:20:05 kvmMini kernel: [3526152.391042]   jiffies              
<1348a0da1>
  Mar 15 14:20:05 kvmMini kernel: [3526152.391042]   next_to_watch.status <0>
  Mar 15 14:20:05 kvmMini kernel: [3526152.391042] MAC Status             
<40080083>
  Mar 15 14:20:05 kvmMini kernel: [3526152.391042] PHY Status             <796d>
  Mar 15 14:20:05 kvmMini kernel: [3526152.391042] PHY 1000BASE-T Status  <3800>
  Mar 15 14:20:05 kvmMini kernel: [3526152.391042] PHY Extended Status    <3000>
  Mar 15 14:20:05 kvmMini kernel: [3526152.391042] PCI Status             <10>

  
  root@kvmMini:~# dmesg | grep e1000e
  [    1.525823] e1000e: Intel(R) PRO/1000 Network Driver
  [    1.530406] e1000e: Copyright(c) 1999 - 2015 Intel Corporation.
  [    1.530762] e1000e 0000:00:1f.6: Interrupt Throttling Rate (ints/sec) set 
to dynamic conservative mode
  [    2.207404] e1000e 0000:00:1f.6 0000:00:1f.6 (uninitialized): registered 
PHC clock
  [    2.278513] e1000e 0000:00:1f.6 eth0: (PCI Express:2.5GT/s:Width x1) 
d8:5e:d3:8f:38:08
  [    2.278576] e1000e 0000:00:1f.6 eth0: Intel(R) PRO/1000 Network Connection
  [    2.278768] e1000e 0000:00:1f.6 eth0: MAC: 14, PHY: 12, PBA No: FFFFFF-0FF
  [    2.280195] e1000e 0000:00:1f.6 eno2: renamed from eth0

  
  root@kvmMini:~# dmesg | grep igc
  [    1.509192] igc 0000:ae:00.0: PTM enabled, 4ns granularity
  [    1.569763] igc 0000:ae:00.0 (unnamed net_device) (uninitialized): PHC 
added
  [    1.600516] igc 0000:ae:00.0: 4.000 Gb/s available PCIe bandwidth (5.0 
GT/s PCIe x1 link)
  [    1.603376] igc 0000:ae:00.0 eth0: MAC: d8:5e:d3:8f:38:09
  [    1.611230] igc 0000:ae:00.0 enp174s0: renamed from eth0

  Both NICs will not work with this kernel. I had to revert back to
  5.15.0-92

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2058109/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to     : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to