Huh, maybe related to the switch these two computers are both connected to?

[   93.999895] ------------[ cut here ]------------
[   93.999933] NETDEV WATCHDOG: enp1s0 (r8169): transmit queue 0 timed out
[   93.999985] WARNING: CPU: 3 PID: 0 at net/sched/sch_generic.c:467
dev_watchdog+0x260/0x270
[   93.999992] Modules linked in: nft_counter 8021q garp stp mrp llc
xt_tcpudp xt_state xt_conntrack nf_conntrack nf_defrag_ipv6
nf_defrag_i
pv4 nft_compat nf_tables libcrc32c nfnetlink ath3k btusb btrtl btbcm
nls_ascii btintel nls_cp437 vfat bluetooth fat snd_hda_codec_hdmi
jitte
rentropy_rng snd_hda_codec_realtek x86_pkg_temp_thermal
intel_powerclamp drbg snd_hda_codec_generic coretemp ledtrig_audio
ath9k ath9k_commo
n snd_hda_intel snd_intel_dspcfg kvm_intel i915 soundwire_intel
ath9k_hw soundwire_generic_allocation snd_soc_core ath kvm mac80211
snd_comp
ress soundwire_cadence irqbypass snd_hda_codec snd_hda_core
aes_generic ghash_clmulni_intel snd_hwdep soundwire_bus cfg80211
snd_pcm snd_tim
er mei_me aesni_intel drm_kms_helper ansi_cprng intel_rapl_msr snd
crypto_simd processor_thermal_device ecdh_generic cryptd ecc rfkill
iTCO_
wdt cec evdev glue_helper libaes mei intel_rapl_common libarc4
soundcore intel_pmc_bxt i2c_algo_bit rapl int340x_thermal_zone tpm_tis
iTCO_v
endor_support at24
[   94.000697]  intel_soc_dts_iosf watchdog intel_pch_thermal
tpm_tis_core intel_cstate sg intel_uncore tpm rng_core pcspkr
efi_pstore butto
n drm fuse configfs efivarfs ip_tables x_tables autofs4 ext4 crc16
mbcache jbd2 crc32c_generic sd_mod t10_pi crc_t10dif crct10dif_generic
ah
ci xhci_pci libahci xhci_hcd libata crct10dif_pclmul crct10dif_common
crc32_pclmul r8169 crc32c_intel usbcore scsi_mod realtek mdio_devres l
ibphy i2c_i801 i2c_smbus lpc_ich usb_common fan video
[   94.001059] CPU: 3 PID: 0 Comm: swapper/3 Not tainted
5.10.0-17-amd64 #1 Debian 5.10.136-1
[   94.001067] Hardware name: GOOGLE Panther/Panther, BIOS
MrChromebox-4.10 08/22/2019
[   94.001089] RIP: 0010:dev_watchdog+0x260/0x270
[   94.001103] Code: eb a9 48 8b 1c 24 c6 05 5f be 0d 01 01 48 89 df
e8 35 75 fa ff 44 89 e9 48 89 de 48 c7 c7 78 cf 76 9f 48 89 c2 e8 b5
99
14 00 <0f> 0b eb 86 66 66 2e 0f 1f 84 00 00 00 00 00 90 0f 1f 44 00 00 41
[   94.001118] RSP: 0018:ffff96d20012ceb0 EFLAGS: 00010282
[   94.001134] RAX: 0000000000000000 RBX: ffff88fc40af2000 RCX: 000000000000083f
[   94.001145] RDX: 0000000000000000 RSI: 00000000000000f6 RDI: 000000000000083f
[   94.001155] RBP: ffff88fc40af23dc R08: 0000000000000000 R09: ffff96d20012ccd0
[   94.001166] R10: ffff96d20012ccc8 R11: ffffffff9fccb448 R12: ffff88fcb4bd0280
[   94.001177] R13: 0000000000000000 R14: ffff88fc40af2480 R15: 0000000000000001
[   94.001188] FS:  0000000000000000(0000) GS:ffff88fcb4b80000(0000)
knlGS:0000000000000000
[   94.001199] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[   94.001207] CR2: 00007ff9f1380860 CR3: 000000015ee0a002 CR4: 00000000001706e0
[   94.001219] Call Trace:
[   94.001228]  <IRQ>
[   94.001247]  ? pfifo_fast_enqueue+0x150/0x150
[   94.001264]  call_timer_fn+0x29/0x100
[   94.001277]  __run_timers.part.0+0x1d9/0x250
[   94.001294]  ? recalibrate_cpu_khz+0x10/0x10
[   94.001308]  ? ktime_get+0x38/0xa0
[   94.001324]  ? lapic_next_deadline+0x28/0x40
[   94.001335]  ? clockevents_program_event+0x8d/0xf0
[   94.001346]  run_timer_softirq+0x26/0x50
[   94.001363]  __do_softirq+0xc5/0x279
[   94.001376]  asm_call_irq_on_stack+0x12/0x20
[   94.001386]  </IRQ>
[   94.001402]  do_softirq_own_stack+0x37/0x50
[   94.001419]  irq_exit_rcu+0x92/0xc0
[   94.001435]  sysvec_apic_timer_interrupt+0x36/0x80
[   94.001450]  asm_sysvec_apic_timer_interrupt+0x12/0x20
[   94.001464] RIP: 0010:cpuidle_enter_state+0xc7/0x350
[   94.001477] Code: 8b 3d 5d da 34 61 e8 78 0a a0 ff 49 89 c5 0f 1f
44 00 00 31 ff e8 e9 15 a0 ff 45 84 ff 0f 85 fe 00 00 00 fb 66 0f 1f
44
00 00 <45> 85 f6 0f 88 0a 01 00 00 49 63 c6 4c 2b 2c 24 48 8d 14 40 48 8d
[   94.001487] RSP: 0018:ffff96d20009fea8 EFLAGS: 00000246
[   94.001503] RAX: ffff88fcb4bafd40 RBX: 0000000000000008 RCX: 000000000000001f
[   94.001510] RDX: 0000000000000000 RSI: 000000004b77ec53 RDI: 0000000000000000
[   94.001523] RBP: ffff88fcb4bb9a00 R08: 00000015e2d42563 R09: 00000015e2bc50e3
[   94.001530] R10: 00000000000353b7 R11: 00000000000088ad R12: ffffffff9fdae7c0
[   94.001541] R13: 00000015e2d42563 R14: 0000000000000008 R15: 0000000000000000
[   94.001560]  ? cpuidle_enter_state+0xb7/0x350
[   94.001574]  cpuidle_enter+0x29/0x40
[   94.001593]  do_idle+0x1f3/0x2b0
[   94.001609]  cpu_startup_entry+0x19/0x20
[   94.001626]  secondary_startup_64_no_verify+0xb0/0xbb
[   94.001641] ---[ end trace 9c348499639096c8 ]---

On Fri, Sep 23, 2022 at 8:39 PM Debian Bug Tracking System
<ow...@bugs.debian.org> wrote:
>
> Thank you for filing a new Bug report with Debian.
>
> You can follow progress on this Bug here: 1020597: 
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020597.
>
> This is an automatically generated reply to let you know your message
> has been received.
>
> Your message is being forwarded to the package maintainers and other
> interested parties for their attention; they will reply in due course.
>
> Your message has been sent to the package maintainer(s):
>  unknown-pack...@qa.debian.org
>
> If you wish to submit further information on this problem, please
> send it to 1020...@bugs.debian.org.
>
> Please do not send mail to ow...@bugs.debian.org unless you wish
> to report a problem with the Bug-tracking system.
>
> --
> 1020597: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020597
> Debian Bug Tracking System
> Contact ow...@bugs.debian.org with problems



-- 
Jiann-Ming Su

Reply via email to