Randomly, after some time using the PC, the network card crashes and it's impossible to recover connectivity
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned | ||
linux-firmware (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
The latest version either of linxu or linux-firmware package has a bug affecting some ethernet LAN devices causing them to randomly crash after a long period of time -around 24h- being active. The bug reported by the kernel is: NETDEV WATCHDOG: enp1s0 (r8169): transmit queue 0 timed out
The complete stack trace is shown below:
NETDEV WATCHDOG: enp1s0 (r8169): transmit queue 0 timed out
WARNING: CPU: 1 PID: 0 at net/sched/
Modules linked in: cdc_ether usbnet r8152 mii vhost_net vhost vhost_iotlb tap tls veth xt_nat xt_CHECKSUM xt_MASQUERADE nf_conntrack_
snd_usb_audio snd_hda_codec i915 irqbypass snd_usbmidi_lib snd_hda_core crct10dif_pclmul polyval_clmulni mc snd_hwdep polyval_generic ghash_clmulni_intel snd_pcm sha512_ssse3 drm_buddy aesni_intel snd_seq_midi crypto_simd ttm snd_seq_midi_event drm_display_helper snd_rawmidi cryptd cec cmdlinepart rc_core snd_seq drm_kms_helper rapl snd_seq_device snd_timer spi_nor i2c_algo_bit syscopyarea intel_cstate snd joydev input_leds mtd wmi_bmof ee1004 soundcore mei_me sysfillrect sysimgblt mei intel_pch_thermal mac_hid acpi_pad acpi_tad sch_fq_codel nct6775 nct6775_core hwmon_vid coretemp nfsd msr parport_pc auth_rpcgss ppdev nfs_acl lockd lp ramoops pstore_blk grace parport drm reed_solomon pstore_zone efi_pstore sunrpc ip_tables x_tables autofs4 btrfs blake2b_generic raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear hid_generic usbhid hid crc32_pclmul spi_intel_pci i2c_i801 r8169 spi_intel ahci i2c_smbus
xhci_pci realtek libahci xhci_pci_renesas video wmi
CPU: 1 PID: 0 Comm: swapper/1 Not tainted 6.2.0-26-generic #26~22.04.1-Ubuntu
Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./H310M-HDV, BIOS P3.30 10/24/2018
RIP: 0010:dev_
Code: 00 e9 31 ff ff ff 4c 89 e7 c6 05 f5 a9 78 01 01 e8 c6 ff f7 ff 44 89 f1 4c 89 e6 48 c7 c7 08 30 84 93 48 89 c2 e8 31 0b 2c ff <0f> 0b e9 22 ff ff ff 66 2e 0f 1f 84 00 00 00 00 00 90 90 90 90 90
RSP: 0018:ffffc37380
RAX: 0000000000000000 RBX: ffffa0ac95fb84c8 RCX: 0000000000000000
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
RBP: ffffc3738003ce98 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000000 R12: ffffa0ac95fb8000
R13: ffffa0ac95fb841c R14: 0000000000000000 R15: 0000000000000000
FS: 000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000055b6d6e550e0 CR3: 0000000029c10006 CR4: 00000000003726e0
Call Trace:
<IRQ>
? __pfx_dev_
call_timer_
? __pfx_dev_
__run_
? ktime_get+0x43/0xc0
? __pfx_tick_
? lapic_next_
? clockevents_
run_timer_
__do_softirq+
? hrtimer_
__irq_
irq_exit_
sysvec_
</IRQ>
<TASK>
asm_sysvec_
RIP: 0010:cpuidle_
Code: a6 51 6d e8 b4 5f 45 ff 8b 53 04 49 89 c7 0f 1f 44 00 00 31 ff e8 72 3e 44 ff 80 7d d0 00 0f 85 e8 00 00 00 fb 0f 1f 44 00 00 <45> 85 f6 0f 88 0f 02 00 00 4d 63 ee 49 83 fd 09 0f 87 c4 04 00 00
RSP: 0018:ffffc37380
RAX: 0000000000000000 RBX: ffffe3737fc40300 RCX: 0000000000000000
RDX: 0000000000000001 RSI: 0000000000000000 RDI: 0000000000000000
RBP: ffffc37380107e78 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000000 R12: ffffffff942c22c0
R13: 0000000000000003 R14: 0000000000000003 R15: 000059122db05713
? cpuidle_
cpuidle_
cpuidle_
do_idle+0x82/0x110
cpu_startup_
start_
secondary_
</TASK>
The stack trace is visible in the journal under the name "kernel". My guess is that it's either kernel-related or because of the firmware package.
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-firmware 20220329.
ProcVersionSign
Uname: Linux 5.19.0-50-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/
/dev/snd/
CasperMD5CheckR
CurrentDesktop: ubuntu:GNOME
Date: Fri Aug 25 12:45:13 2023
Dependencies: firmware-sof-signed 2.0-1ubuntu4.1
InstallationDate: Installed on 2022-03-07 (535 days ago)
InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1)
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
PackageArchitec
ProcEnviron:
PATH=(custom, no user)
XDG_RUNTIME_
LANG=es_ES.UTF-8
SHELL=/usr/bin/zsh
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=
RelatedPackageV
linux-
linux-
linux-firmware 20220329.
RfKill:
SourcePackage: linux-firmware
UpgradeStatus: Upgraded to jammy on 2022-08-22 (368 days ago)
dmi.bios.date: 10/24/2018
dmi.bios.release: 5.13
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P3.30
dmi.board.name: H310M-HDV
dmi.board.vendor: ASRock
dmi.chassis.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.
dmi.modalias: dmi:bvnAmerican
dmi.product.family: To Be Filled By O.E.M.
dmi.product.name: To Be Filled By O.E.M.
dmi.product.sku: To Be Filled By O.E.M.
dmi.product.
dmi.sys.vendor: To Be Filled By O.E.M.
The firmware for this NIC hasn't been updated since 2015 so it's not a firmware regression. Adding 'linux'.